See How Hire2Retire Can Drive Success for Your Organization |15th Nov 2024|
What’s New in Hire2Retire Phase 4.5
Phase 4.5 of Hire2Retire is now live, bringing new features, adding new capabilities to existing features, and providing a better overall user experience. These improvements were chosen and implemented based on market needs and feedback from Hire2Retire customers. 
As part of the 4.5 release Hire2Retire now supports future hire and termination events. With this feature users can now specify a specific employee’s start day or last day of work and Hire2Retire will wait to process the requisite employee lifecycle event on that designated date. In addition, users can set up an offset to customize the process further, instructing Hire2Retire to process events a few days before a start date or after a last day of work. This feature provides Hire2Retire users with even more control to tailor the employee lifecycle management process to their exact needs. 
This release also provides support for Paylocity as a compatible HRIS system, adding to Hire2Retire’s lineup of compatible systems for data integration. Based on the pre-defined rules users set in the platform, Hire2Retire will now be able to automatically sync employee profile data between Paylocity and Active Directory (AD) or Azure AD. 
Other Features and Improvements in Hire2Retire Phase 4.5
Hire2Retire now supports an API connection approach for SAP SuccessFactors integration.
An increase to a maximum of 18 characters for initial employee onboarding passwords.
A new collapsed view of the mappings on the Hire2Retire overview page.
To see a list of all product enhancements and bug fixes in this update, read the full phase 4.5 release notes. 
RoboMQ is not affiliated, associated, authorized, endorsed by, or in any way officially connected with any of the HR systems that it provides integration with and are mentioned in this post. All product and company names are the registered trademarks of their original owners. 

Submit a Comment

Your email address will not be published. Required fields are marked *