All records that are added or modified are first validated against a rulebase before getting stored in the repository. The Validation feature checks for errors in every attribute. When errors are found, they are displayed next to the respective attribute field. There are two types of errors:
Fatal errors: Fatal errors are critical errors such as duplicate ID or EXT, or missing values in mandatory fields that have to be resolved before saving the record. The
Save with errors permission governs whether you can save with these errors.
Rulebase errors: Rulebase errors are about validating attributes against a rulebase. For example, you can have a rulebase constraint that can only accept a range of 20 to 60 in the Age attribute. Rulebase errors are based on a severity flag set in the rulebase. For more information on the severity flag, refer to the
TIBCO MDM Studio Rulebase Designer User’s Guide. The Save with errors permission governs whether you can save with these errors.
Before saving the record, click the
Validate button. The record is validated against a rulebase. If an error is found, it is displayed next to respective attribute field as shown in the following figure. A warning icon is displayed on the relevant tab and on the
Record ID - Record ID Extension tree header.
To get a consolidated list of all the errors in the root record, click the
Show All Errors link. All the errors are displayed on a separate screen.
Resolve all the errors, and then save the record.
Note:
When an Administrator adds or edits a record, the Administrator can confirm the record directly, without using a workflow.
If you do not have Administrator privileges, and if you add or modify a record and click the
Save button, the record will be in an unconfirmed state and the event will be in an In Progress state. In such cases, the event cannot be cancelled. You can complete the event only after you modify the record, initiate a workflow, and click the
Save and Process button.