About a year ago I asked a question about cloning Oracle Databases in the APEX section of the Oracle Community. The question is here (no need to click the link, all of the content is also in this blog post):
I haven't received much traction, so I'm reformulating it as a recommendation. Perhaps I'll get more feedback in this form. I'll also point out an element I think is a bug in APEX...you'll have to read to the end to see that.
I've known Mark, a technical pre-sales consultant at Oracle, for a number of years. I was bcc'd on the farewell email message that he sent out today, his last working day at Oracle. As he said, he's learned a few things over his past 20 years at Oracle and thought he would share them. They were quite simple and powerful reminders - and important enough that I shared them with our entire development and QA teams.
In the last two years I've been using JSON in almost every project I was involved in. For example with APEX Office Print our plugin is sending JSON to the backend. This JSON you can actually see yourself in the Remote Debug screen in your AOP Dashboard.
Since the genesis of Oracle Application Express, customers have asked for a way to open multiple browser tabs (or windows) of an APEX application and have the session state isolated between the respective tabs. There is one and only one APEX session associated with a client, and because of this behavior in APEX, customers would find that the session state manipulated in one browser tab would collide with the session state of the other browser tab.