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.
Add jobs to a workflow
How to add jobs to a workflow in OpCon Continuum: choose each job's job type, set its parameters and agent assignment, and save it to the canvas.
Agents and agent pools
How agents run your jobs, how agent pools route work to whichever agent is available, and how to read an agent state or diagnose a job waiting for one.
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.
Automation export and import
Moving a bundle of workflows, calendars, frequencies, properties, thresholds, resources and tags between environments or tenants — what the bundle contains, what export deliberately leaves out, and the overwrite and all-or-nothing rules import applies.
Connections
How a connection stores the configuration and credentials an external system or a legacy run-as account needs, which connection types exist today, how secrets are stored and masked, and how to attach one to a job.
Copy a workflow
What Copy Workflow and Copy to Another Workflow do and do not carry across — the name rules it enforces, how copied jobs are given fresh identities, how dependencies are rewritten, and which control on the dialog has no effect yet.
Create a service request
How to build a service request so business users can trigger workflows on demand through a guided form.
Create a workflow: what changed from OpCon Classic
How the Classic Schedule/Master/Daily authoring model maps to an OpCon Continuum workflow, and the steps to build your first one.
Create and run reports
How to build, run, and export reports so you can track job activity, agent health, and schedule outcomes.
Create reusable container jobs
How to build a child workflow as a container job, then deploy it so other workflows can reuse the same set of steps.
Credentials: what changed from OpCon Classic
How Classic's Batch Users map to OpCon Continuum connections, and the steps to set one up.
Define a frequency
How to define a frequency so workflows run only on the days and timing patterns you intend.
Deploy a job: what changed from OpCon Classic
How promoting a Classic schedule between instances maps to versioning and deploying an OpCon Continuum workflow.
EASE jobs
How EASE job types add a job to today's instance of your schedule on Jack Henry's EASE OpCon, wait for it to finish, and bring back the remote job's output — the twenty job types and their fields, the schedule pre-checks, which remote statuses pass and fail, the SEQ property write-back, and what the Output tab shows.
Embed another workflow with a Workflow Container
How to embed one workflow inside another with a Workflow Container so you can reuse and nest automation.
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 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.
Files: how arrival and transfer work today
The job types that wait for, move and manage files today, with Wait for File and SMAFT File Transfer walked through in full — including the allowed-path rule that stops a wait before it starts.
Frequencies
The scheduling pattern model that decides which dates a job is eligible to run on, how working days and calendars shape the result, the options each pattern accepts, and how to validate one with the forecast.
Getting started with OpCon Continuum
An orientation to OpCon Continuum that explains the main pieces and points each role to where to begin.
How connectors work
What a connector is, the three ways connectors run, which ones need a saved connection, and the catalog of job types available today.
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.
How workflows work
What a workflow contains and how its jobs are ordered by dependencies, timed by frequencies and build settings, placed on agents, and versioned for deployment.
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 configuration
Every configurable part of a job — job definition, agent assignment, frequencies, dependencies, events, properties, and flags — and the three ways a job can be placed on an agent.
Job dependencies
The four dependency types that sequence a workflow, the Condition and Type axes of a job dependency, exactly which predecessor statuses satisfy each Condition, how an expression dependency is evaluated and what each of its outcomes does to the job, and how to diagnose a job stuck waiting on one.
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.
Job type catalog
Every job type available today, grouped by category, with the plugin it comes from, whether it needs a connection, and where it runs.
Legacy LSAM connectors (UNIX/Linux, Windows, IBM i, SQL, SAP R/3, SAP BW, z/OS, MCP and OS 2200)
How the UNIX/Linux, Windows, IBM i, SQL, SAP R/3 and CRM, SAP BW, z/OS, MCP and OS 2200 LSAM connectors let an OpCon Continuum workflow run commands, WS_FTP Pro transfers, file operations, Corelation batch jobs, Fiserv DNA jobs, HTTP/REST calls, T-SQL scripts, SQL Server Agent jobs, SSIS packages, Oracle SQL*Plus scripts, MySQL scripts, ODBC and OLE DB SQL, IBM i batch jobs, Operator Replay and Restricted Mode scripts and FTP transfers, library scripts, Symitar/Episys batch processing, SAP R/3 and CRM background jobs, SAP BW process chains, z/OS batch JCL members with dataset, message, job/task, tape and REXX pre-runs, z/OS started tasks, REXX execs and console commands, z/OS jobs the agent tracks or queues, Unisys MCP programs, WFL jobs, EAE/AB Suite reports and file copies, renames and removals, each with an optional prerun, Unisys OS 2200 ECL runstreams with a prerun or file dependencies, and file-arrival waits on your existing legacy agents through a relay, and how to diagnose routing and exit-criteria failures.
Manage agents and agent pools
How to add, configure, and group agents into pools so work runs on the right machines and stays available.
Manage connections
How to create, edit, and secure connections — the batch user a legacy job runs as, and the credentials a job type needs for one step.
Manage notifications
How to set up notification groups, triggers, and actions so the right people are told when an agent, workflow, or job needs attention.
Manage permissions
How to use the Permissions page: roles, permissions and scopes that control who can see and change what, event identities for scripts and machines, and workspaces that keep teams' content apart.
Manage plugins
How to enable and disable plugins, and turn single job types of a plugin on or off, so your Builders are offered the job types your organization uses.
Manage relays
How to register, install, and maintain a relay so your on-prem legacy LSAM machines can run jobs dispatched from the cloud.
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.
Null Job
What a Null Job does, why you would use one to aggregate dependencies or carry events, and why a Null Job that never finishes is a dependency or on-hold problem rather than a job failure.
OpCon MFT Transfer job
How the OpCon MFT Transfer job downloads, transforms and uploads files on an OpCon MFT agent — the endpoint and key pickers, the order the compression and encryption steps run in, the compression password connection, what refuses a save, and why a restart resumes the previous run.
OpCon RPA Task job
How the OpCon RPA Task job starts a Robot, Web Macro or Scan Document task on an OpCon RPA agent — the Sub-type, Task and Version pickers, how "Use latest" resolves, which statuses pass and fail, the instance properties the job carries, and what the Output tab shows.
Order jobs with dependencies
How to order jobs with dependencies so each job runs only after the jobs it relies on reach the right outcome.
Organizing content: what changed from OpCon Classic
How Classic Departments map to OpCon Continuum workspaces for keeping a team's or application's content separate.
Prepare agents for connectors
How to prepare agents with the interpreters, drivers, and permissions each connector needs before running connector jobs.
Publish a self-service request for business users
How to build a workflow and a service request, deploy them, and hand business users a guided form so they can trigger the automation themselves.
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.
Relays
What a relay is, how to register, install, and health-check one, and how to rotate its credentials so legacy LSAM machines can run jobs dispatched from the cloud without inbound firewall changes.
Reports
What you can report on, how to build a report from columns, sort rules, and filters, and how to save, re-run, and export the results.
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.
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.
Roles and permissions
How roles, the permission catalog, and per-scope grants in workspaces and environments shape what each person sees in Continuum, where the Permissions page lives, and the refusals that apply to every event.
Run a command
How to add and configure a Run Command job so a job runs a command or program on an agent.
Run a script
How to add and configure a Run Script job so a job runs a script in the interpreter you choose on an agent.
Run Command job
How the Run Command job runs a command line on an agent, when to run it through a shell instead of directly, how exit criteria and output parsing decide success, and how to diagnose command-not-found, environment, and exit-code failures.
Run commands on legacy LSAM machines
How to run commands on legacy LSAM machines so you can automate work on systems connected through the legacy relay.
Run Script job
How the Run Script job runs an embedded PowerShell, Bash, Python, or Shell script on an agent, which interpreters must already be installed there, how exit criteria and output parsing decide success, and how to diagnose missing-interpreter and exit-code failures.
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.
Scheduling and holidays: what changed from OpCon Classic
How Classic frequencies and calendars map to OpCon Continuum's pattern model, where holidays and working days are decided now, and how to confirm a schedule before it goes live.
Scheduling and the run
How build settings, frequencies, and calendars together decide what runs and when, and how to work out why a job did or did not build into a day's run.
Script library
How the script library stores and versions scripts so a job can reference one instead of carrying its own copy, and how a referenced script is pinned or tracked.
Self Service: what changed from OpCon Classic
How Classic Self Service maps to OpCon Continuum service requests, and the steps to build and deploy one.
Self-service portal
How a business user finds a published request in the catalog, fills in its form, and submits it without ever seeing workflows or jobs, and what happens on submit.
Service requests
What a service request is made of, including inputs, events, versions, deployments, and per-environment transformations, so a business user can trigger automation from a form without touching the workflow.
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.
SMAFT File Transfer job
How the SMAFT File Transfer job moves a file between two legacy LSAM machines, how the machine that runs the transfer is derived from Start Transfer On, and what refuses a save, fails a dispatch, or holds the job.
Submit a service request
How to submit a service request so you can trigger an automated workflow without building it yourself.
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.
Thresholds and resources
How thresholds gate jobs on a numeric value and resources limit how many jobs run at once, and how jobs reference both as dependencies.
Toolkit overview
The reusable building blocks you define once and use across workflows — frequencies, calendars, thresholds, resources, properties, and tags — and which are global versus workspace-scoped.
Use a Null Job
When and how to use a Null Job as a placeholder or dependency anchor to simplify workflow structure.
Use the event log
How to use the event log to trace what happened during a run using correlation IDs and event statuses.
Use thresholds and resources
How to use thresholds and resources to control concurrency and coordinate jobs that share limited capacity.
Wait for a file before your workflow continues
How to add and configure a Wait for File job so a workflow waits until a file has arrived and is complete before continuing.
Wait for File job
How the Wait for File job holds a workflow until a file arrives and meets size, age, and stability criteria, and what happens on timeout, a missing file, or a restricted path.
What a job does: what changed from OpCon Classic
How Classic's fixed job-type catalog maps to OpCon Continuum job types and connectors, including legacy LSAM commands.
What migration looks like
What carries over from OpCon Classic and what does not, which capabilities to check against your own automation before you move, and what to have ready for the conversation with your Continuous contact.
What OpCon Continuum can automate
A business-level overview of what OpCon Continuum can automate and why connectors matter for your bank or credit union.
Where jobs run: what changed from OpCon Classic
How Classic machines and machine groups map to OpCon Continuum agents and agent pools, including how existing LSAM machines keep running through the relay.
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.
Workflow Container job
How a Workflow Container embeds another workflow as a step in the current one, what the container does while the nested workflow runs, and how to diagnose missing, circular, and too-deeply-nested references.
Workflow Settings
How to create a workflow in OpCon Continuum and use its Workflow Settings panel: name it, choose its workspace, and set its working days, holidays, start time, automatic builds and schedule instances.