Using Literal Values to Sort Child Records - EnterWorks - EnterWorks Process Exchange (EPX) - Precisely EnterWorks - 10.5

EnterWorks Classic Administration Guide

Product type
Software
Portfolio
Verify
Product family
EnterWorks
Product
Precisely EnterWorks > EnterWorks
Precisely EnterWorks > EnterWorks Process Exchange (EPX)
Precisely EnterWorks
Version
10.5
Language
English
Product name
Precisely EnterWorks
Title
EnterWorks Classic Administration Guide
Topic type
Configuration
Administration
First publish date
2007

You can define a linked relation such that when a parent record is displayed in the Detail Editor, a subset of the linked child records will be displayed. To do this, in addition to defining one or more attribute join pairs that identify a child record as belonging to a particular parent record, you define an attribute pair that identifies the child record’s type.

To do this, the child records must contain an attribute whose value indicates what type of record it is, for instance, “Document”, or “Image”, or whatever other character string you want to use, (without the quotes). In the attribute pair, you would select this attribute as the child attribute.

For the parent attribute selection, you would scroll to the bottom of the attribute selection dropdown list and select Enter Literal Value. A field would appear to the right of the dropdown list that allows you to enter the character string for the type of child record you wish to display. You would enter one of the values stored in the children records’ type attribute. For instance, if the set of values used in your children records’ type attributes was “Document”, “Image”, and “Certificate”, you would enter one of those strings, (without the quotes).

Literal value attribute join pairs are often used to display subsets of a record’s digital assets. For instance, the linked relations defined may be:

  • Product to Digital Assets

  • Product to Digital Assets – Documents

  • Product to Digital Assets – Images

In this case, when a product record is opened in the Detail Editor, it would display three lists of linked records:

  • A list of all linked digital assets.

  • A list of all linked digital assets that are documents.

  • A list of all linked digital assets that are images.

An advantage of using literal value attribute pairs to display subsets of children records is that if when you have a parent record open in the Detail Editor, you add or upload a child record through one of the lists of records of a particular type, EnterWorks will assume that the record you are adding must be of the same type and it will enter the type into the new child record’s type attribute.

To continue our example, if I upload a digital asset through the list of “Image” child records, EnterWorks will set the type of the new record to “Image”. If I enter it through the list of all digital assets (whose link relationship does not contain a literal value attribute pair), EnterWorks will not set the new child record’s type.