Understanding Drop Zones
Configurable drop zones allow you to add fields to delivered pages without customizing the delivered component or page definition. Your fields are displayed and processed along with fields from the main page definition and any nested subpages or secondary pages.
At design time, a placeholder subpage stub (PT_ERCSUBPAGE_STUB) is inserted into a special group box on the page definition, creating what is referred to as a “drop zone.” Drop zones can be added to a main page, to subpages at any nesting level, and to secondary pages. Typically, PeopleSoft application teams (PeopleSoft HCM, PeopleSoft FSCM, and so on) have identified which delivered pages can be extended by customers and have already added one or more configurable drop zones on these pages, subpages, and secondary pages. Then, you create custom subpage definitions and associate your subpages to one or more drop zones. Finally, at runtime during the component build process, the configured subpage dynamically replaces the subpage stub. The records and fields defined on your subpage are loaded into the component buffer along with the records and fields from the main page definition.
The complete procedure for inserting and configuring drop zones includes three tasks described within this topic:
-
(Optional) Inserting configurable drop zones.
Important:
This task is described for informational purposes only. Drop zones are delivered by PeopleSoft application teams. Therefore, this step is typically not performed by you. While you could add drop zones to your own custom application pages, there really is no reason to do so. Moreover, if you were to add drop zones to pages delivered by Oracle, those changes would be considered customizations.
To understand the process used by PeopleSoft application development teams, see Inserting Configurable Drop Zones.
-
Creating subpages for these drop zones.
-
Configuring a selected drop zone by associating a custom subpage to it.