4 6 Tips Techniques

4.6 Tips & Techniques

• Menus created with earlier versions (before V10.0) of the Web Functions Wizard will be automatically converted for the current Web Functions Wizard. Be aware that once these menus have been converted, the menu definitions will no longer be available if you revert to running an earlier version of the Web Functions Wizard. The associated menu component will not be modified until you select to re-build the menu using the new Web Functions Wizard.

• It is recommended that you configure your Menu Features before defining or building any standard menus. This is especially useful if you intend to use dynamic buttons on your menus.

• The menu definitions (Standard and DHTML) are stored on the files DC@W31 and DC@W32. To use the Wizard in a different partition and access these menu definitions, the data from these files must be exported to the partition where the Wizard will be executed.

• When defining a Horizontal Standard Menu including dynamic buttons, you have the option to select a Tab or Button style. Tab buttons will sit on the edge of the horizontal menu area. The conventional button style is designed to sit above the edge of the horizontal menu area. The combined use of Tab and Button styles will provide undesirable results when the menu is built.

• When defining a Horizontal Standard Menu including dynamic buttons, be careful about including other Menu Types in the Menu. Variations in the menu width will provide undesirable results when the menu is built.

• It is not normal to define a dynamic button without an action. If that were the case, if the condition is true the button will appear but when the user clicks on it nothing will happen.

• If you are defining a Left or Right Standard Menu including dynamic buttons, you will only have the option to a conventional Button style. Tabs are not supported in this orientation.

• Defining the menus is the responsibility of the developer. All available combinations of menu type, menu state and link type can be used at the developer's discretion although some variations may not be good design. For example, dynamic buttons are typically used to execute something, so use of dynamic buttons with "no link" may cause user confusion.

• The code within components or Web pages used by the menu is the responsibility of the developer.

• Any optional JavaScript is the responsibility of the developer.

• If you previously chose to Include Menu Separator between Menu Items, the box will be checked when you review the menu definition. Any subsequent changes to Menu items will cause the box to become unchecked.

• If you are using dynamic buttons on your menu, consider including the field STDTABFLR in your functions to automatically support on and off images to indicate which button is currently selected. The STDTABFLR field should be included as a *HIDDEN field in your REQUEST or DISPLAY statements, or in your GROUP_BY statements used with your screens. You can also add the STDTABFLR field to your DEFAULT_HIDDEN or <process>_HIDDEN page. For more details, refer to WIZ004 – Defining a Standard Menu Component.

• When creating menus in multiple languages, configure a single language and test the menus before defining the menus in any other language. Only the Description, Static Image name, MouseOver Image Name and any Optional JavaScript will vary with language.

• When creating menus in multiple languages, one of which is English, configure the English menus first. The English version will then be used as the basis for menus in other languages.