Adding a Node by Modeling After an Existing Node

The model after action enables you to create a node with the same property values and hierarchy relationships as an existing node. You can create the new node in the same viewpoint (for hierarchy viewpoints), or you can create the node in specified related viewpoints in the same view.

This enables you to copy an existing node and insert it into all of the related viewpoints in a single operation rather than having to perform individual request actions.

For example, suppose you had a list viewpoint and two hierarchy viewpoints that each used different hierarchy sets. In the list viewpoint, you configure the two hierarchy viewpoints as related viewpoints. Then, when you perform a model after action in the list viewpoint, a request is generated with these request items:

An Add action in the list viewpoint for the copy of the existing node
Insert actions in both hierarchy viewpoints that insert the new node under the same parents as the existing node in those hierarchy sets. For shared nodes, the new node is inserted under all of the parents of the original node in the hierarchy.

Considerations for Model After

If you do not have permission to perform an action that is generated as part of a model after action, a validation error is displayed. For example, if you do not have Insert permission on a hierarchy set in a viewpoint and you perform a model after that generates that Insert action, the request action is generated and a validation error for that action is displayed.
To perform a model after action in a list viewpoint, you must first specify at least one related viewpoint (see Configuring Related Viewpoints). If there are no related viewpoints for a list viewpoint, use the Copy action instead.

Considerations for Model After Using Related Viewpoints

In order to perform a model after in a viewpoint other than the one containing the source node, you must first configure that viewpoint as a related viewpoint. See Configuring Related Viewpoints.
For model after operations, related viewpoints are one-way. That is, if in Viewpoint A you set Viewpoint B as a related viewpoint, when you perform a model after action in Viewpoint A it will generate a request action to insert the node in Viewpoint B, but when you perform a model action in Viewpoint B it will not generate a request action to insert the node in Viewpoint A.
If you specify a list viewpoint as a related viewpoint, property update actions are generated for each additional property in the list viewpoint for that node. For example, if list viewpoint A has list viewpoint B as a related viewpoint and list viewpoint B contains properties for a node that aren't in list viewpoint A, when you perform a model after action in list viewpoint A the additional properties in list viewpoint B are also copied.

Modeling After a Node

Open the viewpoint that you want to make changes to and then either open a draft request or create a new request.
Select the node instance in the viewpoint that you want model after.
Perform an action:
- For list viewpoints, click Actions , and then click Model After.
  
  Note:
  You must have at least one related viewpoint configured in order to use model after in a list viewpoint.
- For hierarchy viewpoints, click Actions , then Model After, and then select an option:
  - This Viewpoint: Copies the selected node and inserts it under all parents of the selected node in the current viewpoint.
  - Related Viewpoints: Copies the selected node and inserts it under all parents of the selected node in the current viewpoint and all related viewpoints.
    
    Note:
    This option is available only if you have configured at least one related viewpoint.
The new node is created with the name "Copy of (original node)".
Modify the name for the new node and update node properties as needed.