Configuration Validation

When you set up a business configuration for a new tenant, multiple validation checks are performed to ensure that there are no configuration errors.

If a validation error is reported, then the business configuration is not updated. The simple validation checks include the following:

JSON format
The set of fields that must be present in the different sections.
Format of the specified URIs.

The following sections of the business configuration have a more complicated set of validation rules:

Vertical Configuration

This section contains the Reltio verticals L1 and L2. All existing customers using Reltio verticals must update to the new Reltio verticals as the legacy verticals L1 and L2 had validation errors. The new verticals without any errors are as follows:

L1 - configuration/_vertical/reltio-core-2020-1
L2 - configuration/_vertical/reltio-life-sciences-2020-1

Customers who are not using Reltio verticals, must create new verticals and migrate their tenants from the old verticals to the new ones.

Match Rules

All classes (matchServiceClass, matchTokenClasses, comparatorClasses, cleanseAdapter, and documentComparator) mentioned in the match rule must be valid. For more information, see Match Rules.

All attributes mentioned in the rule must be presented in the EntityType attributes or defined at a multi-operand or specify a sourceType URI (for example, configuration/entityTypes/HCP/attributes/FirstName, configuration/entityTypes/HCP/attributes/MultiGroup1, or configuration/sources).

Cleanse Functions

All functions that are specified under the cleanseConfig section must be defined in the physical configuration of the tenant.

For some cleanse functions, additional validations are performed, such as:

S3 file: validates that the file exists and that AWS key has the required privileges
HTTP cleanse function type: checks that there is a connectivity to the 'URL';
Loqate: checks if the specified input/output attributes exist.

Life Cycle Actions (LCA)

The following checks are performed:

Checks if the specified hooks exist.
Verifies that all the actions are registered in the LCA/AWS Lambda services and have a proper Binary/Non Binary format. For more information, see LCA Configuration.

Accelerate the Value of Data

Configuration Validation

Footer