Using the Editors

This appendix lists the properties that are set on screens, widgets, and reports generated by the screen and report wizards. It also describes the function of some of the property settings.

Screen Wizard Output Property Specifications

The screen wizard sets several screen and widget properties for two-tier and three-tier applications. This section lists some of the important properties that control appearance and behavior.

Two-Tier Property Specifications

The screen wizard sets screen properties that control screen behavior. You can edit these properties; however you must be aware that any changes to these properties will alter the behavior of your screens. Some of the important screen properties are as follows:

• Under Focus, the Entry Function property is set to enter_screen. This is a call to a simple screen entry procedure that publics the screen wizard's JPL module, smwizard.jpl.

• Under Focus, the JPL Procedures property includes the enter_screen procedure. This is a one line procedure invoked on screen entry.

• If you requested Menu/Toolbar controls, two more screen properties are set:

  • Under Focus, the Menu Script File property displays the name (smwzmenu) of the screen wizard's template menu file.

  • Under Focus, the Menu Name property is set to the name (wzmain) of the topmost menu within that file.

    Note: The menu bar/toolbar does not display in the screen editor; it is visible in test mode.

Widget Property Specifications

The screen wizard sets properties for the widgets that control their behavior and appearance.

You can edit the widget properties that control the appearance of your widgets. Some of the properties are as follows:

• Label widgets—Under Geometry, the Horiz. Anchor property is set to Right. This permits all label widgets to appear right-aligned and next to their corresponding text widgets.

• Grid widget—The following are some of the visual properties that are set:

  • Under Format/Display, the Stripe Current Row property is set to Yes. A highlight bar indicates the current row in the grid.

  • Under Format/Display, the Column Titles property is set to Per Column. Database column names appear across the top of the grid widget.

  • Under Identity, each column gets its title by way of its Column Title property.

You can also edit the widget properties that control screen behavior. Some of the important properties are as follows:

• Single line text widgets (or widget type adopted from repository)—The following properties are set on any widget of the First table that is a foreign key to an Additional table:

  • Under Help, the Selection Screen property specifies the name of the selection screen for the Additional table.

  • Under Database, the Validation Link property specifies the name of the link widget which connects the First table with the Additional table.

    Note: If you have already set the Validation Link property for the widget in the repository, the screen wizard does not overwrite it.

• Grid widget—The following are some of the properties that are set:

  • Under Focus, the Row Entry Func is set to fill_child. This procedure ensures that all table views that are descendants of the current grid are refreshed whenever the grid stripe moves.

  • Under Focus, the Row Exit Func is set to save_new_record. This procedure saves the current row in the grid widget if it is a new row and it is non-empty.

Selection Screen Property Specifications

For a two-tier architecture, the selection screens (.itm) generated by the screen wizard have the following features:

• The grid widget contains the columns you selected from that table and additional tables. The table's primary key is leftmost in the grid widget; the other columns continue off to the right.

• Two push buttons inside a positioning region box are under the grid: OK and Cancel. The positioning region keeps the buttons centered horizontally on the screen.

You can edit any of the following selection screen properties that control selection screen behavior.

• Grid members associated with the primary key have the Frozen Columns property set. This prevents these grid members from being moved. They can receive focus, but the content cannot be edited at runtime.

• Grid members associated with the primary key have their Double Click property (under Validation) set to translate a mouse double-click to the XMIT logical key. (The XMIT key behaves like an OK.)

• Non-primary key grid members have the Focus Protection property set to Yes. They cannot be updated or receive focus.

• The screen has the Entry Function property (under Focus) set to a function that populates the grid.

• The OK button's Control String property (under Validation) is set to a function that places the cursor back into the grid widget, and then causes an XMIT to happen. Choosing OK at runtime returns the selected item to the calling screen.

  Note: This control string works because the first column in the grid is also the first field on the screen. If you place any widgets above the grid widget, you will have to modify the call to sm_o_gofield.

• The Cancel button's Control String property is defined to close the screen.

If the primary key of the table consists of more than one column (sometimes known as a composite key), then two additional screen properties are set:

• Under Focus, the Control Strings property has one entry that maps the XMIT logical key to call the copy_back function.

• Under Focus, the JPL Procedures property contains the function copy_back(). This function copies all components of the primary key back to the calling screen.

Three-Tier Property Specifications

The screen wizard sets screen properties for three-tier client screens and service components that control screen behavior. You can edit these properties; however you must be aware that any changes to these properties will alter the behavior of your screens.

Some of the important three-tier client screen properties are as follows:

• Under Focus, the Entry Function property is set to enter_screen. This is a call to a procedure that publics the screen wizard's standard JPL module, smwizard.jpl.

• Under Focus, the JPL Procedures property includes the enter_screen procedure, a one-line procedure invoked on screen entry.

• If you requested Menu/Toolbar controls, two additional screen properties are set:

  • Under Focus, the Menu Script File property is set to smwzmenu, the screen wizard's template menu file.

  • Under Focus, the Menu Name property is set to wz3tmain, the name of a menu within the smwzmenu file.

    Note: The menu bar/toolbar does not display in the screen editor; it is visible in test mode.

• Under Transaction, the Model property is set to the Middleware API transaction model. For further information on the Middleware API transaction model, refer to Chapter 7, "Transaction Model for JetNet," in JetNet/Oracle Tuxedo Guide.

Some of the important service component properties are as follows:

• Under Focus, the Entry Function property is set to enter_service. This is a procedure that publics the screen wizard's service component JPL module, smwizsrv.jpl.

• Under Focus, the JPL Procedures property includes the enter_service procedure; a one-line procedure invoked on screen entry.

Widget Property Specifications

For client screens in a three-tier architecture, the screen wizard sets properties for the widgets on the screen that control screen appearance and screen behavior.

You can edit the widget properties that control the appearance of your screens. Some of the properties are as follows:

• Label widget—Under Geometry, the Horiz. Anchor property is set to Right. This permits all label widgets to appear right-aligned and next to their corresponding text widgets.

• Grid widget—The following are some of the properties that are set:

  • Under Format/Display, the Stripe Current Row property is set to Yes. A highlight bar indicates the current row in the grid.

  • Under Format, the Column Title property is set to Per Column. This specifies that the column names appear across the top of the grid widget.

  • Under Identity, each column gets its title by way of its Column Title property.

You can also edit widget properties that control screen behavior. Some of the important properties are as follows:

• Single line text widget (or widget type adopted from repository)—The following properties are set on any widget of the First table that is a foreign key to an Additional table:

  • Under Help, the Selection Screen property specifies the name of the selection screen for the Additional table.

  • Under Database, the Validation Link property specifies the name of the link widget which connects the First table with the Additional table.

    Note: If you have already set the Validation Link property for the widget in the repository, the screen wizard will not overwrite the present value.

• Grid widget—The following are some of the properties that are set:

  • Under Focus, the Row Entry Func is set to fill_child. This procedure ensures that all table views that are descendants of the current grid are refreshed whenever the grid stripe moves.

  • Under Focus, the Row Exit Func is set to save_new_record. This procedure saves the current row in the grid widget if it is a new row and it is non-empty.

• Link widget—Under Service, the Validation Service property specifies the name of the service. The service receives data from the client into the service component, verifies that the primary key exists in the database and returns detail data for that primary key to the client. The service name includes the Service Prefix and the suffix _l# that indicates the validation link operation that the service implements.

• Table view widget—Service properties are set on the First Master table views only. The service properties specify the service names that are called for the different types of transaction manager operations or SQL operations.

  • Delete Service—Specifies a service to implement a Delete operation that removes information from database tables.

  • Insert Service—Specifies a service to implement an Insert operation that adds information to database tables.

  • Select Service—Specifies a service to implement a Select operation that retrieves information stored in database tables.

  • Update Service—Specifies a service to implement an Update operation that makes modifications to the data stored in database tables.

Selection Screen Property Specifications

For a three-tier architecture, the selection screens (.cit) generated by the screen wizard have the following features:

• The grid widget contains the columns you selected from the Additional Table and any of its descendants. The table's primary key is leftmost in the grid widget; the other columns continue off to the right.

• Two push buttons inside a positioning region box are under the grid: OK and Cancel. The positioning region keeps the buttons centered horizontally on the screen.

You can edit any of the following selection screen properties; however you must be aware that any changes to these properties will alter the behavior of your selection screens.

• Grid members associated with the primary key have the Frozen Columns property set. This prevents these grid members from being moved.

• Grid members associated with the primary key have their Double Click property (under Validation) set to map a double-click to the XMIT logical key. (The XMIT key behaves like an OK.)

• Non-primary key grid members have the Focus Protection property set to Yes. They cannot be updated or receive focus.

• The screen has the Entry Function property (under Focus) set to a function call that populates the grid.

• The screen has the Model property (under Transaction) set to jetrb1, the transaction model for JetNet and Oracle Tuxedo applications that generates service requests.

• The OK button's Control String property (under Validation) is set to a function that places the cursor back into the grid widget, and then causes an XMIT to happen. Choosing OK at runtime returns the selected item to the client screen.

  Note: This control string works because the first column in the grid is also the first field on the screen. If you place any widgets above the grid widget, you will have to modify the call to sm_o_gofield.

• The Cancel button's Control String property is defined to close the screen.

• Under Service, the Select Service property is set for the first master table view with the service name specified for the corresponding CHOOSE operation on the Service Definition dialog. The service implements a Select operation that retrieves information stored in database tables.

If the primary key of the table consists of more than one column (sometimes known as a composite key), two additional properties set on the screen:

• Under Focus, the Control Strings property has one entry that maps the XMIT logical key to the copy_back function call.

• Under Focus, the JPL Procedures property contains the function copy_back(). This function sends all parts of the composite key back to the calling screen. This function copies all components of the primary key back to the calling screen.

Report Wizard Output Property Specifications

The report wizard automatically sets a number of properties both on the report file itself and on individual widgets. This section briefly describes some of the properties that are set by the report wizard.

Report file

The report wizard defines and sets the following properties for the report file:

• Under Inclusions, the JPL Procedures property makes public the template JPL file rwwizard.jpl.

• Under Transaction, the Root property is set to the table view selected on the Table Selection dialog box.

Page orientation

If the width of the report exceeds 8.5 inches, the Orientation property is set to Landscape. Otherwise, the property value is set to Portrait.

Data fetching

For each detail node, the Data Source property is set to TM View. This indicates that the transaction manager executes VIEW and CONTINUE commands to fetch the report data. When the transaction manager executes these commands, data is fetched for any dynamic output widget that is a member of the current transaction.

Table views

For the root table view, the Sort Widgets property contains the names of widgets not included in the report totals. If you delete a widget from the report, you also must delete the widget from the Sort Widgets property. Otherwise, you get an error.

Data grouping

For each group node, the Break On property is set to a database column chosen in the Data Group Order dialog box. The hierarchy of group nodes corresponds to the order selected on that dialog.

Output

For each print node, the Area property is set to the appropriate layout area.