Reltio Connect

 View Only
  • 1.  Changing default survivorship, use of 'filter'

    Reltio Partner
    Posted 08-02-2021 07:40
    Hi Everyone, 

    Hope you all are doing safe.
    I am recently facing an issue wherein I am trying to use the filter option to change my sources priority for an attribute that uses Source system as survivorship rule if it meets a certain criteria. 

    Let's say the attribute is ProfessionalType and i want the source priority, in order 1.Onekey 2.Reltio 3.Veeva  if ProfessionalType =402 . So i used the filter option but then I recently got to know that filter doesn't actually check the OV value of the ProfessionalTyle instead it looks for the entire ov+ non-ov values of the array and thus this source priority is getting applied even in cases where ProfessionalType non-ov value is 402.

    Any help in this regard will be appreciated. 

    Thanks, 
    Manish

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


  • 2.  RE: Changing default survivorship, use of 'filter'

    Reltio Employee
    Posted 08-02-2021 17:52
    Hello Manish, 

    The value-based configuration is feasible for another entity, making this a dependent survivorship rule, 

    check out the implementation example here:
    https://docs.reltio.com/matchmerge/dependentsurvship.html

    Can you elaborate more on the use case regarding specifically validating the OV value for the same entity attribute to decide on the source survivorship?
    Can you point me to the documentation reference? 

    Thanks,
    Shantanu

    ------------------------------
    Shantanu Indra
    ------------------------------



  • 3.  RE: Changing default survivorship, use of 'filter'

    Reltio Partner
    Posted 08-03-2021 00:53
    Hi Shantanu, 

    Thanks for your response. Let me try to explain the problem what I am facing. 

    Suppose there's an attribute say Speciality. Now I want to have the source system priority to be like Onekey - Veeva - Sap while generally it is Veeva - Onekey -Sap iff the value for an attitude say professionalType is 402 . 

    "attribute": "configuration/entityTypes/HCP/attributes/Specialities/attributes/Specialty",
                                "sourcesUriOrder": [
                                    "configuration/sources/Onekey",
                                    "configuration/sources/Veeva",
                                    "configuration/sources/SAP",
                                ],
                                "filter": {
                                    "equals": [
                                        {
                                            "uri": "configuration/entityTypes/HCP/attributes/ProfType",
                                            "value": "402"
                                        }
                                    ]
                                },


    At the moment even if ProfType's non-ov value is 402 it is applying this survivorship while i want the OV value to be 402 and only then apply this survivorship . So, basically this is looking for all possible values for ProfType's attribute array and if the value is 402 (Ov or non-ov) , it is executing this rule . 

    Hope this helps . 

    Thanks,
    Manish


    On Tue, 3 Aug 2021, 03:24 Shantanu Indra via Reltio Community, <Mail@reltio.com> wrote:
    Hello Manish,  The value-based configuration is feasible for another entity, making this a dependent survivorship rule,  check out the... -posted to the "Reltio Connect" community
    Reltio Community

    Reltio Connect

    Post New Message
    Re: Changing default survivorship, use of 'filter'
    Reply to Group Reply to Sender
    Aug 2, 2021 5:52 PM
    Shantanu Indra
    Hello Manish, 

    The value-based configuration is feasible for another entity, making this a dependent survivorship rule, 

    check out the implementation example here:
    docs.reltio.com/matchmerge/dependentsurvship.html

    Can you elaborate more on the use case regarding specifically validating the OV value for the same entity attribute to decide on the source survivorship?
    Can you point me to the documentation reference? 

    Thanks,
    Shantanu

    ------------------------------
    Shantanu Indra
    ------------------------------
      Reply to Group Online   View Thread   Recommend   Forward   Flag as Inappropriate  




     
    You are receiving this notification because you followed the 'Changing default survivorship, use of 'filter'' message thread. If you do not wish to follow this, please click here.

    Update your email preferences to choose the types of email you receive

    Unsubscribe from all participation emails




    Original Message:
    Sent: 8/2/2021 5:52:00 PM
    From: Shantanu Indra
    Subject: RE: Changing default survivorship, use of 'filter'

    Hello Manish, 

    The value-based configuration is feasible for another entity, making this a dependent survivorship rule, 

    check out the implementation example here:
    https://docs.reltio.com/matchmerge/dependentsurvship.html

    Can you elaborate more on the use case regarding specifically validating the OV value for the same entity attribute to decide on the source survivorship?
    Can you point me to the documentation reference? 

    Thanks,
    Shantanu

    ------------------------------
    Shantanu Indra
    ------------------------------


  • 4.  RE: Changing default survivorship, use of 'filter'

    Reltio Partner
    Posted 08-05-2021 11:42
    Hi Team, 

    Can anyone please enlighten me here.

                                    "configuration/sources/Onekey",
                                    "configuration/sources/Veeva",
                                    "configuration/sources/SAP",
                                ],
                                "filter": {
                                    "equals": [
                                        {
                                            "uri": "configuration/entityTypes/HCP/attributes/ProfType",
                                            "value": "402"
                                        }
                                    ]
                                },
    At the moment even if ProfType's non-ov value is 402 it is applying this survivorship while i want the OV value to be 402 and only then apply this survivorship . So, basically this is looking for all possible values for ProfType's attribute array and if the value is 402 (Ov or non-ov) , it is executing this rule . 


    Edit : Tried using "options" : "ovOnly" after filter but it gives a JSON parsing error. 


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



  • 5.  RE: Changing default survivorship, use of 'filter'

    Posted 08-17-2021 20:11
    Hi 
    @Manish Kumar
    ,

    I hope this helps, here for all cases the surpivourship is MinValue and considering only Reltio as Source OrgTyp
    but when OrgStatus filed has value as "Out Of Business" then Surviourship changes to MaxValue.

    {
    "attribute": "configuration/entityTypes/Organization/attributes/OrgType",
    "sourcesForOv": [
    "configuration/sources/Reltio"
    ],
    "survivorshipStrategy": "MinValue"
    },
    {
    "attribute": "configuration/entityTypes/Organization/attributes/OrgStatus",
    "sourcesForOv": [
    "configuration/sources/Reltio"
    ],
    "filter": {
    "equals": [
    {
    "uri": "configuration/entityTypes/Organization/attributes/OrgStatus",
    "value": "Out Of Business"
    }
    ]
    },
    "survivorshipStrategy": "MaxValue"
    },


    On Reltio UI you can see the + is showing other value as Active but OV is Out of Business.
    but when it other value is Dormant, Active is selected as ov.



    Hope this helps.

    ------------------------------
    Deepak Bhansali
    Sr Technical Product Manager
    Advance Auto Parts
    Raleigh
    ------------------------------



  • 6.  RE: Changing default survivorship, use of 'filter'

    Reltio Partner
    Posted 08-18-2021 00:28
    Hey @Deepak Bhansali

    Thanks for your reply .

    The problem i am facing is because of multiple sources contributing values to this attribute ProfType . So, Suppose there are 3 sources A,B,C and A is the winner crosswalk for ProfType attribute . The filter attribute doesn't only look for OV values instead it checks for the entire ProfType array and if it finds the value mentioned in the filter criteria , it executes this rule . No matter if the value is OV or Non-Ov . 

    Lately I had been suggested by Reltio Support to create an LCA for this purpose but then i was looking out for any alternatives as LCA is time/resource consuming process . 

    Thanks,
    Manish



    ​​

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