Create a String Set Matches Normalizer

The string set matches normalizer compares a value in a MATRIXX Data Container (MDC) field with a value in another MDC field. Both fields can either be a single string/phone number or a list/array of strings/phone numbers. The comparison could be an exact match, prefix match, or suffix match. If one field is an array/list and one field is a single value, then the system checks if anything in the list/array matches the single value (using the match mode). If a match is found, then the normalizer evaluates to true. It does not matter which field is the list/array and which is the single value. If both are arrays/lists, then the system checks if a value in one list/array matches any value in the other list/array.

Before you begin

My MATRIXX must contain the normalizer template that you want to use for this normalizer that implements the String Set Matches normalization algorithm.

About this task

Configure this normalizer to match a string or list of strings exactly, compare the characters in the string(s) from the beginning of the string (prefix match), or compare the characters in the string(s) from the end of the string (suffix match).

Procedure

  1. In Normalizers, click New Normalizer.
  2. In Create New Normalizer:
    1. In Name, enter a unique name.
    2. (Optional) In Description, enter descriptive information about the item.
    3. (Optional) In External ID, enter any alphanumeric character to serve as a unique ID on this pricing object. The external ID can be used for any reason that is meaningful to your implementation of MATRIXX Engine. External IDs are saved to the pricing configuration file and loaded into the Pricing database.
    4. From the Normalizer Template list, select the name of the normalizer template that implements the normalization algorithm you want to use for this normalizer.
    5. Click Create.
  3. In Start Date/Time, use the date picker to select the date on which the object becomes active in the Pricing database and is first available for use, or enter the date in the format YYYY-MM-DD. Optionally, enter a time for when the object becomes active. The default start date/time is 2000–01–01 00:00:00. If applicable, the range in which the start date/time must fall is listed. For example:
    • Select a date on or before 2021–12–01.
    • Select a date on or after 2020–01–27.
    • Select a date between 2000–01–02 and 2021–10–04.
    Note: If you are creating a new revision of this object, the start date/time must be after the start date/time of the preceding revision and before the start date/time of the next revision. If you are making a copy of this object, the start date/time is not copied. The new object is the first revision, so it has the default start date/time of 2000–01–01 00:00:00.
  4. In Value If Field Not Present, select a parameter value to use when the field value is not set at the time of rating.
  5. In Match Mode, select the mode to use for comparing the MDC field values from the following options:
    • Exact — The field values must match exactly. This is the default option.
    • Prefix — Perform case sensitive matching of the beginning of the string(s) in the first field with the prefix strings in the second field.
    • Suffix — Perform case sensitive matching of the end of the string(s) in the first field with the suffix strings in the second field.
    • Prefix Ignore Case — Perform case insensitive matching of the beginning of the string(s) in the first field with the prefix strings in the second field.
    • Suffix Ignore Case — Perform case insensitive matching of the end of the string(s) in the first field with the suffix strings in the second field.

    If the first field contains a set of strings and an exact/prefix/suffix match is selected, the system loops through each item in that list to find an exact/prefix/suffix match in the set of strings defined in the second field.

  6. (Optional) Click or hover over the Rows menu icon and select Validate to check the normalizer values for errors.
    Validation checks for errors caused by duplicate rows, gaps in ranges, overlapping ranges, and any other missing or invalid configurations. To perform the validation, My MATRIXX sorts the rows in the rate table according to the first parameter value.