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.
Building and ordering the jobs in a workflow.
View all tagsHow 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.
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 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 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 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.
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.
How to order jobs with dependencies so each job runs only after the jobs it relies on reach the right outcome.
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 run events on job outcomes so OpCon Continuum reacts automatically when a job succeeds, fails, or reaches a status.
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 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.
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 to version and deploy a workflow so you can review, promote, and roll back changes safely.
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.