Life Cycle Hooks

Life Cycle Actions (LCA) hooks in Reltio allow you to define custom logic to be executed at specific points during the life cycle of an object, such as before saving or after deletion. These hooks provide a flexible framework for implementing custom tasks and enhancing data management processes. By configuring hooks, you can ensure specific actions are taken automatically based on events, improving the automation and consistency of your data workflows. For more details on LCA, see topic Life Cycle Actions

Life Cycle Action Hooks

Entity-specific Hooks

These hooks are only applicable to entities and their functionality is explained in the following steps:

1. The POST/entities API endpoint receives a list of entities to override. The entities are passed to the rawDataBeforeCleanse hook.
2. The Reltio API cleanses all the entities and then the second hook, rawDataAfterCleanse, is triggered.
3. The Reltio API searches for matches (by auto rules or by crosswalks). If any matches are found, the beforeOverride hook, is triggered. The Action Handler receives the following objects:
   • Raw data that came from the client
   • Content of the object to be overridden
4. After the override, the afterOverrideBeforeCleanse hook is triggered.
5. The results are cleansed and then the beforeSave hook is triggered.
6. Reltio API saves the modified (or created, if there were no matches to override) object. After the object is saved into Cassandra, the afterSave hook is triggered. This hook cannot make any changes to the object and also cannot cancel the operation.

All Object Hooks

These hooks are applicable for entities, graphs, interactions, and groups.

Changing Object

Perform the following steps to change an object:

1. After any change is made to the content of an object (such as attribute, role, tag, crosswalk added/modified/removed, and so on), the Reltio API loads the object. Before the object is modified, the beforeUpdate hook is triggered.
2. After the object is modified, the afterUpdateBeforeCleanse hook is triggered.
3. The modified object is cleansed and the beforeSave hook is triggered.
4. The Reltio API saves the object into Cassandra and runs the afterSave hook.

Deleting Object

Merging Objects

When several objects are merged, the beforeMerge and afterMerge hooks are triggered. The Reltio API cleanses the results of the merge and then saves the result to Cassandra. Appropriate hooks (afterUpdateBeforeCleanse, beforeSave, and afterSave) are triggered.

Unmerging Object

If an object is unmerged, the beforeUnmerge hook is triggered, followed by the beforeNotAMatchSet and afterNotAMatchSet hooks. The beforeSave and afterSave hooks are executed for both the unmerged objects, followed by the afterUnmerge hook. The afterUnmerge hook receives both the objects as a result of the unmerge operation.

Potential Matches Found

If potential matches are found for an object, the potentialMatchesFound hook is triggered.

Mark as Match, Mark as Not a Match

If a client is asked to set Not a Match, remove Not a Match, or set Mark as Match, the following hooks can be triggered:

• beforeNotAMatchSet
• afterNotAMatchSet
• beforeNotAMatchReset
• afterNotAMatchReset
• beforeMarkAsMatch
• afterMarkAsMatch
• beforeUnmarkAsMatch
• afterUnmarkAsMatch

Reference Attributes Changes

If reference attributes are changed, the following hooks are triggered:

• beforeReferenceAttributeAdded
• afterReferenceAttributeAdded
• beforeReferenceAttributeChanged
• afterReferenceAttributeChanged
• beforeReferenceAttributeRemoved
• afterReferenceAttributeRemoved