Rollback Event
After executing the event, sometimes due to errors in the configuration or components, you must roll back the impact of one or more events, or to a certain step in an event. Rollback provides the option to roll back and restart the workflow from any point in the workflow using the Event log UI or the command-line utility.
With rollback you can roll back an event completely or up to any step of an event, so that the workflow can run again without being constrained by the changes done in the previous run.
You can use rollback for the following tasks:
- Roll back and restart the workflow from any step in the workflow from the Event Log UI
- Roll back any cache markers set for failover and fix the relationships affected
- Delete the data from an event, the master data and the history, and set up the application state in such a way that repeating of the event is possible. As rollback removes data, it runs synchronously.
- Roll back an event in any status, such as completed or in progress. All versions are considered. The versions may be in any state, such as unconfirmed, confirmed, or draft.
Rollback deletes the record versions, the entries from synchronization history, as well as the following master data related to the event:
EVENT, EVENT DETAILS, PROCESSLOG, PROCESS, PRINCIPALKEY, GOLDENCOPY, RELATIONSHIP, MCT, RCT, CONVERSION, DOCUMENTS, WORKITEMS, PROCESSDETAILS, FUTUREDATEDRECORD, and so on.
Rollback includes all child events fired from the event (after the step selected for rollback). Rollback does not remove any fragment or failover markers if the full event is rolled back as these markers are unused. The rollback feature can roll back all the child events as long as those events are linked to the parent event.