- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2020 04:10 PM
We have a workflow that sends an approval, however even after the approver approves it the workflow does not continue. It was approved through the the portal approval, and you can see it back in the case but the workflow does not progress. The approver is outside of the HR Department and does not have any roles. Is there a role I need to give the user ? I have tried a sn_hr_core.case_reader role and even a approver_user role, but the workflow is stuck at Approval-User. Any one have any ideas on how to make this move. I did a nudge in "Active workflows" and that makes it move. Thanks for any help.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2020 05:07 AM
Just an update on this issue. We did find a work-a-round and not the solution. We found that if we put in a comment in the HR Case, that will move the workflow. I created a Business Rule running off the SysApprover table that checks that the HR Service approval record has been approved, if so, I place a comment in the HR Case saying the Approval has been Accepted/Rejected, and that will automatically move the workflow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2020 05:07 AM
Just an update on this issue. We did find a work-a-round and not the solution. We found that if we put in a comment in the HR Case, that will move the workflow. I created a Business Rule running off the SysApprover table that checks that the HR Service approval record has been approved, if so, I place a comment in the HR Case saying the Approval has been Accepted/Rejected, and that will automatically move the workflow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2020 01:28 PM
Hi, I have seen similar(ish) behaviour in domain separated instance (some years ago)
where a user updated the approval via inbound action, but did not have access\visibility rights to the workflow; So the workflow only moved on when a user who had access updated the task in some manner IE added comments.
Not exactly sure how this scenario maps to a current SNC release or non domain separated instance, but perhaps you could further investigations by impersonating an impacted user in dev and see if security debugging raised any flags when updating an approval or task directly.