Submit an accountable change across many records
Purpose
Staff and connected systems submit a single authorized job to make a change across a collection of records.
How It Works
A data administrator selects the records to change and supplies the intended operation. A connected system can submit equivalent work through the API. Rhythm checks the permissions and input shape before recording the job. The saved input gives subsequent processing a stable request to follow. Interactive changes travel with the request; imports and larger changes use uploaded files. A repeated keyed request retrieves the earlier job, while an unkeyed request creates new work. Staff follow the resulting job to review progress and outcomes. The product should preserve this authorization model as additional product areas adopt the engine.
Relationships
- Previewing a change uses the submitted job as its starting point.
- Batch processing consumes the saved input.
- Each product area declares the operations its records support.