Relationship Nodes
Relationship folders are used whenever an activity definition file contains more than one activity. The names of the folders match the name of the associated activity. You form the link by matching the name of the relationship folder to the activity ID of the related activity and by matching the values for the data items. You define each relationship using a separate node.
To indicate the unique instance identifier that links the data item between activities:
Map a data item to the ActivityId node of the main orchestration.
Drag and drop a data item with the same name as above to the Relationship node in the related activity. The Relationship node has the same name as the Activity node of the main activity.
For example, in the sample scenario, there could be a related but separate business process represented in an orchestration called RefinanceOrchestration. That orchestration could contain a LoanRefinance Activity node, a Refinance ActivityID, and orchestration shapes such as Receive Appraisal Request. The Relationship node and relationship ID, however, could be LoanID, indicating the link to the original LoanProcess activity.