In the first two parts of this blogpost series we covered the basics and the technique on how to provide nice/friendly/readable URLs for a public APEX Application.
In the first part of this Blogpost Series we touched some fundamentals and finally listed some options. If you haven’t read it, yet, please do now before continuing here.
The last post ended with me saying I found a way for hrURLs that works with APEX Listener, mod_plsql and EPG.
I haven’t tested the Thoth Gateway, but based on the documentation I’d say it works as well as the mod_plsql way.
When developing mobile applications with APEX 4.2 you’ll find the developer toolbar on the page bottom is missing.
This can be a little bit annoying when investigating misbehaving applications. Oracle recognizes this as Issue 14749955 with the workaround to access the toolbar functions through a desktop page…
I finally can start on a new mobile Application, for the first time using Oracle APEX 4.2.1 for a productive mobile App.
All my other mobile Applications have been built with previous Versions of APEX and my self made themes.
So apologies for writing that blogpost so late. But better late than never, right?
If you already developed some mobile Apps with APEX 4.2 you might have found the offered functionalities and templates a good start, but still with room for improvement.
So here are my ideas, maybe one or two things are picked up by the APEX Dev team and included in 4.2.2
Oracle Application Express Release 4.2.1.00.08 was released on December 14, 2012. A good oportunity to take a look behind the scenes and see what actually changed.
Having used Oracle APEX since its first appearance on the Early Adopter Platform I finally got my hands on the real thing and installed in on my test-system.
This Post tries to give you a summary of the big changes in Oracle APEX 4.2 (compared to 4.1.1) from a datamodel/view/API Point of view.