What changes for your role
BETA Preview
This feature is still being finalized by Development.
OpCon Continuum keeps the automation concepts you already know from OpCon Classic and changes how you build, run, secure, and scale them. What that means depends on what you do, so this page is organized by role.
For the vocabulary changes, see Terminology.
In one line
OpCon Continuum moves OpCon onto a modern, web-first foundation, keeping the automation model customers know while improving how it is built, operated, and secured.
For the Administrator
| What changes | Compared with Classic | Why it helps |
|---|---|---|
| Cloud-native services | Independently deployable services rather than a single server stack | Parts of the platform can be scaled and updated without taking all of it down |
| Web-only administration | No Enterprise Manager desktop client to install or patch | One less thing to deploy and keep current across your administrators |
| Hardened agent connections | Agents reach the platform through a single controlled entry point, and the Universal Agent runs plugins in isolated child processes with secrets supplied out of band | A smaller, controlled attack surface — agents are treated as untrusted clients |
| Schema-driven connections | Connections are typed and encrypted, with sensitive-field masking and a test action | Credentials are stored safely and validated before you rely on them |
| Per-tenant plugin control | Enable or disable plugins and pick default versions per organization | Control which job types are available without redeploying |
| First-class environments and workspaces | Explicit environments (with provisioning and health) and workspaces for isolation | Cleaner separation between test and production, and between teams' content |
| Modern access model | A permission catalog, scope tuples (workspace × environment), and a simulation tool | Each person's interface matches their roles, and simulation shows what a role grants before you assign it — see Roles and permissions |
| Incremental adoption | Existing LSAM machines run through the relay | Move to OpCon Continuum without rebuilding your legacy automation first |
For the Builder
| What changes | Compared with Classic | Why it helps |
|---|---|---|
| Visual workflow canvas | A browser-based diagram editor for workflows and jobs | Design and see the shape of your automation directly, with no desktop tool |
| Versioned workflows and promotion | Every change is a version; deploy Latest or Pinned to an environment | Test-to-production promotion with real history and a way back |
| Schema-driven job types | Each connector declares its parameters, and the form is generated and validated | Guided, consistent configuration instead of free-form job setup |
| Reusable Toolkit | Frequencies, calendars, thresholds, resources, properties, and tags shared across workflows | Define once and reuse, so scheduling and limits stay consistent |
| Frequency forecast | A year-calendar preview of exactly which dates a pattern matches | Confirm a schedule is right before it goes live |
| Clear dependency model | Job, threshold, resource, and expression dependencies, with success, failure, or any | Ordering and coordination are stated explicitly |
| Composable workflows | A Workflow Container embeds a reusable workflow as a single step | Build a standard sequence once and reuse it everywhere |
For the Operator
| What changes | Compared with Classic | Why it helps |
|---|---|---|
| Runtime troubleshooting diagram | A status-colored workflow diagram with a timeline and point-in-time status reconstruction | See how a run progressed and where it is blocked, and replay what happened |
| Workflow and job views | Switch between the run's diagram and a filterable job table | Use the right lens for the situation |
| Status-gated actions | Hold, Release, Force Start, Skip, Restart, Mark Fixed, and Under Review, offered only when valid for the status | The interface only offers what the run will actually accept |
| Event log with correlation | Trace an action through everything it triggered using a correlation ID | Faster root-cause work during an incident |
| Role dashboard | A home view of failed jobs, status counts, and queues | See what needs attention without going looking for it |
| Resilient runtime | Two-phase completion, with recovery from the event history | A run survives a restart without orphaning jobs |
For the Business User
| What changes | Compared with Classic | Why it helps |
|---|---|---|
| Self-service | A portal where business users submit published service requests | Teams trigger automation safely without involving the automation team every time |
| Role dashboard | A non-technical home view of activity and the requests available to you | Visibility without needing to understand workflows |
| Modern web experience | Browser-based, with no client to install | Faster onboarding, on the tools people already use |
| Existing investment protected | Connectors meet your existing systems, and legacy LSAM still runs | Adopt the new platform without discarding what works |
| Auditability | Every run and event is recorded | Evidence for examiners and auditors |
Related topics