Upgrade Human Resource Management to version 1.3.0
Replace the module with the supplied v1.3.0 code and run its portable tenant database upgrade without altering unrelated modules or tenant databases.
Exact navigation Admin Area → Setup → Modules → Human Resource Management → Upgrade Database
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 → Setup → Modules → Human Resource Management → Upgrade Database.
- The Administrator / module management access capability or administrator access.
- The correct employee, record, period or authorised evidence.
How to do it
- Confirm the uploaded module directory is named human_resource_management and contains version 1.3.0.
- Open Setup → Modules.
- Locate Human Resource Management; do not uninstall it.
- Use the module’s Upgrade Database action when the platform reports a pending migration.
- Allow migration 120 and then migration 130 to complete for the current tenant.
- Reload the Modules page and confirm version 1.3.0 is active.
- Open the HR Command Centre and verify route, file and database health.
Fields and options
Migration 120Runs the idempotent installer for automated rota tables and settings.
Migration 130Runs the idempotent installer for employee-record data, approvals, sync logs and document versions.
Tenant scopeThe current tenant database only; other tenant databases are not changed by the migration class.
What the module checks
- Do not use uninstall as an upgrade method because uninstall is a destructive lifecycle action.
- The installer is designed to be idempotent and may safely reconcile missing columns/tables for the current tenant.
- The module requires the host module migration runner to execute versions 120 and 130 in order.
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 platform says no migration exists, verify both migrations/120_version_120.php and migrations/130_version_130.php are present and the module version is 1.3.0.
- If a health card reports a missing table, use the module-owned repair/upgrade action only; do not edit unrelated core tables.
- If the menu remains old, clear application caches and confirm the uploaded module replaced the correct directory.
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: human resource management version 1 3 0