Creating selection lists for traceability

Three columns in the Traceability Priority List table (TrPriMst) are not used by the GainSeeker system. You can use these columns to dynamically change the items displayed for a traceability list.  

For example, if a data entry operator selects a particular Department, you may want the list of Machines to reflect only those machines from the selected department rather than those from all Departments.

The Traceability Priority List table (TrPriMst) is formatted as follows:

The SPC/DMS Priority List Editor sets the values for the first four columns when you create the traceability priority list.

To set values in the last three columns, use the SPC/DMS Priority List Editor to edit the traceability priority list. Click the Expand button to show more options.

In this example, the expanded list changes the Expand button to a Collapse button.

The values that you set in these last three columns will depend on the type of template logic you will use to further restrict the traceability list. The following examples show two ways of doing this.

Example 1:

In the loan processing department, two traceability fields have been set up as follows:

However, Mortgage loans are processed using forms 1033, 1034 and 1035, while Personal loans use forms 1043 and 1044.  

The template users would like for the system to work such that after choosing a Loan Type of "Mortgage", the list of available Loan Form Numbers will display only forms 1033, 1034 and 1035.  Similarly, choosing a Loan Type of "Personal" should display only the Loan Form Numbers 1043 and 1044.

To accommodate this need, the template designer created a Priority List on Loan Form Numbers for these users and then set values in the STRING30 column as follows:

The template designer then created a template that uses this extra column to display only the needed loan forms to the user, depending on which loan type was selected:

Notice that the TRACE_OPT command is not needed to set options for the Loan Form Number priority list, because the LIST_Q command actually creates the list of Loan Form Numbers that is displayed to the user.

Example 2:

Continuing with the previous example, a new form – number 1053 – has been added for processing both Mortgage loans and Personal loans.  

The template writer begins by adding this new item to the pre-defined list for Loan Form Numbers:

Next, the template writer adds the new Loan Form Number 1053 to the Priority List for these users and makes a few additional changes:

In this example, the table column STRING150 is not used.  If the number of options in STRING30 caused the value to be more than 30 characters long, however, then STRING150 would need to be used because of its greater length.

Now that the STRING30 column can contain 2 or more values, the SQL query must use "STRING30 LIKE... " instead of "STRING30 = ...".  

To guard against finding a substring of a longer value (e.g., asking for STRING30 LIKE '% MORTGAGE%' and finding both "MORTGAGE" and "MORTGAGE RE-FINANCE"), the template designer has placed the desired values between semicolons.  This ensures that a query for STRING30 LIKE '%;MORTGAGE;%' finds only the desired value (";MORTGAGE;").

The template designer has now modified the template as follows:

Notice that the TRACE_OPT command is not needed to set options for the Loan Form Number priority list, because the LIST_Q command actually creates the list of Loan Form Numbers that is displayed to the user.