SAP Knowledge Base Article - Public

2082025 - Standard tokens not populating on the Requisition Posting Expiration Upcoming email trigger - Recruiting Management

Symptom

  • The Requisition Posting Expiration Upcoming email trigger is sending, but the tokens are not pulling any data
  • The email trigger "Requisition Posting Expiration Upcoming" works in an asynchronous trigger.

Environment

SAP SuccessFactors Recruiting Management

Cause

[[BEGIN_REPEAT]] and [[END_REPEAT]] are not included in the email template

Resolution

The job requisitions that are posted do not trigger an email immediately, rather the emails are sent in a consolidated manner at the end of each day to every recipient. Since this email has consolidated information of all the different job requisitions that are posted within that day, all Job Requisition-related tokens such as JOB REQ TITLE & JOB REQ ID needs to be resolved for every Job Requisition that is included in the email.

To make this possible, we need to wrap the email template content with the mandatory tokens BEGIN REPEAT and END REPEAT.

For example:

 Dear User,

[[BEGIN_REPEAT]]

[[JOB_REQ_ID]] will expire in 5 days.

Kind regards,

Sender

[END_REPEAT]]

Keywords

E-mail, Expire notification , KBA , sf recruiting email , sf email , LOD-SF-RCM , Recruiting Management , LOD-SF-RCM-EML , Recruiting Emails and Notifications , Problem

Product

SAP SuccessFactors Recruiting all versions