Designing processes - EMC Community Network
Designing processes - EMC Community Network Designing processes - EMC Community Network
Creating the User Interface Figure 12 Process and form template version links When a form template associated with a process is checked out and a new version created, Forms Builder automatically links the process to the latest version of the template. Conversely, if you delete the most recent form template version, the associated process automatically points to the previous version. You also cannot delete a task, initiate process, or process parameter template if the template and its associated process are both non-current versions. However, if either the process or the associated form template are the current version, you can delete the form template. Custom error messages The custom error message is important to the validation process and requires careful consideration. It is also an important element of the UI design as it provides useful feedback to the user when entering data. Error messages are created in Forms Builder by the template designer during template creation and are entered in the error message field for each control on the Display tab in the Properties pane. When writing custom error messages, you should give the user-specific information about the correct value to enter. Telling the user that the value entered is invalid does not provide much guidance. It is better to phrase the message in a positive manner and provide an example of a valid value to enter. A good example would be: Enter a valid date using the format MM/DD/YYYY. Another technique that is helpful to users is to provide default values for controls that use specific masks, such as dates, social security numbers, and phone numbers, so that the user has an example to follow before entering a new value. If a control does not have a custom error message defined in the template and the value entered is not valid, the system displays a default error message. The default error messages are generic and only provide guidance as to the data constraints for the control. An example of a default message for an invalid data type is: Value entered is not valid for the integer data type. An example of a default message for an invalid value for a specific data constraint is: Enter a valid value equal to or greater than %%" (where %% = the defined minimum 74 EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide
Creating the User Interface value). While these messages may be helpful to the user, they are not as helpful as messages created specifically for a template, tailored to the data requirement for that template. Data adaptors Some general guidelines for using adaptors are: • Do not use too many different adaptors as it can impede performance. You can use one data source adapter to populate multiple fields at once by populating off one database table with multiple columns. This way, the adaptor only runs once. • Keep adaptors simple and lightweight and keep the execution time of data source adaptors as short as possible. • Do not perform high latency calls within data source adaptors, such as long-running queries or slow web service invocations, as these calls can greatly impede performance of the UI. • If you plan to use more than one adaptor, concentrate on getting one adaptor to work before creating another. • When using a data source adaptor, make sure that the input is required and that the output is repeating. • When creating a custom data source adaptor, you have a choice of creating it as a class or service-based business object (SBO). If you create it as a class first it is much easier to validate and debug the adaptor. You can then convert the adaptor to an SBO if desired. The following table provides information on which templates or controls each adapter can be used with, guidelines for how best to use each type of adaptor, and important limitations. Table 4 Adaptor Types and Uses Adaptor Type Item Initializer Available Templates or Controls Not available on folder information, process parameter, or task templates Available on these controls: Text Field, RichText, Number Field, Date Field, DateTime Field, CheckBox, CheckBox Group, Radio Button Group, ListBox, Dropdown List, Readonly Table, Bar Codes, Slider, Embedded Form, and Filter Best Uses/Limitations Use this adaptor if you want a value entered automatically in a field when the template instance is created. The out-of-the-box item initializer is configured to enter the current date/time in a date/time field. To use your own logic, create a custom initializer. When using an item initializer for an integer value in a number field, also specify a default value for the field. On a document view template, the initialization will only execute when the document view is used while importing documents in TaskSpace. EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 75
- Page 24 and 25: Planning and Designing the Applicat
- Page 26 and 27: Planning and Designing the Applicat
- Page 28 and 29: Planning and Designing the Applicat
- Page 30 and 31: Creating the Data Model submitter_a
- Page 32 and 33: Creating the Data Model should occu
- Page 34 and 35: Designing the Process Defining acti
- Page 36 and 37: Designing the Process The transitio
- Page 38 and 39: Designing the Process 2. Add a seco
- Page 40 and 41: Designing the Process The end resul
- Page 42 and 43: Designing the Process To copy all v
- Page 44 and 45: Designing the Process because the i
- Page 46 and 47: Designing the Process 3. On the Tim
- Page 48 and 49: Designing the Process 48 EMC Docume
- Page 50 and 51: Designing the Process Inter-process
- Page 52 and 53: Designing the Process In the HTTP I
- Page 54 and 55: Designing the Process For the child
- Page 56 and 57: Designing the Process at or right a
- Page 58 and 59: Designing the Process Enabling repo
- Page 60 and 61: Designing the Process Performance a
- Page 62 and 63: Designing the Process 62 EMC Docume
- Page 64 and 65: Creating the User Interface mind th
- Page 66 and 67: Creating the User Interface Figure
- Page 68 and 69: Creating the User Interface 4. Sele
- Page 70 and 71: Creating the User Interface Figure
- Page 72 and 73: Creating the User Interface Figure
- Page 76 and 77: Creating the User Interface Adaptor
- Page 78 and 79: Creating the User Interface Figure
- Page 80 and 81: Creating the User Interface 5. Spec
- Page 82 and 83: Creating the User Interface 1. Open
- Page 84 and 85: Creating the User Interface 11. In
- Page 86 and 87: Creating the User Interface Working
- Page 88 and 89: Creating the User Interface 88 EMC
- Page 90 and 91: Monitoring Business Activity • pu
- Page 92 and 93: Monitoring Business Activity (PRS).
- Page 94 and 95: Monitoring Business Activity • Us
- Page 96 and 97: Performance and Scalability System
- Page 98 and 99: Performance and Scalability Factors
- Page 100 and 101: Performance and Scalability Skill-s
- Page 102 and 103: Performance and Scalability
- Page 104 and 105: Performance and Scalability If regi
- Page 106 and 107: Performance and Scalability 106 EMC
- Page 108 and 109: Deploying the Application At deploy
- Page 110 and 111: Deploying the Application 110 EMC D
- Page 112 and 113: Archiving the Application • When
- Page 114 and 115: Archiving the Application b. Log in
- Page 116 and 117: Archiving the Application 5. Create
- Page 118 and 119: Archiving the Application h. Select
- Page 120 and 121: Archiving the Application 120 EMC D
- Page 122 and 123: Prototyping overview Prototyping ov
Creating the User Interface<br />
Figure 12<br />
Process and form template version links<br />
When a form template associated with a process is checked out and a new version created, Forms<br />
Builder automatically links the process to the latest version of the template. Conversely, if you delete<br />
the most recent form template version, the associated process automatically points to the previous<br />
version. You also cannot delete a task, initiate process, or process parameter template if the template<br />
and its associated process are both non-current versions. However, if either the process or the<br />
associated form template are the current version, you can delete the form template.<br />
Custom error messages<br />
The custom error message is important to the validation process and requires careful consideration. It<br />
is also an important element of the UI design as it provides useful feedback to the user when entering<br />
data. Error messages are created in Forms Builder by the template designer during template creation<br />
and are entered in the error message field for each control on the Display tab in the Properties pane.<br />
When writing custom error messages, you should give the user-specific information about the correct<br />
value to enter. Telling the user that the value entered is invalid does not provide much guidance. It is<br />
better to phrase the message in a positive manner and provide an example of a valid value to enter.<br />
A good example would be: Enter a valid date using the format MM/DD/YYYY.<br />
Another technique that is helpful to users is to provide default values for controls that use specific<br />
masks, such as dates, social security numbers, and phone numbers, so that the user has an example to<br />
follow before entering a new value.<br />
If a control does not have a custom error message defined in the template and the value entered is not<br />
valid, the system displays a default error message. The default error messages are generic and only<br />
provide guidance as to the data constraints for the control. An example of a default message for an<br />
invalid data type is: Value entered is not valid for the integer data type. An<br />
example of a default message for an invalid value for a specific data constraint is: Enter a valid<br />
value equal to or greater than %%" (where %% = the defined minimum<br />
74 <strong>EMC</strong> Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide
Change language