Designing processes - EMC Community Network

Designing the Process
3. Activity C: This activity performs the cleanup. It deletes the temporary group that you just created.
If you do not delete the temporary group, performance may suffer.
Designing processes
Consider the following when designing the process:
• Creating complex conditional routing with a decision split, page 35
• Using sub-processes, page 36
• Understanding message correlation, page 36
Creating complex conditional routing with a decision
split
This section describes how to configure a complex type of routing, one that you can consider three
different routing options based on criteria. An example of a less complex decision split is if you have a
document that must be reviewed by a Vice President (VP). If it is a marketing document, then the VP
of Marketing must review and approve it. If it is an engineering document, then the VP of Engineering
must review and approve it. In this example, the process diagram looks like this:
However, you may have a requirement that is more complex. Similar to the previous example, you
may want the VP of Marketing to review marketing documents or the VP of Engineering to review
engineering documents, but what do you do with a document that is neither marketing or engineering
In this example, a document that does not fall into one of those two categories must be reviewed and
approved by both VPs. This means that there are cases where only one task is triggered (going to one
of the VPs), whereas in other cases both tasks are triggered (going to both of the VPs).
To model this complex routing, you need to add a Join activity. Even though it is common to create
a Join after a decision split, this example uses the Join to consider the two out of three case. In this
example, the process diagram looks like this:
EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 35