Configuring Matching Rules

Define the parameters and matching rules that determine whether an e-mail message is a regular e-mail, or a workflow e-mail at runtime.

Prerequisites
The developer must have created an object query and added an E-mail Subscription starting point when the mobile workflow was designed.
Task

When a multiplexer, which a user configures for a Notification mailbox, retrieves e-mails from the e-mail server, the "Matching rules" are used to determine if an e-mail is a regular e-mail or a workflow e-mail. If the "matching rules" match, then the e-mail is processed as a workflow e-mail. The e-mail is processed for "Extraction rules" (this processing is not visible in SCC) to extract values from the e-mail. This determines further processing, such as calling MBO object queries, and so forth. Then, a workflow message is constructed with the necessary data of the object query result, and sent to device(s) according to the "Distribution rules" (which determine the devices to which the message should be sent).

You can configure a matching rule at one of two levels:
  • At the inbox level to route e-mails for all mobile workflows
  • At the package level to route e-mails only for a specific mobile workflow
  1. In the left navigation pane, click Workflows > WorkFlowName.
  2. In the right administration pane, click the Matching Rules tab.
  3. Configure matching rules by either:
    • Clicking Add to create a new rule, or,
    • Selecting an existing rule name and clicking Properties.
  4. In the Matching Rules dialog:
    1. Select the field in the e-mail from which the parameter value is extracted. For example, if you choose From, the parameter value is extracted from the line of the e-mail message that indicates the name of the sender of the message.
      You can also select one of the custom parameter values. When registering mobile workflow devices, an administrator can choose one of four device settings. The customer then populates the settings with whatever values they like. Custom parameters can also be set programmatically through Web services.
      Note: If you are editing properties of a rule created by a developer, you cannot modify the matching rules.
    2. Choose the type of search expression:
      • Equals – the field must exactly match the text in the label.
      • Begins with – the field must begin with the text in the label.
      • Ends with – the field must end with the text in the label.
      • Contains – the text in the label must exist somewhere in the field.
      • Regular expression – search for text that matches the pattern defined by the regular expression. You can create an expression with Boolean operators, groups, or wildcards like "?" or "*". Unwired Platform uses the Boost regular expression engine. See the Boost documentation on regular expression syntax at http://www.boost.org/doc/libs/1_40_0/libs/regex/doc/html/boost_regex/syntax.html.
    3. Configure the text to search against, or define a regular expression in the Value field.
Next
Test all new and changed rules to ensure they work as designed.