PDF C_THR84_2311 Study Guide

Some leading practices to create locales in Career Site Builder are:

• If the customer requires only one language and it is NOT en_US, you can change the default locale. This will save you time and effort as you do not need to create a new locale and duplicate the pages and components.You can simply edit the default locale and change the language and other settings as needed1.
• Follow the same layout for the localized pages as the default locale. This will ensure consistency and usability across different languages and regions.You can usethe same page templates and components for the locales, and only change the text and images as required2.

The other options are not leading practices for creating locales in Career Site Builder:

• Using Google Translate to translate text for locales is not recommended as it may result in inaccurate or inappropriate translations.You should use a professional translation service or a native speaker to ensure the quality and accuracy of the text3.
• Creating the Home page for the locale instead of duplicating it from the default locale is not a leading practice as it will create extra work and maintenance.You can use the Duplicate Page feature to copy the Home page from the default locale and then edit the text and images as needed for the locale4.

References:1:SAP Help Portal - Change the Default Locale2:SAP Help Portal - Create a New Locale3:SAP Help Portal - Translate Text for Locales4:SAP Help Portal - Duplicate a Page

According to the SAP SuccessFactors Recruiting: Candidate Experience Administration course1, the actions you need to take to facilitate reporting on which candidates arrived at the CSB site from the corporate site are:

• Deliver source-coded backlinks so that your customer can replace all links from their externally-hosted sites to their CSB site. This means that you need to add a source parameter to the URL of each link that points to the CSB site, such as ?source=corporate. This will allow the CSB site to track the source of the traffic and report it in the Advanced Analytics dashboard1.
• Submit the Referral Engine Task support ticket after moving your customer’s CSB site to production. This is a mandatory step that enables the Referral Engine feature, which is a tool that allows you to create and manage referral campaigns for your CSB site. The Referral Engine also provides reporting on the referral sources and conversions of the candidates who applied through the CSB site1.
• Adding a campaign code to all XML job feeds that you create for your customer is not an action you need to take to facilitate reporting on which candidates arrived at the CSB site from the corporate site. This is because the campaign code is used to track the performance of the job postings on external platforms, such as job boards or social media, and not on the corporate site. The campaign code is also optional and not required for the XML job feeds to work23.
• Recommending that your customer opt-in for the Organic Network is not an action you need to take to facilitate reporting on which candidates arrived at the CSB site from the corporate site. This is because the Organic Network is a feature that allows your customer to leverage the existing traffic on their CSB site to promote their jobs to other relevant candidates, and not to track the traffic from their corporate site. The Organic Network is also optional and not required for the CSB site to function4.

References: XML Job Feeds, Campaign Codes, SAP SuccessFactors Recruiting: Candidate Experience Administration, Organic Network

A standard Recruiting statement of work (SOW) is a document that defines the scope, deliverables, and timeline of a Recruiting implementation project. It also specifies the roles and responsibilities of the project team, the assumptions and dependencies, and the acceptance criteria. According to the Recruiting Implementation Handbook, a standard Recruiting SOW includes the following tasks:

• Enable Mobile Apply: This task involves enabling the Mobile Apply feature, which allows candidates to apply for jobs using their mobile devices. The Mobile Apply feature supports various application methods, such as uploading a resume, using a LinkedIn profile, or filling out an application form.
• Configure one job layout: This task involves configuring the appearance and content of the job posting page, which displays the details of a job requisition. The job layout can be customized using Career Site Builder, which provides various components and widgets to enhance the job posting page.
• Configure one standard XML feed: This task involves configuring the XML feed, which is a file that contains the data of the job requisitions. The XML feed can be used to post jobs to external job boards, such as Indeed or Monster, or to internal career sites.

The following tasks are not included in a standard Recruiting SOW:

• Enable LinkedIn integration: This task involves enabling the LinkedIn integration, which allows candidates to use their LinkedIn profile to apply for jobs, and recruiters to source candidates from LinkedIn. The LinkedIn integration requires additional configuration and licensing, and is considered as an optional or custom task.
• Configure 20 Category or Content pages: This task involves configuring the Category or Content pages, which are the pages that display the information or content related to the career site, such as the company culture, benefits, or events. The Category or Content pages can be created and managed using Career Site Builder, which provides various components and widgets to enhance the pages. However, the standard Recruiting SOW only includes the configuration of up to 10 Category or Content pages, not 20.

References:

• Recruiting Implementation Handbook: This document provides an overview of the Recruiting implementation process, including the project phases, tasks, deliverables, and best practices. It also provides the sample SOWs for standard and custom Recruiting projects.

When creating job descriptions in the requisition, it is important to follow some leading practices to ensure that the job descriptions are clear, concise, and compelling. According to the SAP SuccessFactors Recruiting: Candidate Experience Administration course, some of the leading practices are:

• Place the most unique information about the job at the top of the job description: This practice helps to capture the attention of the candidates and highlight the main selling points of the job. The most unique information could include the job title, location, summary, or key responsibilities.
• Include information in the job description such as company information and benefits: This practice helps to showcase the employer brand and value proposition, and to motivate the candidates to apply for the job. The company information and benefits could include the company culture, vision, mission, values, awards, or recognition.

The following practices are not recommended:

• Add an image to the job description to attract more attention: This practice may not be effective, as the image may not display properly on the career site or on external job boards. Moreover, the image may distract the candidates from the actual content of the job description, or may not be relevant to the job.
• Do NOT include bullets in job descriptions as they will not display in the career site: This practice is incorrect, as bullets can be used in job descriptions and they will display in the career site. Bullets can help to organize the information in the job description and make it easier to read and scan.

References:

• SAP SuccessFactors Recruiting: Candidate Experience Administration: This course covers the configuration and administration of the candidate experience features, such as Career Site Builder, Candidate Relationship Management, and Advanced Analytics. It also provides best practices and tips for creating job descriptions in the requisition.