You might ask yourself the question why you want to use the process engine at all. It is possible to model tasks and implementations using Aggregate. Starting a task then is then just starting a flow depending on which entry is selected. While in essence this is possible to do, you will need to create much functionality yourself that comes out of the box when using the process engine. This page shows an overview of the feature of the process engine that are adding value to your implementation and which you will not have or have to create yourself when not using the process engine.
| Feature | Description |
|---|---|
| 2-man rule | Algorithms such as the 2-man rule can be used for authorization on tasks, to make sure that not the same person executes the second task. |
| Authorization | Roles can be authorized to start a specific task so that you can only start a certain task if you have that role. |
| Automatic tasks | Automatic tasks can be triggered, and scheduled to start at a certain time, or even repeatedly after a time interval. |
| Business Activity Monitoring | A business overview can be generated over all the running processes to see the load of the system and the workers. |
| Design overviews | A business engineer can see and model processes. This contributes to the understand-ability and maintainability of business processes. |
| Events | (Life) events can be send to processes that affect the behavior of the process. There are mechanisms in place to make sure that the event can be delivered even in case of failure. |
| Routing | Task can be routed to teams, roles and users to obtain a fair work distribution. |
| Repeat | Task and processes can be repeated for as long as they are needed. |
| Prioritization | Task can be prioritized by using priority algorithms so that knowledge workers can work on the highest priority task first. |
| Process locking | A process can be locked when a task is executed so that no other person is able to start a task at the same time. |
| Tracing | Process actions are traced so that the exact manner in which the process was handled can be reconstructed. |
| Time monitoring | Terms can be monitored and actions can be triggered at a specific point in time. For example, a reminder can be send one week after a task was created. |
| Timeline | Events are logged and can be shown in an overview so that knowledge workers get a good idea of the actions that happened in the past of the case. |
| Case- and Worklist | A list of cases and tasks can be shown to users. Filters and sorting can be added so that users can find the case or task that they are looking for. |
| Error handling | Tasks that get into an error state can be repaired and reopened. |
| Process Migration | Migrating old processes to a new version of the process model is (limited) possible. |
Overview
Content Tools
3 Comments
Jos van Spronsen
In relation to the Business Activity Monitoring feature. Can you provide an example dashboard to show the actual data that is provided? What do you specifically mean by "load of the system"?
Unknown User (r.arts)
Hi Jos,
The data that is provided depends on the structure of your process module. You can model this using the following containers:
With the AQ_Statistic_Process container you can do a count of the processes that match a certain condition. For example all the process that are handled by team x. With a second container you can count all the processes that are handled by team y. And so on. The actual numbers can be shown in a chart using the AQ_Statistic_Visualization container.
So with this example you can show how the load of processes is divided between teams.
Does this answer your questions?
Jos van Spronsen
Yes it does, thank you very much.