Job type catalog
The complete list of job types available today, grouped by category.
Every job in a workflow runs exactly one job type — the thing that decides what the job actually does. Job types are not built into the product one by one: each comes from a plugin (a connector), and each plugin declares a category. Enable a plugin and its job types become available to Builders; disable it and they disappear from new jobs.
Where you choose a job type
In the job editor, on the Job Definition tab, select Show Job Types to open the job type catalog, then pick a type.
Once a type is chosen, the Job Parameters section renders the fields that type declares. Changing the type later clears both the old parameters and the agent assignment, because neither carries over. Agent Assignment appears only for types that run on an agent — Null Job and Workflow Container run in the platform, so it is hidden for them.
The workflow editor sidebar also offers a quick-add shortcut that creates a job with its type already set.
The categories below are each plugin's own category. They are how the Plugins administration page groups and filters plugins; they are not headings in the picker.
The catalog
58 job types across 14 plugins. The newest are the twenty in the new EASE (Episys As A Service) plugin, which runs jobs on Jack Henry's hosted EASE OpCon — three of those twenty are in the catalog but not supported yet. One other, IBM i (AS/400) Batch Job, is also recent and its enablement is still in progress.
Script
| Job type | Plugin | What it does | Connection | Runs on |
|---|---|---|---|---|
| Run Command | Run Command | Runs a command line on the agent — either through a shell (the default) or as a direct process | None | Universal Agent — Windows, Linux, macOS |
| Run Script | Run Script | Runs an embedded script you type into the job, using the matching interpreter: PowerShell, Bash, Python, or Shell | None | Universal Agent — Windows, Linux, macOS |
Both are built in to the Universal Agent, so there is nothing to install or enable. See Run Command job and Run Script job.
Utility
| Job type | Plugin | What it does | Connection | Runs on |
|---|---|---|---|---|
| Wait for File | Wait for File | Holds the workflow until a file appears and meets optional size, age, and stability criteria; can delete the file once detected | None | Universal Agent — Windows, Linux, macOS |
Also built in. See Wait for File job.
Database
All six come from one plugin — SQL Database Executor — and all six require a saved connection of the matching type. The plugin is disabled by default: an administrator has to enable it per organization.
Jobs of these six types do not run in this build. They can be added to a workflow, but the agent is never given the connector, so every one fails with External plugin sql-executor requires pluginDownloadUrl and pluginChecksum.
| Job type | What it does | Connection type | Runs on |
|---|---|---|---|
| MS SQL Script | Runs T-SQL scripts against SQL Server | SQL Server | Universal Agent — Windows, Linux, macOS |
| MS SQL Job | Starts a SQL Server Agent job and monitors it (by default, until it completes) | SQL Server | Universal Agent — Windows, Linux |
| MS SQL DTExec (SSIS) | Runs a SQL Server Integration Services package | SQL Server | Universal Agent — Windows only |
| MySQL Script | Runs queries against MySQL | MySQL | Universal Agent — Windows, Linux, macOS |
| Oracle Script | Runs scripts against Oracle Database | Oracle | Universal Agent — Windows, Linux |
| Other DB Script (ODBC) | Generic database access via an ODBC/OleDB connection string | ODBC | Universal Agent — Windows, Linux |
See Connections.
Internal
These run inside the platform. No agent is involved, so they have no agent assignment and no OS requirement.
| Job type | Plugin | What it does | Connection | Runs on |
|---|---|---|---|---|
| Null Job | Null Job | Completes immediately. Used to aggregate dependencies, hang events off a single point, and build a workflow on hold. Takes no parameters | None | The platform — no agent |
| Workflow Container | Workflow Container | Embeds another workflow as a single step; the referenced workflow is built and run as part of this one | None | The platform — no agent |
See Null Job and Workflow Container job.
Integration — legacy LSAM
These drive your existing OpCon LSAM machines through a relay, so you can bring current automation into OpCon Continuum without rebuilding it. They dispatch only to legacy agents of the matching type, never to a Universal Agent, and they need a configured relay to work at all.
| Job type | Plugin | What it does | Agent type |
|---|---|---|---|
| UNIX Command | UNIX/Linux LSAM | Runs a command or script on a UNIX/Linux LSAM machine | UNIX LSAM |
| UNIX - File Arrival | UNIX/Linux LSAM | Waits for a file to arrive during a time window and succeeds once it has stopped growing; the LSAM agent does the watching, so there is no connector to install and no command line | UNIX LSAM |
| UNIX - Embedded Script | UNIX/Linux LSAM | Runs a script from the script library — you choose the script, the version to track or pin, a runner, and optional arguments | UNIX LSAM |
| UNIX - Episys: Run JobFile | UNIX/Linux LSAM | Runs an Episys batch job file through RSJ, optionally from a restart point, with an edit file or without the SYM lock | UNIX LSAM |
| UNIX - Episys: Answer Prompts | UNIX/Linux LSAM | Fills in the prompts in an Episys batch control file, one prompt-and-response row per prompt | UNIX LSAM |
| UNIX - Episys: Compare ACH Totals | UNIX/Linux LSAM | Compares a FED ACH file's totals against an Episys batch output | UNIX LSAM |
| UNIX - Episys: Find Batch Output Sequence Number | UNIX/Linux LSAM | Finds an Episys job's batch output sequence number and writes it to a property you name | UNIX LSAM |
| UNIX - Episys: Find Report from RSJ Output | UNIX/Linux LSAM | Finds a report by title in an Episys job's RSJ output and writes its sequence number to a property you name | UNIX LSAM |
| UNIX - Episys: Find Report from Episys Reports | UNIX/Linux LSAM | Finds a report by title in the Episys report directory and writes its sequence number to a property you name | UNIX LSAM |
| UNIX - Episys: FTP all Reports in List | UNIX/Linux LSAM | Sends every report listed in a file to an FTP destination | UNIX LSAM |
| Windows Command | Windows LSAM | Runs a command on a Windows LSAM machine | Windows LSAM |
| Windows - WS_FTP Pro | Windows LSAM | Runs a WS_FTP Pro file transfer using site profiles configured on the machine | Windows LSAM |
| Windows - Command: File Copy | Windows LSAM | Copies one or more files (wildcards allowed) | Windows LSAM |
| Windows - Command: File Move | Windows LSAM | Moves one or more files, overwriting the destination without prompting | Windows LSAM |
| Windows - Command: File Rename | Windows LSAM | Renames a single file (cannot overwrite an existing name) | Windows LSAM |
| Windows - Command: File Delete | Windows LSAM | Deletes one or more files or directories (wildcards allowed) | Windows LSAM |
| Windows - Corelation | Windows LSAM | Submits and monitors a Corelation batch job through the SMA Corelation connector on the machine | Windows LSAM |
| Windows - Fiserv DNA | Windows LSAM | Runs a Fiserv DNA SQT job through the SMA DNA connector on the machine | Windows LSAM |
| Windows - Fiserv DNA (File Loader) | Windows LSAM | Runs a Fiserv DNA file-load job through the SMA DNA connector on the machine | Windows LSAM |
| Windows - File Arrival | Windows LSAM | Waits for a file to arrive during a time window and succeeds once it has stopped changing; uses the LSAM's own file watcher, so there is no connector to install | Windows LSAM |
| Windows - Embedded Script | Windows LSAM | Runs a script from the script library — you choose the script, the version to track or pin, and a runner | Windows LSAM |
| Windows - Web Services | Windows LSAM | Runs a sequence of HTTP/REST calls through the SMA Web Services connector on the machine, passing values extracted from one response into later requests | Windows LSAM |
| IBM i (AS/400) Batch Job | IBM i LSAM | Submits a batch job on an IBM i (AS/400) LSAM machine. Enablement in progress — no exit-criteria setting | IBM i LSAM |
| MS SQL Script | SQL LSAM | Runs a T-SQL script on a SQL LSAM machine — inline statements you type into the job, or a .sql file already on the machine. No exit-criteria setting | SQL LSAM |
Every one of them takes a batch user connection — the account it runs as. On Windows, IBM i and SQL that field may be left blank (the agent's service account, the job description's default user, and the agent's service account, respectively); on UNIX it is required. See Batch User.
Four Episys types take a second connection on top of the batch user, for the credential the Episys utility itself needs: the three Find types take an Episys External Event Credential, and FTP all Reports in List takes an Episys FTP Credential. See Episys credentials.
The four file-operation types, WS_FTP Pro, Corelation, Web Services and all seven Episys types build their command line for you from form fields, so they have no command-line field of their own.
See Legacy LSAM connectors and Relays.
Integration — OpCon RPA
| Job type | Plugin | What it does | Agent type |
|---|---|---|---|
| OpCon RPA Task | OpCon RPA | Starts one RPA task — a Robot, a Web Macro or a Scan Document — on an OpCon RPA agent, waits for it to finish, and shows the agent's own logs as the job output | OpCon RPA |
It takes no connection of any kind — no batch user — and it has no exit-criteria setting: the process status the agent reports is the job's verdict. Like an OpCon MFT agent, an OpCon RPA agent is reached through a relay but is not an LSAM, so it has no JORS port and no file-transfer endpoint. Its Task and Version lists are read live from the agent, and an empty Version means run the highest version that exists when the job starts. See OpCon RPA Task job.
Integration — EASE
Twenty job types from one plugin, EASE (Episys As A Service). Each adds the matching pre-built job to today's instance of your schedule on Jack Henry's EASE OpCon, waits for it to finish, and brings the remote job's output back. Like OpCon MFT and OpCon RPA, an EASE agent is reached through a relay but is not an LSAM — no JORS port, no file-transfer endpoint. None of the twenty takes a connection, and none has an exit-criteria setting.
| Job type | What it does | Agent type |
|---|---|---|
| EASE - RSJ | Runs a Symitar job, single-threaded | EASE |
| EASE - RSJMULTI | Runs a Symitar job, multi-threaded | EASE |
| EASE - RSJEDIT | Runs a Symitar job with an edit file | EASE |
| EASE - MONITOR | Watches for an incoming file | EASE |
| EASE - PROMPT | Answers a single prompt | EASE |
| EASE - PROMPTSEQ | Answers a single prompt with a SEQ | EASE |
| EASE - TRANSLATE2COMMAS | Answers a single prompt whose response contains commas | EASE |
| EASE - RESET | Resets a single prompt | EASE |
| EASE - SEQ | Collects a report's sequence number and writes it to the global property SEQ-<identifier> | EASE |
| EASE - SEQ-SEND | Copies a specified SEQ to the reports directory for FTP | EASE |
| EASE - COPY-RPT-OUT | Copies a report to the letter files directory for FTP | EASE |
| EASE - COPY-DATA-TO-LTRFILE | Copies an outgoing data file to the letter files directory | EASE |
| EASE - COPY-RENAME-LTRFILE-OUT | Copies or renames a letter file for FTP, chosen by Action | EASE |
| EASE - MOVE-LTRFILE-TO-DATA | Moves an incoming letter file to the data files directory | EASE |
| EASE - RENAME-LTRFILE-IN | Renames a letter file, removing its prefix | EASE |
| EASE - FILEPERMS | Sets a letter file's privileges to 774 | EASE |
| EASE - RUN-FTP-OUT | FTPs a letter file off Symitar | EASE |
| EASE - BUNDLE-RSJEDIT | Not supported yet — fails at start. In Classic, MONITOR then RSJEDIT | EASE |
| EASE - BUNDLE-SEQ-FTP | Not supported yet — fails at start. In Classic, SEQ, COPY-RPT-OUT then RUN-FTP-OUT | EASE |
| EASE - BUNDLE-SEQ-PROMPT | Not supported yet — fails at start. In Classic, SEQ then PROMPT | EASE |
The three BUNDLE types ship so that a migrated job keeps its field values; a job of one of those types fails as soon as it starts, with a message telling you to model the bundled steps as separate EASE jobs. See EASE jobs.
File transfer — legacy
| Job type | Plugin | What it does | Agent type |
|---|---|---|---|
| SMAFT File Transfer | SMAFT File Transfer | Moves a file between any two file-transfer-capable legacy machines, in either direction. You name a source and a destination machine, and Start Transfer On decides which of the two runs the job | Windows or UNIX LSAM |
| OpCon MFT Transfer | OpCon MFT | Downloads files from one endpoint on an OpCon MFT agent, optionally compresses, decompresses, encrypts, decrypts or renames them, and uploads them to another endpoint on the same agent | OpCon MFT |
SMAFT File Transfer is the only job type that names two machines, and the only one whose machine is derived from its own parameters rather than picked in Agent Assignment. It takes up to two batch users, one per end, and both machines need a file-transfer endpoint before a transfer can be built. See SMAFT File Transfer job.
OpCon MFT Transfer names one machine, picked in Agent Assignment as usual, and moves files between two endpoints configured on that agent. Its optional Compression Password is a connection rather than a typed value, and its endpoint and PGP key lists are read live from the agent. An OpCon MFT agent is reached through a relay but is not an LSAM — it has no JORS port and no file-transfer endpoint, so it can be neither end of a SMAFT transfer. See OpCon MFT Transfer job.
The category list
Nine categories are defined. Six are in use today; the other three are defined for future plugins and no shipped plugin uses them yet.
| Category | In use today |
|---|---|
| Script | Run Command, Run Script |
| Database | SQL Database Executor |
| Integration | UNIX/Linux LSAM, Windows LSAM, IBM i LSAM, SQL LSAM, OpCon RPA, EASE |
| Utility | Wait for File |
| Internal | Null Job, Workflow Container |
| File Transfer | SMAFT File Transfer, OpCon MFT |
| File | — none yet |
| Container | — none yet |
| Custom | — none yet |
Note that Workflow Container is in the Internal category, not Container, and Windows - WS_FTP Pro is in Integration, not File Transfer — a job type's category follows the plugin that provides it, not the kind of work it does. The SMAFT plugin was the first to declare File Transfer; the OpCon MFT plugin is the second.
What's available to you
A job type appears in the picker only if its plugin is enabled for your organization.
| Plugin | Enabled by default? |
|---|---|
| Run Command, Run Script, Wait for File | Yes |
| Null Job, Workflow Container | Yes |
| Legacy LSAM (UNIX/Linux, Windows, IBM i, SQL, SMAFT File Transfer) | Yes — but a job still needs a working relay and a registered LSAM agent. A transfer additionally needs a file-transfer endpoint on both machines |
| OpCon MFT | Yes — but a job still needs a working relay and a registered OpCon MFT agent, and the endpoints it names must already exist on that agent |
| OpCon RPA | Yes — but a job still needs a working relay and a registered OpCon RPA agent with its API token stored, and the task it names must already exist on that agent |
| EASE | Yes — but a job still needs a relay that reports EASE support and a registered EASE agent with its Customer Id, EASE Schedule Name and login stored |
| SQL Database Executor | No — must be enabled per organization |
A plugin can have several versions installed; new jobs pick up its default version. See Plugins.
Where a job can run
Each job type declares what it needs from an agent — an agent type (Universal, UNIX LSAM, Windows LSAM, IBM i LSAM, SQL LSAM, OpCon MFT, OpCon RPA, or EASE) and sometimes a specific operating system. The platform only dispatches a job to an agent that matches, so a job type never lands somewhere it can't run. If no matching agent is available, the job can't be assigned. See Agents and pools.
- A job type is fixed once a job has been processed. In a running or completed instance the Job Type picker is read-only; you choose it while designing the job, not while it runs.
- Changing the job type clears its parameters and its agent. Compatible agents are job-type-specific, so neither can safely carry over. Re-set both after a change.
- "The job type I need isn't in the list" almost always means its plugin is disabled — the SQL Database Executor is off by default. Check Plugins before anything else.
- Two job types are both called MS SQL Script, and the plugin column is what tells them apart. The SQL Database Executor one is for a Universal Agent with a saved SQL Server connection, and does not run in this build; the SQL LSAM one runs on an existing SQL LSAM machine through the relay and takes a batch user.
- Job-type parameters are validated against the plugin's declared fields before work reaches an agent, so a misconfigured job is rejected up front rather than failing on the agent. The legacy LSAM types are the exception: their fields are checked by the relay at dispatch, so a job with a bad value saves cleanly and fails when it runs. The two file-transfer types are partial exceptions to the exception — a set of cross-field rules is enforced when you save a SMAFT transfer or an OpCon MFT transfer.
- Null Job is not a no-op to skip past. It's a workflow-design workhorse — the standard way to fan many dependencies into one point.
- A job may itself be a whole workflow. When troubleshooting, remember a Workflow Container step expands into a child workflow.
- Two families of job type use a saved connection. The Database types need one for the database they query, and the legacy LSAM types take one for the account they run as. The built-in command, script, file-wait, and internal types need none — they take their credentials from the agent.
- A legacy LSAM type with no working relay can't be placed at all. That surfaces as "no agent available" rather than as a relay error, which is worth knowing before you go looking for one.
Related topics
- How connectors work — the connector model behind this list
- Job configuration — everything else on a job besides its type
- Plugins — enabling and versioning the plugins that supply job types
- OpCon RPA Task job — running an RPA robot, web macro or document scan from a workflow
- EASE jobs — running a job on Jack Henry's hosted EASE OpCon
- Create a workflow — using a job type in practice