Designing processes - EMC Community Network
Designing processes - EMC Community Network
Designing processes - EMC Community Network
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Creating the Data Model<br />
• To search on SDTs in the user interface, use a task list template for the search.<br />
• If you delete or change the name of an SDT after implementing it, you will break the data binding in<br />
Forms Builder. You must delete the dangling control or rebind it to the renamed SDT.<br />
• SDTs are more lightweight than object attributes and are better for performance and scalability.<br />
Understanding process parameters<br />
Process parameters provide agility and control by allowing an application administrator to intervene,<br />
overriding the normal process execution. Process parameter values provide administrators with a high<br />
level of control over a process. Specifically, process parameters are used in place of fixed values within<br />
a process such as escalation roles, transition conditions, performer conditions, dynamic performer<br />
assignments, task name, and task instructions. Administrators can change process parameters<br />
without uninstalling the process. When an administrator changes the values of the parameter from<br />
the Administration tab in TaskSpace, the value is used in all process instances started after the<br />
change is made.<br />
Changing process elements<br />
When you decide to alter a process, use caution as you make your changes. You can add elements to<br />
the process, but avoid deleting process variables, Java methods, or structured data types. Create a data<br />
field and use it in the process, but do not delete the old field. Just avoid using it. Deleting a process<br />
variable or package from a process template can cause the process to become unstable.<br />
If you must update process data in Process Builder, ensure that you update the process data in Forms<br />
Builder, as well. Changing the name of a field in Process Builder invalidates the binding to the form<br />
template. Open the templates in Forms Builder and save them to restore the binding. Any changes to<br />
the data model (for example, adding a new SDT) require that you uninstall, save, and reinstall the<br />
form templates and <strong>processes</strong>.<br />
Changing activity names<br />
When you change the name of an activity, it is equivalent to deleting it and creating an activity in its<br />
place. All the associated information is logically deleted. Thus, it is a best practice not to change<br />
activity names after the process has been deployed.<br />
Selecting SDTs and package attributes for<br />
monitoring<br />
When you create an SDT you must mark it as reportable if you want to create BAM reports on this<br />
data. You also have to choose the activities in which to collect this data. Even though it is technically<br />
feasible to monitor every attribute of every SDT and package, do not do that. It is a best practice to<br />
understand thoroughly your reporting requirements. For reports based on SDT/package attributes,<br />
you must precisely identify which attributes to monitor and the location in the process this monitoring<br />
<strong>EMC</strong> Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 31