Reltio Connect

We get a lot of questions around survivorship. Some example questions would be how do I create a "Best Address", survivorship based on other attribute winner, fallback strategies (can't do in UI), other complex type scenarios that might require L3 changes. I will have @Sara Lyons help answer this commonly asked implementation question. 

#Integration
#Survivorship
#ReltioInsights​​​​

------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------

Survivorship is referring to how to define the best and most reliable value for an attribute across all of the different sources loaded into Reltio. The surviving value of an attribute is referred to as the Operational Value. Once the Operational Value for every attribute included in an entity profile is calculated, that profile will contain all of the most accurate information across all of the data sources loaded into Reltio for users in your organization to consume and use to make business decisions. When configuring Reltio, a survivorship rule needs to be defined for each attribute to determine that attribute's Operation Value. It is a very important step in your Reltio implementation to task the business users in your organization to confirm the requirements for defining survivorship rules, or 'survivorship strategy'.

As an example, say you have four sources loaded into Reltio. How do you determine the Survivorship rule for Address? The end users / business owners need to agree on what data they trust to create the Operational Value for that attribute. Questions to consider when defining the survivorship strategy include, Is there one contributing data source that is always more trusted than the rest? Is there a contributing data source that will soon be retired or deprecated that you want to make sure is NOT considered in the survivorship strategy? Do the business owners know that due to an existing process, the most recently updated Address can always be trusted as the Operational Value? It is very important for the business stakeholders of the organization to confirm these requirements for your implementation to be successful. There are different out of the box options for defining survivorship - using a trusted source, most recently updated, frequency, aggregation, oldest value, etc. All of the available survivorship strategies are documented in the Survivorship Rules section of the Reltio Documentation portal.

You should also consider a fallback strategy when defining survivorship rules to ensure the correct Operational Value is calculated. Think of a fallback strategy as a tiebreaker. For example, if your survivorship rule is defined to use the attribute from a Marketing source for calculating the Operational Value for phone number, what happens when there are two records from that Marketing source in the entity? The fallback strategy will determine which attribute in this scenario.

It is a best practice to configure Survivorship in the L3 configuration, however, there is an option to change this through the UI. It is important to remember that if you make a change to Survivorship strategy through the UI, it will propagate the change to the L3, so be cautious of using this functionality!

These are some of the key points to consider when defining requirements for your organization's survivorship strategy to ensure the most accurate and complete profile is being shared with end users and consuming applications of Reltio.

------------------------------
Sara Lyons
Technical Delivery Manager
Reltio
Chicago IL
------------------------------

Original Message:
Sent: 05-19-2021 07:20
From: Chris Detzel
Subject: What is survivorship and how can we best leverage it?

We get a lot of questions around survivorship. Some example questions would be how do I create a "Best Address", survivorship based on other attribute winner, fallback strategies (can't do in UI), other complex type scenarios that might require L3 changes. I will have @Sara Lyons help answer this commonly asked integration question. 

#Integration
#Survivorship
#ReltioInsights​​​​

------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------

Hi Sara, 

Can you clarify more on your statement:

It is important to remember that if you make a change to Survivorship strategy through the UI, it will propagate the change to the L3, so be cautious of using this functionality!


I would think you would want any UI changes to propagate to the L3 so that your changes remain in sync?   

Thank you!
Angie




------------------------------
Angela Wawrzaszek
Manager, MDM governance and Application Enablement
------------------------------

Original Message:
Sent: 05-19-2021 07:22
From: Sara Lyons
Subject: What is survivorship and how can we best leverage it?

Survivorship is referring to how to define the best and most reliable value for an attribute across all of the different sources loaded into Reltio. The surviving value of an attribute is referred to as the Operational Value. Once the Operational Value for every attribute included in an entity profile is calculated, that profile will contain all of the most accurate information across all of the data sources loaded into Reltio for users in your organization to consume and use to make business decisions. When configuring Reltio, a survivorship rule needs to be defined for each attribute to determine that attribute's Operation Value. It is a very important step in your Reltio implementation to task the business users in your organization to confirm the requirements for defining survivorship rules, or 'survivorship strategy'.

As an example, say you have four sources loaded into Reltio. How do you determine the Survivorship rule for Address? The end users / business owners need to agree on what data they trust to create the Operational Value for that attribute. Questions to consider when defining the survivorship strategy include, Is there one contributing data source that is always more trusted than the rest? Is there a contributing data source that will soon be retired or deprecated that you want to make sure is NOT considered in the survivorship strategy? Do the business owners know that due to an existing process, the most recently updated Address can always be trusted as the Operational Value? It is very important for the business stakeholders of the organization to confirm these requirements for your implementation to be successful. There are different out of the box options for defining survivorship - using a trusted source, most recently updated, frequency, aggregation, oldest value, etc. All of the available survivorship strategies are documented in the Survivorship Rules section of the Reltio Documentation portal.

You should also consider a fallback strategy when defining survivorship rules to ensure the correct Operational Value is calculated. Think of a fallback strategy as a tiebreaker. For example, if your survivorship rule is defined to use the attribute from a Marketing source for calculating the Operational Value for phone number, what happens when there are two records from that Marketing source in the entity? The fallback strategy will determine which attribute in this scenario.

It is a best practice to configure Survivorship in the L3 configuration, however, there is an option to change this through the UI. It is important to remember that if you make a change to Survivorship strategy through the UI, it will propagate the change to the L3, so be cautious of using this functionality!

These are some of the key points to consider when defining requirements for your organization's survivorship strategy to ensure the most accurate and complete profile is being shared with end users and consuming applications of Reltio.

------------------------------
Sara Lyons
Technical Delivery Manager
Reltio
Chicago IL

Original Message:
Sent: 05-19-2021 07:20
From: Chris Detzel
Subject: What is survivorship and how can we best leverage it?

We get a lot of questions around survivorship. Some example questions would be how do I create a "Best Address", survivorship based on other attribute winner, fallback strategies (can't do in UI), other complex type scenarios that might require L3 changes. I will have @Sara Lyons help answer this commonly asked integration question. 

#Integration
#Survivorship
#ReltioInsights​​​​

------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------

Hi, Angela, you are correct. We just always reiterate that fact to really drive it home in case a user is not aware that changes made in the UI will be propagated to the L3. 

Thanks!

------------------------------
Sara Lyons
Technical Delivery Manager
Reltio
Chicago IL
------------------------------

Original Message:
Sent: 05-20-2021 09:13
From: Angela Wawrzaszek
Subject: What is survivorship and how can we best leverage it?

Hi Sara, 

Can you clarify more on your statement:

It is important to remember that if you make a change to Survivorship strategy through the UI, it will propagate the change to the L3, so be cautious of using this functionality!


I would think you would want any UI changes to propagate to the L3 so that your changes remain in sync?   

Thank you!
Angie




------------------------------
Angela Wawrzaszek
Manager, MDM governance and Application Enablement

Original Message:
Sent: 05-19-2021 07:22
From: Sara Lyons
Subject: What is survivorship and how can we best leverage it?

Survivorship is referring to how to define the best and most reliable value for an attribute across all of the different sources loaded into Reltio. The surviving value of an attribute is referred to as the Operational Value. Once the Operational Value for every attribute included in an entity profile is calculated, that profile will contain all of the most accurate information across all of the data sources loaded into Reltio for users in your organization to consume and use to make business decisions. When configuring Reltio, a survivorship rule needs to be defined for each attribute to determine that attribute's Operation Value. It is a very important step in your Reltio implementation to task the business users in your organization to confirm the requirements for defining survivorship rules, or 'survivorship strategy'.

As an example, say you have four sources loaded into Reltio. How do you determine the Survivorship rule for Address? The end users / business owners need to agree on what data they trust to create the Operational Value for that attribute. Questions to consider when defining the survivorship strategy include, Is there one contributing data source that is always more trusted than the rest? Is there a contributing data source that will soon be retired or deprecated that you want to make sure is NOT considered in the survivorship strategy? Do the business owners know that due to an existing process, the most recently updated Address can always be trusted as the Operational Value? It is very important for the business stakeholders of the organization to confirm these requirements for your implementation to be successful. There are different out of the box options for defining survivorship - using a trusted source, most recently updated, frequency, aggregation, oldest value, etc. All of the available survivorship strategies are documented in the Survivorship Rules section of the Reltio Documentation portal.

You should also consider a fallback strategy when defining survivorship rules to ensure the correct Operational Value is calculated. Think of a fallback strategy as a tiebreaker. For example, if your survivorship rule is defined to use the attribute from a Marketing source for calculating the Operational Value for phone number, what happens when there are two records from that Marketing source in the entity? The fallback strategy will determine which attribute in this scenario.

It is a best practice to configure Survivorship in the L3 configuration, however, there is an option to change this through the UI. It is important to remember that if you make a change to Survivorship strategy through the UI, it will propagate the change to the L3, so be cautious of using this functionality!

These are some of the key points to consider when defining requirements for your organization's survivorship strategy to ensure the most accurate and complete profile is being shared with end users and consuming applications of Reltio.

------------------------------
Sara Lyons
Technical Delivery Manager
Reltio
Chicago IL

Original Message:
Sent: 05-19-2021 07:20
From: Chris Detzel
Subject: What is survivorship and how can we best leverage it?

We get a lot of questions around survivorship. Some example questions would be how do I create a "Best Address", survivorship based on other attribute winner, fallback strategies (can't do in UI), other complex type scenarios that might require L3 changes. I will have @Sara Lyons help answer this commonly asked integration question. 

#Integration
#Survivorship
#ReltioInsights​​​​

------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------

Its totally dependent on the business requirement.. We have come across two scenarios
1. Customer wants to retain the source provided address information in BO level, if Loqate doesn't provide it
2. Customer totally trust on Loqate provided values.
You can achieve these scenarios through "fallbackUsingCriteria" option by setting it as "MORE_THAN_ONE" or "ZERO_OR_MORE_THAN_ONE"

Normally we set "SRC_SYS" survivorship strategy for AddressLine1 with "ReltioCleanser" has highest priority. 
Then other attributes like City, State, Country, Zip, SubAdministrativeArea would be dependent on AddressLine1 value through "OtherAttributeWinnerCrosswalk" strategy. 
Verification specific attributes such as AVC, VerificationStatus and VerificationStatusDetails would have "LUD" as survivorship strategy.

Sample Survivorship group for Location entity:-

{
"survivorshipGroups": [
{
"uri": "configuration/entityTypes/Location/survivorshipGroups/default",
"default": true,
"mapping": [
{
"attribute": "configuration/entityTypes/Location/attributes/AddressLine1",
"sourcesUriOrder": [
"configuration/sources/ReltioCleanser",
"configuration/sources/Reltio",
"configuration/sources/SOURCE_ABC"
],
"fallbackStrategies": [
{
"attribute": "configuration/entityTypes/Location/attributes/AddressLine1",
"survivorshipStrategy": "LUD"
}
],
"survivorshipStrategy": "SRC_SYS"
},
{
"attribute": "configuration/entityTypes/Location/attributes/AddressLine2",
"primaryAttributeUri": "configuration/entityTypes/Location/attributes/AddressLine1",
"fallbackStrategies": [
{
"attribute": "configuration/entityTypes/Location/attributes/AddressLine2",
"survivorshipStrategy": "LUD"
}
],
"fallbackUsingCriteria": "MORE_THAN_ONE",
"survivorshipStrategy": "OtherAttributeWinnerCrosswalk"
},
{
"attribute": "configuration/entityTypes/Location/attributes/City",
"primaryAttributeUri": "configuration/entityTypes/Location/attributes/AddressLine1",
"fallbackStrategies": [
{
"attribute": "configuration/entityTypes/Location/attributes/City",
"survivorshipStrategy": "LUD"
}
],
"fallbackUsingCriteria": "MORE_THAN_ONE",
"survivorshipStrategy": "OtherAttributeWinnerCrosswalk"
},
{
"attribute": "configuration/entityTypes/Location/attributes/State",
"survivorshipStrategy": "CleanserWinsStrategy"
},
{
"attribute": "configuration/entityTypes/Location/attributes/Country",
"primaryAttributeUri": "configuration/entityTypes/Location/attributes/AddressLine1",
"fallbackStrategies": [
{
"attribute": "configuration/entityTypes/Location/attributes/Country",
"survivorshipStrategy": "LUD"
}
],
"fallbackUsingCriteria": "MORE_THAN_ONE",
"survivorshipStrategy": "OtherAttributeWinnerCrosswalk"
},
{
"attribute": "configuration/entityTypes/Location/attributes/Zip",
"primaryAttributeUri": "configuration/entityTypes/Location/attributes/AddressLine1",
"fallbackStrategies": [
{
"attribute": "configuration/entityTypes/Location/attributes/Zip",
"survivorshipStrategy": "LUD"
}
],
"fallbackUsingCriteria": "MORE_THAN_ONE",
"survivorshipStrategy": "OtherAttributeWinnerCrosswalk"
},
{
"attribute": "configuration/entityTypes/Location/attributes/StateProvince",
"primaryAttributeUri": "configuration/entityTypes/Location/attributes/AddressLine1",
"fallbackStrategies": [
{
"attribute": "configuration/entityTypes/Location/attributes/StateProvince",
"survivorshipStrategy": "LUD"
}
],
"fallbackUsingCriteria": "MORE_THAN_ONE",
"survivorshipStrategy": "OtherAttributeWinnerCrosswalk"
},
{
"attribute": "configuration/entityTypes/Location/attributes/GeoLocation",
"primaryAttributeUri": "configuration/entityTypes/Location/attributes/AddressLine1",
"fallbackStrategies": [
{
"attribute": "configuration/entityTypes/Location/attributes/GeoLocation",
"survivorshipStrategy": "LUD"
}
],
"fallbackUsingCriteria": "MORE_THAN_ONE",
"survivorshipStrategy": "OtherAttributeWinnerCrosswalk"
},
{
"attribute": "configuration/entityTypes/Location/attributes/SubAdministrativeArea",
"primaryAttributeUri": "configuration/entityTypes/Location/attributes/AddressLine1",
"fallbackStrategies": [
{
"attribute": "configuration/entityTypes/Location/attributes/SubAdministrativeArea",
"survivorshipStrategy": "LUD"
}
],
"fallbackUsingCriteria": "MORE_THAN_ONE",
"survivorshipStrategy": "OtherAttributeWinnerCrosswalk"
},
{
"attribute": "configuration/entityTypes/Location/attributes/VerificationStatus",
"survivorshipStrategy": "LUD"
},
{
"attribute": "configuration/entityTypes/Location/attributes/VerificationStatusDetails",
"survivorshipStrategy": "LUD"
},
{
"attribute": "configuration/entityTypes/Location/attributes/AVC",
"survivorshipStrategy": "LUD"
}
]
}
]
}​

------------------------------
Gautam Samantroy
Capgemini
Bengaluru AK
------------------------------

Original Message:
Sent: 05-20-2021 11:23
From: Sara Lyons
Subject: What is survivorship and how can we best leverage it?

Hi, Angela, you are correct. We just always reiterate that fact to really drive it home in case a user is not aware that changes made in the UI will be propagated to the L3. 

Thanks!

------------------------------
Sara Lyons
Technical Delivery Manager
Reltio
Chicago IL

Original Message:
Sent: 05-20-2021 09:13
From: Angela Wawrzaszek
Subject: What is survivorship and how can we best leverage it?

Hi Sara, 

Can you clarify more on your statement:

It is important to remember that if you make a change to Survivorship strategy through the UI, it will propagate the change to the L3, so be cautious of using this functionality!


I would think you would want any UI changes to propagate to the L3 so that your changes remain in sync?   

Thank you!
Angie




------------------------------
Angela Wawrzaszek
Manager, MDM governance and Application Enablement

Original Message:
Sent: 05-19-2021 07:22
From: Sara Lyons
Subject: What is survivorship and how can we best leverage it?

Survivorship is referring to how to define the best and most reliable value for an attribute across all of the different sources loaded into Reltio. The surviving value of an attribute is referred to as the Operational Value. Once the Operational Value for every attribute included in an entity profile is calculated, that profile will contain all of the most accurate information across all of the data sources loaded into Reltio for users in your organization to consume and use to make business decisions. When configuring Reltio, a survivorship rule needs to be defined for each attribute to determine that attribute's Operation Value. It is a very important step in your Reltio implementation to task the business users in your organization to confirm the requirements for defining survivorship rules, or 'survivorship strategy'.

As an example, say you have four sources loaded into Reltio. How do you determine the Survivorship rule for Address? The end users / business owners need to agree on what data they trust to create the Operational Value for that attribute. Questions to consider when defining the survivorship strategy include, Is there one contributing data source that is always more trusted than the rest? Is there a contributing data source that will soon be retired or deprecated that you want to make sure is NOT considered in the survivorship strategy? Do the business owners know that due to an existing process, the most recently updated Address can always be trusted as the Operational Value? It is very important for the business stakeholders of the organization to confirm these requirements for your implementation to be successful. There are different out of the box options for defining survivorship - using a trusted source, most recently updated, frequency, aggregation, oldest value, etc. All of the available survivorship strategies are documented in the Survivorship Rules section of the Reltio Documentation portal.

You should also consider a fallback strategy when defining survivorship rules to ensure the correct Operational Value is calculated. Think of a fallback strategy as a tiebreaker. For example, if your survivorship rule is defined to use the attribute from a Marketing source for calculating the Operational Value for phone number, what happens when there are two records from that Marketing source in the entity? The fallback strategy will determine which attribute in this scenario.

It is a best practice to configure Survivorship in the L3 configuration, however, there is an option to change this through the UI. It is important to remember that if you make a change to Survivorship strategy through the UI, it will propagate the change to the L3, so be cautious of using this functionality!

These are some of the key points to consider when defining requirements for your organization's survivorship strategy to ensure the most accurate and complete profile is being shared with end users and consuming applications of Reltio.

------------------------------
Sara Lyons
Technical Delivery Manager
Reltio
Chicago IL

Original Message:
Sent: 05-19-2021 07:20
From: Chris Detzel
Subject: What is survivorship and how can we best leverage it?

We get a lot of questions around survivorship. Some example questions would be how do I create a "Best Address", survivorship based on other attribute winner, fallback strategies (can't do in UI), other complex type scenarios that might require L3 changes. I will have @Sara Lyons help answer this commonly asked integration question. 

#Integration
#Survivorship
#ReltioInsights​​​​

------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------

Survivorship is the process of determining your operational value or golden record, depending on how you want to describe it, out of the multiple sources you brought together in match and merge. And then particularly within Reltio, how it might be different from some other products. Our survivorship is rules driven and a cool thing about it is that it's calculated on the fly so there is no big heavy backend process or anything like that you have to do if you make a change to a rule, it immediately affects and updates all of your records because it is calculated on the fly.

And the vast majority of survivorship configuration can be done directly in the UI. I'm going to touch on a few more advanced features that we'll jump into postman and play with the JSON a little bit but most of this can be done in the UI, which is nice. Make sure you take a look at this webinar if you want to dive deep.

------------------------------
Joel Snipes
------------------------------

Original Message:
Sent: 05-19-2021 07:20
From: Chris Detzel
Subject: What is survivorship and how can we best leverage it?

We get a lot of questions around survivorship. Some example questions would be how do I create a "Best Address", survivorship based on other attribute winner, fallback strategies (can't do in UI), other complex type scenarios that might require L3 changes. I will have @Sara Lyons help answer this commonly asked implementation question. 

#Integration
#Survivorship
#ReltioInsights​​​​

------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------

Hello, 

It is mentioned in session that , no need to run reindex job when survivorship changes in order to apply it to existing data in Tenant.
 
But as per Reltio documentation,  "Note: When the survivorship strategy is changed, to get the correct search results for OV values the tenant must be reindexed to a separate index. To initiate a Reindex job and create a separate index using the enableSeparateIndexing flag, see Reindex Data Task "

Reference Link :  https://docs.reltio.com/matchmerge/survivorshiprules.html?hl=survivorship%2Cstrategies


Can you please clarify this, Thanks

------------------------------
Srujan kumar
KPI partners
Bangalore
------------------------------

Original Message:
Sent: 09-20-2021 10:29
From: Joel Snipes
Subject: What is survivorship and how can we best leverage it?

Survivorship is the process of determining your operational value or golden record, depending on how you want to describe it, out of the multiple sources you brought together in match and merge. And then particularly within Reltio, how it might be different from some other products. Our survivorship is rules driven and a cool thing about it is that it's calculated on the fly so there is no big heavy backend process or anything like that you have to do if you make a change to a rule, it immediately affects and updates all of your records because it is calculated on the fly.

And the vast majority of survivorship configuration can be done directly in the UI. I'm going to touch on a few more advanced features that we'll jump into postman and play with the JSON a little bit but most of this can be done in the UI, which is nice. Make sure you take a look at this webinar if you want to dive deep.

------------------------------
Joel Snipes

Original Message:
Sent: 05-19-2021 07:20
From: Chris Detzel
Subject: What is survivorship and how can we best leverage it?

We get a lot of questions around survivorship. Some example questions would be how do I create a "Best Address", survivorship based on other attribute winner, fallback strategies (can't do in UI), other complex type scenarios that might require L3 changes. I will have @Sara Lyons help answer this commonly asked implementation question. 

#Integration
#Survivorship
#ReltioInsights​​​​

------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------

Hi @Srujan Kumar,

I am not sure If I understand the question here but While we wait for others to brainstorm us , below is my understanding.

When you post any new configuration and you try to access any ​particular profile either using UI or any calling application , you would see your new survivorship rules applied . But when you try to search any particular profile using the OV value of an attribute , you might not find the proper results and that is why it is recommended to run the Re-Index task . 

What re-indexing task does ?
As per Reltio Docs : 
This task refreshes the index that supports Elastic search of a tenant's Entity data. To speed up the search of a large database, the database management system builds one or more database indexes. Like a book index, a database index is a list of paired items: one item is a significant term from the database, and the other is the address of that term in the data storage (like the page number in a large book), where the program can go to find that term. When you type in a term to search for, it's much faster for the program to scan the index for the term, and go directly to the indexed address, than it is to search through the entire database. Database indexes keep large databases tuned up, so that searches can be performed quickly.

Thanks,
Manish

------------------------------
Manish Kumar
Bangalore
------------------------------

Original Message:
Sent: 12-02-2021 11:47
From: Srujan kumar
Subject: What is survivorship and how can we best leverage it?

Hello, 

It is mentioned in session that , no need to run reindex job when survivorship changes in order to apply it to existing data in Tenant.
 
But as per Reltio documentation,  "Note: When the survivorship strategy is changed, to get the correct search results for OV values the tenant must be reindexed to a separate index. To initiate a Reindex job and create a separate index using the enableSeparateIndexing flag, see Reindex Data Task "

Reference Link :  https://docs.reltio.com/matchmerge/survivorshiprules.html?hl=survivorship%2Cstrategies


Can you please clarify this, Thanks

------------------------------
Srujan kumar
KPI partners
Bangalore

Original Message:
Sent: 09-20-2021 10:29
From: Joel Snipes
Subject: What is survivorship and how can we best leverage it?

Survivorship is the process of determining your operational value or golden record, depending on how you want to describe it, out of the multiple sources you brought together in match and merge. And then particularly within Reltio, how it might be different from some other products. Our survivorship is rules driven and a cool thing about it is that it's calculated on the fly so there is no big heavy backend process or anything like that you have to do if you make a change to a rule, it immediately affects and updates all of your records because it is calculated on the fly.

And the vast majority of survivorship configuration can be done directly in the UI. I'm going to touch on a few more advanced features that we'll jump into postman and play with the JSON a little bit but most of this can be done in the UI, which is nice. Make sure you take a look at this webinar if you want to dive deep.

------------------------------
Joel Snipes

Original Message:
Sent: 05-19-2021 07:20
From: Chris Detzel
Subject: What is survivorship and how can we best leverage it?

We get a lot of questions around survivorship. Some example questions would be how do I create a "Best Address", survivorship based on other attribute winner, fallback strategies (can't do in UI), other complex type scenarios that might require L3 changes. I will have @Sara Lyons help answer this commonly asked implementation question. 

#Integration
#Survivorship
#ReltioInsights​​​​

------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------

Hi Srujan,

Good Question. After updating the survivorship settings of an entityType it will immediately be reflected on the profile page without a re-index. However, search might not reflect the update immediately. To be sure your search results are correct immediately after a survivorship change a re-index would be a good idea.

------------------------------
Joel Snipes
------------------------------

Original Message:
Sent: 12-02-2021 11:47
From: Srujan kumar
Subject: What is survivorship and how can we best leverage it?

Hello, 

It is mentioned in session that , no need to run reindex job when survivorship changes in order to apply it to existing data in Tenant.
 
But as per Reltio documentation,  "Note: When the survivorship strategy is changed, to get the correct search results for OV values the tenant must be reindexed to a separate index. To initiate a Reindex job and create a separate index using the enableSeparateIndexing flag, see Reindex Data Task "

Reference Link :  https://docs.reltio.com/matchmerge/survivorshiprules.html?hl=survivorship%2Cstrategies


Can you please clarify this, Thanks

------------------------------
Srujan kumar
KPI partners
Bangalore

Original Message:
Sent: 09-20-2021 10:29
From: Joel Snipes
Subject: What is survivorship and how can we best leverage it?

Survivorship is the process of determining your operational value or golden record, depending on how you want to describe it, out of the multiple sources you brought together in match and merge. And then particularly within Reltio, how it might be different from some other products. Our survivorship is rules driven and a cool thing about it is that it's calculated on the fly so there is no big heavy backend process or anything like that you have to do if you make a change to a rule, it immediately affects and updates all of your records because it is calculated on the fly.

And the vast majority of survivorship configuration can be done directly in the UI. I'm going to touch on a few more advanced features that we'll jump into postman and play with the JSON a little bit but most of this can be done in the UI, which is nice. Make sure you take a look at this webinar if you want to dive deep.

------------------------------
Joel Snipes

Original Message:
Sent: 05-19-2021 07:20
From: Chris Detzel
Subject: What is survivorship and how can we best leverage it?

We get a lot of questions around survivorship. Some example questions would be how do I create a "Best Address", survivorship based on other attribute winner, fallback strategies (can't do in UI), other complex type scenarios that might require L3 changes. I will have @Sara Lyons help answer this commonly asked implementation question. 

#Integration
#Survivorship
#ReltioInsights​​​​

------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------

Thank you Joel Snipes and Manish Kumar , for your quick response.
Noted your comments. Thank you

------------------------------
Srujan kumar
KPI partners
Bangalore
------------------------------

Original Message:
Sent: 12-02-2021 12:31
From: Joel Snipes
Subject: What is survivorship and how can we best leverage it?

Hi Srujan,

Good Question. After updating the survivorship settings of an entityType it will immediately be reflected on the profile page without a re-index. However, search might not reflect the update immediately. To be sure your search results are correct immediately after a survivorship change a re-index would be a good idea.

------------------------------
Joel Snipes

Original Message:
Sent: 12-02-2021 11:47
From: Srujan kumar
Subject: What is survivorship and how can we best leverage it?

Hello, 

It is mentioned in session that , no need to run reindex job when survivorship changes in order to apply it to existing data in Tenant.
 
But as per Reltio documentation,  "Note: When the survivorship strategy is changed, to get the correct search results for OV values the tenant must be reindexed to a separate index. To initiate a Reindex job and create a separate index using the enableSeparateIndexing flag, see Reindex Data Task "

Reference Link :  https://docs.reltio.com/matchmerge/survivorshiprules.html?hl=survivorship%2Cstrategies


Can you please clarify this, Thanks

------------------------------
Srujan kumar
KPI partners
Bangalore

Original Message:
Sent: 09-20-2021 10:29
From: Joel Snipes
Subject: What is survivorship and how can we best leverage it?

Survivorship is the process of determining your operational value or golden record, depending on how you want to describe it, out of the multiple sources you brought together in match and merge. And then particularly within Reltio, how it might be different from some other products. Our survivorship is rules driven and a cool thing about it is that it's calculated on the fly so there is no big heavy backend process or anything like that you have to do if you make a change to a rule, it immediately affects and updates all of your records because it is calculated on the fly.

And the vast majority of survivorship configuration can be done directly in the UI. I'm going to touch on a few more advanced features that we'll jump into postman and play with the JSON a little bit but most of this can be done in the UI, which is nice. Make sure you take a look at this webinar if you want to dive deep.

------------------------------
Joel Snipes

Original Message:
Sent: 05-19-2021 07:20
From: Chris Detzel
Subject: What is survivorship and how can we best leverage it?

We get a lot of questions around survivorship. Some example questions would be how do I create a "Best Address", survivorship based on other attribute winner, fallback strategies (can't do in UI), other complex type scenarios that might require L3 changes. I will have @Sara Lyons help answer this commonly asked implementation question. 

#Integration
#Survivorship
#ReltioInsights​​​​

------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------