Prepare a population for billing review

Purpose

Controllers inspect selected records before execution and preserve their review choices when the population changes.

How It Works

Controllers inspect selected records before execution and preserve their review choices when the population changes. Preparation claims a draft or scheduled run atomically, refresh claims a ready run, and incompatible states return the current and required statuses. Preparation selects with the run user's access and commits each page's review items alongside its cursor, preventing duplicate items after interruption or redelivery. A saved-query refusal ends preparation with Platform's explanation and leaves the unread page unwritten, while transient faults remain retryable. Completing population selection records preparation time, derives candidate counts from review items and makes the run ready. Refresh preserves exclusions, attribution and outcomes, adds new candidates as pending and retains departed candidates as no longer eligible. Ready runs allow one to five hundred exclusions or inclusions per request, leave settled items alone and report requested and changed counts. Review names reflect CRM at preparation time, and unavailable CRM names produce identifier-only review items without failing preparation. Review lists default to twenty-five items and cap at one hundred, with outcome, action, exclusion, name and identifier filters. Reading review items requires run-read permission; preparing, refreshing and changing exclusions require run-create permission. A reviewer can inspect candidates without authority to change them.

Relationships

Run creation supplies the options that preparation reads. The ready population and its review choices become the input to execution.