Update attributes of Entity once the workflow action(Approve/ Reject) is successful

5. RE: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Recommend

Reltio Employee

Diparnab Dey

Posted 11 days ago

Hi Vishvesh/Aruna,

"CompleteAction" and "CancelAction" are just the names of the user actions that I am using in one of the custom workflows that I am working on. It's doing something similar to what your Approve and Reject service is doing. So you can ignore that.

The approach you are following in the BPMN looks correct to me. But, I have a few more questions regarding the use case

What are the criteria for updating the attributes after the workflow approval or rejection? On the specific action that is taken by the user, are you planning to update different attributes or set different values to a single attribute?
Were you able to debug in the local adapter and see why the workflow is failing intermittently? If both the change request Apply and the Attribute Partial override request are being processed successfully, the workflow should not fail.

Another thing that you can check in your code is that make sure to trigger the partial override API call only if the Change Request Apply or Change Request reject API is successful and throw an error if the apply or reject API fails.

------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal
------------------------------

Original Message

Original Message:
Sent: 04-22-2024 12:46
From: Vishvesh Reddy
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Just adding additional information,

a. The partial update we are doing inside the ACR and DCR workflow is using Reltio API calls.

b. We are occasionally seeing errors where we the workflow is not getting completed but the partial update is going thru and our use case is that the update of attribute should happen only when we are able to close the workflow request or while closing the workflow request.

It would be really helpful if we have can get solution here,

a. How to update attributes without using partial update API during the workflow

b. Do we need to invoke other services to update the attributes after the approve or reject service

c. Can we use completeAction or CancelAction to perform the statement mentioned in item "b"

Please provide your comments.

Thanks,

Vish

------------------------------
Vishvesh Reddy
Onetrust

Original Message:
Sent: 04-22-2024 12:28
From: Aruna S I
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

This is the workflow which we created for Approval and Rejection service.
We have 2 processes. One is ACR (Account Creation Request) another one is DCR(Data Change Request)

ACR:

1) Inside that service task 1 a) partially updating the attributes 1 b) workflow is completing.

DCR:

2) Inside service task, 2 a) partially updating the attributes 2 b) Trigger DCR apply changes API 2 c) workflow is completing.

This is the approach we are following. Facing issue that, attributes updated but workflow failed.

What is your thought process on this flow and how can I modify this workflow, do you have any other service task to use inside the workflow?

In your reply you mentioned about complete action? Is it something can I take it up and use? Please elaborate what is the exact functionality of Complete action? Is it rectify my 501 workflow failing error? Please let me know the solution.

------------------------------
Aruna S I
Onetrust

Original Message:
Sent: 04-18-2024 02:40
From: Diparnab Dey
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi Aruna,

Can you share a bit more information on the way you have built the BPMN? Need to understand in which step you are applying the customization logic? Is it after approval/reject?

Something like

In this case, I presume you have created service tasks after the approve/reject operation which is doing the attribute update. That is the correct approach to updating Reltio attributes on workflow completion.

So, can you please confirm in which situations the workflow is failing but the update is going through?

------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal

Original Message:
Sent: 04-17-2024 02:52
From: Aruna S I
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

We have a requirement that, updating the attributes on the successful execution of custom workflows. Currently, we have the code inside the custom workflow, which is updating the attributes before the successful execution of workflow. Sometimes, updates happened but workflow failed. We have to ensure that the update of the attributes are taken place after the execution of workflow. What are the possible options to achieve this scenario?

------------------------------
Aruna S I
Onetrust
------------------------------

6. RE: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Recommend

Vishvesh Reddy

Posted 11 days ago

Hi Diparnab,

Thank you for sharing the analysis and here are some additional details,

What are the criteria for updating the attributes after the workflow approval or rejection? On the specific action that is taken by the user, are you planning to update different attributes or set different values to a single attribute?
- The criteria is to update account status request attribute and account status request ID attribute when Data stewards approve the ACR and DCR.
- For instance, we have 100's of uncertified accounts in Reltio and as soon as the Data stewards approves the ACR or DCR, then the account has to be certified as a Human viewed the data and it is good to go for publishing.
Were you able to debug in the local adapter and see why the workflow is failing intermittently? If both the change request Apply and the Attribute Partial override request are being processed successfully, the workflow should not fail.
- As we are doing partial update first and then _apply without having a check or condition to verify the status of other action, we haven't encountered this error when tested locally but when deployed to our tenants, we are seeing that the partial update is going thru but _apply failed.

Please let me know if you are suggesting the partial update based on the status of _apply operation so the use case we are trying to a solve for is achieved and how would this resemble to ACR where we do not have _apply operation.

Thanks,

Vish

Thanks,

Vish

------------------------------
Vishvesh Reddy
Onetrust
------------------------------

Original Message

Original Message:
Sent: 04-22-2024 13:40
From: Diparnab Dey
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi Vishvesh/Aruna,

"CompleteAction" and "CancelAction" are just the names of the user actions that I am using in one of the custom workflows that I am working on. It's doing something similar to what your Approve and Reject service is doing. So you can ignore that.

The approach you are following in the BPMN looks correct to me. But, I have a few more questions regarding the use case

What are the criteria for updating the attributes after the workflow approval or rejection? On the specific action that is taken by the user, are you planning to update different attributes or set different values to a single attribute?
Were you able to debug in the local adapter and see why the workflow is failing intermittently? If both the change request Apply and the Attribute Partial override request are being processed successfully, the workflow should not fail.

Another thing that you can check in your code is that make sure to trigger the partial override API call only if the Change Request Apply or Change Request reject API is successful and throw an error if the apply or reject API fails.

------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal

Original Message:
Sent: 04-22-2024 12:46
From: Vishvesh Reddy
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Just adding additional information,

a. The partial update we are doing inside the ACR and DCR workflow is using Reltio API calls.

b. We are occasionally seeing errors where we the workflow is not getting completed but the partial update is going thru and our use case is that the update of attribute should happen only when we are able to close the workflow request or while closing the workflow request.

It would be really helpful if we have can get solution here,

a. How to update attributes without using partial update API during the workflow

b. Do we need to invoke other services to update the attributes after the approve or reject service

c. Can we use completeAction or CancelAction to perform the statement mentioned in item "b"

Please provide your comments.

Thanks,

Vish

------------------------------
Vishvesh Reddy
Onetrust

Original Message:
Sent: 04-22-2024 12:28
From: Aruna S I
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

This is the workflow which we created for Approval and Rejection service.
We have 2 processes. One is ACR (Account Creation Request) another one is DCR(Data Change Request)

ACR:

1) Inside that service task 1 a) partially updating the attributes 1 b) workflow is completing.

DCR:

2) Inside service task, 2 a) partially updating the attributes 2 b) Trigger DCR apply changes API 2 c) workflow is completing.

This is the approach we are following. Facing issue that, attributes updated but workflow failed.

What is your thought process on this flow and how can I modify this workflow, do you have any other service task to use inside the workflow?

In your reply you mentioned about complete action? Is it something can I take it up and use? Please elaborate what is the exact functionality of Complete action? Is it rectify my 501 workflow failing error? Please let me know the solution.

------------------------------
Aruna S I
Onetrust

Original Message:
Sent: 04-18-2024 02:40
From: Diparnab Dey
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi Aruna,

Can you share a bit more information on the way you have built the BPMN? Need to understand in which step you are applying the customization logic? Is it after approval/reject?

Something like

In this case, I presume you have created service tasks after the approve/reject operation which is doing the attribute update. That is the correct approach to updating Reltio attributes on workflow completion.

So, can you please confirm in which situations the workflow is failing but the update is going through?

------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal

Original Message:
Sent: 04-17-2024 02:52
From: Aruna S I
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

We have a requirement that, updating the attributes on the successful execution of custom workflows. Currently, we have the code inside the custom workflow, which is updating the attributes before the successful execution of workflow. Sometimes, updates happened but workflow failed. We have to ensure that the update of the attributes are taken place after the execution of workflow. What are the possible options to achieve this scenario?

------------------------------
Aruna S I
Onetrust
------------------------------

7. RE: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Recommend

Reltio Employee

Aditi Verma

Posted 9 days ago

Hi @Vishvesh Reddy

Can you please share with us more information about ACR ( Account Creation Request) process?
Our DCR workflow supports changeRequests for both record creation and updates.
Do you use changeRequests in ACR process as well or these are just tasks tagged to a record with Apply/Reject actions available? Additionally, what classes do you call for the Apply/Reject actions in your workflow for ACR?

In case of the DCR workflow, like Diparnab mentioned you can try updating the attributes after the DCR is applied and see if it helps.
So the in your class after the DCR is applied, we would make changes similar to this,

if (reltioResponse.getStatus() != null || reltioResponse.getStatus().equals(ReltioConstants.SUCCESS)) {
    //Make the update entities POST call here and if POST entities is not successful, throw Reltio exception.
}else if (reltioResponse.getStatus() == null || !reltioResponse.getStatus().equals(ReltioConstants.SUCCESS)) {
    throw new ReltioException(responseJson);
}

------------------------------
Aditi Verma
------------------------------

Original Message

8. RE: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Recommend

Vishvesh Reddy

Posted 7 days ago

Hi @Aditi,

Thank you for the post.

Here are the details,

a. For ACR: we have only the option of Approve/Reject and no data change requests associated with it. This way we would like to certify an account that has been created on Reltio. On the action of Approve/Reject, we would like to do a partial update on the status attibute to reflect the value based on the action selected.

b. For DCR: the approach suggested should work.

Thanks,

Vish

------------------------------
Vishvesh Reddy
Onetrust
------------------------------

Original Message

9. RE: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Recommend

Reltio Employee

Diparnab Dey

Posted 7 days ago

Hi @Vishvesh Reddy,

So does that mean, that once a new account is created in Reltio, you trigger the ACR workflow manually to certify those records by the data stewards?

If that is the case, then you just have to perform the attribute update API call in the service task that you have created for approve and reject service. After the user clicks approve/reject for ACR workflow, the only operation that is supposed to happen in the service task is the attribute update.

So I am a bit curious to know in which cases, the ACR workflow is failing. Ideally, there should not be a situation for ACR where the attribute update goes through, but the workflow fails.
------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal
------------------------------

Original Message

Original Message:
Sent: 04-26-2024 09:39
From: Vishvesh Reddy
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi @Aditi,

Thank you for the post.

Here are the details,

a. For ACR: we have only the option of Approve/Reject and no data change requests associated with it. This way we would like to certify an account that has been created on Reltio. On the action of Approve/Reject, we would like to do a partial update on the status attibute to reflect the value based on the action selected.

b. For DCR: the approach suggested should work.

Thanks,

Vish

------------------------------
Vishvesh Reddy
Onetrust

Original Message:
Sent: 04-24-2024 10:16
From: Aditi Verma
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi @Vishvesh Reddy

Can you please share with us more information about ACR ( Account Creation Request) process?
Our DCR workflow supports changeRequests for both record creation and updates.
Do you use changeRequests in ACR process as well or these are just tasks tagged to a record with Apply/Reject actions available? Additionally, what classes do you call for the Apply/Reject actions in your workflow for ACR?

In case of the DCR workflow, like Diparnab mentioned you can try updating the attributes after the DCR is applied and see if it helps.
So the in your class after the DCR is applied, we would make changes similar to this,

if (reltioResponse.getStatus() != null || reltioResponse.getStatus().equals(ReltioConstants.SUCCESS)) {
    //Make the update entities POST call here and if POST entities is not successful, throw Reltio exception.
}else if (reltioResponse.getStatus() == null || !reltioResponse.getStatus().equals(ReltioConstants.SUCCESS)) {
    throw new ReltioException(responseJson);
}

------------------------------
Aditi Verma

Original Message:
Sent: 04-22-2024 14:18
From: Vishvesh Reddy
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi Diparnab,

Thank you for sharing the analysis and here are some additional details,

What are the criteria for updating the attributes after the workflow approval or rejection? On the specific action that is taken by the user, are you planning to update different attributes or set different values to a single attribute?
- The criteria is to update account status request attribute and account status request ID attribute when Data stewards approve the ACR and DCR.
- For instance, we have 100's of uncertified accounts in Reltio and as soon as the Data stewards approves the ACR or DCR, then the account has to be certified as a Human viewed the data and it is good to go for publishing.
Were you able to debug in the local adapter and see why the workflow is failing intermittently? If both the change request Apply and the Attribute Partial override request are being processed successfully, the workflow should not fail.
- As we are doing partial update first and then _apply without having a check or condition to verify the status of other action, we haven't encountered this error when tested locally but when deployed to our tenants, we are seeing that the partial update is going thru but _apply failed.

Please let me know if you are suggesting the partial update based on the status of _apply operation so the use case we are trying to a solve for is achieved and how would this resemble to ACR where we do not have _apply operation.

Thanks,

Vish

Thanks,

Vish

------------------------------
Vishvesh Reddy
Onetrust

Original Message:
Sent: 04-22-2024 13:40
From: Diparnab Dey
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi Vishvesh/Aruna,

"CompleteAction" and "CancelAction" are just the names of the user actions that I am using in one of the custom workflows that I am working on. It's doing something similar to what your Approve and Reject service is doing. So you can ignore that.

The approach you are following in the BPMN looks correct to me. But, I have a few more questions regarding the use case

What are the criteria for updating the attributes after the workflow approval or rejection? On the specific action that is taken by the user, are you planning to update different attributes or set different values to a single attribute?
Were you able to debug in the local adapter and see why the workflow is failing intermittently? If both the change request Apply and the Attribute Partial override request are being processed successfully, the workflow should not fail.

Another thing that you can check in your code is that make sure to trigger the partial override API call only if the Change Request Apply or Change Request reject API is successful and throw an error if the apply or reject API fails.

------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal

Original Message:
Sent: 04-22-2024 12:46
From: Vishvesh Reddy
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Just adding additional information,

a. The partial update we are doing inside the ACR and DCR workflow is using Reltio API calls.

b. We are occasionally seeing errors where we the workflow is not getting completed but the partial update is going thru and our use case is that the update of attribute should happen only when we are able to close the workflow request or while closing the workflow request.

It would be really helpful if we have can get solution here,

a. How to update attributes without using partial update API during the workflow

b. Do we need to invoke other services to update the attributes after the approve or reject service

c. Can we use completeAction or CancelAction to perform the statement mentioned in item "b"

Please provide your comments.

Thanks,

Vish

------------------------------
Vishvesh Reddy
Onetrust

Original Message:
Sent: 04-22-2024 12:28
From: Aruna S I
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

This is the workflow which we created for Approval and Rejection service.
We have 2 processes. One is ACR (Account Creation Request) another one is DCR(Data Change Request)

ACR:

1) Inside that service task 1 a) partially updating the attributes 1 b) workflow is completing.

DCR:

2) Inside service task, 2 a) partially updating the attributes 2 b) Trigger DCR apply changes API 2 c) workflow is completing.

This is the approach we are following. Facing issue that, attributes updated but workflow failed.

What is your thought process on this flow and how can I modify this workflow, do you have any other service task to use inside the workflow?

In your reply you mentioned about complete action? Is it something can I take it up and use? Please elaborate what is the exact functionality of Complete action? Is it rectify my 501 workflow failing error? Please let me know the solution.

------------------------------
Aruna S I
Onetrust

Original Message:
Sent: 04-18-2024 02:40
From: Diparnab Dey
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi Aruna,

Can you share a bit more information on the way you have built the BPMN? Need to understand in which step you are applying the customization logic? Is it after approval/reject?

Something like

In this case, I presume you have created service tasks after the approve/reject operation which is doing the attribute update. That is the correct approach to updating Reltio attributes on workflow completion.

So, can you please confirm in which situations the workflow is failing but the update is going through?

------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal

Original Message:
Sent: 04-17-2024 02:52
From: Aruna S I
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

We have a requirement that, updating the attributes on the successful execution of custom workflows. Currently, we have the code inside the custom workflow, which is updating the attributes before the successful execution of workflow. Sometimes, updates happened but workflow failed. We have to ensure that the update of the attributes are taken place after the execution of workflow. What are the possible options to achieve this scenario?

------------------------------
Aruna S I
Onetrust
------------------------------

10. RE: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Recommend

Vishvesh Reddy

Posted 7 days ago

Hi Diparnab,

Yes, that is accurate. We are seeing cases where our ACR approve action button is going thru and the update is not happening as our Code doesn't look into the status of the reponse.

We would like to know whether the update of the attribute should happen first then close the workflow or does it need to happen after

closing the workflow.

Thanks,

Vish

------------------------------
Vishvesh Reddy
Onetrust
------------------------------

Original Message

Original Message:
Sent: 04-26-2024 10:30
From: Diparnab Dey
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi @Vishvesh Reddy,

So does that mean, that once a new account is created in Reltio, you trigger the ACR workflow manually to certify those records by the data stewards?

If that is the case, then you just have to perform the attribute update API call in the service task that you have created for approve and reject service. After the user clicks approve/reject for ACR workflow, the only operation that is supposed to happen in the service task is the attribute update.

So I am a bit curious to know in which cases, the ACR workflow is failing. Ideally, there should not be a situation for ACR where the attribute update goes through, but the workflow fails.
------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal

Original Message:
Sent: 04-26-2024 09:39
From: Vishvesh Reddy
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi @Aditi,

Thank you for the post.

Here are the details,

a. For ACR: we have only the option of Approve/Reject and no data change requests associated with it. This way we would like to certify an account that has been created on Reltio. On the action of Approve/Reject, we would like to do a partial update on the status attibute to reflect the value based on the action selected.

b. For DCR: the approach suggested should work.

Thanks,

Vish

------------------------------
Vishvesh Reddy
Onetrust

Original Message:
Sent: 04-24-2024 10:16
From: Aditi Verma
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi @Vishvesh Reddy

Can you please share with us more information about ACR ( Account Creation Request) process?
Our DCR workflow supports changeRequests for both record creation and updates.
Do you use changeRequests in ACR process as well or these are just tasks tagged to a record with Apply/Reject actions available? Additionally, what classes do you call for the Apply/Reject actions in your workflow for ACR?

In case of the DCR workflow, like Diparnab mentioned you can try updating the attributes after the DCR is applied and see if it helps.
So the in your class after the DCR is applied, we would make changes similar to this,

if (reltioResponse.getStatus() != null || reltioResponse.getStatus().equals(ReltioConstants.SUCCESS)) {
    //Make the update entities POST call here and if POST entities is not successful, throw Reltio exception.
}else if (reltioResponse.getStatus() == null || !reltioResponse.getStatus().equals(ReltioConstants.SUCCESS)) {
    throw new ReltioException(responseJson);
}

------------------------------
Aditi Verma

Original Message:
Sent: 04-22-2024 14:18
From: Vishvesh Reddy
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi Diparnab,

Thank you for sharing the analysis and here are some additional details,

What are the criteria for updating the attributes after the workflow approval or rejection? On the specific action that is taken by the user, are you planning to update different attributes or set different values to a single attribute?
- The criteria is to update account status request attribute and account status request ID attribute when Data stewards approve the ACR and DCR.
- For instance, we have 100's of uncertified accounts in Reltio and as soon as the Data stewards approves the ACR or DCR, then the account has to be certified as a Human viewed the data and it is good to go for publishing.
Were you able to debug in the local adapter and see why the workflow is failing intermittently? If both the change request Apply and the Attribute Partial override request are being processed successfully, the workflow should not fail.
- As we are doing partial update first and then _apply without having a check or condition to verify the status of other action, we haven't encountered this error when tested locally but when deployed to our tenants, we are seeing that the partial update is going thru but _apply failed.

Please let me know if you are suggesting the partial update based on the status of _apply operation so the use case we are trying to a solve for is achieved and how would this resemble to ACR where we do not have _apply operation.

Thanks,

Vish

Thanks,

Vish

------------------------------
Vishvesh Reddy
Onetrust

Original Message:
Sent: 04-22-2024 13:40
From: Diparnab Dey
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi Vishvesh/Aruna,

"CompleteAction" and "CancelAction" are just the names of the user actions that I am using in one of the custom workflows that I am working on. It's doing something similar to what your Approve and Reject service is doing. So you can ignore that.

The approach you are following in the BPMN looks correct to me. But, I have a few more questions regarding the use case

What are the criteria for updating the attributes after the workflow approval or rejection? On the specific action that is taken by the user, are you planning to update different attributes or set different values to a single attribute?
Were you able to debug in the local adapter and see why the workflow is failing intermittently? If both the change request Apply and the Attribute Partial override request are being processed successfully, the workflow should not fail.

Another thing that you can check in your code is that make sure to trigger the partial override API call only if the Change Request Apply or Change Request reject API is successful and throw an error if the apply or reject API fails.

------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal

Original Message:
Sent: 04-22-2024 12:46
From: Vishvesh Reddy
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Just adding additional information,

a. The partial update we are doing inside the ACR and DCR workflow is using Reltio API calls.

b. We are occasionally seeing errors where we the workflow is not getting completed but the partial update is going thru and our use case is that the update of attribute should happen only when we are able to close the workflow request or while closing the workflow request.

It would be really helpful if we have can get solution here,

a. How to update attributes without using partial update API during the workflow

b. Do we need to invoke other services to update the attributes after the approve or reject service

c. Can we use completeAction or CancelAction to perform the statement mentioned in item "b"

Please provide your comments.

Thanks,

Vish

------------------------------
Vishvesh Reddy
Onetrust

Original Message:
Sent: 04-22-2024 12:28
From: Aruna S I
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

This is the workflow which we created for Approval and Rejection service.
We have 2 processes. One is ACR (Account Creation Request) another one is DCR(Data Change Request)

ACR:

1) Inside that service task 1 a) partially updating the attributes 1 b) workflow is completing.

DCR:

2) Inside service task, 2 a) partially updating the attributes 2 b) Trigger DCR apply changes API 2 c) workflow is completing.

This is the approach we are following. Facing issue that, attributes updated but workflow failed.

What is your thought process on this flow and how can I modify this workflow, do you have any other service task to use inside the workflow?

In your reply you mentioned about complete action? Is it something can I take it up and use? Please elaborate what is the exact functionality of Complete action? Is it rectify my 501 workflow failing error? Please let me know the solution.

------------------------------
Aruna S I
Onetrust

Original Message:
Sent: 04-18-2024 02:40
From: Diparnab Dey
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

Hi Aruna,

Can you share a bit more information on the way you have built the BPMN? Need to understand in which step you are applying the customization logic? Is it after approval/reject?

Something like

In this case, I presume you have created service tasks after the approve/reject operation which is doing the attribute update. That is the correct approach to updating Reltio attributes on workflow completion.

So, can you please confirm in which situations the workflow is failing but the update is going through?

------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal

Original Message:
Sent: 04-17-2024 02:52
From: Aruna S I
Subject: Update attributes of Entity once the workflow action(Approve/ Reject) is successful

We have a requirement that, updating the attributes on the successful execution of custom workflows. Currently, we have the code inside the custom workflow, which is updating the attributes before the successful execution of workflow. Sometimes, updates happened but workflow failed. We have to ensure that the update of the attributes are taken place after the execution of workflow. What are the possible options to achieve this scenario?

------------------------------
Aruna S I
Onetrust
------------------------------

Reltio Connect