Skip to main content

Collaborate 2011 - Day 3

By
Day 3 started out with a 8 AM (!) presentation on Mobile Application Development. Didn't cover any APEX specific details, more about the general things to consider when developing these kinds of apps. Like how to handle multiple platforms, like IOS and Android - and over 10 others. Native apps are preferred above browser apps (and any APEX app will be a browser app). The solution for handling all these different platforms is to use a framework (like jQuery Mobile). For data integration, you should use webservices in order to keep the bandwith usage as small as possible.
The next session had the (lomg) title Enhancing your Data Warehouse Data Completeness using APEX. The presenter showed a (very simple) application to authorize and monitor Excel uploads and changes made to the master data of a data warehouse. Nothing very new...
Then David Peake presented on APEX integrating with E-Business Suite. Since v12, EBS doesn't support mod-plsql extensions anymore. But, luckily, there is a solution for that. You have to run EBS 12.1.3 and an additional patch, but then you're there.Recommended is you should set up a separate webserver and listener for APEX (using Glassfish and APEX Listener), and not use the APPS scheme for the workspace, but create a separate one with access to only the APPS objects needed for the customizations. All the details are in this whitepaper.
Last before lunch, there was a 30 minute session about APEX for DBA's. The message here was to kill all the spreadsheets and bring them over to APEX. Isn't always easy, but still worthwhile. The funny thing is, once the spreadsheet is turned into an Interactive Report, users downloaded that one again...in Excel..sigh.
Then there was a 3 hour break. Meant to spend time in the exhibition hall, but I thought the pool was a better place to be!
After that, I attended the session Developing Multi-client applications with APEX. In the presented solution multiple applications existed that are used by multiple clients - without seeing eachothers data. One master table (with the "client" info) was the parent to all tables - or the grandparent. And add an addtional line to the where clause of all queries. (I would have implemented the "client-id" in all tables to make it easier and use the VPD-properties built into APEX). Some smart customization stuff though: Using replacement strings (like &XYZ.) for customizing Tab labels, URL's and even colors and region widths in the templates!
Last session of today was the APEX Panel. Together with Scott Spendolini and David Peake, we tried to answer the questions from the audience. Good questions came up and we even ran 15 minutes out of time.
After the exhibition hall drinks, I attended the traditional ACE dinner. Good food and pleasant company!
Labels:
Location: Orlando, FL, USA

Comments

oraclenerd said…
re: Browser vs. Native

One I found a few months ago that is browser based from my Android (htc Incredible) is Untappd, a social site for beer drinkers!

I like that they didn't go native and stuck with the browser user, they may/might/probably use something like jQuery, but it's pretty slick from the phone.

Sorry I couldn't make it up, was hoping to be able to give you a hard time in person. :)
6:05 am
Post a Comment

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ
1 comment
Read more

apex_application.g_f0x array processing in Oracle 12

By
If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for
Post a Comment
Read more

Stop using validations for checking constraints !

By
 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
Post a Comment
Read more