Reltio Connect

We are currently working on a new Reltio implementation and would greatly appreciate your help and suggestions on the following topics:

1. Best Practices for Version Controlling:

Could anyone share their experience or provide recommendations on the best practices for version controlling in Reltio? Specifically, we are looking for guidance on how to manage and track changes effectively, particularly when multiple environments are involved.

2. Best Practices for Migrating Changes Across Environments:

In our implementation, we are manually moving changes across different environments at the moment. For example:

• Configuration Changes: We merge changes into the respective environment config file and then upload them using the console.
• Mapping Changes: These are created manually in each environment.

We are looking for suggestions or best practices to streamline this process, especially since we are working with several types of changes that need to be migrated across different environments. These include:

• Data Mapping
• Configuration Changes (e.g., model, match, merge, survivorship, etc.)
• UI Changes
• RIH (Reltio Integration Hub) Changes

If there are any existing documents or resources on these topics, please kindly route me to them. Your help would be greatly appreciated!

Thank you in advance!

Best regards,

------------------------------
Rushyendar Akula
Datasys Inc
Concord NC
------------------------------

Hi Akula,

Kindly organize them in your organization's repository by creating separate folders for DEV, Test, and Prod. Ensure that you manage the versions accordingly.  Automate these changes if necessary.

------------------------------
Radhakrishnan Ramalingam Architect
Majix Solutions Inc
San Ramon, CA
------------------------------

Original Message:
Sent: 02-10-2025 09:48
From: Rushyendar Akula
Subject: Request for Best Practices on Version Control and Migrating Changes in Reltio Implementation

We are currently working on a new Reltio implementation and would greatly appreciate your help and suggestions on the following topics:

1. Best Practices for Version Controlling:

Could anyone share their experience or provide recommendations on the best practices for version controlling in Reltio? Specifically, we are looking for guidance on how to manage and track changes effectively, particularly when multiple environments are involved.

2. Best Practices for Migrating Changes Across Environments:

In our implementation, we are manually moving changes across different environments at the moment. For example:

• Configuration Changes: We merge changes into the respective environment config file and then upload them using the console.
• Mapping Changes: These are created manually in each environment.

We are looking for suggestions or best practices to streamline this process, especially since we are working with several types of changes that need to be migrated across different environments. These include:

• Data Mapping
• Configuration Changes (e.g., model, match, merge, survivorship, etc.)
• UI Changes
• RIH (Reltio Integration Hub) Changes

If there are any existing documents or resources on these topics, please kindly route me to them. Your help would be greatly appreciated!

Thank you in advance!

Best regards,

------------------------------
Rushyendar Akula
Datasys Inc
Concord NC
------------------------------

We have done this for a couple of clients - We have built a config file with variables (RDM Tenant ID, auto IDs etc) for each environment further integrate it with bitbucket/ any CI CD tools to post Reltio configurations base file -> built a pipeline to post the configuration as you merge changes in branches dedicated to environment.

------------------------------
Ashish Rawat
Sr. Manager
Fresh Gravity
Bangalore
------------------------------

Original Message:
Sent: 02-10-2025 09:48
From: Rushyendar Akula
Subject: Request for Best Practices on Version Control and Migrating Changes in Reltio Implementation

We are currently working on a new Reltio implementation and would greatly appreciate your help and suggestions on the following topics:

1. Best Practices for Version Controlling:

Could anyone share their experience or provide recommendations on the best practices for version controlling in Reltio? Specifically, we are looking for guidance on how to manage and track changes effectively, particularly when multiple environments are involved.

2. Best Practices for Migrating Changes Across Environments:

In our implementation, we are manually moving changes across different environments at the moment. For example:

• Configuration Changes: We merge changes into the respective environment config file and then upload them using the console.
• Mapping Changes: These are created manually in each environment.

We are looking for suggestions or best practices to streamline this process, especially since we are working with several types of changes that need to be migrated across different environments. These include:

• Data Mapping
• Configuration Changes (e.g., model, match, merge, survivorship, etc.)
• UI Changes
• RIH (Reltio Integration Hub) Changes

If there are any existing documents or resources on these topics, please kindly route me to them. Your help would be greatly appreciated!

Thank you in advance!

Best regards,

------------------------------
Rushyendar Akula
Datasys Inc
Concord NC
------------------------------