Reltio Connect

 View Only

  • 1.  Defining Custom Survivorship strategy

    Reltio Partner
    Posted 22 days ago

    Hi,
    I would like to define a custom survivorship strategy for one of our use cases. For instance, let's consider the email "user.name@domain.com." Reltio's email cleanser has flagged this as an "Invalid" email, and I want to prevent invalid emails from being passed on to downstream systems. Currently, the survivorship for email attributes is set to aggregation. Is there a way to implement a custom survivorship strategy for this scenario?



    ------------------------------
    Thanks & Regards
    Kulasekaran N
    ------------------------------


  • 2.  RE: Defining Custom Survivorship strategy

    Reltio Employee
    Posted 18 days ago

    Hi Kulasekaran,

    Please use the below sample rule to achieve this requirement:

    [
	{
		"attribute": "configuration/entityTypes/Individual/attributes/Email",
		"survivorshipStrategy": "Aggregation",
		"filter": {
			"equals": [
				{
					"uri": "configuration/entityTypes/Individual/attributes/Email/attributes/ValidationStatus",
					"value": "VALID"
				}
			]
		}
	},
	{
		"attribute": "configuration/entityTypes/Individual/attributes/Email",
		"survivorshipStrategy": "SRC_SYS",
		"sourcesForOv": [
			"configuration/sources/FB"
		]
	}
]

    The source system mentioned in the sourcesForOv block should be a dummy source that would never contribute to any attribute value.

    Screenshot of a profile where the rule is applied:

    The Invalid Email does not survive as per the rule.

    Please let me know if you have any questions



    ------------------------------
    Thanks,
    Snehil Kamal
    Solution Architect
    Reltio
    Bangalore
    ------------------------------

    Original Message


  • 3.  RE: Defining Custom Survivorship strategy

    Reltio Partner
    Posted 16 days ago
    Hi Snehil Kamal,
     
    Thank you so much for the detailed explanation. I understood the first part about applying the filter to select only valid email IDs, but I'm unclear about the second part. Could you please explain why a dummy source is being added? Is it necessary to include a dummy source, or can it be omitted?


    ------------------------------
    Kulasekaran N
    MathCo
    ------------------------------

    Original Message


  • 4.  RE: Defining Custom Survivorship strategy

    Reltio Employee
    Posted 16 days ago

    Hi Kulasekaran ,

    The second part gets applied to all the nests where ValidationStatus<>"Valid".  The sourcesForOv list contains only one source "configuration/sources/FB" which directs the platform to only consider values from this source against the survivorship rule. Since this is a dummy source and won't contribute to any values, any nests where ValidationStatus<>"Valid" would be marked as OV:False.

    I can't think of any other ways to achieve this without defining a dummy source in the sourcesForOv block. Hope that explains



    ------------------------------
    Thanks,
    Snehil Kamal
    Solution Architect
    Reltio
    Bangalore
    ------------------------------

    Original Message


  • 5.  RE: Defining Custom Survivorship strategy

    Reltio Employee
    Posted 15 days ago

    Cool trick on the dummy Source approach, Snehil!



    ------------------------------
    Bryant Barrenechea
    Solution Architect | Professional Services
    ------------------------------

    Original Message


Related Content