A chained-process operates independently once it has been activated by its parent process. The parent process continues with its own flow logic without waiting for the chained-process to complete.
The interaction between a parent process and a chained-process goes in one direction only. Neither process control nor values of User Defined Attributes (UDAs) are passed back to the parent process.
To model a chained-process:
Create the parent process definition and model the process flow.
Create the Chained-Process definition and model the process flow.
Add a Chained-Process Node to the parent process definition.
Connect the parent to the chained-process definition.
For instructions, refer to section 9.2.1 Connecting Parent and Chained-Process Definitions.
When the process definitions are connected, you can easily navigate from the parent to the chained-process definition. For instructions, refer to section 9.2.2 Navigating to Chained-Process Definitions.
In both parent and chained-process definitions, specify the User Defined Attributes (UDAs) that will be passed from the parent to the chained-process.
Note
You can use different names for the same UDA in the process definitions involved. However, the data type must be identical. Otherwise, you cannot map the UDAs.
Define data mappings for the UDAs that need to be passed to the chained-process.
For instructions, refer to section 9.2.3 Defining Data Mappings for Chained-Processes.
