Variables

Variables allow the same workflow template to be reused. Workflow templates function differently depending on the variables given.

The variables used in the workflow and in the contract are interconnected. The workflow outlines a sequence of actions triggered by specific events, and the contract establishes the context where those actions will be executed.

In each workflow template, the Variables panel lists the variables that must be configured and will be initialized in the actions of the contract.

Here's a brief analysis of the system_newFile_push workflow template. This template manages the process where Data Mover receives a file - either generic or specific - renames it if necessary, and delivers it to the appropriate recipient.

Going to Design → Workflows → system_newFile_push → View Workflow, you will see these variables listed in the Variables panel on the right:

  • Source Virtual Path *

  • NewFileFilter

  • systemEnableLogDebugToFile

  • systemErrorHandlingWorkflowTemplateName

  • jobManagerPriorityQueueName

  • cluster *

  • spPush_remotePath *

  • spPush_transferProfile *

  • spPush_resourceProfile

  • spPush_renameFile

Mandatory variables have a * red asterisk. Trigger-dependent variables have a yellow lightning bolt.

These variables must be configured appropriately in the corresponding fields of the contract action using the system_newFile_push workflow template.

Going to Design → Contracts and selecting a contract using the system_newFile_push workflow template, the Actions section will list these variables (mandatory variables have an asterisk):

  • Source virtual path *: this is the source virtual path that will receive the file.

  • NewFileFilter: this field applies a filter to the filename. For example, entering 2025, only filenames containing 2025 will be processed.

  • systemEnableLogDebugToFile: this button activates logs.

  • Error handling: this button activates the use of Primeur system workflow templates to manage errors. It corresponds to the systemErrorHandlingWorkflowTemplateName variable in the workflow.

  • cluster *: this is the destination cluster.

  • spPush_remotePath *: this is the remote path where the file triggering this instance will be sent.

  • select remote server *: this is the Client Connection that will be used to send the file to the remote path of the Actor. It corresponds to the spPush_transferProfile variable in the workflow.

  • File resource: this is the resource profile to apply when sending the file. It corresponds to the spPush_resourceProfile variable in the workflow.

  • spPush_renameFile: this is the new filename applied, if renaming is required.

The jobManagerPriorityQueueName variable of the workflow template corresponds to the Execution queue variable in the Name and Description area, above the Actions section.

Last updated