Tenant data configuration

Learn about the Reltio way of storing your business data in object types called tenants.

In Reltio, a tenant is like an instance of the software. You can configure each of your tenant models by configuring that tenant’s metadata and how it displays in the user interface (UI).

Tenant and metadata configuration controls the behavior of the tenant, so when you modify the configuration, you modify the behavior. The metadata functions like a parameter file that the platform reads when it executes commands. This configuration also controls how the system:
  • Represents the data—the entities, attributes, and other data types

  • Controls how the data matches the data—match rules

  • Defines all aspects of the model being used by the intended application, including but not limited to entities, attributes, relationships, and interactions

What does the metadata configuration include?

Typically, you configure the metadata by editing an existing JSON file. Reltio provides examples with each of the Reltio Solution Accelerators. If you have knowledge of JSON and REST, you can use the examples according to need. The system then applies the customized JSON file to the tenant using the Set Configuration API command. You can also perform the metadata configuration with the Reltio Data Modeler.

In the UI Modeler, you can configure some parts of the UI. That configuration defines the:
  • Various screens you see

  • Facets on those screens

  • How each facet relates to the underlying entities, relationships, and other objects definitions

What are some configuration exceptions?

The Profile View entity. The UI Modeler can edit this configuration. To make modifications to the Profile View entity or other parts of the UI, contact your Reltio representative to work with you.

To learn more about configuring entities with the Configuration API, see Configuration API.