...
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 | |
Update a Template |
|
| |
| - Allowed; Requires a corresponding Script change.
|
| - 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
| |
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 |
---|
| 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 |
|
| |
| - 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).
|
| |
| |
| - Allowed.
- No Universal Task data will be updated; multi-update can be performed to apply any required changes to pre-existing Universal Task data.
|
| - Allowed.
- No Universal Task data will be updated, as it may not comply with updated Length constraint.
|
| - 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
| |
- Field Display:
- Label
- Hint
- Sequence
- Form Column Span
- Form Start Row
- Form End Row
- Add To Default List View
| |
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 | |
Delete a Choice | |
Update a Choice |
|
| - Allowed
- Any Universal Task using the previous value will be updated with the new value, but not Universal Task Instances.
|
| |
| |
| |
...
The Controller provides built-in Universal Templates on which you can base Integrations.
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.
...