{
  "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.

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

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

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

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

{
  "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:

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.

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

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

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 service in yuuvis® Momentum. Once deployed in such a manner, a process definition can be instantiated and executed in the BPM Engine. If process instances running in the bpm engine contain user tasks, they will be available in the Inbox of 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 users to handle processes based on Flowable:

• Users can create follow-ups for each object via the action menu. The My follow-ups view lists all active follow-ups with their follow-up date.
• The Inbox view lists all user tasks that are intended for the authenticated user, such as reminder tasks of 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 My processes view lists all processes started by the logged-in user.

Recommendations

• If you start a process related to a document, the ID of the document should be saved in the process variable documentId. The reference client uses this variable to retrieve and display object details.
• When starting a process, specify a meaningful value for the process property name since it will be shown in the Process column in the My processes view.
• When modeling a workflow, specify meaningful names for Tasks, since they will be shown in the Task column in the Inbox view.

My follow-ups

This view lists the follow-up processes with the following specific properties:

...

Description (not available anymore as of version 2021)

...

Inbox

As of version 2021 Autumn, besides the follow-up tasks, the inbox lists all other BPM tasks as well. The following properties are displayed:

...

If the process parameter processDefinitionName is Follow-up, then Follow-up. Otherwise Task.

As of 2021 Winter, an icon is displayed. If the process parameter processDefinition.idPrefix is follow-up, then a bell is shown and the tooltip shows Follow-up. Otherwise, a general process icon is shown and a tooltip with the localized prefix. If no localization is configured, the technical prefix is displayed.

...

Received

as of 2021 Winter: Received on

...

The date and time the task was created.

The value corresponds to the due date that was entered while creating the follow-up.

My processes 

As of version 2021 Autumn, all processes including follow-ups are listed as soon as they are started by the user. The following properties are affected:

...

Process-definition parameter processDefinitionName

As of 2021 Winter, an icon is displayed. If the process parameter processDefinition.idPrefix is follow-up, then a bell is shown and the tooltip shows Follow-up. Otherwise, a general process icon is shown and a tooltip with the localized prefix. If no localization is configured, the technical prefix is displayed.

...

The status of the process can be running, suspended, or completed. 

The status is given in the user's language.

Starting a Process for an Object via a Plug-in Action

The object actions can be extended with a plug-in action that can be offered in the MORE ACTIONS action group. The following example shows the Two step process action, which starts a process based on the twosteptest_proc process model (mapped to Flowable processDefinitionKey) for a single marked object or for multiple selected objects.

As of 2021 Winter, the objects are displayed in the attachment task of the task details for a selected task in the Inbox. 

Image Removed

To provide the example Two step process action in a client, import the client plug-in configuration file shown below. To be able to import a settings file, users need an administrative role.
>> Extending the Clients with Plug-ins

The twosteptest_proc process model has to be deployed to the Flowable BPM Engine.

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 service in yuuvis® Momentum. Once deployed in such a manner, a process definition can be instantiated and executed in the BPM Engine. If process instances running in the bpm engine contain user tasks, they will be available in the Inbox of 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 users to handle processes based on Flowable:

• Users can create follow-ups for each object via the action menu. The My follow-ups view lists all active follow-ups with their follow-up date.
• The Inbox view lists all user tasks that are intended for the authenticated user, such as reminder tasks of 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 My processes view lists all processes started by the logged-in user.

Recommendations

• If you start a process related to a document, the ID of the document should be saved in the process variable documentId. The reference client uses this variable to retrieve and display object details.
• When starting a process, specify a meaningful value for the process property name since it will be shown in the Process column in the My processes view.
• When modeling a workflow, specify meaningful names for Tasks, since they will be shown in the Task column in the Inbox view.

Inbox

As of version 2021 Autumn, besides the follow-up tasks, the inbox lists all other BPM tasks as well. The following properties are displayed:

As of version 2021 Winter, the inbox offers a task details area with the aspects Task, History, and Attachments (not on the following screenshot). 

The following screenshot shows the three possible elements of the aspect Task:

• A static task description is shown if the task name (here: 2nd_task_dynform) that is set in the Flowable process model has a description representation in the localization for the language the user has set. Use the key <task name>_description for the task description and <task name>_title for localizing the task name itself.
• Dynamic messages if the Flowable variable appClientsystem_taskMessages of type JSON have been saved. Message can be plane text lines or as unformatted lists. Colors are given by a level parameter.  More details are given here: (link will come soon). 
• A static or dynamic form. The static form is set via Flowable formKey and a form model that was saved with this name.
  The dynamic form can be set by saving the Flowable variable appClientsystem_taskMessages of type JSON. More details are given here:  (link will come soon)

Image Added

My processes 

As of version 2021 Autumn, all processes including follow-ups are listed as soon as they are started by the user. The following properties are affected:

My follow-ups

This view lists the follow-up processes with the following specific properties:

Starting a Process for an Object via a Plug-in Action

The object actions can be extended with a plug-in action that can be offered in the MORE ACTIONS action group. The following example shows the Two step process action, which starts a process based on the twosteptest_proc process model (mapped to Flowable processDefinitionKey) for a single marked object or for multiple selected objects.

As of 2021 Winter, the objects are displayed in the attachment task of the task details for a selected task in the Inbox. 

Image Added

To provide the example Two step process action in a client, import the client plug-in configuration file shown below. To be able to import a settings file, users need an administrative role.
>> Extending Clients with Plug-ins

The twosteptest_proc process model has to be deployed to the Flowable BPM Engine.

{
  "disabled": false,
  "actions": [
    {
      "id": "yuv.custom.action.two.step.multi.label",
      "label": "yuv.custom.action.two.step.multi.label",
      "description": "yuv.custom.action.two.step.multi.description",
      "priority": 0,
      "icon": "<svg height=\"24\" viewBox=\"0 0 24 24\" width=\"24\" xmlns=\"http://www.w3.org/2000/svg\"> <path d=\"M0 0h24v24H0V0z\" fill=\"none\"></path> <path d=\"M4 10h12v2H4zM4 6h12v2H4zM4 14h8v2H4zM14 14v6l5-3z\"></path> </svg>",
      "group": "further",
      "range": "MULTI_SELECT",
      "isExecutable": "(item) => item.id",
      "run": "(selection) => this.http.post('/bpm/processes', {businessKey: selection[0].id, name: selection[0].title || selection[0].id, processDefinitionKey: 'twosteptest_proc', attachments: selection.map((s) => s.id), subject: selection[0].title, variables: [{ name: 'myVariable', type: 'string', value: 'Lorem ipsum' }]},'api-web').then(() => this.util.notifier.success(this.util.translate('yuv.custom.action.two.step.multi.success')))"
    },
    "yuv-download-action",
    "yuv-delete-action",
    "yuv-delete",
    "yuv-upload",
    "yuv-upload-action",
    "yuv-move-action",
    "yuv-move",
    "yuv-follow-up-action",
    "yuv-follow-up",
    "yuv-reference-action",
    "yuv-open-context-action",
    "yuv-open-versions-action",
    "yuv-clipboard-action",
    "yuv-clipboard-link-action"
  ],
  "translations": {
    "en": {
      "yuv.custom.action.two.step.multi.label": "Two step process",
      "description": "yuv.custom.action.two.step.multi.description",
      "priority": 0": "Starts simple process with two steps, also for many objects",
      "iconyuv.custom.action.two.step.multi.success": "<svg height=\"24\" viewBox=\"0 0 24 24\" width=\"24\" xmlns=\"http://www.w3.org/2000/svg\"> <path d=\"M0 0h24v24H0V0z\" fill=\"none\"></path> <path d=\"M4 10h12v2H4zM4 6h12v2H4zM4 14h8v2H4zM14 14v6l5-3z\"></path> </svg>",
      "group": "furtherProcess has started"
    },
    "de": {
      "yuv.custom.action.two.step.multi.label": "Zweischritteprozess",
      "range": "MULTI_SELECT",
      "isExecutable": "(item) => item.idyuv.custom.action.two.step.multi.description": "Startet einen einfachen Prozess mit zwei Schritten, auch für mehrere Prozesse",
      "runyuv.custom.action.two.step.multi.success": "(selection) => this.http.post('/bpm/processes', {businessKey: selection[0].id, name: selection[0].title || selection[0].id, processDefinitionKey: 'twosteptest_proc', attachments: selection.map((s) => s.id), subject: selection[0].title, variables: [{ name: 'myVariable', type: 'string', value: 'Lorem ipsum' }]},'api-web').then(() => this.util.notifier.success(this.util.translate('yuv.custom.action.two.step.multi.success')))"
    },
    "yuv-download-action",
    "yuv-delete-action",
    "yuv-delete",
    "yuv-upload",
    "yuv-upload-action",
    "yuv-move-action",
    "yuv-move",
    "yuv-follow-up-action",
    "yuv-follow-up",
    "yuv-reference-action",
    "yuv-open-context-action",
    "yuv-open-versions-action",
    "yuv-clipboard-action",
    "yuv-clipboard-link-action"
  ],
  "translations": {
    "en": {
      "yuv.custom.action.two.step.multi.label": "Two step process"Prozess wurde gestartet"
    }
  }
}

Handling of Task Forms

As of version 2021 Winter, the Inbox view displays tasks in task forms that can be configured in order to provide a specific form for a specific Flowable task. The configuration can be done via following steps:

• Display the task in the Flowable process modeler and write a technical name into the property FormKey.
• Define your configuration in a JSON file as shown below.
• Save this form using the configuration endpoint in the admin-controller or system-controller of the Web-API Gateway. Use the value of FormKey for the path parameter name of the configuration.
  >> POST /api-web/api/admin/resources/config/{name} or POST /api-web/api/system/resources/config/{name}

The client is calling this configuration file using the corresponding endpoint of the resource-controller of the Web-API Gateway.

Structure of the JSON Configuration File

The JSON format for task forms is the same as used for the object forms. Thus, the complete feature set is supported here as well. The expandable code block below shows an example configuration.

The Flowable variable names are specified as values for the key name. We recommend user task names with a prefix (in the example: 'xyz') for easier localization.

If the variable has not been used in the process before the form is called, the given values are saved to these variables after saving the form.

The property types used in forms for yuuvis® Momentum objects can be used for the Flowable variable types as well. Only the yuuvis® property type decimal is mapped to the Flowable variable type double, and the yuuvis® property type datetime is mapped to the Flowable variable type date.

The yuuvis® table properties are saved as in a variable of type JSON. 

All other attributes given in this example are mostly self-explanatory.

{
  "name": "twosteptest_proc:1st_task",
  "situation": "EDIT",
  "script": "",
  "elements": [
    {
      "name": "core",
      "type": "o2mGroup",
      "elements": [
        {
          "type": "o2mGroup", 
          "layout": {
              "align": "row"
          },
      "yuv.custom.action.two.step.multi.description    "elements": "Starts[
simple process with two steps, also for many objects",   {
   "yuv.custom.action.two.step.multi.success": "Process has started"     },    "type": "deo2mGroup":, {
      "yuv.custom.action.two.step.multi.label": "Zweischritteprozess",       "yuv.custom.action.two.step.multi.descriptionname": "StartetxyzSimplefields",
 einen einfachen Prozess mit zwei Schritten, auch für mehrere Prozesse",     "layout": {
                  "yuv.custom.action.two.step.multi.successalign": "Prozess wurde gestartet""column"
          }   } }

Handling of Task Forms

As of version 2021 Winter, the Inbox view displays tasks in task forms that can be configured in order to provide a specific form for a specific Flowable task. The configuration can be done via following steps:

• Display the task in the Flowable process modeler and write a technical name into the property FormKey.
• Define your configuration in a JSON file as shown below.
• Save this form using the configuration endpoint in the admin-controller or system-controller of the Web-API Gateway. Use the value of FormKey for the path parameter name of the configuration.
  >> POST /api-web/api/admin/resources/config/{name} or POST /api-web/api/system/resources/config/{name}

The client is calling this configuration file using the corresponding endpoint of the resource-controller of the Web-API Gateway.

Structure of the JSON Configuration File

The JSON format for task forms is the same as used for the object forms. Thus, the complete feature set is supported here as well. The expandable code block below shows an example configuration.

The Flowable variable names are specified as values for the key name. We recommend user task names with a prefix (in the example: 'xyz') for easier localization.

If the variable has not been used in the process before the form is called, the given values are saved to these variables after saving the form.

The property types used in forms for yuuvis® Momentum objects can be used for the Flowable variable types as well. Only the yuuvis® property type decimal is mapped to the Flowable variable type double, and the yuuvis® property type datetime is mapped to the Flowable variable type date.

The yuuvis® table properties are saved as in a variable of type JSON. 

All other attributes given in this example are mostly self-explanatory.

{
  "name": "twosteptest_proc:1st_task",
  "situation": "EDIT",
  "script": "",
  "elements": [
    {
      "name": "core",
      "type": "o2mGroup",
      "elements": [,
              "elements": [
                {
                  "name": xyzDatetime",
                  "type": "datetime",
                  "required": false,
                  "cardinality": "single",
                  "readonly": false
                },
                {
                  "name": "xyzDate",
                  "type": "datetime",
                  "required": false,
                  "cardinality": "single",
                  "readonly": false,
                  "resolution": "date"
                },
                {
                  "name": "xyzInteger",
                  "type": "integer",
                  "required": false,
                  "cardinality": "single",
                  "readonly": false                },
                {
                  "name": "xyzDecimal",
                  "type": "decimal",
                  "required": false,
                  "cardinality": "single",
                  "readonly": false
                },
                {
                  "name": "xyzString",
                  "type": "string",
                  "required": false,
                  "rows": 1,
                  "readonly": false                },
                {
                  "name": "xyzStringmultirow",
                  "type": "string",
                  "required": false,
                  "rows": 3,
                  "readonly": false
                }
              ]
            },
            {
              "type": "o2mGroup", 
              "name": "xyzComplexfields", 
              "layout": {
                  "align": "column"
              },
              "elements": [
                {
                  "name": "xyzEmail",
                  "type": "string",
                  "cardinality": "single",
                  "readonly": false,
                  "classifications": ["email"]
                },
                {
                  "name": "xyzUrl",
                  "type": "string",
                  "required": false,
                  "readonly": false,
                  "classifications": ["url"]
                },
                {
                  "name": "xyzPhone",
                  "type": "string",
                  "required": false,
                  "readonly": false,
                  "classifications": ["phone"]
                },
                {
                  "name": "xyzUser",
                  "type": "string",
                  "required": false,
                  "cardinality": "single",
                  "readonly": false,
                  "classifications": ["id:organization"]
                },
                {
                  "name": "xyzReference",
                  "type": "string",
                  "required": false,
                  "cardinality": "single",
                  "readonly": false,
                  "classifications": ["id:reference[]"],
                  "label": "Reference"
                },
                {
                  "name": "xyzCatalogcustom",
                  "type": "string",
                  "required": false,
                  "cardinality": "single",
                  "readonly": false,
                  "classifications": ["custom:catalog[/api-web/api/dms/catalogs/tenMytenant:processstatus]"],
                  "label": "Catalog status"
                },
                {
                  "name": "xyzBroc:boolean",
                  "type": "boolean",
                  "required": false,
                  "readonly": false,
                  "label": "Boolean"
                }
              ]
            }
          ]
        },
        {
          "name": "xyzTest_table",
          "type": "table",
          "required": false,
          "readonly": false,
          "label": "Notices",
          "description": "List of notices",
          "classifications": "sortable",
          "elements": [
            {
              "name": "xyzColumn_string",
              "type": "string",
              "required": false,
              "cardinality": "single",
              "readonly": false,
              "label": "String"
            },
            {
              "name": "xyzColumn_date",
              "type": "datetime",
              "required": false,
              "cardinality": "single",
              "readonly": false,
              "label": "Date"
            },
            {
              "name": "xyzColumn_user",
              "type": "string",
              "required": false,
              "cardinality": "single",
              "classifications": ["id:organization"],
              "readonly": false,
              "label": "User"
            },
            {
              "name": "xyzColumn_boolean",
              "type": "boolean",
              "required": false,
              "cardinality": "single",
              "readonly": false,
              "label": "Boolean"
            }
          ]
        }
      ]
    },
    {
      "name": "data",
      "type": "o2mGroupStack",
      "elements": [],
          "layout": { "align": "column" },
          "label": "Table group"
    }
  ]
}

Note: The key-value pair  "classifications": ["sortable"] allows the user to sort the table rows manually by drag & drop.

The following client-specific Flowable variables are available:

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

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

"taskMessages": [
  {
    "message": "messageWithoutColor"
  },
  {
    "level": "error",
    "message": "messageError",
    "type": "ul"
  },
  {
    "level": "warning",
    "message": "messageWarning",
    "type": "ul"
  },
  {
    "level": "info",
    "message": "messageError"
  },
  {
    "message": "Not translated message"
  }
] 

{
  "action": "save",
  "variables": [
    {
      "name": "appClientsystem_taskMessages",
      "type": "json",
      "value": [ 
        {
          "message": "messageWithoutColor"
        },
        {
          "level": "error",
          "message": "messageError",
          "type": "ul"
        },
        {
          "

...

level": "

...

warning",

...

          "

...

message": 

...

"messageWarning",
          "

...

type": "

...

ul"
        

...

},
        {
 

...

...

        "level": "info",
  

...

        "message": "messageError"
     

...

...

  },
        {
    

...

...

...

"message": "Not translated message"
    

...

...

   }
      ]
    }
  

...

]
}

"taskForm": {
    "schemaProperties": [
      "tenMytenant:strsingle",
      "tenMytenant:datesingle"
    

...

]

"taskForm": 

...

{
    "model": {
            "

...

name": "

...

twosteptest_proc:2nd_task",

...

            "

...

situation": 

...

"EDIT",
            

...

"script": "",
            "elements": 

...

[
 

...

...

   {
                "

...

name": "

...

core",

...

                "

...

type": 

...

"o2mGroup",

...

...

"

...

elements": [

...

                  {

...

...

                   "

...

type": "

...

o2mGroup", 
               

...

     "layout": {
          

...

...

"

...

align": "

...

row"

...

...

 },
                    "

...

elements":

...

 [
                    {
    

...

...

                   "

...

type": 

...

"o2mGroup", 
              

...

          "name": "twosteptest_proc:simplefields",
     

...

                   "

...

layout": {

...

...

...

        "align": "column"
         

...

...

              },
    

...

...

                   "

...

elements": 

...

[
                   

...

       {
         

...

                   "name": "

...

twosteptest_proc:date",
                            "

...

labelkey": "

...

Date",
                  

...

...

         "type": "datetime",
        

...

...

                   "

...

required": false,
               

...

             "cardinality": "single",
         

...

                   "

...

readonly": 

...

false,
        

...

...

                   "

...

resolution": 

...

"date"
                  

...

...

       },
           

...

...

              {
  

...

...

           "name": 

...

"twosteptest_proc:string",
             

...

               "type": "

...

string",
            

...

...

               "cardinality": "

...

single"

...

,

...

...

...

        "required": false,
      

...

...

...

      "rows": 1,
         

...

                   "

...

readonly": 

...

false                
  

...

...

...

...

   }
               

...

...

        ]
          

...

...

...

}

...

...

...

]
            

...

...

     }
             

...

...

  ]
              }
 

...

...

          ]
     ]

{
  "

...

action": 

...

"save",
  "variables": [
    

...

{
      "

...

name": 

...

"

...

appClientsystem_taskForm"

...

,
      

...

"type": "json",
      "value": { 
       

...

...

"schemaProperties": [
          "

...

tenMytenant:strsingle",
          "tenMytenant:datesingle"
       

...

 ]
      }
    }
  ]
}

{
  "

...

action": 

...

"save",
  "variables": [
    {
      

...

"

...

name": 

...

"appClientsystem_taskForm",
      

...

"type": "json",
      

...

"

...

value": 

...

{ 
        "model":
      

...

    {
            

...

"name": "twosteptest_proc:2nd_task",
            

...

"

...

situation": "

...

EDIT",

...

            "

...

script": "

...

",
            

...

"elements": 

...

[
              {
   

...

...

...

"name": 

...

"core",
                

...

"

...

type": 

...

"

...

o2mGroup",
                "elements": [
 

...

                 {
                    "

...

type": "

...

o2mGroup", 
                    "

...

layout":

...

 {
                        "

...

align": 

...

"row"
                   

...

 },
                    "

...

elements":

...

 [
                    {
    

...

...

                   "

...

type": "

...

o2mGroup", 
               

...

...

"name": "twosteptest_proc:simplefields",
     

...

                   "

...

layout": {

...

...

...

        "align": "column"
         

...

...

              },
    

...

...

                   "

...

elements": [

...

...

...

    {
              

...

...

...

            "name": "twosteptest_proc:date",
   

...

...

        "labelkey": "Date",
         

...

                   "type": "

...

datetime",
                            "required": false,
                  

...

...

         "cardinality": "single",
        

...

...

...

  "readonly": false,
           

...

...

    "resolution": "date"
     

...

...

...

   },
       

...

...

...

...

      {
    

...

...

...

...

           "

...

name": "

...

twosteptest_proc:string",
             

...

               "

...

type": "string",

...

...

               "

...

cardinality": "

...

single",
              

...

...

...

"required": false,
              

...

...

...

"

...

rows": 

...

1,
       

...

...

...

       "readonly": false     

...

...

...

...

...

      }
        

...

...

...

]
               

...

       }
       

...

...

            ]

...

...

     }
         

...

...

      ]
        

...

...

     }
         

...

...

  ]
          }
 

...

...

    }
    }
  

...

]
}

The code clock below shows an example for the Flowable representation of a yuuvis table property. Tables are only shown up in a form where the types of the column properties are added as seen above.

    {
      "name": "xyzColumn_boolean",
       twosteptest_proc:test_table",
      "type": "booleanjson",
      "value": [
      "required": false,    {
          "cardinalitytwosteptest_proc:column_string": "single",
   abc",
          "readonlytwosteptest_proc:column_date": false,
   "2021-09-07T17:31Z",
          "labeltwosteptest_proc:column_user": "Boolean"2685df3a-1cf8-4da3-968c-0a4a10b48921",
          "twosteptest_proc:column_boolean": true
 }       }
   ]   ],
     } "scope": "global"
    ]
    },
    {
      "name": "data",
      "type": "o2mGroupStack",
      "elements": [],
          "layout": { "align": "column" }},

Start Forms for Starting Processes

As of version 2021 Winter, a plug-in action is available that allows to start a process via a start form as shown in the example screenshot. If all form fields are filled with valid values, the Start button is enabled. Both form fields User and Comment are required variables for starting a process. The code block below shows the corresponding plug-in configuration offering a start form with the name taskform in the object action view (displayed after a click on the object action Test process with role assignment).

Image Added

{ 
  "disabled": false,
  "actions": [
    {
      "id": "yuv.custom.action.userGroupAssignment.multi.label",
          "label": "Table group"yuv.custom.action.userGroupAssignment.multi.label",
    }   ]
}

The code clock below shows an example for the Flowable representation of a yuuvis table property. Tables are only shown up in a form where the types of the column properties are added as seen above.

    {"description": "yuv.custom.action.userGroupAssignment.multi.description",
      "priority": 1,
      "name": "twosteptest_proc:test_table",
      "type": "jsonicon": "<svg height=\"24\" viewBox=\"0 0 24 24\" width=\"24\" xmlns=\"http://www.w3.org/2000/svg\"> <path d=\"M0 0h24v24H0V0z\" fill=\"none\"></path> <path d=\"M4 10h12v2H4zM4 6h12v2H4zM4 14h8v2H4zM14 14v6l5-3z\"></path> </svg>",
      "valuegroup": [
        {"further",
           "twosteptest_proc:column_string"range": "abcMULTI_SELECT",
 
        "twosteptest_proc:column_date"isExecutable": "2021-09-07T17:31Z",
(item) => item.id",
         "twosteptest_proc:column_user": "2685df3a-1cf8-4da3-968c-0a4a10b48921",
"buttons": {
         "twosteptest_proc:column_boolean": true"finish": "yuv.custom.action.userGroupAssignment.multi.start"
      },
  }    "plugin": {
 ],       "scopecomponent": "yuv-object-form",
        "globalinputs": {
     },

Start Forms for Starting Processes

As of version 2021 Winter, a plug-in action is available that allows to start a process via a start form as shown in the example screenshot. If all form fields are filled with valid values, the Start button is enabled. Both form fields User and Comment are required variables for starting a process. The code block below shows the corresponding plug-in configuration offering a start form with the name taskform in the object action view (displayed after a click on the object action Test process with role assignment).

Image Removed

{ 
  "disabled": false,
  "actions": [
    {
      "id": "yuv.custom.action.userGroupAssignment.multi.label",
      "label": "yuv.custom.action.userGroupAssignment.multi.label",
      "description": "yuv.custom.action.userGroupAssignment.multi.description",
      "priority": 1,
      "icon": "<svg height=\"24\" viewBox=\"0 0 24 24\" width=\"24\" xmlns=\"http://www.w3.org/2000/svg\"> <path d=\"M0 0h24v24H0V0z\" fill=\"none\"></path> <path d=\"M4 10h12v2H4zM4 6h12v2H4zM4 14h8v2H4zM14 14v6l5-3z\"></path> </svg>",
      "group": "further",
      "range": "MULTI_SELECT",     "__initOptions": "this.http.get(`/resources/config/taskform`, 'api-web').then((res) => {component.cmp.options = {formModel: res.data.tenant, disabled: false}})",
          "__init": "() => parent.finished.subscribe((event) => { var selection = parent.selection; var cmp = component.cmp; this.http.post('/bpm/processes',{businessKey: selection[0].id,name: selection[0].title || selection[0].id,processDefinitionKey: 'userGroupAssignment',attachments: selection.map((s) => s.id),subject: selection[0].title,variables: [{ name: 'user', type: 'string', value: cmp.formData.user || '' },{ name: 'comment', type: 'string', value: cmp.formData.comment || '' },{ name: 'nextUserAssignee', type: 'string', value: 'fakeUserId' },{ name: 'nextGroupAssignee', type: 'string', value: 'YUUVIS_MANAGE_SETTINGS' }]},'api-web').then(() => this.util.notifier.success(this.util.translate('yuv.custom.action.userGroupAssignment.multi.success')))})"
        },
        "outputs": {
          "isExecutablestatusChanged": "(itemstatus) => item.id",{ parent.disabled = status.invalid; }"
      "buttons": { }
      }
"finish": "yuv.custom.action.userGroupAssignment.multi.start"   },
   }, "*"
  ],
  "plugintranslations": {
        "componenten": "yuv-object-form",{
        "inputs"yuv.custom.action.userGroupAssignment.multi.label": {"Test process with role assignment",
      "__initOptionsyuv.custom.action.userGroupAssignment.multi.description": "this.http.get(`/resources/config/taskform`, 'api-web').then((res) => {component.cmp.options = {formModel: res.data.tenant, disabled: false}})",
   Starts a process with two tasks. Second task assigned to YUUVIS_MANAGE_SETTINGS",
      "__init": "() => parent.finished.subscribe((event) => { var selection = parent.selection; var cmp = component.cmp; this.http.post('/bpm/processes',{businessKey: selection[0].id,name: selection[0].title || selection[0].id,processDefinitionKey: 'userGroupAssignment',attachments: selection.map((s) => s.id),subject: selection[0].title,variables: [{ name: 'user', type: 'string', value: cmp.formData.user || '' },{ name: 'comment', type: 'string', value: cmp.formData.comment || '' },{ name: 'nextUserAssignee', type: 'string', value: 'fakeUserId' },{ name: 'nextGroupAssignee', type: 'string', value: 'YUUVIS_MANAGE_SETTINGS' }]},'api-web').then(() => this.util.notifier.success(this.util.translate('yuv.custom.action.userGroupAssignment.multi.success')))})"yuv.custom.action.userGroupAssignment.multi.success": "Process has started"
    }
  }
}

The following code block shows the form definition for the plug-in action example displayed above:

 {
  "description": "This form is used during process start and both task of process userGroupAssignment",
  "name": "taskform",
  "situation": "EDIT",
  "elements": [
    {
      "name": "core",
      "type": "o2mGroup",
      "elements": [
        },{
          "outputsname": {"user",
          "statusChangedlabelkey": "(status) => { parent.disabled = status.invalid; }""userGroupAssignment:user",
          "type": "string",
  }       }     }"cardinality": "single",
    "*"   ],   "translationsrequired": {
true,
   "en": {       "yuv.custom.action.userGroupAssignment.multi.labelreadonly": "Testfalse,
process with role assignment",       "yuv.custom.action.userGroupAssignment.multi.description"classifications": ["id:organization"Starts]
a process with two tasks. Second task assigned to YUUVIS_MANAGE_SETTINGS" },
      "yuv.custom.action.userGroupAssignment.multi.success": "Process has{
started"     }   }
}

The following code block shows the form definition for the plug-in action example displayed above:

 {   "descriptionname": "Thiscomment",
form is used during process start and both task of process userGroupAssignment",   "namelabelkey": "taskformuserGroupAssignment:comment",
          "situationtype": "EDITstring",
  "elements        "required": [true,
    {       "namereadonly": "core"false,
          "typerows": "o2mGroup", 3
        }
  "elements": [   ],
     { "layout": {
        "namealign": "usercolumn",
      }
   "labelkey": "userGroupAssignment:user", },
    {
      "typename": "stringdata",
       "label": "data",
      "cardinalitytype": "singleo2mGroupStack",
      "elements": []
  "required": true, }
         "readonly": false,
          "classifications": ["id:organization"]
        },
        {
          "name": "comment",
          "labelkey": "userGroupAssignment:comment",
          "type": "string",
          "required": true,
]
}

As of version 2021 Winter, the value multi is supported as an alternative for the value single of the property cardinality in order to configure a multi-value field:

• If the cardinality of a field is single, its type is mapped to the type of the Flowable variable with the same name.
• If the cardinality of a field is multi, the Flowable variable type is set to JSON and its values are listed in the specified JSON structure.

Custom Confirm Actions

As of version 2022 Spring, it is possible to configure custom confirm actions for BPM tasks. These custom confirm actions trigger optional forms that give users the possibility to provide further data that is relevant only for this particular outcome. The so-called outcomes can be configured in static BPM form files as well as in dynamic ones:

{
  "model":
  {
    ...
  },
  "outcomes": [
    {
         "readonlyname": false,
          "rows": 3
     "taskflow_finish",
  }       ]"variable": "status",
      "layoutvalue": {"close"
    },
   "align": "column" {
      }
"name": "taskflow_forward",
   },   "secondary": true,
{       "namevariable": "datastatus",
      "labelvalue": "dataopen",
      "typemodel": "o2mGroupStack",taskflow-form-forward"
    }
    "elements": []
    }
  ]
}

As of version 2021 Winter, the value multi is supported as an alternative for the value single of the property cardinality in order to configure a multi-value field:

...

]
}

The outcomes list contains custom task confirm actions that will be displayed as buttons in the UI instead of the standard confirm button. The order of the buttons is from right to left. The buttons are displayed in the accent color per default. The outcomes section can be used in dynamic action forms as well.