Symptom
While sending emails (and/or SMS), the email template follows the locale of the recipient user, but some tokens configured in the template do not resolve in the recipient's locale if it contains localized data.
The same applies to other standard & custom tokens that can take localized values (such as Picklist fields).
- Current behavior: The token values which can have localized data are always resolved in sender's locale.
- Expected behavior: The token values which can have localized data should resolve in recipient's locale for each primary recipient.
Note that the current behavior is observed for all types of emails sent: Recruiting Email trigger emails, Contact Candidate emails, Status emails and so forth.
Example cases:
- When the system sends Interview Confirmation to Interviewers, the Interview Type (token: INTERVIEW_SCHEDULING_INTERVIEW_TYPE) is resolved in the candidate's locale instead of the interviewer's locale.
- FO/GO tokens do not resolve values based on the email template language. The token locales are currently being based on the user's system language.
Read more...
Environment
SAP SuccessFactors Recruiting Management
Product
Keywords
RCM-43886, interview scheduling, email, token, recipient locale, interview type, interview date, interview duration, INTERVIEW_SCHEDULING_INTERVIEW_TYPE, INTERVIEW_SCHEDULING_INTERVIEW_DATE, INTERVIEW_SCHEDULING_INTERVIEW_LENGTH, FO/GO, DEPARTMENT_OBJ, DIVISION_OBJ, offer letter, INC2211749 , KBA , LOD-SF-RCM-EML , Recruiting Emails and Notifications , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.