Skip to main content

Sunday's APEX Symposium ... from A to X (or Z)

By
This morning I started with an early walk to the zoo. With the idea in mind that it might be not so hot around 8 or 9 AM. But that was wrong... Even at that time of day it is hot. The temperature would rise to a 37 C this day!
But the zoo is very worthwhile. Not that I have seen all of it, because the whole track is about 15 kilometers... I especially went to see the Giant Panda's. Never seen them before, but they are just as cute and adorable as you would expect. After the zoo I went to the National Cathedral, one of the biggest churches in the US. I thing it is a sort of copy of the St. Peter in Rome - and I heard that Darth Vader is on one of the colored glass windows (didn't see it though). Beautiful church with a number of "Dan Brown" style crypts below.
Around 10:30 I got back to the conference to pick up on the ongoing APEX Symposium. At that moment Dan McGhan was talking about Dynamic Actions and PlugIns. Especially his "recurring event" PlugIn is rather cool. Next in line was Doug Gault, talking about performance. Takeaway: Think about the number of rows you'll return, the pagination style of the reports and the sorting options you offer, because those might have a performance penalty!
After a (good!) lunch Scott Spendolini showed how to create a neat user interface. Just start from scratch and keep your templates as clean and minimal as you need. Only that way you will create an applications that conforms to the look-and-feel. All the styling should be done by CSS, only define the structure (based on DIVs) in the template. Dietmar Aust was next about printing with Jasper Reports. You can use Jasper as a cheap (as in free) alternative to BI Publisher. It is not as easy as BIP, but hey, everything has it's price!.
Then Anton Nielsen talked about security. One good tip was that you should secure (set an authorization on) your Page Processes and Pages before you do that on the buttons and links that call these processes and pages. If you do it in that order you lower the risk of forgetting something. Another nice tip was, if you use your own authentication scheme, append the login name to the hash string when hashing the password. When you do that, even two people with the same password will get a different hashed password!
Last one of the day was Francis Mignault about Globalization. One good tip if you use this functionality: if you move from one instance to another (from Dev to Test), you only move the Primary Application and reseed the translated applications from there. If you should export and import the translated applications the link between the Primary app and the translated ones is lost and it will get difficult to manage change.
All in all a very interesting day with a good crowd: around 250 people were present during the day!
After the sessions there was the Speaker and Ambassador meeting (with drinks and food), right after that the Welcome reception (more drinks and food) and later the ACE Dinner (even more drinks and food) at a lovely location at the Potomac river.
Conclusion: It has been a good day, and the conference haven't even started yet (officially)...
Location: Woodley Park, DC, USA

Comments

Stew said…
Wish I was there! Thanks for letting us know some of the cool stuff we missed. Glad you're enjoying yourself outside the conference too, but anyone who's been to DC before could have told you it's brutal in the summer, mostly because of the humidity.

Enjoy! Don't forget to visit the Smithsonian, so much to see there!
5:03 pm
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