If you link processes together with child processes, then you can specify that any changes made (or items are added) to the parent process are automatically reflected in its children. For example, if you have an Incident (Incident A) with three child Incidents (Incidents B, C and D), and you add a note to Incident A, then the note is also added (or propagated) to the child Incidents.
You can configure which actions and optional actions are added to child items using the Process Designer.
In addition to specifying parent-child propagation using the Process Designer, you need to ensure that the business object upon which the process is based has been configured such that parents can be linked to children in either a downward or upward direction. That is, either items added to the parent are reflected in its children (downward) or items that are added to the children are reflected in its parent (upward). You cannot specify both directions. For more information, see Attributes.
For information about adding actions, see Adding a manual action to a process. For information about adding optional actions, see Associating an optional action with a status.
When using the Create Child action, you can also specify which process and template the child process will use. This enables you to populate some fields on the child process automatically. For more information about templates, see Templates.
When linking processes together, remember to activate all of the processes being used; otherwise, the associated action will not appear at runtime.
Was this article useful?
The topic was:
Not what I expected