# 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.

<figure><img src="/files/8LXbpOwGTAIsVJsuf3TR" alt="" width="446"><figcaption></figcaption></figure>

Going to **Design** → **Workflows** → **system\_newFile\_push** → **View Workflow**, these variables are listed in the **Variables** panel on the right:

* Source Virtual Path <mark style="color:red;">**\***</mark> ![](/files/Jt5PrE4B2sxFjVMt29Oe)
* NewFileFilter ![](/files/z0jAk8o7nAPtCp1dDfPA)
* systemEnableLogDebugToFile ![](/files/t7gGEKxYI4ZYWhxDtUOr)
* systemErrorHandlingWorkflowTemplateName ![](/files/TI6Hdjmc3mYuXEnZvDZ7)
* jobManagerPriorityQueueName ![](/files/mNZAiSta4mPbL0xxizu2)
* cluster <mark style="color:red;">**\***</mark>
* spPush\_remotePath <mark style="color:red;">**\***</mark>
* spPush\_transferProfile <mark style="color:red;">**\***</mark>
* spPush\_resourceProfile
* spPush\_renameFile

Mandatory variables have a <mark style="color:red;">**\***</mark> red asterisk.\
Trigger-dependent variables have a ![](/files/69CAaW01AYNui4D2Zpcc) yellow lightning bolt.  ***(specificare meglio questo concetto)***

These variables must be configured appropriately in the corresponding fields of the contract action using the **system\_newFile\_push** workflow template.&#x20;

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.&#x20;
* 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.&#x20;
* spPush\_remotePath **\***: this is the remote path where the file 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.&#x20;
* File resource: this is the resource profile to apply when sending the file. It corresponds to the spPush\_resourceProfile variable in the workflow.&#x20;
* 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.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.primeur.com/data-mover-1.21/workflow-templates/variables.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.