You want to send a candidate an Ad-hoc e-mail but you CANNOT find the e-mail template you have
configured. What could be the cause of this problem? Note: There are 2 correct answers to this
question.
B C
Explanation:
In SAP SuccessFactors Recruiting, there are several possible reasons why an email template may not
appear in the Ad-hoc email selection. Here’s a detailed breakdown of the causes and solutions as per
SuccessFactors Recruiting documentation:
Selected Language is NOT Correct (Option B):
SAP SuccessFactors Recruiting offers multi-language support. When configuring email templates,
each template can be defined in multiple languages. If a user selects a language for which the email
template is not configured, the template will not be visible in the email selection options.
Steps to Check:
Go to Admin Center > Manage Recruiting Email Templates.
Open the desired email template and check if it has content for the language selected by the user.
Add the required translations for missing languages if needed.
Reference: SAP SuccessFactors Recruiting Management Implementation Guide - Email Template
Configuration section.
Email is NOT Enabled (Option C):
For an email template to be accessible, it must be enabled in the system. If the email template has
not been enabled, it will not be available for ad-hoc use.
Steps to Enable:
Navigate to Admin Center > Manage Recruiting Email Templates.
Locate the template in question, open its settings, and verify if it is enabled. If it is not, select the
option to enable it.
Reference: SAP SuccessFactors Recruiting Management User Guide - Enabling Email Templates.
Explanation of Incorrect Options:
Option A - The email is NOT linked to the correct email notification template:
Email notification templates and ad-hoc email templates function independently in SAP
SuccessFactors Recruiting. Notification templates are used for automatic notifications triggered by
specific actions, while ad-hoc templates are manually selected by users. This separation means that
an ad-hoc email template does not need to be linked to a notification template.
Option D - The email is NOT assigned to the correct email trigger:
Triggers are primarily used for system-generated notifications based on events, not for ad-hoc
emails. Ad-hoc emails do not require a trigger to be visible to users, so this is not a relevant cause.
In Admin Center where would you configure the e-mail template that is associated with the
requisition route map?
D
Explanation:
To configure an email template associated with a requisition route map in SAP SuccessFactors
Recruiting, administrators must use the E-mail Template Notification Settings. This is where email
templates tied to various actions in the recruiting process, including requisition approval workflows
(route maps), are managed and assigned.
Steps to Configure:
Go to Admin Center > E-mail Template Notification Settings.
Within this section, locate the templates associated with requisition events or requisition route
maps.
Customize or assign the appropriate email template based on the route map stage or approval action
for requisitions.
Reference: SAP SuccessFactors Recruiting Management Implementation Guide - Requisition Route
Map and Email Notifications sections.
Explanation of Incorrect Options:
Option A - Manage Recruiting Groups: This option is used to define recruiting groups for managing
permissions across recruiting users, not for configuring email templates.
Option B - Manage Recruiting Settings: This setting allows configuration of general recruiting
preferences but does not manage specific email templates.
Option C - Manage Offer Letter Template: This option is used exclusively for configuring offer letter
templates, not requisition-related emails.
Where do you grant a user access to Recruiting E-mail Templates?
D
Explanation:
To grant a user access to Recruiting Email Templates, permissions must be assigned via Manage
Permission Roles in Admin Center. Permissions control which users or roles can access, view, and
manage recruiting email templates.
Steps to Grant Access:
Go to Admin Center > Manage Permission Roles.
Select the role for which you want to grant access to email templates.
In the role permissions, navigate to Recruiting Permissions and check the option for Manage
Recruiting Email Templates.
Save the changes to apply the permissions.
Reference: SAP SuccessFactors Recruiting Management Security and Permissions Guide - Recruiting
Permissions section.
Explanation of Incorrect Options:
Option A - In Provisioning → Company Settings: Provisioning is used primarily for backend
configurations and system setup, but it does not directly control user access permissions to email
templates.
Option B - In Admin Center → Manage Recruiting Settings: This area allows configuration of
recruiting-related settings but does not control user-specific permissions.
Option C - In Provisioning → Managing Recruiting: Provisioning is not where user access to recruiting
email templates is configured.
=========================
What could cause an automated e-mail notification to be triggered? Note: There are 2 correct
answers to this question.
B C
You want to trigger e-mails by candidate status. Where is the trigger configured?
A
Explanation:
To trigger emails by candidate status, the appropriate configuration is done in the Edit Applicant
Status Configuration section. Here, administrators can define email notifications based on specific
candidate status changes.
Steps to Configure:
Go to Admin Center > Edit Applicant Status Configuration.
Select the relevant status and specify the email template to trigger for each status change.
Save the configuration to ensure that emails are triggered automatically based on status changes.
Reference: SAP SuccessFactors Recruiting Management Configuration Guide - Applicant Status and
Email Triggers section.
Explanation of Incorrect Options:
Option B - In E-mail Notification Template Settings: This is for managing general email templates, not
configuring status-based triggers.
Option C - In Recruiting E-mail Triggers: This option does not exist as a specific configuration area.
Option D - In Manage Recruiting E-mail Templates: This is used to manage email templates but does
not control the triggering mechanism for candidate status changes
Which of the following are characteristics of standard e-mail notification templates? Note: There are
2 correct answers to this question.
B C
Explanation:
Standard email templates in SAP SuccessFactors have the following characteristics:
Shared with Other Modules (Option B):
Some email templates are designed for use across multiple SAP SuccessFactors modules, such as
Onboarding or Employee Central, and can be shared to streamline communication workflows.
Reference: SAP SuccessFactors Email Templates Guide - Shared and Multi-Module Templates.
Predefined for Recruiting (Option C):
SAP SuccessFactors provides a set of predefined templates tailored specifically for recruiting. These
templates support common recruiting actions, such as interview scheduling and application
submission acknowledgments.
Reference: SAP SuccessFactors Recruiting Management Implementation Guide - Standard Email
Templates.
Explanation of Incorrect Options:
Option A - Standard templates can be deleted in Provisioning: Standard templates cannot typically be
deleted. They can be deactivated but remain in the system.
Option D - All standard templates are enabled by default: Not all templates are enabled by default;
administrators must selectively enable and configure templates as needed.
Which SMS messages are tracked on the correspondence audit trail within the candidate summary
page? Note: There are 2 correct answers to this question.
A B
What needs to be configured to enable recruiting e-mail triggers? Note: There are 2 correct answers
to this question.
A C
Explanation:
To enable recruiting email triggers in SAP SuccessFactors Recruiting, two primary configurations are
necessary:
Assign an E-mail Template to the E-mail Trigger (Option A):
Email triggers rely on specific email templates that determine the content of the notification sent.
For each recruiting event, an email template must be assigned to the corresponding trigger to ensure
the correct email is sent when the event occurs.
Steps:
Go to Admin Center > Manage Recruiting E-mail Templates.
Select and configure the email template that matches the trigger you want to activate.
Assign the template to the relevant email trigger.
Reference: SAP SuccessFactors Recruiting Management Implementation Guide - Setting up Email
Triggers and Templates.
Enable the E-mail Trigger in the Admin Center (Option C):
Each email trigger must be enabled to ensure it activates the email notifications. This is done through
the Email Trigger settings in the Admin Center.
Steps:
Go to Admin Center > E-mail Notification Template Settings.
Find the specific trigger (e.g., application submission, offer approval) and ensure it is enabled.
Reference: SAP SuccessFactors Recruiting Management User Guide - Enabling E-mail Triggers.
Explanation of Incorrect Options:
Option B: The "J permission" is related to candidate permissions but is not required to enable email
triggers.
Option D: The Job Requisition template does not control email triggers; enabling them is managed at
the Admin Center level.
When creating multi-stage application permission blocks which of the following must be defined in
the permission? Note: There are 2 correct answers to this question.
A C
Explanation:
In multi-stage application settings, each permission block must define certain elements to control
access for different stages of the application process:
Operator (Option A):
The operator refers to users involved in the recruiting process, such as hiring managers, recruiters,
and approvers. Each permission block must define the operator to specify who has access to the
application stage.
Steps:
Go to Admin Center > Manage Recruiting Roles.
Configure each operator’s access to the relevant stage.
Reference: SAP SuccessFactors Recruiting Management Implementation Guide - Configuring Multi-
Stage Application Permissions.
Permission Type (read or write) (Option C):
Each permission block must also specify the type of access—either read or write—allowing you to
control who can view or edit application information at a given stage.
Steps:
In the Application Template XML, define the read/write access for each stage and operator.
Reference: SAP SuccessFactors Recruiting Management Implementation Guide - Permission Types in
Application Templates.
Explanation of Incorrect Options:
Option B: Applicant type does not need to be specified in each permission block; permissions are
applied based on stages and roles.
Option D: Status labels are not required in permission blocks; they are typically used for candidate
status tracking.
What triggers the country-specific overrides on an Application template?
B
Explanation:
In the Application template, country-specific overrides are triggered based on the derived country
field in the Job Requisition template. This field determines the location of the job and thereby
activates any corresponding country-specific fields or configuration set in the application template.
Define Derived Country Field in Job Requisition Template:
The derived country field is specified in the Job Requisition template, allowing the system to
determine which country-specific settings to apply.
Activate Country-Specific Overrides:
Once the derived country is identified, any predefined fields or layout adjustments for that country in
the Application template are triggered.
Reference: SAP SuccessFactors Recruiting Management Implementation Guide - Configuring
Country-Specific Overrides in Application Templates.
Explanation of Incorrect Options:
Option A and Option C: These options refer to fields in the Application and Candidate Profile
templates, which do not trigger country overrides for the application itself.
Option D: The candidate search filters do not control overrides in the application template.
Which of the following attributes can be used when defining fields on the Application XML? Note:
There are 3 correct answers to this question.
A C D
If a recruiter forwards a candidate's application (using the Forward as Applicant action) which of the
following information can be accessed from the candidate's initial application? Note: There are 3
correct answers to this question.
A C D
What is the Anonymize Attribute intended for?
D
Explanation:
The Anonymize Attribute is used to mark fields that contain personally identifiable information (PII)
so that they can be hidden or anonymized. This is commonly applied to comply with privacy
regulations such as GDPR. When anonymization is triggered (for example, when a candidate’s data
retention period expires), all fields marked with this attribute are anonymized or deleted.
What happens if you set the candidate application attribute sensitive to "true"?
D
Explanation:
When the Sensitive attribute of a candidate application field is set to true, any read or change action
on that field is recorded in the audit logs. This ensures traceability and compliance for fields
containing sensitive or confidential data.
When defining the field attribute overrides in the Application XML which of the following attributes
determine which override(s) should trigger? Note: There are 2 correct answers to this question.
B D
Explanation:
When defining field attribute overrides in the Application XML, certain attributes determine which
overrides will trigger. These include:
Country of the Job (Option B):
The location of the job posting is a common condition for overrides, especially for compliance with
country-specific regulations.
Applicant Type (Option D):
Overrides can be based on the applicant type (e.g., internal or external candidate), as different
application processes may apply to different applicant types.
Reference: SAP SuccessFactors Recruiting Management XML Configuration Guide - Field Attribute
Overrides.
Explanation of Incorrect Options:
Option A - State/Province of the Job Posting: This level of geographic specificity is not typically used
for XML overrides.
Option C - Country of the Candidate: Overrides are generally configured based on job location rather
than candidate location.