Localizing the Career Site

Objectives

After completing this lesson, you will be able to:
  • Review localization requirements and responsibilities with the customer
  • Enable the approved locales
  • Duplicate each page on the career site and enter the translated text
  • Create a header and footer for each localized page and enter the translated text
  • Enable other locale-specific settings

Localization Overview

As an organization extends its global reach, the need to attract local talent often requires localizing (translating) your customer's career site. In addition to allowing candidates to search for jobs based on their local language, all elements of the Career Site Builder site can be localized, including job alert emails and Google Job Maps.

Localization Timing

During implementation projects, the default locale (usually English) should be built and approved before moving forward with additional locales. Begin the process as soon as the default locale text has been approved.

The customer’s additional locales can be enabled and configured either during Iteration 2 or 3, depending on the state of the default language text. If the customer’s text in English is approved at Iteration 2, begin the localization process. If not, wait to begin localization until the English copy is approved during Iteration 3.

If the translation phase does not begin until iteration 3, you’ll need to add a cushion in the schedule.

Career Site Builder Localization

Locales are set up to mirror the base site (typically en_US, US English) calling in the same imagery and design, but localized based on the language.

Examples of the same Best Run company's pages in different locales.

Introduction to Locales

A locale identifier consists of a language code and a country/region code.

Examples of Locales Identifier such as en_GB, en_US, es_MX, or es_ES.

Within SAP SuccessFactors, the standard default language is normally English US (en_US), though it can be changed to another language. For example, if your customer only requires Danish, change the default locale to da_DK.

Note

  • UTF-8 Encoding should always be used for every xml, csv and spreadsheet file involved in a translation project. All file uploads in SAP SuccessFactors should be done with UTF-8 encoding selected.
  • Translations are always provided by the customer. Do not use Google Translate! It exposes the customer’s content to Google.

General Localization Process

The SAP SuccessFactors statement of work or Schedule A lists the languages that the consultant is responsible for implementing. The leading practice is to have the same layout, images, and (translated) copy as your base site locale. This is a web standard and the way CSB projects are normally scoped. If your customer requests changes to the layout, images, or other elements for their localized pages, that may require a change request.

General considerations of the localization process are as follows:

  • The text in the system interface is translated when the locale is enabled. System text translations can be replaced in Career Site Builder under Tools → Translations.
  • Career Site Builder locales typically include localized content for all page types and job alert email templates.
  • Any custom text that the customer provides for the default language must be translated by the customer for the other locales that are enabled. This includes text provided for CSB page components.
  • On the pertinent tabs in the Recruiting Marketing Workbook, columns for translations have been added at the right. Copy the columns for additional languages. Hide unnecessary columns before providing the workbook to the customer for translations.
  • All translations should be provided by the customer in the workbook and delivered to the consultant at one time. If necessary, before beginning configuration of the languages, the consultant will alert the customer of any translations that were missed, HTML that was corrupted, and so on.
  • The consultant is responsible for entering the translations that are provided.
  • The customer is responsible for testing the translations.
Global Elements Localization Columns in the Workbook with the fr_FR and zh_CN columns highlighted.

Manage Languages and Manage Templates

Locales can be enabled from Provisioning → Company Settings → Language Packs or from Admin Center → Manage Languages.

Leading practice is to always enable two tools for your customers from Provisioning → Company Settings. This empowers customers to manage their own localization needs after go-live.

  • Manage Languages can be used to enable languages and change translations for labels within SAP SuccessFactors HCM. (Manage Languages was previously called Tier 3 Language Packs.)
  • Manage Templates enables customers to edit the Recruiting templates: Job Requisition, Job Application, Candidate Profile, and Offer Detail templates.

Remind your customers that Manage Languages and Manage Templates are powerful tools and should only be used by trained users. Please see instructions in HR831, the Recruiter Experience Administrator Training Guide, which can be downloaded from the SAP Learning Hub.

Need more Recruiting localization information? See the Localization slides in the Recruiting Learning Room to learn how to translate all candidate-facing content, including labels on the Recruiting templates, plus communication with candidates, data privacy statements, and so on.

Localization Permissions

For users who will use Manage Languages, also from Manage Permission Roles, select Manage Recruiting on the left and Manage Recruiting Languages on the right.

Manage Recruiting Languages Permission.

From Manage System Properties, select Text Replacement on the right. This is also the permission for Manage Languages.

From Manage System Properties, select Text Replacement.
Manage Languages page with a few languages selected.

Localization Enablement

The customer’s locales are enabled in the following places:

  • Manage Languages (or Provisioning)
  • Manage Recruiting Languages
  • Career Site Builder

Enablement of Locales from Manage Languages

To enable a new locale, proceed as follows:

  1. Navigate to Admin Center → Manage Languages.
  2. Select the desired locales from the Active column.
  3. Choose Save.

Once a language is enabled, it appears as an option for all SAP SuccessFactors HCM users to select as their preferred language from the Settings menu. The language will also become available in Admin Center → Manage Recruiting Languages.

Also recommended: At the bottom of the page, choose Update to increase the maximum number of keys to 10,000 and the file size maximum to 10 MB.

To increase the maximum number of keys to 10,000 and the file size maximum to 10 MB, choose Update on the Configuration age.

Enablement of Locales from Manage Recruiting Languages

From Admin Center → Manage Recruiting Languages, select the same languages that you enabled from Manage Languages.

The Default Language is set during the initial implementation.

In Admin Center, specify the default language from the dropdown list and select the enabled languages checkboxes.

Enablement of Locales in Career Site Builder

To enable locales in Career Site Builder, proceed as follows:

  1. From Career Site Builder, navigate to Settings → Site Configuration → Site Locales.
  2. Select the same locales as from Manage Languages. The Default Locale displays at the top. Do not delete the default.
  3. Save.
On the Site Configuration, enable locales. Under Site Configuration, the en_Us and es_ES are highlighted.

IMPORTANT! Select the identical locales that were enabled from Manage Languages. For example, do not select es_ES in Manage Languages and es_MX in Career Site Builder.

Enable Locales

Business Example

Enable English, German, and Spanish for Best Run in Provisioning, Admin Center, and Career Site Builder.

Task 1: Enable Locales in Provisioning

Steps

  1. Log in to Provisioning and navigate to Company Settings → Language Packs. Alternatively, you can enable locales from Admin Center → Manage Languages.

  2. In addition to English US-en_US, select Deutsch (German)-de_DE and Español (Spanish)-es_ES). If additional languages are enabled, you can leave them. You won’t select them for Recruiting.

  3. Scroll up and choose Save Feature to save your changes.

Task 2: Enable Locales Used in Recruiting in Admin Center

Steps

  1. Log in to your instance and navigate to Admin Center → Manage Recruiting Languages.

  2. Confirm that English US is the Default Language.

  3. For Enabled Languages, select Deutsch (German), English US, Español (Spanish).

  4. Save Changes.

Task 3: Enable Locales in Career Site Builder

Steps

  1. Open Career Site Builder and navigate to Settings → Site Configuration → Site Locales.

  2. Confirm that en_US is enabled and is the default Locale.

  3. Enable de_DE and es_ES.

  4. Save.

Page Localization

The following instructions guide you through the localization of each page type.

Home Pages Localization

To localize home pages, you may take advantage of the CSB function to quickly duplicate pages. You will be able to duplicate the home page in the default language and create it under the new locale. This will copy the design and the structure of components on the new locale’s home page; however, you will need to provide the translated text for each component as necessary.

On the Home Page, the Duplicate Page button is highlighted.

Content Pages Localization

To localize content pages, you can use the duplicate page functionality.

Under the Pages → Content tab, select the Main Brand and the content page which you want to duplicate.

Use the duplicate page functionality to localize content pages.

Once you have duplicated the page, enter the title and select the desired locale and brand as well as the translations.

Landing Pages Localization

To localize content pages, you can use the duplicate page functionality.

Under the Pages → Landing tab, edit the page which you want to duplicate and choose the gear button and select Duplicate Page.

To edit the page which you want to duplicate, choose the gear button and select Duplicate Page.
  • Enter a name and select the desired locale and brand.
  • Enter the translations.

Localize Category Pages

These instructions duplicate the English (default language) components, but the rule must be recreated, and of course, any text must be translated.

To localize category pages, proceed as follows:

Steps

  1. Under the Pages → Category tab, click Add.

  2. Name the new category page in the desired language.

  3. On the Details page, make the new page Active and Save.

  4. On the main Category Pages listing, select to edit the English category page.

  5. Choose the gear icon at the top of the page and select Duplicate Page. Confirm. Now the English components are duplicated on the translated page.

  6. Enter the translations.

  7. From the Rule Editor page, recreate the rule. The values need to be translated on the job requisition. For example, "Rojos" for the brand field.

    On the Category Pages, choose to Job List tab. It displays the (es_ES) Espanol (Espana) ? Red / Empleaos rojor label at the top of the page. At the bottom, the field Brand and the value Rojos are highlighted.

    Note

    For category pages based on brand, if all locales display in the results, in addition to creating the rule based on brand (such as "Brand=bestrun"), also add a rule for language (such as "Locale=en_us").

Create a Spanish-Language Home Page in Career Site Builder

Business Example

In this exercise, duplicate the Default Brand home page and enter placeholder text in Spanish.

Steps

  1. Navigate to Pages → Home and notice that all available locales are displayed. If they are not, refresh the browser window containing Career Site Builder.

  2. Navigate to en_US → Default Brand → Home.

  3. Select the gear icon at the top of the page and select Duplicate Page to create a duplicate of the base locale homepage.

  4. Select the Locale and Brand you wish to copy to, for example, es_ES and Default Brand.

  5. Select Save.

  6. Navigate to the Spanish Default Brand home page that you have just created and confirm that all components were copied.

  7. Save Draft and preview. Notice which text was localized, and which must be updated manually.

  8. For practice, enter translations for the Spanish Subscribe Form.

    1. Return to Pages → Home → es_ES → Default Brand → Home.

    2. Choose the Subscribe Form to open it.

    3. For both the Header Text and Body Text, enter Español.

    4. Publish and preview.

      During an implementation, you would enter the translations for each of the components for each page in the same way.

    5. From the page preview, click the Language (Idoma) dropdown and switch to English.

Localization of the Header and Footer

You create headers and footers for each locale. (These elements cannot be duplicated.) In a standard statement of work, the logos and links are the same, but updated for the local language.

Navigate to Appearance → Styles → Headers (select the locale and brand) and then select Menu.

The leading practice is to have the same header and footer links in the same order, with the same action for all locales. This is a web standard and helps with testing and future troubleshooting.

On the Global Styles: Header Editor menu, create headers for each locale.

Enablement of the Locale Selector in the Header

To enable the Locale Selector in the header, proceed as follows:

  1. Navigate to Appearance → Styles → Headers (select the locale and brand) and then select Details.
  2. For Use Locale Selector, select Yes.
On the Details tab, turn the Use Locale Selector toggle on.

System Text  Localization

The Tools → Translations menu allows you to replace default (system) text on the CSB site for any enabled locale.

Select the desired locales from the Locale Filter dropdown at the top.

To edit the provided translation, select the text you would like to change, and then enter the new text in the text box that appears.

Remember that custom translations entered on this page must be exported from the Stage site and imported to Production separately from the site import and export.

Use the Tools: Translations menu, to replace default (system) text on the CSB site for any enabled locale. The Export and Import buttons on the right-hand side are highlighted.

Localize the Job Alert Email Template

To localize the Job Alert Email Template, proceed as follows:

Steps

  1. In Career Site Builder, navigate to Layouts → Job Alerts Email Template.

  2. Select the desired language.

  3. Enter any changes that your customer requires.

  4. Select Preview and take a screen capture for your customer’s review.

    On the Job Alert Email Template page, the es_ES locale is highlighted.

    If your customer would like to ensure that the only jobs that the user receives are from their selected locale, you must note this in the CSB → Settings → Site Configuration → Site Information → Use Locale for Job Alerts.

    When checked, only jobs in the user's selected locale will be sent in job alert emails. For example, if the user chooses their locale as es_ES, only jobs matching that locale will be sent to the user via agent email.

Optional: Google Job Map for Other Locales

When adding a Google Job Map, you have the option of filtering job searches by locale. Some customers present job maps by locale, so a different map is displayed when the candidate selects the language.

Display different job maps based on the language that the candidate selected.

For this use case, the map component is added to the home page for each locale and updated to represent the various regions of the world.

To allow job searches performed on the Google Job map be filtered by locale, on the Details page, turn the Search Filtered by Locale toggle on and set the Region Code to US.
The Job Map Can be Customized for the Home Page for each Locale.

Using this configuration option, when the candidate selects a different language from the header, the appropriate page – and map – display.

Optional: Region Code on the Google Job Map

Google Maps applies a default bias for application behavior towards the United States. If you want to change how the map is presented, change the Region Code.

Help Text From the Google Job Map Component, disclosing the default bias.

Optional: Region Code on the Google Job Map

Optional: Labels Updating on the Create an Account Page

To change labels on the Create an Account page, consider the following:

  • Sometimes customers wish to change the text on the Create an Account page.
  • Create an Account is the only page accessed from Career Site Builder sites that requires Manage Languages to change the text.
  • Note that you cannot add or remove or reorder fields on this page, but you can change the labels.
  • See the Localization slides in the Recruiting Learning Room for instructions.
Change Labels on the Create an Account Page.

Roles in CSB to Maintain the Content for New Locales

Once you have configured the necessary localization requirements, it is critical to provide permissions for administrators who will be responsible to maintain localizations to the career site builder pages. Customers commonly have a user or team who maintains the pages on the career site. CSB-specific roles are created from Career Site Builder → Users → Roles.

After creating the role, assign it to Admin Users. Work with your customer on their specific needs.

Sample permissions for the Update Pages Role for Spanish-speaking admins are highlighted.

Some sample permissions for the Update Pages Role for Spanish-speaking admins are shown in the figure above.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn