Relationships Good to Know
Relationships and the "Rule of Two"
You can only view or query a parent object and its children at any given time. While CSM allows you to violate this rule by building Relationship chains in certain cases, doing so may cause display and performance issues.
For example, if an Incident is related to a Change and the Change Business Object determines which form displays based on a third Business Object, such as a Change Details object, Users may encounter display issues if you embed the Change Details form into the Incident form.
The rule of two also impacts field value selection. Using the example above, when you are working with Incidents, you cannot traverse the relationship from Change to Change Details to retrieve a value from the Change Details object.
Finding Relationships in Your System
A full list of Relationships is beyond the scope of this document. From CSM Administrator, export a schema document in a Blueprint (Blueprint > Tools > Export Schema) to view a full list of Relationships associated with a particular type of Business Object (example: Major).
To view a list of Relationships associated with one particular Business Object (example: Incident), you can export a Business Object schema.
Use Visualizations to view graphical representations of Relationships.
Form/Record Editing Guidelines
If a Form/record in the Form Arrangement is in an owned-by Relationship with the parent Form/record (example: Incident Owns Journals), then it can by edited; however, Forms/records in linked Relationships (example: Incident Links Problem) are read-only.