Browse all documentation

The sidebar walks one hierarchy and search needs the right words. This page lets you narrow by what kind of page it is, who it's for, and which area it covers — in any combination.

Filters combine, and your selection goes into the address bar, so a filtered view is a link you can send to someone.

Search titles and descriptions

Type

Audience

Area

133 of 133 pages

• Overview · OtherAdministrator documentationSet up and maintain the environment, including agents, connections, environments, workspaces, and access.
• Reference · Orientation · AdministratorAdministrator learning pathA guided reading order for the Administrator pages, grouped into modules that build on each other.
• Reference · Agents · AdministratorAgents and agent poolsHow 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.
• How-to · Transitioning from OpCon Classic · Administrator · BETA PreviewAlerts: what changed from OpCon ClassicHow 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.
• How-to · Workflows · BuilderAutomate the nightly core exportHow 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.
• Reference · Environments · AdministratorAutomation export and importMoving 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.
• Overview · OutcomesAutomation outcomesComplete business requirements, built end to end -- each threads the individual features together into one thing you actually need to deliver.
• Reference · OrientationBrowse all documentationFilter every page by type, audience, and feature area to find what you need without walking the sidebar or guessing search terms.
• Overview · OtherBuilder documentationDesign workflows, jobs, and the building blocks they share, from your first workflow to service requests and deployment.
• Reference · Orientation · BuilderBuilder learning pathA guided reading order for the Builder pages, grouped into modules that build on each other.
• Overview · OtherBusiness User documentationUnderstand what OpCon Continuum can automate for you, then find and submit a service request without building anything yourself.
• Reference · Orientation · Business UserBusiness User learning pathA guided reading order for the Business User pages, grouped into modules that build on each other.
• Reference · Toolkit · BuilderCalendarsHow a named set of holiday or blackout dates excludes days from scheduling, the fields a calendar carries, and what refers to a calendar before you rename or delete one.
• Reference · Connections · AdministratorConnectionsHow 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.
• Reference · Workflows · BuilderCopy a workflowWhat Copy Workflow does and does 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.
• How-to · Service Requests · BuilderCreate a service requestHow to build a service request so business users can trigger workflows on demand through a guided form.
• How-to · Workflows · BuilderCreate a workflowHow to build a workflow by adding jobs, dependencies, and schedules so OpCon Continuum can run your automation end to end.
• How-to · Transitioning from OpCon Classic · BuilderCreate a workflow: what changed from OpCon ClassicHow the Classic Schedule/Master/Daily authoring model maps to an OpCon Continuum workflow, and the steps to build your first one.
• How-to · Reports · AdministratorCreate and run reportsHow to build, run, and export reports so you can track job activity, agent health, and schedule outcomes.
• How-to · Workflows · BuilderCreate reusable container jobsHow to build a child workflow as a container job, then deploy it so other workflows can reuse the same set of steps.
• How-to · Transitioning from OpCon Classic · AdministratorCredentials: what changed from OpCon ClassicHow Classic's Batch Users map to OpCon Continuum connections, and the steps to set one up.
• Reference · Administration · AdministratorCustom fieldsHow to add your own tenant-global metadata fields to jobs, what each definition field controls, where values are set, and which input types are available.
• Concept · Dashboards · OperatorDashboardsHow each user is routed to the dashboard that matches their role, and what the Administrator, Operator, and Business dashboards surface.
• How-to · Toolkit · BuilderDefine a frequencyHow to define a frequency so workflows run only on the days and timing patterns you intend.
• How-to · Administration · AdministratorDefine custom fieldsHow to define custom fields so you can capture and track additional information on jobs across your environment.
• How-to · Transitioning from OpCon Classic · BuilderDeploy a job: what changed from OpCon ClassicHow promoting a Classic schedule between instances maps to versioning and deploying an OpCon Continuum workflow.
• Reference · Job types / Legacy (LSAM) · Builder · BETA PreviewEASE jobsHow 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.
• Reference · Connectors / Internal · BuilderEmbed another workflow with a Workflow ContainerHow to embed one workflow inside another with a Workflow Container so you can reuse and nest automation.
• Reference · Administration · AdministratorEnvironmentsWhat an environment is as a deployment target for workflows and service requests, the fields and service health it reports, and why a newly created one may still be provisioning.
• Reference · Event Log · OperatorEvent logHow 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.
• Reference · Agents · Administrator · BETA PreviewEvents raised by a legacy agentHow 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.
• How-to · Workflows · BuilderExchange files with a partnerHow 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.
• Reference · WorkflowsExport the canvas as an SVG imageWhat the SVG Image button in Canvas Tools produces — how the image is framed, which jobs it leaves out, the three messages that refuse an export, and why the file renders in a browser but opens blank in a vector editor.
• Reference · Toolkit · BuilderExpressions in property tokensThe expression language a property token can carry — arithmetic, comparisons, string and date functions, and nested evaluation — what each operator accepts, the precedence and value rules that decide the answer, and how a failed expression behaves in a job parameter, an event, a notification, and an expression dependency.
• How-to · Transitioning from OpCon Classic · BuilderFiles: how arrival and transfer work todayThe 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.
• Reference · WorkflowsForecast viewThe workflow editor's Forecast switch — how it redraws the canvas as the build for a chosen date, what each job card shows, how the estimated start window is worked out, and why it forecasts your unsaved edits.
• Reference · Toolkit · BuilderFrequenciesThe 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.
• How-to · Orientation · BuilderGet familiar as a BuilderA checklist of hands-on tasks so you can learn OpCon Continuum by building a workflow, its building blocks, and a service request in a test environment.
• How-to · Orientation · Business UserGet familiar as a Business UserA checklist of hands-on tasks so you can learn how to find and submit a service request through OpCon Continuum self-service.
• How-to · Orientation · AdministratorGet familiar as an AdministratorA checklist of hands-on tasks so you can learn OpCon Continuum administration by setting up agents, connections, and access in a test environment.
• How-to · Orientation · OperatorGet familiar as an OperatorA checklist of hands-on tasks so you can learn OpCon Continuum by monitoring a run and responding to jobs in a test environment.
• Concept · Orientation · Business UserGetting started with OpCon ContinuumAn orientation to OpCon Continuum that explains the main pieces and points each role to where to begin.
• Reference · Search · OperatorGlobal searchHow 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.
• Reference · OrientationGlossaryDefinitions of key OpCon Continuum terms so you can understand the vocabulary used across the documentation.
• Concept · Connectors / Job types · Business UserHow connectors workWhat a connector is, the four ways connectors run, which ones need a saved connection, and the catalog of job types available today.
• Concept · Processes / Runtime · OperatorHow the daily run worksHow 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.
• Concept · Workflows · BuilderHow workflows workWhat a workflow contains and how its jobs are ordered by dependencies, timed by frequencies and build settings, placed on agents, and versioned for deployment.
• Reference · Connectors / Job typesIntegrationsThe agents and connectors that are part of OpCon Continuum, and the documentation for every OpCon agent, connector, and utility, with the ones that work with Continuum today.
• Reference · Processes / Runtime · OperatorJob and workflow statusesThe 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.
• Reference · Workflows · BuilderJob configurationEvery 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.
• Reference · Workflows · BuilderJob dependenciesThe 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.
• Reference · Processes / Runtime · OperatorJob statuses and actionsA reference to job statuses and the operator actions available for each, so you know how to respond during the daily run.
• Reference · Job types · BuilderJob type catalogEvery job type available today, grouped by category, with the plugin it comes from, whether it needs a connection, and where it runs.
• Reference · OrientationLearning pathsPick your role to get a guided reading order through the OpCon Continuum documentation, grouped into modules that build on each other.
• Reference · Connectors / Legacy (LSAM) · BuilderLegacy LSAM connectors (UNIX/Linux, Windows, IBM i, and SQL)How the UNIX/Linux, Windows, IBM i, and SQL 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, library scripts, Symitar/Episys batch processing, and file-arrival waits on your existing legacy agents through a relay, and how to diagnose routing and exit-criteria failures.
• How-to · Agents · AdministratorManage agents and agent poolsHow to add, configure, and group agents into pools so work runs on the right machines and stays available.
• How-to · Connections · AdministratorManage connectionsHow to create, edit, and secure connections — both the endpoint and login for an external system and the batch user a legacy job runs as.
• How-to · Administration · AdministratorManage environmentsHow to create and manage environments so you can separate and promote work across development, test, and production.
• How-to · Notifications · Administrator · BETA PreviewManage notificationsHow to set up notification groups, triggers, and actions so the right people are told when an agent, workflow, or job needs attention.
• How-to · Plugins · AdministratorManage pluginsHow to enable, disable, and update plugins so you can extend OpCon Continuum with built-in and external capabilities.
• How-to · Toolkit · BuilderManage properties, calendars, and tagsHow to manage properties, calendars, and tags so you can reuse values, control timing, and organize work across workflows.
• How-to · Administration · Administrator · BETA PreviewManage roles and permissionsHow roles, permissions, and scopes control who can see and change what, and how to assign them.
• How-to · Administration · AdministratorManage workspacesHow to create and manage workspaces so you can organize work and control access by team or function.
• How-to · Vision · Operator · BETA PreviewMonitor critical paths and SLAs with VisionHow 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.
• How-to · Vision · Builder · BETA PreviewMonitor critical paths and SLAs with VisionHow to build Vision cards with service-level agreements so an at-risk critical path is visible before the deadline is missed.
• How-to · Transitioning from OpCon Classic · OperatorMonitor operations: what changed from OpCon ClassicHow Solution Manager Operations/Vision map to OpCon Continuum's Workflow View and Job View, and the operator actions available.
• How-to · Processes / Runtime · OperatorMonitor the daily runHow to monitor the daily run so you can track progress and act on jobs that need attention.
• Reference · Notifications · BETA PreviewNotification Manager (groups, triggers, channels)How notification groups, triggers, and channels decide who gets told when an agent, relay, workflow, or job changes state.
• Reference · Job types / Internal · BuilderNull JobWhat 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.
• Reference · Administration · BuilderObject namingThe character policy and length bounds that apply to the names you give properties, tags, calendars, frequencies, scripts, service requests, and every other named object, the objects that keep their own stricter rule, and what happens when you edit an object whose name predates the policy.
• Reference · Job types / Legacy (LSAM) · BuilderOpCon MFT Transfer jobHow 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.
• Reference · Job types / Legacy (LSAM) · BuilderOpCon RPA Task jobHow 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.
• Overview · OtherOperator documentationWatch the daily run, read job statuses at a glance, and know what to do when a job needs attention.
• Reference · Orientation · OperatorOperator learning pathA guided reading order for the Operator pages, grouped into modules that build on each other.
• Reference · Processes / Runtime · OperatorOperator response guideWhat 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.
• How-to · Workflows · BuilderOrder jobs with dependenciesHow to order jobs with dependencies so each job runs only after the jobs it relies on reach the right outcome.
• How-to · Transitioning from OpCon Classic · AdministratorOrganizing content: what changed from OpCon ClassicHow Classic Departments map to OpCon Continuum workspaces for keeping a team's or application's content separate.
• Reference · Plugins · AdministratorPluginsHow plugins package the job types your jobs can run, which plugins are enabled by default for a tenant, and why a job type you cannot build with is usually a disabled plugin.
• Reference · Agents · AdministratorPrepare agents for connectorsHow to prepare agents with the interpreters, drivers, and permissions each connector needs before running connector jobs.
• Reference · Toolkit · BuilderProperties and tagsHow workspace-scoped properties parameterize jobs and keep secrets out of job parameters, and how global tags organize and filter what you build.
• How-to · Service Requests · BuilderPublish a self-service request for business usersHow to build a workflow and a service request, deploy them, and hand business users a guided form so they can trigger the automation themselves.
• How-to · Workflows · BuilderRecover a failed run automaticallyHow 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.
• Reference · Agents · AdministratorRelaysWhat 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.
• Reference · Reports · AdministratorReportsWhat 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.
• How-to · Transitioning from OpCon Classic · AdministratorReports: what changed from OpCon ClassicHow 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 what has no report in this build.
• Reference · Connectors · OperatorRespond to a failed connector jobHow to diagnose and respond to a failed connector job so you can get a stalled workflow moving again.
• Reference · Processes / Runtime · OperatorRespond to a failed jobHow to respond to a failed job by reviewing the cause and choosing the right recovery action.
• Reference · Job types · OperatorRespond to a stuck or failed Wait for File jobHow to respond to a stuck or failed Wait for File job so a waiting workflow can continue or be escalated.
• Reference · Administration · Administrator · BETA PreviewRoles and permissionsHow roles, the permission catalog, and workspace and environment scopes shape what each person sees in Continuum, and the refusals that apply to every event.
• Reference · Connectors / Built-in · BuilderRun a commandHow to add and configure a Run Command job so a job runs a command or program on an agent.
• Reference · Connectors / Built-in · BuilderRun a scriptHow to add and configure a Run Script job so a job runs a script in the interpreter you choose on an agent.
• Reference · Job types / Built-in · BuilderRun Command jobHow 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.
• Reference · Connectors / Legacy (LSAM) · BuilderRun commands on legacy LSAM machinesHow to run commands on legacy LSAM machines so you can automate work on systems connected through the legacy relay.
• How-to · Workflows · BuilderRun events on job outcomesHow to run events on job outcomes so OpCon Continuum reacts automatically when a job succeeds, fails, or reaches a status.
• Reference · Job types / Built-in · BuilderRun Script jobHow 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.
• How-to · Workflows · BuilderSchedule a workflowHow to schedule and build a workflow so it is added to the daily run and ready to submit jobs.
• Reference · Workflows · BuilderSchedule instancesHow 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.
• How-to · Transitioning from OpCon Classic · BuilderScheduling and holidays: what changed from OpCon ClassicHow 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.
• Reference · Workflows · BuilderScheduling and the runHow 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.
• Reference · Scripts · BuilderScript libraryHow 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.
• How-to · Search · OperatorSearch across OpCon ContinuumHow to search across OpCon Continuum so you can quickly find jobs, workflows, and other objects.
• Reference · OrientationSee What's NewNew features and fixes in OpCon Continuum, by week and area.
• How-to · Transitioning from OpCon Classic · BuilderSelf Service: what changed from OpCon ClassicHow Classic Self Service maps to OpCon Continuum service requests, and the steps to build and deploy one.
• Concept · Self Service · Business UserSelf-service portalHow 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.
• Reference · Service Requests · BuilderService requestsWhat 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.
• How-to · Agents · AdministratorSet up and manage relaysHow to register, install, and maintain a relay so your on-prem legacy LSAM machines can run jobs dispatched from the cloud.
• Reference · Connections · AdministratorSet up database connectionsHow to set up and test database connections so jobs can run SQL against your databases securely.
• How-to · Notifications · Administrator · BETA PreviewSet up failure notificationsHow to create a notification group, target the jobs that matter, and prove it works, so a failure overnight never goes unnoticed.
• Reference · Job types / Legacy (LSAM) · BuilderSMAFT File Transfer jobHow 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.
• How-to · Self Service · Business UserSubmit a service requestHow to submit a service request so you can trigger an automated workflow without building it yourself.
• Reference · Transitioning from OpCon Classic · BuilderTerminology: OpCon Classic to OpCon ContinuumA single lookup table mapping OpCon Classic terms to their OpCon Continuum equivalents, with a link to the page that explains each change.
• Reference · Processes / Runtime · OperatorThe Processes page (runtime)How to work the Processes page, including the Job and Workflow views, filters and search, single and bulk job actions, and job detail.
• Reference · WorkflowsThe workflow editor tool panelThe panel down the left of the workflow editor — Search Jobs, New Job, the Card Filters and Frequencies switches, and Canvas Tools with its minimap, zoom, fit, re-layout and undo controls.
• Reference · Toolkit · BuilderThresholds and resourcesHow thresholds gate jobs on a numeric value and resources limit how many jobs run at once, and how jobs reference both as dependencies.
• Concept · Toolkit · BuilderToolkit overviewThe reusable building blocks you define once and use across workflows — frequencies, calendars, thresholds, resources, properties, and tags — and which are global versus workspace-scoped.
• Overview · Transitioning from OpCon ClassicTransitioning from OpCon ClassicHow familiar OpCon Classic concepts map to OpCon Continuum, and the steps to do the same jobs the OpCon Continuum way.
• Concept · Connectors / Internal · BuilderUse a Null JobWhen and how to use a Null Job as a placeholder or dependency anchor to simplify workflow structure.
• How-to · Event Log · OperatorUse the event logHow to use the event log to trace what happened during a run using correlation IDs and event statuses.
• How-to · Toolkit · BuilderUse thresholds and resourcesHow to use thresholds and resources to control concurrency and coordinate jobs that share limited capacity.
• How-to · Workflows · BuilderVersion and deploy a workflowHow to version and deploy a workflow so you can review, promote, and roll back changes safely.
• Reference · Vision · BETA PreviewVision (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.
• Reference · Job types · BuilderWait for a file before your workflow continuesHow to add and configure a Wait for File job so a workflow waits until a file has arrived and is complete before continuing.
• Reference · Job types / Built-in · BuilderWait for File jobHow 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.
• How-to · Transitioning from OpCon Classic · BuilderWhat a job does: what changed from OpCon ClassicHow Classic's fixed job-type catalog maps to OpCon Continuum job types and connectors, including legacy LSAM commands.
• Concept · Positioning · Business User · BETA PreviewWhat changes for your roleWhat OpCon Continuum changes for Administrators, Builders, Operators, and business users, and which of those areas are still maturing.
• Concept · Transitioning from OpCon Classic · AdministratorWhat migration looks likeWhat 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.
• Concept · Connectors · Business UserWhat OpCon Continuum can automateA business-level overview of what OpCon Continuum can automate and why connectors matter for your bank or credit union.
• How-to · Transitioning from OpCon Classic · AdministratorWhere jobs run: what changed from OpCon ClassicHow Classic machines and machine groups map to OpCon Continuum agents and agent pools, including how existing LSAM machines keep running through the relay.
• How-to · Processes / Runtime · OperatorWork the Processes pageHow to use the Processes page to watch the daily run and act on jobs -- filter, search, and take single or bulk actions.
• Reference · Job types / Internal · BuilderWorkflow Container jobHow 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.
• Reference · Workflows · BuilderWorkflow eventsHow events fire a command in response to a job outcome, whether that is a status, a comparison against the job's termination description, or a completion expression, and which triggers and operators are available.
• Reference · Workflows · BuilderWorkflow versions and deploymentsHow every saved change to a workflow becomes a reviewable version you can roll back to, and how deployments decide which version runs in which environment.
• Reference · Administration · AdministratorWorkspacesHow workspaces group and isolate workflows, properties, thresholds, resources, scripts, and service requests, what stays global, and why access comes from role scopes rather than workspace membership.