Skip to main content

OOW2006 - Day 0 (Sunday) : The Opening Ceremony

Image
By
For me OOW started on Sunday morning with the ODTUG Oracle Developer Suite Special Interest Group Meeting in the Hilton. In this session 2 Oracle Emps of the Forms and Designer Development Depts answered questions of the audience.

The highlights :
  • The main goals for Forms 11 are : better Application Server integration; higher interoperability (with webservices, BPEL and browser); ease of upgrade.

  • JInitiator will be replaced by (native) JVM

  • WebUtil will be a part of Forms (not a seperate utility anymore)

  • Forms PL/SQL scanner that checks the quality of the code

  • No plans for extra UI widgets

  • Oracle Applications is migrating to Forms 10gR2, so Forms is here to stay

  • XML Publisher is the standard reporting tool in Applications (you can imagine the consequences for the future of Oracle Reports)

  • Designer 11 will not contain any new functionality, just a new version to keep up with Forms
Of course no time frame for the release has been given.

At 6:00 pm Charles Phillips had the honour of kicking of OOW with the Opening Keynote. Charles announced that the Oakland Arena will be renamed to Oracle Arena (according to the basket and ball, it had something to do with basketball....). After that Charles emphasized that all Applications (EBS, JD Edwards, Peoplesoft etc), will be supported and extended "unlimited", next to Fusion. Then he announced - and even live demo'ed! - Oracle Accelerate, a tool to simplify the setup for your Oracle Apps instance, just by answering a few questions.

At 7:00 the first party of OOW started: The Welcome Reception in the tents on Howard Street.

Comments

Post a Comment

Popular posts from this blog

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

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