Human Resource Management Version 1 3 0 · How-to guide

Troubleshoot the HRM v1.3.0 upgrade

Diagnose missing migrations, stale menus, missing tables or incomplete backfill without changing unrelated application files.

Audience: HR administrators and authorised managersPermission: Human Resource Management: ViewModule v1.3.0
Exact navigation Admin Area → Setup → Modules → Human Resource Management
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.
  • The Human Resource Management: View capability or administrator access.
  • The correct employee, record, period or authorised evidence.

How to do it

  1. Confirm the module directory and config.php both report version 1.3.0.
  2. Confirm migration files 120_version_120.php and 130_version_130.php exist.
  3. Run Upgrade Database once from the affected tenant.
  4. Open HR Command Centre and identify the exact missing route, file or table.
  5. Use only the matching module-owned repair/installer action if required.
  6. Re-run the affected test and review application logs for the exact exception.

What the module checks

  • Do not uninstall the module to fix an upgrade.
  • Do not manually create unrelated core tables.
  • Production repair endpoints require the module maintenance unlock file where implemented.

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.