Events Section Overview

What are OpCon events?

OpCon events are commands that trigger system actions — building schedules, changing job status, updating properties, sending notifications, and more. Events can be attached to jobs, schedules, or notification triggers, and submitted externally through the External Event interface.

Events are structured as command strings processed by the SAM. Each event belongs to a category such as $JOB, $SCHEDULE, $MACHINE, $THRESHOLD, $NOTIFY, $TOKEN, or $PROPERTY, followed by a colon and the specific action (for example, $JOB:ADD or $SCHEDULE:BUILD).

Common use cases

• Attach an event to a job to trigger downstream actions on completion or failure.
• Use the External Event interface to submit events from external systems.
• Define an event in a notification trigger to send alerts when a condition is met.
• Set or update a property or threshold value in response to a job outcome.

What is in this section?

Page	Description
Introduction	What OpCon events are, how they work, and where they can be used
Defining Events	How to define event strings with parameters
Event Types	Complete reference for all available OpCon event types and their parameters

Glossary

Term	Definition
Event (OpCon Event)	A command string that OpCon runs when a defined condition is met, such as a job finishing, a threshold being updated, or a schedule completing.
Job	A unit of work defined in OpCon, such as running a program on an Agent, transferring files, or running a sub-schedule.
Notification	An alert generated by the SMA Notify Handler when a machine, schedule, or job reaches a defined status. Notifications can be sent as email, text message, SNMP trap, or Windows Event Log entry.
Role	A named collection of privileges that can be assigned to one or more user accounts. Users in a role inherit all of that role's privileges.
Schedule	A named group of jobs in OpCon that represents a business process. Schedules are built each day based on their defined frequencies and calendars.