foundU to enableHR one-way integration
An integration connector has been built on iHUB to sync foundU’s approved employee’s data with basic and mandatory HR information to create an employee in enableHR as a part of joint customers onboarding.
1-way connector that will send data from foundU to enableHR
Newly onboarded employee in foundU with details (Personal and basic employment details) are created in enableHR
This connector only sync’s data for approved employee records from foundU
Terminations (Finish Date and Termination Reason in foundU) are not added/updated through this connector
foundU's approved employees who are not available in enableHR will now be automatically created once the sync runs:
Through foundU integration, all approved employees onboarded in foundU will now also be created in enableHR with basic and mandatory HR details.
-
New employee is created only when there exists no matching employee during comparison between both systems. It is compared as below:
ID as per the ID map table (if exists on both systems)
Match by work e-mail (1 and only 1 employee should have the e-mail address), error if multiple matches found.
-
If no e-mail can be found, alternate match strategies (but matched record e-mail should be blank)
Combination of First, last name and Date of Birth (if exists on both systems)
Personal details during the sync includes Address, email, Phone number, title, first name, last name, preferred name, gender, date of birth, emergency contact details
Employment details during the sync includes Commencement date, Position title and Employment type
foundU's approved employees who are already available in enableHR will now be automatically updated once the following sync runs:
Matching employee should exist in enableHR to make any updates on an employee record. If not matching found, a new employee will get created with the available information in foundU
Employee Personal details such as Address, email, Phone number, title, first name, last name, preferred name, gender, date of birth, emergency contact details changes are updated in enableHR with the new information
Employment details such as Commencement date, position title and employment type are updated in enableHR with the new information
Bugs
Reset MFA
A fix is made such that the 'Reset MFA' button is visible when the admin is in edit mode on the user details screen.
Emergency Contact Report
A fix is made to display both work email and home email under the correct column i.e. worker email work and worker email home respectively in the Emergency Contacts Report when they are entered correctly in the employee’s profile.
Enhancements
enableHR username Validations
We’ve added stronger validation rules for creating and updating usernames across all account types (B2C and non-B2C).
-
Email usernames
Must follow the format username@domain
Allowed characters before the “@”: letters, numbers, periods (.), dashes (-), plus + and underscores (_)
The domain must be a valid DNS domain name
Invalid email formats will be rejected with the error:
“Invalid email format. Please use a valid email address (e.g., user@domain.com).”
-
Non-email usernames
Must be 3–64 characters long
Must start with a letter or number
Allowed characters: letters, numbers, periods (.), dashes (-), and underscores (_)
No spaces allowed
Invalid usernames will be rejected with the error:
“Usernames must be 3 to 64 characters, start with a letter or number, and only include letters, numbers, periods, dashes, or underscores.”
-
User updates
The same validation rules apply when editing existing users, not just when creating new ones.
Usernames with spaces or invalid formats cannot be saved.
All changes are validated to ensure correct information is stored in the database.
User data sync with Azure B2C
New Accounts Automatically Enable Azure Authentication
When an Account and User are created through the MPAQ Importer, they are now automatically marked as “Azure Authentication Enabled.”
Updates Sync to Azure B2C
If a user’s First Name, Last Name, or Contact Email is updated through the importer, those changes are now automatically updated in Azure B2C as well.
This ensures the application and Azure B2C always have the same user information.
Error Notifications
-
When there’s an issue during account or user creation or update, the system now includes detailed error messages in the email notification.
Error 002-201: Shown for issues during Create.
-
Error 002-202: Shown for issues during Update.
User update page changes and sync with B2C
The account registration process has been updated to improve the user experience and ensure accurate data synchronisation with Azure B2C.
In the registration flow, Step 3 is now labeled as “Confirm your user details.” The fields Username, First Name, Surname, and Email are now mandatory, and users will see clear error messages if any required fields are left blank or if invalid information is entered.
When users update their Username, Email, First Name, or Surname, these changes are automatically synchronised with Azure B2C to keep user data consistent. If no updates are made, no changes are sent to Azure B2C or enableHR / CitationHR.
WHS Date of Incident
Date of Incident field now does not give an error when admin is trying to edit and save the incident report created via eSS by the employees.