Applying Escalation Rules to Triggers
Theme: Configure
Who Is It For? System Administrator, Automation Engineer
What Is It?
Use this procedure to apply Escalation Rules to Triggers in the Enterprise Manager.
To apply a rule to a trigger, complete the following steps:
- Select on Notification Manager under the Management topic
- Select the Machines, Schedules, or Jobs tab in the Notification Triggers frame
- Select the
arrow to expand a folder and select the desired trigger - Select the option to the left of Send Email (SMTP). The Email tab appears and the Escalation Rule sub-frame activates
- Select an escalation rule from the list in the Escalation Rule sub-frame, or select Find (Ctrl+F) to use the Quick Search
- Select the Email tab
- Enter an email address in the To field and a subject in the Subject field
- (Optional) Enter values for the CC and/or Bcc fields
- Select the Message tab and add a message
- (Optional) Select the Attachments tab and add attachments
- Select Save
Configuration Options
| Setting | What It Does | Default | Notes |
|---|
FAQs
Q: How many steps does the Applying Escalation Rules to Triggers procedure involve?
The Applying Escalation Rules to Triggers procedure involves 11 steps. Complete all steps in order and save your changes.
Glossary
Notification: A message sent by the SMA Notify Handler when a Machine, Schedule, or Job changes to a specific status. Notifications can be delivered as emails, text messages, Windows Event Log entries, SNMP traps, or other formats.
Resource: A numeric variable in OpCon representing a finite pool. Jobs can be configured to require a set number of resource units to run, limiting concurrent executions and preventing resource contention.
Machine: A platform defined in the OpCon database that has an agent installed. OpCon routes job execution requests to machines via SMANetCom, and machines report job completion status back to SAM.
Schedule: A named container for jobs in OpCon, built for a specific date to create that day's automation. Schedules define build settings, frequencies, and the jobs that run within them.
Job: The fundamental unit of work in OpCon. A job defines what to run, on which machine, when to start, and what conditions must be met. Job results are tracked and can trigger events and notifications.