To configure an Automation Task that should run when a session starts, go to Composition > Actions By Type > Automation Tasks.
To configure an Automation Task that should run when an application starts, open the application at Composition > Applications and go to Configuration > Actions.
You can override the global settings of this feature for specific Workspace Containers.
When configuring an Automation Task, optionally enter a note in the Administrative note field. This is useful to differentiate the Automation Tasks that you configured.
Click in the Task field to load the available Automation Projects and Modules from the Automation environment that you specified at Setup > Integration > Ivanti Products > Automation. This allows you to select the Automation Projects or Modules that should be part of the Automation Task.
Skip if application executable was found (only available on application level) when selected, a check will be done whether the application executable is present on the client computer before the task is executed. When the option is not selected, the task is executed as configured when the application is started.
Workspace Control can detect whether the Automation Task has run before for that user, on that computer, or for the combination of that user on that computer. In the Run once field, you can configure whether the Task should be executed or skipped when a user starts the application:
No: the Automation Task will be executed, irrespective of whether it has been executed before.
Per user: the Automation Task will be executed once for each user who logs on to the Workspace Control environment.
Per computer: the Automation Task will be executed once for each computer in the Workspace Control environment.
Per user per computer: the Automation Task will be executed once for each user who logs on to the Workspace Control environment on a specific computer.
If you need to repeat an existing Automation Task that has been configured to Run once, select Clear history. This resets the count, so that the existing Automation Task is executed again throughout the environment, according to the rules selected for Run once.
When you configure a custom message, you can communicate additional information about the Automation Task to the user.
Wait for task to finish before continuing forces Workspace Control to finish the task before continuing with the next Task. Clear this check box to force Workspace Control to continue with the next Task if the Task does not complete. It can be useful to select this option when you have configured a custom message: this allows the user some additional time to read this message. However, if the Automation Task has not started before the specified timeout expires, the Task will be canceled.
Run before other actions makes it possible to specify that the Automation Task should be executed before other configuration Actions (except Environment Variable Actions). At application level, an Automation Task that is configured to Run before other actions will appear on top of the list of Actions on the Actions tab; The option Run before other actions will automatically be selected or cleared again when moving an Automation Task in the list by using the arrows.
Required connection state specifies the required connection state that allows the Task to be executed. For example, this allows you to configure a Task that only runs if the laptop has an online connection state.
Click the Parameters tab to view which parameters will be used in the Automation Task. This tab is only available if the selected Automation Project or Module contains parameters.
Click the Access Control tab to configure the Access Control criteria of the Automation Task.
Click the Workspace Control tab to configure to which Workspace Container(s) the Automation Task applies.