Skip to main content

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.

What this solves

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 ClassicIn OpCon ContinuumWhat changed
Alternate Machines on a jobBackup agents (Secondary, Tertiary and Quaternary Agent) on a Specific Agent jobWhere jobs run
Batch User (run-as account, per job type)Connection: central, reused by any jobCredentials
Daily / Daily JobJob, inside a workflowWhat a job does · Create a workflow
Database job typesSQL LSAM job types, listed under SQL - (SQL - MS SQL Script, SQL - MS SQL Job, SQL - MS SQL DTExec, SQL - Oracle, SQL - Other DB, SQL - MySQL), on an existing SQL LSAM machineWhat a job does
DepartmentWorkspaceOrganizing content
Editing changes the live scheduleCommitting your edits creates a version; an earlier version can be viewed, or pinned in a deploymentCreate a workflow · Deploy a job
Enterprise Manager / Solution Manager (desktop)The web UI: workflows on a visual canvasCreate a workflow
Existing LSAM machinesStill usable: legacy LSAM reached via a relayWhere jobs run
File-arrival handlingWait for File job type (built in), or Windows - File Arrival, UNIX - File Arrival or IBM i - File Arrival on an existing LSAM machineWhat a job does
Job type / sub-type (fixed catalog)Job type, chosen per job and provided by a connectorWhat a job does
Live schedule listWorkflow View + Job ViewMonitor operations
LSAM agent on a named MachineUniversal AgentWhere jobs run
LSAM command on a MachineUNIX Command / Windows Command: legacy LSAM via a relayWhat a job does
Machine (decides much of the run context)Agent assignment decides where a job runsWhere jobs run · Credentials
Machine GroupAgent Pool; for legacy LSAM machines, a legacy agent groupWhere jobs run
Master JobJob, inside a workflowCreate a workflow
Promote via separate instances / departmental setupDeploy a versioned workflow to an environmentDeploy a job
Rerun / mark / hold a jobSame actions: Restart, Mark Fixed, Under Review, CancelMonitor operations
Schedule (a Master that builds into a Daily)Workflow, versionedCreate a workflow · Deploy a job
Self Service requestService Request: typed inputs plus events on submitSelf Service
Self Service form fieldsInputs: text, password, number, date, choice, text collection, workflow selection, job selectionSelf Service
Solution Manager OperationsProcesses view (web-only)Monitor operations
Vision (cards with SLA targets)Vision, a separate area for critical paths and SLAsMonitor operations
Windows / UNIX command and script job typesRun Command, Run Script (built in)What a job does
Vision is its own area, not part of Processes

Classic's Vision cards and SLA targets map to OpCon Continuum's own Vision area, for monitoring critical paths and SLAs. Watching the day's run, which Classic does in Solution Manager Operations, is the Processes view. See Monitor critical paths and SLAs with Vision.

New in OpCon Continuum, with no Classic equivalent​

In OpCon ContinuumWhy it's new
Versions on every commit; an earlier version can be viewed, or pinned in a deploymentClassic edits changed the live schedule directly

Related topics