Variables

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 will be initialized in the contract.

Let's make a quick analysis of the system_newFile_push system workflow template, which handles the following scenario:

1. Data Mover receives a generic or specific file.

2. Data Mover either renames the file and sends it to the intended recipient or sends the file directly.

Going to Design → Workflows → system_newFile_push → View Workflow, these variables are 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 determines the files eligible for action; for example, it can be set to process only filenames containing 2025.

• 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 Execution queue variable is above the Actions section, in the Name and Description area. This corresponds to the jobManagerPriorityQueueName variable in the workflow.