3787640 - Custom Task Email Notification Not Triggered in Onboarding

• Custom task email notification is not triggered
• Business rule execution completes successfully and the email initiation function is called in rule trace.
• No email record is generated and no email status entry appears.
• Backend logs may show “callbackName = null” during email processing.

SAP SuccessFactors Onboarding

1. Complete the onboarding custom task that is configured to send a custom email notification via Email Services.
2. Check Email Status and observe that no email is created although the rule trace shows successful execution.

The issue occurs due to inconsistent configuration between the business rule, email category, and content builder context.

• The system attempts to retrieve data from an incorrect or unavailable context
• This results in null values, causing the email trigger to fail
• Additionally, mismatches between email category, template, and recipient configuration can prevent notification triggering

To resolve the issue, ensure that the email trigger configuration is consistent and aligned with the Custom Task context:

1. Use Correct Email Category

• Set the Email Category to:
  • Onboarding Custom Task Content Builder (when the business rule is configured on the Custom Task object in Configure Object Definitions)
• This ensures the email is triggered using the correct object context

2. Align Business Rule Data Source

• Ensure the business rule is:
  
  • Using the correct base object/data source aligned with Custom Task
• Avoid dependencies on unrelated objects, which may return null

3. Validate Recipient Configuration

• In the email category:
  • Maintain a valid Recipient Builder
  • Ensure all users in dynamic/static groups are active
• If using:
  • Dynamic Group → verify users exist and are active
  • Role-based recipients → ensure proper assignment

4. Ensure Template and Category Consistency

• Verify that the email template is correctly linked to the category
• Maintain consistent configuration for:
  • To (Recipients)
  • CC and BCC fields
• Ensure content builder and template setup are aligned

5. Validate Custom Task Data

• Navigate to: Manage Data → Custom Task Object
• Verify:
  • Task status is valid
  • Required fields are populated
  • Conditions used in the business rule are met

6. Perform Rule Trace and Testing

• Enable Rule Trace
• Complete the Custom Task
• Validate:
  • Rule execution
  • Condition satisfaction
  • Email trigger action

Conclusion

Email notifications for Custom Tasks depend on proper alignment between business rule context, email category (content builder), and recipient configuration. Any inconsistency in these components may prevent the notification from triggering.

• 3337864 - Custom Email notification is not sending - Onboarding
• 3228120 - Email Services Main KBA - Onboarding
• 2935125 - Notifications fail to be sent although explicitRecipients is maintained
• Creating a Business Rule to Trigger an Email Notification When the Personal Data Collection Step is Completed

onboarding email, email services, email category, explicit recipient builder, explicitRecipients, notification not sending, custom task email, business rule, rule trace, email not generated, cc, bcc, recipient builder, callbackName null, onboarding notification , KBA , LOD-SF-OBX-EML , Notifications , Problem