In ApEx 4.0 you will be able to determine the “Default Error Display Location” under Shared Components/Edit Application Definition
An other nice feature of ApEx 4.0 will be the option to create tabular form validations. This will give tabular forms the only thing it missed so far, an easy way to validate the data before you try to save it.
In the previous editions you could write your own validation for a tabular form but you had to take care of the session state of the data you filled in, otherwise the date you changed would be lost if a validation was triggered.
To create a tabular form validation in ApEx 4.0 you just create a new validation and you will see that an extra option is present:
I have recently been playing with SQLdeveloper and came around an interesting feature: you can group connections in folder. This will prevent you from having a very big list of connections.
To group your connections you must do the next thing:
1. Select two or more connections
2. Press your right mouse button
3. Choose “Add To Folder” -> “New Folder”
Nothing very special but it’s a very handy feature!
The ApEx Symposium on the first day of ODTUG is over. It was a great day full of very interesting presentations. The day started with Joell Kallman presenting the keynote: Application Express: Ahead of the Curve. A very interesting and amusing presentation about the possible future of ApEx.
After Joell it was my time to present ‘APEX at Brussels Airport‘. I had a limited time slot of 30 minutes but at the end I had a good feeling about my presentation. Seeing I got several questions after the presentation, I hope I helped some people with giving them new ideas for possible technical solutions.
During the symposium I saw some very nice presentations giving all sorts of approaches for developing ApEx applications. At the end of the day there was an ApEx Panel Discussion with:
- David Peak
- Joell Kallman
- Patrick Wolf
- John Scott
Everyone (including moderator Scott Spendolini) got a chance to ask questions about ApEx with some interesting discussions following.
I’m looking forward to monday where Michael Hitchwa will be presenting Oracle Application Express 4.0.
ODTUG 2009 in Kaleidoscope is coming very close. I will be presenting: Mission Critical APEX – APEX at Brussels Airport in the category Customer Success.
The ApEx Symposium will start on Sunday 21 JUN and I will be first after the keynote of Joel Kallman.
I started to prepare quite late as I never got an answer on my abstract BUT it seemed that all mails from ODTUG for some reason came into my junk mail folder. A good reason to not just delete any message that lands into it, totally my own fault.
A colleague found my name on this website, from then on I could confirm for ODTUG.
I’m looking forward to the next sessions:
- Dietmar Aust: PDF Printing with APEX—A Cost-free Alternative
- Roel Hartman: How to Integrate APEX and Oracle Forms?
- John Scott: Increasing Scalability with Oracle Application Express
- Patrick Wolf: The Quest for the Hidden Treasure of Oracle APEX
And there are at least 10 other sessions I want to attend to, there are so many session that it is very difficult to choose from them.
See you at ODTUG!!
A nice enhancement in the new ApEx version 3.2 is that you can set autocomplete off under page security. AutoComplete in HTML forms stores information entered into INPUT_text, the next time that a user visits your Web page a list of previously used data will appear.
Go to Edit Page -> Page Attributes -> Security and you will see the new option Form Auto Complete.
The default value when creating a page is “On”, setting it to “Off” will generate autocomplete=”off” in your page FORM tag, now a user will not see a list of previously entered data anymore.
If you are planning to play the new Oracle APEX 3.2 version then be sure to checkout the new security feature Session Timeout.
Session Timeout will automatically invalidate your apex session if you use it. You can find session timeout under Shared Components -> Edit Security Attributes where you have have 2 options:
- Maximum Session Length: setting this property will allow you to define how long a user can use his session when logging in into your application, after witch the user will be forced to login again.
- Maximum Session Idle Time: Setting this property will define how many seconds a user can be idle before his/her session will be invalidated and the user will be forced to login again.
Optionally you can set a logout URL where you will redirect the user to, if the URL is an ApEx page then remeber to redirect the user to a public page.
The documentation of this new feature says that you can use three substitution items for your url: &APP_SESSION., &SESSION., and &APP_ID., although the session substitution items would probably have little value seeing the session has ended.