Triggers

Each workflow template is associated with a trigger, which links a contract action to a specific type of event - such as the arrival of a new file, a scheduled time, or other predefined criteria.

The association chain works as follows:

• Each workflow template has a trigger.

• Each contract action is associated with a trigger.

• Each contract action is associated with a workflow template that has the same trigger.

This structure ensures that when a specific action occurs, the appropriate workflow template is activated based on its predefined trigger conditions.

Several trigger types exist, each designed to initiate data transfer under specific events:

• Time: the action starts at scheduled intervals or specific times, such as daily at 6 a.m.

• OnDemand: the action starts through a direct REST API invocation.

• Incoming transfer: the action starts when a file is completely transferred to a VFS.

• Incoming update metadata: the action starts when a file metadata is modified through a REST API invocation.

• New File: the action starts when the file is written on the VFS specified in the contract.

• Outgoing transfer: the action starts when a file is completely transferred from a VFS to its final destination.

• VirtualBox bind: the action starts when a virtual box is bound to a file.

• VirtualBox unbind: the action starts when the virtual box is unbound from a file.

• OnMessage: the actions execution starts when a JMS message arrives.

Each trigger type can have associated execution variables, which are added at runtime. For example, in the New File trigger, an execution variable named file of type FileDetail is added. Its attributes are set based on the information sent from the event that initiated the trigger.