People attending Open World to have a closer look at fusion technologies and how to integrate them in your existing applications, need to check out the following session:
Title: Oracle Forms in the Middle of Middleware with Oracle Product Management
Track: Application Servers, Application Grid, and Development
Date: 22-SEP-10 Time: 13:00 – 14:00
Venue: Marriott Marquis Room: Salon 9
Together with Grant Ronald we will talk you through the possible scenario’s to modernize your existing forms applications. After each scenario we will demo the functionalities and showcase some of the success stories we’ve conducted together with our benelux customers.
The different scenario’s include upgrading to 11g to use the event-driven architecture, integrate with existing applications such as apex, .net, google maps, bpel, …
In other words if you’re using fusion technologies such as BPEL, OSB, ADF, … you can easily integrate these with your existing forms applications using the new features provided in 11g.
Team development is one of the new features of APEX 4.0, one option to use with this feature is Feedback. In short, Feedback allows users to easily report “bugs” for an application. (Like we APEX developers can program bugs… NOT!).
This blog post will describe how you would export your feedback from a production system to the development system where you as developer try to make/solve things. After changes are made you want to inform your users what has been modified…
1. Setting your environment variables
The first thing you have to check before you want to export/import feedback, is the name of your workspace. If you use the same name for a workspace in both environments then we will have to distinct the development environment from the production environment. If you don’t do this, the export/import feature for feedback will not work. You can distinct the environments by altering the Feedback Synchronization Source Identifier, this will default be the name of your workspace. Changing the identifier can be done by using the Internal workspace -> Manage Workspace -> Workspace Details -> Edit Workspace Information.
One of the big improvements of ApEx 4.0 in my opinion is the rebirth of the date picker Item. The old version of the date picker was a popup that opened a calender, it was ok but a lot of developers already used something more sexy like the jQuery Ui Datepicker. This required some custom development and was’t out of the box functionality.
In ApEx 4.0 the date picker got a new look and feel based on the jQuery Datepicker. It opens a lot faster and is overall more simple to use. You don’t have to create a validation anymore to check if the user has specified a valid date, this is done automatically.
Some new properties are available for the date picker:
When creating a new workspace you might have noticed that there will be some extra tables on your schema.
All these table start with the name APEX$_ and are used for the websheets feature of the new version of ApEx.
If you don’t use websheets (at start) and you don’t want these extra tables present on your schema then you can prevent the creation of these tables by following the next steps:
- Login into the internal workspace
- Go to Manage Instance -> Feature Configuration
- Set “Create Websheet objects in new workspaces” to No
Please keep in mind that the above action will still allow developers to make websheets. If these objects do not exist then the developer will see a warning message when he/she tries to create a websheet. You then will able to create these objects again:
If you have the Websheet Objects on your schema and you wish to remove them then go to “
Home -> Administration > Manage Service -> Websheet Database Objects” and there you can safely remove these objects.
A feature that hasn’t been highlighted much is the Quick Pick functionality with items of type “Popup LOV” and “Select List”.
This features enables you to make a quick choice from the the list values in the LOV. Only downside is that you can’t use a query or function that returns the Quick Picks. However you can still reference to other items using the &MY_ITEM. notation.
Last year on ODTUG I did a presentation where I showed my own implementation of region tabs. These are extra buttons to display regions in a more user friendly way. Suppose you have a lot of regions on your page then you could present a list of buttons, each button will show/hide a region.
I’m pleased to announce that in ApEx 4.0 you can do this declarative by using a new region type: “Region Display Selector”.
To set it up just follow these simple steps:
- First alter any existing region on your page and set the Region Display Selector to YES. You can find this setting under Region Attributes.
- Make a new region of type Region Display Selector
- You can add more regions to the display selector by setting the Region Display Selector to YES
You can see my own implementation of region tabs in the next photo gallery:
ApEx 4.0 has been released. You can download the new version of ApEx on the website of Oracle.
You can read about the new features of Application Express 4.0 here.
Please mind that the requirements are changed:
Oracle Application Express 4.0 is supported on all Editions (SE1, SE, EE, and XE) of the Oracle database, 10.2.0.3 or higher. Application Express 4.0 can also be used with Oracle Database 10g Express Edition.