Skip to main content

UKOUG Day 2

Image
By
After yesterdays Blogger Meetup it was hard to start the day...
The first session of the day was Sue Harper's talk on SQL Developer Latest Features. She mainly focussed on the new / enhanced features of version 1.5, that will be production somewhere (early?) 2008. To name some new features : external authentication (OPS$ users), browsing queues and Java, schema differences and schema copy, recall filters and a flashback query tab, formatter enhancements, your own code templates and drill down reports. With very new version SQL Developer looks more like the current TOAD version ;-).

After that I visited a session about Building Rich UI with APEX and AJAX. It was pretty impressive what you can do with a combination of APEX and AJAX (look at ajaxpatterns.org. The presenter also showed the use of widgets of the jQuery UI library like an accordion and a fancy date picker (jquery.com).

The next session about the Roadmap for legacy system migration I chaired. A solution for the upgrade to Designer / Developer 10g was presented that can' t compete with our Famous solution! The most interesting part of this presentation was the use of Dataload Classic (dataload.net) for playback testing (recording actions in the old forms, playing it back in the new ones).

After that one I went to see Grant Ronald on AJAX UI Development with JSF and ADF Faces. The good news is that we don't have to worry about the (complicated) AJAX stuff, because it's all hidden after the new ADF Faces Rich Client UI objects. And they look really great : Accordions, drag and drop etc.

Next on the program was a session on Rules Manager and Expression Filter: a way to let Oracle watch for incoming data conforming a specific where clause. You can use this feature for information distribution or workflow. Sadly to say that it needs a lot of difficult steps to set up.

Last but not least was Steven Davelaar (again chaired by me) enthousiastic as ever telling en demoing JHeadstart. He showed the new (version 10.1.3) features on Security, Dynamic Menu's, Multi Language Support and Flexible Items. The most impressive news is that also for JHeadstart Oracle is working on a Release 11 version - with all the beautiful AJAX features.... As allways it was hard to keep him to the time schedule ;-).

And now off to the ' community focus pubs' .

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