Automation Engine Script Guide > Ordered by Function > Script Structure and Processing > :PSET

:PSET

Script statement: Assigns a value to an objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type..

Syntax

:PSET Object variable = Value

Syntax

Description/Format

Object variable

Name of an object variable (starting with the character "&") that should be supplied with a value.

A script variableA placeholder for a value within a script.'s name for the :PSET and :RSET scriptA particular Automation Engine object type. statements is limited to 31 alphanumeric characters (in most other cases script variable names are limited to 32 characters), including the special characters "$", "_", "@", "§" and "#". German Umlauts are not allowed. The first character must not be a number. Variables within the script must always specified with a leading "&" following the variable name!

Format: script variable

Value

Value that should be assigned to the object variable.
Format: script literal, script variable or script function

Comments

Object variables are stored in the Variables & Prompts tabs of objects.

The workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."] containing the jobAn Automation Engine object type for a process that runs on a target system., where :PSET is used, is called processor or parentThere are different ways of activating objects. The originator of an activation is referred to as the superordinate task (parent). See also: Child; Children.

Below are the individual steps of :PSET:

  1. Replaces or adds the object variable in the taskAn executable object that is running. Tasks are also referred to as activities..
  2. Replaces or adds the object variable in the parent.

The modified value only applies for the execution of tasks. It is not permanently stored in the object itself.

The value of the script variable that is set with :PSET are now only be passed on to the next workflow one level above (parent) but not to the top workflow (such as grandparents or great-grandparents etc.).

The value of the script variable that is set with :PSET will never be passed on to a Schedule or Period Container.

The setting "Generate at runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start)." greatly affects objects. Subsequent modifications in object variablesPlaceholder for values that are stored in an object's "Variables & Prompts" tab/section. do not affect the script if it has already been generated.

Note that object variables are not always passed on to tasks. You can define in each object if values can be inherited and which of them should be inherited from the superordinate taskThere are various ways of activating objects. The originator of the activation is referred to as the superordinate task (parent)..

In nested workflows, :PSET does not pass on object variables. These are only replaced or added in the particular workflow which contains the task the script statement :PSET addresses.

Note that inherited object variables that have not been defined in the task itself are only available as long as the task is shown in the Activity Window. If restarted, the job as shown in the example below can only access the object variable &HOST# if file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object). plus workflow are still available in the Activity Window.

Also note that a script, where ACTIVATE_UC_OBJECT as activator of the job is used, will neither be parent nor processor of the job. Therefore, canceling the script will not cancel the job.
On the other hand will canceling of the job in a parent (the workflow containing the job, for example) directly cancel the job itself. The parent-childA subordinate task (such as a task that runs in a workflow).-relationship directly affects the job.

Example

A workflow contains the two objects "MM.GET.FILES" and "MM.END.PROCESSING". The setting "Generate at runtime" has been specified in both objects in order to ensure that their scripts are only generated when it is their turn.

The file transfer checks the environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. and changes the object variable &HOST# if required.

:PSET  &HOST# = "unix01"

 

 

See also:

Script element Description

:RSET

Assigns a value to a script variable and stores it in the activation reportA report provides more detailed information about a task's execution or a component..

:SET

Assigns a value to a script variable.

:SET_SCRIPT_VAR

Sets the values of script variables indirectly.

Script Elements - Script Structure and Processing

About Scripts
Script Elements - Alphabetical Listing

Script Elements - Ordered by Function

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH