SAP Knowledge Base Article - Public

3340377 - Adoption of General Display Name in Recruiting

Symptom

Enabling the adoption of General display name

Environment

SAP SuccessFactors Recruiting Management

Resolution

Pre-Requisites

  1. Go to Admin Center  Company System and Logo Settings.
  2. Select the Enable adoption of General Display Name option.
  3. Save your changes.

Enabling General Display Name in SAP SuccessFactors results in the following for Recruiting:

  • Recruiting users — which can include administrators, recruiters, hiring managers, and internal candidates — see their chosen names in all interactions where a legal or formal name isn’t required.
  • Administrators, HR business partners, and any other users with access to a user's legal name can access it when needed.

General Display name isn’t adopted on the following User Interfaces:

  • Shared pool with users: Although you can search for people by their General Display Name when adding them to the Shared list, the General Display Name isn't supported in the Search for First Name in Shared List and Search for Last Name in Shared List fields when looking for those who are already on the Shared list.

  • Adding a candidate to an email campaign: You can only perform an internal candidate search of manually added recipients by their legal names. If General Display Name is enabled, however, the search returns their display names.
  • Message Center: The Search field in the Message Center doesn't support General Display Name.
  • SFAPI and OData APIs response only expose Legal Name.
  • Table and Story reports for Recruiting.
  • The Manage Templates page in Admin Center for Job Requisitions, Job Applications, Candidate Profile, and Offer Detail pages, and adhoc reports don’t adopt General Display Name.
Note
  • In the Job Requisition Change History (Job Requisition Field Audit), the records created for the change history before you enabled the Enable Adoption of general display name option will still display the legal name. Only the records created after enabling the Enable Adoption of general display name option adopts the display name.
  • In talent pools, you can search for people by their General Display Name when adding them to the Shared list, but the General Display Name isn't supported in the Search for First Name in Shared List and Search for Last Name in Shared List fields when looking for those who are already on the Shared list.
  • The email templates created before enabling the Enable adoption of General Display Name option, the CC, and BCC fields won’t resolve the display name for the By Employee name option. So, you need to resave the email template to view the display name.
  • When creating new email campaigns, the Search First Name and Search Last Name fields in the Manually Added Recipients dialog for candidates don't support General Display Name.
  • The from and reply-tofields in an email trigger always adopt the display name from the value configured in the Admin Center, Manage Recruiting Setting. If no values are configured in the Admin Center, Manage Recruiting Settings, the from and reply-to fields in an email trigger adopt the value from V4admin.
  • When the display name is enabled, it doesn’t reflect in Recruiting Posting immediately. Instead, the changes are reflected only after user synchronization updates.
  • Recruiting Posting doesn’t send a display name to the job board while sending the job posting data.
  • Contact information on the Field Completion Rulespage in Recruiting Posting doesn’t support the General Display Name.

Keywords

KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , How To

Product

SAP SuccessFactors Recruiting 2305