Mass actions in reports

Applies to version 2019.1; author: Kinga Bożęcka

Introduction

Mass actions allow you to go through the path (and execute the actions that are on it e.g. starting sub-workflows) for many instances at the same time. The article describes the configuration of this action and two examples of use.  

Fig. 1. The example process

Fig. 2. The form

Mass acceptation

Let’s create a report with instances from the Acceptation step.

Fig. 3. The report configuration - source

In the Columns tab, add the [System] “Step” column:

Fig. 4. The report configuration - columns

1 – Mass actions tab

2 – Adding a new mass action button

3 – Changing the name displayed on the report bar

4 – Selecting the transition path

5 – Adding a custom message about confirming the operation

6 – Disable the message about confirming the operation (in case of errors)

Fig. 5. The report configuration – Accept action

Fig. 6. The report configuration - Reject action

In the Views tab move the mass action buttons from right to the left:

Fig. 7. The report configuration – views

On the report bar you will see two mass actions:

Fig. 8. Mass actions on the form

After executed the action you will see the confirmation of the completed operation.

Fig. 9. Conformation of the operation

Mass change of form field value

To change the form field value at the Archive step, select the path (in this example – “_change value”) which redirects to the Archive step. You do not add the action to change the field value.

Similarly as before, create a report with instances from the Archive step. Add a new mass action button, select the created technical path and drag the form field from the tree to the left side (5). Select if the field should be required and make sure that the report has a column called Step!. Drag the button to the left in the Views tab.

Fig. 10. Mass action changing the “Change amount” field value

After clicking on this button, a window for entering a new value in the “Change amount” field will appear:

Fig. 11. The action of changing the “Change amount” field value

Finally, hide the visibility of technical field on the form.

Fig. 12. Availability restrictions