Reltio Connect

Hi Team ,

We have a mandatory and critical requirement in DCR Workflow that if any user do the Reject activity then instead of ending the workflow ,this should be  assigned back to the same user who has initiated  the workflow.

Please let us know how can we achieve this as even through customization also we are not getting option  to meet this requirement .

Hi @Utsa Das -

Previously, I customized an Authoring workflow to orchestrate an entity creation process. In the workflow diagram below, you'll notice that when a reviewer in the 'Packaging & Pricing' team receives a task from 'Planning', the Reject action does not end the workflow. Instead, it redirects the task back to the Planning team reviewer for further updates.

The workflow only ends when the 'Approve Service' or 'Reject Service' tasks are triggered-these govern the final outcome. However, in the scenario I mentioned, the rejection does not trigger a system-level termination but instead routes the task back for iteration.

Let me know if you need further clarification!

Hi Team ,

We have a mandatory and critical requirement in DCR Workflow that if any user do the Reject activity then instead of ending the workflow ,this should be  assigned back to the same user who has initiated  the workflow.

Please let us know how can we achieve this as even through customization also we are not getting option  to meet this requirement .

hi @Karthik Thomas ,

Thanks for your explanation ,but I believe this is routing back to the  first user task ,not to the requester/initiator who has created the task .
The requirement is we need to route back the reject flow to the user who has created/started the DCR .

Hi @Utsa Das -

Previously, I customized an Authoring workflow to orchestrate an entity creation process. In the workflow diagram below, you'll notice that when a reviewer in the 'Packaging & Pricing' team receives a task from 'Planning', the Reject action does not end the workflow. Instead, it redirects the task back to the Planning team reviewer for further updates.

The workflow only ends when the 'Approve Service' or 'Reject Service' tasks are triggered-these govern the final outcome. However, in the scenario I mentioned, the rejection does not trigger a system-level termination but instead routes the task back for iteration.

Let me know if you need further clarification!

Hi Team ,

We have a mandatory and critical requirement in DCR Workflow that if any user do the Reject activity then instead of ending the workflow ,this should be  assigned back to the same user who has initiated  the workflow.

Please let us know how can we achieve this as even through customization also we are not getting option  to meet this requirement .

Hi @Utsa Das -

Understood. 
Since the Start Event itself cannot directly receive tasks, the process must be structured so that a new user task is assigned back to the original initiator.

Some customization that may be involved here could be as follows:

Start Event → Captures the initiator's details for future reassignment.
User Task: Assigned to the Reviewer → A second user reviews the task.
Exclusive Gateway (Approval Decision?)

• If Approved → Process moves forward.
• If Rejected → Task is routed back to the initiator.
  • User Task: "Update Request" (Assigned back to the Initiator).
  • Initiator modifies and resubmits the request, sending it back into the workflow.

Although this may not be the most elegant workaround nor have I tested this style of implementation myself, could you please try and let us know if it helps?


@Yury Timofeev would you have any alternate/better recommendation to help our customer here?

hi @Karthik Thomas ,

Thanks for your explanation ,but I believe this is routing back to the  first user task ,not to the requester/initiator who has created the task .
The requirement is we need to route back the reject flow to the user who has created/started the DCR .

Hi @Utsa Das -

Previously, I customized an Authoring workflow to orchestrate an entity creation process. In the workflow diagram below, you'll notice that when a reviewer in the 'Packaging & Pricing' team receives a task from 'Planning', the Reject action does not end the workflow. Instead, it redirects the task back to the Planning team reviewer for further updates.

The workflow only ends when the 'Approve Service' or 'Reject Service' tasks are triggered-these govern the final outcome. However, in the scenario I mentioned, the rejection does not trigger a system-level termination but instead routes the task back for iteration.

Let me know if you need further clarification!

Hi Team ,

We have a mandatory and critical requirement in DCR Workflow that if any user do the Reject activity then instead of ending the workflow ,this should be  assigned back to the same user who has initiated  the workflow.

Please let us know how can we achieve this as even through customization also we are not getting option  to meet this requirement .

hi @Karthik Thomas ,

Yes ,that's one of the way  we can think of  but I want to know in the step of Modify Requestor(Initiator) , how to find the Initiator so that the  Modify Requestor can be assigned to the user who has started the DCR . Is there any way to do the same ?

Hi @Utsa Das -

Understood. 
Since the Start Event itself cannot directly receive tasks, the process must be structured so that a new user task is assigned back to the original initiator.

Some customization that may be involved here could be as follows:

Start Event → Captures the initiator's details for future reassignment.
User Task: Assigned to the Reviewer → A second user reviews the task.
Exclusive Gateway (Approval Decision?)

• If Approved → Process moves forward.
• If Rejected → Task is routed back to the initiator.
  • User Task: "Update Request" (Assigned back to the Initiator).
  • Initiator modifies and resubmits the request, sending it back into the workflow.

Although this may not be the most elegant workaround nor have I tested this style of implementation myself, could you please try and let us know if it helps?


@Yury Timofeev would you have any alternate/better recommendation to help our customer here?

hi @Karthik Thomas ,

Thanks for your explanation ,but I believe this is routing back to the  first user task ,not to the requester/initiator who has created the task .
The requirement is we need to route back the reject flow to the user who has created/started the DCR .

Hi @Utsa Das -

Previously, I customized an Authoring workflow to orchestrate an entity creation process. In the workflow diagram below, you'll notice that when a reviewer in the 'Packaging & Pricing' team receives a task from 'Planning', the Reject action does not end the workflow. Instead, it redirects the task back to the Planning team reviewer for further updates.

The workflow only ends when the 'Approve Service' or 'Reject Service' tasks are triggered-these govern the final outcome. However, in the scenario I mentioned, the rejection does not trigger a system-level termination but instead routes the task back for iteration.

Let me know if you need further clarification!

Hi Team ,

We have a mandatory and critical requirement in DCR Workflow that if any user do the Reject activity then instead of ending the workflow ,this should be  assigned back to the same user who has initiated  the workflow.

Please let us know how can we achieve this as even through customization also we are not getting option  to meet this requirement .

Hi Utsa -

This would invariably involve some degree of custom java code to capture the initiator ID - something that our Professional Services team can assist you with better, provided that is the most elegant workaround out there.

hi @Karthik Thomas ,

Yes ,that's one of the way  we can think of  but I want to know in the step of Modify Requestor(Initiator) , how to find the Initiator so that the  Modify Requestor can be assigned to the user who has started the DCR . Is there any way to do the same ?

Hi @Utsa Das -

Understood. 
Since the Start Event itself cannot directly receive tasks, the process must be structured so that a new user task is assigned back to the original initiator.

Some customization that may be involved here could be as follows:

Start Event → Captures the initiator's details for future reassignment.
User Task: Assigned to the Reviewer → A second user reviews the task.
Exclusive Gateway (Approval Decision?)

• If Approved → Process moves forward.
• If Rejected → Task is routed back to the initiator.
  • User Task: "Update Request" (Assigned back to the Initiator).
  • Initiator modifies and resubmits the request, sending it back into the workflow.

Although this may not be the most elegant workaround nor have I tested this style of implementation myself, could you please try and let us know if it helps?


@Yury Timofeev would you have any alternate/better recommendation to help our customer here?

hi @Karthik Thomas ,

Thanks for your explanation ,but I believe this is routing back to the  first user task ,not to the requester/initiator who has created the task .
The requirement is we need to route back the reject flow to the user who has created/started the DCR .

Hi @Utsa Das -

Previously, I customized an Authoring workflow to orchestrate an entity creation process. In the workflow diagram below, you'll notice that when a reviewer in the 'Packaging & Pricing' team receives a task from 'Planning', the Reject action does not end the workflow. Instead, it redirects the task back to the Planning team reviewer for further updates.

The workflow only ends when the 'Approve Service' or 'Reject Service' tasks are triggered-these govern the final outcome. However, in the scenario I mentioned, the rejection does not trigger a system-level termination but instead routes the task back for iteration.

Let me know if you need further clarification!

Hi Team ,

We have a mandatory and critical requirement in DCR Workflow that if any user do the Reject activity then instead of ending the workflow ,this should be  assigned back to the same user who has initiated  the workflow.

Please let us know how can we achieve this as even through customization also we are not getting option  to meet this requirement .

Hi Team ,

We have a mandatory and critical requirement in DCR Workflow that if any user do the Reject activity then instead of ending the workflow ,this should be  assigned back to the same user who has initiated  the workflow.

Please let us know how can we achieve this as even through customization also we are not getting option  to meet this requirement .

To meet your requirement of reassigning the Data Change Request (DCR) workflow back to the initiator upon rejection instead of ending the workflow, you will likely need to modify the workflow configuration.

Possible Solutions:

1. Customizing Workflow Business Process Definition

   • Reltio allows customization of workflows by modifying the business process definition and Java code that controls process execution.
   • You would need to adjust the decision gateway logic so that the "Reject" action routes the task back to the initiator instead of terminating the process​
     community.reltio.com
     .

2. Using Workflow API for Reassignment

   • Reltio provides workflow APIs that allow task reassignment dynamically based on conditions.
   • A potential workaround is to configure an automatic reassignment rule using APIs when a rejection event is triggered​
     docs.reltio.com
     .

3. Inbox Reassignment Feature

   • Reltio Inbox allows manual reassignment of tasks. If an automated solution is not possible through configuration, an alternative is to allow the reviewer to manually assign the task back to the initiator​
     community.reltio.com
     .

4. Custom Workflow Deployment

   • If the out-of-the-box configuration does not support this change, you may need to develop a custom workflow using Reltio's workflow customization options.
   • Reltio provides a Bitbucket-based pipeline for custom workflow development and deployment​.

https://docs.reltio.com/en/objectives/manage-workflow-tasks/workflow-management-at-a-glance/workflow-management-reference/workflow-use-cases/reviewing-data-changes

Hi Team ,

We have a mandatory and critical requirement in DCR Workflow that if any user do the Reject activity then instead of ending the workflow ,this should be  assigned back to the same user who has initiated  the workflow.

Please let us know how can we achieve this as even through customization also we are not getting option  to meet this requirement .

Hi All ,

Any expert advise to achieve this requirement ?
Please let me know .

To meet your requirement of reassigning the Data Change Request (DCR) workflow back to the initiator upon rejection instead of ending the workflow, you will likely need to modify the workflow configuration.

Possible Solutions:

1. Customizing Workflow Business Process Definition

   • Reltio allows customization of workflows by modifying the business process definition and Java code that controls process execution.
   • You would need to adjust the decision gateway logic so that the "Reject" action routes the task back to the initiator instead of terminating the process​
     community.reltio.com
     .

2. Using Workflow API for Reassignment

   • Reltio provides workflow APIs that allow task reassignment dynamically based on conditions.
   • A potential workaround is to configure an automatic reassignment rule using APIs when a rejection event is triggered​
     docs.reltio.com
     .

3. Inbox Reassignment Feature

   • Reltio Inbox allows manual reassignment of tasks. If an automated solution is not possible through configuration, an alternative is to allow the reviewer to manually assign the task back to the initiator​
     community.reltio.com
     .

4. Custom Workflow Deployment

   • If the out-of-the-box configuration does not support this change, you may need to develop a custom workflow using Reltio's workflow customization options.
   • Reltio provides a Bitbucket-based pipeline for custom workflow development and deployment​.

https://docs.reltio.com/en/objectives/manage-workflow-tasks/workflow-management-at-a-glance/workflow-management-reference/workflow-use-cases/reviewing-data-changes

Hi Team ,

We have a mandatory and critical requirement in DCR Workflow that if any user do the Reject activity then instead of ending the workflow ,this should be  assigned back to the same user who has initiated  the workflow.

Please let us know how can we achieve this as even through customization also we are not getting option  to meet this requirement .