Welcome to our Spring 2021 Release Preview!
NOTE: The release notes are subject to change. We will update this article to reflect any updates to the release.
If you follow the Release Notes section and received an email update, please note that you may not see the images in the email; please click through to the article to view any images.
We'll be going over new features, updates, and improvements to Reflektive below. These features will be available to test on your Demo Accounts starting April 8th, 2021.
Below is a table of contents of all topics related to our Spring 2021 Release. Click any of the links below to jump directly to that topic for more information.
> General Availability
People Intelligence:
Product Update
Customers can now choose to hide the standard Gender field across all reports available in classic PI.
Who does this affect?
This feature can be enabled for any Reflektive customer (upon request).
Why the update?
Some customers may choose to hide Gender due to privacy reasons, because they do not collect that information in their source HR systems, or they choose not to import that data into Reflektive. If flag is enabled, the "Gender" field is hidden from all PI drop-down choices in Add/Edit Columns, Filters and Group By searches
Product Update
Customers may choose to hide the email button in class PI. When the flag is ON, the email icon will be disabled (but still displayed). User can hover icon where the following tooltip message is displayed "Email sharing has been disabled for this report"
Note: We are not handling scheduled email (cancelling scheduled email) here as users can always open the report and remove the schedule when toggled off.
Who does this affect?
This feature can be enabled for any Reflektive customer (upon request).
Why the update?
Customers may want to halt the emailing of reports.
Product Update
Customers can choose to hide the “Create Action Plan” link that appears on some Survey reports (Favorability reports) in classic PI.
Who does this affect?
This feature can be enabled for any Reflektive customer (upon request).
Why the update?
Customers who wish to restrict goal creation from within Survey reporting may choose to enable this flag. Some customers may not wish to show this option as it may be confusing if they use different processes (e.g., outside of Reflektive) to create and manage action plans.
Foundations and Permissions:
Product Update
To prevent inadvertent updates to employee preferred names in the UI the edit access of name on Profile page can be disabled.
Who does this affect?
This feature can be enabled for any Reflektive customer (upon request).
Why the update?
Customers may choose to lock down employee profile updates in the UI to prevent the user from editing their preferred name via the Profile page.
Product Update
Display additional employee details in user search results including Department, Location and Email. These fields will augment the Name and Job Title.
Note: All three additional fields will be included with this feature enabled -- there is no fine-grained configurability at this time.
Who does this affect?
This feature can be enabled for any Reflektive customer (upon request).
Why the update?
Larger organizations in particular, may have duplicate user names, displaying additional employee details will allow the user to further differentiate search results.
Reviews:
Product Update
Admins may choose to re-add declined peer reviews.
Who does this affect?
This feature will be enabled for all Reflektive customers as default.
Why the update?
This update improves the usability of Reviews. Admins may now re-select a peer that accidentally declined a peer review in the review tracker for an employee. This action will re-trigger an email to the peer reviewer notifying them that they've been selected as a peer reviewer for employee when re-added to cycle from review tracker.
Goals:
Product Update
Customers who are using Goals module and wish to see full reporting hierarchy in Goals reports (both direct and indirect hierarchies) can now show secondary reports and their full hierarchy on Goals reports on PI.
- Full direct reporting hierarchy (ie, all Indirect Reports)
- All Secondary (direct) Reports (ie, all users that the user is a secondary manager for)
- Full indirect reports for user’s secondary direct reports
Currently, only Direct Reports are available in reporting.
Who does this affect?
This feature can be enabled for any Reflektive customer (upon request).
Why the update?
To enable managers with full visibility of goals within their full reporting hierarchy- important in large organizations where there may be multiple levels of hierarchy.
Product Update
With this new feature, customers using the Goals module with large teams can choose to hide all member names and avatars at the top of the team goals page. A count of the number of members will be shown instead. If the total team member count is <100 then the user can open to see the members. When the total member count is >100 the user is unable to open the modal.
Who does this affect?
This feature can be enabled for any Reflektive customer (upon request).
Why the update?
Improved appearance of the team goals page (otherwise, large teams are not displayed cleanly).
Product Update
Customers can now set a goal title limit to less than or equal to 2000 characters. The limit to the length of the goal title field will improve reporting and goals data exports. It will not have any impact on customers unless there are existing goal titles over this limit and if the user updates these goals it will throw an error letting them know that the goal is more than 2000 characters.
Who does this affect?
This feature will be enabled for all Reflektive customers as default.
Why the update?
The limit to the length of the goal title field will improve reporting and goals data exports.
Product Update
Customers may now configure the Goals Module to hide the 'switch' button in the Edit Alignment modal. Some customers may choose to disable the ‘switching’ feature as part of aligning goals if their methodology is that goals are only ever aligned upwards. This can remove some confusion.
Who does this affect?
This feature can be enabled for any Reflektive customer (upon request).
Why the update?
If the goal process is to only align goals upward, then removing the 'switch' button will remove confusion for the process
Product Update
For an organization which is exclusively using private goals, direct reports can never view their manager’s (private) goals. Customers can now choose by default to hide the manager's name in the left side panel in goals.
If the user manually adds their manager as a favorite, it is subject to standard visibility rules.
Who does this affect?
This feature can be enabled for any Reflektive customer (upon request).
Why the update?
When private goals are in use Goals customers may opt to use this feature. Hiding the manager's name in the side panel in goals avoids confusion for direct reports as they are not able to view their manager’s private goals.; otherwise, direct report’s manager will appear to have no goals.
Product Update
For an organization which is exclusively using team goals, there is no need to see the individual goals of other employees. This feature will hide the People section in the Goals page. This product update simplifies the UI for non-admin users without direct reports.
Who does this affect?
This feature can be enabled for any Reflektive customer (upon request).
Why the update?
This product update simplifies the UI for non-admin users without direct reports.
Product Update
Goals API enhancements are to enable our customers to pull goals efficiently and have access to more fields. The enhanced Goals API endpoints to allow incremental updates (changes) that have been updated since the last set of goals were pulled. Additionally, this change provides more data about goals attributes and relationships.
Added the following fields to existing Goals API endpoints:
- Cloned ID & Cloned title (to understand which goals have been cascaded and what they are linked to)
- is goal cascaded
- is aligned
- Aligned Owner Type
- Aligned Owner UUID
- Aligned parent ID
- Parent Name
- Goal Owner
- Goal Owner Type
- created_date filter keys: filter[created_date][from] , filter[created_date][to]
-
- created_date filter will be considered only if filter[created_date][from] and filter[created_date][to] are present in a call with proper values.
- values of keys should be in format yyyy-mm-dd '2020-09-04'
- always 'from' should be less than or equal to 'to'
- edited_date filter keys: filter[edited_date][from] , filter[edited_date][:to]
- See also created_date rules above
- edited_date filter will be considered only if filter[edited_date][from] and filter[edited_date][to] are present in a call with proper values.
Who does this affect?
This feature is available for all customers using Goals API who want to pull changes only and/or are looking for these additional fields in the API
See swaggerhub link: https://app.swaggerhub.com/apis/Reflektive/API/1#/goals%20v2/showGoalInfo
Why the update?
Delta/incremental pulls of data is more efficient.
Product Update
New Goals API endpoint that can replace existing multiple APIs to provide customers with goals extracts similar to what is provided in the All Active Goals report from PI. Some additional details:
- API includes deleted Goals
- API supports filter by Goal Type (Objective/Key result) -- default will be Objective
- Max Pagination limit – 1000. Default is 10
Who does this affect?
This feature is available for all customers using Goals API.
See swaggerhub link: https://app.swaggerhub.com/apis/Reflektive/API/1#/goals%20v2/listGoals
Why the update?
More efficient and performant way to pull goals data into an external data warehouse compared to connecting data from multiple API calls.
Feedback and Recognition:
Product Update
The ability to hide Feedback/Recognition Elements functionality is for clients who want to disable the feedback and recognition products but want to continue using the plugin.
Who does this affect?
This feature can be enabled for any Reflektive customer (upon request).
Why the update?
To avoid confusing end users who don’t use the feedback/RTF features
Comments
0 comments
Please sign in to leave a comment.