16 Understanding External Forms (Release 9.2.1)

This chapter contains the following topics:

16.1 External Forms Overview

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

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.

16.2 External Form Properties

The external form supports the following properties:

  • External Application Type

  • External Application

  • Entry Point

16.2.1 External Application Type Property

Choose the external application type from the drop-down menu. The valid values are:

  • JavaScript - This is a classic EnterpriseOne page or an EnterpriseOne page created with Oracle JavaScript Extension Toolkit (JET). Other javascript libraries may also be used, but JET libraries are provided within EnterpriseOne specifically for use in EnterpriseOne pages.

  • Adf - This is an ADF bounded task flow.

  • Composed Page - This is a Composed EnterpriseOne Page.

Note:

If using JavaScript or Composed Page application types, you must have created these User Defined Objects (UDOs) first so that you have the unique ID to enter in the External Application field.

Also, you must share the page in order for other users to see it. However, you do not need to enable view security for others to see it. Application security is used instead to control who can run and view the external application.

16.2.2 External Application Property

This section discusses valid values for the External Application field.

16.2.2.1 JavaScript

If the external application type is JavaScript, enter the object name of the UDO in the External Application field.

You can find the JET (JavaScript) object name by following these steps:

  1. On the EnterpriseOne screen, click the user personal information located on the right side of the banner bar at the top.

  2. Under the Personalization category, click the Manage Content link, then click Classic Pages.

  3. Select the name of the Classic Page that represents your JET object and click the information icon.

    The About form displays the EnterpriseOne Page information including the Object Name. You can copy the Object Name from here.

You can also look up the object name in P98220W.

16.2.2.3 Composed EnterpriseOne Page

If the external application type is Composed Page, enter the object name of the UDO in the External Application field.

You can find the Composed EnterpriseOne Page object name by following these steps:

  1. On the EnterpriseOne screen, click the user personal information located on the right side of the banner bar at the top.

  2. Under the Personalization category, click the Manage Content link, then click Composed Pages.

  3. Select the name of the Composed EnterpriseOne Page that you are looking for and click the information icon.

    The About form displays the Composed EnterpriseOne Page information including the Object Name. You can copy the Object Name from here.

    You can also look up the object name in P98220W.

Note:

Be very careful when entering the external application value as there is no immediate error checking. This field will allow any value and you will not receive an error if the external application does not exist or is mis-typed.

16.2.3 Entry Point Property

External forms can be entry forms. Entry point is an option which, when selected, flags the form as being the one that you want users to see when they first launch the application.

If the form is flagged as an entry point, you can access it directly through FastPath and place it on a menu using only the application name.

Once these forms are configured properly, these forms can be used across EnterpriseOne as normal forms can be, with Form Interconnects, FastPath, and so forth.

16.3 Data Structures

You can define a form data structure for external forms. External form types of JavaScript and ADF both support passing data into the external application via the data structure. Currently, you can only send data into the external form, you cannot receive data values back.

For more information regarding ADF, see Consuming Form Interconnect Values in the JD Edwards EnterpriseOne Tools Deploying and Developing Oracle Application Development Framework (ADF) Applications for EnterpriseOne Guide.

For more information regarding JET, see Consuming Form Interconnect Values in the JD Edwards EnterpriseOne Tools UX One Deployment and Development Guide