Validation & releases
Review changes
before they go live.
Give the people who know the records a way to check the results. Keep findings connected to the record, field and version being reviewed.
Discuss your review processThe mapping handles RB. A reviewer spots R/B in older records.
The issue is fixed and checked again before the release is approved.
Review with the people who use the records
Check the result.
Keep the finding specific.
Use representative records and the agreed acceptance criteria. The customer brings knowledge of the records, and the implementation team investigates and resolves the findings.
- 01
Compare with the source
Check the fields, relationships, report layout and supporting files that matter to the task.
- 02
Identify the issue
Point to the record, field and version so the team can reproduce what the reviewer found.
- 03
Recheck the result
Review the revision before approval and publication. Assign the reviewers and release responsibilities.
Choose the right change workflow
What are you changing?
A correction, a mapping change and a new report layout can have different effects. Make that scope clear to the people reviewing the work.
The correction applied to an individual record.
The original value, the correction and its reason.
How the report reads or transforms the source.
Affected records, including older or unusual values.
How the information is presented to staff.
Fields, repeating sections, relationships and output.
Corrections & record history
Correct a value.
Keep its history.
Authorized staff can enter a corrected value and explain why it changed. The record shows the value in use while keeping its source and correction history available.
Record corrections follow their configured permissions and review requirements. They are separate from publishing a version of a report or query.
What about record removal?
Removal is a separate responsibility. Agree on authorization, retention, review and any recovery provisions before enabling it. The scope must account for related information and backups. Removing a record from view does not mean copies elsewhere have been erased.
This example is laid out for a wider screen.
After launch
The review process continues after launch.
A later question may reveal a value to correct or a report to improve. Identify what the change affects, review the result and keep its history. New sources, report types and integration work receive their own scope.
Subscription and supportDefine a useful review
Which records would your team check first?
A few representative examples set the coverage, the priorities and who should review the archive.