Description
As the process creator, you select the 'Adhoc-Workflow' action, and then configure the necessary tasks with the relevant recipients and optional periods.
...
- To handle date and time outputs internationally, copy the moment-with-locales.min.js library (download here) to ..\jboss\wildfly_ci<core-service>\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 IF the "Changeable" check box is selected, recipients can reconfigure the routing list . When by editing the remaining tasks or adding new ones. If 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.
As the process creator, you can monitor the routing list in your workflow inbox during runtime. This needs to be activated on the start form. You can then edit any all tasks that are not yet completed created or add new ones.
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
Download the example model at the bottom of this page. To import the model into yuuvis RAD designer, follow these steps:
- Copy the downloaded .bpmdef file into your yuuvis RAD designer project directory and open the designer.
- Create a model with same namespace and name of the model (namespace: "adhoc", name: "AdHoc-Workflow-x" where x is the version number) you just downloaded and moved into your project directory.
After importing the process model, set the correct process initiators in the main activity attributes. Here , configure the initiators, process owners and the preset task defined in the start form script. Here, you can also limit the number of object types used, or deactivate 'process start with object' for a start without any object via mainmenue + 'Further actions'.
Steps to import the process:
...
Then validate the model and if everything is fine, deploy it on your system, move it into a model group in management-studio and activate it.
Process Model Version History
| Version | Date | Compatible core-service version | Author | Description | Download | |||
|---|---|---|---|---|---|---|---|---|
| 2.0 | 13th May 2024 | 10.4 or newer | A-Team | Refactored script codes to replace deprecated methods |
|
...
|
...
|
...
ToDos
Set task period as process model period via API, when implemented.- Set task as activity name via API, when implemented.
Implement better routine for sorting the routinglist after changes.Implement better date-time representation in the what about text.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.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
Start with basics:
- Fill routing list during process start
- Optional monitoring and controlling task allows changes by the process initiator
- Sequential processing of the routing list with only one editor per task. If allowed by the process initiator, the current editor can change the rest tasks of the routing list
- Protocol of the processing comments.
Internationalization:
- Preset text for 'What about' and 'Comment'
- If 'What about' and 'Comment' are empty, some corresponding text
- Timestamp within 'What about'
- Some error cases handled in a better way
| 1.20 | 05th May 2024 | 9.8 or newer | A-Team |
|
| ||||||
| 1.19 | 17th Aug 2023 | 9.8 or newer | A-Team |
| |||||||
| 1.18 | 26th Apr 2023 | up to 9.7 | A-Team |
| |||||||
| 1.16 | 6th Sep 2021 | Martin Bartonitz / Lars Nock |
| ||||||||
| 1.15 | 4th Jan 2020 | Martin Bartonitz |
| ||||||||
| 1.12 | 21st June 2018 | Martin Bartonitz |
| ||||||||
| 1.10 | 22nd Nov 2017 | Martin Bartonitz |
| ||||||||
| 1.9 | 16th Sep 2017 | Martin Bartonitz |
| ||||||||
| 1.8 | 4th Sep 2017 | Martin Bartonitz |
| ||||||||
| 1. |
| 5 |
| 2nd Aug 2017 | Martin Bartonitz |
- A process deadline is configured which finishes the corresponding task. The deadline ist set via API and uses the deadlines which the users set in the routing list.
- needs release 3.23.2 2017-09-11 or earlier
| |||
| 1.5 | 25th Jul 2017 | Martin Bartonitz |
- Bugfix: Problem with finish last task
- Setting more events to be historitized
- optimizes process subject
- javascript conformed technical names
Internationalization:
| |||||
| 1.4 | 20th Jul 2017 | Martin Bartonitz | Start with basics:
|