Skip to main content

Builder learning path

This is the order to work through the Builder pages. Each module builds on the one before it, so you meet a workflow before you deploy one, and the individual job types before the end-to-end scenarios that combine them.

You don't have to follow it end to end. Each module stands on its own, so it also works as a checklist for one area you're picking up.

How to read a module

Each module runs from the task to the detail: the how-to page first, then the concept behind it, then the full reference, and finally an end-to-end scenario where one exists. Stopping after the how-to page is a perfectly good outcome if that's all you need today.

8 modules · 45 pages · about 6 hr 5 min of reading estimated so far, across 22 of the 45 pages

  1. Workflow basics

    What you'll be able to do
    • Explain what a workflow contains and how jobs are ordered and timed
    • Identify the four dependency types and the three agent-assignment modes
    • Explain how build settings, frequencies, and calendars determine what runs and when
    • Diagnose why a job did or didn't build into a day's run
    • Explain what a schedule instance is and how it differs from a multi-instance job
    • Define named instances on a workflow and give each its own property values
    • Build one named instance, or every instance at once, and read the result
    • Predict how a dependency, a conflict or an event resolves when several instances exist
    • Build one instance more than once for a date, and tell a repeat run from a rebuild
    • Describe the four dependency types and the two axes of a job dependency (Condition and Type)
    • Explain how the day offset lets a job depend on another day's run
    • Predict what an expression dependency does to a job when it renders True, False, or cannot be evaluated
    • Diagnose a job that is waiting on an unmet dependency
    • Identify the configurable parts of a job and the three agent-assignment modes
    • Explain what a workflow copy carries across and what it deliberately does not
    • Apply the workflow name rules, including the 40-character ceiling
    • Predict how dependencies behave in a copy, inside and across workflows

  2. Toolkit basics

    What you'll be able to do
    • Explain what each Toolkit item is and which are workspace-scoped vs global
    • Describe the frequency pattern model and what the forecast shows
    • Predict where a pattern lands when a match falls on a non-working day
    • Explain how thresholds gate jobs and how resources limit concurrency
    • Explain how a job references a library script, and when to pin a version rather than track the latest

  3. Legacy connectors

    What you'll be able to do
    • Configure a UNIX or Windows LSAM command job and route it to the right machine
    • Attach the right batch user to a legacy Windows, UNIX, or IBM i job, and know what a blank Batch User field means on each platform
    • Apply the remaining Windows limitations (no embedded scripts on the command job) and use the Windows fields brought to Classic parity (env vars, output parsing, command shell, custom log path)
    • Configure a Windows WS_FTP Pro file-transfer job using site profiles defined on the agent
    • Configure the Windows file-operation job types (Copy, Move, Rename, Delete)
    • Configure a Windows Corelation job that submits and monitors a Corelation batch job
    • Configure a Windows Fiserv DNA job (SQT job or File Loader) that runs a DNA job through the connector on the machine
    • Configure a Windows File Arrival job that waits for a file during a time window, and read its exit code
    • Configure a UNIX File Arrival job, keep its path inside the characters the relay accepts, and read its exit code
    • Configure a UNIX Embedded Script job against the script library, and quote its arguments correctly
    • Configure the UNIX Episys job types against an existing RSJ install, including the RSJPATH property and the two Episys credential connections
    • Recognise that an Episys credential is visible in the job output, and scope the account accordingly
    • Use the arrived file's path and its parts in the events and notifications a File Arrival job fires
    • Build a Windows Web Services job as a sequence of HTTP steps, pass extracted values between them, and set the exit criterion its raw-HTTP-status exit code requires
    • Recognise that the IBM i job type carries no exit criteria, and how that changes failure detection
    • Configure a SQL LSAM MS SQL Script job, choose between inline T-SQL and a script file on the machine, and set its authentication and encryption
    • Diagnose relay/connectivity and exit-criteria failures
    • Configure a SMAFT File Transfer job and predict which machine runs the transfer
    • Attach the right batch user to each end, and know what a blank Batch User means per platform
    • Apply the cross-field rules that refuse a save, fail a dispatch, or hold the job
    • Register an EASE agent and predict which EASE schedule a job will be added to
    • Configure an EASE job and read its outcome from the remote job's status
    • Account for the SEQ property write-back and what it needs before it can succeed
    • Configure an OpCon MFT Transfer job and predict the order its steps run in
    • Attach a compression password connection and know what leaving it empty means
    • Apply the cross-field rules that refuse a save, and recognise the two combinations that silently drop a step
    • Configure an OpCon RPA Task job and predict which task version it will run
    • Read an RPA job's outcome from the process status the agent reports
    • Account for the instance properties the job carries to the agent, and the ones it withholds

  4. Service requests

    What you'll be able to do
    • Describe a service request's inputs, events, deployments, and transformations

  5. End-to-end outcomes

  6. Transitioning from OpCon Classic

  7. Internal job types

    What you'll be able to do
    • Explain the design uses of a Null Job (aggregation, events, on-hold builds)
    • Recognize when a "stuck" Null Job is really a dependency or on-hold condition
    • Configure a Workflow Container to embed another workflow as a step
    • Diagnose missing-reference, circular-reference, and nesting-depth failures

  8. Built in job types

    What you'll be able to do
    • Name every job type available today and the category it belongs to
    • Determine whether a job type needs a connection, an agent, or a relay before using it
    • Configure a Run Command job, choosing shell vs direct execution appropriately
    • Use exit criteria and output parsing to define what counts as failure
    • Diagnose command-not-found, environment-filtering, and exit-code failures
    • Configure a Run Script job for PowerShell, Bash, Python, or Shell
    • Use exit criteria and output parsing to define what counts as failure
    • Diagnose missing-interpreter and exit-code failures
    • Configure a Wait for File job using size, age, and stability criteria
    • Predict the job outcome for timeout, missing-file, and restricted-path cases

Where the time estimates come from​

The estimates are authored per page and not every page has one yet, so a module or role total covers only the pages that do — treat it as a floor, not a full syllabus.

Related topics