BPM Task Assignee Cannot Approve In Case He Previously Has Been Assigned An FYI Task For The Same Approval Workflow
(Doc ID 2625057.1)
Last updated on MARCH 18, 2020
Applies to:Oracle Fusion Self Service Procurement Cloud Service - Version 11.13.19.07.0 to 11.13.20.01.0 [Release 1.0]
Information in this document applies to any platform.
Depending on the approval rules definition, there are cases where, during the approval workflow, the same user is assigned first an FYI task and later on an approval task. If the human task is set with aggregation this user gets assigned the FYI task and he is able to see it in the worklist. Further, when the user is assigned the action required task, created some time after the FYI, he has no means to act upon it (approve/reject).
This has a severe impact on users activity as it results in the transactions with this type of approval workflow being stuck.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document