Summary¶

The Hire2Retire Phase 4.4 release adds new features and significant enhancements to the product based on market needs and customer feedback.
Hire2Retire now supports the iCIMS applicant tracking or recruitment platform, allowing customers to integrate with iCIMS and sync employee lifecycle data to AD at the “hired” stage before the employee record is created in HCM. This way an employee’s AD identity will be created upon hiring and then updated to reflect requisite roles and privileges upon getting a full HR profile and role assignment from HCM. RoboMQ has also upgraded the process of updating OU. When updating an employee profile, Hire2Retire will check the defined OU mapping rules and decide if an employee needs to be moved to any new OU subsequent to change of role, department, location or other determining attributes.
In addition to the above, there are other minor improvements to existing capabilities and/or bug fixes listed at the bottom of this note.

Support iCIMS as a new recruitment system¶

This is a New Feature in the Hire2Retire Platform.

Hire2Retire now supports a new Applicant Tracking System (ATS), iCIMS, for pre-boarding. Users can now use both iCIMS and HR (Human Resources) systems and sync profiles to AD systems using the Hire2Retire platform. Hire2Retire can receive files from iCIMS upon hiring to perform pre-boarding and later from HRIS when the employee profile is created in HR system. An employee’s AD identity will be created upon hiring (or pre-boarding)I and then subsequently updated to reflect the requisite roles and privileges upon getting a full HR profile on HRIS. This enhancement addresses a common ask from the customers and will provide fully automated integration from hiring or pre-boarding without the need to change processes on the HR side. At runtime, iCIMS will send file extracts to the RoboMQ-hosted SFTP server, and the Hire2Retire flow will process employee profiles based on the pre-defined rules set on the Hire2Retire platform.

Organization Unit (OU) will not be updated for an employee if none of the OU mapping rules match¶

This is a feature enhancement in Hire2Retire Platform.

When updating an employee profile, Hire2Retire will now check the defined Organization Unit (OU) mapping rules and decide if an employee needs to be moved to a new OU. If there is no OU mapping rules that match then instead of moving the user to the default OU, Hire2Retire will now keep the user in their previous or pre-existing OU. If you want to move the user to the new OU, you can add a new OU mapping rule and rerun the employee profile.

There is no impact on users’ existing flow functions. Users need to redeploy their existing workflows to apply this new feature.

Ability to update Primary Email or SMTP address¶

This is a feature update in Hire2Retire Platform.

Users can update their primary email and primary SMTP address by unchecking the option “Primary Email or SMTP address” from the “Exclude Employee Attributes” of the target lifecycle business. At runtime, if the target email value is changed then the Hire2Retire flow will update the email and primary SMTP proxy address. The previous primary SMTP proxy address will be stored as an alias in the proxy address list. For example:

At design time, a user unchecks the “Primary Email or SMTP address” option from “Exclude Employee Attributes” of target lifecycle business. UPN suffix is defined as rbmq.com
At run time, process an existing employee “anande.rs@robomq.com” when his new email address is derived as anande.rs@rbmq.com
expected result:
1. The email attribute will be updated to anande.rs@rbmq.com
2. The primary SMTP address change to anande.rs@rbmq.com
3. A new smtp address will be added to the alias list: anande.rs@robomq.com

There is no impact on users’ existing flow functions.

Upgrade AD and Azure AD “Exclude Employee Attributes” list to support all attributes that are available for data mapping¶

This is a feature enhancement in Hire2Retire Platform.

All the AD and Azure AD attributes that are available for data mapping will now also be available in the “exclude employee attribute” list. Users can select them and prevent the attributes from being overwritten while updating employee profiles.

There is no impact on users’ existing flow functions.