You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user, we have noticed that if a workflow trigger fails, it is necessary to roll back all data and statuses across Form.io, Web API, and Camunda databases.
In the initial investigation, we found that Form.io data is sent first to pull the correct data into the Camunda service for triggering and executing the workflow. Therefore, if any error occurs during workflow triggering or execution, manual updates will be required on Form.io and Web API services. To address this, we need to ensure that existing statuses are stored in temporary storage and removed upon successful execution.
Task:
Make sure formio data rollback.
Updated same status into webapi database.
The text was updated successfully, but these errors were encountered:
As a user, we have noticed that if a workflow trigger fails, it is necessary to roll back all data and statuses across Form.io, Web API, and Camunda databases.
In the initial investigation, we found that Form.io data is sent first to pull the correct data into the Camunda service for triggering and executing the workflow. Therefore, if any error occurs during workflow triggering or execution, manual updates will be required on Form.io and Web API services. To address this, we need to ensure that existing statuses are stored in temporary storage and removed upon successful execution.
Task:
The text was updated successfully, but these errors were encountered: