Skip to main content

Page Zero Supernova

Page Zero in APEX is a powerful tool.  For the uninformed, it allows you to put APEX components  on it and have them render on every other page in your application - unless conditionally set to do otherwise.  Components supported on page zero include regions, items, buttons, branches, computations and dynamic actions.

For years now, anytime that I needed a region or item or button on more than one page, I would put it on page zero, and if needed set the condition to display as needed.  It saved a lot of time, as I would only need to create the component once, and was a lot easier to manage as there was only one copy for multiple pages.  As you needed that component to render on additional pages, all that was required was a small change to the condition.

Dynamic Actions, which were introduced in APEX 4.0, are in my opinion, the best feature to happen to APEX.  In a nutshell, they make JavaScript development - specifically of the jQuery type - declarative.  You can specify a number of simple options to do things such as show and hide an item or region, disable items, change the select list values based on the value of another item, etc.  The possibilities are literally infinite, as once you outgrow the declarative features of dynamic actions, you can execute either JavaScript or PL/SQL code.

Thus, the combination of Dynamic Actions on Page Zero is quite powerful, as once you define a Dynamic Action, it would be available on each and every page.  Add a couple of Dynamic Action Plugins to the mix, and you can create some powerful, reusable components in your APEX applications.

But like almost anything else, too much of a good thing is also bad for you.  I recently started using a plugin that allows you to pop open a region on a page via dynamic action in sumnevSERT.  Initially, our requirements were simple - show a single region and allow the user to edit a couple of fields.  But as development progressed, the requirements got more and more sophisticated.  In some cases, the region needed multiple conditional items and even a report.

At this time, we took a step back and had a look at page 0, and it was a mess.  Over 30 dynamic actions, several regions, items and buttons - all of which would render on almost every page - were present.  Since we didn't know which dynamic action or region would be required, we had to render most of them on most of the pages in the application, thus reducing performance and adding a whole lot of complexity.

We fast realized that there had to be a better way.  After some research, we found a different plugin that supported popups based on pages, not regions.  While it did take some re-tooling, it was a lot easier to manage these popups as individual pages, as development could use almost all default functionality and require few, if any, conditional components.  Since the page would only render when requested, the application became much more efficient.  We reduced the number of dynamic actions on page 0 to 8 and eliminated all additional regions, items and buttons.  This was a huge savings not only for immediate performance, but for overall manageability of the application.

Lessons learned here - don't get too attached to any specific plugin or technique that you become blinded by it.  I've often advocated the use of page 0 and will continue to do so, but that recommendation should be taken as such, not as an absolute rule that can not be bent.  If you find yourself in the same scenario, it may be time to retool your approach as well.


Raymond said…
Hi Scott,

Which plugin have you used now instead?
Scott said…

We're using the Skillbuilders Page Plugin by Dan McGhan:


- Scott -

Popular posts from this blog

Logging APEX Report Downloads

A customer recently asked how APEX could track who clicked “download” from an Interactive Grid.  After some quick searching of the logs, I realized that APEX simply does not record this type of activity, aside from a simple page view type of “AJAX” entry.  This was not specific enough, and of course, led to the next question - can we prevent users from downloading data from a grid entirely?

I knew that any Javascript-based solution would fall short of their security requirements, since it is trivial to reconstruct the URL pattern required to initiate a download, even if the Javascript had removed the option from the menu.  Thus, I had to consider a PL/SQL-based approach - one that could not be bypassed by a malicious end user.

To solve this problem, I turned to APEX’s Initialization PL/SQL Code parameter.  Any PL/SQL code entered in this region will be executed before any other APEX-related process.  Thus, it is literally the first place that a developer can interact with an APEX page…

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon...

Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure.

Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a format…

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility.While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region.In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can remain un…