Skip to main content

What a job does: 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

In OpCon Classic, what a job did was set by its job type / sub-type: a fixed catalog built into the product. In OpCon Continuum, a job's action comes from a job type, provided by a plugin (connector) your administrator enables. The idea is the same ("pick what this job does"), but the catalog is now extensible, so where you look for a capability is different.

What you get. The mapping from Classic job types to OpCon Continuum job types, and how a Builder picks one when adding a job.