| Page Properties | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
Resources & Remarks Modification History
|
| Excerpt |
|---|
Use the BPM Engine for process and task management within your client. |
...
Processes and Tasks in the reference client
The yuuvis® client as reference client implementation 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 lists all active follow-ups with their follow-up date.
The 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.
With As of version 2021 Autumn, all tasks of processes the currently logged-in user is offered assigned to are listed as well.
As of version 2021 Autumn, the new view 'My processes' that lists lists all processes he has started , and the inbox is listing all tasks of processes he is assigned toby the logged-in user.
Recommendations
- If you start a process that relates related to a document, the ID of the document shall be saved in the process variable
documentId. The reference client uses this variable to load retrieve and show display the object details. - When starting a process, set the process property
nameto a relevant and meaningful value since it will be shown in the column Process in the 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
The This view My follow-ups lists on the follow-up processes with the following specific parameters that are affectedproperties:
| Column in yuuvis® client | Corresponding Counterpart in BPM Engine | Description |
|---|
| Description | Process variable whatAbout | The description that was entered during creating the follow-up. |
Description| Start time | Process |
whatAboutparameter startTime | The time the follow-up (process) was created. |
Start time| Follow-up date | Process |
startTimevariable expiryDateTime | The due date was entered while creating the follow-up. |
Follow-up dateexpiryDateTimeInbox
Beginning with As of version 2021 Autumn, the inbox lists besides the follow-up tasks all other BPM tasks as well. The view shows the following information:
...
Following properties are displayed:
| Column in yuuvis® client | Technical details | The type of task that can be Follow-up or Task in case of other process models. | Column Description |
|---|---|---|---|
| Type | If the process parameter | The specific Task is either the follow-up description that was entered during creating the follow-up or the name of a taskColumn . | |
| Task | Task name | The time the task follow-up (process) was created. | |
| Column Received | Task CreateTime | The due date was entered while creating the follow-up. |
My processes
Beginning with As of version 2021 Autumn the new view My process lists all , all processes including the follow-up ones ups are listed as soon as they are started by the user has started. The following yuuvis and Flowable parameters properties are affected:
| Description | Column in yuuvis® client | Technical details | Process definition nameDescription | |
|---|---|---|---|---|
| Column Type | Process-definition parameter processDefinitionName | Process | instance name (e.g. a case number)Columndefinition 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 | Column Start time | |
Process-instance parameter startTimeStatus | 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. | Column Status | Derived from process-instance parameters 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.
...