Acting on runs in Processes
How to act on a run from the Processes page, including scheduling a workflow, single and bulk job and workflow actions, deleting, adding a job to a running instance, editing a job on a running instance and Push Changes to Workflow.
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.
Automate the nightly core export
How to connect the pieces you already know -- a workflow, a frequency, a wait for file, dependencies, and a failure event -- into one unattended nightly core export.
Dashboards
How Continuum chooses which of its three dashboards to open, and what the Admin, Operator, and Business User dashboards surface.
Event log
How to read an event's fields and use status, source, and correlation ID to trace a whole chain of related actions back to what caused it.
Events
Every OpCon event type OpCon Continuum accepts — its syntax field by field, what it does, whether Continuum applies it, refuses it for now or refuses it for good, where you can raise it from, and the permission it needs.
Events raised by a legacy agent
How a job or process on a legacy LSAM machine raises an OpCon Continuum event by writing a file of event syntax into the agent's MSGIN directory — the Default event environment it needs, the line format and the credential pair Continuum verifies, which events are applied, how each one is attributed and where a rejected line goes.
Exchange files with a partner
How to wait for an inbound file from a partner, validate and process it, and handle failures, without a person watching for the file to arrive.
Exit codes and machine messages
What the exit codes, termination descriptions and agent messages OpCon Continuum records for a job mean — Initialization Error reasons, universal and legacy agent results, relay failure texts — and where you see each one.
Get familiar as an Operator
A checklist of hands-on tasks so you can learn OpCon Continuum by monitoring a run and responding to jobs in a test environment.
Global search
How to find objects across ten entity types from one place, save a search to re-run it, and use the bulk actions and exports available.
How the daily run works
How a built workflow moves through waiting, running, pending-term, and terminal statuses, so you can tell a job that is working as designed from one that is genuinely stuck.
Job and workflow statuses
The authoritative list of every job and workflow status, what each one means, and which lifecycle actions a job or workflow in that status will accept.
Job statuses and actions
A reference to job statuses and the operator actions available for each, so you know how to respond during the daily run.
Monitor critical paths and SLAs with Vision
How to group jobs into Vision cards with SLAs so you can see at a glance whether critical work is on track to finish on time.
Monitor critical paths and SLAs with Vision
How to build Vision cards with service-level agreements so an at-risk critical path is visible before the deadline is missed.
Monitor operations: what changed from OpCon Classic
How Solution Manager Operations and Vision map to OpCon Continuum's Processes (Workflow View and Job View) and Vision, and the operator actions available.
Monitor the daily run
How to monitor the daily run so you can track progress and act on jobs that need attention.
Operator learning path
A guided reading order for the Operator pages, grouped into modules that build on each other.
Operator response guide
What each waiting, running, failed, or held job state means during the daily run, which action to take in response, and how to read a completed job's exit code.
Recover a failed run automatically
How to build a failure-triggered recovery dependency and event so a failed run retries or reroutes on its own, before an operator needs to step in.
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 which report holds the change history.
Resizing table columns
How to make a column in a Continuum list wider or narrower by dragging its header edge, how the width is kept in your browser, and how to put a column back to its default width.
Respond to a failed connector job
How to diagnose and respond to a failed connector job so you can get a stalled workflow moving again.
Respond to a failed job
How to respond to a failed job by reviewing the cause and choosing the right recovery action.
Respond to a stuck or failed Wait for File job
How to respond to a stuck or failed Wait for File job so a waiting workflow can continue or be escalated.
Schedule instances
How one workflow builds as several named schedule instances for the same date, each carrying its own property values — how instances are defined, how a build targets them, how they are named and displayed, and how dependencies, conflicts and events address one instance.
Search across OpCon Continuum
How to search across OpCon Continuum so you can quickly find jobs, workflows, and other objects.
Set up failure notifications
How to create a notification group, target the jobs that matter, and prove it works, so a failure overnight never goes unnoticed.
The Processes page (runtime)
How to read the Processes page, including the Job and Workflow views, the run diagram, filters and search, job detail and output, and who can do what.
Use the event log
How to use the event log to trace what happened during a run using correlation IDs and event statuses.
Vision (critical-path monitoring & SLAs)
How Vision boards, tag cards, and SLA targets show whether the right work is finishing on time, and how each card is evaluated.
What changes for your role
What OpCon Continuum changes for Administrators, Builders, Operators, and business users, role by role, and where each change is measured against OpCon Classic.
Work the Processes page
How to use the Processes page to watch the daily run and act on jobs -- filter, search, and take single or bulk actions.