3760957 - Email Language Not Triggered as Expected When Preferred Language Is Passed from Recruiting to Onboarding

• Email notifications are not triggered in the expected language during the Onboarding process.
• The system defaults to a standard language (for example, English) despite maintaining a preferred language in Recruiting.
• The defaultLocale field does not reflect the expected locale value (for example, fr_FR, de_DE).

SAP SuccessFactors Onboarding

1. Enable Native Preferred Language.
2. In Recruiting, select Native Preferred Language = French for the candidate.
3. Initiate Onboarding and proceed to Review New Hire Data.
4. Submit Review New Hire Data; the candidate receives the IAS activation email in English.

By design, email triggering in IAS depends on the locale value maintained in the User Sys Info table (table_users_sys_info), specifically the defaultLocale field.

For candidates initiated from Recruiting, the defaultLocale is typically set to a default value (for example, en_US) unless it is explicitly updated during the data flow.

In the standard process, the preferred language captured in Recruiting is not directly used to update the defaultLocale. As a result, if no mechanism is in place to derive and pass the appropriate locale value, the defaultLocale remains unchanged.

Consequently, IAS uses the default locale value for email notifications, leading to emails being triggered in the default language instead of the expected preferred language.

To ensure email notifications are triggered in the expected language, it is required to update the defaultLocale field with the correct locale value during the data flow and ensure it is correctly consumed by downstream processes.

Please verify and ensure the following:

1. A valid locale value (for example, en_US, fr_FR) is derived based on the preferred language captured during the Recruiting process.
2. The derived locale value is stored in a field that is used to update the defaultLocale.
3. The value is successfully propagated through the process and synchronized via HRIS Sync to the User Sys Info table (table_users_sys_info).
4. The defaultLocale field reflects the expected locale value after synchronization.
5. Any IAS/IPS transformations are correctly configured to:
   • Consume the defaultLocale (or relevant mapped field), and
   • Apply appropriate filtering/logic to determine the email language.
6. Ensure that corresponding language templates are maintained in IAS for the expected locale values.
7. Validate the behavior by reprocessing a test candidate and confirming that:
   • The defaultLocale is correctly updated, and
   • Email notifications are triggered in the expected language.

Note:

• The method used to derive and pass the locale value (for example, configuration, business rules, or transformations) may vary depending on the implementation design.
• It is important to ensure that the value maintained is in the correct locale (external code) format, as expected by IAS/IPS.

• How the language for the email template is determined when IAS sends emails (3416720)
• How to send welcome e-mails in a predefined language? (3035482)
• Define PreferredLanguage Transformation

ias activation email language, Preferred Language, defaultLocale, Email Language, IAS, IPS, HRIS Sync, Recruiting to Onboarding, Locale Mapping, table_users_sys_info, Email Default Language, identity authentication , KBA , LOD-SF-OBX-IAS , IAS User Authentication , Problem