Skip to main content

Deploy a job: what changed from OpCon Classic

Concept mapping, under review

This page maps OpCon Classic concepts to their OpCon Continuum equivalents. It is a conceptual mapping under review, and it deliberately does not compare the two products' platform or job-type breadth. Use it to translate what you already know — not as the basis for a migration plan. Confirm specifics with your Continuous contact.

What this solves

Transitioning from OpCon Classic, "move this job to production" used to mean promoting a schedule between separate OpCon instances or departmental setups. There was no single versioned thing you deploy to an environment. In OpCon Continuum that model changes, and carrying the old mental model over is the main thing that trips people up.

What you get. A clear picture of the new deployment model (you version a workflow and deploy it to an environment) and the exact steps to move a job from test to production the OpCon Continuum way.