Actions, triggers and workflows
Before learning how to create a contract in Data Mover, it's important to understand that each contract must have one or more associated actions. These actions define contract details such as the folder in the data producer's Virtual File System (VFS) from which Data Mover will retrieve files, the types of files to be retrieved or sent, the timing of when the action should be performed, the email address to which confirmation messages should be sent, and so on.
Actions are triggered by events defined in a workflow, which must be associated with the contract. Three trigger types exist:
the arrival of a file
a specific time
an on-demand trigger via API
Contracts and workflows are closely related: contracts specify where actions should be performed, while workflows dictate which actions should be taken.
Data Mover offers a variety of workflow templates that guide you on which actions to take following an event.
Workflow templates are explained in detail in the Workflow Templates section. To get started, keep in mind the following key points:
For input and output contracts, you must use one of the System workflow templates provided by Primeur.
For mediation contracts, you must design a Workflow template.
There are additional workflow template types available, but for now, let's concentrate on these two types.
This diagram summarizes the above concepts. Input, mediation, and output contracts can each have multiple actions, and each action must have its own workflow template, trigger type, and variables.
Last updated