Service tasks
Last updated
Last updated
Service tasks define the actions drawn in the workflow template. They can be either standard or triggerable.
Standard service tasks execute and complete the action they are called to perform, and then the workflow continues. For example, the RenameFile service task renames the file. They are documented on the page.
Triggerable service tasks do not perform a specific action, but rather, initiate a request to start an operation. The instance enters a paused state, waiting for a completion notification to trigger it. The spPush service task, for example, delivers a file to a remote host using a specific transport protocol. It sends a request to STENG to initiate the file transfer and then waits. Once the transport finishes, the process is triggered again upon receiving the completion event. They are documented on the page.
When dragging a service task, the fields in the More panel (bottom right) must be filled out. This panel appears when the service task is selected. These fields can be mandatory or optional and are documented on the following pages. The More section always includes the Throw exception property. If this property is checked and an error happens in the service task, it will stop the entire workflow.
Clicking outside the service task (in the white space), the data/fields for the entire workflow template will be shown in a panel on the right.
Primeur can offer additional Service tasks with a separate license.
Service tasks are essential components of every workflow template. They perform the main operations or actions.
Service tasks are listed in Design → Workflows → Shape repository:
The description of how to use service tasks to create workflow templates is on the page and on its subpages.
