Symptom
When a workflow is escalated from Approver A to Approver B, it still shows as 'Currently with' Approver A when the initiator looks at their pending workflows in transaction 'View my pending requests'
*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 - Workflow
Reproducing the Issue
- Go to View my pending requests page.
- When the initiator opens the ‘View my pending requests’ transaction to view their pending workflows, the workflow appears as currently with the original approver, even when it has already been escalated. (As highlighted in the below screenshot).
3. However, when you open the workflow to view the details, it shows that it was escalated to Correct Approver.
Cause
This is an expected behavior as per system design.
Resolution
- For delegation cases, it will impact the "Currently with" in the page 'View my pending requests'.
- For escalation cases, it won't impact the "Currently with".
For the portlet 'View my pending request', it shows the workflow requests initiated by current user. And the "Currently with" shows the current blocker of the workflow.
- When the workflow gets escalated, the escalatee should have to deal with the workflow passively for the blocking caused by escalator. So, the escalator shows in "Currently with".
- When the workflow delegate is granted, the delegatee is expected to deal with the workflow initiatively. So, the delegatee shows in "Currently with".
See Also
Keywords
workflow, escalation, currently with, view my pending request, delegation, approver, escalated, Automatic Escalation , KBA , LOD-SF-EC-WFL , Workflows - Configuration, Tools, Objects & Rules , Problem
Product
Attachments
Pasted image.jpg |
Pasted image.jpg |
Pasted image.jpg |
Pasted image.jpg |