Screens (.NET or Java Web Application)

Use the Screens tab to configure how you want to handle unrecognized screens and to specify how to display recognized screens.

Configuring Unrecognized Screens

Configuring Recognized Screens



Configuring Unrecognized Screens

If a model does not have defined entities for host application screens, specify how Host Integrator should handle these unrecognized screens. Generate web pages for unrecognized screens using one of the following options:

Terminal

After a connection is established to the host, Web Builder reformats each host screen into a terminal-like web page. This is the default. When you choose Terminal, you can control how aid keys are displayed:

Always show aid keys
Select this option to always display aid key buttons in your web application. If you've defined operations in your model, operation buttons appear above the aid key buttons.

Always hide aid keys
Select this option to suppress the display of terminal aid keys.

Custom

You can create a custom format for unrecognized screens. This option may be useful to display a screen containing an error or alert in a different format than the recognized screens (entities) that you have defined.

HREF
Specify the hypertext reference for a page defining the format of the custom screens. This designation is associated with the folder location you specify for the Custom Settings of your web application.

Examples:
custom1.asp
/mypages/custom1.asp

Hide

Select this option to hide unrecognized screens.

Message to display
Type in the text that is displayed when the unrecognized screen is hidden.

Error

Rather than display an unrecognized screen, display an error message. You can configure the following:

Message to display
Type in the text that is to be displayed.

Disconnect from the host
Select this option if you want the web application to disconnect from the host when the unrecognized screen is encountered.

Configuring Recognized Screens (Entities)

You can set up the way your web applications handle recognized screens (entities) on a global basis, or you can select individual entities and specify a a different display. You can use Reset All to return all recognized entities to the default values.

Default Display
By default, a web application uses a form display type for entities. You can choose a different default display. All entities will use the display type you select here unless you override it for a specific entity.

Overriding the default display: The name of any entity that is modified from the default is displayed in bold and has an asterisk following the name. You can quickly locate any special display handling you have added for an individual entity in the web application.

Overriding the display of attributes and operations: You can choose to suppress the display of attributes or operations for a specific entity. Click the + sign next to any entity to view the settings for attributes and operations for that entity; clear the check box next to Attributes or Operations to change the setting.

By default, all attributes and operations defined in the model are displayed. You must explicitly deselect the attribute or operation for each separate entity.

Form

Web Builder generates a web application that handles the data fields differently than it handles the screen display. This is the default. The dynamic data on an entity (the defined attributes, recordsets, or operations) comes from the host application, and is updated as needed.

The appearance of the user interface remains static and is generated into either .jsp or .aspx pages that can be modified by a web designer. You can, however, copy the form and use the Custom option described below to make modifications.

Terminal

Web Builder reformats each host screen into a terminal-like web page. When you choose Terminal, you can control how aid keys are displayed:

Always show aid keys
Select this option to always display aid key buttons in your web application. If you've defined operations in your model, operation buttons appear above the aid key buttons.

Always hide aid keys
Select this option to suppress the display of terminal aid keys.

Hide aid keys when operations are available
Select this option to conceal the aid key buttons and display a button for defined operations instead.

 

Custom

You can create a custom format for unrecognized screens. This option may be useful to display a screen containing an error or alert in a different format than the recognized screens (entities) that you have defined.

HREF
Specify the hypertext reference for a page defining the format of the custom screens.

Examples:
custom1.asp
/mypages/custom1.asp

Hide

Select this option to hide screens.

Message to display
Type in the text that is displayed with this terminal screen.

Error

Rather than display a screen, display an error message. You can configure the following:

Message to display
Type in the text that is to be displayed.

Disconnect from the host
Select this option if you want the web application to disconnect from the host when the unrecognized screen is encountered.