Batch
Mass functions: the jobs every module runs over many records at once, the run books that order them, and what each run actually touched. A job that takes longer than anybody will wait runs in the background, and one nobody should have to be awake for runs on a schedule.
12 steps · 10 questions · 7 screens on this shelf
The screens on this shelf
Workspace
Batch Console
The job library for every module, with a rehearsal that shows which records a job would touch before it touches them.
Open
Records
Job Definitions
What each job selects, what it does to what it selects, and whether it is safe to run twice.
Open
Records
Job Sets
A run book: several jobs in the order somebody would run them by hand, and what to do when one of them fails.
Open
Records
Set Steps
The order of a run book, and which steps may fail without stopping it.
Open
Records
Job Schedules
When each job runs without anybody starting it. Every one of these fires in the background as the person who created it, so it may take as long as it takes — which is the point for a large file read off a drive, or a folder somebody drops one into every morning. "State" says whether it is waiting, running, overdue or paused; overdue for long means the API is not running the scheduler.
Open
View
Job Runs
Every run that has happened, what it selected, and what it did to each record. A run cannot be deleted — that is the point of keeping it.
Open
View
Set Runs
A run book executed end to end, including where it stopped.
Open
Progress is kept in this browser only — it is not sent anywhere and nobody else can see it.