Define Advanced Properties for a Relationship

Advanced Users can use the Advanced page in the Relationship Properties window to define the following properties:

• Advanced Options:

  Options for deleting child objects when parent objects are deleted, making records in the Relationship read-only, reloading the Relationship when constraints change, etc.

• Load Options:

  Options for loading Relationship data (load all data, load only keys, or load based on size).

• Groups:

  Options for defining Group Member type when child records are added (only applicable if the child object is a Group Object).

• Attributes:

  Additional pieces of information (or meta-data) that can be associated with the Relationship. Some attributes are automatically set, but others must be provided manually.

To define advanced properties for a Relationship:

1. Open the Relationship Properties window:
   1. In the CSM Administrator main window, click the Blueprints category, and then click the Create a New Blueprint task.

      Note: If working on a saved Blueprint, open the existing Blueprint.

   2. In the Object Manager, click a Business Object in the Object tree, and then click the Edit Relationships task in the Structure area.

      The Relationship Editor opens.

      Tip: You can also click the Edit Relationship button on the Blueprint Editor Toolbar to open the Relationship Editor.

   3. Click Add to add a new Relationship, or Edit to edit an existing Relationship.
2. Click the Advanced page.
3. Define advanced options for the Relationship:
   • (Owns Relationships only) Delete children with parent:

     Select this check box to delete child objects when the parent object is deleted.

   • Read-only:

     Select this check box to make records in the Relationship read-only. In CSM, Users will be able to view records for the Relationship, but will not be able to add or remove records.

   • Load immediately:

     Select this check box to load the child object when the parent is loaded. If this is not checked, the child object might not be loaded until it is needed.

     Note: This check box can affect system performance. Only change this setting if absolutely necessary.

     .
   • (Owns Relationships only) Automatically create record:

     Select this check box to automatically create a child object when the parent is created.

     .
   • Children must be in final state before owner can go into final state:

     Select this check box to require child objects to be in a final state before the parent object can be set to its final state. For this setting to be effective, the objects in the Relationship must have lifecycles defined with a status designated as the final state.

   • Reload Relationship when constraint Fields change:

     Select this check box to reload the Relationship data when a Field that defines one of its constraints changes values.

     Note: Normally, Relationships are loaded and updated based on specialized controls (tabs, related item selectors, etc.). However, if you have Relationship constraints based on Fields whose values can change for other reasons, the data in the Relationship will not be up to date if the values in those Fields change. For example, the SLA related to an Incident might change based on the selected Incident category and priority, which are Relationship constraints. When the Priority or Category fields change, the Relationship should be reloaded to show the relevant SLA.
   • Don't load when constraints are blank:

     Select this check box to not load the Relationship if the Fields that define its constraints do not contain any values.

   • (Link Relationships only) Exclude Relationship from Grid customization:

     Select this box to prevent Users from personalizing the Tab Grid for linked records that appear in the parent object's Form Arrangement.

4. Define load options for the Relationship:
   • Load Everything (default):

     Select this option to load the entire table of related data into memory.

   • Load Keys:

     Select this option to load only the keys for the Relationship, along with pages of records as needed. If loading from a Grid, the number of Fields is limited to those on the Grid.

   • Load Based on Size:

     Select this option to have the system decide how to load data. If the estimated dataset exceeds 3 MB, only keys are loaded. If the estimated dataset does not exceed 3 MB, the entire dataset is loaded. The dataset estimate is based on the definition type, such as the number of Fields and their type, as well as the amount of text stored in the Fields.

   • Default Sort Field When Loading Keys:

     If loading keys or loading based on size, select a Field from the related Business Object to determine the order in which the keys are loaded.

     • Ascending:

       Select this option to sort the data in ascending order (ex: 0-10, A-Z) based on the selected Field.

5. Define advanced Group options for the Relationship:
   Note: The Groups section is only available if the child object is part of a group.
   1. Click the down arrow to expand the Groups section.
   2. Define options for determining the type of Group Member that is created when a child object is added to the Relationship:
      • Type is set manually (when added):

        Select this radio button to allow Users to select the Group Member that is used as the child in the Relationship. No member is used until a User selects it.

      • Type automatically changes based on:
        • Field:

          Select this radio button to use the value from a Field in the parent object to determine which Group Member to use. Then, select a Field in the drop-down. For example, in an Incident Links Customer Relationship, Incident might have a Customer Type field that can hold the values External or Internal.

        • Expression:

          Select this radio button to use an Expression that returns the Group Member type. Then, click the Ellipses button to open the Expression Manager, where you can select an existing Expression or create a new one; or click the Custom Expression button to create a custom Expression.

   3. Define additional options for determining when a Group Member is added to the Relationship:
      • Only auto-create when Group Member type can be determined:

        Select this check box to automatically create a Group Member only after the Group Member type is determined. If the Group Member type is based on a Field or an Expression, the system will not necessarily know which Group Member to create until the Field has been populated or the Expression has been evaluated. If you check this option, the system will wait until there is a value in the Field or until the Expression is evaluated before it creates a Group Member.

      • Set Group Member ID in parent:

        Select this check box to populate the Group Member Type field in the parent object with the Group Member's RecID when the Group Member is created.

        Note: This option is only available if you selected to determine the Group Member type based on a Field in the parent object.
      • Transfer fields when Group type changes:

        Select this check box to transfer fields from one Group Member to another when the Group Member type changes.

6. Define attributes for the Relationship. Database attributes are used to indicate special attributes used for a Business Object’s database table. Most of these are set by the system.
   • General Attributes:

     Click the down arrow to expand the General Attributes section. Then, click an empty row and provide the attribute name and associated value (if applicable).

   • Database Attributes:

     Click the down arrow to expand the Database Attributes section. Then, click an empty row and provide the attribute name and associated value (if applicable).

     Note: Only advanced Users should define attributes. For more information about attributes, please contact Cherwell Support.
7. View additional advanced information for the Relationship:
   • Relationship ID:

     Select this button to open a window that displays the internal ID that is used for the Relationship. This ID can be used instead of the Relationship's name in many places in the system.

   • Find Dependencies:

     Select this button to scan the Relationship for a list of other definitions in the system that use this Relationship. When the scan is finished, the Definition Dependencies window opens, listing the dependent definitions.

8. Click OK.

9. Publish the Blueprint (File>Publish Blueprint) to commit the changes, or save the Blueprint (File>Save Blueprint) to continue making other changes.