Page Comparison

Page Properties

hidden	true
id	PROGRESS

Product Version
Report Note
Assignee

Resources & Remarks

Modification History

Name	Date	Product Version	Action
Antje	23 JUL 2021	2021 Autumn	created
Martin	26 JUL 2021	2021 Autumn	draft
Bratislav	29 JUL 2021	2021 Autumn	draft
Antje	29 JUL 2021	2021 Autumn	formatting, published
Agnieszka	25 AUG 2021	2021 Autumn	rLANG
Martin	24 SEP 2021	2021 Winter	Added the section for starting processes with a startform

Hallo Antje, ich würde gerne noch eine Sektion einbauen, die Client-spezifische Flowable Variablen listet und beschreibt.

Task parameter
(Web-API Gateway GET tasks) Example format Flowable variable name Example format Description

subject

"subject": "My subject"

appClientsystem_subject

Code Block
{ "action": "save", "variables": [ { "name": "appClientsystem_subject", "type": "string", "value": "My subject" }

Process subject

The client-specific task parameter subject is presented in the Inbox column Subject.

The parameter can be set using the Web-API Gateway GET/PUT endpoints for tasks or the corresponding BPM-API endpoints for saving the variable appClientsystem_subject.

attachments

"attachments": ["GUID1","GUID2", "GUID2"]

appClientsystem_attachments

Code Block
{ "action": "save", "variables": [ { "name": "appClientsystem_attachments", "type": "json", "value": [ "GUID1", "GUID2" ] }

Process attachments

The client-specific task parameter attachment is used for the task aspect Attachments in the Inbox. This parameter contains an array of object GUIDs. The user sees the title of the corresponding objects in the list of attachments.

The parameter can be set using the Web-API Gateway GET/PUT endpoints for tasks or the corresponding BPM-API endpoints for saving the variable appClientsystem_attachment.

taskMessages

Example code for the GET tasks response of the Web-API Gateway:

Code Block
"taskMessages": [ { "message": "tenKolibri:text1" }, { "level": "error", "message": "text 2" }, { "level": "warning", "message": "text 3" }, { "level": "info", "message": "text 4" } ]

appClientsystem_taskMessages

Example code for saving the Flowable variable appClientsystem_taskMessages via BPM-API PUT tasks:

Code Block

{
  "action": "save",
  "variables": [
    {
      "name": "appClientsystem_taskMessages",
      "type": "json",
      "value": [ 
        {
          "message": "tenKolibri:text1"
        },
        {
          "level": "error",
          "message": "text 2"
        },
        {
          "level": "warning",
          "message": "text 3"
        },
        {
          "level": "info",
          "message": "text 4"
        }
      ]
    }

Dynamic Task Messages

This client-specific task parameter can be used to present necessary information for working on this particular task. The messages are presented on the top of the task aspect area in the inbox.

The parameter level differentiates 4 types of formating the messages:

level	description
without level	The message is rendered in the normal format
info	The text is rendered in Green
error	Text is rendered in Red
warning	Text is rendered in Yellow

In this case, the message is a localization key the key will be translated (see "tenKolibri:text1" in the example).

The task parameter taskMessages is responded in the GET tasks endpoint of the Web-API Gateway and can only be set by saving the Flowable variable appClientsystem_taskMessages.

taskForm

appClientsystem_taskForm

Example code for saving the Flowable variable appClientsystem_taskForm via BPM-API PUT tasks:

Code Block
{ "action": "save", "variables": [ { "name": "appClientsystem_taskForm", "type": "json", "value": { "schemaProperties": [ "tenKolibri:strsingle", "tenKolibri:datesingle" ] } } ] }

...

Column in yuuvis® client	Corresponding Counterpart in BPM Engine	Description
Description (not available anymore as of version 2021)	Process variable `whatAbout`	The description that was entered while creating the follow-up.
as of 2021 Winter: Subject	Web-API Gateway parameter `subject`, represented as Flowable string variable `subject`	Set while creating the process.
Created on	Process parameter `startTime`	The time the follow-up (process) was created.
Follow-up date	Process variable `expiryDateTime`	The due date that was entered while creating the follow-up.
Status	Derived from process parameters `endTime` and `suspended`	Possible values for Status are `running`, `completed` and `suspended`.

...

Versions Compared

Old Version 37

New Version 38

Key