Skip to main content

Region Attributes Feature in APEX 3.1

Patrick Wolf blogged about a new feature of APEX 3.1 called Region Attributes.  I remember trying to get this in to HTML DB 1.6, back when I was the Product Manager in 2003!

Basically, this feature enables you to specify a parameter at the region level which, in turn, will be placed where the #REGION_ATTRIBUTE# tag is located in the template itself.

This feature will definitely cut down on the number of templates required for an application, as going with Patrick's example, the width of a region template can be defined differently for each instantiation of that template.

I just ran into this issue with a client and had to use a slight workaround.  We have an application with 7 tabs - each of which is a different function.  We wanted to indicate which function a user was performing by placing the corresponding icon in the region itself.  I did not want to have to create 7 almost identical region templates, as that would be too cumbersome to manage.

So, I simply created an Application Item called G_ICON, and then referred to that in my region template using the following notation: &G_ICON.

On each page, I created a Before Header computation that sets the value of G_ICON.  Thus, as the user moves from tab to tab, they will see a different icon, and I only have to manage the contents of a single region template.

This method will be unnecessary once APEX 3.1 is released, but if you do have the need for a very dynamic region or other template, it may come in handy today and in the future.

Comments

Joel R. Kallman said…
>> I remember trying to get this in to HTML DB 1.6

You just didn't offer enough bottles of Maker's Mark as your bribe. ;)

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…