Relationship access configuration - HxGN SDx - Update 63 - Administration & Configuration

Administration and Configuration of HxGN SDx

Language
English
Product
HxGN SDx
Search by Category
Administration & Configuration
SmartPlant Foundation / SDx Version
10

Relationship Definitions are configured between two interfaces, and each end interface can be realized by many different class definitions. Referring to an object at end 1 means any object that realizes interface 1 of the relationship definition.

Access groups are used to control relationship navigation, creation, and termination with optional conditions further qualifying the access. Access groups are related to relationship definitions, and the properties are set on these relationships.

The relationships can be configured in a number of ways:

  • When creating the relationships through drag and drop (access group onto relationship definition or vice versa) or updating it, select the Maintain Attributes link on the confirmation dialog box to display a form with the section shown below. Details of the option on this dialog box are described in the sections below.

  • To use the Manage Access Groups command from the relationship definition, right-click on the relationship definition. This user interface allows you to drag access groups onto the relationship definition and list edit the relationship properties. Click Remove Selected Item to remove relationships between the access groups and relationship definitions.

Relationship navigation access

Relationships can be navigated in two directions: forwards from end 1 to 2 and backwards from end 2 to 1.

The expansion in each direction is controlled separately by a Boolean property and optional condition found on the relationship definition/access group relationship.

To allow users of the access group to navigate the relationship, select the check box for either Expand relationship 1 to 2 or Expand relationship 2 to 1 or both. (These are Exp12 and Exp21 in the Manage Access Groups user interface.)

When used in the Web Client, the Allow expansion of InfoMap 1-2 and Allow expansion of InfoMap 2-1 options let you expand the relationship from the end 1 object to the end 2 object, or from the end 2 object to the end 1 object, respectively, in the Info Map view. (These are InfomapExp12 and InfomapExp21 in the Manage Access Groups user interface.) If these attributes are not set, the non-Info Map specific Exp12 and Exp21 attributes are used.

To make this navigation conditional, select a condition for Forward expansion filter condition or Reverse expansion filter condition or both. Note that the condition definition is based on the two objects being related, and these are identified as Obj1 and Obj2. (These are Condition12 and Condition21 in the Manage Access Groups user interface.)

Relationship creation and update access

Relationships can be created in two directions

  • by dropping the object at end 1 onto end 2

  • by dropping the object at end 2 onto end 1

When a relationship is being created between two objects, the system determines which objects go to end 1 and end 2 based on the interfaces on each object compared with the interfaces at end 1 and end 2 of the relationship definition. Only when both objects instantiate both interfaces is the direction of the drag and drop important, and then the object being dropped is treated as the object at end 2.

The creation in each direction is controlled separately by a Boolean property and optional condition found on the relationship definition to access group relationship.

  • To allow users of the access group to create the relationship, select the check box for either Allow drop of object 1 onto object 2 or Allow drop of object 1 onto object 2 or both. (These are Drop12 and Drop12 in the Manage Access Groups user interface.)

  • To make this navigation conditional, select a condition for Create condition. Note that the condition definition is based upon the two objects being related, and these are identified as Obj1 and Obj2.

  • A user can update the relationship if they can create it. The user’s role must have an access group related to the relationship definition with either of the drag and drop properties set, and the condition must be satisfied.

Relationship terminate access

When configuring the access to terminate a relationship, a separate Boolean property is used, and the same condition used initially for create conditions is used.

  • To allow a user to terminate the relationship, in the Update form, select the check box for Allow terminate. (This is Ter in the Manage Access Groups user interface.)

  • To make terminating a relationship conditional, select a condition for Create condition. The system uses the same condition for create, update, and terminate.