Rollback process example

Let us consider the following process template as an example of how to create and define a process template using the rollback process. Figure 21 represents a Purchase Request process template.

The Purchase Request process contains the following user-defined dataslots.

The process is summarized as follows: An employee requests an item. If the manager approves the item, then a purchase order program is executed. In addition to searching for the availability of the requested item, the program can save the information in a database to track the employee order and update entries in the database. In the final workstep, "Order Approval," a manager approves the order and the order is placed.

You may want rollback functionality in the process, when the following situations occur:

Table 13 summarizes the workstep properties in this example.

The "Manager Approve" workstep has a rollback point set to allow rollback to this workstep. The dataslot values of Product_Description, Product_ID, Product_Quantity, Product_Price, Product_Name, and Estimated_DeliveryTime can be replaced at a later stage in the process with the dataslot values from this workstep.

The Decision gateway has two outgoing links, "Approved" and "Not Approved" (default). For the "Approved" conditional link, configure the condition with "approved" dataslot value set to true.

The "Purchase Order" workstep also includes compensatory JavaScript, which can be added to reactivate the "Manager Approve" workstep and clean the database of changes the failed adapter might have made.

To define the compensatory JavaScript in the On Recovery area under the Advanced tab, click in the Execute script text area and make changes or add new script as required (Figure 22).