INTRO

It is possible to create variables by 'Chaining' together Attributes in a manner that will follow the Parent Attribute on  through to the desired Child attribute(s).

It is important to note that the system Objects (Travelers, Parts, Work Orders, etc.) contain two types of attributes.

Linking Attributes

These attribute types are used to link to Child Objects.  As seen in figure 1 below, the Flow Traveler contains a Linking Attribute to a Work Order.  This Linking Attribute is named 'sFRRQ'.    Then if you follow the diagram, you can see that the Work Order also contains Linking Attributes; sRQOR (the Work Orders selected Organization) and sRQAD (The Work Orders selected Contact).  From there we can link to the actual Data Attributes as described below.

Data Attributes

These attributes are the final data you wish to display.  Because we link through them by composing a 'Chaining' technique of attribute names we can access these Data Attributes that may be nested down within Child Objects.

In figure 1 below, you can see these attributes:

sORName - the selected Organization Name

sADContact - The selected Contact from the Parent Work Order

sADTitle - Title of the Contact Person of the Contact Object

Example 1 - Configuration of a Variable for a Label Type Document

The following example demonstrates how to compose a variable by Chaining together attribute names from parent objects down to nested child objects.  The screenshot was taken from within the Document Object with a Label Type.

String Attribute Composing

You can see that our first Attribute (sFRRQ) is a linked attribute that provides the Work Order Number.

An underscore must be added between each specified Attribute.

Now we call the second attribute which is once again a linked attribute.  This attribute (sRQOR) is on the previously called RQ object and links to the Organization Object.

Now we can call the final Data Attribute that contains the information we are really after, the Organization Name (sORName).

Example 2 - Obtaining PO Information for Received Parts

This example will demonstrate how to display PO data to the operator while they are viewing a Traveler.  

You must first create a Calc NV on the Step Definition.

After it has been added to the NV listbox of the Step Definition you will need to click on it to open and further configure it.

Attribute Chaining 

sPRPI - because the NV is linked to the PR, you can immediate grab the Part Record Part Item numer (sPRPI)

sPIPS - the PI links to the Part Item Part Supplier (sPIPS)

sPSPN - the PS links to the Part Supplier Part Number

This Attribute Chain must be used to obtain the Part Supplier Part Number.  

Now that you have drilled down to the Part Supplier Part Number you can use the same chain to get additional data.

This includes any item listed on the Part Supplier form such as Supplier Part Name, Supplier Price, Part Lead-Time, Manufacturer Part

Supplier Part Name = sPRPI_sPIPS_sPSName

Supplier Price = sPRPI_sPIPS_sPSPrice

Part Lead-Time = sPRPI_sPIPS_sPSsLeadTime

Manufactuer Part = sPRPI_sPIPS_sPSMP

Resulting Display on Traveler