Versions Compared

Old Version 3

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Stonebranch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Universal Templates allows you to create the templates on which Universal Tasks Integrations are based.

Within each Universal Template, you:

  • Enter either:
    • A script that will be executed by any Universal Task based on that Universal Template.A
    • An Extension that will be executed by any Universal Task based on that Universal Template through the Universal Extension framework.
  • Create Fields that the Universal Controller:
    • Assigns matching variables for use in the Universal Template script.
    • Adds matching fields to the Details of any Universal Task that you create based on that Universal Template.

When you create a Universal Template, the Controller creates a Universal Task type, under the Universal Tasks folder in the Automation Center navigation pane, based on that Universal Template.

...

When a Universal Task is run, it executes the script, and the system-assigned script variables are resolved to the user-defined values of their matching fields in the Universal Task instance.

...

Step 1

Create a Universal Template, which includes selecting the type of Agent(s) on which Universal Tasks based on this Universal Template can be run, and a variable prefix used for script variables that you want resolved when a Universal Task executes the script in this Universal Template.

Step 2

Enter a script in the Universal Template that all Universal Tasks based on this Universal Template will execute when they are run.

Step 3

After you have entered/selected any other desired values in the Universal Template Details, save the Universal Template.

Step 4

For each parameter in the script that you want to replace with a variable, create a Universal Template Field of an appropriate Field type. The Controller automatically assigns a variable (format: ops_<Variable Prefix>_<Field Name>) to each Field, using the variable prefix that you specified in Step 1, and will place those Fields in the Details of all Universal Tasks based on this Universal Template.

Step 5

Replace the appropriate parameters in the script with the system-assigned variables.

Step 6

Update the Universal Template. Now that the Universal Template has one or more defined Fields, the Controller creates a Universal Task type for it and adds the Universal Task type to the Automation Center navigation pane. (You must refresh the Automation Center navigation pane in order to see the new Universal Task type.

Step 7

Create a Universal Task for that Universal Task type. The Universal Task Details will contain the fields that you created in the Universal Template for that Universal Task type.

Step 8

Enter/change values in the Universal Task fields that match the Universal Template fields, based on how you want their matching variables in the script to be resolved.

Step 9

Run the task, which executes the script. The variables in the script are resolved to the values of their matching fields in the Universal Task.

...

Action

Restriction

For Universal Templates

The following Delete and Update actions refer to Universal Templates and the fields in Universal Template Details.

Delete a Template

  • Prohibited.

Update a Template


  • Name
  • Allowed.
  • Variable Prefix
  • Allowed; Requires a corresponding Script change.
  • Agent Type
  • Broadening Allowed (Windows to Any, Linux/Unix to Any)
  • Narrowing Not Allowed (Any to Windows, Any to Linux/Unix, Windows to Linux/Unix, Linux/Unix to Windows)
  • Use Common Script
  • Script
  • Linux/Unix Script
  • Windows Script
  • Windows Script Type
  • Allowed.

For Universal Template Fields

The following Add, Delete, and Update actions refer to the user-defined Fields that are added to a Universal Template.

Add a Field

  • Allowed (with conditions); Requires a corresponding Script change.
  • Prohibited if either Required or Required If Field/Required If Field Value(s) are specified.
  • Default Value applied to all Universal Tasks, but not to Universal Task Instances.

Delete a Field

  • Allowed (with conditions); Requires a corresponding Script change.
  • Prohibited if the Field is the only Field in the Universal Template Details; User can either:
    • Update the only Field.
    • Create a new Field prior to deleting the only Field.
Note
titleNote

This restriction applies regardless of the existence of Universal Task/Task Instances associated with the Universal Template.

  • NULL value is applied to deleted Text, Integer, Choice, and Credential Fields in all Universal Tasks, but not Universal Task Instances.
  • A boolean False value is applied to a deleted Boolean Field for all Universal Tasks, but not Universal Task Instances.

Update a Field


  • Name
  • Prohibited.
  • Required
  • Allowed (with conditions).
  • Unchecking the Required field; Allowed (without conditions).
  • Checking the Required field; Allowed only if all Universal Tasks based on the Template have a value specified for this Template Field (does not apply to Universal Task Instances).
  • Require If Field
  • Require If Field Value(s)
  • Allowed (with conditions).
  • Removing a Require If Field specification; Allowed (without conditions).
  • Adding a Require If Field specification; Allowed only if all Universal Tasks based on this Template have a value specified for this Template Field (condition does not apply to Universal Task Instances).
  • Type
  • Prohibited.
  • Mapping
  • Prohibited.
  • Default Value
  • Allowed.
  • No Universal Task data will be updated; multi-update can be performed to apply any required changes to pre-existing Universal Task data.
  • Length
  • Allowed.
  • No Universal Task data will be updated, as it may not comply with updated Length constraint.
  • Minimum
  • Maximum
  • Allowed.
  • No Universal Task data will be updated, as it may not comply with updated Minimum/Maximum constraint.
  • Boolean Value Type
  • Boolean Yes Value
  • Boolean No Value
  • Allowed.
  • Field Display:
    • Label
    • Hint
    • Sequence
    • Form Column Span
    • Form Start Row
    • Form End Row
    • Add To Default List View
  • Allowed.

For Universal Template Field Choices

The following Add, Delete, and Update actions refer to the Choices that are defined for a Universal Template Field type of Choice.

Add a Choice

  • Allowed.

Delete a Choice

  • Allowed (with conditions).

  • Prohibited if the Template Field Choice is the only Choice; user can either:

    • Update the Choice Value.
    • Create a new Choice prior to removing the Choice.
    Note
    titleNote

    This restriction applies regardless of the existence of Universal Task/Task Instances associated with the Universal Template.


  • Any Universal Tasks using the Choice will still display the value, and substitute the old value into the Script; however, the drop-down will no longer display that Choice as an option.

Update a Choice


  • Value
  • Allowed
  • Any Universal Task using the previous value will be updated with the new value, but not Universal Task Instances.
  • Use Value For Label
  • Allowed.
  • Label
  • Allowed.
  • Sequence
  • Allowed.

...

The Controller provides built-in Universal Templates on which you can base Universal Tasks.

The title of each built-in Universal Template is preceded by UAC -.

Built-in Universal Templates are not editable, but you can use Copy to create a renamed copy of a built-in Universal Template, and then edit that template.

To use a built-in Universal Template, you first must load it from the List/Load Built-In Universal Templates Server Operation.

...

  • .