Use the BPM Engine for process and task management within your client.
Introduction
The BPM Engine is provided by the BPM-ENGINE service based on the workflow functionality of the open-source software Flowable. In yuuvis® client as reference implementation, it can be integrated in order to support process and task management via the browser application.
Administrators can model process models with the help of a Flowable editor and deploy them to the BPM engine. Once deployed a process instance based on that model can be started and resulting tasks being executed.
The following information is intended to support administrators to set up Flowable processes that are supported by the reference client.
Processes and Tasks in the reference client
The reference client offers three specific views that allow the user to handle the processes based on Flowable. The first process that was as a standard delivered with yuuvis® was for supporting follow-ups. A user can create follow-ups for each object via the action menu. The view 'My follow-ups' lists all active follow-ups with their follow-up date. The inbox lists all follow-ups that have reached their follow-up date.
With version 2021 Autumn the user is offered the new view 'My processes' that lists all processes he has started, and the inbox is listing all tasks of processes he is assigned to.
The process history as well as actions on the processes like suspending, resume, cancel, as well as on tasks like forwarding will with the next version.
Recommendations
If you start a process:
- Map the yuuvis parameter
system:objectID
to the Flowable parameterbusinessKey
. The reference client uses this parameter to load the object details. - Map the yuuvis parameter
appClient:clientTitle
to the Flowable parametername
and optionally to the variablewhatabout
as well. The reference client uses these parameters to show them in theInbox
columnTask
as well as in theMy processes
columnProcess
.
My follow-ups
The view My follow-ups
lists on the follow-up processes with the following specific parameters that are affected:
Description | yuuvis® | Flowable |
---|---|---|
The description that was entered during creating the follow-up. | Column Description | process variable whatAbout |
The time the follow-up (process) was created. | Column Start time | startTime |
The due date was entered while creating the follow-up. | Column Follow-up date | process variable expiryDateTime |
Inbox
Beginning with version 2021 Autumn the inbox lists besides the follow-up tasks all other BPM tasks as well. The view My follow-ups
lists on the follow-up processes with the following specific parameters that are affected:
Description | yuuvis® | Flowable |
---|---|---|
The type of task that can be Follow-up or Task in case of other process models. | Column Type | If the processDefinitionName is Follow-up then this value otherwise the static label Task |
The specific Task is either the follow-up description that was entered during creating the follow-up or the name of the process | Column Task | If the processDefinitionName is Follow-up the process variable whatAbout otherwise the task name |
The time the follow-up task was received by the user. | Column Received | CreateTime |
My processes
Beginning with version 2021 Autumn the new view My process
lists all processes including the follow-up ones the user has started. The following yuuvis and Flowable parameters are affected:
Description | yuuvis® | Flowable |
---|---|---|
Process model name as deployed. | Column Type | processDefinitionName |
Process instance name (e.g. a case number) | Column Process | name := is any user-entered string while starting |
The time the follow-up (process) was created | Column Start time | startTime |
The status of the process can be running, suspended, or deleted. The status is given in the user's language. | Column Status | derived from completed and suspended |
Start a process for an object via plugin action
You can extend the object actions with a plugin action that can be offered in the action group MORE ACTIONS
. The following example offers the action Two step process
that starts a process based on the process model twosteptest_proc
( mapped to Flowable processDefinitionKey
) for a single marked object.
To get this example action offered the following code must be imported as a file in the settings of the client. The user needs an administrative role.
And the process model twosteptest_proc
has to be deployed to the Flowable BPM engine