-
From a tree view, right-click on an existing relationship definition and click Create new RelDef.
-
In the New Relationship Definition dialog box, provide a name and description for the new relationship. For more information about relationship definitions, see Relationship Definitions.
-
In the End 1 section of the dialog box, choose the interface definition for End 1 of the relationship.
-
In the Role and Role display name boxes, provide labels to represent the object or objects that will be on this end of the relationship.
-
Use the Minimum cardinality box to indicate whether this relationship is a requirement for objects on this end.
For example, documents cannot exist without a relationship to an owning group, so
for the relationship definition between documents and owning groups, the minimum cardinality
on the owning group end is set to 1. If the relationship is not required, you can
leave this value 0.
-
Use the Maximum cardinality box to indicate how many of the objects at this end can be related to each of the objects at the other end.
For example, any number of files can be related to each document, so for the relationship
definition between documents and files, the maximum cardinality on the file end is
set to *, indicating any number.
-
If necessary, choose an option from the Object at end 1 list to indicate restrictions on creating relationships on published objects. You can restrict the creation of the relationship to objects that are published by the same authoring tool or within the same container, or you can allow the relationship to be created when the object is created by a different authoring tool.
-
If you want to limit access to this relationship in SmartPlant Foundation Desktop Client or when viewing data in Schema Editor using the standard security options, set Filter out edge in display to True. Otherwise, the command to see this relationship on the end 1 object will be available to all users.
-
In the End 2 section of the dialog box, use the boxes to provide the same information about the other end of the relationship definition as you provided for end 1.
-
In the Delete behavior section of the dialog box, indicate what should happen to the objects on each end of an existing relationship when the object on the other end is deleted.
For example, if you are creating a relationship between a contract and a document,
specify what you want to happen to documents associated with the contract when the
contract is deleted or what you want to happen to the contract when the document is
deleted. In this section, select True if you want the deletion of one object to result in the deletion of the object at
the other end. Select False if the object on the other end should be kept.
-
In the Copy behavior section of the dialog box, indicate what should happen to the objects on each end of an existing relationship when the object on the other end is copied.
For each end, you can specify if copying that object will result in copying the other
object, copying the other object and the relationship (leaving the relationship pointing
to the same objects as the first relationship), or not copying the object or relationship
at all.
-
Click OK.