Value validation settings ensure that the values added for an attribute or reference meet the business requirements. For example, allowing only numeric characters or using inheritance to ensure consistent data.
Recommended Use
-
A business condition is required when a value should be validated dynamically, that is, based on a change on another attribute on the node.
-
If a value should always be validated in the same way, use the Web UI designer or other validation options to set the value requirement permanently. To create custom validation messages without using business rules, refer to the Custom Validation Error Messages topic in the System Setup documentation (here) or the Reference Help Text in the Web UI topic (here).
Value validation can be set in the Web UI as defined in the linked topics below.
Attributes
Validation can be set on attribute objects as defined in:
-
Validation Rules topic in the System Setup documentation (here)
-
List of Values (LOVs) topic in the System Setup documentation (here)
-
Specification Attributes topic in the System Setup documentation (here)
-
Description Attributes topic in the System Setup documentation (here)
-
Single and Multi-valued Attributes topic in the System Setup documentation (here)
Business Conditions
Validation can be set dynamically based on other information on the node via business conditions as defined in:
-
Configuring Business Conditions in Web UI topic (here)
-
Data Issues Report Bind topic (for use with JavaScript business rules) in the Resource Materials online help documentation (here)
References
Validation can be set on reference type objects as defined in:
-
Reference and Link Types topic in the System Setup documentation (here)
-
Custom Reference Target Search topic (here)
Use of Business Conditions in the Web UI versus in Workflows
By adding business conditions to transitions in workflows, it is possible to prevent users from submitting. When a user tries to submit and submission is prevented by a business condition in the workflow, the user is presented with errors and warnings from the business condition, which the user can dismiss in the Notification Panel. For more information, refer to the Mandatory Attributes and References in Workflows topic in the Workflows documentation and the Workflow Mandatory Attributes in Web UI topic in the Web User Interfaces documentation.
It is recommended to apply business conditions to workflows due to their governance capabilities. By also adding business conditions to the Web UI configuration, errors and warnings can be presented to the user as screens are loaded, and these business conditions are reevaluated in real time as the user modifies data. For details, refer to the Configuring Business Conditions in Web UI topic in the Web User Interfaces documentation.
Solution Enablement Use Cases
For additional considerations when configuring data validation to support a customer and supplier MDM environment, refer to the Controlling Data Validity topic in the Solution Enablement: Customer & Supplier MDM documentation.