Parent-child relationships
When you link objects with other objects of the same type, then a parent-child relationship is created. For example, you can link Incidents to other Incidents, thereby creating a parent-child relationship.
You can specify that any items added to the parent are also added to the children. For example, if you add a note to the parent incident, the same note is added to the child incidents. The same note is not linked to all of the child incidents, rather, copies of the note are added to each child incident.
Not only are items added, but actions are also applied. For example, if the parent item is closed, then any child items that are in a state to be closed are also closed.
There will be instances when child items cannot be closed. If that is the case, then you are notified which item cannot be closed.
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.
In addition to specifying the Propagation Action property on a parent or child collection attribute, you also need to specify that specific actions are propagated. For more information, see Actions.
To specify parent-child linking on an attribute:
- Open the required business object.
- In the Properties grid, alongside the Propagate Actions property, set the required value.
- Save the changes you have made.
If you select the... |
then alongside the Propagation Action property, |
---|---|
Parent collection attribute, |
select True to indicate that any changes made to the Child item are applied to the Parent item. |
Children collection attribute, |
select True to indicate that any items added or changes applied to the Parent item are applied to the Child item. |