Problem:
How do you create web pages using EnterpriseLink Builder?
Resolution:
A static page is one that is not mapped to any host screen. You can use these has extended help pages or choose to build new business rules using SmartScript, SQL database interactions or invoking external Web services. For the user to navigate off of static pages a hyperlink must be used. If the hyperlink destination is to the primary or secondary page of the session's current host screen (i.e., the host screen belonging to the most recent primary page that was displayed), there is no mainframe interaction.
This KB describes how to attach browser-side and server-side scripts using Builder, and describes the SmartScript classes you use to write server-side scripts.
Entry field for Database selection - the host input field to which the value of the selected radio button is sent. Drag the host input field, which is next to Database selection, and drop it on the first radio button. Click Yes to use this host input field for all the radio buttons in the group.
If multiple objects are selected on a page, the last one selected (in Builder object name order) determines the cursor position sent to the host application. For example, if there are two groups of radio buttons and one button is selected in each group, and the name of the first group is "RadioButtons1" and the second is "Databases", the cursor position of "RadioButtons1" is sent to the host.
Before setting up a dynamic table the host screen should be properly recorded. Usually a variable length list generated from a mainframe is managed through PF8 (next) and PF7 (prior). The screen that will be scrolling should therefore contain two self transitions (destination is the same screen name). Also in these cases there is usually a screen where one supplies the query parameters. There should be a transition from this screen to the scrolling screen as well. Further, there should be one and only one scrolling screen recorded in the database. If there are other screens that "sort of" look like the scrolling screen (partial data, partial rows) they should be removed. Only the screen with the most rows should remain. That is the screen used for customization.
When setting up dynamic tables, you must map data from the host screen into each cell of the table. If, for example, the data you map into the table is the result of a search of a host database, you must, when capturing that screen, use a search that generates results in each row and column. Also, specify which AID Key values should be used for Forward (required) and Backward (optional) operations. EnterpriseLink IntegrationServer will continually send the Forward AID key to the host application until one of two events happens: (1) The Max Rows in the table have been collected or (2) the stopping condition has been met. These are specified in the Scanning Algorithm tab.
#EnterpriseLink
#Rumba