65 docs tagged with "Builder"

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.

A guided reading order for the Builder pages, grouped into modules that build on each other.

How 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.

What 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 build a service request so business users can trigger workflows on demand through a guided form.

How to build a workflow by adding jobs, dependencies, and schedules so OpCon Continuum can run your automation end to end.

How the Classic Schedule/Master/Daily authoring model maps to an OpCon Continuum workflow, and the steps to build your first one.

How to build a child workflow as a container job, then deploy it so other workflows can reuse the same set of steps.

How Classic's Batch Users map to OpCon Continuum connections, and the steps to set one up.

How to define a frequency so workflows run only on the days and timing patterns you intend.

How promoting a Classic schedule between instances maps to versioning and deploying an OpCon Continuum workflow.

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.

How to embed one workflow inside another with a Workflow Container so you can reuse and nest automation.

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.

What 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.

The 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.

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.

The 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.

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.

A 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.

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.

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.

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.

Every job type available today, grouped by category, with the plugin it comes from, whether it needs a connection, and where it runs.

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 manage properties, calendars, and tags so you can reuse values, control timing, and organize work across workflows.

How to build Vision cards with service-level agreements so an at-risk critical path is visible before the deadline is missed.

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.

The 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.

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.

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.

How to order jobs with dependencies so each job runs only after the jobs it relies on reach the right outcome.

How Classic Departments map to OpCon Continuum workspaces for keeping a team's or application's content separate.

How workspace-scoped properties parameterize jobs and keep secrets out of job parameters, and how global tags organize and filter what you build.

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.

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.

How to add and configure a Run Command job so a job runs a command or program on an agent.

How to add and configure a Run Script job so a job runs a script in the interpreter you choose on an agent.

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.

How to run commands on legacy LSAM machines so you can automate work on systems connected through the legacy relay.

How to run events on job outcomes so OpCon Continuum reacts automatically when a job succeeds, fails, or reaches a status.

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.

How to schedule and build a workflow so it is added to the daily run and ready to submit jobs.

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.

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.

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.

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.

How Classic Self Service maps to OpCon Continuum service requests, and the steps to build and deploy one.

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.

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.

The 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.

How thresholds gate jobs on a numeric value and resources limit how many jobs run at once, and how jobs reference both as dependencies.

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.

When and how to use a Null Job as a placeholder or dependency anchor to simplify workflow structure.

How to use thresholds and resources to control concurrency and coordinate jobs that share limited capacity.

How to version and deploy a workflow so you can review, promote, and roll back changes safely.

How to add and configure a Wait for File job so a workflow waits until a file has arrived and is complete before continuing.

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.

How Classic's fixed job-type catalog maps to OpCon Continuum job types and connectors, including legacy LSAM commands.

What OpCon Continuum changes for Administrators, Builders, Operators, and business users, and which of those areas are still maturing.

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.

How Classic machines and machine groups map to OpCon Continuum agents and agent pools, including how existing LSAM machines keep running through the relay.

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.

How 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.

How 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.