Plugin Views Creation

There is an inbound and outbound plugin. The inbound plugin is to load data from snowflake canonical schema into Reltio, and the outbound plugin to extract the ov data from Reltio into a S3 bucket. These plugins need a Reltio connection string and Reltio extract to be setup with version v2 with gzip compression. see Configure Connection, step 5 to create reltio connection.

Reltio Setup

Change Reltio extract compression to gzip

To change the Reltio compression to gzip, create a Reltio technical task ticket with following information.

Replace the <Placeholders> with the appropiate information

Subject: <Team\Client>-<Reltio user name>: Request to change the fileCompression to GZIP in physical config

Description:

Request to change the fileCompression to GZIP instead of Zip in physical config

Tenant detail:

<Reltio tenant URL>

Change Reltio extract version to v2

To change Reltio extract version, execute following API:

[POST] {{serviceURL}}/jobs/settings/{{tenantID}}/exportVersion

Body:

{

"value": "v2"

}

Create Plugin Dataload Views

Relto inbound plugin post data into Reltio from the snowflake canonical schema. Snowflake views (dataload view) are used to select data in a Reltio json format from the canonical schema tables to post into Reltio. The canonical tables represent the Reltio entities/relations to load and it'snested attributes. For example, C_CUSTOMER table for Reltio HCP\HCO entity and C_SPECIALTY for the specialty nested attributes of the HCP and HCO.

The main canonical tables have following columns to track the Reltio load status:

  • LOAD_STATUS: Possible values: 'PENDING_PLUGIN' and 'SUCCESSFUL'. PENDING_PLUGIN status indicates the record has been updated and needs to be posted into Reltio. SUCCESSFUL status indicates that the record has been posted into Reltio without errors.

  • MDM_URI: Reltio entity\relation uri for the last time the record was posted successfully.

  • PLUGIN_PROCESS_DT: Time of the last time records was attempted to be pushed into Reltio.

  • LOAD_DETAILS: If Reltio update is successfully same as the MDM uri column, if update fails, error received from Reltio.

The dataload views only select data with 'PENDING_PLUGIN' status. These views are created once on every release or when the views are customized to match the modified canonical schema. The baseline views are created when running the data pipeline task. The data pipeline tasks are created from templates. There is a single view for each entity to load in Reltio (example. VIEW_RELTIO_HCP to load data into HCP entity). Each view joins other views to include nested attributes (example. VIEW_RELTIO_IDENTIFIERS for identifier nested attribute). Dataload views are named as VIEW_RELTIO_[CANONICAL_TABLE_SUFFIX]. For example: dataload view for C_SPECIALTY is VIEW_RELTIO_SPECIALTY.

Templates

MDM_Load_Refresh_Reltio_Views_Customer_Master_<version>.json

View to load customer data into Reltio: HCP, HCO, Account, Affiliations, and Merges.

MDM_Load_Refresh_Reltio_Views_RDM_<version>.json

View to load RDM codes into RDM tenant.

MDM_Load_Refresh_Reltio_Views_Product_Master_<Version>.json

View to load product data into Reltio: Medicinal Product and Relations. Product_HierarchyType is added to this task group with new plugin view (VIEW_RELTIO_PRODUCT_HIERTYPE) which can load RM hierarchical data from canonical to RMHierarchyList reltio nested attribute. Also a new attribute is added under relation plugin view (VIEW_PM_RELTIO_RELATIONS) for RMHierarchyType reltio attribute.