E-AWE: Approval Workflow Path Sequence Is Based On The Order Stored In The Database, Does The Order Cause Issues While Processing The Definition Transactions?
(Doc ID 2376870.1)
Last updated on MARCH 21, 2018
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.55 and later
PeopleSoft Enterprise SCM eProcurement - Version 9.1 and later
PeopleSoft Enterprise HCM Human Resources - Version 9.1 and later
Information in this document applies to any platform.
Approval Framework (AWE) Paths appear to be built by database row sequence. A cloned Process Definition where the Paths are exactly the same, except on how they are stored in the database, this SQL output illustrates the opposite order of the Path ID :
Would this behavior be a cause for concern while processing the Definition Transactions?
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