Skip to main content

A review of APEX World 2017 - Day 2

(You can read my impression of the first day here)
After a short but good night sleep and an excellent breakfast, Mike Hichwa delivered his second keynote "RAD Challenge: Build a Real World application in 60 minutes”. Although he suffered from connection issues, Mike managed to wow the audience showing the new packaged app "Quick SQL” and  the new (currently Cloud-only) “Blueprint” option to create a new application. As JSON is not code (but just a collection of value-attribute pairs), it was really a no-code showcase!

Then it was parallel session time again and I went to see how Christian Rokitta would "Bootstrapify Universal Theme”. The message is: You don’t have to unsubscribe from the Universal Theme (and please don’t!) to create an application that looks totally different from the “regular” APEX applications.

Then I had to deliver my second presentation “Docker for Dummies”. It was aimed at people who might have heard of Docker but really have hardly a clue what it is - and what the benefits are. I received really good feedback on this session and quite a lot of additional questions afterwards. So it seems I did made people curious and enthousiast about Docker. Mission completed! 

During another excellent lunch, we could still enjoy the beautiful weather and the Rotterdam skyline. It was good to spend some time outside in the fresh air.

Then the last part of the event started. Dimitri kicked it off with “Moving my APEX app to the Exadata Express Cloud. Live!”. He explained the differences in (some of) the cloud offerings Oracle has and how you can move your application and data from your local instance into the Exadata Express Cloud. As Mike explained during his keynote on the first day, EECS will get better: more workspaces, really “Cloud first”, optional upgrading (after APEX 5.1), a local datacenter etc. Oh, yes, and a free subscription to the Oracle Developer Cloud Service as well!

The last regular session I attended was “Forms to APEX” by Sergei Martens. The APEX pages he showed were impressive. So different than anything else and enriched with numerous cool features. I especially liked the “Outlook style” interface because it is so close to what a user is used to, he/she can start using that application right away without any training whatsoever. The presentation could even be better if he had shown the original Forms screens as a reference ...

And finally, at the last keynote, Shakeeb could do his “The Center of the Universal Theme” presentation. Of course the presentation wasn’t just good looking - it had good content as well and I really like Shakeeb’s presentation style (as do a lot of other people I heard afterwards). 

As a “goodbye” we were offered some drinks and snacks and then it was time to go home. 

Next year APEX World 2018 it will probably be on the same wonderful location. I am already looking forward to it and i encourage everyone who is interested in APEX to attend! 
Post a Comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…

Using LDAP for Authentication and Authorization within APEX

One of my current customers would like to use their LDAP (Microsoft Active Directory) server for authentication and authorization of APEX applications. Of course we tried to set up a standard LDAP Authenication that's available within APEX. But we couldn't get that to work. Maybe it has to do with the fact that the client stored their Users within Groups within Groups within .... . Or maybe it doesn't do a full tree walk in the directory. Or maybe it is just because it is Microsoft - and not Oracle Internet Directory (OID). So we moved to a custom Authentication using the DBMS_LDAP functions (and some examples from the Pro Oracle Application Express book and Tim Hall - a.k.a. Oracle Base).

One of the issues we encountered that we wanted to use the user's login name, like "jdoe" and not his full name ("John Doe"). And the login name is stored in the "sAMAccountName" attribute. But authenticating using just "jdoe" didn't work. …