SAP Knowledge Base Article - Public

3423490 - [[SENDER]] token behaviour in Recruiting Management emails

Symptom

This KBA will detail the behaviour of the token [[SENDER]].

Environment

SAP SuccessFactors Recruiting Management 

Reproducing the Issue

  1. Add the token [[SENDER]] to a recruiting email template for adhoc, trigger, or system emails.
  2. Trigger the respective email.

Cause

Emails will be sent with the token [[SENDER]] being filled by the actual user triggering the email.

Resolution

The behaviour for the token is detailed:

  1. For ad-Hoc emails the logged in user or the user who is proxying that gets their name used in the token in the sent email.
  2. For emails that rely on a job to send the email, such disqualified candidate email delay job, the token will use the Job Owner as the sender for the token.

From the Guide Available Tokens for Configuring Recruiting Email Templates 

[[SENDER]]: Name of the user performing the action that causes the email to be sent.

See Also

Available Tokens for Configuring Recruiting Email Templates 

2676541 - Manage Recruiting Email Templates

Keywords

SENDER, token, name, first, last, correspondence, mail , KBA , LOD-SF-RCM-EML , Recruiting Emails and Notifications , How To

Product

SAP SuccessFactors Recruiting all versions