A form definition is stored for each of the 4 process steps.

Opening the form editor

This form will later be offered to the respective agent (in his process role) for editing this process step.

For this purpose, the respective process step is marked in the process graphic and its properties are edited in the right area.

Via the function Display the form editor for the selected process step is opened:

Add fields

The form editor offers a toolbox with design elements as well as the attributes of the model type (ticket). These can be dragged into the form:

Remove fields

To remove an element from the form, it is put back using drag and drop.

Edit fields

By double-clicking on a form field, its properties can be edited. In particular, annotations for visibility can be selected here, in order to present a field as read-only or as a mandatory field, if necessary.

Using form templates

The forms for the further process steps are often based on the previous ones. Therefore, existing forms can be selected as templates and thus copied:

This simplifies the creation of multiple forms with similar content.

Example form

The execution of the process takes place by displaying the respective active task (the process step) to the users with the corresponding process role in their task list (a kind of "inbox").

If a user then selects this task for processing, the form defined at the process step is offered to him for processing.

After making the necessary entries or taking note of the displayed contents, the agent can complete this task and pass it on to the next process step.

If there are several possible subsequent steps in the process ("gateway"), the agent selects the subsequent step and thus decides which process path is to be followed.