How To Use Acumatica Erp

Size: px
Start display at page:

Download "How To Use Acumatica Erp"

Transcription

1 System Administration Training Guide S400 Introduction to Acumatica Technology

2 Table of contents Certification Course Prerequisites... 4 Introduction to Acumatica Web Services... 6 Learning Objects:... 6 Web Services API Overview... 6 Web Services Calls... 6 Web Services API Objects... 7 Generating Web Services... 7 Introduction to Acumatica ERP Customization... 8 Learning Objects:... 8 Acumatica ERP Customization: Basic Concepts... 8 Identifying Changes to the Acumatica ERP Application Planning Changes in Data Presentation Planning Changes in Workflow Rules Delegating Customization Role Privileges to Acumatica ERP Users Customization Development Customization Deployment Working on a Project UI Customization Functional Customization Moving and arranging fields Examples of Customization Adding a TextEdit Input Field onto a Form Adding Selector Fields onto a Form Adding a Combo Box onto a Form Page 2 of 97

3 Adding a Column to a Grid Control Adding a Column to a Lookup Window Implementing a Custom Event Page 3 of 97

4 Certification Course Prerequisites This course consists of Hands-On guide that will walk you through the specifics of the Integration Services. The guide is intended for a half-day on-site training. You will perform the exercises in your installed copy of Acumatica with the Template DATA that is provided with the Acumatica installation package. Prior to start the Hands-on Guide, make sure to activate all the features of the Application using the Common Settings: 1. Open Enable/Disable Features form (CS ) a. Configuration > Common Settings > Licensing > Enable/Disable Features 2. Click the Modify button from the tool bar 3. Confirm that the features are enable/disable as follows: Field Organization Customer Management Project Management Time Reporting on Activity Finance Multi-Branch Support Inter-Branch Transactions Multi-Currency Accounting Deferred Revenue Management Subaccounts Fixed Assets Management VAT Reporting Invoice Rounding Support for Expense Reclassification Contract Management Tax Entry from GL Module ROT & RUT Deduction Consolidated Posting to GL Volume Pricing Distribution Inventory Subitems Automatic Packaging Warehouses Warehouse Locations Blanket Purchase Orders Drop Shipments Multiple Unit of Measure Value {checked} {checked} {checked} {checked} {checked} {checked} {checked} {checked} {checked} {checked} {checked} {checked} {unchecked} {unchecked} {checked} {unchecked} {unchecked} {checked} {unchecked} {checked} {checked} {checked} {checked} {checked} {checked} {checked} {checked} Page 4 of 97

5 Misc Row-Level Security Field-Level Audit Avalara Tax Integration Address Validation Notification Module {checked} {checked} {checked} {checked} {checked} {checked} 4. Save your changes 5. Click the Activate button from the tool bar 6. Also, in General Ledger, generate the Financial Period up to today s financial period and year. Page 5 of 97

6 Introduction to Acumatica Web Services Learning Objects: Understand concepts behind Acumatica web services. The Acumatica Web Services Application Programming Interface (API) provides a fast, reliable, and convenient way of exposing business functionality and data managed by an Acumatica application for integration with any external business and operation support system. The Acumatica API is based on web service standards, such as SOAP and WSDL, and can be accessed with almost any current programming environment or integration tool. By using the development environment you are familiar with, you can easily create a client application that accesses the Acumatica Studio application through standard web services protocols to do any of the following: Authorize the programmer with the server running the Acumatica application Get query and access information from the Acumatica application Import information into the Acumatica application Create, update, and delete objects in the Acumatica application Execute some long-running processes and perform administrative tasks Every operation that uses the Acumatica API is executed through the same business logic layer as the user interface. Web Services API Overview Acumatica introduces a simple, streamlined way of interacting with its web services. The system automatically generates a WSDL file describing the operations (services) and list of parameters and objects; you can access this file through the Web Services (SM ) form. You can implement advanced integration scenarios involving operations on one or more forms by using the new web services configuration form to generate custom WSDL files. All the functionality of the application is available through the Web Services API; however, the functionality and information that will be exposed and available to the web services client depends on the access rights granted to the user logged in as a client to the Acumatica ERP instance. Web Services Calls To execute the API call, you need to prepare the SOAP message and send it to the remote server that provides web services by using the HTTP/HTTPS protocol. To simplify this process, most development environments (such as Microsoft Visual Studio and Page 6 of 97

7 NetBeans) support importing of the WSDL definition file and provide automation tools for the creation of proxy classes. This approach enables you to access the object model in a convenient and familiar way, while ensuring compile-time verification of the web services calls. Web Services API Objects Interaction with the API is made through an object called Screen. This object acts as a gateway between the web services client and Acumatica Inc., so that you can log in and retrieve, insert, update, or delete data, as well as perform any action that may be exposed by the form. The preparation and execution of web services calls is facilitated by the Content object, which you can retrieve by calling the GetSchema()API function. This function returns an object that closely matches the way the form is presented to the end user. Each area on the form is mapped to an object in the Content object. For example, the Account Settings area in the General Info tab of the Customers(AR ) form is defined in the GeneralInfoAccountSettings object. This object exposes a public property for every field in this area. Actions that can be performed in the form are exposed in a property called Actions. To execute an API call, you must build an array of commands and submit it to the form by calling the Submit() function. To process batch import and export operations, you define a scenario and use the Import() and Export() functions. Generating Web Services Acumatica ERP automatically generates a WSDL file describing the operations (services) and an XML description of parameters and objects for a form or multiple forms. You can access this file through the Web Services (SM ) form of Acumatica ERP. Page 7 of 97

8 Introduction to Acumatica ERP Customization Learning Objects: Understand Acumatica Customization Engine and learn to perform basic customization tasks that do not involve programming. With Acumatica ERP web-based customization tools, you can change the look and functionality of forms. By using these tools, you can create, configure, and maintain custom user interface elements for Acumatica ERP applications, as well as the functionality of the modules developed with Acumatica Framework. Acumatica ERP Customization: Basic Concepts Customization Project A project is a set of steps designed to customize either Acumatica ERP or another application developed in Acumatica Framework and used by a company. A step might be, for instance, adding a user interface (UI) element on a form. Within a project, you can customize UI and form elements and the properties of elements, and you can implement additional program code that changes some application logic. Specialists who will work on customization projects should be assigned the Customizer role so they can use Acumatica ERP customization tools. You can optimize various UIs and business processes within a project, following customization requirements that your company s managers have defined. By the time you complete a project, you will have developed the customization code and updated the production application, merging customization code with the existing application code. Page Design Mode You use Page Design mode when working with a form to adjust the properties of UI form elements (input fields, check boxes, panels, and buttons), add new elements onto the form, and hide existing elements. You can bind newly added elements with data fields simultaneously added to an appropriate database table. You can change the locations of UI elements on the selected area (main form, grid control, or tab) of a form template, as well as the quantity and location of tabs and grids. A form template is one of the form structures predefined by Acumatica ERP developers. You can easily add UI elements onto the form templates. Page 8 of 97

9 You can program a form to react to certain events for example, when the user clicks buttons to invoke appropriate pop-up forms. Also, you can change the UI elements and properties of pop-up forms. When you enter Page Design mode, the system also makes these pop-up forms available for UI customization. In Page Design mode, you can also perform a functional customization, which means adding custom code that changes the business logic and database structure of the application. Customization Session Every time you log in, open a customization project, and enter Page Design mode, the system starts a new customization session. When each customization session begins, new customization code is created or the existing customization code is opened for editing. (With existing code, Page Design mode starts automatically, right after you select the project name, for all the forms already changed within all of the previous customization sessions.) During a customization session, you can change the appearance of Acumatica ERP forms by adding or removing UI elements. You can also alter system behavior with custom events, add and modify system objects, change objects properties, and add custom code fragments to the application. The system automatically updates the customization code of the project when you use the Acumatica ERP customization tools to make changes to the application. You can also manually edit the customization code during the current customization session and save these changes. The customization session ends when you close the current project. When you continue the customization process and start a new customization session, the system automatically loads the customization code of the project, which includes saved changes from all previous customization sessions. After you open a project in Page Design mode, you can view and edit all changes made to the application within the project by customizers. Multiple customizers may not publish the same project simultaneously. Customization Stages Using customization tools, you can fit an Acumatica ERP application to your specific business requirements. To make the customization process consistent, controllable, and predictable, we recommend that you divide the customization into the following key stages: Customization Planning The customization planning stage starts with identifying the changes you want to make to the current version of the Acumatica ERP application and defining the requirements of those changes. After analyzing the defined requirements, your customization team should estimate the customization scope. In the process, you will identify the components of the application to be changed, make a detailed list of changes, and split the changes into customization steps. Gap Analysis To define the customization scope, first thoroughly review the Acumatica ERP application and study your business processes to find the gap between existing and new business processes. This information will help you identify changes you want to make to the current version of the application. Before you plan any changes to the application, you should fully understand the logic implemented in the current version of the Acumatica ERP application and review the source code. To view the application code, use Page 9 of 97

10 the Source Code Browser capability, which is included in the Acumatica ERP customization tools. To estimate the customization scope, you need to carefully review your current business processes and identify differences between the changed business requirements and the possibilities that the current application version gives users. To begin your business process review, identify all relevant business processes. For each, identify the following: The user roles that participate in this process. The operations that users perform within this process (in the proper order). The data that users add, view, select, and modify when performing these operations. The workflow rules including conditions, constraints, and necessary data verifications performed when users fulfill these operations. Identifying Changes to the Acumatica ERP Application Next, start planning necessary changes to the current version of the Acumatica ERP application. Split the customization planning into the following steps: Step Identifying Changes in Data Presentation Description To plan changes to the presentation of data, first compare the data involved in the business process and the data provided by the current version of Acumatica ERP application to users. To identify necessary changes to the application, you should answer the following questions: What data do application users need to work with, if any, that the current version of the application doesn t provide? What data, if any, does the current version of the Acumatica ERP application display to users that you don t want the application to display? Identifying Changes in Workflow Rules In this step, you compare the operations performed by the users who participate in the business process and the capabilities provided by the current version of the Acumatica ERP application. To identify the necessary changes to the application, answer the following questions: Does the business process include any operations performed under certain conditions that are not implemented in the Acumatica ERP application? If so, what are these? What data verifications does the business process require that are not performed in the application? What specific data should be verified? Which constraints influence the way the users perform the operations involved in the business process, and the data required to perform these operations? Identifying Changes in User Access Rights Analyze the answers to these questions, which will help you estimate the changes required to add the necessary facilities to the Acumatica ERP application. Depending on your planned changes to the workflow rules, you may need to define access rights to system objects for users who participate in parts of the Page 10 of 97

11 workflows. To identify the necessary changes in the user access rights, you should answer the following questions: What changes to the current user access rights are required? What new Acumatica ERP user roles or user groups, if any, will be required to perform some steps within the changed business processes? You will also need to define appropriate access rights for users involved in customization development and deployment. Planning Changes in Data Presentation If any data required in the business process is not available in the current version of the Acumatica ERP application, you might decide to change the data structure and make the required data available for user entry and viewing on the application forms. Before adding new logic to the application, you might need to again examine the existing code by using the Source Code Browser. Before making changes to the user interface (UI), you should list changes in data presentation for each form of the current application version that requires changes. Estimate and allocate the needed changes in the volume of data available for Acumatica ERP application users. At the moment of writing this guide, Acumatica ERP customization tools do not provide any means for adding new forms to the Acumatica ERP application. If some new forms are necessary, you can develop them within Acumatica Framework and bind them to the product application as an add-on. When planning the changes in data presentation, you need to determine the following: Acumatica ERP forms that need to be modified. UI elements input fields, check boxes, panels, or buttons that need to be added or removed from the forms. Changes in data sets associated with these forms and UI elements. By using Acumatica ERP customization tools, you can change the data structure when you add new UI elements onto a form. Because most form modifications involve adding UI elements onto a form and linking them to new data fields, you can add UI elements to a form more easily. You can easily customize the UI because of the visual customization tools, which facilitate adding new UI elements onto Acumatica ERP forms and linking them to the data source. If you need to remove a UI element from the user s view, you can hide the element on the form. (You cannot completely delete a UI element that was available on a form in the original version of the Acumatica ERP application.) When you re performing a more complex customization and the necessary data is not provided by the data member object associated with the current form, you can add a new UI element onto the form and associate the data member object with it, or add custom code that changes the structure of the data tables associated with the Acumatica ERP application forms. The customizations may include changes to the data management classes and attributes. The facility, named Code Editor, facilitates this type of customization. Page 11 of 97

12 Planning Changes in Workflow Rules In addition to changes made to the Acumatica ERP application data structure and UI elements, you can add custom logic and functions that meet the changed business requirements. These rules should be formalized before you develop new code. To formalize rules, describe the new functions, conditions, data verifications, and constraints that are required in the customized version of the Acumatica ERP application. For best results when you add custom code, map the code to the application forms and check that the added code will not break the current application version or interfere with application features that should not be affected by the customization. For this purpose, you should carefully review the existing code of the Acumatica ERP application by using the Source Code Browser. You can add new events, functions, data verifications, and constraints to the application to implement the new business logic in the customized version. These modifications involve by using the Code Editor included in the Acumatica ERP customization tools. To control the user data input to the UI elements, you can add input masks by changing the properties or attributes of the data field associated with the element. Delegating Customization Role Privileges to Acumatica ERP Users Finally, decide which users will access the Acumatica ERP customization suite tools and perform the customizations. First, divide the customization process into preparing the customization code (as a rule, within a customizer s application instance) and updating the company s production application. (We do not recommend that customization development be performed on a production application.) No constraints are needed when a customization project is being developed in the customizer s own application instance, except for the requirements of not publishing more than one project simultaneously, as well as not publishing the same project simultaneously by more than one customizer. In each customizer s application instance, you can grant customizer privileges to many customizers, but we recommend that you have no more than two customizers per instance. As for customizers who work on a company s production application, one to three users with the Customizer role is usually enough, depending on the customization scope and the company s scale. Consider the following common requirements: You can grant customization privileges to Acumatica ERP application users only by assigning them the built-in Customizer role. The users who will be granted the Customizer role must be authorized Acumatica ERP internal users. You should keep the list of customizers as short as possible to avoid significant system performance degradation. Customization Development During this stage, you will develop the customization, which involves implementing your planned changes by using Acumatica ERP customization tools. Whether on your own or with other members of Page 12 of 97

13 the Customizer role, you will modify the appearance and logic of the Acumatica ERP application to meet the defined requirements. Usually, each customization step involves the customization of one form, and you may have multiple steps per form, depending on the scope of the changes. Development Guidelines For a verifiable, manageable, and predictable customization process, follow these guidelines during the development process: Create the customizer s application instance, which represents a standard installation of Acumatica ERP with the same release that the company s application uses, and consists of the website and the database. All further actions must be performed on this instance. Split every form customization into elementary steps, such as adding a user interface (UI) element or creating a new event. Validate the changes performed after completion of every step. Save the validated changes to an external file before you move on to the next step. Remove the unsuccessful customization, if necessary. You cannot publish more than one project for each application instance used by a customizer. The company s production version of the application, too, cannot have more than one customization project. If you need to further customize the production version of the application after the project has already customized it, you must unpublish the project and make all needed new customization steps part of the same project. Customizing a Form You will use the Acumatica ERP Customization Tools to perform the steps of the customization project. You use these tools to modify the appearance, behavior, and logic of Acumatica ERP application forms. To begin working with these tools, you create a new customization project or open the existing one. The customization of a form is usually split into the following steps: Performing the UI Customization: This step might involve adding or removing the elements, or changing the properties and locations of elements. The visual customization tools automate the processes of adding elements onto the form, changing properties, and removing elements from the form. Performing the Functional Customization: Functional customization entails changing the structure of data fields associated with the form, adding custom events, or modifying the Acumatica ERP application business logic associated with the customized form. To perform functional customizations, you usually add custom code to the application by using the Acumatica ERP Customization Tools tool. Checking the performed customization for errors (validation): To ensure that the changes made to the UI are error free, compile the Acumatica ERP application code, incorporating the changes made to the UI and business logic of the form. Saving the customization project to the database: You save the current project to persist it and make the customization data available for use in the future. You can also download the project customization code to an XML file for instance, to have an archive copy or to upload customization data to another customizer s application instance or to the company s production application. Page 13 of 97

14 Removing any unsuccessful customization code: To remove the code, you can edit the customization code and manually delete the erroneous data. Alternatively, you can upload the code saved in the external file to continue the customization process from a point when the project s customization changes had been verified (validated) and established. Saving and Restoring Customization Data As mentioned, you can preserve changes you made to an Acumatica ERP form during customization by saving the customization project s code. By using Acumatica ERP customization tools, you can remove changes performed in one customization step or multiple steps. You can manage the customization code of the project in any of these ways: Save the code to the database. Select Save Project to Database from the Customization menu, or use the relevant options available in the Acumatica ERP Customization Tools or Code Editor. Download the code to an external file. For details about uploading and downloading, see the Customization Data Editor section of the Acumatica ERP Customization Tools article. Restore the last compiled customization by reloading the customization code of the project from the last successful compilation. You can use this option when the customization performed within a customization step fails code compilation. To restore the last compiled customization, choose Restore Project from Database from the Customization menu. Upload the customization code of the project from the external file saved after the last successful customization step. Customization Deployment During customization deployment, the customizer applies all the changes made to the Acumatica ERP application version by using an application instance: a local instance of the application with a separate database. This instance, including the database structure, must have the same application configuration as the production application where the project customization will be deployed. The customizer s application instance should be a standard installation of Acumatica ERP with the same release. After finishing the customization project, the customizer validates and publishes it in the local application instance to test the results of the project. If the test results are successful, the customizer downloads the project code to an external XML file, uploads the code to the company s production application, and validates and publishes the uploaded project. (The customizer could instead send this file to another specialist who performs this final work.) The customizer begins customization deployment by downloading validated, published, and tested customization code to an external XML file. Within the company s production application, the customizer (or another specialist with the Customizer role) does the following: Uploading the XML-file code to the application Validating and publishing the customization project; updating the current application version Removing the customization project from the company s application, if the published customization was unsuccessful or the current customization project code is to be replaced with another one Validating and Publishing the Project Locally Page 14 of 97

15 You perform the essential validation step in your local application instance to ensure that the customization changes do not conflict with the current application version. During this step, you merge the Acumatica ERP application code with the project customization code, so that the changes made during development will take effect. The system reports any errors that occur during validation. If the customization fails validation, you must troubleshoot the customization or delete it from the database. To validate the changes of the customization project and publish the changes in your application instance, perform the following actions: To start validation, on the Customization menu, select Validate and Publish. The validation results window shows the code compilation results. To view the validation results, browse the opened window. If the customization validation fails, the window displays the list of errors. The screenshot below illustrates an example of error messages. To fix errors, do either of the following: To return to the customization code from the last successful customization, refuse the publication; then upload the appropriate XML file by using the Customization Data Editor. To discard the customization changes, refuse the publication. Then correct or delete the project customization code through the Project Editor, Customization Data Editor, or Code Editor. After successful validation, you can publish the customization project, which adds the customization code to the current version of application instance, yielding a new version with the validated changes. To publish the validated customization project, on the validation results window, click Publish. To ensure that the local application has been customized correctly, you should thoroughly test the application. Page 15 of 97

16 Downloading the Project to an External XML File After you test the finished customization project, you must download the customization code to an external XML file for uploading this code to the company s production application. Use the Customization Data Editor to perform the download and upload actions. Uploading the XML-file Code and Updating the Production Application You can update and use the project customization code in only the same application configuration on which it was developed. Thus, after you have developed and thoroughly tested a customization with your application instance, you can deploy it to the production instance (or to multiple instances) with the same application configuration; for Acumatica ERP, the customizer s instance and the production instance must have the same release number. To deploy the customization, use the external XML file created in the previous step. If the customizer s application instance for Acumatica ERP has another release number than the company s production application to be customized, you should upgrade the application with the earliest release date. You can upgrade any customized application without invoking the Undo Publish procedure, which is performed automatically. If the upgrade finishes successfully, the Validate and Publish procedure starts after the first website opening. Invoke the Undo Publish procedure only if validation fails, which can happen due to incompatibility of the customization and the new Acumatica ERP version code. In this case, you should revise the customization code of the project to eliminate the incompatibility issues. To deploy a successful customization to a production application instance, do the following: Upload the customization file on the target application where you must deploy the customization, by using the Customization Data Editor. Validate and publish the customization to apply the customization (merging the customization code with the main application code) on the target application and make it available for users of the Acumatica ERP application. Removing an Unsuccessful Customization from the Production Application If the published customization was unsuccessful (for example, it doesn t meet user requirements) or you must replace the code of the customization project, you should cancel the publication of the customization. To do this, select Undo Publish on the Customization menu. The customization code is not deleted, but the application does not use it. If necessary, you can then partially or completely remove the unpublished customization code from the production application through the Project Editor window. Working on a Project As a rule, the customizer uses an application instance the local application with a separate database while developing the customization. This instance must have the same configuration, including database structure, as the production application where the project customization will be deployed. Page 16 of 97

17 The customizer s application instance is usually a standard installation of Acumatica ERP with the same release as the production application has; the instance consists of the website and the database. Thus, both the customizer s application instance and the production application to be customized have the same configuration. As described in the Customization Project definition, each project consists of a series of steps. Depending on the application to be customized and the steps involved, customizers can share work in ways that best meet the company s needs. For example, each customizer can work on the same project within the common application instance, while the project includes some steps to gradually customize the application. The customizers would divide among themselves these steps, according to the customization plan. You may not publish more than one customization project in a customizer s application instance; otherwise, problems of code compatibility can take place. If a project is not too complicated, we recommend that you use a separate application instance for each project and a single customizer for each project. As another example, imagine that a project includes customizing the user interface (UI) and form elements, and adding code that changes some application logic. In this case, several customizers may work within the same project. However, we don t recommend that customizers work simultaneously on one customizer s application instance within the same project, to avoid situations when multiple customizers try to publish the same customization or download it for publishing in another application; unpredictable consequences can take place. The whole project must be successfully validated before it is published. Customizing a Form within a Project Because you have been assigned the Customizer role, every time you open a project, the system automatically invokes Page Design mode for all previously changed forms and starts a new customization session. The system automatically updates the customization project after you perform changes. You can easily customize Acumatica ERP applications by using visual tools to change the properties and behavior of UI elements on the selected form. You can create and edit the customization code in either of the following ways: Automatically for UI form elements and their properties by visually adding and managing them, as well as specifying the properties of elements by using Aspx Control Tree. Manually in the Code Editor, Project Editor, or Customization Data Editor window (described in Acumatica ERP Customization Tools). You can access the code of the current customization project in any of these windows. You can simultaneously open multiple forms within the same project in Page Design mode. Each customizer who enters Page Design mode within the same project can view changes made to these forms, which are saved in the body of the customization code of the project. Starting and Finishing a Customization Session To start a new customization session, follow the instructions below: Page 17 of 97

18 1. Create a new project (or select the name of the existing one), open the Acumatica ERP form you want to customize, and enter Page Design mode. (If the project already exists, previously customized forms will be opened in Page Design mode automatically.) 2. Perform all necessary changes. 3. To check the changes for errors, validate each customization step that you performed. 4. If you need to add another form to the current customization project, open the form, enter Page Design mode, and start customization. 5. Repeat instructions 2 4 for the new customized form. 6. Save the customization changes of the validated project. You can also download the updated customization code to an external file. You can later upload data from the downloaded file, either to the current customizer s application instance or to the company s production application (as a distributive unit of sorts). For example, after you create, validate, and test your project on a local copy of the main working application, you can upload the project s changes to the main application. When you re ready to apply the changes performed within a customization session to the application, publish the customization. You may also publish intermediate versions of the project customization code to test changes. After testing, you shouldn t invoke the Undo Publish action to continue with developing the customization project. To finish the customization session, close the project, which closes all the forms opened in Page Design mode. You can handle changes made within the customization session in any of the following ways: Discard the changes, if they were not yet saved to the database manually, by selecting Reload Project from Database on the Customization menu. Changes within the current session are saved automatically when you exit Page Design mode (for the current form) and when you close the project (for all customized forms and for other changes, including functional changes). You can also manually save changes within the current project session by clicking Save to database in the Customization Data Editor window. Remove the changes partially, if they have been already saved to the database, by manually editing the customized forms or customization project. You can remove any changes within the selected project. You can act upon all the changes of the project, including those made in previous customization sessions, as follows: Validate and publish: On the Customization menu, select Validate and Publish. Published without validation: This option is not recommended. Unpublished: Select Undo publish on the Customization menu, and the application will be returned to its initial state. The customization project data will not be removed; it can be corrected and supplemented for further validation and publication. Page 18 of 97

19 Removed from the database: Use the Project Editor to delete from the appropriate customization project saved changes that you no longer deem necessary. UI Customization As your business processes change, you might want to make corresponding changes to the user interface (UI) of Acumatica ERP applications so that users can work more efficiently. With Acumatica ERP customization tools, you can easily perform UI customizations, such as changing the look and behavior of forms, tweaking the design of forms, and expanding the necessary input data range (for instance, by changing data types or digit capacity). By using Acumatica ERP customization tools, you can perform the following UI customization tasks with ease and flexibility: Adding advanced controls (form views, grids, tabs, panels, and buttons) onto forms Adding input UI elements onto forms Customizing the properties of existing UI elements and adjusting the properties of added elements Hiding existing UI elements and removing added elements Adding new forms based on Acumatica Framework templates Classifying UI Objects If you understand how to classify UI objects that must be customized, you can more easily assess the complexity of the customization project and work more efficiently. Bound and Unbound Objects You can classify each UI element added to a form as either bound or unbound. Bound objects are UI objects input fields, check boxes, group boxes, combo boxes, and selectors linked to database fields. When you define bound objects, you must use data types with the DB prefix (for instance, DBString or DBDecimal). All bound UI objects are input UI elements. To connect a bound object to its data source, you add the object onto the form and link the object to an existing data field (or a new data field you create). You can then modify the behavior, appearance, and visibility of the object by changing its properties, which changes the properties of the data field associated with the bound object. Changes made to data field properties affect all the UI elements that are linked to this data field. Unbound objects are UI objects form views, grids, tabs, panels, buttons, field labels, and descriptors that have no connection to the database. As a rule, after you have added an unbound object onto the form, you customize the properties of the object only on the UI level. No other customization is involved, except for adjusting such property values as width, height, font style, background color, and top and left positions of the object s upper left edge. In this guide, unbound UI objects are called advanced controls. Page 19 of 97

20 To use buttons, you should add an event handler that will react on mouse clicks and will perform commands, which are provided by customization code. To use a descriptor for a selector field, you have to add the DescriptionField parameter value to the PXSelector attribute. You can consider as unbound objects non-ui objects, such as events and primary views. You implement these objects into customization code by performing functional customization. Most properties of unbound objects (except for panels) are stored in the code of data access classes (DACs), business logic containers (BLCs), or.aspx pages. (For instance, unbound field label names are stored in DACs or BLCs while unbound field properties are stored in.aspx pages.) Bound UI objects are bound with both database tables and appropriate system objects. For example, after you add a UI field, new code lines with the field (having the same name as in the database table) and its attributes are added to the code of the relevant DAC automatically. Simple and Complex Objects You can also classify UI objects as simple and complex: Simple objects: You do not need to adjust these UI elements (or you might change them slightly, such as for location and size) after you add them onto the form. Simple objects can be bound or unbound. Most input (text, numeric, Boolean, and date) fields, as well as check boxes and group boxes, are simple bound objects, which can use data fields as the data source. Form views, grids, tabs, panels, and group captions (which logically group the UI elements on the form) are simple unbound objects; you can add them and take no further actions. Complex objects: You must adjust these UI elements after you have added them onto the form (whether they are bound or not). Selectors, combo boxes, and descriptors are complex bound objects. You can bind selectors to multiple referenced database tables by adding attribute parameters or BQL expressions to the corresponding DAC code. To use combo boxes, you must add appropriate customization code to the relevant BLC. To use descriptors for the selector fields, you have to add the appropriate parameter values to the code of the corresponding DAC. Adding Input UI Elements Data Field Types A data field type defines how the data associated with the UI element will be stored or retrieved. Depending on the data type requirements, you can create a new field in the database or use an appropriate data field type to link the UI element with a system object data access class (DAC) or business logic container (BLC) that stores the corresponding data as a value. Only data field types with the DB prefix can be used to store data in and retrieve data from the database. In the Field Type box, you can select one of the data field types listed in the following table. Data Field Type Description Page 20 of 97

21 DBInt(Int) DBBool(bit) DBLong(bigint) DBDecimal(decimal) DBDate(datetime) DBGuid(uniqueidentifier) DBDouble(real) DBString(nvarchar) DBString(nchar) String Int Bool Long Decimal Double Date Guid Links an input field to a new or existing database table column with the integer data type. Links an input field to a new or existing database table column with the Boolean data type. Links an input field to a new or existing database table column with the bigint data type that is, an integer containing values from 2 63 through (2 63 1). Links an input field to a new or existing database table column with the decimal data type (fixed precision and scale numbers). When maximum precision is used, valid values range from ( ) through ( ). Links an input field to a new or existing database table column with the datetime data type (a fixed-length string that represents either a specific date and time or an interval). Links an input field to a new or existing database table column with the uniqueidentifier data type (a 32-character hexadecimal string that is stored as a 128-bit integer). Links an input field to a new or existing database table column with the real data type a floating precision number from ( 3.40E + 38) through (3.40E + 38). Links an input field to a new or existing database table column with the nvarchar data type, which means that data in the database fields is stored as variable-length character strings of Unicode characters. You can define the maximum length of the string. Links an input field to a new or existing database table column with the nchar data type, which means that data in the database fields is stored as fixed-length character strings of Unicode characters. You can define the maximum length of the string. Links an input field to a system object storing and retrieving the data as string values. You can define the length of the string. Links an input field to a system object storing and retrieving the data as integer values. Links an input field to a system object storing and retrieving the data as Boolean values. Links an input field to a system object storing and retrieving the data as 32-bit signed integer values. Links an input field to a system object storing and retrieving the data as signed 128-bit (16-byte) values representing 96-bit (12-byte) integer numbers scaled by a variable power of 10. Links an input field to a system object storing and retrieving the data as signed floating precision values from ( 3.40E + 38) through (3.40E + 38). Links an input field to a system object storing and retrieving the data with the datetime data type (a fixed-length string that represents either a specific date and time or an interval). Links an input field to a system object storing and retrieving the data as a 32-character hexadecimal string that is stored as a 128-bit integer. Types of Input UI Elements Page 21 of 97

22 Acumatica ERP users use input UI elements to enter, view, or select data on forms. By using the Acumatica ERP Customization Tools, you can add UI elements onto Acumatica ERP forms and link them to the database fields or system objects that store the entered values. You can also set the visual properties of the UI element. You can add the following types of input UI elements onto forms: TextEdit: The user enters text in an input field. NumberEdit: The user enters a number in an input field. Selector: The user selects a value from a list of elements in the database. Selector with Description: The user selects a value from a list of elements in the database; the UI element description is based on the data selected from a specific database field. ComboBox: The user selects a value from a list of elements composed of a set of options predefined in the business logic or data access class, with the possibility to type data into the editing combo box. CheckBox: The user selects or clears the option. MaskEdit: The user enters values (text or numbers) with the predefined format in the input field. SegmentMask: The user enters values (text or numbers) with the predefined format in the input field; the masking rules, which define the input format, can be set individually for each segment of the input string. LinkEdit: The user enters a webpage URL within the input field; the entered data is verified for the correct URL format. MailEdit: The user enters an address within an input field; the entered data is verified for having the correct address format. GroupBox: This element is used to visually group a set of buttons. DateTimeEdit: The user selects the date by using a visual tool. ImageUploader: The user can upload an image file to the selected area of a form. Adding an Input UI Element onto a Form To add an input UI element onto a form, you create a new element and then link it to the relevant table field in the database or to a system object. By using Acumatica ERP customization tools, you can link new input UI elements to the relevant sources of data either by linking a new UI element to the existing data field, or by creating a new data field (illustrated in this section). To add any UI element onto a form, perform the following instructions: 1. In Page Design mode, right-click the area where you need to add the element, and select Add Input Control, as shown below. Page 22 of 97

23 2. In the Create control window, click Add. (To use an existing data field, you should instead open the lookup window by clicking the Magnifier icon of the Data field box and selecting the required data field name. Select the needed ControlType value, and click Save. ) 3. In the Create data field window that appears, define the following values (see the screenshot below): Field Name, Display Name, Field Type, and Length &Precision (which appears if you select a field type that requires entering these values, such as String, DB String, Decimal, and DBDecimal). If you select the DBString rather than the String type, for instance, the UI element will be bound to the database (and thus is a bound object). Otherwise, the system will extend the appropriate data access class (DAC) with this UI element, but the element will not be bound to the database (and is an unbound object). The Mapped to database check box (also shown in the second screenshot) is automatically selected or cleared, depending on whether the data field type has the DB prefix. Page 23 of 97

24 4. Click OK to again view the Create control window. Select the required ControlType (that is, the type of UI element you want to add), as shown in the screenshot below. Notice that the new added data field has been renamed, with the Usr prefix automatically added to the name previously defined as a field name. 5. Click OK. Once the form is reloaded, the new UI element and its label will be added onto the form. 6. Right-click the added UI element and select Control Tree. This brings up the Aspx Control Tree window, so that you can adjust the added UI element and its label positions. Then you can drag the element and its label to the needed place. Customizing Properties You can set properties for new user interface (UI) elements and modify the properties of existing elements. Depending on the end result you want and the objects affected by the property changes, you define UI elements to customize. Based on the type of the UI element, the system displays the applicable property types in the Aspx Control Tree window, which you open after right-clicking the appropriate UI element or any area of the form (see the screenshot below). Page 24 of 97

25 Some of the main property types are: The PXEdit type (for instance, PXTextEdit, PXNumberEdit, and PXDateTimeEdit) includes visual properties of the UI element. By adjusting these properties, you can change the visibility of the UI element on the form and the user s ability to enter a value in it. You can also control the alignment of UI elements and set the tab index to manage the order in which elements gain focus as the user presses Tab or Enter. The PXSelector type includes properties analogous to those of the PXEdit type, as well as properties used after the lookup window is opened (see the screenshot below). Page 25 of 97

26 The PXSegmentMask type includes properties analogous to those of the PXSelector type (see the three screenshots below). This type is used along with the PXMaskEdit type (see the screenshot below). By adjusting properties of the PXMaskEdit type, for example, you can define or change the complex input mask for the account field. As a rule, customization values are manually added to the Customized value column of the Aspx Control Tree window, as shown in the screenshot above. Page 26 of 97

27 Notice that you can adjust property values after you select the appropriate node of the UI element. To see all type properties, select All Props on the drop-down list located above the type property table. By using the Aspx Source window (see the screenshot below), you can see the current property values (either the existing values, displayed in gray, or the customized ones, displayed in red). To open this window for the selected UI element, click Aspx in the upper area of the Aspx Control Tree window. By using the Acumatica ERP Customization Tools, you can manually change the.aspx code of the form The PXDropDown type includes properties analogous to some of the PXSelector and PXSegmentMask types. This type, as a rule, is used for combo boxes. Page 27 of 97

28 The PXCheckBox type includes properties of Boolean UI elements. This type is generally used for check boxes. The PXGroupBox type includes properties analogous to those of the PXCheckBox type (see the screenshot below). You use the PXGroupBox type along with the PXRadioButton type, which you can access from the corresponding subnode of the PXGroupBox node, if you have expanded the subnode in the navigation tree (see the screenshot below). By adjusting properties of the PXMaskEdit type, you can define or change the name and default value of each radio button 1 if it is selected, or 0 if it is not. The AutoCallBack type is a separate group of properties: Unlike all the aforementioned types, this type is auxiliary, and the properties can be adjusted along with such types as PXTextEdit, Page 28 of 97

29 PXNumberEdit, PXSelector, and PXDropDown. The AutoCallBack type includes the callback properties of the UI element. By adjusting these properties, you can determine how the system reacts to data input by the user. For example, the value entered into the specified field can change values of other fields (which usually have bigger tab index values than the edited UI element has). These values are added automatically. The following tables summarize the main UI element properties you can adjust. (Properties of a few auxiliary property types, such as the Style and GridProperties types, as well as those of basic types whose usage and adjustment rules are obvious, are not listed here.) Property Visible Enabled Required TabIndex MaxLength Description Displays (if set to True) or hides (if set to False) the selected UI element from the form. You can also adjust this value in the relevant DAC, if you add this property and its value for the PXUIField attribute. Enables or disables the user s ability to select and edit the UI element. When the property is set to True, users can select and edit the element; setting this property value to False disables the element for users. You can also adjust this value in the relevant DAC, if you add this property and its value for the PXUIField attribute. Enables or disables the user s ability to skip data entry to the UI element. When the property value is set to True, users cannot skip data entry to the element; if it is set to False, users do not need to enter data for the UI element. You can also adjust this value in the relevant DAC, if you add this property and its value for the PXUIField attribute. Determines the precedence of the UI element in the order in which the user moves among form elements by pressing the Tab or Enter key. To keep the UI element from accepting keyboard focus, set this property to -1. Determines the maximum number of characters the edit box can accept when the user enters data. Setting this property affects only this UI element on the form. You can also adjust this value in the relevant DAC, if you add this property and its value for the PXDBString attribute. The following properties are included in the PXSegmentMask and PXSelector property types. Property ValueField TextField HintField AutoRefresh Description Defines the name of the field in the data source, which contains the data to be saved in the database when the user selects a value. The value saved to the database when the user selects a value may be different from the data that is displayed to the user on the screen. This property, along with the TextField property, defines the names of the data source fields used to display data in the list in the lookup window and saves the new value in the database. Along with the ValueField property, defines the names of the data source fields used to display data in the lookup window and saves the new value in the database. Provides the hint about the data displayed to the user in the list box; this property is usually used along with the ValueField and TextField properties. Indicates that the list of fields in the lookup window should not be cached in the browser but should instead be refreshed from the server each time. Page 29 of 97

30 AutoGenerateColumns AutoAdjustColumns AllowEdit AllowAddNew Indicates whether bound fields are automatically created for each field in the data source. If the value is True, bound fields are created, and if the value is False, bound fields are not created. Enables (if set to True) or disables (if set to False) automatic column width adjustment in the grids. Gives the user the ability to edit the referenced page by using a new window, if the property is set to True for the UI element. If it is set to True for the UI element, gives the user the ability to edit the referenced page by using a new window, after the user clicks the icon within the lookup window. The following properties are included in the PXMaskEdit property type. Property InputMask MaxLength Description Holds the string expression that governs the format of the data that may be entered into the edit box of the UI element. Limits the number of characters for the input UI element. If multiple UI elements on form are linked to a single data field, changes to this data field property will affect all these controls. The main properties included in the AutoCallBack property type are described in the following table. Property Enabled Target Command Description Enables or disables the AutoCallBack option. If this property is set to True, a change within the edit box of the UI element initializes sending the contents from the form to the server and waiting for the refreshing response data from the server. This property is used along with the Target and Command parameters. Specifies the target of performing the command of the AutoCallBack property. The added property value depends on the required result and on where the adjusting UI element is on the form, tab, or grid. This property can be set to ds (default data source), form, tab, or grid. An external data source can be also used as a target. Defines, along with the Target value, the behavior of the appropriate container control. This property can have various predefined values; the main values are Save, Cancel, and Refresh. When a form field is specified as the callback target, for instance, the system posts container data to the server and requests command execution. When it is requested for the container control, the Save action updates the DAC associated with the container control with changed values. Functional Customization When you need to add an event handler, generate a data access class, or change code fragments for the application business logic, you are planning to perform a functional customization. As a rule, before you begin to add customization code lines, you need to look through the relevant fragments of the existing application code (source code). For complicated changes, you should review the source code to get information, such as SQL expressions and names of classes and fields, you need to optimally perform the customization task. Page 30 of 97

31 Adding a Data Event Handler As a rule, the process of adding a data event handler includes the following steps: Analyzing the source code (that is, the existing application code lines that relate to the customization task) Creating the code template of the event handler Implementing event logic In simple cases, when you need no additional information from the source code to implement an event handler, you can skip the first step. Analyzing the Source Code Analyzing the source code might help you get optimal results if, for example, you don t know which data access class (DAC) supports the form with the event handler you want to add, what kind of data is represented by code lines of the views used in the appropriate business logic container (BLC) file, or what field names are bound in the specified SQL expressions included in the views of the form. The Event Model used in Acumatica ERP represents the set of available event handlers, which can be split into three groups: field handlers (FieldDefaulting, FieldUpdating, FieldVerifying, and so on), row handlers (such as RowInserting, RowInserted, and RowUpdating), and special handlers (CommandPreparing, ExceptionHandling, and CacheAttached). Depending on the kind of handler you plan to implement, you could analyze the appropriate source code fragments to find the relationships among fields and rows, or to understand, for example, how to create the required exception code or how to override properties of an attribute by adding business logic code lines. Depending on the customization objectives, you can use either or both of the following customization facilities: The DataField Attributes window (see the screenshot below) Page 31 of 97

32 The Source Code Browser (see the screenshot below) By using the DataField Attributes window, you can get the primary view name of the form that is used in the appropriate BLC, as well as name of the DAC that contains the selected field name as an attribute. The original names of one or more fields may also be needed if, for instance, the customization must include a handler to verify a field value or calculate the difference between field values and then validate and constrain it (for instance, to prevent employment of a person younger than 16 years). To open this window, right-click each required field (if a row handler is to be added and the form contains more than one underlying DACs) or the field that must be verified by using a field handler, and select Attributes. In the upper area of this window, note the View Name (the primary view is displayed after the colon), Cache Type (symbols to the right of the rightmost period represent the DAC name), and Field Name values. The lines defining the original field attributes, which are shown in the middle of the window, can be also useful for developing the customization code. By using the Source Code Browser, you can get information needed to correctly implement the event handler code. You can open a separate window with the Source Code Browser by navigating to the form to be customized and selecting View Source Code on the Customization menu. On the Find in Files tab, you can search for required objects or fields by using their names (if you noted them while analyzing the DataField Attributes window), or by using any function or attribute names (if you had not opened the DataField Attributes window). The found items are displayed with the appropriate code fragments; each item also contains the name of the found object and the code line number, as the screenshot below illustrates. You can thus review key code fragments before you begin to create the event handler. Page 32 of 97

33 Creating the Event Handler Code Template The code template of the event handler represents the initial basic code, which includes namespace declarations and a declaration of the event handler to be added, as shown in the first screenshot below. To create a template, perform the following actions: 1. Navigate to the form to be customized, open the customization project (or create it, if it doesn t exist), and enter Page Design mode. 2. Right-click the appropriate area of the form and select Add Data Event, as shown in the first screenshot below. Page 33 of 97

34 Page 34 of 97

35 3. In the Add Event Handler dialog that appears, select the event type from the drop-down list, keep the Data table name value, and click OK, as shown in the second screenshot above. The Code Editor appears in a separate window with the code template. Implementing Event Logic Now you should develop the required event logic code and add it to the code template. Proceed as follows: 1. In the Code Editor window, add the code lines of the event handler to the BLC, by using information you obtained during the analysis step (see the screenshot below). 2. Click Save to store the customization code in the database. 3. Click Validate and Publish. (You can click this button anytime after you save the project code.) 4. If the validation has finished successfully, click Publish, which appears under the BLC code lines. 5. Perform a comprehensive set of tests to ensure that the event handler has been implemented correctly. Other Methods of Functional Customization In addition to performing functional customization to add an event handler, you can develop advanced customization code to satisfy different requirements. These requirements can range from implementing complicated logic and through creating a new form and providing fields on it whose values are calculated using new algorithms. (The second case represents combination of UI and functional customization.) Page 35 of 97

36 Moving and arranging fields The Acumatica Customization Engine let you customize the user interface (UI) directly from your web browser. You can move columns within grid controls, add new input UI elements onto form and tab controls, add columns to grid controls, and move a UI element within a layout by dragging it to the location that you want. The layout control has following properties: Property Description ColumnSpan Allows to specify number of columns the targeted control will span ColumnWidth Specifies the width of the stack columns. Following values are valid: XXS, XS, S, M, XM, L, XL, XXL (Extra/Small/Medium/Large) ControlSize Specifies the default controls size. Following values are valid: XXS, XS, SM, S, M, XM, L, XL, XXL (Extra/Small/Medium/Large) LabelsWidth Determines the width of the inner control labels. Following values are valid: XXS, XS, S, M, XM, L, XL, XXL (Extra/Small/Medium/Large) StartGroup Logical value that specifies the start of a new group EndGroup Logical value that specifies the end of the group. GroupCaption String value that specifies the caption of the controls group. StartColumn Logical value that specifies the start of the new column StartRow Logical value that specifies the start of the new row Merge Logical value that specifies if the control should be displayed in same row with the previous control. SuppressLabel Logical value that specifies if controls should render labels Using the Acumatica Relative Positioning Layout Control This section explains how to position a set of input UI elements by using the PXLayoutRule control onto a form or tab. The following example shows the main techniques for using the PXLayoutRule to create input controls layout. Before you start the layout adjustments,complete the following steps: 1. Start the Acumatica ERP application. 2. Navigate to Distribution > Inventory > Work Area > Manage > Stock Items. Create a new customization project called RelativePositioningDemo. 3. Create new tab item and add bunch of un-bound controls as shown: Page 36 of 97

37 4. While in design mode on the Stock Items webpage, right-click the Relative Positioning Layout tab, and then click Control Tree. 1. On the control tree in the left pane, expand the Relative Positioning Layout node and select the UsrDefaultShipFee subnode. 2. On the Add menu, click Add Layout Rule. 3. Select the added node, Rulexx, where xx is the order number of the rule record; the filter box above the table (far right) must display the Base Props default value. Set the customized value of the StartRow property to True, as shown in the screenshot below; this property creates an independent set of UI elements. 5. Repeat adding layout rule for each of the following nodes of the control tree: UsrExtraShipFee UsrActive UsrSprTitle Page 37 of 97

38 6. Click Apply to Page. 7. On the Customization menu, click Save Project to Database. Page 38 of 97

39 The figure above illustrates the results of the performed instructions. Placing Input UI Elements in Multiple Columns To uniformly distribute UI elements on the webpage, you can separate some elements into separate columns. To do this, proceed as follows: 1. Open the Stock Items webpage in page design mode within the, right-click the Relative Positioning Layout tab, and then click Control Tree. 2. On the Aspx Control Tree window that appears, add a column by performing the following actions: 1. On the control tree, expand the Relative Positioning Layout node and select the LastStdCost subnode. 2. Click the Down button until the LastStdCost subnode is moved directly under the Page 39 of 97

40 UsrSearchWords subnode. 3. On the Add menu, click Add Layout Rule. Select the added node, Rulexx, where xx is the order number of the rule record; the filter box above the table (far right) must display the Base Props default value. Set the customized value of the StartColumn property to True, as shown in the screenshot below. 3. Click Apply to Page. 4. On the Customization menu, click Save Project to Database. 5. Validate and publish the project, and then close it. 6. Open the Stock Items webpage to ensure that the new column with the Last Cost UI element has been created, as the screenshot below illustrates. Widening Input UI Elements to Span Multiple Columns Page 40 of 97

41 To make a UI element wider, you can either adjust its width property value or adjust it to span multiple columns. To adjust two UI elements to span multiple columns, proceed as follows: 1. Open the Stock Items webpage in page design mode within the, right-click the Relative Positioning Layout tab, and then click Control Tree. 2. On the Aspx Control Tree window that appears, perform the following actions: 1. On the control tree, expand the Relative Positioning Layout node and select the UsrDescrLong subnode. 2. On the Add menu, click Add Layout Rule. 3. Select the added node, Rulexx, where xx is the order number of the rule record; the filter box above the table (far right) must display the Base Props default value. Set the customized value of the ColumnSpan property to Repeat same steps for the UsrSearchWords subnode, as shown in the following screenshot. 5. Click Apply to Page. Notice that the Description (long) and Search Keywords text fields became wider and are now spread across the width of two columns, as the screenshot below illustrates. Setting the Label Width of an Input UI Element Page 41 of 97

42 To adjust the label width of a UI element, proceed as follows: 1. Open the Stock Items webpage in page design mode within the, right-click the Relative Positioning Layout tab, and then click Control Tree. 2. On the Aspx Control Tree window that appears, perform the following actions: 1. On the control tree, expand the Relative Positioning Layout node and select the LastStdCost subnode. 2. Change the filter box above the table (far right) to the All Props value through the dropdown list. 3. Set the customized value of the LabelWidth property to 75px, as shown in the screenshot below. 3. Click Apply to Page. Notice that the Last Cost label is displayed without being shortened, as the screenshot below illustrates. 4. On the Customization menu, click Save Project to Database. Aligning UI Elements Horizontally Page 42 of 97

43 You can align UI elements horizontally so that UI elements placed under a selected one become arranged in the same row as it. Proceed as follows: 1. Open the Stock Items webpage in page design mode within the, right-click the Relative Positioning Layout tab, and then click Control Tree. 2. On the Aspx Control Tree window that appears, perform the following actions: 1. On the control tree, expand the Relative Positioning Layout node and select the UsrExtraShipFee subnode. 2. On the Add menu, click Add Layout Rule. 3. Select the added node, Rulexx, where xx is the order number of the rule record; the filter box above the table (far right) must display the Base Props default value. Set the customized value of the Merge property to True. Setting Merge to True specifies that UI elements contained within the target PXLayoutRule object and any subsequent PXLayoutRule object are arranged horizontally. 4. Repeat instructions 2.1 through 2.3 for the UsrDefaultPostalCode subnode, as shown in the following screenshot. Page 43 of 97

44 5. Click Apply to Page. Notice that the Extra Ship Fee field and Use On Entry check box have become aligned horizontally, as have the Default Postal Code field and View on Map button, as the screenshot below illustrates. 3. On the Customization menu, click Save Project to Database. Creating a Group of UI Elements You can group UI elements to make the user's work more convenient and to minimize possible data entry errors. To create a group that holds two UI elements, perform the following actions: 1. Open the Stock Items webpage in page design mode within the, right-click the Relative Positioning Layout tab, and then click Control Tree. 2. On the Aspx Control Tree window that appears, perform the following actions: 1. On the control tree, expand the Relative Positioning Layout node and select the first PXLayoutRule subnode above the UsrActive subnode. 2. For the selected Rulexxnode, make sure the filter box above the table (far right) displays the Base Props default value; type Status as the customized value of the GroupCaption property. By setting the value of GroupCaption, you create a group of UI elements and define its name. A PXLayoutRule object with the EndGroup property value set to True should be placed below the last UI element of the group. 3. Select the UsrFeatured subnode, and then on the Addmenu, click Add Layout Rule. 4. For the added node, Rulexx (for which the filter box above the table must display the Base Props default value), which became selected, set the customized value of the EndGroup property to True. Page 44 of 97

45 5. Click Down once so that the Rulexx subnode is moved below the UsrFeatured subnode, as shown in the screenshot below. 6. Click Apply to Page. Notice that the Status group with two check boxes has appeared, as the following screenshot illustrates. 3. On the Customization menu, click Save Project to Database. Hiding the Labels of Input UI Elements Each input UI element has a label that is displayed left of the element. Because check boxes include no labels, they are by default left-aligned with the appropriate column's UI elements. If you need to hide the labels of input controls or align check boxes at the leftmost position, you should use the SuppressLabel property of the PXLayoutRule object. Proceed as follows: 1. Open the Stock Items webpage in page design mode within the, right-click the Relative Positioning Layout tab, and then click Control Tree. Page 45 of 97

46 2. On the Aspx Control Tree window that appears, perform the following actions: 1. On the control tree, expand the Relative Positioning Layout node and select the first Rulexx subnode above the UsrActive subnode. 2. Change the filter box above the table (far right) to the Base Props value through the drop-down list, if the value differs from this. 3. Set the customized value of the SuppressLabel property to True, as shown in the screenshot below. 4. Click Apply to Page. Notice that the Active and Featured check boxes are now left-aligned with the labels of the first column's UI elements, as shown in the screenshot below. The Featured check box has been aligned too, because it is included in the same Status group that holds the Active check box. Page 46 of 97

47 3. On the Customization menu, click Save Project to Database. Creating Nested Input Controls PXPanel is a nested input control that is used as a simple placeholder for UI elements. This section describes how to create the PXPanel control and then add simple UI elements onto it. Proceed as follows: 1. Open the Stock Items webpage in page design mode within the, right-click the Relative Positioning Layout tab, select Advanced Controls, and then click Panel. 2. Right-click the new added PXPanel control and click Add Input Control. 3. On the Create control dialog box that appears,select PendingBasePrice as the Data field name, keep the automatically entered ControlType value, and click OK. 4. Repeat Instructions 2 and 3 to create and add onto the panel each of the following UI elements (see the screenshot below): PendingStdCost UsrUseOnEntryPndPrice UsrUseOnEntryPndCost Page 47 of 97

48 5. Again right-click the PXPanel control and click Control Tree. 6. On the Aspx Control Tree window that appears, perform the following actions: 1. Set the filter box above the table to Ext Props and then clear the Customized check box for the height property, and set the RenderStyle property to Simple, as the screenshot below illustrates. 2. Expand the PXPanel virtual container node and select the PendingBasePrice subnode. On the Add menu, click Add Layout Rule. 3. On the control tree, set the filter box above the table to Base Props, and then set the StartRow property to True. 4. By using the Up and Down buttons, put subnodes within the PXPanel node in the following order: PendingBasePrice PendingStdCost UsrUseOnEntryPndPrice UsrUseOnEntryPndCost Page 48 of 97

49 5. Select the UsrUseOnEntryPndPrice subnode. On the Add menu, click Add Layout Rule, and then set the StartColumn and SupressLabel properties to True. 6. Select the PXPanel node and click Up several times so that this node is placed under the Status group of UI elements. 7. On the Add menu, click Add Layout Rule. 8. Select the new added node, Rulexx (for which the filter box above the table must display the Base Props default value); set the StartColumn property value to True and type Pending Values as the GroupCaption value, as shown in the screenshot below. 9. Select the UsrSprTitle node. Then on the Add menu, click Add Layout Rule. 10. Set the EndGroup property to True. 11. Click Up several times so that the last added layout rule is placed under the PXPanel group of UI elements. 7. Click Apply to Page. Notice the PXPanel control with the Pending Values group name and four UI elements. (See the screenshot below.) Page 49 of 97

50 8. On the Customization menu, click Save Project to Database. Setting the Width Value for Multiple UI Elements You can set the common width value for multiple UI elements placed one under another. This example illustrates setting a common width for two check boxes from the Status group. To set the common width value, proceed as follows: 1. Open the Stock Items webpage in page design mode within the, right-click the Relative Positioning Layout tab, and then click Control Tree. 2. On the Aspx Control Tree window that appears, perform the following actions: 1. On the control tree, expand the Relative Positioning Layout node and select the first Rulexx subnode above the UsrActive subnode. 2. Change the filter box above the table (far right) to the Base Props value through the drop-down list, if the value differs from this. 3. Set the ColumnWidth property value to XS, as shown in the screenshot below. Page 50 of 97

51 3. Click Apply to Page. Notice the increased common column width (within the yellow borders) of the check boxes from the Status group (as shown in the screenshot below). 4. On the Customization menu, click Save Project to Database. Setting the Label Width Value for Multiple UI Elements You can set a common label width value for multiple UI elements placed one under another. This example illustrates setting the common label width for fields from the Pending Values group within the PXPanel control. To set a common label width value, proceed as follows: 1. Open the Stock Items webpage in page design mode within the, right-click the Relative Positioning Layout tab, and then click Control Tree. 2. On the Aspx Control Tree window that appears, perform the following actions: 1. On the control tree, expand the Relative Positioning Layout node, expand the PXPanel subnode, and select the Rulexx subnode above the endingbaseprice subnode. 2. Change the filter box above the table (far right) to the Base Props value through the drop-down list, if the value differs from this. 3. Type S as the LabelsWidth property value. 3. Click Apply to Page. Notice the label width of fields from the Pending Values group within the PXPanel control. 4. On the Customization menu, click Save Project to Database. By setting the LabelsWidth property value, you specify that input UI elements contained within the target PXLayoutRule object and any subsequent PXLayoutRule object are displayed with a strictly defined label width. Page 51 of 97

52 To override the width of an input control label, you should use the LabelWidth property of the appropriate UI element. Setting the Width of a UI Element You can set the width value for each UI element. This example illustrates the separate setting the width for a few elements. Proceed as follows: 1. Open the Stock Items webpage in page design mode within the, right-click the Relative Positioning Layout tab, and then click Control Tree. 2. On the Aspx Control Tree window that appears, perform the following actions: 1. On the control tree, expand the Relative Positioning Layout node and select the first Rulexx subnode above the UsrSprTitle subnode. 2. Change the filter box above the table (far right) to the Base Props value through the drop-down list, if the value differs from this. 3. Set the Merge property value to True, type Supervisor as the GroupCaption property, and type S as the LabelsWidth property. 4. Select the UsrSprLastName subnode; then on the Add menu, click Add Layout Rule. 5. Select the UsrSprTitle subnode. 6. Set the filter box above the table to Ext Props, type 84px as the width property value, set the SupressLabel property value to True, and type Empty as the Size property value. 7. Select the UsrSprFirstName subnode. 8. Type 300px as the width property value, and type Empty as the Size property value, as shown in the screenshot below. 9. Select the UsrSprLastName subnode. On the Add menu, click Add Layout Rule. 10. Change the filter box above the table to the Base Props value through the dropdown list and set the EndGroup property to True. Page 52 of 97

53 11. Click Down to move the last added PXLayoutRule subnode under the UsrSprLastName subnode. 3. Click Apply to Page. Notice the widths of the check boxes from the Status group (see the screenshot below). 4. On the Customization menu, click Save Project to Database. Explore the result of the performed actions, as shown in the screenshot below. Setting the Size for Multiple UI Elements You can set the common size value for multiple UI elements placed one under another. This example illustrates setting the common size of a few fields. Proceed as follows: 1. Open the Stock Items webpage in page design mode within the, right-click the Relative Positioning Layout tab, and then click Control Tree. 2. On the Aspx Control Tree window that appears, perform the following actions: 1. On the control tree, expand the Relative Positioning Layout node and select the Rulexx subnode above the UsrSprTitle subnode. 2. Change the filter box above the table to the Base Props value through the dropdown list, if the value differs from this. 3. Type XXL as the ControlSize property value. 3. Click Apply to Page. Notice the label width of fields from the Pending Values group within the PXPanel control. 4. On the Customization menu, click Save Project to Database. Check the result of the performed actions. Page 53 of 97

54 By setting the LabelsWidth property value, you specify that the input UI elements contained within the target PXLayoutRule object and any subsequent PXLayoutRule object are displayed with a strictly defined label width. To override the width of an input control label, you should use the LabelWidth property of the appropriate UI element. Page 54 of 97

55 Examples of Customization Adding a TextEdit Input Field onto a Form In this example, you will add a TextEdit input field to the upper area of the Journal Transactions (GL ) form. This field, which will contain a user-definable description, must be linked to a new database field of the String type. To add the input field, do the following: 1. Create a new project (see a project s definition in Customization Project). The screenshot below illustrates the consecutive actions you need to take: o o o o Navigate to Finance > General Ledger > Enter to select the Journal Transactions form, click the Customization menu button (see the item above the red 1 in the screenshot below),and select Open Customization Project. In the Select Working Project window that appears, click New to add the new project (item 2). In the New Project window that appears, add the project name for instance, GL1 (item 3). Click OK to close the New Project window (item 4); click OK again to close the Select Working Project window (item 5) and create the new project. If your customization application instance includes a published project already, we recommend that you select the Unpublish Existing Customization check box, which appears in the New Project window in this case, to automatically start the Undo Publish procedure before creating the new project. 2. On the Customization menu, select Enter Page Design Mode. Now you can begin the customization of the form. 3. In the Batch Summary area, right-click near the place where the new field should be located, and select Add Input Control. Page 55 of 97

56 4. In the Create control window that appears, click Add to add a new data field (see item 8 in the screenshot below). 5. In the Create data field window that appears, enter the following values (item 9): o Field Name: Note o Display Name: Short Note o Field Type: DBString(nvarchar) o Length: 30 For the type, make sure that you select DBString, not String. The DB prefix indicates that it will be bound to the database. Otherwise, the system will only extend the DAC with a field, but the added field will not be bound to the database. 6. Click OK (item 10). You will again be viewing the Create control window. Accept the suggested Control Type, TextEdit, and click OK (see item 11 on the screenshot below). Once the form is reloaded, the new text edit field and its label will be added onto the form. Page 56 of 97

57 The label of the field added onto the form becomes visible after publishing the project. You can drag and drop the field to change its placement, but you should do this with accuracy so that not to replace the existing fields; moreover, if necessary, you can move or replace any field, as well as change its size by dragging the left side of the selected field. During a UI customization, the automatic alignment is supported by the system the left side of an added or moved field and its label is aligning to the nearest field column of the upper area of the form (if enough free space exists within this column). If you want to restore the original view of the form before you close the project, that is, if you decided to reject the results or part of unsaved results of adding UI text field, you should click Reload Project from Database item on the Customization menu. 7. On the Customization menu, select Validate and Publish. The Compilation window appears, and the application validation process begins immediately. 8. When the validation process has been completed successfully, click Publish within the validation window (see item 18 in the screenshot below); otherwise, view the build output and eliminate the cause of the problem. Page 57 of 97

58 9. Once the Journal Transactions form is reloaded after publishing, close the project and refresh the page. The new text field, Short Note, appears on the form and can be used. Page 58 of 97

59 Adding Selector Fields onto a Form You will add three selector fields onto the Journal Transactions (GL ) form. You will link the selector fields to new data fields related to the system database fields, within one common project. The selectors will use the data access classes (DACs) to manipulate the data and access the system database. You will define the DACs that are used by the selector fields by setting the appropriate attributes for the fields. Adding the Account Class Selector Field In this example, you will add the Account Class selector field onto the Journal Transactions (GL ) form. You will create a new data field to store and display the selected data. The AccountClassID key will be used to access the data in the relevant system database table. To add the Account Class selector field onto the form, you will perform two general steps: adding the user interface (UI) element onto the form, and setting the field attributes. After that, you will use the descr DAC attribute (the descr field exists in the appropriate database table) to set the HintField property of the added selector field. Finally, you will validate the customization changes and save them to an external file as an archive copy in case the next customization step fails, and then publish the project. Adding the UI Element onto the Form Navigate to Finance > General Ledger > Enter to select the Journal Transactions form and create a new project called GL2. add the UI element of the Account Class selector field onto the form as follows: 1. On the Customization menu, select Enter Page Design Mode. Now you can begin the customization of the form. 2. In the Batch Summary area, right-click near the place where the new field should be located, and select Add Input Control. 3. In the Create control window that appears, click Add to add a new data field. 4. In the Create data field window that appears (see the screenshot below), enter the following values: o o o Field Name: AccountClass Display Name: Account Class Field Type: DBString(nvarchar) For the type, make sure that you select DBString rather than String. The DB prefix indicates that it will be bound to the database. If you don t use the prefix, the system will extend the DAC with a field, but the added selector field will not be bound to the database. Page 59 of 97

60 5. Click OK to again view the Create control window. Define the ControlType value as Selector, and click OK. Once the form is reloaded, the new selector field (without its label at the moment) will be added onto the form. The label of the field added onto the form becomes visible after publishing the project. You can drag and drop the field to change its placement, but you should do this with accuracy so that not to replace the existing fields; moreover, if necessary, you can move or replace any field, as well as change its size by dragging the right side of the selected field. To move a field, click and hold its left side and drag. During a UI customization, the automatic alignment is supported by the system the left side of an added or moved field and its label is aligning to the nearest field column of the upper area of the form (if enough free space exists within this column). If you want to restore the original view of the form before you close the project, that is, if you decided to reject the results or part of unsaved results of adding UI text field, you must click Reload Project from Database on the Customization menu. Setting the Field Attributes and Validating the Project To set the attributes of the selector, perform the following actions: 1. Right-click the added Account Class selector field, and select Attributes. 2. Edit the original expression to include the attributes of the selector field, as the screenshot below shows) by setting the PXSelector, DescriptionField, and Substitute Key attributes. Then click OK to save the changes and close the DataField Attributes window. The code lines below illustrate the final code of the DAC field with the selector field property. Page 60 of 97

61 [PXDBString(10, IsKey=false, BqlTable=typeof(PX.Objects.GL.Batch), IsFixed=false, IsUnicode=true)] [PXUIField(DisplayName="Account Class")] [PXSelector(typeof(PX.Objects.GL.AccountClass.accountClassID), DescriptionField=typeof(PX.Objects.GL.AccountClass.descr), SubstituteKey=typeof(PX.Objects.GL.AccountClass.descr) )] If you add code lines for this field for the first time, keep the How to Apply parameter value as Append to Original, otherwise you should select Replace Original. (See the screenshot above) 3. On the Customization menu, select Validate and Publish. In the Compilation window that appears, the validation process begins immediately. 4. When the validation process has completed successfully, the Publish action button appears within the validation window (see the screenshot below), but it is soon to publish the project changes. Close the Compilation window. 5. On the Customization menu, select Save Project to Database (GL2) to save intermediate customization changes to the database. Saving the Current State and Publishing the Project Page 61 of 97

62 To make it possible for you to return to this customization step if the next step fails, you will save the current customization data to an external file. Open the Customization Data Editor and save this data as follows: 1. On the Customization menu, select View Customization Manager to open the Customization Projects form. 2. Click the Edit XML button in upper part of the form, on the main toolbar. 3. In the Customization Data Editor that appears within the new browser window, click Download Package, select Save File, and click OK, as shown in the screenshot below, to save the current state of the customization project to the external file. 4. Close the Customization Data Editor window. 5. On the Customization menu, again select Validate and Publish. In the Compilation window that appears, the validation process begins. 6. When the validation process has completed successfully, click the Publish action button to publish the project. 7. After the project has been published, select Close Project on the Customization menu. Notice the new Account Class selector field on the form; click the Magnifier icon at the right end of this field to open the lookup window with the account classes items with descriptions. (See the screenshot below.) Page 62 of 97

63 Adding the Business Account Selector Field In this example, you will add the Business Account selector field, which will display information about the business account, to the Journal Transactions (GL ) form. In the process, you will create a new data field to store and display the selected data. The baccountid key will be used to access data in the relevant system database table. To add the Business Account selector field, you will perform two general steps: adding the user interface (UI) element onto the form, and setting the attributes of the selector. Finally, you will validate the customization changes and download them to an external file, in the case the next customization step fails, and then publish the project. Adding the UI Element onto the Form Navigate to Finance > General Ledger > Enter to select the Journal Transactions form, if this form is not active at the moment. To add the UI element of the Business Account selector field onto the form, do the following: 1. On the Customization menu, select Open Customization Project to open the existing project, GL2, if it had been closed. Since this project has the UI customization code (see the previous example), the Page Design Mode activates with the Journal Transactions form automatically. 2. On the Journal Transactions form, click the Batch Summary (upper) area to select it, rightclick near the place where you want to place the new field, and select Add Input Control. 3. In the Create control window, click Add to add a new data field (see the screenshot below). 4. In the Create data field window that appears (also shown in the screenshot), enter the following values: o o o Field Name: baccountid Display Name: baccount Field Type: DBInt(int) Page 63 of 97

64 Make sure that you select the DBInt type, rather than Int. DB in front of the type indicates that the field will be bound to the database. If the prefix is absent, the system will extend the DAC with a field, but the added selector field will not be bound to the database. 5. Click OK to again view the Create control window. Select Selector as the ControlType and click OK. Once the form is reloaded, the new selector field will be added onto the form. Setting the Field Attributes and Validating the Project To set the attributes of the selector, perform the following actions: 1. Right-click the baccountid field and select Attributes. 2. In the Custom attributes area of the DataField Attributes window that appears (see the screenshot below), enter the following code to define the attributes of the baccount selector field: [PXSelector(typeof(PX.Objects.CR.BAccount.bAccountID), SubstituteKey=typeof(PX.Objects.CR.BAccount.acctCD) )] If you add code lines for this field for the first time, keep the How to Apply parameter value as Append to Original, otherwise you should select Replace Original. 3. Click OK to save the changes and close the DataField Attributes window. Page 64 of 97

65 4. On the Customization menu, select Validate and Publish, which brings up the Compilation window and starts the application validation process immediately. 5. When the validation process has completed successfully, the Publish action button appears within the validation window (see the screenshot below), but it is soon to publish the project changes. Close the Compilation window. In this case, you may first publish the project s code and then perform downloading of the archive file. Considering such an order of actions is useful within more complicated projects, when each internal substep needs to be validated and archived not to spoil the whole project s code during the next step. Page 65 of 97

66 6. On the Customization menu, select Save Project to Database(GL2) to save intermediate customization changes to the database. Saving the Current State and Publishing the Project To make it possible for you to return to this customization step if the next step fails, you will save the current customization data to an external file. Open the Customization Data Editor and save this data as follows: 1. On the Customization menu, select View Customization Manager to open the Customization Projects form. 2. Click the Edit XML button in upper part of the form, on the main toolbar. 3. In the Customization Data Editor that appears within the new browser window, click Download Package, click Save File, and click OK to save the customization project to the external file. 4. Close the Customization Data Editor window. 5. On the Customization menu, select Validate and Publish again. In the Compilation window that appears, the validation process begins. 6. When the validation process has completed successfully, click the Publish action button to publish the project. 7. After the project has been published, select Close Project on the Customization menu. Notice the new Account Class selector field on the form; click the Magnifier icon at the right end of this field to open the lookup window with the account classes records. (See the screenshot below.) Page 66 of 97

67 Adding the Contact Selector Field In this example, you will add the Contact selector field, which will display additional information about business accounts to the Journal Transactions (GL ) form. In the process, you will create a new data field to store and display data selected by using this field, and use the ContactID key to access data in the relevant system database table. The selector field will use a parameterized query to display records from the BAccount table whose ContactID values match the BAccountID values. To add the Contact selector field onto this form, you will perform two general steps: adding the user interface (UI) element for the field, and setting the attributes of the field. After that, you will create the parameterized query for the added selector field. Finally, you will validate the customization changes, publish them as a finalized project, and save them to an external file (for example, to upload the project s code to another application instance or for the real production application). Adding the UI Element onto the Form Navigate to Finance > General Ledger > Enter to select the Journal Transactions form, if this form is not active at the moment. To add the UI element of the Contact selector field onto the Journal Transactions form, do the following: 1. On the Customization menu, select Open Customization Project to open the existing project, GL2, if it had been closed. Since this project has the UI customization code (see two previous examples), the Page Design Mode activates with the Journal Transactions form automatically. 2. On the Journal Transactions form, click the Batch Summary (upper) area to select it, rightclick near he location where you want to place the label of the new selector field, and select Add Input Control. 3. In the Create control window, click Add to add a new data field (see the screenshot below). 4. In the Create data field window that appears, enter the following values: o Field Name: ContactID Page 67 of 97

68 o Display Name: Contact ID o Field Type: DBString(nvarchar) o Length: 25 The exact value you add for the Length parameter is not so important, because the system automatically sets this value with discrete size steps from small (s) to extralarge (xl), depending on the field length in symbols entered by you. You can adjust this value further manually. 5. Click OK, and you will again be viewing the Create control window. Select Selector as the Control Type (see the screenshot below) and click OK. Once the form is reloaded, the new selector field will be added onto the form. Setting the Field Attributes To set the attributes of the selector field, perform the following steps: 1. Right-click the added Contact selector field, and select Attributes. 2. In the Custom attributes area of the DataField Attributes window that appears (see the screenshot below), enter the following additional code to define the attributes of the contactid selector field: [PXSelector(typeof(Search<PX.Objects.CR.Contact.contactID, Where<Optional<PX.Objects.GL.Batch.usrBAccountID>, Equal<PX.Objects.CR.Contact.bAccountID>>>))] 3. Click OK to save the changes and close the DataField Attributes window. 4. Open the Customization Data Editor, and save the customization project to an external file before performing instructions of the next step. Page 68 of 97

69 Setting Query Parameters for the Field To set additional limitations on the data displayed by the Contact selector field, define parameters for the query used for the data selection: 1. Right-click the Contact selector field on the form, and select Control Tree. 2. In the Aspx Control Tree window that appears, select Parameters in the tree, and on the Add menu, select Add Item, as shown in the screenshot below. 3. In the New Item window that appears, ensure that Parameters is displayed in the Collection box and PXControlParam in the Item Type box, and then click OK, as shown in the screenshot below. Page 69 of 97

70 4. Select PXControlParam in the tree, and select the All Props item on the drop-down list of the small window located above the parameter table. The property list for PXControlParam is displayed, as shown in the screenshot below. Use All Props selection to have the possibility to see all the parameters. 5. Define the query parameters by performing the following steps: o Set the PropertyName customized value in the tree, as follows: Select UsrBAccountID:PXSelector and copy to the clipboard the ID customized value, as shown in the screenshot below. Page 70 of 97

71 o Select the PXControlParam in the tree, and add as a customized value DataControls[BAccount_selector_ID].Value for the PropertyName. In this expression, you need to paste the ID customized value from the clipboard instead of the BAccount_selector_ID expression. Add form as the ControlID and Batch.usrBAccount as the Name customized values, as shown in the screenshot below. Validating and Publishing the Customization Project To validate the customization and publish it on the Acumatica ERP application, perform the following steps: 1. On the Customization menu, select Validate and Publish. The Compilation window appears and the validation process begins immediately. When the validation process has been successfully completed, the appropriate message is displayed in the window. 2. If no errors has encountered, click the Publish button that appears within the Compilation window. 3. After the project has been published, select Close Project on the Customization menu. 4. View the updated version of the Acumatica ERP application website, and test the implementation results of the customization project (see the screenshot below): o o o o Add a new record by clicking Add New Record. In the Account Class box, select an item (COGS, for instance) and add it to the form. In the baccount box, select an item (RAPIDBYTE, for instance) and add it to the form. Notice the new Contact ID selector field on the form; click the Magnifier icon at the right end of this field to open the lookup window with the possible contact data; this data corresponds to the entered baccount value, as shown in the screenshot below. Page 71 of 97

72 5. If this project had been developed for the real production application, you should download the final customization code to the XML file that will represent the archived distributive unit for the update procedure. To prepare this distributive unit, do as follows: o o o o On the Customization menu, select View Customization Manager to open the Customization Projects form. Click the Edit XML button in upper part of the form, on the main toolbar. In the Customization Data Editor that appears within the new browser window, click Download Package, click Save File, and click OK to save the customization project to the external file. Close the Customization Data Editor window. To use the distributive unit, open the Customization Data Editor on the target (real) application instance and upload the project s code to this real production application after specifying archive name of the XML file and its path. (You shouldn t unzip an external zipped XML file.) Validate and publish the customization code. Now the real production application has been updated. Adding a Combo Box onto a Form In this example, you will add the Level of Benefit combo box to the Opportunities (CR ) form. Classifying opportunities in this way can help users to sort and filter preferred potential contracts, and special reports based on this information can be generated for your company s top management. When they use this customized form, users can then select an appropriate level of benefit for each opportunity, based on criteria established by company management. In this example, we will use Low, Middle, High, and Very High as the benefit levels. You can, of course, implement different levels. Page 72 of 97

73 Creating a New Project 1. Create a new project (see a project s definition in Customization Project). The screenshot below illustrates the consecutive actions you need to take: o o Navigate to Organization > Customer Management > Enter to select the Opportunities form, and on the Customization menu, select Open Customization Project. In the Select Working Project window that appears, click New to add the new project. o o In the New Project window that appears, add the project name for instance, CR1. Click OK to close the New Project window; click OK again to close the Select Working Project window and create the new project. Adding the Combo Box onto the Form Proceed as follows to add the Level of Benefit combo box onto the form: 1. On the Customization menu, select Enter Page Design Mode. Now you can begin the customization of the form. 2. In the Opportunity Summary area, right-click near the place where the new combo box should be placed (under Effective Amount), and select Add Input Control. 3. In the Create control window that appears, click Add to add a new UI element. 4. In the Create data field window that appears, enter the following values (see also the screenshot below): o o Field Name: BenefitLevel Display Name: Level of Benefit Page 73 of 97

74 o o Field Type: DBString(nvarchar) Length: (may be empty) Make sure that you select the DBString type, rather than String. DB in front of the type indicates that the field will be bound to the database. If the prefix is absent, the system will extend the DAC with a field, but the added selector field will not be bound to the database. 5. Click OK to again view the Create control window. Select the Control Type as ComboBox, and click OK. Once the form is reloaded, the new selector field will be added onto the form. Creating the PXStringList Attribute and Activating the AllowEdit Property To prepare the list of benefit levels for the created combo box, you must edit the CROpportunity DAC code that had been automatically added along with the combo box. Do the following steps: 1. Right-click the added combo box and select Attributes. 2. In the DataField Attributes window that appears, type (within the Custom attributes entry box) the following additional code lines, also shown in the screenshot below. Page 74 of 97

75 [PXStringList(new string[] { "L", "M", "H", "VH" }, new string[] { "Low", "Middle", "High", "Very High" })] [PXDefault("M")] If you add code lines for this field for the first time, keep the How to Apply parameter value as Append to Original, otherwise you should select Replace Original. Optionally, you can allow the user not only to select an existing benefit level item from the drop-down list but also to add another level of benefit (which won t be displayed on the created drop-down list of levels but will be saved to the database and displayed after the user defines the different value and saves the form); with this purpose you should also activate the AllowEdit property for the combo box as follows: 3. Click OK to save the added code lines in the CROpportunity DAC, right-click the combo box again, and select Control Tree. 4. In the Aspx Control Tree window that appears (the UsrBenefitLevel:PXDropDown node is allocated), set the All Props criteria from the drop-down list of the small window located above the property table, set the AllowEdit property (of the PXDropDown type) to True, and click Apply to Page, as shown in the screenshot below. Page 75 of 97

76 Note that you defined in the added code lines not only the list of benefit level values but also the default value (M for Middle) of the combo box. Publishing the Project and Testing the Results Now the customization code for the project must be validated and tested. Do the following: 1. Optionally: If you want to make some other changes, you should save before the current project code; to do this, on the Customization menu, select Save Project to Database (CR2) to save the customization changes to the database. If your new changes will be erroneous, you can restore the project s code, obtained during performing instructions of the current example by using the Reload Project from Database item of the customization menu. 2. On the Customization menu, select Validate and Publish. The Compilation window appears and the validation process begins immediately. 3. When the validation process has been completed successfully, click Publish. 4. Close the project. You can see the added combo box, Level of Benefit, in the Opportunity Summary area. Notice that the Middle level is displayed by default. 5. In the Opportunity ID box, select any existing opportunity. Then open the Level of Benefit drop-down list, select the appropriate level, and click Save, as shown in the screenshot below. Page 76 of 97

77 6. Select another or add a new opportunity, type a level that is not displayed in the drop-down list, and click Save, as shown in the screenshot below. Adding a Column to a Grid Control In this example, you will add a new selector column to the Transaction Details grid control of the Journal Transactions (GL ) form. The new column must use an appropriate data access class (DAC) to access the system database and manipulate data. You will define this DAC by setting appropriate attributes for the selector column. Page 77 of 97

78 Adding the Selector Column By using the selector column, Customer s , the Acumatica ERP application user can select a client address to use it as a contact on the details of a transaction. To add a new selector column to the Transaction Details grid control, do the following: Navigate to Finance > General Ledger > Enter to select the Journal Transactions form and after creating the new project, GL3 (see as an example Creation a New Project), proceed as follows to add the UI element of the Account Class selector field onto the form: 1. On the Customization menu, select Enter Page Design Mode. Now you can begin the customization of this form. 2. Click the Transaction Details grid control to select it, right-click any place within the grid control header area, and select Control Tree. 3. In the Aspx Control Tree window that appears, on the Add menu, select Add Column to Grid (see item 1 in the screenshot below). 4. In the Add Grid Column window that appears, click Add to add a new data column (item 2). 5. In the Create data field window that appears, enter the following values (as item 3 shows): o Field Name: CustMail o Display Name: Customer s o Field Type: DBString(nvarchar) o Length: 50 Page 78 of 97

79 6. Click OK (item 4) to again view the Create control window. Select Selector in the Column Editor box (see item 5 in the screenshot below), and click OK (item 6) to save the entered data. 7. In the Aspx Control Tree window that appears again, click Apply to Page (see item 7). Setting Attributes and Publishing the Project To set the attributes of the selector column, perform the following actions: 1. On the Aspx Control Tree, click Attributes. 2. In the DataField Attributes window that appears, add the following code line to the Custom attributes area: [PXSelector(typeof(PX.Objects.CR.CRMassMail.mailTo))]. Click OK (see the screenshot below). If you add code lines for this field for the first time, keep the How to Apply parameter value as Append to Original, otherwise you should select Replace Original. Page 79 of 97

80 3. Optionally: If you want to make some other changes, you should save before the current project code: to do this, on the Customization menu, select Save Project to Database (GL3) to save the customization changes to the database. If your new changes will be erroneous, you can restore the project s code, obtained during performing instructions of the current example by using the Reload Project from Database item of the customization menu. 4. On the Customization menu, select Validate and Publish. The Compilation window appears and the validation process begins immediately. 5. When the validation process has been completed successfully, click Publish. 6. Close the project and refresh the page. You can see the new selector column, Customer s , in the grid control (see the screenshot below). You can begin to enter a new line to see the lookup window that can be opened from the new selector column. (If the MailTo column values of the CRMassMail table contain null values, the lookup window will be empty.) Page 80 of 97

81 Adding a Column to a Lookup Window This example illustrates adding to the Order Nbr lookup window on the Sales Orders (SO ) form a column that displays internal sales order numbers used by sales managers. You will also implement the quick search by setting the appropriate lookup property. To add this column to the lookup window, proceed as follows: 1. Create a new project (see a project s definition in Customization Project) by doing the following actions: o o o o Navigate to Distribution > Sales Orders > Enter to select the Sales Orders form, and on the Customization menu, select Open Customization Project. On the Select Working Project window that appears, click New to add the new project. On the New Project window that appears, add the project name, such as SO1. Click OK to close the New Project window; then click OK again to close the Select Working Project window and create the new project. 2. On the Customization menu, select Enter Page Design Mode to begin the form customization. 3. Right-click the Order Nbr field and select Control Tree. o In the Aspx Control Tree window that appears, on the Add menu, select Add Column to Selector, as shown in the screenshot below. Page 81 of 97

82 4. In the Add Selector Column window that appears, click Magnifier and select from the list of fields CustomerOrderNbr, as shown in the screenshot below. 5. Click OK to add the column for the OrderNbr lookup window. (This column is shown in the screenshot below as a tree item.) Page 82 of 97

83 6. Click Apply to Page to save the new column and close the Aspx Control Tree. 7. On the Customization menu, select Validate and Publish. The Compilation window appears and the validation process begins immediately. 8. When the validation process has been completed successfully, click Publish. 9. Close the project and open the lookup window of the Order Nbr box. Check that the Customer Order column is there as the rightmost column of the lookup window. 10. If you want to change the position of the added column, you can drag its header to the required position, as shown in the screenshot below. Page 83 of 97

84 To keep the new column s position (as well as widths of this and all the other columns) in the lookup window, you should click the leftmost column s header (icon), and in the column adjustment window, click Save layout, as shown in the screenshot below. (The order of columns in the column adjustment window shouldn t correspond to the order of columns in lookup window; drag column headers to change any column s position before saving the layout.) Page 84 of 97

85 Testing the Quick Context Search To test the current adjustment of the facility that enable the user to rapidly find the required customer s order number, do as follows: 1. Reopen the project. 2. Right-click the Order Nbr field, and select Control Tree again. (Keep the set by default Base Props item value on the drop-down list of the small window located above the parameter table.) Use Base Props selection by default to quickly find the parameters with the current value different from Null; select the Base Props instead of Show All to see, in particular, all the adjusted properties of the selected section. 3. In the Aspx Control Tree window that appears, notice the Current value of the FastFilterFields property of the OrderNbr:PXSelector section: CustomerOrderNbr, as shown in the screenshot below. Page 85 of 97

86 4. Close the project and open the Order Nbr lookup window. In the search window (in the lower left corner of the lookup window), try to type any full or partial order number, and ensure that search settings are applied to the new Customer Order column, as well as to the Order Nbr, because this is the single key column. The screenshot below illustrates an example of the quick search. Quick context search in key columns of a lookup field is always possible by default; search for other columns can be implemented after the appropriate adjustment of the FastFilterFields property. Implementing a Custom Event In this example, you will implement a custom event for the Journal Transactions (GL ) form. Implementing the event provides the ability to make sure the transaction is correct. If the CreditTotal value does not equal the DebitTotal value, the this.outofbalance boolean variable is set to true. Page 86 of 97

87 To implement this event, perform the following steps: 1. Create a new project (see a project s definition in Customization Project) by doing the following actions: o o o o Navigate to Finance > General Ledger > Enter to select the Journal Transactions form, and on the Customization menu, select Open Customization Project. On the Select Working Project window that appears, click New to add the new project. On the New Project window that appears, add the project name, such as GL4. Click OK to close the New Project window; then click OK again to close the Select Working Project window and create the new project. 2. On the Customization menu, select Enter Page Design Mode to begin the form customization. 3. Right-click the upper area of the form, and select Add Data Event on the pop-up menu. 4. In the Add Event Handler dialog that appears, select FieldUpdated as the Event Type, select CreditTotal as the Field Name, and click OK, as shown in the screenshot below. 5. In the Code Editor, which appears in a separate browser window (as shown in the screenshot below), you can see the following code template, which has been added to the code edit area for the form. Page 87 of 97

88 #region Event Handlers protected void Batch_CreditTotal_FieldUpdated(PXCache sender, PXFieldUpdatedEventArgs e) { var row = (Batch)e.Row; // var CreditlTotal = row.credittotal; } #endregion 6. Edit the custom event code so that the resulting code will be the following: using System; using System.Collections; using System.Collections.Generic; using System.Text; using System.Text.RegularExpressions; using PX.Data; using PX.Objects.CS; Page 88 of 97

89 using PX.Objects.CM; using PX.Objects.CA; using PX.Objects.GL.Overrides.PostGraph; using PX.Objects.PM; using PX.Objects; using PX.Objects.GL; namespace PX.Objects.GL { [PXCustomization] public class Cst_JournalEntry: JournalEntry { #region Event Handlers bool OutOfBalance = false; protected void Batch_CreditTotal_FieldUpdated(PXCache sender, PXFieldUpdatedEventArgs e) { var row = (Batch)e.Row; var CreditTotal = row.credittotal; if ((Batch)e.Row)DebitTotal!= row.credittotal { this.outofbalance = true; } } #endregion Page 89 of 97

90 } } 7. Click Validate and Publish in the upper side of the Code Editor window. 8. After successful completion of the validation process, click Publish to publish the customization code of the project. The value of this variable can be further displayed on the form if you add a field onto it. The field must be bound with the variable. Validating Field Values Using a Custom Event In this example, a custom event will be used for the Employees (EP ) form to ensure that the employee s date of birth has been specified and that the employee is 16 years of age or older. Creating the New Project Take the following actions to start creating validation logic: 1. Create a new project by doing the following actions: o o o o Navigate to Organization > Organization Structure > Manage to select the Employees form, and on the Customization menu, select Open Customization Project. On the Select Working Project window that appears, click New to add the new project. On the New Project window that appears, add the project name, such as EP1. Click OK to close the New Project window; then click OK again to close the Select Working Project window and create the new project. 2. On the Customization menu, select Enter Page Design Mode to begin to customize the form. Setting AutoCallBack Properties First, you should set AutoCallBack properties for the Hire Date field so that the form sends data to the server after each modification of the field value. This invokes validation logic that will be implemented for the form and stored in the server. Perform the following actions: 1. Right-click the Hire Date field, and select Control Tree. 2. In the Aspx Control Tree window that appears, select the All Props item on the drop-down list which is opened through the small window located above the property table. 3. Into the Customized value column, add the following AutoCallBack properties (see also the screenshot below): o o o Enabled: True Target : form Command: Save Page 90 of 97

91 4. Click Apply to Page to save the customized property values and close the Aspx Control Tree window. Starting to Add Validation Logic Proceed as follows to add validation logic: 1. Right-click area of the General Info tab and select Add Data Event. 2. In the Add Event Handler window that appears, select RowPersisting as the event type, keep EPEmployee as the table name, and click OK, as shown in the screenshot below. Page 91 of 97

92 3. In the Code Editor form, which appears in a separate browser window, you can see the following template, which has been added to the code edit area for the form (see the code fragment). #region Event Handlers protected override void EPEmployee_RowPersisting(PXCache sender, PXRowPersistingEventArgs e) { base.epemployee_rowpersisting(sender, e); var row = (EPEmployee)e.Row; // } #endregion Analyzing the Source Code To get optimal validation results, you must first analyze the corresponding original source code fragments to find out which data access classes (DACs) contain the fields that are to be validated, as well as how these fields are bound with one another within the appropriate business logic container (BLC) views. Proceed as follows: 1. Return to the Employees form, right-click the Date Of Birth field, and select Attributes. In the DataField Attributes window that appears, note the exact Field Name value (DateOfBirth). Also notice the View Name, which is the primary view name of this BLC, and Cache Type field values, as the screenshot below illustrates. Click Cancel to close the window. Page 92 of 97

93 The primary view is displayed after the colon within the View Name field value, while symbols to the right of the rightmost period of the Cache Type field value represent the name of the DAC. 2. On the Employees form, right-click the Hire Date field and select Attributes. In the DataField Attributes window that appears again, note the exact Field Name value (HireDate); also notice the View Name and Cache Type field values, as the screenshot below illustrates. 3. Click Cancel to close the window. 4. On the Employees form, by using the Customization menu, select View Source Code. 5. In the Source Code Browser form, which appears in the separate window with the Business logic tab active, open the Select Declarations region of the PX.Objects.EP.EmployeeMaint Page 93 of 97

94 name of the current BLC (which was automatically defined when the Source Code Browser form was opened and is displayed within the upper left lookup box, named Graph Name), and find view declarations where the aforementioned field names are used, as shown in the screenshot below. The two view definitions are selected with red rectangles. The second view definition is the most important, because by use of this view definition, you can find out how the fields of the two DACs are bound with one another. The definition code of the view is shown below. public PXSelect<Contact, Where<Contact.bAccountID, Equal<Optional< EPEmployee.parentBAccountID>>, And<Contact.contactID, Equal <Optional<EPEmployee.defContactID>>>>> Contact; Implementing the Validation Logic To implement the validation logic, proceed as follows: 1. In the Code Editor window, edit the custom event code so that the resulting code will be the following. using PX.Objects.AP; using PX.Objects.GL; using PX.SM; using PX.TM; using PX.Common; using System; using System.Collections; using PX.Data; using PX.Objects.CS; using PX.Objects.CR; using PX.Objects.CA; Page 94 of 97

95 using PX.Objects.CM; using System.Collections.Generic; using PX.Objects.AR; using PX.Objects.PM; using PX.Objects; using PX.Objects.EP; namespace PX.Objects.EP { [PXCustomization] public class Cst_EmployeeMaint: EmployeeMaint { #region Event Handlers protected override void EPEmployee_RowPersisting(PXCache sender,pxrowpersistingeventargs e) PXDefaultAttribute.SetPersistingCheck<Contact.dateOfBirth> (sender, e.row, PXPersistingCheck.NullOrBlank); DateTime birth = (DateTime)this.Contact.Current.DateOfBirth; EPEmployee row = (EPEmployee)e.Row; DateTime alloweddate = new DateTime(birth.Year + 16, birth.month, birth.day); DateTime hire = (DateTime)row.HireDate; if (hire!= null &&((DateTime)hire) < alloweddate) throw new PXSetPropertyException("The employee's hire date must be " + "at least 16 years after his or her birthdate."); } #endregion } } Within the RowPersisting event code, two methods of a field validation are used: The PXDefaultAttribute.SetPersistingCheck method, which is used to remind the user to enter the appropriate date of birth. The following code lines, which (along with the PXSetPropertyException method) checks the condition to warn the user if the new employee is younger than 16. These validation methods prevent a record from being saved if at least one of the aforementioned conditions is true. If the date of birth is null or empty, the common error message is displayed (such as Nullable object must Page 95 of 97

96 have a value), but you can use the PXSetPropertyException method to declare your own detailed error message by using the second validation version. 2. Click Validate and Publish. After the validation process has been finished successfully, click Publish to publish the customization project (see the screenshot below). Testing the Results Now you should test the results of the implemented validation logic to ensure that the logic works properly. Perform the following actions: 1. Return to the Employees form, close the project, and try to add a new employee record without entering the Date Of Birth value. Enter values for all the other required fields (allocated by the asterisk at the left of the name), as shown in the screenshot below. Page 96 of 97

97 2. Click Save: The error message appears that the nullable object must have a value, and the record is not saved. As was mentioned in the hint in the previous section, to define a more exact error message, you can add on your own a few more customization code lines to the EmployeeMaint BLC code lines that contain the appropriate condition check and error message text. 3. Add the date of birth so that the difference between it and the hire date is less than 16 years, and the second error message appears. This is the message text added by you to the event code as a parameter of the PXSetPropertyException method. 4. Make the hire date at least 16 years later than the date of birth, and click Save. The new record has been saved. Page 97 of 97

System Administration Training Guide. S125 Document Management

System Administration Training Guide. S125 Document Management System Administration Training Guide S125 Document Management Table of contents Certification Course Prerequisites... 4 Document Management... 6 Learning Objects:... 6 Wiki... 6 Wiki Article Approval...

More information

Web Services API Developer Guide

Web Services API Developer Guide Web Services API Developer Guide Contents 2 Contents Web Services API Developer Guide... 3 Quick Start...4 Examples of the Web Service API Implementation... 13 Exporting Warehouse Data... 14 Exporting

More information

T300 Acumatica Customization Platform

T300 Acumatica Customization Platform T300 Acumatica Customization Platform Contents 2 Contents How to Use the Training Course... 4 Getting Started with the Acumatica Customization Platform...5 What is an Acumatica Customization Project?...6

More information

Distribution Training Guide. D110 Sales Order Management: Basic

Distribution Training Guide. D110 Sales Order Management: Basic Distribution Training Guide D110 Sales Order Management: Basic Certification Course Prerequisites The combined D110 Sales Order Management certification course consists of a hands- on guide that will walk

More information

Using SQL Server Management Studio

Using SQL Server Management Studio Using SQL Server Management Studio Microsoft SQL Server Management Studio 2005 is a graphical tool for database designer or programmer. With SQL Server Management Studio 2005 you can: Create databases

More information

DiskPulse DISK CHANGE MONITOR

DiskPulse DISK CHANGE MONITOR DiskPulse DISK CHANGE MONITOR User Manual Version 7.9 Oct 2015 www.diskpulse.com info@flexense.com 1 1 DiskPulse Overview...3 2 DiskPulse Product Versions...5 3 Using Desktop Product Version...6 3.1 Product

More information

SQL Server An Overview

SQL Server An Overview SQL Server An Overview SQL Server Microsoft SQL Server is designed to work effectively in a number of environments: As a two-tier or multi-tier client/server database system As a desktop database system

More information

How to Configure the Workflow Service and Design the Workflow Process Templates

How to Configure the Workflow Service and Design the Workflow Process Templates How-To Guide SAP Business One 9.0 Document Version: 1.0 2012-11-15 How to Configure the Workflow Service and Design the Workflow Process Templates Typographic Conventions Type Style Example Description

More information

Distribution Training Guide. D100 Inventory Management: Basic

Distribution Training Guide. D100 Inventory Management: Basic Distribution Training Guide D100 Inventory Management: Basic Certification Course Prerequisites The course consists of a hands- on guide that will walk you through the specifics of Acumatica s Inventory

More information

Vodafone PC SMS 2010. (Software version 4.7.1) User Manual

Vodafone PC SMS 2010. (Software version 4.7.1) User Manual Vodafone PC SMS 2010 (Software version 4.7.1) User Manual July 19, 2010 Table of contents 1. Introduction...4 1.1 System Requirements... 4 1.2 Reply-to-Inbox... 4 1.3 What s new?... 4 2. Installation...6

More information

Release Document Version: 1.4-2013-05-30. User Guide: SAP BusinessObjects Analysis, edition for Microsoft Office

Release Document Version: 1.4-2013-05-30. User Guide: SAP BusinessObjects Analysis, edition for Microsoft Office Release Document Version: 1.4-2013-05-30 User Guide: SAP BusinessObjects Analysis, edition for Microsoft Office Table of Contents 1 About this guide....6 1.1 Who should read this guide?....6 1.2 User profiles....6

More information

ODBC Client Driver Help. 2015 Kepware, Inc.

ODBC Client Driver Help. 2015 Kepware, Inc. 2015 Kepware, Inc. 2 Table of Contents Table of Contents 2 4 Overview 4 External Dependencies 4 Driver Setup 5 Data Source Settings 5 Data Source Setup 6 Data Source Access Methods 13 Fixed Table 14 Table

More information

Content Author's Reference and Cookbook

Content Author's Reference and Cookbook Sitecore CMS 6.5 Content Author's Reference and Cookbook Rev. 110621 Sitecore CMS 6.5 Content Author's Reference and Cookbook A Conceptual Overview and Practical Guide to Using Sitecore Table of Contents

More information

Kaldeera Workflow Designer 2010 User's Guide

Kaldeera Workflow Designer 2010 User's Guide Kaldeera Workflow Designer 2010 User's Guide Version 1.0 Generated May 18, 2011 Index 1 Chapter 1: Using Kaldeera Workflow Designer 2010... 3 1.1 Getting Started with Kaldeera... 3 1.2 Importing and exporting

More information

Colligo Email Manager 6.2. Offline Mode - User Guide

Colligo Email Manager 6.2. Offline Mode - User Guide 6.2 Offline Mode - User Guide Contents Colligo Email Manager 1 Benefits 1 Key Features 1 Platforms Supported 1 Installing and Activating Colligo Email Manager 3 Checking for Updates 4 Updating Your License

More information

Scheduling Software User s Guide

Scheduling Software User s Guide Scheduling Software User s Guide Revision 1.12 Copyright notice VisualTime is a trademark of Visualtime Corporation. Microsoft Outlook, Active Directory, SQL Server and Exchange are trademarks of Microsoft

More information

SQL Server 2005: Report Builder

SQL Server 2005: Report Builder SQL Server 2005: Report Builder Table of Contents SQL Server 2005: Report Builder...3 Lab Setup...4 Exercise 1 Report Model Projects...5 Exercise 2 Create a Report using Report Builder...9 SQL Server 2005:

More information

Intellect Platform - Tables and Templates Basic Document Management System - A101

Intellect Platform - Tables and Templates Basic Document Management System - A101 Intellect Platform - Tables and Templates Basic Document Management System - A101 Interneer, Inc. 4/12/2010 Created by Erika Keresztyen 2 Tables and Templates - A101 - Basic Document Management System

More information

BulkSMS Text Messenger Product Manual

BulkSMS Text Messenger Product Manual BulkSMS Text Messenger Product Manual 1. Installing the software 1.1. Download the BulkSMS Text Messenger Go to www.bulksms.com and choose your country. process. Click on products on the top menu and select

More information

Results CRM 2012 User Manual

Results CRM 2012 User Manual Results CRM 2012 User Manual A Guide to Using Results CRM Standard, Results CRM Plus, & Results CRM Business Suite Table of Contents Installation Instructions... 1 Single User & Evaluation Installation

More information

System Administration Training Guide. S100 Installation and Site Management

System Administration Training Guide. S100 Installation and Site Management System Administration Training Guide S100 Installation and Site Management Table of contents System Requirements for Acumatica ERP 4.2... 5 Learning Objects:... 5 Web Browser... 5 Server Software... 5

More information

Building and Using Web Services With JDeveloper 11g

Building and Using Web Services With JDeveloper 11g Building and Using Web Services With JDeveloper 11g Purpose In this tutorial, you create a series of simple web service scenarios in JDeveloper. This is intended as a light introduction to some of the

More information

Increasing Productivity and Collaboration with Google Docs. Charina Ong Educational Technologist charina.ong@nus.edu.sg

Increasing Productivity and Collaboration with Google Docs. Charina Ong Educational Technologist charina.ong@nus.edu.sg Increasing Productivity and Collaboration with Google Docs charina.ong@nus.edu.sg Table of Contents About the Workshop... i Workshop Objectives... i Session Prerequisites... i Google Apps... 1 Creating

More information

Section 1: Ribbon Customization

Section 1: Ribbon Customization WHAT S NEW, COMMON FEATURES IN OFFICE 2010 2 Contents Section 1: Ribbon Customization... 4 Customizable Ribbon... 4 Section 2: File is back... 5 Info Tab... 5 Recent Documents Tab... 7 New Documents Tab...

More information

DocumentsCorePack for MS CRM 2011 Implementation Guide

DocumentsCorePack for MS CRM 2011 Implementation Guide DocumentsCorePack for MS CRM 2011 Implementation Guide Version 5.0 Implementation Guide (How to install/uninstall) The content of this document is subject to change without notice. Microsoft and Microsoft

More information

Legal Notes. Regarding Trademarks. 2012 KYOCERA Document Solutions Inc.

Legal Notes. Regarding Trademarks. 2012 KYOCERA Document Solutions Inc. Legal Notes Unauthorized reproduction of all or part of this guide is prohibited. The information in this guide is subject to change without notice. We cannot be held liable for any problems arising from

More information

Installation & User Guide

Installation & User Guide SharePoint List Filter Plus Web Part Installation & User Guide Copyright 2005-2011 KWizCom Corporation. All rights reserved. Company Headquarters KWizCom 50 McIntosh Drive, Unit 109 Markham, Ontario ON

More information

HP IMC User Behavior Auditor

HP IMC User Behavior Auditor HP IMC User Behavior Auditor Administrator Guide Abstract This guide describes the User Behavior Auditor (UBA), an add-on service module of the HP Intelligent Management Center. UBA is designed for IMC

More information

Visualization with Excel Tools and Microsoft Azure

Visualization with Excel Tools and Microsoft Azure Visualization with Excel Tools and Microsoft Azure Introduction Power Query and Power Map are add-ins that are available as free downloads from Microsoft to enhance the data access and data visualization

More information

Global Search v.2.8 for Microsoft Dynamics CRM 4.0

Global Search v.2.8 for Microsoft Dynamics CRM 4.0 Global Search v.2.8 for Microsoft Dynamics CRM 4.0 User Manual Akvelon, Inc. 2012, All rights reserved. 1 Contents Overview... 3 What s New in Global Search Versions... 4 Licensing... 6 Installation...

More information

Table and field properties Tables and fields also have properties that you can set to control their characteristics or behavior.

Table and field properties Tables and fields also have properties that you can set to control their characteristics or behavior. Create a table When you create a database, you store your data in tables subject-based lists that contain rows and columns. For instance, you can create a Contacts table to store a list of names, addresses,

More information

SourceAnywhere Service Configurator can be launched from Start -> All Programs -> Dynamsoft SourceAnywhere Server.

SourceAnywhere Service Configurator can be launched from Start -> All Programs -> Dynamsoft SourceAnywhere Server. Contents For Administrators... 3 Set up SourceAnywhere... 3 SourceAnywhere Service Configurator... 3 Start Service... 3 IP & Port... 3 SQL Connection... 4 SourceAnywhere Server Manager... 4 Add User...

More information

StreamServe Persuasion SP5 Ad Hoc Correspondence and Correspondence Reviewer

StreamServe Persuasion SP5 Ad Hoc Correspondence and Correspondence Reviewer StreamServe Persuasion SP5 Ad Hoc Correspondence and Correspondence Reviewer User Guide Rev B StreamServe Persuasion SP5 Ad Hoc Correspondence and Correspondence Reviewer User Guide Rev B 2001-2010 STREAMSERVE,

More information

PULSE Dashboard Administrator Guide (Updated 2/19/15)

PULSE Dashboard Administrator Guide (Updated 2/19/15) PULSE Dashboard Administrator Guide (Updated 2/19/15) All functions described in this document may be performed from a workstation on the network with the exception of Updating the Pulse Dashboard Software

More information

F9 Integration Manager

F9 Integration Manager F9 Integration Manager User Guide for use with QuickBooks This guide outlines the integration steps and processes supported for the purposes of financial reporting with F9 Professional and F9 Integration

More information

Colligo Email Manager 6.0. Offline Mode - User Guide

Colligo Email Manager 6.0. Offline Mode - User Guide 6.0 Offline Mode - User Guide Contents Colligo Email Manager 1 Key Features 1 Benefits 1 Installing and Activating Colligo Email Manager 2 Checking for Updates 3 Updating Your License Key 3 Managing SharePoint

More information

HOW TO USE THIS GUIDE

HOW TO USE THIS GUIDE HOW TO USE THIS GUIDE This guide provides step-by-step instructions for each exercise. Anything that you are supposed to type or select is noted with various types and colors. WHEN YOU SEE THIS Click Help

More information

Chapter 15: Forms. User Guide. 1 P a g e

Chapter 15: Forms. User Guide. 1 P a g e User Guide Chapter 15 Forms Engine 1 P a g e Table of Contents Introduction... 3 Form Building Basics... 4 1) About Form Templates... 4 2) About Form Instances... 4 Key Information... 4 Accessing the Form

More information

Strategic Asset Tracking System User Guide

Strategic Asset Tracking System User Guide Strategic Asset Tracking System User Guide Contents 1 Overview 2 Web Application 2.1 Logging In 2.2 Navigation 2.3 Assets 2.3.1 Favorites 2.3.3 Purchasing 2.3.4 User Fields 2.3.5 History 2.3.6 Import Data

More information

Hypercosm. Studio. www.hypercosm.com

Hypercosm. Studio. www.hypercosm.com Hypercosm Studio www.hypercosm.com Hypercosm Studio Guide 3 Revision: November 2005 Copyright 2005 Hypercosm LLC All rights reserved. Hypercosm, OMAR, Hypercosm 3D Player, and Hypercosm Studio are trademarks

More information

PowerLogic ION Enterprise 6.0

PowerLogic ION Enterprise 6.0 70002-0298-00 06/2009 PowerLogic ION Enterprise 6.0 Power management software User guide Notices This section describes the symbols used in this guide. Danger This alerts you to things that may cause

More information

Manual English KOI Desktop App 2.0.x

Manual English KOI Desktop App 2.0.x Manual English KOI Desktop App 2.0.x KOI Kommunikation, Organisation, Information Comm-Unity EDV GmbH 2010 Contents Introduction... 3 Information on how to use the documentation... 3 System requirements:...

More information

Content Author's Reference and Cookbook

Content Author's Reference and Cookbook Sitecore CMS 6.2 Content Author's Reference and Cookbook Rev. 091019 Sitecore CMS 6.2 Content Author's Reference and Cookbook A Conceptual Overview and Practical Guide to Using Sitecore Table of Contents

More information

VEDATRAK CRM 2.1. User's Guide

VEDATRAK CRM 2.1. User's Guide VEDATRAK CRM 2.1 User's Guide 2 (C) 2006-2010 SUI SOLUTIONS. All rights reserved. 3 Contents Overview...9 System Requirements...11 Installation Notes...12 Vedatrak Basics...13 User Roles...13 System Administrator...13

More information

Vector HelpDesk - Administrator s Guide

Vector HelpDesk - Administrator s Guide Vector HelpDesk - Administrator s Guide Vector HelpDesk - Administrator s Guide Configuring and Maintaining Vector HelpDesk version 5.6 Vector HelpDesk - Administrator s Guide Copyright Vector Networks

More information

Setting Up ALERE with Client/Server Data

Setting Up ALERE with Client/Server Data Setting Up ALERE with Client/Server Data TIW Technology, Inc. November 2014 ALERE is a registered trademark of TIW Technology, Inc. The following are registered trademarks or trademarks: FoxPro, SQL Server,

More information

Customization Manager in Microsoft Dynamics SL 7.0

Customization Manager in Microsoft Dynamics SL 7.0 Customization Manager in Microsoft Dynamics SL 7.0 8965: Customization Manager in Microsoft Dynamics SL 7.0 (1 Day) About this Course This one-day course is designed to give individuals a comprehensive

More information

Decision Support AITS University Administration. Web Intelligence Rich Client 4.1 User Guide

Decision Support AITS University Administration. Web Intelligence Rich Client 4.1 User Guide Decision Support AITS University Administration Web Intelligence Rich Client 4.1 User Guide 2 P age Web Intelligence 4.1 User Guide Web Intelligence 4.1 User Guide Contents Getting Started in Web Intelligence

More information

Umbraco v4 Editors Manual

Umbraco v4 Editors Manual Umbraco v4 Editors Manual Produced by the Umbraco Community Umbraco // The Friendly CMS Contents 1 Introduction... 3 2 Getting Started with Umbraco... 4 2.1 Logging On... 4 2.2 The Edit Mode Interface...

More information

IBM Sterling Control Center

IBM Sterling Control Center IBM Sterling Control Center System Administration Guide Version 5.3 This edition applies to the 5.3 Version of IBM Sterling Control Center and to all subsequent releases and modifications until otherwise

More information

Web Forms for Marketers 2.3 for Sitecore CMS 6.5 and

Web Forms for Marketers 2.3 for Sitecore CMS 6.5 and Web Forms for Marketers 2.3 for Sitecore CMS 6.5 and later User Guide Rev: 2013-02-01 Web Forms for Marketers 2.3 for Sitecore CMS 6.5 and later User Guide A practical guide to creating and managing web

More information

Supply Chain Finance WinFinance

Supply Chain Finance WinFinance Supply Chain Finance WinFinance Customer User Guide Westpac Banking Corporation 2009 This document is copyright protected. Apart from any fair dealing for the purpose of private study, research criticism

More information

UOFL SHAREPOINT ADMINISTRATORS GUIDE

UOFL SHAREPOINT ADMINISTRATORS GUIDE UOFL SHAREPOINT ADMINISTRATORS GUIDE WOW What Power! Learn how to administer a SharePoint site. [Type text] SharePoint Administrator Training Table of Contents Basics... 3 Definitions... 3 The Ribbon...

More information

BID2WIN Workshop. Advanced Report Writing

BID2WIN Workshop. Advanced Report Writing BID2WIN Workshop Advanced Report Writing Please Note: Please feel free to take this workbook home with you! Electronic copies of all lab documentation are available for download at http://www.bid2win.com/userconf/2011/labs/

More information

Custom Reporting System User Guide

Custom Reporting System User Guide Citibank Custom Reporting System User Guide April 2012 Version 8.1.1 Transaction Services Citibank Custom Reporting System User Guide Table of Contents Table of Contents User Guide Overview...2 Subscribe

More information

MODULE 7: TECHNOLOGY OVERVIEW. Module Overview. Objectives

MODULE 7: TECHNOLOGY OVERVIEW. Module Overview. Objectives MODULE 7: TECHNOLOGY OVERVIEW Module Overview The Microsoft Dynamics NAV 2013 architecture is made up of three core components also known as a three-tier architecture - and offers many programming features

More information

DEPLOYMENT GUIDE Version 2.1. Deploying F5 with Microsoft SharePoint 2010

DEPLOYMENT GUIDE Version 2.1. Deploying F5 with Microsoft SharePoint 2010 DEPLOYMENT GUIDE Version 2.1 Deploying F5 with Microsoft SharePoint 2010 Table of Contents Table of Contents Introducing the F5 Deployment Guide for Microsoft SharePoint 2010 Prerequisites and configuration

More information

NorthClark Computing, Inc. Bill of Material and Parts Master Maintenance. Administrator s Guide

NorthClark Computing, Inc. Bill of Material and Parts Master Maintenance. Administrator s Guide ERP Consulting Web Development Custom Programming Solutions Desktop & Web Applications for Manfact NorthClark Computing, Inc. Bill of Material and Parts Master Maintenance Administrator s Guide Web and

More information

Microsoft Word 2010. Quick Reference Guide. Union Institute & University

Microsoft Word 2010. Quick Reference Guide. Union Institute & University Microsoft Word 2010 Quick Reference Guide Union Institute & University Contents Using Word Help (F1)... 4 Window Contents:... 4 File tab... 4 Quick Access Toolbar... 5 Backstage View... 5 The Ribbon...

More information

Using the Query Analyzer

Using the Query Analyzer Using the Query Analyzer Using the Query Analyzer Objectives Explore the Query Analyzer user interface. Learn how to use the menu items and toolbars to work with SQL Server data and objects. Use object

More information

Microsoft Access 2010 handout

Microsoft Access 2010 handout Microsoft Access 2010 handout Access 2010 is a relational database program you can use to create and manage large quantities of data. You can use Access to manage anything from a home inventory to a giant

More information

Project Management Certification Exam. P200 Project Management: Basic

Project Management Certification Exam. P200 Project Management: Basic Project Management Certification Exam P200 Project Management: Basic Table of contents Certification Test Prerequisites... 3 Project Scenario: T&M Project... 4 Project Scenario Update: T&M Project... 5

More information

Asset Track Getting Started Guide. An Introduction to Asset Track

Asset Track Getting Started Guide. An Introduction to Asset Track Asset Track Getting Started Guide An Introduction to Asset Track Contents Introducing Asset Track... 3 Overview... 3 A Quick Start... 6 Quick Start Option 1... 6 Getting to Configuration... 7 Changing

More information

Knocker main application User manual

Knocker main application User manual Knocker main application User manual Author: Jaroslav Tykal Application: Knocker.exe Document Main application Page 1/18 U Content: 1 START APPLICATION... 3 1.1 CONNECTION TO DATABASE... 3 1.2 MODULE DEFINITION...

More information

Microsoft Access 2010 Part 1: Introduction to Access

Microsoft Access 2010 Part 1: Introduction to Access CALIFORNIA STATE UNIVERSITY, LOS ANGELES INFORMATION TECHNOLOGY SERVICES Microsoft Access 2010 Part 1: Introduction to Access Fall 2014, Version 1.2 Table of Contents Introduction...3 Starting Access...3

More information

Sendspace Wizard Desktop Tool Step-By-Step Guide

Sendspace Wizard Desktop Tool Step-By-Step Guide Sendspace Wizard Desktop Tool Step-By-Step Guide Copyright 2007 by sendspace.com This publication is designed to provide accurate and authoritative information for users of sendspace, the easy big file

More information

NINTEX WORKFLOW TIPS AND TRICKS. Eric Rhodes

NINTEX WORKFLOW TIPS AND TRICKS. Eric Rhodes NINTEX WORKFLOW TIPS AND TRICKS Eric Rhodes Table of Contents Eric Rhodes 1 Label It 2 Document Your Workflows with Action Labels Going Way Back 3 Backup Workflows with the Export Feature Name That Variable

More information

7 th Annual LiveText Collaboration Conference. Advanced Document Authoring

7 th Annual LiveText Collaboration Conference. Advanced Document Authoring 7 th Annual LiveText Collaboration Conference Advanced Document Authoring Page of S. La Grange Road, nd Floor, La Grange, IL 6055-455 -866-LiveText (-866-548-3839) edu-solutions@livetext.com Page 3 of

More information

The Power Loader GUI

The Power Loader GUI The Power Loader GUI (212) 405.1010 info@1010data.com Follow: @1010data www.1010data.com The Power Loader GUI Contents 2 Contents Pre-Load To-Do List... 3 Login to Power Loader... 4 Upload Data Files to

More information

Table of Contents INTRODUCTION... 2 HOME PAGE... 3. Announcements... 7 Personalize & Change Password... 8 Reminders... 9 SERVICE CATALOG...

Table of Contents INTRODUCTION... 2 HOME PAGE... 3. Announcements... 7 Personalize & Change Password... 8 Reminders... 9 SERVICE CATALOG... Table of Contents INTRODUCTION... 2 HOME PAGE... 3 Announcements... 7 Personalize & Change Password... 8 Reminders... 9 SERVICE CATALOG... 11 Raising a Service Request... 12 Edit the Service Request...

More information

Visual Studio.NET Database Projects

Visual Studio.NET Database Projects Visual Studio.NET Database Projects CHAPTER 8 IN THIS CHAPTER Creating a Database Project 294 Database References 296 Scripts 297 Queries 312 293 294 Visual Studio.NET Database Projects The database project

More information

Setting up the Oracle Warehouse Builder Project. Topics. Overview. Purpose

Setting up the Oracle Warehouse Builder Project. Topics. Overview. Purpose Setting up the Oracle Warehouse Builder Project Purpose In this tutorial, you setup and configure the project environment for Oracle Warehouse Builder 10g Release 2. You create a Warehouse Builder repository

More information

Abstract. For notes detailing the changes in each release, see the MySQL for Excel Release Notes. For legal information, see the Legal Notices.

Abstract. For notes detailing the changes in each release, see the MySQL for Excel Release Notes. For legal information, see the Legal Notices. MySQL for Excel Abstract This is the MySQL for Excel Reference Manual. It documents MySQL for Excel 1.3 through 1.3.6. Much of the documentation also applies to the previous 1.2 series. For notes detailing

More information

How to Define Authorizations

How to Define Authorizations SAP Business One How-To Guide PUBLIC How to Define Authorizations Applicable Release: SAP Business One 8.8 All Countries English September 2009 Table of Contents Introduction... 3 Authorizations Window...

More information

Employee Management Certification Exam. P130 Employee Management: Basic

Employee Management Certification Exam. P130 Employee Management: Basic Employee Management Certification Exam P130 Employee Management: Basic Certification Test Prerequisites You will perform the certification test in your installed copy of Acumatica with the Template DATA

More information

14.1. bs^ir^qfkd=obcib`qflk= Ñçê=emI=rkfuI=~åÇ=léÉåsjp=eçëíë

14.1. bs^ir^qfkd=obcib`qflk= Ñçê=emI=rkfuI=~åÇ=léÉåsjp=eçëíë 14.1 bs^ir^qfkd=obcib`qflk= Ñçê=emI=rkfuI=~åÇ=léÉåsjp=eçëíë bî~äì~íáåö=oéñäéåíáçå=ñçê=emi=rkfui=~åç=lééåsjp=eçëíë This guide walks you quickly through key Reflection features. It covers: Getting Connected

More information

Access 2007 Creating Forms Table of Contents

Access 2007 Creating Forms Table of Contents Access 2007 Creating Forms Table of Contents CREATING FORMS IN ACCESS 2007... 3 UNDERSTAND LAYOUT VIEW AND DESIGN VIEW... 3 LAYOUT VIEW... 3 DESIGN VIEW... 3 UNDERSTAND CONTROLS... 4 BOUND CONTROL... 4

More information

Learn how to create web enabled (browser) forms in InfoPath 2013 and publish them in SharePoint 2013. InfoPath 2013 Web Enabled (Browser) forms

Learn how to create web enabled (browser) forms in InfoPath 2013 and publish them in SharePoint 2013. InfoPath 2013 Web Enabled (Browser) forms Learn how to create web enabled (browser) forms in InfoPath 2013 and publish them in SharePoint 2013. InfoPath 2013 Web Enabled (Browser) forms InfoPath 2013 Web Enabled (Browser) forms Creating Web Enabled

More information

2X ApplicationServer & LoadBalancer Manual

2X ApplicationServer & LoadBalancer Manual 2X ApplicationServer & LoadBalancer Manual 2X ApplicationServer & LoadBalancer Contents 1 URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies,

More information

Global Search v 6.1 for Microsoft Dynamics CRM Online (2013 & 2015 versions)

Global Search v 6.1 for Microsoft Dynamics CRM Online (2013 & 2015 versions) Global Search v 6.1 for Microsoft Dynamics CRM Online (2013 & 2015 versions) User Manual Akvelon, Inc. 2015, All rights reserved. 1 Overview... 3 What s New in Global Search Versions for CRM Online...

More information

www.dfcconsultants.com 800-277-5561 Microsoft Dynamics GP Audit Trails

www.dfcconsultants.com 800-277-5561 Microsoft Dynamics GP Audit Trails www.dfcconsultants.com 800-277-5561 Microsoft Dynamics GP Audit Trails Copyright Copyright 2010 Microsoft. All rights reserved. Limitation of liability This document is provided as-is. Information and

More information

Table of Contents INTRODUCTION...2 HOME PAGE...3. Announcements... 6 Personalize... 7 Reminders... 9 Recent Items... 11 SERVICE CATALOG...

Table of Contents INTRODUCTION...2 HOME PAGE...3. Announcements... 6 Personalize... 7 Reminders... 9 Recent Items... 11 SERVICE CATALOG... Table of Contents INTRODUCTION...2 HOME PAGE...3 Announcements... 6 Personalize... 7 Reminders... 9 Recent Items... 11 SERVICE CATALOG...12 REQUEST...14 Request List View... 15 Creating a New Incident...

More information

EBOX Digital Content Management System (CMS) User Guide For Site Owners & Administrators

EBOX Digital Content Management System (CMS) User Guide For Site Owners & Administrators EBOX Digital Content Management System (CMS) User Guide For Site Owners & Administrators Version 1.0 Last Updated on 15 th October 2011 Table of Contents Introduction... 3 File Manager... 5 Site Log...

More information

To launch the Microsoft Excel program, locate the Microsoft Excel icon, and double click.

To launch the Microsoft Excel program, locate the Microsoft Excel icon, and double click. EDIT202 Spreadsheet Lab Assignment Guidelines Getting Started 1. For this lab you will modify a sample spreadsheet file named Starter- Spreadsheet.xls which is available for download from the Spreadsheet

More information

HP Enterprise Integration module for SAP applications

HP Enterprise Integration module for SAP applications HP Enterprise Integration module for SAP applications Software Version: 2.50 User Guide Document Release Date: May 2009 Software Release Date: May 2009 Legal Notices Warranty The only warranties for HP

More information

Stored Documents and the FileCabinet

Stored Documents and the FileCabinet Stored Documents and the FileCabinet Introduction The stored document features have been greatly enhanced to allow easier storage and retrieval of a clinic s electronic documents. Individual or multiple

More information

USER MANUAL (PRO-CURO LITE, PRO & ENT) [SUPPLIED FOR VERSION 3]

USER MANUAL (PRO-CURO LITE, PRO & ENT) [SUPPLIED FOR VERSION 3] Pro-curo Software Ltd USER MANUAL (PRO-CURO LITE, PRO & ENT) [SUPPLIED FOR VERSION 3] CONTENTS Everyday use... 3 Logging on... 4 Main Screen... 5 Adding locations... 6 Working with locations... 7 Duplicate...

More information

CRM Migration Manager 3.1.1 for Microsoft Dynamics CRM. User Guide

CRM Migration Manager 3.1.1 for Microsoft Dynamics CRM. User Guide CRM Migration Manager 3.1.1 for Microsoft Dynamics CRM User Guide Revision D Issued July 2014 Table of Contents About CRM Migration Manager... 4 System Requirements... 5 Operating Systems... 5 Dynamics

More information

DNNCentric Custom Form Creator. User Manual

DNNCentric Custom Form Creator. User Manual DNNCentric Custom Form Creator User Manual Table of contents Introduction of the module... 3 Prerequisites... 3 Configure SMTP Server... 3 Installation procedure... 3 Creating Your First form... 4 Adding

More information

Copyright EPiServer AB

Copyright EPiServer AB Table of Contents 3 Table of Contents ABOUT THIS DOCUMENTATION 4 HOW TO ACCESS EPISERVER HELP SYSTEM 4 EXPECTED KNOWLEDGE 4 ONLINE COMMUNITY ON EPISERVER WORLD 4 COPYRIGHT NOTICE 4 EPISERVER ONLINECENTER

More information

Workflow Conductor Widgets

Workflow Conductor Widgets Workflow Conductor Widgets Workflow Conductor widgets are the modular building blocks used to create workflows in Workflow Conductor Studio. Some widgets define the flow, or path, of a workflow, and others

More information

SonicWALL CDP 5.0 Microsoft Exchange InfoStore Backup and Restore

SonicWALL CDP 5.0 Microsoft Exchange InfoStore Backup and Restore SonicWALL CDP 5.0 Microsoft Exchange InfoStore Backup and Restore Document Scope This solutions document describes how to configure and use the Microsoft Exchange InfoStore Backup and Restore feature in

More information

Developing Rich Web Applications with Oracle ADF and Oracle WebCenter Portal

Developing Rich Web Applications with Oracle ADF and Oracle WebCenter Portal JOIN TODAY Go to: www.oracle.com/technetwork/java OTN Developer Day Oracle Fusion Development Developing Rich Web Applications with Oracle ADF and Oracle WebCenter Portal Hands on Lab (last update, June

More information

Hands-On Lab. Client Workflow. Lab version: 1.0.0 Last updated: 2/23/2011

Hands-On Lab. Client Workflow. Lab version: 1.0.0 Last updated: 2/23/2011 Hands-On Lab Client Workflow Lab version: 1.0.0 Last updated: 2/23/2011 CONTENTS OVERVIEW... 3 EXERCISE 1: DEFINING A PROCESS IN VISIO 2010... 4 Task 1 Define the Timesheet Approval process... 4 Task 2

More information

Qvidian Playbooks & Salesforce Setup Guide. Fall Release 2013

Qvidian Playbooks & Salesforce Setup Guide. Fall Release 2013 Qvidian Playbooks & Salesforce Setup Guide Fall Release 2013 Last Updated: 11/12/2013 Introduction Welcome to Qvidian Sales Playbooks & Analytics! This guide is directed toward CRM Administrators, Playbook

More information

Bonita Open Solution. Introduction Tutorial. Version 5.7. Process Design User Guidance Profile: Business Analyst

Bonita Open Solution. Introduction Tutorial. Version 5.7. Process Design User Guidance Profile: Business Analyst Bonita Open Solution Version 5.7 Introduction Tutorial Process Design User Guidance Profile: Business Analyst Contents Introduction... 5 Part 1. Download, install, and launch Bonita Open Solution locally...

More information

Aspera Connect User Guide

Aspera Connect User Guide Aspera Connect User Guide Windows XP/2003/Vista/2008/7 Browser: Firefox 2+, IE 6+ Version 2.3.1 Chapter 1 Chapter 2 Introduction Setting Up 2.1 Installation 2.2 Configure the Network Environment 2.3 Connect

More information

The Smart Forms Web Part allows you to quickly add new forms to SharePoint pages, here s how:

The Smart Forms Web Part allows you to quickly add new forms to SharePoint pages, here s how: User Manual First of all, congratulations on being a person of high standards and fine tastes! The Kintivo Forms web part is loaded with features which provide you with a super easy to use, yet very powerful

More information

Connectivity Pack for Microsoft Guide

Connectivity Pack for Microsoft Guide HP Vertica Analytic Database Software Version: 7.0.x Document Release Date: 2/20/2015 Legal Notices Warranty The only warranties for HP products and services are set forth in the express warranty statements

More information

Witango Application Server 6. Installation Guide for Windows

Witango Application Server 6. Installation Guide for Windows Witango Application Server 6 Installation Guide for Windows December 2010 Tronics Software LLC 503 Mountain Ave. Gillette, NJ 07933 USA Telephone: (570) 647 4370 Email: support@witango.com Web: www.witango.com

More information