The expert mode allows to access more settings and create even more advanced workflows, but at the cost of an increased complexity. To enable the expert mode, just flip the switch at the bottom of the page in the modeler. The next element selected will then appear with the additional options and parameters.


Warning: the expert mode allows to build much more advanced workflows, but also makes it possible to set incorrect parameter or settings and thus to deploy workflows that will crash when running an instance. It is highly recommended to test your workflows before making them available to the end users.



Forms


The first thing the expert mode enables is to use custom forms for the start event and for user tasks. Building forms allow to display or request information from the end user when starting or taking action on a workflow.




To build a form, click on the tab “Forms” in the configuration panel. By default, only the list of form fields is displayed. Once a form field is selected, the parameters of this field appear below.


Four buttons allow to manage form fields:

  •  : move the selected field one step down in the list.

  •  : move the selected field one step up in the list.

  • : delete the selected field.

  • : add a new field.



The different types of fields that can be added are:

  • Label

  • Text input

  • Number input

  • Date input

  • Boolean input

  • List

  • Buttons




1 - Label

A label is a simple line or paragraph of text displayed in the form and that cannot be edited or interacted with.

The following settings need to be configured:

  • ID: the ID of the field.

  • Type: the type of field. The value to select for the label is Label.

  • Default value: the text to display in the form.



2 - Text field


A text input allows users to input unrestricted text. 



The following settings need to be configured:

  • ID: the ID of the field.

  • Name: the title of the input field in the form.

  • Variable: the variable in which the text entered by the user will be stored. Has to be unique in the whole workflow.


  • Required: defines whether the user is required to fill the field before submitting the form.

  • Type: the type of field. The value to select for the text input is Text Field.

  • Default value: the default value to set in the text field. It can be left empty.





3 - Number field


A number input is similar to a text field, but only allows users to input numbers. 


The following settings need to be configured:

  • ID: the ID of the field.

  • Name: the title of the input field in the form.

  • Variable: the variable in which the number entered by the user will be stored. Has to be unique in the whole workflow.

  • Required: defines whether the user is required to fill the field before submitting the form.

  • Type: the type of field. The value to select for the number input is Number Field.

  • Default value: the default number to set in the field. It can be left empty.



4 - Date


A date field allows users to input a date. 


The following settings need to be configured:

  • ID: the ID of the field.

  • Name: the title of the input field in the form.

  • Variable: the variable in which the date entered by the user will be stored. Has to be unique in the whole workflow.


  • Required: defines whether the user is required to fill the field before submitting the form.

  • Type: the type of field. The value to select for the date input is Date.

  • Default value: the default date to set in the field, in format “DD/MM/YYYY”. It can be left empty.




5 - Boolean


A boolean input allows users to select either “Yes” or “No” through a switch.





The following settings need to be configured:

  • ID: the ID of the field.

  • Name: the label of the switch field in the form.

  • Variable: the variable in which either “true” or “false” will be stored. Has to be unique in the whole workflow.

  • Type: the type of field. The value to select for the boolean input is Boolean.

  • Default value: the default value to set in the field, in format “true” or “false”. It can be left empty.





6 - Dropdown list


A list allows users to select a value among a set of options.




The following settings need to be configured:

  • ID: the ID of the field.

  • Name: the title of the list in the form.

  • Variable: the variable in which the ID of the value selected will be stored. Has to be unique in the whole workflow.


  • Required: defines whether the user is required to select a value before submitting the form.


  • Type: the type of field. The value to select for the list is Dropdown List.

  • Default value: the ID of the option to be selected by default in the field, in format “true” or “false”. It can be left empty.


  • Values: list of options in the list with the ID to save if selected and the label to display in the form.



7 - User picker


A user picker input users to select one or multiple users from the domain.



The following settings need to be configured:

  • ID: the ID of the field.

  • Name: the label of the field in the form.

  • Variable: the variable in which the list of users IDs will be stored. Has to be unique in the whole workflow.

  • Type: the type of field. The value to select for the user picket is User Picker.

  • Default value: the default value to set in the field, in format “true” or “false”. It can be left empty.



8 - Buttons


Buttons are a special case in form fields and do not work exactly as the other fields do.



By default, a single form field with the ID “btn_submit” is set in the user tasks and start events. This form field defines the button(s) users have to click to take action.



Warning: do NOT delete this field or change its ID. It would create a task with no buttons, and thus no way of taking actions.



The following settings need to be configured:

  • ID: the ID of the field. The value for the buttons should always be btn_submit.

  • Variable: the variable in which the ID of the button picked is saved.
    By default, the result is stored in pt4d_result, which is the variable tested when selecting UserTask.result in a Gateway condition.

  • Type: the type of field. The value for the buttons should always be "Dropdown List".

  • Values: list of buttons with the ID to save if clicked and the label to display in the form.
    Adding new values here will add new buttons to the form. The buttons' colour depend on their ID value:

    • “ok” = green

    • “ko” = red

    • Everything else = blue