E-AWE: Why Does Monitor Approvals Use PSROLEMEMBER, Which Does Not Allow Use of Dynamic Roles For Administrators?
Last updated on DECEMBER 06, 2016
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.50 and later
PeopleSoft Enterprise FIN Payables - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.
Is there a specific reason that Approval Framework (AWE) would need to enforce Static vs Dynamic Roles while working with the Approval Workflow?
For instance the EOAW_APPROVAL_MONITOR.ADMIN.adminActionsPage App Class method buildApproverPromptSQLText, includes building the &fromText using PSROLEMEMBER;
Is this a bug? Or designed this way for a specific reason? Can this be worked around?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms