When you want to refer to the process state in terms that are larger in scope than its individual activities, a Compound Activity Node is used. A Compound Activity Node is a container that contains various nodes and arrows.
A Compound Activity Node contains child nodes. A Compound Activity Node must have a child Start Node and at least one child Exit Node. Also, no arrow transition is allowed from child nodes inside the Compound Activity Node to the nodes outside the compound activity.
A Compound Activity Node can have any node except another compound node.
Following are the features of a Compound Activity Node:
You can resize a Compound Activity Node by selecting it and dragging its boundaries.
You must define the arrow of the same name as that of the Exit node defined in Compound Activity as the outgoing arrow of the Compound Activity.
A Compound Activity Node can have only one Start node.
Default name of a Compound Activity Node is Compound Activity 1. Suffix digit is incremented according to the creation of compound nodes in a process definition.
Compound Activity Node does not support Iterator Node, Recall, Voting, Triggers.
The Compound Activity Node offers no support for the Iterator (Parallel) Loop node, reclaiming, voting rules, or triggers.
You can add the following to a Compound Activity Node:
UDAs: Refer to 6.18 Specifying User Defined Attributes for more details.
Action Set: Refer to 11.1 Using Java Actions for more details.
Timers: Refer to 6.22 Using Due Dates and Timers for more details.
Due Date: Refer to 6.22 Using Due Dates and Timers for more details.
Forms: Refer to Chapter 8 Using Forms for more details.
Priority: Refer to 6.7.3 Setting Activity Level Priority for more details.
