Resolve an employee change-request hash conflict
Handle a pending approval whose source employee record changed after the request was submitted.
Exact navigation Admin Area → Human Resources → Employee Record Centre → Select employee → Approval Queue
Code-backed scope These instructions follow Human Resource Management v1.3.0. Use only controls visible to your permission level and confirm the saved record or audit entry after every action.
What you need before you start
- Access to Admin Area → Human Resources → Employee Record Centre → Select employee → Approval Queue.
- The Human Resource Management: Approve capability or administrator access.
- The correct employee, record, period or authorised evidence.
How to do it
- Do not approve the outdated request.
- Review the current record and the pending request’s changed fields.
- Reject the outdated request with a conflict explanation.
- Open Current Record and submit a fresh amendment against the current version.
- Approve the new request after evidence review.
What the module checks
- Approval compares the stored before_hash with the current authoritative payload hash.
- A mismatch prevents applying stale protected values.
What happens next
The module saves the permitted change and records the resulting status, version, delivery or synchronisation evidence. Reopen the relevant register and verify it.
Troubleshooting
- If the control is missing, confirm the required HRM permission and module version 1.3.0.
- If saving fails, correct the exact field or state named in the validation message.
- If an email/automation is missing, review the module delivery/audit log and host cron/mail settings.
HR data safety Restrict identity, right-to-work, payroll, bank, health, disciplinary and document information to authorised staff. Do not place protected values in free-text notes, email recipients or screenshots.
Browse connected topics: employee record approvals