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

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
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

APEX ReadOnly Pages - The easy way

By
If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...
Post a Comment
Read more