Trigger on merging identity via Duplicate Identity Management (formerly IMM)

[gergonagy]

Hello Team,

We would like to trigger action on merging potential duplicate identity to primary record i.e. when duplicateDetectionStatus values changes (to 1). However in User Update Rule none of the available trigger types (Import,API,UI) applies to this type of value change. What is the best practice to capture this change in order to be able to trigger action (Re-run Technical rules or Custom Jar action)?

Thank you!
Gergo

[Darshanjain]

Hi @gergonagy 

Duplicate user status and duplicateDetectionStatus  gets updated during the merge process and event source is 6 ( it is updated by Api call ).

You can create the user update rule and re-run technical rules as per your need.

Thanks

Darshan

[gergonagy]

Hello Darshan,

Thank you for your response. Unfortunately, the change in duplicateDetectionStatus cannot be captured in User Update Rule directly, it is not even visible in the User's  Update History. We will test a workaround where we can capture the change on owneronterminate and we can filter that (owneronterminate is not null AND duplicateDetectionStatus = 1) on merge. 

In case of 'Reject', however, we still do not know how to capture the change in duplicateDetectionStatus (0 ->2). Worst case we can think about a detective User Update Rule, but we would appreciate any better idea.

Thanks,

Gergo

[nimitdave]

@gergonagy , additionally you can refer to identitymatchandmergedetails table as this table captures the primary and secondary user mapping alongwith the action taken for the duplicate identities.

[gergonagy]

@nimitdave, Is that possible to refer to identitymatacandmergedetails table from User Update Rule?

[nimitdave]

You can have a runtime analytics and the invoke that from saviynt rest api in the custom jar which in turn will be invoked by user update rule. the you can use the saviynt rest apis to do rest account/user operation.

[gergonagy]

@nimitdave , thank you! we will look into this option.