KScope19 - Future of APEX

-



I’m currently attending the annual ODTUG conference, KScope 19, this year organized in Seattle, Washington.

Traditionally the Sunday Symposiums, the first day of this 5 day conference, are provided by the Oracle Development teams, presenting the latest and upcoming features of their products. Naturally I went to join the APEX symposium and this is a brief summary of subjects and features that I consider worth mentioning.

LOV on Steroids

19.2 will introduce a new and revamped Popup LOV component. The functionality will be hugely enhanced with features we were only used to get from plug-ins like Select2 (who does not use this?!). With 19.2 we will have all the features:
  • Display Popup as Modal or Inline (Combo-Bob like), the modal flavor is resizable
  • Display Multiple Columns
  • Search, in multiple columns, fully configurable
  • Sorting, presorted and user enabled
  • Automatic/manual initial fetch
  • Select multiple values (like a tag list)
  • Add new values
  • Search as you type (configurable)
  • Configurable height and width
  • Additional output to other form fields/items
  • keyboard navigable
  • different data source flavors: local table/view/SQL/PLSQL returning SQL, REST Enabled SQL or Web Source





Join the Dark Mode

A new feature in 19.1 was the Dark Mode UI for the Builder. In 19.2 a Dark Mode Theme Style will be included in the upgrade. Combined with the functionality that enables the end-user to switch theme, you can provide an application that has this modern functionality that let’s your customers and colleagues work day AND night!

More Bulk Edit

In 19.2 it will be possible to bulk edit more attributes, like the larger text fields that would open the pop-up editor and Template Options. Being able to modify multiple Template Options in one go is something that will not only save time, but is definitely reduce the annoyance of repetitive work if you have to consistently make changes to similar components.

No wobbling Spinner anymore

I noticed that in 19.2 the processing spinner has been replaced with a spinning circle. And where the current “old” spinner wobbles a bit out-of-center, the new one is nicely smooth. Sometimes it’s the small things that make all the difference

Comments

Post a Comment

Popular posts from this blog

Remember Me - APEX Autologin

-
Image
I promised to publish about this subject to one of the attendees during my presentation at KScope 12 in San Antonio. I used this functionality in my demo application ( FifApex ) and it seems there is interest in how to do this. Most of the public websites like Facebook, LinkedIn, Twitter, Amazon or OTN do have it: an option to stay logged in, even if you closed the browser, so you do not have to authenticate each time you visit the site again. I’m pretty used to it and would be surprised if a website didn’t offer this convenient feature. OK, it’s not entirely secure, but, as I said, very convenient. I’m working on a “consumer” site/application, I’m building it with APEX and I want to offer this “remember me” option too. I knew an APEX based website that does offer this feature ( www.plsqlchallenge.com ) and I had a chat with the developer that implemented it’s login mechanism, Paul Broughton from Apex Evangelists . So, here my thanks to him for the original inspiration.   Oracle
Read more

Tabular Forms on Complex Views - using INSTEAD OF Triggers

-
Image
Creating tabular forms in Apex is relative straight forward. One gets fully generated, instant insert/update/delete functionality. Unfortunately (for the form developer), tables are usually part of a more or less complex data model, which is optimized for data storage, rather then for form-layout. Well, Apex offers some possibilities to the developer to enable tabular forms beyond 1:1 table based. Collections One alternative is to create your tabular form using the Apex Collection API. There is a good article on Martin Giffy D'Souza’s blog describing this technique. This collection-approach basically pre-fetches data into a (PL/SQL) collection from a query/cursor. The “collected” data will be displayed in the form. An on-submit page process will store the data submitted from the form into the collection. After this you can perform some validation before submitting the data to table(s) in an on-submit page process. Database Views Well, I favor an approach that keeps the
Read more

"Who are you?" – client device Categorizr for APEX

-
Image
This article describes a solution to determine the client device category (i.e. desktop, browser or tablet) your APEX application is accessed from. Until recently, building a web application with Oracle Application Express usually meant to build a desktop browser application. But if you look at the growing number of mobile devices, this will change very soon, if not already has for some of you. Being able to develop applications, that can be accessed by tablets or smart phones offers lots of new possibilities. But it also comes with some challenges. Mobile devices are different. Interaction by touch screen, screen size and (non-) support of certain common web functionality (flash, for example), just to mention a few. Oracles announcement to integrate the jQuery mobile framework into APEX 4.2 will help us to deal with many of the challenges, developing for multiple devices will bring. Until now, one of the biggest challenges is, to determine the actual client your application
Read more