SAP Knowledge Base Article - Public

3716123 - Custom tokens are not populated in some custom notification submissions in Onboarding.

Symptom

Custom tokens are not populated in some custom notification submissions in Onboarding.

Environment

SAP SuccessFactors Onboarding 2.0

Reproducing the Issue

Custom notifications were created when the Final Review step is completed in Onboarding.

 This group of notifications is sent to different users depending on the company.

1. The Final Review step is completed.

2. The emails are sent

3. For some emails, tokens are not populated.

Cause

System limitation

Resolution

  • The issue occurs when the start date is postponed during the Final Review step

  • When the start date is changed on the Final Data Review page, the process object is not updated with the new start date before the email is sent. Because of this delay, the tokens do not resolve correctly from Job Info. This is a system limitation and happens only when the start date is postponed.

  • To avoid this issue, please do not change the start date during the Final Review Data step. Instead, update the start date by navigating to Actions → Access New Hire Data Page, and then proceed with the Final Review step.

  • As an alternative, you may consider using a different email trigger point such as MPH in progress, if MPH is always the next step after the Final Review in your process

Keywords

  • Start Date Postponed
  • Final Review Step
  • Final Data Review Page
  • Process Object Not Updated
  • Job Information Token Delay
  • Email Trigger Timing Issue
  • Token Resolution Failure
  • System Limitation
, KBA , LOD-SF-OBX-DOC , Generation of Documents using PFS , Problem

Product

SAP SuccessFactors Onboarding 2511