...
You can embed Universal Controller variables in the script content. Embedded variables are resolved at trigger/run time before the script is sent to an Agent.
...
Note | ||
---|---|---|
| ||
You also can enter a script directly into a Universal Template, but you cannot select a stored script. |
...
There are five types of scripts:
Script | For use in Windows or Linux/Unix tasks. |
---|---|
SAP Definition | For use in SAP tasks. |
UDM Script | For use in UDM File Transfer tasks. |
Web Service Payload | For use in Web Service tasks. |
Data | For use in a script or task (see Data Scripts, below). |
...
- Content of a Script specified in the Script field in a Linux/Unix or Windows task.
- Content of a Data Script.
- Universal Template Script (Script, Linux/Unix Script, or Windows Script field).
...
To use a Data Script with a task, embed the Data Script in any of the following:
- Command field in a Linux/Unix or Windows task
- Parameters field in a Linux/Unix or Windows task
Note | ||
---|---|---|
| ||
Although you can embed a Data Script in the Command field or Parameters field of a Linux/Unix or Windows task, only scripts with Script Type = Script can be referenced in a Linux/Unix or Windows task; that is, it is the only type of script that is available for selection in the Linux/Unix or Windows task Script field. |
...
To embed a Data Script, use the following Script Function:
Name | Description | Syntax |
---|---|---|
Used for embedding the path to a Data Script. |
|
...
For every Data Script embedded in a Data Script, the Controller will resolve ${_scriptPath('script_name')
} (if Resolve UAC Variables is enabled for the Data Script), and look for additional Data Script references (and Resolvable Credentials references). This process will continue until no additional Data Script references are found.
...
UAG will replace any tokens within the Script Content, Universal Template Script, Command, or Parameters with the appropriate file path associated with the Data Script Content. UAG also will replace any tokens within each Data Script Content.
Additionally, for a Universal Template, you can create a Field of Type = Script, which lets you select or create Data Scripts. The Controller will create a variable for the Data Script Field, which you can embed in the Universal Template script using the Script Functions. This also lets you change Scripts when you run a Universal Task based on the Universal Template.
...
For every embedded Data Script, the Execution User must have Execute permission for the Data Script; otherwise, the task instance will transition to the Start Failure status with one of the following status descriptions:
...
Creating a Script
Step 1 | From the Automation Center navigation pane, select Other > Scripts. The Scripts list displays a list of all existing scripts. |
---|---|
Step 2 | Enter / select Details for a new script, using the field descriptions below as a guide.
To display more of the Details fields on the screen, you can either:
|
Step 3 | Click a button. The script is added to the Controller database, and all buttons and tabs in the Script Details are enabled. |
Note | ||
---|---|---|
| ||
To open an existing record on the list, either:
|
Anchor | ||||
---|---|---|---|---|
|
...
For information on how to access additional details - such as Metadata and complete database Details - for Scripts (or any type of record), see Records.
Anchor | ||||
---|---|---|---|---|
|
...
Field Name | Description | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Details | This section contains detailed information about the Script. | ||||||||||||||||
Name |
| ||||||||||||||||
Version |
| ||||||||||||||||
Description |
| ||||||||||||||||
Member of Business Services |
| ||||||||||||||||
| Type of script:
| ||||||||||||||||
| Controls whether or not the Script will be parsed in pursuit of Universal Controller variables. It allows the Controller to avoid the overhead of parsing a Script that does not contain variables.
| ||||||||||||||||
|
For UDM Scripts, Source and Destination credentials are available for use. The credentials can be coded into the UDM script using the following File Transfer variables: The variables will be resolved by UDM internally. The following example illustrates the correct way to code them:
| ||||||||||||||||
Metadata | This section contains Metadata information about this record. | ||||||||||||||||
UUID | Universally Unique Identifier of this record. | ||||||||||||||||
Updated By | Name of the user that last updated this record. | ||||||||||||||||
Updated | Date and time that this record was last updated. | ||||||||||||||||
Created By | Name of the user that created this record. | ||||||||||||||||
Created | Date and time that this record was created. | ||||||||||||||||
Buttons | This section identifies the buttons displayed above and below the Script Details that let you perform various actions. | ||||||||||||||||
Save | Saves a new script record in the Controller database. | ||||||||||||||||
Save & New | Saves a new record in the Controller database and redisplays empty Details so that you can create another new record. | ||||||||||||||||
Save & View | Saves a new record in the Controller database and continues to display that record. | ||||||||||||||||
New | Displays empty (except for default values) Details for creating a new record. | ||||||||||||||||
Update |
| ||||||||||||||||
| Allows you to upload a script from the local file system and place it in the Content field (see Uploading a Script, below). | ||||||||||||||||
Copy | Creates a copy of this script, which you are prompted to rename. | ||||||||||||||||
Delete |
| ||||||||||||||||
Refresh | Refreshes any dynamic data displayed in the Details. | ||||||||||||||||
Close | For pop-up view only; closes the pop-up view of this task. | ||||||||||||||||
Tabs | This section identifies the tabs across the top of the Script Details that provide access to additional information about the script. | ||||||||||||||||
Tasks | Lists of all tasks using this script. | ||||||||||||||||
Notes |
| ||||||||||||||||
Versions |
|
...
Step 1 | Click the Upload Script button. The Script File Uploader pop-up displays. |
---|---|
Step 2 | Click the Choose File button and select a script from the local file system. |
Step 3 | From the Select file encoding drop-down list, select the character set of the script:
|
Step 4 | Click the Submit button to add the script to the Content field. |
...