Skip to main content

Integrate Oracle Forms with APEX

APEX 3.2 will contain functionality to migrate Oracle Forms to APEX. I am one of the (about) 10 lucky people that take part in testing the Limited Early Adopter release, so I know what it can and cannot do (I will blog about that later).
In 2007 Wilfred van der Deijl did a presentation at ODTUG about the integration of Oracle Forms with JSF, JSP and ADF Faces. This eventually resulted in a product OraFormsFaces. The technique he used is elaboratly described in this Step-by-step guide.
So I thought: Why not try to copy this technique and do this also in APEX?

So first I created a simple form showing Orders (all is based on the HR scheme). The second step is to incorporate this Form in an APEX region. So I created a page and within that page a PL/SQL region. The region source is a call to a database procedure APEX$CALL_FORM. This procedure has a couple of arguments, like formname, username and password. This procedure simply uses htp.p to put out the same tags that are used to show a form the regular way (I used Firebug to grab that code) and uses the parameters to replace the formname etc.

The result is:

This is showing a Form within an APEX region. The form is embedded in two DIV's: An 'innerdiv' and an 'outerdiv'.
Next was to apply some style attributes to the div's and the applet itself to keep the menu, buttons and scrollbar out of sight. I used the width and height settings to eliminate the scrollbars and negative margin settings to clip all unwanted content.

The result of that excercise looks like this:
You can hardly tell that this is an Oracle Form (especially because I used similar visual attributes as the APEX theme).

The next step was to use this form as a master for a (detail) APEX region: Order Items. Just above the Order Items region I created a dummy region that contains the Order Id for which the Order Items should appear in the report. In the HTML Form Elements Attributes of the Order Id I entered a piece of javascript (onchange="javascript:refresh_region(this);") that would refresh the Order Item region on a change of the Order Id (therefore the function refresh_region does a call to html_PPR_Report_Page).

So far so good. When navigating through the form the Order Id should be updated (and automagically the Order Items get updated as well). So I added a WHEN-NEW-RECORD-INSTANCE to the Order Block in the form with just one simple call:
 web.show_document('javascript:$s("P1_ORDER_ID",'||:DEMO_ORDERS.ORDER_ID ||')', _self');
This sets the (APEX) P1_ORDER_ID to the current Order Id in the form. And this works magnificent!
The final step is to use the Oracle Form as a detail to an APEX region as well (so a master-detail-detail page). Therefore I copied the 'CommunicatorBean' java code from Wilfred's guide and deployed that on my Forms Server (it took somewhat longer than just these two lines, but I won't go in to that ;-) ). I also added a CommunicatorBean-item to my form and added the following code in the WHEN-CUSTOM-ITEM-EVENT triger on that item.

declare
BeanEventDetails ParamList;
ParamType number := text_parameter;
Event varchar2(1000);
Payload varchar2(1000);
begin
BeanEventDetails := get_parameter_list(:system.custom_item_event_parameters);
get_parameter_attr(BeanEventDetails, 'Event', ParamType, Event);
get_parameter_attr(BeanEventDetails, 'Payload', ParamType, Payload);
if event='do_key'
then
message('About to '||payload);
do_key(payload);
end if;
if event='execute_query'
then
set_block_property('DEMO_ORDERS', DEFAULT_WHERE, 'WHERE CUSTOMER_ID = '||payload);
execute_query;
end if;
end;


Then I created a master region (Interactive Report on Customers) and on the column Customer ID a link:
javascript:setFormItem(#CUSTOMER_ID#);
and this function does nothing more than :
 document.formsapplet.raiseEvent('execute_query', pCustId ); 
And now, when I click on a Customer Id, the Form immediately shows the Orders for that customer and the Order Items are synchronized with the Order in the Form.
So it is possible to integrate your existing Forms with an APEX application, making a smooth transition possible.
I have submitted an abstract for ODTUG on this subject, so if it is selected I can show you this (and more!) live...
Last but certainly not least, many thanks to Wilfred for sharing his knowledge on the web!
13 comments

Popular posts from this blog

Refresh selected row(s) in an Interactive Grid

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 worse) while you…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one:
then you disable the "Escape special characters" property and the result is an updatable multirecord form.
That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for processing y…