External Forms Overview

An external form is the window through which users interact with an external application like an ADF application, a JET page, a Composed EnterpriseOne Page, or a Soft Coding Reference.

Starting with Release 9.2.6, you can create and edit external forms from within the EnterpriseOne web client.

The principle value of an external form is that it provides a direct link to an external application and allows it to be displayed within an EnterpriseOne web client. This means it can be a task, within a Composed EnterpriseOne Page, on a menu, linked to from an EnterpriseOne page, or accessed through FastPath.

Note: With Release 9.2.1.4, you can also use a modal form interconnect or Shortcut Launcher to launch external applications. However, you cannot use Shortcut Launcher to open external forms that are ADF applications.If using Shortcut Launcher to open an external form, you can see the tasks on the form, but you cannot launch the tasks. (Release 9.2.1.4)

External forms can also be secured just like any other application. You can pass values into the external application using the data structure of the external form. You can also use static text controls on the external form, so when the external form is called using the AIS form service, those static text fields will be returned as translated labels.

Before creating your external form, you must have your external content first, whether that is an ADF application, EnterpriseOne Page/JavaScript, or Composed EnterpriseOne Page. You should also know what kind of input is expected, so you can provide the correct data structure members in the external form. Then you can create the external form in FDA for that content.

Note: You cannot add any controls or events to an external form except static text controls. This is due to the fact that an external form is just a container for the external content to be executed.