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!).
There are already 2 blog posts that cover the way you can add a feedback page to your application and how to access your feedback as developer.
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:
Exporting an Interactive Report in one click is possible, you don’t have to use the right menu witch can save your user 3 clicks!
To accomplish this you have make a branch to the page containing an Interactive Report and play around with your Page Request:
- HTMLD (ApEx 4.0 Only)
Although this sounds actually very nice, it becomes less nice when I try to disable the export for an Interactive Report.
Even when I disable every option for the Interactive Report, it still will allow me to download all the data when playing around with the page request.
Maybe not a critical issue but definitely something to take in account when you use a lot of Interactive Reports.
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.
This is how you set it up:
This is the result:
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.
Last Thursday (17/06) Oracle Benelux User Group, aka OBUG, organised his first APEX SIG, an initiative of Dimitri Gielis and Roel Hartman. Even though the new version of the product is not yet “in production”, the theme of the day was APEX 4.0.
We, at iAdvise, are one of the early promoters of Oracle Application Express in Belgium. Since 2006, we implemented already different solutions with APEX. Therefore, we could not be absent at this event and decided to participate and sponsor this first APEX SIG day.
Olivier Dupont and Jan Huyzentruyt gave a presentation with the title: “APEX 4.0: Feature 135, 184, 301, 315, 348 … How it was before, how it is now !“ The idea was to demonstrate some of the less spectacular new features of Apex 4.0 that (1) makes the life of the APEX developer easier and more productive and (2) allows to create more good looking, to the point web-application. Most of those features we explained by showing how it was in the “old” days, and how (easy) it is with APEX 4.0.
For everybody who could not attend the OBUG session, we published our presentation at slideshare.net:
A report of the day can also be found here.