Property | UI Field Name | Description | Specifications | Required |
---|
Anchor |
---|
| arrayField1 - UT |
---|
| arrayField1 - UT |
---|
|
arrayField{1-4 } | <array field> | Array field for this Universal task. Examples: Create / Update XML:
<arrayField1 nameTitle="Custom Name" valueTitle="Custom Id">
<field>
<name>John Doe Jr.</name>
<value>1234567</value>
</field>
<field>
<name>Max</name>
<value>888888</value>
</field>
</arrayField1>
<arrayField2>
<field>
<name>A1</name>
<value>test1</value>
</field>
<field>
<name>A2</name>
<value>test2</value>
</field>
</arrayField2> JSON:
"arrayField1": {
"fields": [
{
"name": "John Doe Jr.",
"value": "1234567"
},
{
"name": "Max",
"value": "888888"
}
],
"nameTitle": "Custom Name",
"valueTitle": "Custom Id"
},
"arrayField2": {
"fields": [
{
"name": "A1",
"value": "test1"
},
{
"name": "A2",
"value": "test2"
}
]
},
Read XML:
<arrayField1 name="array1" label="Customers" nameTitle="Custom Name" valueTitle="Custom Id">
<field>
<name>John Doe Jr.</name>
<value>1234567</value>
</field>
<field>
<name>Max</name>
<value>888888</value>
</field>
</arrayField1> JSON:
"arrayField1": {
"fields":[
{
"name": "John Doe Jr.",
"value": "1234567"
},
{
"name": "Max",
"value": "888888"
}
],
"label": "Customers",
"name": "array1",
"nameTitle": "Custom Name",
"valueTitle": "Custom Id"
} | Only fields defined in the corresponding Universal Template will be set. Validation rules defined on the template apply. Attributes name and label are for informational purpose only. | N |
Anchor |
---|
| booleanField1 - UT |
---|
| booleanField1 - UT |
---|
|
booleanField{1-10 } | <boolean field> | Boolean field for this Universal task. Examples: Create / Update XML:
<booleanField1>false</booleanField1>
JSON:
"booleanField1": false Read XML:
<booleanField1 name="run_immediately" label="Run Immediately">false</booleanField1>
JSON:
"booleanField1": {
"label": "Run Immediately",
"name": "run_immediately",
"value": false
} | Only fields defined in the corresponding Universal Template will be set. Validation rules defined on the template apply. Attributes name and label are for informational purpose only. | N |
Anchor |
---|
| choiceField1 - UT |
---|
| choiceField1 - UT |
---|
|
choiceField{1-15 } | <choice field> | Choice field for this Universal task. Examples: Create / Update XML:
<choiceField1>val 1</choiceField1>
JSON:
"choiceField1": "val 1" Read XML:
<choiceField1 name="progname" label="Program Name">val 1</choiceField1>
JSON:
"choiceField1": {
"label": "Program Name",
"name": "progname",
"value": "val 1",
} | Only fields defined in the corresponding Universal Template will be set. Validation rules defined on the template apply. Attributes name and label are for informational purpose only. | N |
Anchor |
---|
| createConsole - UT |
---|
| createConsole - UT |
---|
|
createConsole | Create Console | If desktopInteract is true; Specification for whether or not to allocate a new console for the process, rather than having it inherit one. | Boolean; Valid values: true/false. Default is false. | N |
Anchor |
---|
| credentialField1 - UT |
---|
| credentialField1 - UT |
---|
|
credentialField{1-6 } | <credential field> | Credential field for this Universal task. Examples: Create / Update XML:
<credentialField1>val 1</credentialField1>
JSON:
"credentialField1": "val 1" Read XML:
<credentialField1 name="credname" label="Credential Name">val 1</credentialField1>
JSON:
"credentialField1": {
"label": "Credential Name",
"name": "credname",
"value": "val 1",
} | Only fields defined in the corresponding Universal Template will be set. Validation rules defined on the template apply. Attributes name and label are for informational purpose only. | N |
Anchor |
---|
| desktopInteract - UT |
---|
| desktopInteract - UT |
---|
|
desktopInteract | Interact with Desktop | Specification for whether or not a task that runs an application with a GUI requires some manual actions from a user (for example, clicking buttons or entering values). | Boolean; Valid values: true/false. Default is false. This property is effective only for tasks executed on Windows XP or Server 2003. Windows Vista introduced the desktop isolation feature, which prevents tasks from accessing the interactive desktop session on Vista, Windows 7, Server 2008, Windows 8, and Server 2012. The Windows agent will execute the task, but the Interact with Desktop option has no effect. Therefore, an interactive application's GUI will not be visible on those platforms. | N |
Anchor |
---|
| elevateUser - UT |
---|
| elevateUser - UT |
---|
|
elevateUser | Run with Highest Privileges | Specification for whether or not to execute the task using an elevated privileges token, rather than one subject to User Account Control (UAC) restrictions. An elevated token allows a process to execute with all the privileges available to its specified credentials. For example, a task executed with an administrative account will behave as though it received permission via a UAC dialog to perform a privileged operation. | Boolean; Valid values: true/false. Default is false. This property will not give a user account privileges that have are not already granted to it. For example, taking ownership of a file is a privileged operation by default. A task will still fail even with this option selected if it is run with a regular user account that has not been granted the ability to change file ownership. | N |
Anchor |
---|
| environment - UT |
---|
| environment - UT |
---|
|
environment | Environment Variables | Environment variables needed by the program to run. | List of environment variables: |