Think of this component as a template used in a mail merge. I strongly advise not to meddle with these definitions as they are very complex, tightly bound to existing Compositions and also liable to change through PUM Updates as new features are added and the inevitable defects are fixed.

All Fluid Approval pages use the same component and page definitions - namely COMPONENT.EOAWMA_MAIN_FL along with it's main pages PAGE.EOAWMA_MAIN_FL, PAGE.EOAWMA_TXNHDTL_FL and PAGE.EOAWMA_TXNLDTL_FL. A composition describes what transaction data/fields to make available to your Page Composer when you come to define (or compose) your Fluid Approval page.Ĭ) Page Composer - (Enterprise Components > Page Composer) - This a developer/functional tool used to build a Fluid Approval page using fields defined in the Composition.Ģ) Page Composer is used to define a Fluid page for Approvals.

This means if you have an AWE definition and you want to surface your approval transaction in Fluid then you're already part way there.ī) Developer Registration - (Enterprise Components > Page Composer Administration)- This is a developer tool used to define compositions. What makes Page Composer so powerful is the underlying data structures defined in 'Developer Registration'- found in Enterprise Components > Page Composer > Developer Registration.ġ) There are 3 'moving parts' to Fluid ApprovalsĪ) AWE Process Definition - This is not new and has always existed since AWE first appeared. Using Page Composer you can change the Fluid Approval pages - adding or removing fields, change field layout and style for any device form factor. Page Composer is currently used by Fluid Approvals for rendering AWE Workflow transactions in Fluid.

Awe setup in peoplesoft