Symptom
Dynamic-role approver not skipped in workflow when custom filter field in dynamic role is null.
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 Employee Central
Reproducing the Issue
- If you have configured a custom field in Job Information and this field refers to a Foundation Object/Generic Object, you can use it as a custom filter when setting up a dynamic role.
- In workflow configuration, this dynamic role is configured as approver with both Target and Source context.
- When editing Job Information, the field (which servers as dynamic group filter) is changed to null. You expect the step 3 approver should be skipped since the target value is null and no approver can be resolved.
- However, the approver step is NOT skipped — the workflow resolves the approver using the source value of the custom field.
Cause
This is expected behavior.
Resolution
If customized field is configured as filter in Dynamic Role and it's set to null, the workflow will not respect Target context and falls back to the source value to resolve approver.
Keywords
workflow approver not expected, dynamic role, DR, wfconfig, INC16734058, workflow context, no approver behavior , KBA , LOD-SF-EC-WFL , Workflows - Configuration, Tools, Objects & Rules , Problem
SAP Knowledge Base Article - Public