Subfile (drop-down)

The subfile (drop-down) widget is responsible for rendering a 5250 subfile.

This widget renders data supplied by the subfile component.

Note: For DBCS considerations when using this widget see SBCS eliminate maximum length.
The following figure shows how a subfile (drop-down) widget appears on a transformation, using the data from the Subfile component example as input:
Figure 1. Subfile (drop-down) widget example
Example of subfile (drop-down) widget
  1. Caption type (show both)
  2. Leading token
  3. Description
  4. Submit button (show submit button)
  5. Submit button caption (Submit)
The following settings can be configured for this widget:
Caption type:
Specifies how the caption for each item in the drop-down is determined. The value of the leading token and the description are derived from the component; you can select what appears as the caption. For example, if the host screen had an action that read 5. Display, you can have the caption display 5, or Display, or 5. Display.
Show subfile actions
Select this box if you want to display the descriptive text of the subfile actions, such as 2=Add, with the rendered subfile in addition to the drop-down list. The check box is not enabled when you select Show description.
Auto submit on select
If selected, once a selection is made in the drop-down, it is submitted.
Show submit button
If selected, a submit button is rendered below the subfile.
Submit button caption
Optional. Specifies the caption of the submit button.
Button style class (Web-only)
Optional. The CSS style class associated with the generated submit button. The value of the class attribute of the HTML button tag will be set to this value. The default value is HATSBUTTON. See Using style sheets for more information.
Button row style class (Web-only)
Optional. The CSS style class associated with the generated table row which contains the submit button. The default value is HATSTABLEHEADER. See Using style sheets for more information.
Rows per record
Number of rows
Specify the fixed number of rows per record in your subfiles.
Columns placement (Web-only)

This widget can be configured to display primary columns of data, and optionally to have a details section to view additional detail columns. This setting is useful when displaying table data on a mobile device. For more information about these settings and about other settings for this option that do not appear in the ZIETrans Toolkit GUI, see Considerations and limitations for mobile devices.

Primary columns
Use this field to specify which columns to display, and in what order. The field allows for numeric any-order listing of column numbers with expansion shorthand, and columns are allowed to be displayed more than once or not at all, for example, 1,3,2,5-7,2-3,9.

A hyphen (-) between two numbers indicates a range of columns. You can use the asterisk character (*) to indicate the last available column. An asterisk alone means columns 1 through n where n is the last available column. You can also use 5* as a shorthand for 5-*. These mean the same thing: 1-*, *.

For Web projects, this setting defaults to *, or all columns. For Web projects optimized for mobile devices, this setting defaults to 1-2, or columns 1 and 2.

Note: The numbers represent columns provided to the widget by the component. They do not represent the columns originally recognized by the component, which may or may not be excluded, before providing them to the widget.
Detail columns
Use this optional field to specify which detail columns to display when requested, and in what order. The field allows for numeric any-order listing with expansion shorthand.

For Web projects, this setting defaults to empty, or no detail columns section. For Web projects optimized for mobile devices, this setting defaults to 3*, or column 3 through the last column.

Keep detail columns on the server
Select this option to keep the detail columns section on the server until requested by the user. This reduces the amount of HTML output at initial rendering. The default is cleared.
Enable foreground colors
If selected, host screen foreground colors are rendered.
For Web applications, colors are mapped to CSS stylesheet classes representing that color. For example, if a host screen field is marked as RED, the Field widget will enclose the generated HTML for that field in a tag whose class name attribute is set to HRED. This allows for you to remap host screen colors on your generated Web page.
Note: The blacktheme.css directly maps host screen field foreground colors (for example, red text on the host screen will appear as red text on the generated Web page). However, other stylesheet files like monochrome.css, map field colors differently in an attempt to create a consistent, modern style.
Field style class (Web-only)
Optional. The CSS style class associated with the generated field. The value of the class attribute of the HTML tag will be set to this value. The default value is HATSFIELD. See Using style sheets for more information.
Enable extended attributes
If selected, extended field attributes (blink, reverse video, underline, and column separator) are rendered with the specified style. See Using style sheets for more information.
Blink style (Web-only)
The CSS style setting you want to use to render blinking text from the host screen.
Reverse video style (Web-only)
The CSS style setting you want to use to render reverse video text from the host screen.
Underline style (Web-only)
The CSS style setting you want to use to render underlined text from the host screen.
Column separator style (Web-only)
The CSS style setting you want to use to render column separators from the host screen.
Strip underscores on input field
Select this box if you want to strip the underscores from text when it is rendered.
Trim spaces on input field
Select this box to trim leading and trailing spaces from the input field.
Enable cursor positioning option on input fields (Web-only)
Select this box to allow the user to switch from data input mode to cursor positioning mode for input fields. When in data input mode, the user can enter data into the input field. When in cursor positioning mode, the user can tab to or otherwise position the cursor on any character in the input field. This setting is useful for Web projects that are optimized for mobile devices that do not have other cursor positioning capabilities. For more information about other settings for this option that do not appear in the ZIETrans Toolkit GUI, see Considerations and limitations for mobile devices for more information.
Provide spreadsheet file
If selected, a launcher is provided that will retrieve the table data in spreadsheet file format.
File name prefix
Specifies a prefix for the spreadsheet file name. The default is spreadsheet. The complete file name will be in the form of FileNamePrefix_TimeStamp, where the timestamp format is MMDDYY_HHMMSS, for example, spreadsheet_041506_113020.
File name extension
The extension name for the type of spreadsheet format. Options are .csv and .xls. The .csv file are pure text files, with data columns separated by commas. The .xls files are Microsoft Excel Biff3 files. The default is .csv.
Launcher type
The type of launcher to display to the user. Options are Link, Image, and Button. The default is Link (Web projects).
Launcher caption
The caption for the launcher to display to the user. The default is Download (Web projects).
Button style class (Web-only)
The CSS style class associated with the generated launcher button. The value of the class attribute of the HTML button tag will be set to this value. The default value is HATSBUTTON. See Using style sheets for more information.
Link style class (Web-only)
Optional. The CSS style class associated with the generated launcher link. The value of the class attribute of the HTML link tag will be set to this value. The default value is HATSLINK. See Using style sheets for more information.
Drop-down style class (Web-only)
Optional. The CSS style class associated with the generated drop-down. The value of the class attribute of the HTML drop-down tag will be set to this value. The default value is HATSDROPDOWN. See Using style sheets for more information.
List option style class (Web-only)
Optional. The CSS style class associated with each option in the drop-down. The default value is HATSOPTION. See Using style sheets for more information.
Table style class (Web-only)
Optional. The CSS style class associated with the generated table. The value of the class attribute of the HTML table tag will be set to this value. The default value is HATSTABLE. See Using style sheets for more information.
Table cell style class (Web-only)
Optional. The CSS style class associated with each cell in the generated table. The value of the class attribute of the HTML table cell (td) tag will be set to this value. The default value is HATSTABLECELL. See Using style sheets for more information.
Header row style class (Web-only)
Optional. The CSS style class associated with each header row or column in the generated table. The value of the class attribute of the HTML table row or cell tag will be set to this value. The default value is HATSTABLEHEADER. See Using style sheets for more information.
Odd row style class (Web-only)
Optional. The CSS style class associated with each odd numbered row in the table. The value of the class attribute of the each HTML table row tag in an odd row number will be set to this value. The default value is HATSTABLEODDROW. See Using style sheets for more information.
Even row style class (Web-only)
Optional. The CSS style class associated with each even numbered row in the table. The value of the class attribute of the each HTML table row tag in an even row number will be set to this value. The default value is HATSTABLEEVENROW. See Using style sheets for more information.
Style (Web-only)
Optional. Use the launcher button next to this field to open a style properties dialog. This dialog frees you from the need to understand CSS to change the font, color, or other style settings for the widget. See Using style sheets for more information.
fieldTextAlignment (Web-only)
For Web projects, if you use a non-monospace font such as Sans Serif, the rendered data does not align properly with spacing problems between words. You can use the source setting, fieldTextAlignment, to correct the alignment of the data. To enable this setting on a project-wide basis, open the source view of the application.hap file, locate the class for the SubfileWidgetV6 widget, and change the value of the setting to NO_SEGMENTING as shown in the following example:
<class name="com.ibm.hats.transform.widgets.SubfileWidgetV6">
.
   <setting name="fieldTextAlignment" value="NO_SEGMENTING"/>
.
</class>
To enable this setting on a component-level basis in a transformation, open the source view for the transformation, locate the ZIETrans:Component tag for the SubfileWidgetV6 widget, and change the value of the setting to NO_SEGMENTING as shown in the following example:
...
widget="com.ibm.hats.transform.widgets.SubfileWidgetV6"
...
widgetSettings="...|fieldTextAlignment:NO_SEGMENTING|..."
...
The values for this setting are WORD_BY_WORD and NO_SEGMENTING. The default value is WORD_BY_WORD.
Note: This setting has no effect when you use the Table (visual) recognition option for data recognition in the Subfile component.