SAP Knowledge Base Article - Public

2144747 - Tokens are not working with triggers Requisition Posted or Requisition Posting Expiration Upcoming - Recruiting Management

Symptom

Tokens [[JOB_REQ_ID]] and [[JOB_REQ_TITLE]] are not resolving with the “Requisition Posted” and “Requisition Posting Expiration Upcoming" recruiting email triggers.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

SAP SuccessFactors Recruiting Management

Resolution

The email triggers "Requisition Posted" and “Requisition Posting Expiration Upcoming" work in an asynchronous trigger.

This means that posting a Job Requisition does 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 that day, all Job Requisition-related tokens such as [[JOB_REQ_ID]] and [[JOB_REQ_TITLE]] need to be resolved for every Job Requisition that is included in the email.

To make this possible, email content must be wrapped with the mandatory tokens [[BEGIN_REPEAT]] and [[END_REPEAT]].

Example:

[[BEGIN_REPEAT]] Requisition [[JOB_REQ_ID]] [[JOB_REQ_TITLE]] has been posted [[END_REPEAT]]

Requisition Posted.png

As you can see in the above screenshot, Job Requisition-related tokens must be placed between the mandatory tokens [[BEGIN_REPEAT]] and [[END_REPEAT]].

See Also

2122640 - Configuring the Requisition Posted Email Trigger - Recruiting Management

Keywords

requisition posted, requisition posting expiration, e-mail trigger, token, begin repeat, end repeat , KBA , LOD-SF-RCM-EML , Recruiting Emails and Notifications , Problem

Product

SAP SuccessFactors Recruiting all versions