9 Understanding Message Forms

This chapter contains the following topics:

9.1 Message Forms

The message form type is a form that appears as a secondary window to inform the user of something or to ask a question. It parallels the behavior of a Windows message box. The form does not have a tool bar or a status bar and can only contain static text and buttons.

Message forms permit only limited use of processing option (PO) values and business functions. Therefore, do not use this form type for complex logic.

You can use the message form as a hover form by selecting the pop-up option under the message form properties.

When the "Pop-up Form" check box is selected, all the action buttons, such as OK and Cancel, are hidden. A message form marked as a pop-up form acts as a plain container for the controls. The following controls are supported on a message form that is marked as a pop-up form: Label, Text Block, Group Box, and Image.

When the user hovers on the orange dot and clicks the hover indicator in the hover supported control, a pop-up window with context-based information is displayed.

See "Message Form as Hover Form" in JD Edwards EnterpriseOne Tools Foundation Guide.

The hover form can be associated with the selected controls using the system function Show Popup and Mouse is Hovered event or Feature Authorization applications.

See "Understanding Hover Forms" in the JD Edwards EnterpriseOne Tools Runtime Administration Guide.

The application developer can associate the hover form to the hover form supported form controls, grid row, and grid cell by calling the Show Popup system function in the Mouse is Hovered event.

9.1.1 Hover Events

Mouse is Hovered

This event is provided for hover form supported form controls; grid, and grid columns. This event is used to associate a hover form using Show Popup system function on form controls, grid rows or grid cells.

9.1.2 Hover System Functions

Show Popup (Web Only) System Function

This system function is provided to show the hover form when user hovers on a form control, a grid row selector or grid cell. This system function is listed in the General section of the Event Rules system function listing.

Parameters

<Popup Form>

There are two options to choose a pop up form:

  1. Select Pop Up Form: Use this option to select a specific pop-up form. Once you click on this option, the system will let you choose the Application Name, Form Name, Version, and the parameters to pass into the selected hover pop up form.

  2. Default Popup: Use this option to select the default pop-up option for grid headers. When using the Show Popup (Web Only) system function on the Mouse is Hovered event on the Grid control itself and you choose the Default Popup option, the system will display the grid row data in a tabular format on the hover pop up form. When user hovers on a grid row header, the system will display that particular row data in a tabular format within the hover form. This way, you can quickly glance at a row's values without scrolling the row if it has many columns.

Get Hovered Row Number

This system function returns the current hovered row number when you hover on a hover form associated grid cell.

Parameters

  • Grid :

    Input, required. The grid control on which the hover form is associated on a particular cell.

  • Row

    Output, required. Currently hovered row number - return value from the system function.

GetCollaborate

This system function is provided to create the HTML content for the Collaborate tab with the List of contact names and defined email addresses for the address book numbers.

Parameters

  • TEXTBLOCKCONTROL

    Input, required. FC text block control to effect.

  • SEGMENT ID

    Input, required. Segment of the text block control to effect.

  • Address Number

    Input, required. The address number for which the contacts have to be fetched from Who's Who table.

  • Collaborate Content

    Output field. This string field contains the HTML content for the Collaborate tab with the List of contact names and defined email addresses for the address book numbers.

  • Show Parameterized URL

    Input, required. Flag to indicate whether to show or hide the parameterized URL in the email or calendar request.

Note:

With Release 9.2.1, for existing hover forms that call the Get Collaborate system function, you can create a "Collaborate" tab and drop a subform that contains a grid on the tab. In the Grid Properties, under the HTML Options tab, enter "5" for the Grid Row Count. The form should be over a business view that is a simple join between F0111 and F01151 by column AN8, distinct IDLN, with a filter F01151.ETP equals "E".

With Release 9.2.1, use the Hover Form property on the Power Browse form, to create new hover forms.

See Section 12.3, "Power Browse Form Design-Time Considerations".

9.2 Message Form Design-Time Considerations

Message forms are unique among JD Edwards EnterpriseOne forms in that they include a default push button control on the form. You can configure this button to be OK, Cancel, Yes, or No. You can also make it of type Other and equip it with special functions of your own. Because they have no tool bar, message forms do not have the standard menu buttons available to the other forms. Hence, you must provide all functions with manually-added controls. Because message forms are modal windows, you cannot access the controls on the calling form.

The default size for a message form is 64 pixels high and 273 pixels wide. To accommodate different screen sizes or resolutions, you can change it in the Properties form.

9.3 Understanding Message Form Events

These events can occur on the message form during runtime:

  • Dialog is Initialized

  • XAPI Subscribe Event

9.4 Message Form Runtime Processing

This section discusses how the runtime engine processes the message form.

9.4.1 Dialog Initialization

When a message form is called, runtime initializes these items in this order:

  1. Form controls

  2. Static text

  3. Helps

  4. Event rules (ER) structures

Then, it fires Dialog is Initialized.

9.4.2 Dialog Close

Message forms close when the user clicks the default button. Then runtime performs these tasks in this order:

  1. Terminate helps.

  2. Free all form structures.

  3. Destroy the window.