Skip to main content

Oracle APEX 3.2 Released

Oracle has announced the general availability of Oracle APEX 3.2.  In addition, they have re-vamped the APEX home page (http://apex.oracle.com) with a cleaner look than the previous version.

There seems to be a number of security features in addition to the Forms Conversion features that have been discussed for some time.

Comments

Anonymous said…
Hi Scott,

Is there an upgrade version available from 3.1.2 to 3.2?

Thanks
Scott said…
Sure - if you download APEX 3.2 from OTN and install it on top or 3.1.x, it will upgrade it automatically.

Thanks,

- Scott -
Anonymous said…
Thanks Scott. I successfully managed to upgrade from 3.1.2 to 3.2 by following the steps in the installation guide.

Paul
Anonymous said…
Hi Scott,

Do you know if Apex 4.0 will have support for primary keys based on more than two columns? Also, if not, is there are workaround for this short of redesigning the table to use a primary key based on a SID? This is a major potential problem for us since we want migrate a legacy system to Apex.

Thanks In Advance

Paul
Scott said…
Paul,

I don't know if it will, and if I had to guess, would say no.

You can use commas in the two fields to "hack" it and have more than two values as an alternative.

You may want to post this query on the OTN Forum, as it will get a much broader audience - including the APEX development team - there.

Thanks,

- Scott -
Anonymous said…
Thanks again Scott.

Paul
christid said…
Scott,

Dan from FHLB.

How to proceed importing sql script
version 3.2.0.00.27?

We are currently on 3.1.0.0032

Thanks!
Scott said…
Dan,

You'll have to upgrade to 3.2, as APEX is not backward-compatible.

Thanks,

- Scott -

Popular posts from this blog

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 forma

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 rem

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 p