Process Restart

The function described here is similar to the process instance modification Process Instance Modification.

1. Select Instance

In the Process Definition View, you can restart individual or multiple process instances. First, navigate to the 'Restart Tab'.

As in the process instance modification, restarting a terminated process instance includes instructions, which are displayed at the bottom of the screen.

To add an instruction, hover over and click on an activity in the process diagram. By using the modification button, you can select the instruction to be performed with this activity. There are two possibilities:

• start before: restart before the activity
• start after: restart after the activity

The option 'start after' is only possible if there is only one sequence flow going out of the activity.

At any point during the creation of the restart, you can view the payload by clicking the link 'show request payload'. This will display the request payload that will be sent via the REST API.

After clicking on select instances, a modal dialog is shown, where you can select your instances. Initially, all instances are displayed. You can use the filter bar above the list of instances to filter the displayed instances. You can select specific instances or click on the query button to select all instances matching the filter. In our example, there is only one instance, which can be selected using the checkbox on the left.

By clicking on the red button 'reset selected instances', the restart needs to be confirmed.

2. Confirm Restart

In this confirmation dialog, you will see two sections. The options section allows you to specify settings related to the execution of the restart.

• Asynchronous is recommended to keep checked when you want to process a large number of instances. Otherwise, unchecking the box allows you to process the batch synchronously.
• Skip Custom Listeners and Skip IO Mappings make it possible to skip invocations of execution and task listeners, as well as input/output mappings for the transaction that performs the restart. This can be useful when the restart is executed on a system that has no access to the involved process application deployments and their contained classes.
• Initial variables allows you to set the initial set of variables. By default, it is the last set of variables used.
• Without Business Key offers the option to avoid carrying over the business key of the historic process instance to the new instance.

The part below shows a summary of the operations and number of instances you have specified earlier.