Designing processes - EMC Community Network

More documents

Recommendations

Info

Designing the Process Inter-process communication Process Builder includes an Invoke Process activity template that enables a parent process to invoke a child process. An example of this is if you have an order process that must perform a credit check. Instead of building the credit check procedure into the order process, create it as a separate process to be invoked as a child process. You can manage the credit check process separately and independently, and it can be called by other parent processes. The Invoke Process activity template provides a basic mechanism to pass process data from the parent process to the child process. By using the Post Event to Parent activity template, the child process communicates to the parent process by posting events to the parent process instance. However, the posted event is only a name that carries no payload to the parent. To pass a data payload from the child to the parent, use the following approach: In this example, the parent process invokes the child process in the third activity: 50 EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide
Designing the Process The Invoke Process activity passes a workflow correlation identifier to the child. The child process needs this identifier to call the correct parent process instance. Map the correlation identifier of the parent to the variable parentInstanceCorrId of the child, as illustrated: After invoking the child process, the parent process instance waits for a response message with the payload from the child in the HTTP Inbound - Step activity. The following shows the configuration for the HTTP Inbound - Step activity: EMC Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 51
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 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 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 76 and 77: Creating the User Interface Adaptor
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
Page 124 and 125:
Understanding the approach to proto
Page 126 and 127:
Create and run the New Account Appl
Page 128 and 129:
Designing the New Account Applicati
Page 130 and 131:
Designing the New Account Applicati
Page 132 and 133:
Design dashboard and add dashlets 1
Page 134 and 135:
Design dashboard and add dashlets 1
Page 136 and 137:
Process Duration alert 3. From the
Page 138 and 139:
Process Duration alert 17. On the k
Page 140 and 141:
Designing the New Account Process -
Page 142 and 143:
Designing the New Account Process -
Page 144 and 145:
Running the Average Duration proces
Page 146 and 147:
Designing the Average Duration repo
Page 148 and 149:
Designing the New Account by Custom
Page 150 and 151:
Designing the New Accounts by Custo
Page 152 and 153:
Designing the New Accounts Opened t
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Designing the New Accounts Opened L
Page 160 and 161:
Completing the prototype dashboard
Page 163 and 164:
Index A activities count children,
Page 165:
Index designing activity triggers,
show all

Designing processes - EMC Community Network

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?