Skip Headers
JD Edwards EnterpriseOne Tools Development Tools: Form Design Aid Guide
Release 8.98 Update 4

Part Number E14706-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Working with Forms

This chapter contains the following topics:

2.1 Understanding Forms

Use Oracle's JD Edwards EnterpriseOne Tools Form Design Aid (FDA) to create one or more forms for an application. A form is a graphical user interface where users interact with the system. A form can be used to search and display data, as well as enter new data and modify existing data.

A single application can contain one or more forms. Usually, a find/browse form is the first form that appears in the application. It enables the user to locate a specific record with which to work. Upon selecting a record, a subsequent form such as a fix/inspect form can be used to provide details of the record. With the introduction of power forms, applications can use one single power form to locate a specific record and display its detail records on one form.

A form has these elements:

2.2 Understanding Form Interconnections

You can call a form from a form. This kind of form interconnection falls into two categories, modal and modeless:

Modal is the default interconnection type. Modal interconnections are appropriate when you want to lead the user through a particular process in which a number of values must be input in a specific order. In this case, you want the user to completely fill out each form before moving on to the next one. Add and copy functions also lend themselves to modal processing because you want the user to complete the function before going on to others.

Modeless interconnections are valuable when the user needs to view or update a series of data records. Avoid using modeless form interconnections if both the parent and child forms should be presented to the user at the same time. A power form is more appropriate in this case.

The parent form in a modeless interconnect must be a find/browse form. The child form type can be fix/inspect or transaction forms (header and headerless detail). When the user updates a record on the transaction form, the parent find/browse form automatically reflects the change.

When the user closes the parent form, the system closes all its modeless children forms.

Parent form ER that follow a modeless form interconnection call execute immediately instead of waiting for the child form to return.

2.3 Configuring Forms at Design Time

The property settings for a form control its appearance, how it displays errors, and how it interacts with its underlying business views. When you first create a form, the system prompts you to configure its properties. You can change the properties of a form later in the design process.

Some property values are common to all form types, although many are shared by just a few. This table lists the property values for all form types. The descriptions given in some cases are for general use only. If a particular property significantly impacts a given form type, then those impacts are discussed in detail in the section devoted to that form type.

Property Form Type Description
Business View Name Find/Browse

Fix/Inspect

Header Detail

Headerless Detail

Search & Select

Parent/Child Browse

Power Edit

Power Browse

Edit Subform

Browse Subform

Edit Portlet

Browse Portlet

The BV that is attached to the form.
Data Structure All form types The data structure underlying the form that maps incoming and outgoing data.
Enable In-Your-Face-Error Display Find/Browse

Fix/Inspect

Header Detail

Headerless Detail

Search & Select

Message Form

Parent/Child Browse

Power Edit

Power Browse

An option which, when selected, displays error text in red at the top of forms displayed in Web applications. Typically, the system indicates an application error by highlighting the Errors and Warnings link in the upper right area of the application. Selecting In-Your-Face-Errors has no noticeable effect on performance.
End Form on Add Fix/Inspect

Header Detail

Headerless Detail

An option which, when selected, causes the system to close the form and return to the previous form after a user adds a record and clicks the OK button. If you want greater control over form flow, clear this option.
Entry Point Find/Browse

Header Detail

Headerless Detail

Search & Select

Message Form

Parent/Child Browse

Power Edit

Power Browse

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 you do not assign one of the forms as the entry point, the runtime engine loads the first form it finds in the application. FDA does not permit you to set more than one form as an entry point. Fix/Inspect forms cannot be used as entry points.
Fetch on Form Business View Find/Browse

Fix/Inspect

Header Detail

Search & Select

Parent/Child Browse

Edit Subform

Browse Subform

Edit Portlet

Browse Portlet

An option which, when selected, causes the system to perform fetches based on information in the business view underlying the form. This option is unavailable if the form has no business view. Even though this setting is available for all form types, it only applies to Fix/Inspect, header/detail, headerless/detail, Power Edit forms with no grids, and subforms.
Fetch on Grid Business View Find/Browse

Headerless Detail

Header Detail

Search & Select

Parent/Child

Power Edit

Power Browse

An option which, when selected, causes the system to update the grid during runtime based on information in the tables underlying the grid when the user clicks the OK button. This option is unavailable for entry unless the form contains a grid control.
Form Guide Find/Browse

Fix/Inspect

Header Detail

Headerless Detail

Search & Select

Message Form

Parent/Child Browse

Power Edit

Power Browse

The height and width in pixels to set the form guides. FDA indicates the optimum form size for different platforms by superimposing light blue lines that indicate height and width along the top and left-hand side of the form.
Form Name All form types The system name for the form. FDA names the form based on JD Edwards EnterpriseOne naming standards (forms start with W, subforms with S), the application name, and the creation sequence (the first form is appended with an A, the second with a B, and so forth). You cannot change this property.
Form Type Find/Browse

Fix/Inspect

Header Detail

Headerless Detail

Search & Select

Message Form

Parent/Child Browse

Power Edit

Power Browse

The type (find/browse, search & select, and so forth) of the current form. You cannot change this property.
Height

Width

All form types The height and width of the form in dialog units. You can change the form size by resizing it manually with the mouse or by using these properties to set the size precisely.
Mapping Links Power Edit

Power Browse

Edit Subform

Browse Subform

Edit Portlet

Browse Portlet

The mapping of data between a parent and its child subforms.
Tile Wallpaper Find/Browse

Fix/Inspect

Header Detail

Headerless Detail

Search & Select

Message Form

Parent/Child Browse

Power Edit

Power Browse

This option, when selected, displays multiple copies of the background image in a tile-like manner. If you select this option, then you cannot select the Wallpaper property. Additionally, you cannot select this property unless you have set either the Wallpaper File or the Wallpaper Full Name File property.
Title All form types The text name of the form. This name appears at the top of the form when users work with the application. By default, FDA enters the form type in this field. You should change it.
Total Controls on a Form Find/Browse

Fix/Inspect

Header Detail

Headerless Detail

Search & Select

Message Form

Parent/Child Browse

Power Edit

Power Browse

A field that shows the current number of controls (including subforms) on the selected form. You cannot change this property
Transaction Fix/Inspect

Header Detail

Headerless Detail

Power Edit

Power Browse

Edit Subform

Edit Portlet

An option which, when selected, causes runtime to commit all changes at one time instead of individually. If the form makes a single database change or a group of unrelated changes, do not enable Transaction. However, if the form has a group of inserts that rely on each other and if the system should revert to the previously committed changes if a change fails or for another condition, then select Transaction.

Transaction works differently for subforms and portlet forms.

Update on Form Business View Fix/Inspect

Header Detail

Power Edit With No Grid

Edit Subform

Edit Portlet

An option which, when selected, causes the system to update the tables underlying the form (except those underlying the grid control) during runtime when the user clicks the OK button. This option is unavailable for entry unless you have attached a BV to the form.
Update on Grid Business View Header Detail

Headerless Detail

Power Edit with Grid

An option which, when selected, causes the system to update the tables underlying the grid during runtime when the user clicks the OK button. This option is unavailable for entry unless the form contains a grid control.
Wallpaper Find/Browse

Fix/Inspect

Header Detail

Headerless Detail

Search & Select

Message Form

Parent/Child Browse

Power Edit

Power Browse

An option which, when selected, displays a single image on the form as its wallpaper. If you enable this option, then you cannot enable the Tile Wallpaper property. Additionally, you cannot select this property unless you have set either the Wallpaper File or the Wallpaper Full File Name property.
Wallpaper File Find/Browse

Fix/Inspect

Header Detail

Headerless Detail

Search & Select

Message Form

Parent/Child Browse

Power Edit

Power Browse

The name of the image to use in conjunction with the Tile Wallpaper and Wallpaper properties. Use this property if the image is in the path code for the application.
Wallpaper Full File Name Find/Browse

Fix/Inspect

Header Detail

Headerless Detail

Search & Select

Message Form

Parent/Child Browse

Power Edit

Power Browse

The name of the image to use in conjunction with the Tile Wallpaper and Wallpaper properties. Use this property if the image is not in the path code for the application.

2.4 Creating Forms

This section provides an overview of form creation and discusses how to:

2.4.1 Understanding Form Creation

Use FDA to create one or more forms that appear in an application. These forms are the visual interface for the end user of the application and enable that user to view, add, or modify data that is stored in one or more tables.

After you create the form, you can modify the system data for the form, such as its metadata, Help ID, and so forth.

2.4.1.1 Recommended FDA Configuration

FDA offers a variety of tool bars and panes that you can place on the desktop while you work. This list provides recommendations for using these objects:

  • Display the Main Toolbar, Layout, and Insert Controls tool bars at all times.

  • Use the Insert Controls tool bar to insert controls on a form.

  • Display the Application Tree View whenever possible.

    The pane helps you keep the entire application in mind, and it provides an easy way to open other objects in the application.

  • Display the Property Browser at all times and use it to set the properties for all objects.

  • Display the Tab Sequence Toolbar when working with power forms and subforms.

This table lists the objects, why you would use them, and how to display them:

Object Notes Navigation in FDA
Main Toolbar Provides standard actions such as open, cut, and paste. View, Toolbars, Main Toolbar
Layout tool bar Provides functions to align and space form controls precisely. View, Toolbars, Layout
Insert Controls tool bar enables you to place controls on a form with the push of a button. View, Toolbars, Insert Controls
Status Bar Displays a status bar at the bottom of the tool. View, Status Bar
Application Tree View Displays a pane showing the objects in the current application and their relationship to each other. Double-click an object in this pane to open it. The pane can be filtered for language. You can also configure the tree to display its hierarchy by control or by business unit. View, Application Tree View
Property Browser Displays a pane showing the properties of the selected object. You can change object properties in this pane. View, Property Browser
Data Dictionary Browser Displays a pane where you can search for data dictionary (DD) objects. You can drag and drop DD objects from this pane to the form. View, Data Dictionary Browser
Business View Columns Browser Displays a pane where you can search for columns in a BV. You can drag and drop objects from this pane to the form. View, Business View Columns Browser
Tab Sequence Toolbar enables you to manipulate the tab sequence functionality, including changing the object being sequenced on the form. View, Toolbars, Tab Sequence Toolbar

2.4.2 Creating a Form

This task provides a general overview of the typical form creation process. Many of the steps in this task are described in greater detail in other topics.

To create a form:

  1. In Oracle's JD Edwards EnterpriseOne Object Management Workbench (OMW), create an application or open an existing one, and then start FDA.

  2. On Form Design Aid, select the type of form you want to create.

  3. Configure the form properties as appropriate.

  4. If required, attach one or more BVs to the form by selecting Form, Business View, Add Business View.

    Headerless detail forms permit you to attach two BVs to them; all other forms, except for message forms, permit you to attach only one. You cannot attach a BV to a message form.

  5. Add and configure controls, as required.

    Set the Data Item Information property for a control to attach DD items or BV columns to it. To attach ER to a control, right-click the control and select Event Rules. To set text variables for a control, right-click the control and select Text Variables.

  6. Arrange the controls on the form so that they line up and are equally spaced, and then resize the form to fit.

  7. Add menu and tool bar exits to the form.

  8. Save and test the form.

2.4.3 Creating a Modal Form Interconnection

To create a modal form interconnection:

  1. On Event Rules Design, select an event.

  2. Click the Form Interconnect button.

  3. On Work with Applications, select the application to which you are connecting.

    Work with Forms displays available forms for the chosen application.

  4. Select the form to which you want to connect (the target).

  5. Select the version of the form to which you want to connect.

    The Data Item column displays data items in the data structure of the target form. The keys in the primary unique index for the primary table of the BV are automatically set up as the data structure.

  6. In the Available Objects column, select the object that you want to pass and move it to the Data Structure-Value Column.

  7. Indicate the direction of data flow between Value and Data Items.

    As you click the direction arrow, it toggles through these options:

    • Data flows from the source to the target.

    • Data flows from the target to the source.

    • Data flows from the source to the target and, upon exiting the target, data flows back to the source.

    • Upon exiting the target, data flows back to the source.

    • No data flows either way.

  8. Select the Include in Transaction option to include this interconnection for transaction processing.

    This option is available for entry only if you are calling from a fix/inspect, header detail, or headerless detail form.

  9. Click one of these buttons to add notes:

    • Structure Notes

    • Parameter Notes

  10. After the data structure is defined, click the OK button.

    Event Rules Design displays the form interconnect with this statement:

    Call (Application <name> Form <name>)
    

2.4.4 Creating a Dynamic Modal Form Interconnection

To create a dynamic form interconnection:

  1. On Event Rules Design, select an event.

  2. Click the System Function button.

  3. Select the General folder.

  4. Select Dynamic Form Interconnect (Web Only).

  5. Assign event rules to the input values Application ID, Form ID (both are required),Version, and DSValue (both are optional).

    If you are not using either Version or DSValue, you must include the pipes around the null values.

  6. Click OK to save the interconnection.

2.4.5 Creating a Modeless Form Interconnection

To create a modeless form interconnection:

  1. On Event Rules Design for the find/browse form that you want to use (the source), select an event.

  2. Click the Form Interconnect button.

  3. On Work with Applications, select the application to which you are connecting.

    Work with Forms displays available forms for the chosen application.

  4. Select the form to which you want to connect (the target).

    The Form Interconnect - Values to Pass window displays the data structure for the target form.

  5. Select the version of the fix/inspect form to which you want to connect.

    The Data Item column displays data items in the data structure of the target form. The keys in the primary unique index, for the primary table of the BV, are automatically set up as the data structure.

  6. Select the Modeless option.

  7. In the Available Objects column, select objects that you want to pass and move them to the Data Structure-Value column.

  8. Indicate the direction of data flow between Value and Data Items.

    As you click the direction arrow, it toggles through these options:

    • Data flows from the source to the target.

    • Data flows from the target to the source.

    • Data flows from the source to the target and, upon exiting the target, data flows back to the source.

    • No data flow.

  9. Click one of these buttons to add notes:

    • Structure Notes

    • Parameter Notes

  10. After you define the data structure, click the OK button.

    Event Rules Design displays the form interconnect with this statement:

    Call http://ple-mbarrera:8080/PSOL/e1tools896pbr0/eng/psbooks/index.htm
    (Application <name> Form <name>)
    

2.5 Working with the Accessibility Violation Check Feature

This chapter provides an overview of the accessibility violation check feature and discusses how to:

2.5.1 Understanding Accessibility Violation Check Feature

Accessibility Violation Check enables the EnterpriseOne application to capture the Accessibility violations at design time. It provides a way in the Form Design Aid (FDA) to implement empty tooltip validation on image controls. Accessibility Violation Check is developed in FDA wherein the EnterpriseOne application generates a warning report for all the image controls that have an empty tooltip.

The Accessibility Violation Check feature is available in 8.98 tools release only with JD Edwards EnterpriseOne 9.0 Apps release and above.

2.5.2 Enabling the Accessibility Violation Check Feature

You must enable the Accessibility Violation Check in EnterpriseOne in order to access it. To enable the Accessibility Violation Check feature:

  1. In FDA, click the View menu, and then select User Options.

  2. On User Options, click the General tab.

  3. Select the Enable Accessibility Violation Check option, as shown in this example:

    Figure 2-1 User Options, Enable Accessibility Violation Check

    Description of Figure 2-1 follows
    Description of "Figure 2-1 User Options, Enable Accessibility Violation Check"

  4. Click OK.

    The check box for the Enable Accessibility Violation Check is selected by default. If you want to disable the feature, you must clear the Enable Accessibility Violation Check option.

2.5.3 Identifying Empty Tooltips Using Accessibility Violation Check Feature

To ensure that all the applications developed in EnterpriseOne have tooltips inserted on image controls, perform the following steps:

  1. Verify that the Accessibility Violation Check option is selected on the User Options screen.

  2. Click File, and then select Check Accessibility Violation Check.

  3. EnterpriseOne performs a violation check for all the image controls that have an empty tooltip and generates the Accessibility Violation Check screen.

  4. If all the image controls have tooltips inserted, EnterpriseOne displays the No Empty Tooltips found message, as shown in this example:

    Figure 2-2 Accessibility Violation Check, No Empty Tooltips

    Description of Figure 2-2 follows
    Description of "Figure 2-2 Accessibility Violation Check, No Empty Tooltips"

    Note:

    If the image controls have empty tooltips, EnterpriseOne displays details of the warnings and the location of the log file.
  5. Click Yes on the Accessibility Violation Check screen to view the log files for the warnings generated.

    The log file generated provides information about:

  • Application Name

  • Application Title

  • Form Name

  • Warning Description

  • Bitmap Control ID

  • Bitmap ER Title

    Note:

    If you close any given EnterpriseOne application with empty tooltips, then the system displays an error message. Click Yes to exit the application, click No to remain in the application.

2.6 Working with Quick Form

This section discusses how to use Quick Form. By default, a form is opened in update mode. This means the system will only update existing data records. If a form is launched by a form interconnect statement in the Add button, then the form will be opened in add mode. This means the system will add new data into a business view when the form is closed.

2.6.1 Prerequisite

Attach a BV to the form.

2.6.2 Using Quick Form

Quick Form enables you to place multiple database fields on a form faster than choosing each data item individually. Select one or more data items, and Quick Form automatically places the fields on the new form simultaneously.

Depending on the number of selected fields, you might need to resize the form or move and align fields to achieve the desired layout.

To use Quick Form:

  1. On Form Design Aid, select Form, Quick Form.

  2. On Quick Form layout, select the number of columns of controls you want on the form and whether you want the columns arranged horizontally or vertically.

  3. Select the data items from the BV that you want to display and move them to the columns in the form pane.

  4. Use the buttons under the columns in the form pane to order the data items.

  5. Click the OK button to place the fields on the form.

    Quick Form remains open so that you can adjust the arrangement by changing the columns per row and the vertical and horizontal placement.