Validation - SmartPlant Foundation - IM Update 46 - Help - Hexagon

SmartPlant Foundation Help

Language
English
Product
SmartPlant Foundation
Search by Category
Help
SmartPlant Foundation / SDx Version
10
SmartPlant Markup Plus Version
10.0 (2019)
Smart Review Version
2020 (15.0)

Validation of data is performed on the data that is imported into the staging area. Validation ensures the imported objects meet the criteria mentioned in the selected rule sets.

Validation rules verify that the data in an imported record meets the data standards specified for the target system. Each validation rule contains a formula that evaluates the imported data and verifies that it matches the existing criteria and hierarchy found in the target system database. Each validation rule includes an error message that is recorded in a validation report when the rule returns an invalid value.

All the validation rules that will be used in a job are grouped into a set. You can create a validation rule set, and then create the individual rules that will make up that set.

When any validation rule is deleted that contains class definitions, relationship definitions, or property definitions no longer used by Data Validator, those schema items are automatically removed from the database.

In the following graphic, you’ll see the schema validation and the business/data logic rules validate the imported data in the staging database. Some of the rules also check the target system schema. The validation report displays errors found in the imported data.

SHARED Tip You can configure Data Validator to automatically generate validation rules when you create your import mapping.

Validation rules and their descriptions

The following table lists all the validation rules and their descriptions delivered with Data Validator.

Rule name

Description

Check Claimed to Sub Configuration

Checks to see if a plant-level item has been claimed to the project.

Check Duplicate Issue Dates

Checks to see if there are revisions with duplicate issue dates for the same master document.

Check File Exists

Checks to see if a file exists in the specified path and that security has been set to configure access permissions.

Check File Exists for Document Revision

Checks to see if any file is attached to the document revision if the document revision is not a planned revision.

Check For Cyclic Relationships

Checks to determine if the same object is set on both End 1 and End 2 of a relationship definition.

Check Is Claimable

Checks to see if the data object is claimable into the SmartPlant Foundation collaboration project and prevents the object from being loaded.

Check Is Revisable

Checks to see if the document is revisable to the SmartPlant Foundation collaboration project and prevents the document revision from being loaded.

Check Object Exists

Checks to see if the object exists in the target system already.

Check Parallel Claim

Checks to see if the item is claimed to a parallel project under the same plant.

Check Revised to Sub Config

Checks to see if a plant-level document has been revised to the project.

Check Revised to Parallel Config

Checks to see if the document item has been revised to a parallel project under the same plant.

Check Properties Against Schema

Checks to see if the target property definitions are valid for the target object type and if the values are valid for this property, including whether required values are present.

Check Relationship Exists

Checks to see if the relationship exists in the target system.

Check Unique Key

Checks to see if a specific unique key already exists elsewhere in the system and cannot be implicitly claimed. This check runs only on the target system and detects duplicates in the source files.

Check Value and UOM

Checks to see if the UOM of the object property is the same as the UOM configured in the target system. It also checks to see if the object property value is defined within a specified range of minimum and maximum values.

Compare All Property Values For Object

Checks to see if all the staging system object property values are the same as the target system property values.

Compare Value

Checks to see if the staging system property value is the same as the target system property value.

Date Time

Checks to see if an object property must validate against some date and time, YMD, or DMY.

Double

Checks to see if an object property value has a minimum and a maximum value.

Integer

Checks to see if an object property value is defined within a specified range by a minimum and maximum value.

Regular Expression

Checks to see if an object property value adheres to a specified pattern.

Staging System Cardinality

Checks for the cardinalities between the related objects.

String Does Not Start With

Checks to see that the value does not start with the given value.

String Length

Checks to see if the length of an object property is within a specified minimum and maximum limit or adheres to a specified pattern.

String Not Equal To

Checks to see that the value is not equal to the given value.

Target System Cardinality

Checks for the minimum and maximum cardinality values between related objects from the target system.

Configure the automatic generation of validation rules

When you create your import mappings from the target system, you can automatically generate validation rules that are set on the import definition. By selecting this option, the system determines which rules it will run for each action, saving configuration time. You can configure which rules are automatically generated for each action in the Data Validator system options. The actions and rules are configurable.