Required Updates for Existing Trillium Projects with Spain Process Flow - trillium_quality - trillium_discovery - Latest

Trillium DQ Release Notes

Product type
Software
Portfolio
Verify
Product family
Trillium™ software
Product
Trillium™ software > Trillium™ Quality
Trillium™ software > Trillium™ Discovery
Version
Latest
ft:locale
en-US
Product name
Trillium Quality and Discovery
ft:title
Trillium DQ Release Notes
Copyright
2024
First publish date
2008
ft:lastEdition
2026-01-30
ft:lastPublication
2026-01-30T16:16:09.403000
L1_Product_Gateway
Verify
L2_Product_Segment
Data Quality
L3_Product_Brand
Precisely Trillium
L4_Investment_Segment
Legacy DQ
Core Data Quality
L5_Product_Group
Legacy DQ - Application
Data Quality - Application
L6_Product_Name
Trillium Quality
Trillium Discovery
Existing projects requiring these updates:
  • Projects exported to a project definition file.
  • Projects migrated from a previous version.
  • Projects exported for batch processing.
  • Projects exported for real-time processing.

Project updates can be made using any one of the following methods:

  1. Import an existing project that includes a Spain process flow into the Control Center.

    Updates for the following Spain processes included in a project (Note: not all processes are included for all projects):
    • Customer Data Parser

      Apply the updated Standard Definitions ESCDPRUL file containing new street types, city aliases, and pattern updates by running Parser Customization from the Parser Tuner.

    • Transformer Data Reconstruction (now required for Geocoder)

      Updates for the Output Conditionals section:

      Replace the Output Conditional line:
      SET DR_STREET_NAME = TQ_GOUT_STREET_TYPE |: TQ_GOUT_STREET_NAME
      With:
      IF (TQ_GOUT_MATCH_LEVEL = "0")
          IF (TQ_GOUT_EXT_KEY_1 = "Y")
              SET DR_STREET_NAME = TQ_GOUT_STREET_NAME |: TQ_GOUT_STREET_TYPE
          ELSE
              SET DR_STREET_NAME = TQ_GOUT_STREET_TYPE |: TQ_GOUT_STREET_NAME
          ENDIF
      ELSE
          IF (TQ_GOUT_EXT_KEY_2 = "Y")
              SET DR_STREET_NAME = TQ_GOUT_STREET_NAME |: TQ_GOUT_STREET_TYPE
          ELSE
              SET DR_STREET_NAME = TQ_GOUT_STREET_TYPE |: TQ_GOUT_STREET_NAME
          ENDIF
      ENDIF
      Replace the Output Conditional lines:
      SET DR_ADDRESS = TQ_GOUT_DELIVERY_ADDRESS
      /* SET DR_ADDRESS = DR_STREET_NAME |: DR_HOUSE_NUMBER1 |: DR_HOUSE_NUMBER2
      With:
      /* SET DR_ADDRESS = TQ_GOUT_DELIVERY_ADDRESS
      SET DR_ADDRESS = DR_STREET_NAME |: DR_HOUSE_NUMBER1 |: DR_HOUSE_NUMBER2
      Note: Actual Conditional lines may vary.
      Move the Table Recode routine, SUBROUTINE(3), to run first instead of last:
      IF (ALWAYS)
          /*--------------------------------------
          /*    MAIN    routine -- run ALWAYS
          /*--------------------------------------
          /* run table recoding - moved to run 1st, so I can use the flag in subroutine 1
          RUN SUBROUTINE(3)
      
          /* Fill DR address fields
          RUN SUBROUTINE(1)
      
          /* Field Scanning + fill and case DR name fields + case DR address fields
          RUN SUBROUTINE(2)
      
          /* note: no DUAL address routine for address 2 - tqpmatch does it
      ENDIF
      Note: Actual Conditional lines may vary.
      Edit Table Recode Settings for:
      • Table File Name: es_strtyp_recode.tbl
      • Table DDL File Name: es_strtyp_recode.ddx
      • File Delimiter: Comma
      • Lookup Table Fields: STRTYP
      • Lookup Output Fields: TQ_GOUT_STREET_TYPE
      • Recode Table Fields: STRTYP_POS_AFTER
      • Recode Output Fields: TQ_GOUT_EXT_KEY_2
      Apply this update by replacing the Table Recode section with the following:
      <TABLE_RECODING>
          <ARGUMENTS>
              <ENTRY>
                  <ENTRY_ID>1</ENTRY_ID>
                  <ENTRY_DESCRIPTION>STREET_TYPE_RECODE</ENTRY_DESCRIPTION>
                  <FILE_QUALIFIER>RECODE1</FILE_QUALIFIER>
                  <TABLE_FILE_NAME>/TS_TABLES/general_resources/es_strtyp_recode.tbl</TABLE_FILE_NAME>
                  <DDL_FILE_NAME>/TS_TABLES/general_resources/es_strtyp_recode.ddx</DDL_FILE_NAME>
                  <FILE_DELIMITER>COMMA</FILE_DELIMITER>
                  <USE_QUOTES_AS_QUALIFIER></USE_QUOTES_AS_QUALIFIER>
                  <DELIMITED_FILE_COMMENT_INDICATOR></DELIMITED_FILE_COMMENT_INDICATOR>
                  <LOOKUP_PHRASE_SEPARATOR></LOOKUP_PHRASE_SEPARATOR>
                  <LOOKUP_PHRASE_CHANGE></LOOKUP_PHRASE_CHANGE>
                  <LOOKUP_POSITION></LOOKUP_POSITION>
                  <LOOKUP_TABLE_FIELDS>STRTYP</LOOKUP_TABLE_FIELDS>
                  <LOOKUP_FIELDS_CASE_SENSITIVE>N</LOOKUP_FIELDS_CASE_SENSITIVE>
                  <LOOKUP_OUTPUT_FIELDS>TQ_GOUT_STREET_TYPE</LOOKUP_OUTPUT_FIELDS>
                  <LOOKUP_OUTPUT_FIELDS_FORMAT></LOOKUP_OUTPUT_FIELDS_FORMAT>
                  <RECODE_TABLE_FIELDS>STRTYP_POS_AFTER</RECODE_TABLE_FIELDS>
                  <RECODE_TABLE_FIELDS_FORMAT></RECODE_TABLE_FIELDS_FORMAT>
                  <RECODE_OUTPUT_FIELDS>TQ_GOUT_EXT_KEY_2</RECODE_OUTPUT_FIELDS>
                  <SORT_OPTIONS></SORT_OPTIONS>
              </ENTRY>
          </ARGUMENTS>
      </TABLE_RECODING>
      Note: If directly editing the .stx file for this update, the /TS_TABLES parameter must be substituted with the correct path to the general_resources directory for the above TABLE_FILE_NAME and DDL_FILE_NAME parameters. Actual settings file lines may vary.
      Example:
      <TABLE_FILE_NAME>../../tables/general_resources/es_strtyp_recode.tbl</TABLE_FILE_NAME>
      <DDL_FILE_NAME>../../tables/general_resources/es_strtyp_recode.ddx</DDL_FILE_NAME>
    • Geocoder (optional process in project)
      Change the Geocoder Input Attributes used for Street line part 1 and Street line part 2:
      Street line, part 1: TQ_GOUT_STREET_TYPE
      Street line, part 2: TQ_GOUT_STREET_NAME
      To:
      Street line, part 1: DR_STREET_NAME
      Street line, part 2: <blank>
      Example of resulting settings:
      <ENTRY>
          <ENTRY_ID>34</ENTRY_ID>
          <INPUT_FIELD_NAME>DR_STREET_NAME</INPUT_FIELD_NAME>
          <GLOBAL_FIELD_NAME>Street</GLOBAL_FIELD_NAME>
      </ENTRY>
      Note: Actual settings file lines may vary.
      A Transformer Data Reconstruction process is now required for Geocoder processing.
    • Transformer Label Lines (optional process in project)

      Replace the occurrences in the Output Conditional section of:

      SET NEWADDRL2 = INPUT.TQ_GOUT_STREET_TYPE |: INPUT.TQ_GOUT_STREET_NAME

      With:

      SET NEWADDRL2 = UCASE(INPUT.DR_STREET_NAME)
      Where INPUT is the FILE_QUALIFIER value from the INPUT_SETTINGS settings.
      Note: Actual Conditional lines may vary.
    • Transformer Unified Output (optional process in project)

      Replace occurrences in the Output Conditional section of:

      SET NEWADDRL2 = INPUT.TQ_GOUT_STREET_TYPE |: INPUT.TQ_GOUT_STREET_NAME

      With:

      SET NEWADDRL2 = UCASE(INPUT.DR_STREET_NAME)

      Where INPUT is the FILE_QUALIFIER value from the INPUT_SETTINGS settings.

      Note: Actual Conditional lines may vary.
  2. For a project migrated from a previous version that includes a Spain process flow, edit the existing project in the Control Center and apply the updates from step 1.
  3. For a project exported for batch or real-time processing, manually change the following Spain process flow settings files.
    Updates for the following Spain processes:
    • Parser Customization

      Run Parser Customization to apply the updated Standard Definitions ESCDPRUL file containing new street types, city aliases, and pattern updates.

    • Transformer Data Reconstruction

      Manually apply the updates from the above Transformer Data Reconstruction section to the settings file, example: esdrtrans.stx

    • Geocoder

      Manually apply the updates from the above Geocoder section to the settings file, example: eslatlon.stx

    • Transformer Label Lines

      Manually apply the updates from the above Transformer Label Lines section to the settings file, example: eslabelln.stx

    • Transformer Unified Output

      Manually apply the updates from the above Transformer Unified Output section to the settings file, example: esunified.stx

  4. Create a new project with a Spain process flow and apply any customization from the existing project to the new project.

    This may simplify the update process for a project that has little or no customization as all the updates are automatically applied when creating a new project.

Existing SAP projects that include Spain will require the same changes to the processes for:
  • Parser Customization
  • Transformer Data Reconstruction
  • Geocoder

    SAP projects do not include the Transformer Label Lines and Transformer Unified Output processes.

For additional information, refer to the relevant sections of the Trillium Control Center.

Contact Precisely Support with any questions.