Reflektive Fall 2022 Release Notes

Blank pages have been removed from the PDF report design. 

Who does this affect?

This enhancement is already available and is of use to Reviews customers.  

Why the update?

This enhancement reduces the report size, minimizes wasted space, and makes the report more visually appealing and easier to understand. 

A collection of improvements have been made to the review builder in step 3 (question creation) and step 4 (participant selection):

• Targeting has ben added based on custom attributes and teams for steps 3 and 4. 
• Participant targeting rules and exclusion of employee hire date are displayed in active cycles and can be updated in active cycles. 
• Enhanced validations for table view in step 4 (such as the ability to hide fields and to view all employee custom attributes). 
• After the Autumn release, we plan to add the ability to download Questions CSV files and Participants CSV files in draft and active cycles, and extend the enhanced validations for table view in step 4 to include sort and filter capabilities. Planned for fourth quarter 2022. 

Customers will be able to use the new targeting workflow for new cycles created after this feature is enabled. Cycles created before this feature was enabled will continue to be on the existing targeting workflow.

Who does this affect?

This enhancement will be available by request and is of interest to Reviews customers. 

Why the update?

To improve the limited targeting criteria in the review builder for step 3 (question creation) and step 4 (participant selection). 

A "No feedback results” message now appears when feed filters yield no results. 

Who does this affect?

This enhancement is already available and is of use to Feedback 2021 customers. 

Why the update?

This minor UX enhancement improves the user experience when using Feedback 2021.

You can now use module access control for the Rewards module, allowing controlled exposure of the rewards module to users based on user targeting rules. This defaults to "All Employees" when turned on. 

Who does this affect?

This will be available by request and is of use to Rewards customers. 

Why the update?

This enhancement allows administrators to restrict rewards to users in certain locations, for example, and also have the flexibility to block any given user from using rewards. 

We have enabled role based access control (RBAC) of who should be notified when users redeem rewards. 

Who does this affect?

This is already available and is of use to Rewards customers. 

Why the update?

This enhancement allows the right people (for example, admins or managers) to be aware of rewards redemptions. 

This enhancement adds widgets to the user's home page detailing points-to-give and points-to-redeem balances. 

Who does this affect?

This will be available by request and is of use to Rewards customers. 

Why the update?

This enhancement exposes information and functions that were previously only available in the Recognition alternate tab. 

There is a new “Is a Manager” user targeting rule type that can be used with “Equals True”. 

Who does this affect?

This is available by default and is of interest to customer administrators using teams, module access, or role-based access control where user targeting is employed. 

Why the update?

 This enhancement allows you to target employees who are managers, which is useful when you are configuring access to People Intelligence, for example. 

Company switches to grant managers and master admins access to PI have been migrated from internal access to Module Access and Roles.

Who does this affect?

This is already available and is of interest to customers using People Intelligence and looking to enable RBAC. 

Why the update?

So that no additional configuration is necessary to preserve existing access when RBAC is toggled on. 

 "Company Admins" has been relabeled to "Master Admins." We also added sorting and pagination to the Master Admin list.

Who does this affect?

This is already available and is of interest to customer administrators using role based access controls. 

Why the update?

 Master Admin is a better term for the role and more commonly used, and sorting and pagination increases the usability of the Master Admins list. 

A clock face now appears on the Admin Roles page when a data sync is occurring.

Who does this affect?

This is already available and benefits customers using role based access controls. 

Why the update?

So that admins will know that the configured access needs to be processed before it will take effect.

 In this release we have made technical improvements to the Role Based Access Control framework.

Who does this affect?

This is already available and benefits customers using role based access controls. 

Why the update?

This enhancement improves the user experience for managing role-based access controls. 

When configuring targeting rules, customers now have the ability to select “All Teams”. 

Who does this affect?

This is already available and is of use to customer admins that want to target all of their teams. 

Why the update?

To preserve access to all teams without having to manually add teams to targeting rules when new teams are created. 

Reports can currently be shared with individual users or all users belonging to a team. Role-based sharing will allow for sharing reports based on a role that has been configured in the administrator area.

Who does this affect?

This enhancement is already available and is of use to all users with access rights to share Reports and Dashboards.

Why the update?

Teams are generally defined for the purpose of creating shared goals and may not always be an effective way to distribute reports for a specific class of employee (for example, all managers or all HRBPs). Role definitions can be more reflective of a class of user, so sharing based on roles should add efficiency and avoid creating unnecessary teams just to serve the report sharing purpose. 

A new page is available to display the status of the data synchronization process.  

Who does this affect?

This enhancement is already available and is of use to system administrators. 

Why the update?

The reporting database is continually refreshed with the transactional data from the Reflektive application. In cases where system latency or process failures occur, reporting data can appear inaccurate. This page will allow system administrators to confirm the integrity of the currently available data or identify situations where data may not be 100% up to date. 

This feature allows customers to "drill down" more on the sub-groups through expansion of a parent group by using the Summarize By option. 

Who does this affect?

This enhancement is already available and is of use to all users with access rights to share Reports and Dashboards. 

Why the update?

The reporting system provides grouping capabilities to group the data to apply various KPIs to get insights on the data. But prior to this feature there was only one level of grouped data and no sub-group expansion to know the data insights of groups within a parent group.

A new feature is available to pivot tabular data in reports with addition of multiple Key Performance Indicators (KPIs).

Who does this affect?

This enhancement is already available and is of use to all users with access rights to share Reports and Dashboards. 

Why the update?

The reporting functionality previously supported only a single KPI to be added in a pivot table. Multiple customers have requested the ability to pivot on multiple KPIs within the same pivot, and we have added that capability in this release. 

This enhancement improves existing error handling to show more specific errors to the users in case of exceptions rather than one generic message. 

Who does this affect?

This enhancement is already available and is of use to all users with access rights to share Reports and Dashboards. 

Why the update?

New People Intelligence (PI) had only one generic message to ask the user to migrate the report/dashboard to new PI if it did not load. This was not serving the right purpose as not all the errors were migration-specific. Now more categories for various errors (such as permission denials) have been added as part of this improvement. 

This new feature shows a column for Feedback Delivery for a review report. 

Who does this affect?

This enhancement is already available and is of use to all users with access rights to share Reports and Dashboards. 

Why the update?

People Intelligence did not have any specific way of giving the user the ability to report Feedbacks Delivered as part of the review process. A part of this release, new PI will have a new column in Review Reporting called Feedback Delivered, with Yes/No values for the future cycles.