Designing processes - EMC Community Network
Designing processes - EMC Community Network Designing processes - EMC Community Network
Designing the Process To copy all values of a multi-valued attribute to a specific index of multi-valued indexes: 1. In the target tree, create a node representing the specific index of the multi-valued attribute. 2. Select the node representing all values (the index value for this node is ALL) in the source tree. 3. Select the node representing the single-attribute node in the source tree. 4. Launch the function dialog box by double-clicking on the function. 5. In the function dialog box, select FOR-EACH as the value for Input Context, and select Over-Write, Insert Before, or Insert After as the value of Output Context. When using the Insert After or Insert Before options, the values are inserted after or before the index. When using the Overwrite option, the existing values are overwritten. XML and other data formats Since Extensible Markup language (XML) is the standard used to exchange structured data between applications, the activity templates shipped with Process Builder support XML natively. Process designers can associate an XML schema with a service-specific message and use the data mapper to create an XML payload that can be sent to other applications. However, if the target application uses another data format (like Comma Separated Value (CSV)), then associate a translator with the message. At runtime, the Process Integrator uses a translator, if specified in data mapper, to convert the XML document into the desired format. A translator is a custom Business Object Framework (BOF) module that you write, for example, to convert a Comma Separated Variable (CSV) file to an XML document. This is a standard feature of the data mapper. Setting custom object types for attachments In some applications, executing processes must receive email with attachments. The default object type for an attachment is dm_document. However, you can also treat it as a custom object type by using the data mapper for the Email Inbound activity template. In the data mapper, set the ObjectType attribute in the Attachments node of the process data to any type that is valid for your repository. Looping Many applications must perform a series of activities several times in succession. Process Builder enables you to define loops by using a counter mechanism. The following process shows how to set up looping within a process. In the first activity, a human performer specifies a set of departments. Then, an automated loop cycles through each department, invoking a process for each department. 42 EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide
Designing the Process To create a simple loop: 1. Create a manual activity called Define Departments in which the user defines the departments for which a new process is started. 2. Create a Process Data Mapping activity called Setup Loop. This activity gets the number of departments defined in the manual activity and assigns that number to a counter. 3. Use another data mapping activity to decrement the CurrentCount by 1. Use a Subtract function to subtract 1 from CurrentCount and map it back to the same variable. It is valid to map the variable back to itself to get: CurrentCount = CurrentCount -1. This is necessary EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 43
- Page 1 and 2: EMC ® Documentum ® xCelerated Com
- Page 3 and 4: Table of Contents Chapter 1 Overvie
- Page 5: Table of Contents Chapter 8 Cleanin
- Page 8 and 9: Preface 8 EMC Documentum xCelerated
- Page 10 and 11: Overview • Provides security and
- Page 12 and 13: Overview 12 EMC Documentum xCelerat
- Page 14 and 15: Product Overview Documentum ECM pla
- Page 16 and 17: Product Overview Process automation
- Page 18 and 19: Planning and Designing the Applicat
- Page 20 and 21: Planning and Designing the Applicat
- Page 22 and 23: Planning and Designing the Applicat
- 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 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 74 and 75: 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
<strong>Designing</strong> the Process<br />
To copy all values of a multi-valued attribute to a specific index of multi-valued indexes:<br />
1. In the target tree, create a node representing the specific index of the multi-valued attribute.<br />
2. Select the node representing all values (the index value for this node is ALL) in the source tree.<br />
3. Select the node representing the single-attribute node in the source tree.<br />
4. Launch the function dialog box by double-clicking on the function.<br />
5. In the function dialog box, select FOR-EACH as the value for Input Context, and select<br />
Over-Write, Insert Before, or Insert After as the value of Output Context.<br />
When using the Insert After or Insert Before options, the values are inserted after or before the<br />
index. When using the Overwrite option, the existing values are overwritten.<br />
XML and other data formats<br />
Since Extensible Markup language (XML) is the standard used to exchange structured data between<br />
applications, the activity templates shipped with Process Builder support XML natively. Process<br />
designers can associate an XML schema with a service-specific message and use the data mapper to<br />
create an XML payload that can be sent to other applications. However, if the target application<br />
uses another data format (like Comma Separated Value (CSV)), then associate a translator with the<br />
message. At runtime, the Process Integrator uses a translator, if specified in data mapper, to convert the<br />
XML document into the desired format. A translator is a custom Business Object Framework (BOF)<br />
module that you write, for example, to convert a Comma Separated Variable (CSV) file to an XML<br />
document. This is a standard feature of the data mapper.<br />
Setting custom object types for attachments<br />
In some applications, executing <strong>processes</strong> must receive email with attachments. The default object<br />
type for an attachment is dm_document. However, you can also treat it as a custom object type by<br />
using the data mapper for the Email Inbound activity template. In the data mapper, set the ObjectType<br />
attribute in the Attachments node of the process data to any type that is valid for your repository.<br />
Looping<br />
Many applications must perform a series of activities several times in succession. Process Builder<br />
enables you to define loops by using a counter mechanism. The following process shows how to set up<br />
looping within a process. In the first activity, a human performer specifies a set of departments. Then,<br />
an automated loop cycles through each department, invoking a process for each department.<br />
42 <strong>EMC</strong> Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide