Skip to main content

Oracle Application Express Forms Converter Book - Review

As I promised earlier I should write a review of the Oracle Application Express Forms Converter book by Douwe Pieter van den Bos. I finally found the time to work it through...it doesn't take that much time, because it is "just" 150 pages thick (or thin).
The book contains 8 chapters, in which the reader is guided through an Forms2APEX conversion project from start to finish. It starts of with "Understanding your Project" (1), wherein understanding the reasons for conversion as well as the functionality of the Forms application is stressed as important, because these will influence the way you'll solve things in the APEX application. One or more examples should have been useful here.
The next chapter, "Preparing your Forms Conversion" (2), covers the creation of XML files from the source files. BTW, not only Forms, also "Reports" are - briefly - touched (and can be converted as well). Also different ways of creating a target database are mentioned (but IMHO you usually can just re-use your current Forms development environment).
Chapter (3), "Create your Forms Conversion Project", covers the next step in the project: uploading the XML files and understanding the Project Overview Page.
The next chapter is about "Planning your Project" (4). It shows how you can dive into the different components (blocks, triggers and what's not), and how to use the Annotations, Tags, Assignments and Applicablity to estimate the work you've done and still have to do. That last one is rather difficult, because only the number of objects-to-do are counted - and, as we all know - that doesn't tell you everything about the time needed to accomplish things. But it might help you in planning and monitoring the project.
Chapter (5), "Getting your Logic Right!", is probably the key-chapter of the book. The difference between Original, Enhanced and Custom Query is explained in detail. Alas one line "Implementing the business logic is done post-generation, execpt for some Post-Query triggers" says it all... I now the conversion utlity is not a silver bullet, but some examples on how to convert Forms logic to the APEX equivalent would have been a very useful add-on!
Chapter (6) covers "Generating your Application", and doesn't tell anything new if you're already an APEX Developer (actually there is nothing more to tell about it than what covered here).
"Reviewing and Customizing your Application" is the penultimate chapter (7). It handles tweaking the generated LOV's, Titles and how to create a Validation based on what was an WHEN-VALIDATE-RECORD trigger in the Form.
The last chapter (8), on "Delivering your Application", discusses (very briefly) how to create an Application Export and import that in a Test-, Acceptance or Production environment. No specific Forms2APEX stuff.

All in all it is a good book when you need an overview of the steps you have to take for converting an Oracle Forms application to APEX - more on a Project Management level than a Developer level. If you really need to get your hands dirty and do the actual conversion yourself, this book is just the beginning of a great adventure...
Post a Comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…

Using LDAP for Authentication and Authorization within APEX

One of my current customers would like to use their LDAP (Microsoft Active Directory) server for authentication and authorization of APEX applications. Of course we tried to set up a standard LDAP Authenication that's available within APEX. But we couldn't get that to work. Maybe it has to do with the fact that the client stored their Users within Groups within Groups within .... . Or maybe it doesn't do a full tree walk in the directory. Or maybe it is just because it is Microsoft - and not Oracle Internet Directory (OID). So we moved to a custom Authentication using the DBMS_LDAP functions (and some examples from the Pro Oracle Application Express book and Tim Hall - a.k.a. Oracle Base).

One of the issues we encountered that we wanted to use the user's login name, like "jdoe" and not his full name ("John Doe"). And the login name is stored in the "sAMAccountName" attribute. But authenticating using just "jdoe" didn't work. …