Enhancements
Improved foundU to enableHR Employee Conversion
We enhanced the integration to ensure a smooth transition from candidate to employee.
Key updates
When syncing approved employees, the system now checks for an existing candidate in enableHR first.
If found, the candidate is automatically converted to an employee, with clear messaging in the logs.
The system now automatically updates internal mappings after conversion.
-
New safeguards prevent incorrect linking when multiple candidate matches are detected.
Improved MFA Disable and Reset Controls
We’ve enhanced the MFA management options to better support users who cannot access their existing MFA method.
What’s new
Disable MFA now removes all MFA methods and allows the user to sign in without MFA on their next login. If re-enabled, the user will be guided through MFA setup again.
Reset MFA clears existing MFA methods but keeps MFA turned on, prompting users to re-register MFA at their next login.
-
Updated tooltips and messages provide clearer explanations of when to use Disable vs Reset.
Duplicate Email Validation
To reduce unnecessary blocks during user creation or updates, we refined how duplicate emails are detected.
Inactive users without an Azure ID are now ignored in duplicate-email checks.
Active users or any user with an Azure ID will still be treated as a valid duplicate.
-
This applies across all user creation and update processes, including ESS, checklists, MPAQ imports, and record linking.
Configurable Error Threshold for iHub Jobs
We increased the error threshold for iHub connector jobs to improve processing efficiency.
What’s changed
Jobs now stop only after reaching 50 errors, instead of 15.
The threshold can be configured to suit business needs.
-
More data can now be processed before a job stops.
iHUB - Detailed Reports for Failed Jobs
We improved visibility into job failures by ensuring Detail Reports are always provided. Even when a job stops due to too many errors, a detailed report is now generated so users can clearly see which records failed and why.
Better Sync Handling for Terminated Employees (iPayroll & CloudPayroll)
We corrected inconsistencies in how terminated employees sync between systems.
Improvements
Syncing continues until both systems mark the employee as terminated and the payroll finish date has passed.
Data updates continue up to and including the finish date.
Clear warnings now appear when termination statuses differ between systems.
Normal syncing continues unchanged for active employees.
Fixes
WHS Incident Date Validation Fix
We resolved an issue where managers received a date-format error when editing an incident created via ESS.
The Date of Incident field no longer triggers an error when the record is edited without changing the date.