![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
When you create a screen table you must specify certain fields to contain the data. The other attributes affect the presentation of the field and can be defined at any time. Refer to Controlling Presentation for more information on presentation attributes.The following fields are required for you to create a screen field to contain the data. For valid values, press PF1.
Enter a value that determines in which row of the screen table the field appears. To change the row that a screen field is in, use the cut and paste functions. Changes in the row position are reflected automatically with a new value in this field.You can define one or more fields to row 0 and column 0. This creates a non-display field that you can use to pass values to by using rules. Enter a value that determines in which column of the screen table the field appears. To change the column that a screen field is in, use the cut and paste functions. Changes in the column position are reflected automatically with a new value in this field.You can define one or more fields to row 0 and column 0. This creates a non-display field that you can use to pass values to by using rules. Type a name in this field to uniquely identify the screen field within the screen table. Rules use this name to read data from or write data to the field. Screen fields can be given the same names as fields in other tables; if you are loading data from another table, giving the fields the same name simplifies the process. Specify the syntax for the field. The syntax determines how the data is stored. For more information on syntax, refer to TIBCO Object Service Broker Programming in Rules.
• Use non-display fields (ROW 0, COL 0) to store information that should not be visible on the screen. For example, you can store information that is should not be released at the present time as it is to be used for future development.
• If the information on the screen comes directly from a MetaStor table, use the same field names for the screen tables as those in the MetaStor. Using the same field names makes the assignment of data to the screen field easier.The following fields determine how the data is presented in the screen field. For valid values, press PF1.
Specify a length for the field. This value determines the displayed length of the field allotted to a value of the field when it appears, for example, the maximum number of character positions, including the decimal point, mantissa, and so on. This is done by changing the value of the Len field or by adding characters (A or 9) to the field in the image area.
When defining field lengths, the display size does not always correspond to the stored dictionary length. For example, if a field is defined as 10, 2, the underlying field is defined as length 5 and decimal 2. Of those 5 bytes, 9 nibbles are for digits and 1 nibble is for the sign.
Indicate if you want the field to contain decimals by providing the number of digits to appear to the right of the decimal point. You can also add a decimal point to the field in the image area. Determines how the data in the field is to be justified. Data can be right, left, or center justified. The following fields determine how a field operates in the screen table. For valid values, press PF1.
Type Y if you want to protect a field and use it only for display purposes. If the field is not protected (N), the user can enter data in the field. A screen field cannot be both required and protected. Type N if you do not want the contents of the field to be shown. An example of this could be a field used for a password. Type Y if you want the user to be required to provide a value in the field. A field requires data only if an occurrence exists to validate. Phase Two validation ensures you supply this data. A screen field cannot be both required and protected. Specify Y if you want the cursor to automatically skip to the next field when the last character of the field is entered. Specify Y if you want the unused portion of the field to be filled with nulls. If the unused portion is filled with nulls, insertions are allowed as nulls can be overwritten. If the unused portion is filled with blanks, no insertions can be made into the field as blanks are characters.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |