Summary¶

The Hire2Retire Phase 4-2 release adds improvements to the existing functionality and new enhancements to the product features based on the market needs and the customer feedback. One of the significant enhancements provides a wide range of options to apply dynamic rule-based group memberships to security groups and distribution lists. This enhancement will allow the user to either choose implicit group whitelist limiting Hire2Retire to the only manipulate groups known to it or choose an explicit whitelist along with other options. The user will now have more options to exclude groups from being updated during the automation and we should be able to accommodate various possible combinations that we have encountered and heard from our customers and prospects.

We have also updated the Get help section on the product, which will allow users to easily reach out to the RoboMQ support team for technical support more effectively.

There are multiple other enhancements to add features to existing capabilities or improve the user experience (UX).

Dynamic Group Membership Whitelist Redesign¶

This is a Feature Enhancement in Hire2Retire Platform.

Hire2Retire now provides more options to whitelist dynamic group memberships with an intent to address all possible scenarios and practices being followed. With the new update, customers can select one of the following options that fit for their business needs.

Whitelist groups options for update operation:

Retain all groups NOT defined in group mapping automation
Retain ALL existing groups
Do not retain any existing groups
Retain below selected groups

Retain all groups NOT defined in group mapping automation¶

When updating an employee data, hire2retire workflow will only update or remove the security groups or distribution groups you defined in the “Security Group Assignment” or “Distribution List Assignment” steps. Other groups or memberships that you did not define in those two steps will not be removed from this employee.

Retain ALL existing groups¶

When updating an employee data, all employee’s existing memberships will be retained. And new groups or memberships will be added based on the rules you defined in the “Security Group Assignment” or “Distribution List Assignment” steps.

Do not retain any existing groups¶

This is a complete sync of employee data between HR system and AD system. When updating an employee data, employee’s memberships will be updated completely based on the rules defined in the “Security Group Assignment” or “Distribution List Assignment” step. New memberships will be added based on the new criteria, and existing memberships will be removed if the groups don’t exist in the rule set or do not meet the criteria.

Retain below selected groups¶

You can select a list of groups to retain when updating an employee data. The groups do not belong to this list will be reviewed and updated by Hire2Retire workflow based on the defined rule set defined in the “Security Group Assignment” or “Distribution List Assignment” steps.

The existing “Select all” option is removed from the multi-selection dropdown since “select all” was only applicable to the groups fetched and presented on the view and not to all the groups existing in AD. This was causing confusion. This removal is backward compatible since it can be replaced by the new options mentioned above.

If user has selected certain security groups to retain in the existing workflow, then the 4th option “Retain below selected groups” will be pre-selected in the new view post release 4.2. If user did not select any security groups to exclude, then the 3rd option “Do not retain any previous groups” will be chosen in the new view post release 4.2. Since workflow configurations remain the same as before therefore there is no need to redeploy the existing workflows.

Improvement on “Get Help” form¶

This is a Feature Enhancement in Hire2Retire Platform.

The Get Help section has been upgraded, user will be able to reach the RoboMQ support team through the “Get Help” section and provide detailed information about the issue including the relevant screenshots.

The Get Help section will collect the following information：

username
Flow id if exists
Summary of the issue
Detailed information about the issue
Relevant business impact:
1. Level 1: Platform unusable or major impact on business function
2. Level 2: Serious impact on business function or degraded application performance
3. Level 3: Limited isolated impact on business function or application performance
4. Level 4: Questions, or minor impact on business function or application performance
5. Level 5: Suggestions or ideas for enhancements of the application functionality
6. Relevant screenshots