Skip to main content

Abstracts accepted for IOUG Collaborate and ODTUG Kaleidoscope

By
Last Friday I received a mail from IOUG Collaborate telling me my abstracts were accepted. It will be my first Collaborate attendance (and my first visit to Las Vegas), so I am very honored by that!
I will do the next two presentations there:

It's great to integrate: Integrating Oracle Forms within Oracle Application Express.
Since the release of version 3.2, the Oracle Forms migration toolkit is part of Oracle Application Express. This toolkit is not a silver bullet, so for complex Forms, labor-intensive adjustments in APEX will be necessary. To preserve investments in Oracle Forms and to prevent large re-investments in APEX, it is an advantage if you fully integrate existing Oracle Forms within Oracle Application Express.
In this session you will learn how to integrate existing Oracle Forms in Oracle Application Express pages and how you can make these two technologies communicate with each other.

Tales from a Parallel Universe: Using 11gR2’s Edition Based Redefinitions (in APEX).

Of all of the new features that are included in version 11gR2 of the Oracle Database, Edition Based Redefinitions could be the one that has the highest impact on the way we develop database centric applications. With Edition Based Redefinitions you can have multiple versions of the same object in your database schema in order to support multiple releases of an application at a time.
In this session you will learn what Edition Based Redefinitions are, how to use them and how this new functionality could change the way you look at your application development lifecycle.
In this presentation there will be lots of demos, to show the potentiality in an APEX environment.

A couple of hours later I received a similar mail from ODTUG Kaleidoscope that one of the abstracts I submitted was also accepted! The one I'll do in Washington is:

Creating sub-zero dashboard plugin for APEX with Google Visualizations

APEX is cool, Google is cool, Google Visualizations are even cooler. So the combination the coolest technologies available must be sub-zero.
Using the new APEX 4.0 plug-in features I will show how to create dashboards - with charts not native available in APEX - using Google Visualizations.

So I hope to see you all in either Vegas or Washington (or both!). In the meantime I have some time (and need it!) to create the presentations - 2 out of 3, because I already did the first one a couple of times - and white papers....

Comments

Patrick Wolf said…
Roel, you are brave to have a plug-in presentation without having ever looked at the product! But you should be able to do it soon ;-)
9:42 pm
Roel said…
I have seen some demo's and think it should (must) be possible. And sometimes you have to do something new. Especially when a call for papers is half a year in advance...
9:27 am
Post a Comment

Popular posts from this blog

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

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

Refresh selected row(s) in an Interactive Grid

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