A basic rule association is an association between a business entity field and a simple condition-based rule. When you create basic rule associations, you configure conditions, which are predefined functions, such as Regular Match and Concatenate. Use basic rule associations for business entities involved in high concurrent cleansing transactions.
For example, Smith Store wants to master data from a newly acquired business. Smith Store wants to combine the first name and last name of each customer to generate the full name to print on receipts. Smith Store can associate a basic rule with the Full Name field and concatenate the first name and last name values.
You can also create basic rule associations to validate input fields that are empty. These rule associations aren't applicable if configured for required fields.
When you configure basic rule associations, you configure conditions that transform or validate field values. To set the conditions, you can use predefined validation functions or predefined transformation functions. A validation function validates whether data matches the specified condition. A transformation function transforms source data.
The following table describes the validation functions that you can use:
Function
Description
Maximum Length
Validates whether the length of a string is less than or equal to the specified length.
Minimum Length
Validates whether the length of a string is greater than or equal to the specified length.
Starts With
Validates whether a string starts with the specified string.
Ends With
Validates whether a string ends with the specified string.
No Spaces
Validates whether a string does not contain spaces.
Contains
Validates whether a value contains the specified string in the exact order.
Does Not Contain
Validates whether a value does not contain the specified string in the exact order.
Allowed Characters
Validates whether a value contains the specified allowed characters.
Not Allowed Characters
Validates whether a value contains the specified characters that are not allowed.
Regular Match
Validates whether a string matches the specified regular expression pattern.
Business 360 Console follows the ECMA-262 standard for regular expression.
External Validation
Validates the field data based on an external validation rule that is associated to a Cloud Application Integration process. The Cloud Application Integration process uses external APIs to validate the data.
Basic rule associations with external validation functions validate the field values of records that you create or update in real time through the user interface and REST API.
For more information about creating a process, see Cloud Application Integration.
Date Range
Validates whether a date is in between two specified dates.
Greater Than Date
Validates whether a date is greater than the specified date.
Lesser Than Date
Validates whether a date is less than the specified date.
No Future Date
Validates whether a date is not a future date.
Maximum Decimal Scale
Validates whether the number of decimal places is less than or equal to the specified value.
Minimum Value
Validates whether a numerical value is greater than or equal to the specified value.
Maximum Value
Validates whether a numerical value is less than or equal to the specified value.
Maximum Precision
Validates whether the total number of digits in a decimal number is less than or equal to the specified value.
The following table describes the transformation functions that you can use:
Function
Description
Concatenate
Concatenates two or more strings.
Concatenate With Spaces
Concatenates two or more strings with spaces in between.
Uppercase
Converts lowercase string characters to uppercase.
Lowercase
Converts uppercase string characters to lowercase.
Title Case
Capitalizes the first character in each word of a string and converts all other characters to lowercase.
Left Trim
Removes spaces from the beginning of a string.
Right Trim
Removes spaces at the end of a string.
Replace
Replaces a character set in a string with another character set.
Rules and guidelines for basic rule associations
Consider the following rules and guidelines to create basic rule associations:
•Basic rule associations with a maximum or minimum value consider only the first 16 digits of numeric values.
For example, if you specify 20 as the maximum value and the input is 20.09123456904589098743, the rule considers 20.09123456904589 and ignores the remaining digits.
•You can't create basic rule associations for boolean fields and dynamic fields.
•You can't create multiple basic rule associations for a field with the same validation or transformation function.
•When users enter value for a field and switch to a different field in a business application, basic rule associations are run.
•A basic rule association with an external validation function must use a validation rule associated with the Cloud Application Integration process. The validation rule must contain param<n> as the input field name, where n is the position of the input field. Otherwise, the rule association fails.
For example, when you configure an external validation function for fields, such as First Name, Middle Name, and Last Name, the validation rule must contain param1, param2, and param3 as the input field names.
•When a field with an external validation function is updated in a business application, MDM SaaS sends the value of the field as the value of param1. For example, if the value of the First Name field with a basic rule association that uses an external validation function is updated, MDM SaaS sends the updated value as the value of param1.
•When you configure basic rule associations with functions, such as maximum length, minimum length, maximum precision, and maximum decimal scale, ensure that fields don't contain null or negative values.
If fields contain null or negative values, MDM SaaS doesn't apply rule associations to these fields.
•When you configure basic rule associations with functions, such as maximum value, minimum value, data range, and regular match, and select business entity fields for validation, ensure that these fields aren't null.
If inputs fields are null, MDM SaaS doesn't apply basic rule associations to these fields.
•Basic rule associations run sequentially in the order they are listed on the Data Quality tab of a business entity.