We love to hear your feedback. Your suggestions and ideas are important to us. Our feedback forum is a great place to post your ideas and vote on others. Please share your detailed use case and how the proposed enhancements can increase value to your business. We do read all of your posts, but may not be able to respond to all comments.
More information on the status of submitted ideas can be found here
If a preferred name has been populated in a User profile, do not reflect their Legal (First) name, the system should use the Preferred Name & Legal Last Name to refer to the User in search fields, reports and Teams. The option to allow a preferred name, but then the system not actually masking their legal name is counter productive to providing an inclusive culture.
|
What business value are you trying to achieve?
Diversity and Inclusion requires that we refer to employees by their preferred name where they have provided it. |
FYI - solution already exists
Phase 1 per:
https://knowledgeportal.pageuppeople.com/hc/en-gb/articles/20368880878489-Displaying-preferred-names-consistently-throughout-Admin-Phase-1-Deployed-to-Live-2-Aug-2023-
Phase 2 per:
https://knowledgeportal.pageuppeople.com/hc/en-gb/articles/21542374396953-Displaying-preferred-names-consistently-throughout-Admin-Phase-2-Deployed-to-Live-4-Oct-2023
preferred names should be in general communication templates but I would have thought formal contracts would use actual name
It can be devastating to individuals that the system and communications have their "dead name" showing. I agree with Mark, this is necessary in the merge fields for communications as well.
Agree. Where a preferred name exists, it should be displayed to the user across the system.
some logic behind the merge fields would be required e.g. Preferred first name merge field selected, if preferred name is present then use that merge field otherwise drop back to first name merge field