C_THR84_2311 Exam Dumps : SAP Certified Application Associate - SAP SuccessFactors Recruiting: Candidate Experience 2H/2023

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 internal career site is enabled, you can configure different settings and content for internal employees and external candidates on your Career Site Builder site. This allows you to tailor the candidate experience based on the audience and the business needs. Some of the differences that can be applied are:

• Internals and externals may be able to apply to different jobs: You can set up job requisitions to be visible only to internal employees, only to external candidates, or to both. This way, you can control who can view and apply to certain jobs based on their eligibility and suitability. You can also set up different application processes and forms for internals and externals, such as requiring different information or documents, or enabling different integrations or assessments.
• Internals and externals may see different page components: You can create different page components for internal employees and external candidates, such as banners, videos, testimonials, or forms. You can also assign different page components to different pages based on the audience, such as showing different messages or images on the home page, category page, or job details page. This way, you can customize the look and feel of your site and provide relevant and engaging content for each group.
• Internals and externals may see different headers and footers: This is not a correct answer, because the header and footer settings are global and apply to the entire site, regardless of the audience. You cannot create or assign different headers and footers for internal employees and external candidates. However, you can use the header and footer components to display different links or menus based on the audience, such as showing different career site pages, external sites, or internal resources.
• Internals and externals may see different job layouts: This is not a correct answer, because the job layout settings are also global and apply to the entire site, regardless of the audience. You cannot create or assign different job layouts for internal employees and external candidates. However, you can use the job layout components to display different information or actions based on the audience, such as showing different job details, apply buttons, or share options. References