Reltio Integration Hub

Creating Custom Workflows with Reltio Integration Hub: An Ask Me Anything Session

In a recent Ask Me Anything session, Chris Detzel and Dan Gage discussed how to create a custom workflow with three steps that are triggered whenever a new profile is created for an entity in Reltio Integration Hub. The discussion covered various aspects of building workflows, triggering them, and incorporating conditional logic.

Building Workflows with Listener Classes and Service Tasks

Chris and Dan explained the use of listener classes and service tasks for constructing workflows. They discussed two methods for triggering the workflow: using the event queue or utilizing Reltio Integration Hub. Dan explained the process of setting up an external queue in the tenant management section and selecting the events to be published to that queue. With Reltio Integration Hub, users can create a recipe to listen to the queue and activate the desired workflow when a new profile is created.

Triggering Workflows for Community Review

Dan Gage demonstrated how to initiate a workflow for community review using the Reltio Integration Hub. First, he modified the data model by adding a "Community Review" attribute. This allows business users to determine when a record is ready for review. He then created a saved search for users to monitor records pending review or needing work.

To trigger the workflow, Dan recommended using Reltio Integration Hub. He created a new recipe that runs every five minutes to search for records with the Community Review attribute set to true and an empty Process ID attribute. Once a workflow is assigned, the workflow identifier is added to the Process ID attribute to prevent assigning another workflow to the same record. Dan emphasized that conditional logic could be incorporated into the Reltio Integration Hub, allowing different workflows to be triggered based on specific attributes of the record.

Custom Message Error Warnings and Bulk Requests

Dan Gage noted that throwing custom message error warnings based on workflow logic is not currently customizable but is likely to change in the next 12 months. He suggested using a try-except block in Java code to log errors and make them accessible and reportable. Regarding the creation of ARN and SQS queues, Dan explained that Reltio provides three standard queues (dev, test, and production) as part of the license agreement. If more queues are needed, they can either be created by Reltio for a small fee or by system administrators who can generate the ARN themselves.

For bulk requests, Dan confirmed that calling workflows is possible, as long as the same type of workflow is started for multiple entities. Timeouts could be a concern, so the invoking process should be willing to wait for the processing duration. If potential matches are too high, it could become an overhead, and posting a message on the community or submitting a support ticket is recommended for more specific thresholds.

Debugging APIs and Working with the Developer Console

Dan Gage discussed debugging an API and working with the developer console to examine incoming data. He demonstrated using a custom action to start a workflow process in Reltio, configuring the path, input, and headers, and adding an action to update a record. He emphasized the need to use the correct environment URL, manage schema, and handle arrays.

The session concluded with Chris Detzel thanking everyone for participating and mentioning that it would be recorded and posted to the community for later access. Dan Gage agreed to the idea of an "Ask Me Anything Part 2" to continue the discussion and answer more questions in the next couple of weeks.