Deleting Master Jobs
Theme: Configure
Who Is It For? System Administrator, Automation Engineer
What Is It?
Use this procedure to delete Master Jobs in Solution Manager.
Administration
Required Privileges
To delete a job, you must be in the ocadm role or have all of the following privileges:
- Schedule Privilege: Access to the job's parent schedule
- Access Code Privilege: Access to the assigned job access code with Allow job updates set to true
- Machine / Machine Group Privilege: Access to the assigned job machine or machine group
- Departmental Function Privilege: All Function Privileges, Delete Jobs from Master Schedules, or Modify Jobs in Master Schedules
- Department Privilege: Access to the assigned job department or All Departments
Deleting a Job
To delete a master job, complete the following steps:
-
Go to Library > Master Jobs.
-
Select one or more jobs in the list.
-
Select Delete. A confirmation dialog opens:
-
Select Yes to confirm the deletion or No to cancel.
Result: The selected master job records are permanently removed from OpCon.
Configuration Options
| Setting | What It Does | Default | Notes |
|---|---|---|---|
| Schedule Privilege | Access to the job's parent schedule | — | — |
| Access Code Privilege | Access to the assigned job access code with Allow job updates set to true | — | — |
| Machine / Machine Group Privilege | Access to the assigned job machine or machine group | — | — |
| Departmental Function Privilege | All Function Privileges, Delete Jobs from Master Schedules, or Modify Jobs in Master Schedules | — | — |
| Department Privilege | Access to the assigned job department or All Departments | — | — |
FAQs
Q: Can a master job record be recovered after deletion?
No. Deleting a master job record permanently removes it from OpCon. Verify the record is no longer needed before deleting it.
Q: What should you check before deleting a master job?
Verify the master job is not currently in use or assigned to other records before deleting it, as deletion may affect dependent objects.
Glossary
Access Code: A security label applied to jobs and schedules in OpCon. Users must have the matching access code privilege to view or manage items with that label.
Department: An organizational grouping in OpCon used to assign jobs to logical divisions. User roles can be scoped to specific departments, controlling which jobs a user can manage.
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.
Role: A named security profile in OpCon that groups privileges together. Roles are assigned to user accounts to control which features, schedules, jobs, machines, and administrative functions a user can access.
Privilege: A specific permission granted through an OpCon role that controls access to a feature, function, or object type. Privileges are organized into categories such as Function Privileges, Machine Privileges, Schedule Privileges, and Access Codes.
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.