Add/Modify Condition dialog box
Conditions consist of one or more logical statements that evaluate the value in an input field. Use the Add Condition or Modify Condition dialog box to define the criteria to determine if a record is an exception.
The Add Condition dialog box is opened when you click Add on the Conditions tab of the Exception Monitor Options dialog box. It provides options to configure a new condition. The Modify Condition dialog box is opened when you click Modify. It allows you to edit values of the same options for an existing condition. After you have create conditions, they appear on the Conditions tab of the Exception Monitor Options dialog box.
- Predefined Conditions
- Select a predefined condition or retain <custom condition> in the drop-down menu to create a new condition. After you have created predefined or custom conditions, they will appear on the Conditions tab of the Exception Monitor Options dialog box. The icon next to the name of the condition identifies it as either a predefined condition or a custom condition. A dual-document icon
designates a predefined condition, and a single document icon 
designates a custom condition. Click the Save button to save a condition. After you save a condition, the Predefined conditions field changes to show the name of the condition rather than <custom condition>. - Name
- A name for the condition. The name can be anything you like. Since the condition name is displayed in the Data Stewardship Portal, you should use a descriptive name. For example, MatchScore<80 or FailedDPV. If you try to give a new condition a name that is identical to an existing condition but with other characters appended to the end (for example, FailedDPV and FailedDPV2), you will be asked whether you want to overwrite the existing condition as soon as you type the last character that matches its name (using our example, "V"). Respond Yes to the prompt, finish naming the condition, and when you press OK or Save, both conditions will be visible on the Exception Monitor Options dialog box. The new condition will not overwrite the existing condition unless the new name is identical.
- Assign to
- The user to whom the exception records meeting this condition are assigned. This user is referred to as the data steward. If this setting is empty, exception records from a job are automatically assigned to the user who ran the job. For an approval flow, you can configure this setting to specify a data steward other than the user who runs the job.
Condition categories
- Data domain
- (Optional) Specifies the kind of data being evaluated by the condition. This is used solely for reporting purposes to show which types of exceptions occur in your data. For example, if the condition evaluates the success or failure of address validation, the data domain could be "Address"; if the condition evaluates the success or failure of a geocoding operation, the data domain could be "Spatial", and so forth. You can specify your own data domain or select one of the predefined domains:
- Account—The condition checks a business or organization name associated with a sales account.
- Address—The condition checks address data, such as a complete mailing address or a postal code.
- Asset—The condition checks data about the property of a company, such as physical property, real estate, human resources, or other assets.
- Date—The condition checks date data.
- Email—The condition checks email data.
- Financial—The condition checks data related to currency, securities, and so forth.
- Name—The condition checks personal name data, such as a first name or last name.
- Phone—The condition checks phone number data.
- Product—The condition checks data about materials, parts, merchandise, and so forth.
- Spatial—The condition checks point, polygon, or line data which represents a defined geographic feature, such as flood plains, coastal lines, houses, sales territories, and so forth.
- SSN—The condition checks U.S. Social Security Number data.
- Uncategorized—Choose this option if you do not want to categorize this condition.
- Data quality metric
- (Optional) Specifies the metric that this condition measures. This is used solely for reporting purposes to show which types of exceptions occur in your data. For example, if the condition is designed to evaluate the record's completeness (meaning, for example, that all addresses contain postal codes) then you could specify "Completeness" as the data quality metric. You can specify your own metric or select one of the predefined metrics:
- Accuracy—The condition measures whether the data could be verified against a trusted source. For example, if an address could not be verified using data from the postal authority, it could be considered to be an exception because it is not accurate.
- Completeness—The condition measures whether data is missing essential attributes. For example, an address that is missing the postal code, or an account that is missing a contact name.
- Consistency—The condition measures whether the data is consistent between multiple systems. For example if your customer data system uses gender codes of M and F, but the data you are processing has gender codes of 0 and 1, the data could be considered to have consistency problems.
- Interpretability—The condition measures whether data is correctly parsed into a data structure that can be interpreted by another system. For example, social security numbers should contain only numeric data. If the data contains letters, such as
xxx-xx-xxxx, the data could be considered to have interpretability problems. - Recency—The condition measures whether the data is up to date. For example, if an individual moves but the address you have in your system contains the person's old address, the data could be considered to have a recency problem.
- Uncategorized—Choose this option if you do not want to categorize this condition.
- Uniqueness—The condition measures whether there is duplicate data. If the dataflow could not consolidate duplicate data, the records could be considered to be an exception.
Approval flow
- Type
- Specifies the name of an approval flow type. Approval flows define a succession of review levels through which exception records must be accepted by reviewers after they are edited by the data steward. When a condition is met, a record is associated with the approval flow specified here. The approval flow type is defined on the Management Console page. If the option is left as <undefined>, the condition will not be associated with an approval flow type, and records will be resolved by the data steward without any subsequent review.
Expression and Notification tabs
- Expressions
- List expressions defined for a condition. Expressions are logical statements that check the value of a field to determine if the record might be considered an exception. Click the Add button to add a new expression. You must add at least one expression to a condition. Expressions are evaluated in the order that they appear hear. You can click Move Up or Move Down to change the order.
- Notification
- Complete options on this tab to send a message to email addresses when this condition is met a specific number of times. A notification email includes a link to the failed records in the Data Stewardship Portal Editor, where you can manually enter the correct data. If you do not wish to set up notifications, do not configure options on this tab. To stop sending notifications to a particular email address, remove that address from the list of recipients in the Send notification to box.