#AWE SETUP IN PEOPLESOFT REGISTRATION#

In fact the Registration name must be the same as the AWE Process Definition. Each Registration is bound to an AWE Process Definition.

You can also define the number of columns that will displayed which can help with field and field label alignment.ДЈ) The Developer Registration tool is used to create a Registration that is based on this template.

If the Section bound to a HTML field on the Page (see Page Registration Section Definitions below) then Page Composer allows you to drag and drop fields into the section.The EOAWMA_RSLT_SBF has 2 sections that are available (technically there are 3 but the third is a special case used for handling the Mas Approval function).Lookout for a blog post on the 'wonders' of the Header Detail page in the very near future. To keep this blog post digestible I'm just going to describe some characteristics of the Main Summary page. This is the page you see if you click one of the approval transactions. Approval transactions, shown on the right, are actually rendered using a sub-page PAGE.EOAWMA_RSLT_SBF (main page is PAGE.EOAWMA_MAIN_FL). This is what you see when you click the Approval tile. The template COMPONENT.EOAWMA_MAIN_FL has 3 main pages The template has a fixed set of 'sections' in which there are a fixed set of 'field placeholders' of various types which are available if you need them. 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