Transitioning from OpCon Classic
If you know OpCon Classic, most of what you understand carries over. The names changed more than the ideas did. Start with the terminology lookup, then read the page for whatever you're trying to do.
What migration looks like
What carries over from OpCon Classic and what does not, which capabilities to check against your own automation before you move, and what to have ready for the conversation with your Continuous contact.
Terminology: OpCon Classic to OpCon Continuum
A single lookup table mapping OpCon Classic terms to their OpCon Continuum equivalents, with a link to the page that explains each change.
Alerts: what changed from OpCon Classic
How Classic's notification setup maps to OpCon Continuum's notification groups, triggers, and channels, and how to prove an alert arrives before you depend on it.
Create a workflow: what changed from OpCon Classic
How the Classic Schedule/Master/Daily authoring model maps to an OpCon Continuum workflow, and the steps to build your first one.
Credentials: what changed from OpCon Classic
How Classic's Batch Users map to OpCon Continuum connections, and the steps to set one up.
Deploy a job: what changed from OpCon Classic
How promoting a Classic schedule between instances maps to versioning and deploying an OpCon Continuum workflow.
Files: how arrival and transfer work today
The job types that wait for, move and manage files today, with Wait for File and SMAFT File Transfer walked through in full — including the allowed-path rule that stops a wait before it starts.
Monitor operations: what changed from OpCon Classic
How Solution Manager Operations/Vision map to OpCon Continuum's Workflow View and Job View, and the operator actions available.
Organizing content: what changed from OpCon Classic
How Classic Departments map to OpCon Continuum workspaces for keeping a team's or application's content separate.
Reports: what changed from OpCon Classic
How reporting moves from Classic's reporting service to OpCon Continuum's built-in report builder — what you can report on, how a report is saved and exported, and what has no report in this build.
Scheduling and holidays: what changed from OpCon Classic
How Classic frequencies and calendars map to OpCon Continuum's pattern model, where holidays and working days are decided now, and how to confirm a schedule before it goes live.
Self Service: what changed from OpCon Classic
How Classic Self Service maps to OpCon Continuum service requests, and the steps to build and deploy one.
What a job does: what changed from OpCon Classic
How Classic's fixed job-type catalog maps to OpCon Continuum job types and connectors, including legacy LSAM commands.
What changes for your role
What OpCon Continuum changes for Administrators, Builders, Operators, and business users, and which of those areas are still maturing.
Where jobs run: what changed from OpCon Classic
How Classic machines and machine groups map to OpCon Continuum agents and agent pools, including how existing LSAM machines keep running through the relay.
Related topics