Skip to main content

ODTUG Kaleidoscope 2008 : APEX rules!

Image
By
In a couple of weeks ODTUG's Kaleidscope 2008 takes off. This years theme seems to be: APEX, APEX and again..APEX. At least, for me it is. Because my preliminary schedule is packed with 24(!) APEX sessions in 5 days. So at Thursday afternoon I should know everything I always wanted to know about APEX, but were afraid to ask.
I'm looking forward visiting New Orleans and meet again some friends from the Oracle blogosphere. I will report back my findings here!

So here's the schedule:

































DateFrom To Title Presenter
Sunday 9:00 10:00 Managing the Army's Enterprise Real Property Planning with Oracle APEX Bharat Pappu and Brian Duffy

 10:00 11:00 Creating Dynamite Applications that Deliver Kathy Hunsicker

 11:15 12:15 Oracle Application Express: Power to the People Rich Mutell, Dimitri Gielis, John Scott

 13:00 14:00 How IntelliReal used Oracle Application Express to Rapidly Build their Production Environment Chris Ostrowski

 14:00 15:00 Mastering Unreasonable Deadlines with APEX at the German Telecom Shops Dietmar Aust

 15:15 16:15 How Iron Mountain Has Used APEX to Improve Operational Abilities Within the Enterprise Chris Veenstra

 16:15 17:15 APEX Roundtable With Panel of Presenters Moderated by Scott Spendolini

 18:00 19:30 Welcome Reception and Jam Session
Monday 10:30 12:00 APEX Hints, Tips, and Best Practices John Scott

 13:15 14:15 The Top 10 - No 11 - New Features of Oracle Database 11g Tom Kyte

 14:30 15:30 Forms Migration to Java ADF Rohit Bhalla

 16:00 17:00 Use the Power of APEX Dictionary Views to Increase the Quality of Your APEX Applications Karen Van Hellemont

 17:15 18:15 Oracle Application Express (APEX) Version 3.1 David Peake
Tuesday 8:00 9:00 APEX Development: Watch It Live Bill Holtzman

 9:15 10:15 You Can't Do THAT in a Browser! Extending Oracle APEX with Third Party Components Scott Spendolini

 10:30 11:30 Advanced Oracle Application Express Tips and Techniques Chris Ostrowski

 12:45 13:45 APEX Experts Panel (SIG) Scott Spendolini

 14:00 15:00 Application Express in Support of Institutional Strategic Planning Tanya Podchiyska

 15:15 16:45 Writing a Custom Authentication Scheme for Application Express: A Case Study Raj Mattamal

 17:00 18:00 Explore and Benefit the APEX Repository Michiel Jonkers

 18:00 19:30 Meet the Oracle Ace Directors and Oracle Aces Reception
Wednesday 8:00 9:00 Creating Dynamite Applications in Application Express that Deliver Kathy Hunsicker

 9:15 10:15 Building Advanced Tabular Forms Marcie Young

 10:30 11:30 Creating Advanced Charts in Oracle Application Express Dimitri Gielis

 13:30 14:30 Increase Your Oracle APEX Development Productivity with Open Source Tools Patrick Wolf

 14:45 15:45 How to Hack an Oracle Application Express Application Anton Nielsen

 16:00 17:00 Building the New Stuff: AJAX, JSON, and APEX 3.1 Carl Backstrom

 18:30 21:30 New Orleans Party
Thursday 8:30 12:00 APEX Versus ADF Lucas Jellema, Dimitri Gielis
Labels:

Comments

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