Cisco Cisco Workload Automation 6.3 Betriebsanweisung

Events

Event Types



 – When this option is selected, the 

 tab disappears and the 

actions are associated with all jobs. For example, if you want to always notify users if their agent is not available for 
their job, you can set up a job event with the 

 event trigger, an email action and then 

enable the 

 option. If the agent goes down, all users with jobs scheduled to run on 

that agent will be notified.



 – Makes the event available to all users of CWA.



 – Makes the event active and available for use. When this option is disabled, you can still assign the event 

but it will not be triggered when the job runs.

Associated Action(s) Tab

This tab associates action(s) to the job event. An event must have at least one associated action before it can be enabled. 
The actions that are available are the actions that are predefined in the 

 pane. If you are defining a job event, 

then job control actions are also available. The associated actions will occur in sequence that they are listed. 



 – The action(s) to issue when the event occurs. You can specify one or more actions for each 

event. The actions will occur in the order they are listed. You can rearrange the sequence of multiple actions by 
selecting an action and clicking the up or down arrow.



 – The actions that you can assign to the job event. To assign an action, select the action and 

click the right arrow button. To select more than one action at the same time, hold down the S

 key or the C

 

key on your keyboard while clicking your selections.

You cannot add the same action more than once. Although you can assign multiple actions to a job event, you can 
apply only one job control action to an event. Adding a second job control action will replace the original job control 
action displayed in the 

 field. The actions available to use may be limited by your security policy. 

You can choose from the following types of job control actions that CWA provides (for Job events only):

 – Cancels the job occurrence but passes the job’s dependencies to any successor jobs. In 

essence, the job goes into a 

 state as the dependencies run. Once all of the job’s 

dependencies are satisfied, the job ends with a 

 

 status that is equivalent to a 

status.

Cancel/Abort

 – Terminates the job if it is active, resulting in the job completing abnormally.

 – Cancels the job occurrence if it has not started yet.

Hold/Stop

 – Prevents your job from running when its dependencies are met. The job changes its status to 

. You can 

release the job at a future time. (Not available for jobs running on Windows agents).

 – Stops the execution of an active job. You can restart the job at a future time using the 

 job control. 

(Not available for jobs running on Windows agents).

 – Specifies that when the event occurs, the operator does not need to 

release the job.

 – Specifies that when the event occurs, the operator must release the job.

 – Overrides any dependencies for which your job is waiting. It is recommended to use this option only 

with the 

 and 

 

event triggers.

Release/Resume