Aaron Engelsrud

Aaron Engelsrud

Drop Zones in PeopleTools 8.58

While Drop Zones were released as new functionality in PeopleTools 8.57, PeopleTools 8.58 extends the included functionality by allowing drop zone to be included in Classic and Classic Plus pages, sub-pages at any nesting level, and secondary pages. Further, Oracle also now offers support for drop zones on unregistered components.

Previously, in the PeopleTools 8.57 release, the functionality was only available on Fluid pages. If you are not yet familiar with Drop Zones, they allow developers the ability to add new fields which are displayed and processed on pages without customizing either the component to the page itself.

Keep in mind, Drop Zones are delivered functionality from Oracle that allow you to add custom fields to delivered pages, sub-pages and components. Per Oracle’s documentation, PeopleSoft application teams are responsible for determining which delivered pages can be extended by customers and have already added one (or more) configurable drop zones on those pages, sub-pages, and secondary pages. If,  you, as a customer, added the drop zone component to a delivered page yourself (say where one didn’t exist but you wanted one), that would be considered a customization. Make sense? If Oracle does it, it’s ok, if you do it, not so much. However, if you read through the linked resource I’ve included below, Oracle has provided detailed instructions on how to insert your own configurable drop zone. They want you to do it - they just don’t support it.

Much like the Application Engine Action Plug-ins, Drop Zones are another effort by Oracle to decrease customer customization while allowing for and encouraging customers to make PeopleSoft meet their specific business needs.

Linked Resource: Configuring Drop Zones