Parameter types

There are three types of parameters:
  • Process parameters only apply to processes that are called in an advanced task, and only have the scope of the process within the task.
  • Task parameters are scoped to an individual task and all processes within that task will see the same value.
  • Global parameters have a scope that covers all tasks.

Parameters and scope

The same name can be used for global, task, and process parameters. When a parameter is referenced during a task run, MOVEit Automation uses a specific method to select the appropriate parameter to implement.

When a process in an advanced task references a parameter, the following occurs in this order:
  1. MOVEit Automation looks for a parameter of that name defined at the process level. If found, that parameter is used.
  2. If the parameter is not found at the process level, MOVEit Automation looks for a task parameter defined with the same name and uses it if available.
  3. If a task parameter is not found, MOVEit Automation looks for a global parameter defined with the same name and uses it if available.
  4. If no parameter with that name is available, MOVEit Automation uses an empty string.
Similarly, when a regular or sync task references a parameter, the following occurs in this order:
  1. MOVEit Automation looks for a parameter of the same name defined at the task level. If found, that parameter is used.
  2. If a task parameter is not found, MOVEit Automation looks for a global parameter defined with the same name and uses it if available.
  3. If no parameter with that name is available, MOVEit Automation uses an empty string.

Built-in scripts and secure parameters

Certain built-in scripts parameters require user input to function correctly. Some of these parameters must be secured while others cannot be secured.
  • The parameters for mandatory secure fields, such as built-in script parameters with password values, must be secure.
  • Some other fields, including custom parameters and the HTTP_Post_URL, HTTP_URL, HTTP_Post_Data, HTTP_ExtraFields, and CommandLineApp_AppParms built-in parameters can optionally use secure parameters.
  • Fields with drop-down lists that present the user with predefined values cannot be secure parameters.
  • The remaining fields in built-in scripts cannot be secure parameters.
Note: Secure parameters are only available with 2022.1 or later.

Parameters and lifetime

Task and process parameters are set in a task and can be changed during a task run. However, at the end of the task run, the parameter changes are not saved.

Similarly, global parameters can be changed during a task run but the changes are not saved at the end of the task run. The original value of the global parameter will be used the next time a task is run.