Symptom
CC Role Types receive the Custom Workflow Notifications while some receive the Standard Workflow Notifications.
Environment
SAP SuccessFactors Employee Central
Cause
- Cause 1: The DEFAULT_LOCALE of the CC Role is not maintained in any templates within the Document Generation Group. For example, if the CC Role's DEFAULT_LOCALE is Korean and the Document Generation Group (Email Template Group) assigned in the Workflow does not have any templates in Korean, the CC Role will receive the Standard Workflow Notification.
- Cause 2: Group "Document Generation Group" is Missing in Document Generation template.
- Cause 3: No placeholders present in document template.
- Cause 4: The user triggering the notification does not have permission to Document Generation.
- Cause 5: Incomplete Mapping
Resolution
- Cause 1: If the CC Role Type's DEFAULT_LOCALE is maintained in the Templates within the Document Generation Group, the Workflow Email Notification will be sent in this locale. If it is not maintained, the Standard Workflow Notification will be used.
- Cause 2: If the CC Role Type is External Email, the locale of last approver will be used, if no approvers and only cc then the locale of initiator will be used. If templates in matching locale is maintained within the Document Generation Group, the Workflow Email Notification will be sent in this locale. If it is not maintained, the Standard Workflow Notification will be used.
- Cause 3: If no placeholders present in template, then put a placeholder to in template to put values like name, document name or any text value onto template so that custom email would be sent out and not missed.
- Note: After including the placeholder, please ensure to add the Manage Document Template Mapping as described in SAP Help Portal - Mapping the Document Template in SAP SuccessFactors Document Generation
- Cause 4: Make sure that the user has related permissions under "Manage Document Generation" table in RBP. The permissions available here are:
- Manage Document Template,
- Manage Document Template Mapping,
- Generate All Documents as Admin,
- Mass generate all documents as an admin.
- To avoid any unexpected behavior, make sure to maintain all the available Languages in the Instance within the Document Generation Template and assign them in the same Document Generation Group.
- Cause 5:
- Go to Manage Document Template Mapping
- For the FULLNAME row — click Save to ensure the current reference mapping is committed
- Navigate away and return to confirm the issue persists
- If the Base Object and Target Field show as required and are blocking the save, change the Mapping Type to Field and select the appropriate base object and name field
- After saving, trigger a test workflow for a probationary period evaluation
- Confirm the custom email is received instead of the standard one
- If the issue persists, set the following mapping:
- Mapping Type -> Direct
- Base Object -> The relevant desired object
- Target Field -> externalName
See Also
- KBA 2347226 - Employee Central - Document Generation
- KBA 2699796 - How to check the users who received a mass generated document
- KBA 2287616 - List of supported tags for EC Workflows and EC Alerts
- KBA 2295288 - Document Generation: Specific employees are unable to see the "Document Generation" related tools in Admin Center
- SAP Help Portal - Employee Central Workflows: Implementation and Administration
- SAP Help Portal - Employee Central Document Generation
Keywords
Default Locale, CC Role, Custom Email Notifications, Custom Workflow Notifications, Email Template Group, Standard Workflow Notifications, Document Generation, Language, Workflow Email Notifications, External Email, CC Role Type, Incorrect Workflow Template, Document Generation Template, Locale, doc gen, incorrect template, inconsistent template, standard email, custom email. , KBA , LOD-SF-EC-WFL , Workflows - Configuration, Tools, Objects & Rules , LOD-SF-EC-DOC , Document Generation , LOD-SF-MDF-WFL , Custom Object based Workflows , Problem
SAP Knowledge Base Article - Public