Documentation
Back to Ribbon Hub

Job Console

The Job Console — the Job Orchestrator — runs Calculation Manager rules, rulesets and data load processes directly from Excel, and the Job Monitor next to it shows how they actually ran. Scheduling is not part of the add-in; that is what EPM Conductor does.

Run a job

Every job defined in the application — business rules, rulesets, imports, exports and the rest — is listed in the job catalog and runs from Excel.

  1. Click Job Console in the Operation Management group.
  2. Find the job in the catalog and choose Run.
  3. If the job has Runtime Prompts, a form appears with searchable member, alias and substitution-variable pickers, showing hierarchy depth. The values the job last ran with are remembered once the pod accepts the job.
  4. Submit. The job runs on the pod; Excel stays responsive while it does.

Rulesets

Rulesets defined in Calculation Manager appear in the same catalog and run as one job, in the order Calculation Manager holds them — the usual shape of a month-end close chain.

Sequences

Queue jobs of any type into the sequence tray and run them in order from Excel — rules, imports and exports in one chain, so the overnight sequence stops being a script only one person understands.

A sequence runs while Excel is open and you are signed in. For unattended, scheduled runs use EPM Conductor.

Job Monitor

A separate button beside the Job Console. It downloads the job console execution records and reports how jobs actually ran over 7, 30 and 60 days — by rate, not raw count.

Runs per day, success rate, failures grouped by job, total run time and the timing trend per job, with the failure reason attached rather than a status code. The history is kept locally, so nothing re-runs on the pod to produce it, and it is the same history the Job History report module reads.