Create or Edit a Link Relationship - EnterWorks - EnterWorks Process Exchange (EPX) - Precisely EnterWorks - 10.5

To create or edit a link relationship:

1. Log into the EnterWorks Classic UI as a user with Administrative privileges.

1. Open the parent repository’s Manage Links editor: open the Feature bar, open the Content folder, open the desired repository folder, click the arrow to the right of the repository’s name, click the arrow to the right of Manage Model, and select Manage Links. The list of all link relationships for the repository will be displayed.

2. Do one of the following:

• To create a new link relationship, open the Action dropdown list and select New. An empty link relationship will be opened in the Manage Links editor.

• To edit an existing link relationship, select the link relationship, open the Action dropdown list, and select Edit. The link relationship will be opened in the Manage Links editor.

4. Edit the configuration values:

   • Name: The name of the link relationship. Link relationships must have names that are unique across the EnterWorks system. Do not include special characters in the name, such as & < > ".

   • Description: A description of the purpose of the link relationship.

   • Child Repository: Choose the child repository.

   • Link Type:

     • Use Join Condition: One or more pairs of attributes are used to link the repositories. For more information, see Join Conditions.

     • Manually choose record(s): Deprecated. Do not use this option. If you choose this option, link tables may not load, the Hierarchy/Taxonomy Manager may not load, users may not be able to create linked preferences, and other errors may occur. For more information, see Link Management Troubleshooting.

   • Sub Type:

     • One to Many (Parent-Child): One parent repository is linked to one child repository.

     • Many to Many (Parent-Child): Many parent repositories are linked to many child repositories.

     • Accessory: Deprecated.

     • Hierarchy View: To use a non-restricted hierarchy in a repository, you must create a link of sub-type Hierarchy View between the repository and the Hierarchy Catalog repository.

     • Extended: Deprecated.

     • Digital Assets: In order to link a repository to DamLink, you must create a linked relation of sub-type Digital Assets.

     • Retail Product: Deprecated.

     • Retail Product SKU: Deprecated.

   • Show in Simplified Display List: These settings determine where this link relationship will be available to be used.

     • User Preferences: This link relationship will be available for use in user preferences.

     • Search: The link relationship will be available for use in searches.

     • Import Templates: The link relationship will be available for use when you create an import template.

     • Export Templates: The link relationship will be available for use when you create an export template.

     • Reports: The link relationship will be available for use when you create a report.

5. When you are finished editing the configuration options, click Next.

6. If you selected Use Join Condition for the Link Type, the Join Condition list will be displayed. Edit the configuration options:

1. Child Repository Sort Attribute: This attribute will be used to determine the order in which child records are displayed in the parent record. This attribute must be in the snapshot table.

If you want to be able to reorder the records, this attribute must be a dedicated attribute, meaning it must only be used for sorting. If a child record may be linked to more than one parent record, do not reorder the child records, because when you reorder the records in one parent record, it will disrupt the sort order in the other parent records.

2. Choose the Attribute Pair: Join attribute pairs are used to identify linked records. They consist of an attribute in the parent repository and an attribute in the child repository. Both attributes must be in the snapshot table. For more details on join attribute pairs, see Join Conditions.

Define one or more join attribute pairs:

• To add a join attribute pair that does not use a literal value, (for information on literal values, see Using Literal Values to Sort Child Records):

  1. Parent Repository Attribute: Select the join attribute for the parent repository. The parent repository’s join attribute’s values must be unique, meaning that no two records in the repository will have the same value in their join attribute.

  2. Child Repository Attribute: Select the join attribute for the child repository. The child repository’s join attribute must be dedicated – it must only be used to identify a child record’s parent record.

  3. Click the Add button.

• To add a join attribute pair that uses a literal value:

  1. Parent Repository Attribute: Scroll to the bottom of the attribute dropdown list and select Enter Literal Value.

  2. A field will appear to the right of the Parent Repository Attribute field. Enter the character string you will use to identify the subset of child records, for instance “Documents”, (without the quotes).

  3. Child Repository Attribute: Select a dedicated attribute that will only be used to record which subset of child attributes it will be displayed in, for instance “Image Context”, (without the quotes).

  4. Click the Add button.

  • To delete a join attribute pair, in the Join Conditions list, click the trashcan to the left of the attribute pair you wish to delete.

  1. When you have finished editing the join attributes, click Next to move to the Display Options screen.

7. The Display Option screen has two tabs:

• Child: These settings define which attributes from the child repository will be displayed when the parent record is opened in the Detail Editor, and how those attributes will be displayed.

• Parent: These settings define which attributes from the parent repository will be displayed when the child record is opened in the Detail Editor, and how those attributes will be displayed.

Edit the configuration options on the Child tab, then do the same on the Parent tab. The configuration options are the same on both tabs.

• Number of Records Per Page: How many records will be displayed on a page.

• Window Display Height: The height of the display, in pixels.

• Show Link in Detail Editor: If this is checked, the link table will be shown when the parent repository record is opened in the Detail Editor.

• Placement Group: When a record is opened in the Detail Editor, this is the Attribute Group and Attribute Tab in which the linked record’s attributes will appear. Either select an existing Attribute Group and Tab or click the Manage button to add or change the Attribute Group or Tab.

• Show Buttons: These checkboxes control which action buttons will be available to users.

  • Open Link Table in Tab with Preference: The linked records will be displayed in a tab, as a table. The only attributes that will be displayed are those that are included in the specified preference.

• Edit Button Label Description: Click this button to modify the default labels for the selected buttons:

• There are two lists of attributes. The attribute list on the left holds attributes that are available to be shown in the parent’s record when it is in the Detail Editor. The attributes in the list on the right are the attributes that will be shown.

  • To move an attribute from one list to the other, select it and use the arrow buttons to move it to the left or the right.

  • To change the display order of attributes in the Detail Editor, select one or more attributes and use the up and down arrows to move the attributes to the desired location.

• Source: To display attributes from another linked repository, select the repository in the Source dropdown list. That repository’s attributes will be displayed in the list of available attributes.

• Display Width: To change the width of the boxes used to display the attributes, click the Display Width button, and edit the settings as desired.

• Define Parent JSON Properties: On the Parent tab, if you want to configure the Unified Parent Child View for the New UI, define the JSON properties that control it.

When the Unified Parent Child View capability is configured, when a child record is displayed in the Detail Editor in the New UI, selected attributes from the parent record are displayed in the group indicated by the setting Placement Group.

Note that the Unified Parent Child View capability does not support muti-edit (editing more than one record at once).

Build the JSON properties string to define how the parent record’s attributes will be displayed.

JSON Property	Purpose
"mergeView":true	This property is mandatory. It enables the Unified Parent Child View.
"hideGrid":<true-or-false>	If this property is false, the parent record’s attributes will be displayed in a table rather than in a list. The default value for this is true.
"filterByColocatePrefix":<true-or-false>	If this property is true, the only parent attributes that will be displayed are those whose name begins with the text string specified by the colocatePrefix property. The default value for this is false. If "filterByPreference" is set to true, it will override the "filterByColocatePrefix" setting. The attributes will be filtered by the specified preference instead of filtered by the prefix specified by colocatePrefix.
"colocatePrefix":"<put-your-prefix-string-here>"	If this property is true, display the parent’s attributes before the child attributes that begin with this string. If the filterByColocate property is true, the only parent attributes that will be displayed are those whose name begins with the text string specified by this property.
"filterByPreference":<true-or-false>	If this property is true, the only parent record’s attributes that will be displayed are those that are included in the preference specified by the Open Link Table in Tab with Preference setting. The default value for this is false. If "filterByPreference" is set to true, it will override the "filterByColocatePrefix" setting. The attributes will be filtered by the specified preference instead of filtered by the prefix specified by colocatePrefix.

Examples of Unified Parent Child View Configurations
To display the parent record’s attributes that begin with the text string “member”: {"mergeView":true, "filterByColocatePrefix":true, "colocatePrefix":"member"}
To display the parent record’s attributes in a table: {"mergeView":true, "hideGrid":false}
To display only the parent record’s attributes included in the preference specified in the Open Link Table in Tab with Preference setting: {"mergeView":true, "filterByPreference":true}
To display in a table of the parent record’s attributes that begin with the text string “member”: {"mergeView":true, "hideGrid":false, "filterByColocatePrefix":true, "colocatePrefix":"member"}

8. When you are finished editing the settings on the Child tab, move to the Parent tab. This tab defines which of the parent record’s attributes will be displayed when a child repository’s record is viewed in the Detail Editor. The configuration options for the Parent tab are the same as those on the Child tab. Configure the Parent tab.

9. When you are finished editing the Parent tab, click the Save button to save your changes to the link relationship.

10. Clear the cache in both the Classic UI and the New UI.