Batch
One callable program that orchestrates several steps, a multi-part procedure with one id to call it by.
A Batch program orchestrates several steps as one callable operation. Anywhere a procedure would otherwise be copy-pasted across Components, a multi-step save, a loop over records, a sequence of API calls, a Batch gives it one name and one id. From a caller's side it looks exactly like a Get Data or Set Data program: call it with the batch action, pass parameters, get a result back.
Properties
progFields
Batch parameters follow the common shape (data.field_id, data.type: "virtual", props.fieldType), referenced inside the Batch's workflow as @field_id.
progEvents and the workflow body
Unlike a Table or an Alert, a Batch's actual logic is not a top-level array, it lives inside progEvents, almost always the on_load event, whose workflow array is the Batch's body:
A step inside that workflow can be any action in the Workflow catalog: get_data, set_data, call_native_javascript, call_project_api, call_external_api, delay, update, raise_event, a nested batch call, and more. Each step can carry props.condition to gate it, or props.async: true to fire it without waiting.
Calling a Batch
Worked example
Declare the parameters
progParams for whatever the Batch needs from its caller, mirrored into progFields.
Build the body on on_load
Add steps to the on_load event's workflow: a get_data to read, a computation, a set_data to write back.
Call it like any other program
batch action, name.prog set to this Batch's id, results reachable through the caller's own fields.
Create a Batch node under Programs, declare parameters on its Properties tab, then build the step sequence on the Events → on_load → Workflow editor, the same workflow editor every other program uses.
A Batch bound directly to a datasource runs its before_record / after_record steps once per matching row, the iterative form of the unit.