Use the BPM Engine for process and task management within your client.
Introduction
The BPM Engine in yuuvis Momentum 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 (process-definitions in Flowable nomenclature) with the help of a Flowable modeler, pack them and export them as applications, and deploy the applications to the BPM-ENGINE in Momentum. Once deployed in such manner, a process definition can be instantiated and executed in the engine. In case that process instances running in the bpm-engine contain user-tasks, they will be available in the Inbox of client for the user to whom they were assigned.
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
yuuvis® client as reference implementation offers three specific views that allow the user to handle the processes based on Flowable:
- 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 view Inbox lists all user-tasks that are intended for the authenticated user, such as the reminder tasks of the Follow-up processes that have reached their follow-up date.
As of version 2021 Autumn, all tasks of processes the currently logged-in user is assigned to are listed as well. - As of version 2021 Autumn, the new view My processes lists all processes started by the logged-in user.
Recommendations
- If you start a process related to a document, the ID of the document shall be saved in the process variable
documentId
. The reference client uses this variable to retrieve and display the object details. - When starting a process, set the process property
name
to a relevant and meaningful value since it will be shown in the column Process in the My processes view. - When modeling a workflow, set the meaningful and relevant names to
Tasks
, since they will be shown in the column Task of the Inbox view.
My follow-ups
This view lists the follow-up processes with the following specific properties:
Column in yuuvis® client | Corresponding Counterpart in BPM Engine | Description |
---|---|---|
Description | Process variable whatAbout | The description that was entered during creating the follow-up. |
Start time | Process parameter startTime | The time the follow-up (process) was created. |
Follow-up date | Process variable expiryDateTime | The due date was entered while creating the follow-up. |
Inbox
As of version 2021 Autumn, the inbox lists besides the follow-up tasks all other BPM tasks as well. Following properties are displayed:
Column in yuuvis® client | Technical details | Description |
---|---|---|
Type | If the process parameter | The description that was entered during creating the follow-up. |
Task | Task name | The time the follow-up (process) was created. |
Received | Task CreateTime | The due date was entered while creating the follow-up. |
My processes
As of version 2021 Autumn, all processes including the follow-ups are listed as soon as they are started by the user. The following properties are affected:
Column in yuuvis® client | Technical details | Description |
---|---|---|
Type | Process-definition parameter processDefinitionName | Process definition name |
Process | Process-instance parameter name (as set when starting the process instance) | Process instance name (e.g. a case number) |
Start time | Process-instance parameter startTime | The time the process was created |
Status | Derived from process-instance parameters completed and suspended | The status of the process can be running, suspended, or deleted. The status is given in the user's language. |
Start a process for an object via plugin action
The object actions can be extended 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 provide the example Two step process action in a client, import the client settings file displayed below. For the settings file import, the user needs an administrative role.
The process model twosteptest_proc
has to be deployed to the Flowable BPM engine.