Forms-APEX workflow

Forms-APEX Workflow is a ready made APEX application and library for Forms. The toolset allows Forms based legacy systems to be extended and integrated with APEX – without changing a single line of code. The added value is the seamless integration between the browserless Forms application (FSAL) and the browser-based web application in APEX. The integration is based on the websocketJSI , a new javascript interface that was first released together with Forms R. This extends the Forms application with APEX functionality, including navigation, analysis and graphics. Any form can send a raiseEvent to the APEX application with APEX deep-linking, including payload (parameters) from the screen, and thus let APEX act, e.g. for reports, mobile forms etc.


SSO (Single-Sign-On). When starting the Forms-APEX workflow, a sign-on is made in APEX, and followingly inherited by Forms, which also makes a native sign-on. This requires no change in your existing Forms Application authentication model. Both the Forms and the APEX client are started automatically.

Single-sign-Off. When logging off in APEX, the Forms client is automatically logged off, or when logging off in Forms the APEX client is automatically logged off.


The Forms application is split into modules in the Forms-APEX workflow administration application. The modules are defined in a common hierarchical model, and access can be granted to a whole structure (module) and then revoked on branches (sub structures) or even on leaf’s (forms). This is done per user role. A user can have one or more roles, and the access is the summary of the roles. The forms themselves proof the authorization in the same way, if called directly.

Combining the Forms-APEX workflow component with the APEX MasterApp provides the same authorization in APEX


When navigating in APEX, as a part of the Forms-APEX workflow, and clicking on a menu entry, the Forms application responds seamlessly and instantly. You can navigate between forms in APEX and in Forms and you can navigate from APEX to APEX within an application, or between applications if combining with the APEX MasterApp.


The navigation is totally dynamic based on the summary of the user roles and automatically derived from the authorization model.

Deep linking

Any page in the Forms Application, can with the right click API, which is a part of the Forms Value-upgrade component raise an event to APEX including a payload (One or more parameters form the Forms page or application). The APEX Application will act on the event and show the information requested on the page or branch to another page or application and show the information requested.


On a production order in Forms, operations are planned. Right click and the form page and APEX will open a Gantt chart of the production order. The same could be done for a project.


On a production order in Forms, right click to APEX and show the QA notes and measurements which have been done in an APEX mobile App, even including pictures and time stamps.

Direct setup based upon version 12c – or as addon to Forms Value-upgrade

1)  A specification per App_ID/PAGE_ID, Here you list all relevant variables per page, that are able to receive parameters.

2)  A specification listed to the Forms Value-upgrade Right click API. Here you specify per defined call, which screen item(s) from the Form to pass to which application/page (ref. the illustration shown to the right).

APEX Deployment

APEX can be deployed on the same or a different server as the Forms application. It can be deployed with ORDS through WLS or ORDS through Tomcat, IIS or any other web-server certified for ORDS, which then is deployed through Apache or OHS, i.e. no further Oracle license is required.