Approval Rules Are Set up in BPM With Routing by Application Role and Task Aggregation = Once Per Task and User Receives 2 Notifications and Must Approve Twice
(Doc ID 2552926.1)
Last updated on SEPTEMBER 04, 2023
Applies to:
Oracle Fusion Purchasing - Version 11.13.19.01.0 and laterOracle Fusion Self Service Procurement Cloud Service - Version 11.13.19.01.0 and later
Oracle Fusion Self Service Procurement - Version 11.13.18.05.0 and later
Oracle Fusion Purchasing Cloud Service - Version 11.13.19.01.0 and later
Information in this document applies to any platform.
Goal
Approval Rules Are Set up in BPM With Routing by Application Role and Task Aggregation = Once Per Task and User Receives 2 Notifications and Must Approve Twice
Does Aggregation = Once for Task work with tasks that are not assigned to a user?
Reproduce by steps:
1. BPM rules are set up for routing to user based on Application Roles
2. The same user/Approver is triggered twice and receives 2 approval notifications
3. Since Aggregation = Once for Task set up, you expect this user to approve only once, but the system is requiring the approver to approve twice.
Solution
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
| Goal |
| Solution |
| References |