Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added using or statements sub-section


Zen Section

The Match String

The Match value in a routing rule is arguably the most important piece of the Routing entry. Each time the status of a transaction is changed by ILLiad, the system also runs a query to cycle through any active Routing Rules and determine if any should be applied to that transaction.

The Match String is where you may set the conditions that distinguish one routing rule from another. These conditions, coupled with the other conditions specified in a routing rule, determine which transactions are impacted by the rule and which are not.

This query string should only reference the Users and Transactions, or LenderAddresses tables, unless a compound routing rule is used.

 Guidelines for the Match String:

  • Each item or course table value name in the match string must be preceded by a (u.) for the Users table, a (t.) for the Transactions table, or an (l.) for the Lender Addresses table.
  • Only single quotation marks ('), not double quotation marks (") may be used in the match string.

  • There cannot be any extra characters or spaces in the match string.

  • If you are using OR clauses in your match string, it's a good practice to surround them with parentheses.

    • For example:

      Code Block
      (t.Location like '%alpha%' or t.Location like '%beta%')
      Code Block
      (t.CallNumber like ‘%gamma%’ or t.CallNumber like ‘%omega%')

See examples for demonstrations on how to correctly write and format the match string. If a match string is not formatted correctly, the routing rule will not work.