Screens (.NET or Java)

Use the Screens configuration page to specify how you want the generated Web application to handle both recognized and unrecognized host application screens.

Clear the Screens checkbox if you do not want the generated Web application to provide interaction with the host application screens.

Configuring Unrecognized Screens

To configure how the Web application will handle host application screens that are not recognized as a defined entity by Host Integrator, select the Unrecognized Screens node and modify the following Unrecognized Screen and Error settings:

Display

Terminal
When the Web application encounters an unrecognized host application screen it is rendered as a terminal on the Web page. Choose either to:
- Always show Aid keys (default)
  -or-
- Always hide Aid keys. If you choose this option, you can only disconnect after viewing the host screen.
Custom
When the Web application encounters an unrecognized host application screen the custom user-defined page displays. Using this option you can take complete control of how unrecognized screens are handled in the Web application.
Specify the URL of the page you want displayed when an unrecognized screen is encountered. A relative URL is assumed to be relative to the root of the Web application and the page must be included with the Web application. You can do this manually or by using the Custom Content options. Custom settings are available from the Project Properties Customization tab.
Example URLs:
To create and use a custom page
1. Generate your Web application.
2. Copy the page that most closely approximates the page or pages you want to use. In Java, JSP and ASP pages are located in <vhi-install>/tomcat/webapps/<Web-app name>. In .NET the pages are located in <Inetpub>/wwwroot/<Web application name>.
3. Use this page as a starting point for creating a custom page. You can create a page from scratch. If you are not using .NET, custom pages must be either a JSP page or an absolute URL to another page.
4. Create a folder in which to place your custom pages. This is the location that will be specified in the URL field on the Screens or Procedures and Models dialog box.
5. In Web Builder options > Customization > Custom Content, specify the folder that you just created.
6. Under Screens or Procedures and Model Features, select the item you want to replace with your custom page. Set the Display type to "Custom".
7. Specify the path to your custom file in the URL field. This path should be relative to the directory structure you created in step 4.
8. Rebuild your project. When the project is rebuilt, the custom page is added to and deployed with your Web application. Each time you rebuild, the overlay folder is inserted into the built Web application.
For information on customizing Web applications and themes, see Customizing Verastream Web applications
Hide
When the Web application encounters an unrecognized host application screen, rather than display an unrecognized screen, display the message entered here.
Error
When the Web application encounters an unrecognized host application screen, rather than display an unrecognized screen, display an error message. You can configure the following:
- Message to display. Type in the text you want to display.
- Disconnect from the host. The Web application disconnects from the host when an unrecognized screen is encountered.

Configuring Recognized Screens (Entities)

To configure how the Web application will handle host application screens that are recognized as a defined entity by Host Integrator, select the Recognized Screens (Entities) node and modify the following settings:

Display

Form (default)
Web Builder generates a page exposing the defined attributes, recordsets, and operations for a recognized host application screen.
- Attributes. If defined as writable, an input field on the form is generated. If not, the attribute is displayed as readable text on the form.
- Recordsets. A table is generated showing the defined column headings and data for the recordset. A link is provided for navigating through the recordset data.
- Operations. A button is generated for each operation which has the name specified in the Design Tool as a caption and the description specified as a tool tip.
Terminal
Web Builder generates a page that exposes the host application screen as a terminal. Choose either to:
- Always show Aid keys. If you've defined operations in your model, operation buttons display above the Aid key buttons.
- Always hide Aid keys. If you choose this option, you can only disconnect after viewing the host screen.
  -or-
- Hide Aid keys when operations are available (default). Only show Aid keys when there are no operations defined for the entity. If there are defined operations, then no Aid keys are displayed.
Custom
Web Builder will not generate a page for this entity, but will instead use the specified URL for the page to be displayed when the entity is encountered. Using this option you can take complete control of how the entity is handled in the Web application.
Specify the URL of the page you want displayed when the entity is encountered. A relative URL is assumed to be relative to the root of the Web application and the page must be included with the Web application. You can do this manually or by using the Custom Content options.
Example URLs:
For steps on creating a custom page, see Configuring Unrecognized Screens at the top of this page.
Hide
Web Builder generates a page in which a message is displayed instead of information defined for the entity. If there is not a message defined, nothing is displayed. Enter the text you want displayed.
To change the default setting for an individual entity use this option.
Error
When the Web application encounters an unrecognized host application screen, rather than display an unrecognized screen, display an error message. You can configure the following:
- Message to display. Type in the text you want to display.
- Disconnect from the host. The Web application disconnects from the host when an unrecognized screen is encountered.