E-EOPC: FAQs on Setting up Fluid approvals using Page composer for Custom AWE transaction
(Doc ID 2264417.1)
Last updated on JULY 15, 2020
Applies to:PeopleSoft Enterprise SCM eProcurement - Version 9.2 and later
PeopleSoft Enterprise PT PeopleTools - Version 8.55 and later
PeopleSoft Enterprise HCM Human Resources - Version 9.2 and later
PeopleSoft Enterprise FIN General Ledger - Version 9.2 and later
Information in this document applies to any platform.
The Purpose of this document is to provide answers to common questions related to the new Page Composer functionality used for Fluid Approvals in PS 9.2 Applications.
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
|Questions and Answers|
|Q1. What are the steps to create a custom Approval process.|
|Q2. Can a custom field be added to get updated upon approval of a transaction?|
|Q3. How to define the labels on the summary list|
|Q4. How/what methods to be used to display/populate grid on the fluid approval page that uses Page composer?|
|Q5. How does the priority(High/Medium/Low) set on the summary page for each transactions. How can this be implemented for a custom approval process?|
|Q6. How to get started with Fluid Approval implementation of custom AWE Approvals?|
|Q7. With Fluid Approvals what is the trigger that would cause the call to custom code that previously had been invoked with classic AWE from Record.Field.FieldChange on Approve Button?|
|Q8. After using the Page Composer Administrator, Developer Registration to Copy an existing Composition into a custom AWE Composition, what steps should be taken to update the Pages and Sections to be unique to the newly created Composition?|
|Q9. How to use Page Composer to create a Link on Approval Page.|