Adhoc Workflow

Description

As the process creator, you select the 'Adhoc-Workflow' action, and then configure the necessary tasks with the relevant recipients and optional periods.

You then start the workflow, and a loop activity processes the routing list task by task.

You can use an optional monitoring and controlling action to observe the progress and modify the remaining tasks.

Here is a preview of the graphical process model:

Important Notes

• This process model needs version 2017-07-19 or later.
• To handle date and time outputs internationally, copy the moment-with-locales.js library (download here) to ..\jboss\wildfly_ci\standalone\configuration\bpm-script-api\lib
  • Otherwise a Zulu-formatted timestamp is given in the comments track.
• Screenshots on this page may differ slightly from the current look of this process model.

Send feedback to bartonitz@optimal-systems.de or leave a comment on this article.

Process start

As the process creator, you can configure the routing list during the process start.

In this example, the column "No" is used as a workaround to sequence tasks. You can have the workflow execute the third task in the list before the second task by changing "30" to a number between 10 and 20. Or you can add a new task with a recipient and a number that sorts it into the desired slot in the sequence. A sorting routine ensures that the tasks are listed and executed in numerical order.

When you select the "Changeable" check box, recipients can reconfigure the routing list. When the check box is not selected, no other users can edit the list during runtime.

Monitoring and controlling the process

As the process creator, you can monitor the routing list in your workflow inbox during runtime. You can edit any tasks that are not yet completed.

For compliance purposes, you can view the initial routing list by clicking the "History" tab.

Executing the workflow

The recipients get a notification about the things to be done and can leave a comment if desired. The comments are written into the process history.

If the recipient has the corresponding permissions, he can reconfigure the routing list for any tasks still open.

Administering the Adhoc Workflow

After importing the process model, set the correct process initiators in the main activity attributes. Here you can also limit the number of object types used, or deactivate 'process start with object' for a start without object via mainmen + 'Further actions'.

Also configure the script for the start form. The script contains some preset entries for the routing list, which you can delete or change.

Meanwhile the export/import function has been changed since version 2018-02-14 and with this the file format has changed. So, Please, import the following model into a release from 2018-02-28:

The following model version 1.12 can be used with enaio redline 4.x:

ToDos

1. Set task period as process model period via API, when implemented.
2. Set task as activity name via API, when implemented.
3. Implement better routine for sorting the routinglist after changes.
4. Implement better date-time representation in the what about text.
5. A new feature can help to show the new sorting after changes of the routing list. Currently there is no re-sorting after saving row data.
6. May be a bit more interantionality

With more effort:

• One task may be sent to each member of a group (multi-activity parallel)
• Saving and loading routing lists
• Forwarding action 'Send to last editor' which goes one task back in the routing list
• Add a last activity with a notification for the process initiator which ends the monitoring task.
• Create a process protocol file as object and link it to the object the process was running against.

Process model version history