Inspect job progress and account for its changes
Purpose
Administrators inspect job outcomes and connect a record’s history to the work that changed it.
How It Works
An administrator uses the job list to locate recent work and narrow it by the available filters. Record-kind visibility determines which submissions the service can reveal. CRM routes additionally require bulk access, so their ordinary callers already meet that wider visibility condition. Job detail exposes progress and ordered outcome pages. Staff use refusals to locate input that needs correction. Delivered work also retains source and file context. Record history provides a separate route back to the responsible job and submitter. The approved retention period and large-result tools describe work still to implement. Their absence must remain visible when Product considers approval.
Relationships
- Batch processing creates the receipts and refusals inspected here.
- Rollback planning uses those receipts to determine restoration candidates.