Glossary

Key terms used across OpCon Continuum documentation. This page and the inline definitions you see when you hover a term elsewhere in the docs are generated from the same source, so they always agree.

Core concepts

Term	Meaning
OpCon Continuum	The product — the platform that automates your processes and their interactions with your systems, including the mainframe core.
Workflow	An automated process: a set of jobs that run in a defined order, on a schedule. (Represented internally as a schedule.)
Job	A single unit of work in a workflow. It runs one job type on an agent.
Job type	The kind of work a job does (run a command, run a SQL script, wait for a file, etc.).
Connector	What provides job types — the way OpCon Continuum works with a kind of system or action.

Roles

Term	Meaning
Builder	The person who designs workflows, jobs, service requests, and Toolkit items (frequencies, calendars, thresholds, resources, properties, tags).
Operator	The person who monitors the daily run and responds to jobs that need attention.
Administrator	The person who manages agents, connections, environments, plugins, workspaces, and roles and permissions.
Business User	A business user who finds and submits service requests through self-service, without building automation.
Scope / Scoped	The workspaces and environments a role's permissions apply to. A scoped item belongs to, and is visible within, a particular workspace.

Running work

Term	Meaning
Agent	The software that runs jobs on a machine. The Universal Agent runs the built-in and downloadable connectors.
Agent pool	A group of agents that jobs can be routed to.
Relay / legacy LSAM	The bridge to existing legacy OpCon LSAM machines, which run jobs through the relay.
Build	Turning a workflow into a concrete day's run.
Instance	A specific run of a workflow or job.
Daily run	The set of workflow/job instances running for a given day.

Ordering and scheduling

Term	Meaning
Dependency	A condition a job waits on before it runs — a job, threshold, resource, or expression.
Predecessor	A job that another job depends on (on success, failure, or any result).
Frequency	A reusable scheduling rule that decides which days a job is eligible to run.
Calendar	A named set of dates (e.g. holidays) used to exclude days.
Threshold	A named numeric value used to gate a job.
Resource	A named capacity pool that jobs reserve and release, used to limit concurrency.

Building blocks and organization

Term	Meaning
Property	A named, reusable value (a path, an environment name); can be encrypted for secrets.
Tag	A label for organizing and searching jobs and other objects.
Event	An action (a command) fired in response to a job outcome.
Connection	Stored configuration and credentials — for an external system, or for the account a job runs as — so jobs use them without embedding secrets.
Batch user	A connection holding the account a legacy Windows, UNIX, or IBM i job runs as. The OpCon Continuum equivalent of an OpCon Classic Batch User.
Plugin	A package that provides job types (and sometimes connection types); enabled per organization.

Requests and governance

Term	Meaning
Service request	A form a Builder publishes so business users can trigger automation.
Self-service	The portal where business users find and submit deployed service requests.
Workspace	A boundary that scopes and isolates content.
Custom field	An admin-defined attribute added to workflows, jobs, and other objects.
Environment	A target such as test or production that workflows and requests are deployed to.
Version / Deployment	A saved snapshot of a design / which version runs in an environment (Latest or Pinned).

Operator actions

Term	Meaning
Hold / Release	Pause a job so it won't run / take it off hold.
Force Start	Start a waiting job now, regardless of what it's waiting on.
Skip	Mark a job so it doesn't run; dependents stop waiting on it.
Restart	Run a failed or cancelled job again.
Mark Fixed	Treat a failed job as resolved (work done outside the system).
Cancel	Stop a job; dependents stop waiting on it.
Kill	Stop a job that's actively running. Cancel doesn't apply once a job is running.
Mark Finished OK	Force a job to a successful outcome so its dependents proceed.
Mark Failed	Force a job to a failed outcome so its dependents react accordingly.

Related topics

• Getting started with OpCon Continuum