Roll-back functionality

Thank you for submitting your enhancement request. We think this is a good idea and will target this for inclusion in a future release.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Internet of Things
Product family - Asset Management
Product - IBM TRIRIGA Real Estate Management / IBM TRIRIGA Lease Accounting
Component - Product functionality
Source - Accelerated Value Program (AVP)

For recording keeping, the previous attributes were:
Brand - Internet of Things
Product family - Asset Management
Product - IBM TRIRIGA Application Platform
Component - Product functionality
Source - Accelerated Value Program (AVP)

Thank you for submitting this request. It is currently under review.

Updates :

Description -> TRIRIGA application has a lot of events that execute workflows that are not visible to the business users of the application. Many a times these events hang up causing Java Heap or memory issues that result in unstable application (i.e. application crashes). At McDonalds we have implemented monitoring of these events on a regular basis wherein the team identifies events that are long running (e.g. running for more than 2 hrs) and these events are closely monitored to check if they have activities at OS level (i.e. process ids) that are chugging along or not. If the processes don't show any movement these processes are killed via scripts provided by IBM. Post killing the stuck events the progress of the functionality from TRIRIGA perspective is considered to be in stuck state where event cannot be re-executed from where it left off earlier nor is the transaction in a rolled back state where we can initiate a new event. Due to this we would like functionality on TRIRIGA to be able to functionality events so that we can either perform a cancel/suspend (not needing IBM script follow mundane change management activity), perform a retry/resume (the transaction can be rerun from where it left off), perform a reset/rewind (i.e. rollback to a determined state of the event to initiate event from that point forward). Further details for this as in Use Case section provided below (i.e. in cases where approvals are needed and event/workflow is stuck if we get ability to reassign the approval it will be a good value add).

Business cases (few examples) where this impact is faced today:
- Contract approval events get stuck and business has approved the contract but due to stuck event the application shows that contract is still under process (i.e. Revision in Progress) and this remains the status with no action available for business or IT to take
- Approvals are stuck - Business has taken action and approved the contract but due to stuck event being killed the contract needs to be reset and approvals need to be redone that is frustrating from user experience perspective - this is a manual back end process today - having ability from the application will allow us and the users to determine next best course for approval and next step if needed
- Payment generation events get stuck - this has resulted in lot of pain where once the event has been killed and rerun it has generated duplicate payments as the new run did not consider the previously created payments and generated them again as duplicates

Attachment (Description)

Description -

In case of any stuck threads within the application because of corrupted Contract then we need functionality to suspend/rollback to previous state(refer to Use case for more details)

Use Case
To reassign a notification activity that is not yet complete, select the reassign icon
To suspend a process activity that is not yet complete, select the suspend icon in the Suspend/Resume column. All further processing for the process is suspended until the process is resumed.
To resume a suspended process activity, select the resume icon in the Suspend/Resume column. Processing for the process is resumed and any activities that were transitioned to while the process was suspended are now executed.
To skip an activity and force the workflow to transition to the next activity, select the activity and select the Skip button. In the Skip page, enter the result value to assign to the activity if required.
To retry an activity, select the activity and select the Retry button.
To rewind the workflow to an earlier activity stage, select the Rewind button. In the Rewind page, select the activity you want from the list of activities that the Workflow Engine has reached. Workflow stops processing at the current activity and resumes processing at the specified activity.
To cancel the workflow, select the Cancel Workflow button. In the Cancel page, select Apply. The Workflow Engine sets the status of the workflow to #FORCE, and all processing for the workflow is canceled and cannot be restarted.