Configuration Concepts

In Reltio, where your business data is stored in tenants, you can configure your tenant models by configuring its metadata and the UI interface.

Typically, metadata is configured by editing an existing JSON file, such as those which are provided with each of Reltio’s Solution Accelerators. The customized JSON file is applied to the tenant using the Set Configuration API command. Anyone with knowledge of JSON and REST can perform this exercise. The metadata configuration can be performed with the Data Modeler. The Metadata Configuration defines all aspects of the model being used by the intended application including but not limited to entities, attributes, relationships, and interactions.

The UI configuration defines the various screens the user will experience, the facets on those screens, and how each facet relates to the underlying entities, relationships, and other objects defined in the metadata configuration. The UI configuration for the entity Profile View can be edited using the UI Modeler. For other parts of the UI, you must contact your Reltio representative to arrange to have Reltio personnel modify the UI.

For more information about the Configuration API, refer to Configuration API.

Metadata Configuration

The configuration of all tenant object types held in the tenant configuration and utilized by your business.

Metadata configuration refers to the configuration of all object types held in the tenant configuration and utilized by your business. Examples include entities, relationships, interactions, source declarations, lookups, entity references, linkages to Reference Data Management, entity and relationship attributes, cleanse configurations, validation, and more.

UI Configuration

Information about portions of the UI that can be configured using the UI Modeler within the Console.

Some portions of the UI can be configured using the UI Modeler within the Console. For other aspects of UI configuration, contact your Reltio Customer Success Manager. This topic is discussed in detail in Configuring the Hub.

Applying an L3 to a Tenant

The L3 layer configuration creates the metadata configuration for a tenant.

The Data Modeler within the Console will enable you to retrieve, edit, and apply a modified L3 to your tenant. You can also use the Get Configuration and Set Configuration API calls available in the Reltio API.

When you execute the PUT command defined in the Set Configuration API, the L3 you have crafted undergoes a validity check and if it passes, is applied to your tenant, and it overwrites the existing L3 configuration. If it the validity check fails an error is returned to the client. For details about L3 validation errors, refer to L3 Validation Errors.

Important: When the L3 is applied to the tenant, the inheritance is executed (assuming your L3 includes a reference to an L2 or the L1 layer) and the resulting consolidated configuration (L1+L2+L3) becomes, and is known as, the “tenant configuration” or “metadata configuration”. It is this consolidated tenant configuration that is used by the tenant.