An Oracle blog about PeopleSoft Technology

Using Drop Zones at Multiple Levels

Rajesh Shankare gowda
Principal Software Engineer

Components in PeopleSoft can span to multiple pages, sub-pages, and secondary pages. When customizations are needed in these pages, it takes a considerable amount of effort to re-implement these changes in Application Designer when you want to take a new image.

What if we have places where we can add customizations without having to re-implement them for each image update?  

What are Drop Zones?

Configurable Drop Zones allow you to add your custom fields that are displayed and processed on delivered fluid pages without customizing the component or fluid page definition.

This can be achieved using the following simple steps

  • At page design time, a placeholder subpage stub (PT_ERCSUBPAGE_STUB) is placed inside a related content group box in the fluid page definition.
  • You create subpage definitions and associate your subpages to one or more Drop Zones.
  • 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.

See these posts for more information on drop zones:

Using Drop Zones to Isolate Customizations

Drop Zones for Classic Pages

There are also many application posts on drop zones.  Here is one example.

More details are also available in the  “Creating and Configuring Drop Zones” section in peoplebooks.

Can I add Drop Zones at Multiple Levels?

As part of PeopleTools 8.58, Drop Zone configuration support has been extended to support Drop Zones placed at multiple nesting levels of subpages or secondary pages. The following image shows Drop Zones added at multiple levels with a combination of secondary/subpages in the hierarchy.

In the below example, for our ease of understanding, a group box is added around the Drop Zones and are named based on the level in which they are added.

Ex: Label Sub->Sec->Sub->Sub DZ means, the Drop Zone is placed at the 4th level from the top of the main page and Sub signifies Subpage and Sec signifies Secondary page.

The maximum level of Drop Zone added in this example is at the 9th level from the top of the main page. The below image shows the way a Drop Zone is added to an example page.

With the Drop Zone added as shown above, the “Configure Drop Zones” page displays the following. We can see three different Drop Zones added at three different levels

This is how the pages rendered look like before Drop Zone configuration


Labels displayed are from the group boxes, which are added around the related content group box.

Let us configure MULTI_DROP_ZON_SBP to all Drop Zones. MULTI_DROP_ZON_SBP is a simple fluid subpage, which just displays a static text.

After configuration of MULTI_DROP_ZON_SBP to Drop Zones, the below image shows that MULTI_DROP_ZON_SBP is rendered in all Drop Zones at different levels.

This shows the flexibility of Drop Zones even when placed at different levels, without any changes to the page design; we could assign subpages from PIA.

The above behavior is supported in Classic Drop Zones added as well.

Drop Zone Vs Embedded Related Content (ERC) in Fluid Pages

Related Content group box can be used to configure ERC or Drop Zone or both.

To configure only ERC, A Related content group box alone can be placed in a page.

To configure Drop Zone, we should have a Subpage stub (PT_ERCSUBPAGE_STUB) placed inside a related content group box.

Whenever both ERC and Drop Zone is configured for the same related content group box, Drop Zone configuration takes over precedence. Please note that ERC configuration is not removed when we configure Drop Zone for the same related content group box. The below example shows the behavior where the Drop Zones and ERC configuration co-exist.

ERC Configuration: External URL is configured as ERC for the related content group box named ERC_and_DZ. The below image shows ERC Configuration for the same.