Skip to main content

Some "small" APEX 4.0 EA3 features...

By
In the latest release of APEX 4.0 (available on tryapexnow) I noticed two nice new features. First of all, on the far right side of the Home page of the builder, there is a little region called "Available Updates". If you click on the little "i" in the upper right of that region, you'll navigate to another page where you can control if you want to check for those updates. Wonder what will happen if I set it to "No"...will it be switched of for just my workspace or for the whole APEX instance? To me it seems it should be an "Administration" kind of functionality - so instance wide. In the "Help" it says: "This attribute controls if Application Express should check if updates are available for Oracle Application Express and the Oracle Application Express Listener. Note: To perform this check Application Express transmits the version number of Application Express and other system components to Oracle Corporation." This seems like a nice functionality to get a sort of alert if there is a patch available. I don't know if you need a Metalink account to enable this feature.
The second one is a "Set Screen Reader Mode On" link at the bottom. If you click that a SET_SESSION_SCREEN_READER_ON is added to the URL of the Builder. I assume that this means that all HTML rendered can be read by a screen reader like JAWS to enhance the accessibility of APEX for visually impaired developers.
I inspected the HTML source of that page before and after that setting and it seems that nothing has changed. Maybe because all rendered HTML is already "screen reader ready"?
Next to these things there are a lot of new features in APEX 4.0. Check out the New Features Application to see a dozen of nice examples. Also check out the Learn More About Oracle Application Express application - which seems a Websheets application to me....

Comments

Patrick Wolf said…
Hi Roel,

you don't need a Metalink account for the version check, but you might need one to download the patchset if you don't want to install the full version.

The switch is on developer level, because it's planned to have more "online" features like new plug-ins,... in future version of APEX.

Regards
Patrick
6:24 pm
Anthony Rayner said…
Hi Roel,

Regarding screen reader mode, this is designed to optimise the usabality of both the APEX development environment and your own applications (if you choose to provision it) for the screen reader user. Note: It will not solve all the issues with what we generate, details of which will be documented in our release notes.

This feature will be documented fully in the 'Advanced Programming Techniques' chapter of the user guide, but basically it has a number of built-in features (such as rendering Flash Charts 5 in a report format, adding 'legend' tags to radios and checkboxes, making IRR's WAI-ARIA 'Live Regions' so the user is notified of the Ajax update and a few more) and is also extensible via a set of APIs (so you can control your own components).

Anthony.
10:19 am
Roel said…
Thanks for filling in the details and the explanation guys!
10:22 am
Post a Comment

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good o...
1 comment
Read more

apex_application.g_f0x array processing in Oracle 12

By
If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for ...
Post a Comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function ...
Post a Comment
Read more