Design pattern
Governed data exchange
Export governed records and validate imported changes before an authorised person confirms them.
Production pattern
Live preview
This static example is rendered from the same package consumed by UJ applications; it does not fetch data from the owning application.
Programmes administration
Data exchange
Export governed records or upload a workbook for validation before any changes are applied.Validated before change
Uploading a workbook creates a review job. It never changes Programme records immediately.
Export
Prepare a governed workbook
Choose the authorised scope and download current Programme records.
Scope: Faculty of Science · XLSX · Published and draft records
Import
Upload and validate changes
Match records, choose one XLSX workbook, then create a validation job.
- UploadCurrent
- ValidateUpcoming
- ConfirmUpcoming
- ResultUpcoming
XLSX only. The workbook will be checked before confirmation is available.
Required| Workbook | Scope | Status | Created |
|---|---|---|---|
| science-programmes.xlsx | Faculty of Science | Review ready | 27 July 2026 |
Guidance
How the pattern works
Owned by Corporate Identity.
Use this pattern when authorised staff need to exchange governed records through a workbook or similarly bounded file contract. Present export and import as separate, full-width tasks. Explain scope, included content, matching strategy and file constraints before the primary action.
An upload must never imply that records changed immediately. Show Upload, Validate, Confirm and Result as an ordered workflow. Validation identifies blocked rows, warnings, unchanged records and proposed changes; a separate authorised confirmation applies an eligible change set.
Use choice cards only when their supporting descriptions help staff distinguish matching strategies. Use the governed file input for explicit format, size and validation feedback. Provide an accessible error summary for server validation, and name the horizontally scrollable review table from its visible caption.
Keep permissions, scope calculation, workbook creation, uploads, malware controls, parsing, matching, validation, idempotency, transactions, audit history and application terminology in the owning application. The design package owns presentation and interaction contracts only.
Composition