Conversations, Enhanced Objectives, Feedback | Troubleshooting

A leaver's objective has a review date and action

The system terminated a direct report that had an objective with a review date, but still shows the action to review.

To resolve, remove the review date. Alternatively, you can add the Alerts related list to the Team Member page layout, and delete the Alert record for the manager.

External feedback requests aren’t being sent

If the system isn't sending External feedback, make sure you’ve defined an organization-wide email address. You then need to select it for the Fairsail Digest From Address field on the HCM package Configure page.

For more information, see Organization wide email addresses and Sage People Actions Digest.

"You do not have sufficient privileges to access the controller: CommonRemoting"

A team member sees an error message: "spperfmgmt__performance: system.security.NoAccessException: You do not have sufficient privileges to access the controller: CommonRemoting".

Review the team member's permission set assignment. Access to Conversations, Enhanced Objectives, and Feedback requires the Sage People Platform Team Member - Performance Management permission set.

"Another user is also editing this Objective" error in WX

Users attempting to complete an enhanced objective by selecting End Objective are getting an error. It reads "Another user is also editing this Objective" error despite nobody else editing the objective.

This error occurs when custom fields use the Roll-up Summary data type. It happens specifically if the custom field aggregates information related to objective reviews. For example, the roll-up summary field aggregates the created dates of the objective review comments. A manager goes to a team member's objective, adds a review comment, and then attempts to end the objective, and gets the error. This is because there’s now a mismatch between the objective on the manager's screen in WX and what they saved in the system. As a workaround, the manager can refresh their screen, which saves the record and clears the error. To prevent triggering the error in this scenario, avoid using roll-up summary fields.