Terminology: OpCon Classic to OpCon Continuum
If you know OpCon Classic, most of what you already understand carries over — the names changed more than the ideas did. Use this table to translate a term, then follow the link for what actually changed about it.
Everything in OpCon Continuum has a new name, so experienced OpCon users can't find features they already know how to use. Searching for the Classic term is the fastest way to feel like the product lost something it didn't.
Quick lookup
Sorted by the OpCon Classic term.
| In OpCon Classic | In OpCon Continuum | What changed |
|---|---|---|
| Batch User (run-as account, per job type) | Connection: central, reused by any job | Credentials |
| Daily / Daily Job | Job, inside a workflow | What a job does · Create a workflow |
| Database job types | SQL Database job types, via a connection | What a job does |
| Department | Workspace | Organizing content |
| Enterprise Manager / Solution Manager (desktop) | The web UI: workflows on a visual canvas | Create a workflow |
| File-arrival handling | Wait for File job type (built in), or Windows - File Arrival / UNIX - File Arrival on an existing LSAM machine | What a job does |
| Job type / sub-type (fixed catalog) | Job type, chosen per job and provided by a connector | What a job does |
| Live schedule list | Workflow View + Job View | Monitor operations |
| LSAM agent on a named Machine | Universal Agent | Where jobs run |
| LSAM command on a Machine | UNIX Command / Windows Command: legacy LSAM via a relay | What a job does |
| Machine (decides much of the run context) | Agent assignment decides where a job runs | Where jobs run · Credentials |
| Machine Group | Agent Pool | Where jobs run |
| Master Job | Job, inside a workflow | Create a workflow |
| Promote via separate instances / departmental setup | Deploy a versioned workflow to an environment | Deploy a job |
| Rerun / mark / hold a job | Same actions: Restart, Mark Fixed, Under Review, Cancel | Monitor operations |
| Schedule (a Master that builds into a Daily) | Workflow, versioned | Create a workflow · Deploy a job |
| Self Service request | Service Request: typed inputs plus events on submit | Self Service |
| Self Service form fields | Inputs: text, password, number, date, choice | Self Service |
| Solution Manager Operations / Vision | Processes view (web-only) | Monitor operations |
| Windows / UNIX command and script job types | Run Command, Run Script (built in) | What a job does |
| Existing LSAM machines | Still usable: legacy LSAM reached via a relay | Where jobs run |
| Editing changes the live schedule | Every save creates a version, with history and rollback | Create a workflow · Deploy a job |
Classic's Vision maps to the OpCon Continuum Processes view for watching the day's run. OpCon Continuum also has its own, separate feature named Vision, for monitoring critical paths and SLAs. See Monitor critical paths and SLAs with Vision. They are not the same feature.
New in OpCon Continuum, with no Classic equivalent
| In OpCon Continuum | Why it's new |
|---|---|
| Versions on every save, with rollback | Classic edits changed the live schedule directly |
Related topics
- What a job does: what changed
- Where jobs run: what changed
- Glossary (OpCon Continuum terms)