11 Understanding Message Forms

This chapter contains the following topics:

11.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.

11.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.

11.3 Understanding Message Form Events

These events can occur on the message form during runtime:

  • Dialog is Initialized

  • XAPI Subscribe Event

11.4 Message Form Runtime Processing

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

11.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.

11.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.