Create and estimate a dated billing run

Purpose

Controllers choose a template and calendar day, inspect an estimate and retain a dated snapshot for later work.

How It Works

Controllers choose a template and calendar day, inspect an estimate and retain a dated snapshot for later work. Creating a run requires a workspace template and a valid calendar reference date, with missing templates and malformed dates refused before any run is written. A run retains the template's identity, version and copied action options, preserving its work when the template changes or becomes inactive. Run creation resolves nested relative dates against the reference day, including the legacy relative-date form, and retains absolute dates in the resulting options. Default run names combine the reference date and template name; a supplied nonblank name is trimmed, and the business unit remains the template's. Manual runs use their requester's identity for population reads and do not accept a different execution identity in the request. A template containing an unavailable action cannot create a run, even if it predates that action's withdrawal. Manual creation accepts inactive templates although recurring occurrences refuse them. Saved-query estimates use the requester's access, return per-action counts capped at ten thousand with a cap indicator, and create no run, item or job. Estimation preserves Platform's explanation for query refusals and returns a referenced unavailability message for an invalid Platform response. Run lists use newest-first cursor paging, default to twenty-five and cap at one hundred, support status, template, recurrence, creator, date and name filters, and reject unknown statuses without shifting already-read pages. The product should align installment estimates with the template's business unit.

Relationships

Template configuration supplies the run’s copied instructions. Preparation then turns the saved run into a reviewable population.