View and Update Master Jobs Overview
Theme: Overview | Who is it for? Automation engineers who configure the full set of properties on a master job
What Is It?
Each master job has multiple configuration panels covering its core task details, frequencies, dependency rules, events, tags, and more. This section is the reference for all panels available when you open a master job record.
When Would You Use It?
- Use this feature when you open a master job record
Why Would You Use It?
- Centralized control: Each master job has multiple configuration panels covering its core task details, frequencies, dependency rules, events, tags, and more
Configuration Options
When would you use this section?
- Configuring a new job and setting all required fields
- Updating a job's frequency, dependency, or event rules
- Adding documentation or notification triggers to a job
- Reviewing a job's full configuration before deploying it
What is in this section?
| Panel | Description |
|---|---|
| Accessing Master Jobs | How to open a master job record from the Library |
| General Info | Job name, schedule, machine, department, access code, and disable flags |
| Documentation | Free-text and hyperlink documentation attached to the job |
| Job Task Details | Platform-specific settings (task type, command, script, parameters, etc.) |
| Tags | Tags applied to this job for cross-schedule filtering |
| Frequencies | Frequency rules that control when this job qualifies to run |
| Events | OpCon events fired when the job reaches specific status conditions |
| Instance Properties | Instance-level property definitions passed to this job |
| Job Dependencies | Jobs that must complete before this job starts |
| Expression Dependencies | Property expression conditions that must evaluate true |
| Resource Dependencies | Resources this job requires before it can run |
| Threshold Dependencies | Threshold conditions that must be satisfied before the job starts |
| Resource Updates | Resource counter changes applied when this job reaches a status |
| Threshold Updates | Threshold counter changes applied when this job reaches a status |
| Notification Triggers | Notifications sent when this job reaches specific status conditions |
Glossary
| Term | Definition |
|---|---|
| Access Code | A named object used to apply record-level security to individual job records, restricting which roles can view or modify specific jobs. |
| Department | A named object used to apply function-level security to individual job records. A single department can secure as many jobs as necessary. |
| Dependency (Job Dependency) | A condition that must be met before a job is allowed to start. OpCon supports job dependencies, threshold dependencies, resource dependencies, and expression dependencies. |
| 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. |
| Frequency | A named rule that specifies the recurring days on which a schedule or job runs. OpCon uses frequencies during the Schedule Build process. |
| Job | A task or activity defined in OpCon, such as running a program on a remote machine, transferring files, or running a sub-schedule. |
| Machine (Agent) | An execution target for OpCon jobs. Each machine runs an agent that communicates with the OpCon server and runs submitted jobs. |
| 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, SNMP, or Windows Event Log entries. |
| Property | A name-value pair stored in OpCon. Properties can be referenced in job definitions using token syntax to pass dynamic values at runtime. |
| Resource | A user-defined object with a name and a numeric limit. Used to restrict how many jobs run concurrently across schedules and machines in OpCon. |
| 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. |
| Solution Manager (SM) | The browser-based web interface for OpCon. Provides access to operations, self-service, vision dashboards, and configuration. |
| Threshold | A user-defined placeholder with a name and a numeric value. Used to resolve dependencies that cannot be handled by a standard job dependency and to allow external applications to affect schedules. |
FAQs
Q: What does the View and Update Master Jobs Overview cover?
Each master job has multiple configuration panels covering its core task details, frequencies, dependency rules, events, tags, and more. This section is the reference for all panels available when you open a master job record.
Q: Who manages Solution Manager - Library in OpCon?
Automation engineers and administrators manage Solution Manager - Library settings, user access, and related processes.
Q: Where should I start in the Solution Manager - Library section?
Begin with the overview pages in the sidebar. Each page covers a distinct feature or workflow. If you are new to this area, review access and role requirements with your OpCon system administrator before making configuration changes.