Skip to main content

EASE jobs

BETA Preview

This feature is still being finalized by Development.

In briefAn EASE job adds the matching pre-built job to today's instance of your schedule on Jack Henry's hosted EASE OpCon, waits for it to finish, and reports the remote job's status as its own outcome. Twenty EASE job types come from one plugin; seventeen work today, and the three BUNDLE types fail as soon as they start.

WhereRegister the agent on the Agents tab with New Agent and the agent type EASE. Build the job in the job editor: Job Definition tab › Job Type, choosing one of the EASE - ... types, then name the EASE agent in Agent Assignment.

When

  • You run Symitar work on EASE and want a workflow to drive it.
  • A later job needs a report's sequence number — an EASE - SEQ job writes it to the global property SEQ-<identifier>.
  • An EASE job failed, or is still running after the remote job finished.

For Symitar work on a UNIX machine you run yourself, use the Episys job types instead.

How

  1. Make sure the relay reports EASE support, then register the EASE agent with its host, port, Customer Id, EASE Schedule Name, EASE User and EASE Password.
  2. For SEQ jobs, also store Local Event User and Local Event Token and set the agent's Default Event Environment.
  3. Add a job, choose the EASE job type, fill in its fields and assign the agent.

The full detail is in Before you can build one and Registering the agent.

Notes
  • EASE jobs take no connection and have no exit-criteria setting: the remote job's status decides the outcome.
  • Set Time Zone on the agent if the relay host's date can differ from the EASE schedule's day.
  • A rejected login holds further logins off for five minutes; editing the agent's user or password clears the hold.
Watch out
  • Do not build on the three BUNDLE types. Model the bundled steps as separate EASE jobs with dependencies.
  • An add failure that ends the job may have been added to the EASE schedule is ambiguous — check the EASE schedule before you restart the job.
  • A remote job left in a status the outcome table does not name keeps the Continuum job running until you kill it.