Comment:
Published by Scroll Versions from space WDESIGNER and version 24.0
Page properties
id
bpmn_elements_general
Element
Description
A User Task waits for an external trigger to arrive which is released by human action, for example after a form has been filled. If the process execution reaches a user task, the process stays in a wait state until a specific message is received by the engine, which triggers continuation of the process.
Attributes
Name
Description
Form (see Particularity)
Trigger Events (see Particularity)
Symbol Type
Particularity
Form: Use the attribute Form in the Attributes Panel to select one of your forms. The drop-down list contains all forms that are available in the current service. When you select a form, the icon appears. If you click on this icon, the related form opens in a new window.
Trigger Events: Use the attribute Trigger Events to define which button of a form associated to the element triggers the default process flow of a BPMN process.
State
Waiting_for_<name of the user task with underscores>, e.g. Waiting_for_User_Task
Execution
Name
Parameters
Type
Direction
Description
API
Get Data
return
Any
out
Executed before showing the form. Default type of the output parameter is Any but you can also use your own Library or Data Model class.
If a form is linked to a User Task, the form type is automatically determined as type of return. In this case, the type is read-only.
GET /{id}/<name of the task with underscores> GET /{id}/User_Task
On Exit
message
Any
in
Executed after having displayed the form. Default type of the input parameter is Any but you can also use your own Library or Data Model class.
If a form is linked to a User Task, the form type is automatically determined as the type of message. In this case, the type is read-only.
POST /{id}/<name of the task with underscores> POST /{id}/User_Task