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! 

Comments

Popular posts from this blog

How to create neatly formatted Excel documents using PL/SQL?

If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...

Stop using validations for checking constraints !

 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 ...