Fusion Absence Management: Why is "Approved By" showing as Employee when Manager submits the transaction on behalf of the Employee?
(Doc ID 2946576.1)
Last updated on JULY 16, 2023
Applies to:
Oracle Fusion Absence Management Cloud Service - Version 11.13.23.01.0 and laterInformation in this document applies to any platform.
Goal
The approval rule condition is the following.
Rule Condition : 1=1
Approval Action: Auto Approve
Starting participant :HierarchyBuilder.getPrincipal( Task.payload.absencesApprovalsRequest.Requestor,-1,null,"LINE_MANAGER")
Top participant :HierarchyBuilder.getPrincipal( Task.payload.absencesApprovalsRequest.Requestor,-1,null,"LINE_MANAGER")
Approval Action: Auto Approve
Starting participant :HierarchyBuilder.getPrincipal( Task.payload.absencesApprovalsRequest.Requestor,-1,null,"LINE_MANAGER")
Top participant :HierarchyBuilder.getPrincipal( Task.payload.absencesApprovalsRequest.Requestor,-1,null,"LINE_MANAGER")
Now Line Manager is submitting the Transaction on behalf of employee.
Now approved by is showing as Employee instead of Manager in the transaction history section in BPM (Manager is the person who submitted the transaction but it is showing as the Employee the approver).
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 |