Service Tasks

PRIMEUR Data One Workflow Templates can be modeled using a palette of BPMN service tasks. In the context of PRIMEUR Data One, these widgets are referred to as Service tasks.

Warning!

The configuration must be entered in the Service task property screen (the More section of column BPMN-Diagram). In this section, the Throw exception property is always present. When checked, if an error occurs in the Service task, the error will block the entire workflow.

Primeur can provide additional Service tasks with a separate license.

Service tasks are the business components of every workflow template. They are the entities performing every core operation or action.

Service tasks are listed in Design → Workflows → Shape repository:

Depending on what they are supposed to do, on the duration of the operation they must perform and on the server that is responsible to execute the task, they can be divided in two categories:

1. Normal Service Tasks
2. Triggerable Service Tasks

From an end-user point of view there is no actual difference between Normal Service Tasks and Triggerable Service Tasks, the only difference is in the architectural behavior.

Head over to the next pages to know more about Normal and Triggerable Service Tasks.