Bug Fixes
Custom fields now display in the correct order on Risk/Incident/Hazard Register reports
We fixed an issue where custom fields appeared out of order on the Risk, Incident, and Hazard Register reports. Custom fields now show exactly in the order you select, appearing after the built-in standard fields.
Only non-standard custom fields are shown (standard fields remain built in), and outputs are consistent across both HTML and CSV.
long account names are handled automatically
Candidate-to-Employee conversions and user provisioning could fail silently if an account name exceeded Azure B2C’s 64-character limit. We now automatically shorten long account names before sending them to Azure B2C.
New and updated users—including eSS users created via checklists and users created through registration links—sync without errors. Existing users continue to sync normally, and users under long account names can be migrated successfully.
Enhancements
Clearer error messages for Username & Contact Email
We’ve improved validation messages so they’re accurate and guide you to the field that needs fixing. Focus now returns to the field with the error.
Invalid Username (email format):
Error: The system responded: <Username> has invalid email format. Please use a valid email address (e.g., user@domain.com).Duplicate Username (email):
Error: The system responded: Sorry, the username <Username> is not available.Invalid Contact Email:
Error: The system responded: The email address <Contact email> isn’t in a valid format. Please enter a valid email (for example, user@domain.com).Duplicate Contact Email:
Error: The system responded: The contact email <Contact email> provided is already in use by another user. Please enter a unique email address.
These updates apply to all clients, whether Azure B2C is enabled or not.
Clear login warning for invalid B2C usernames
Users signing in with an invalid Azure B2C username (for example, using “@” without a valid name) now see a clear explanation and what to do next.
A Continue button lets you keep working while you update your username.
Validation applies to all roles (Superuser, Account Admin, eSS user, Partner user, Salesperson). Unaffected users see no change.
Stronger, standardised password policy (Azure B2C aligned)
New users must now set passwords that meet the Azure B2C STANDARD_POLICY across enableHR.
Mandatory fields: Password and Contact Email are now required (marked with “*”) when creating a user in the Admin screen.
-
Password rules:
At least 8 characters (no max)
Include 3 of 4 types: uppercase, lowercase, numbers, special characters (~!@#$%<>+)
Must not contain your username or any part of your full name
Helpful errors: If a password doesn’t meet the rules, creation is blocked and a clear error explains what to fix (e.g., “Password must contain at least 8 characters”).
-
Where this applies:
Users created in Admin (AAS) or directly in Azure B2C
Admin and eSS users created through enableHR
Password resets (AAS or Azure)
New eSS self-registrations
iHub: automatic re-match when employee IDs change
If an employee’s Person ID changes in CloudPayroll/iPayroll, iHub now attempts an automatic re-match so syncing keeps working.
When re-match succeeds, you’ll see:
“Previously matched employee with sourceId [$sourceId] and targetId [$targetId] was not found. Using re-match, this employee is now mapped to new targetId [$newTargetId].”iHub Report Details now shows the new Target ID so future syncs update the right record.
If no match can be found (for example, Person ID and name and date of birth all changed), you’ll see:
“Previously matched employee… Using re-match, no employee match was found.”
foundU: updates respected when employees move branches
If an employee moves to a non-primary branch in foundU, enableHR now updates their details correctly on the next sync. This works for both manual and scheduled syncs.
iHub: correct scheduled sync timings shown per connector
When creating connector jobs, iHub now displays the accurate scheduled sync timings in the pop-up for each connector, removing confusion about when the next run will occur.