Field Loop Expansion Tokens

 

Field loop expansion tokens are used to insert information about the current field being processed within the context of a field loop into the output stream. Field loop tokens can only be used inside a field loop.

Field Loop Token

Description

<FIELD#>

Inserts the 1-based index of the current field in the record, without considering array elements or group fields as individual fields.

See also: <FIELD#_ZERO>, <FIELD#LOGICAL>, <FIELD#LOGICAL_ZERO>

<FIELD#_ZERO>

Inserts the 0-based index of the current field in the record, without considering array elements or group fields as individual fields.

See also: <FIELD#>, <FIELD#LOGICAL>, <FIELD#LOGICAL_ZERO>

<FIELD#LOGICAL>

Inserts the 1-based index of the current field in the record. Array elements and group fields are considered as individual fields. For example a structure with three fields, one of which is an array of 8 elements, is treated as having 10 fields.

See also: <FIELD#>, <FIELD#_ZERO>, <FIELD#LOGICAL_ZERO>

<FIELD#LOGICAL_ZERO>

Inserts the 0-based index of the current field in the record. Array elements and group fields are considered as individual fields. For example a structure with three fields, one of which is an array of 8 elements, is treated as having 10 fields.

See also: <FIELD#>, <FIELD#_ZERO>, <FIELD#LOGICAL>

<FIELD_ALTNAME>

Inserts the alternate name of the field. Array fields are represented in Synergy format, for example ALTNAME[1]. If no alternate name is available then the real name is used.

Alternates:  <field_altname> <Field_Altname> <Field_altname> <FieldAltname> <fieldAltname>

See also: <FIELD_BASENAME>, <FIELD_NAME>, <FIELD_NETNAME>, <FIELD_NET_ALTNAME>, <FIELD_ODBCNAME>, <FIELD_ORIGINAL_NAME>, <FIELD_SQL_ALTNAME>, <FIELD_SQLNAME>

<FIELD_ARRIVEM>

Inserts the name of the fields arrive method if present, or by nothing if not.

Alternates:  <field_arrivem> <Field_Arrivem> <Field_arrivem> <FieldArrivem> <fieldArrivem>

See also: <FIELD_CHANGEM>, <FIELD_DRILLM>, <FIELD_HYPERM>, <FIELD_LEAVEM>

<FIELD_BASENAME>

Inserts the base name of the field. Array field dimensions are not included in the base name.

Alternates:  <field_basename> <Field_Basename> <Field_basename> <FieldBasename> <fieldBasename>

See also: <FIELD_ALTNAME>, <FIELD_NAME>, <FIELD_NETNAME>, <FIELD_NET_ALTNAME>, <FIELD_ODBCNAME>, <FIELD_ORIGINAL_NAME>, <FIELD_SQL_ALTNAME>, <FIELD_SQLNAME>

<FIELD_BREAK_MODE>

Inserts a value indicating whether the field is a break field, and if so what type of break field.

Possible Values: "None", "Change", "Always", "Return"  (quotes not inserted)

<FIELD_CHANGEM>

Inserts the name of the fields change method if present, or by nothing if not.

Alternates:  <field_changem> <Field_Changem> <Field_changem> <FieldChangem> <fieldChangem>

See also: <FIELD_ARRIVEM>, <FIELD_DRILLM>, <FIELD_HYPERM>, <FIELD_LEAVEM>

<FIELD_CLASS>

 

Inserts the name of the fields class, if present. Only date, time and user-defined fields can have a class assigned.

 

Possible Values: YYMMDD, YYYYMMDD, YYJJJ, YYYYJJJ, YYPP, YYYYPP, HHMMSS, HHMM, UserAlpha, UserBinary, UserDate, UserNumeric

<FIELD_COL>

Inserts the screen column for placement of the field on the screen in a cell-based environment. If the field has a column position specified then this is used, otherwise the default of column 15 is used.

See also: <FIELD_DRILL_PIXEL_COL>, <FIELD_PIXEL_COL>, <FIELD_PIXEL_ROW>, <FIELD_PIXEL_WIDTH>, <FIELD_ROW>, <PROMPT_COL>, <PROMPT_PIXEL_COL>, <PROMPT_PIXEL_ROW>, <PROMPT_PIXEL_WIDTH>, <PROMPT_ROW>

<FIELD_CSCONVERT>

Inserts a string indicating the appropriate C# string to numeric conversion method to use to attempt to parse a string into a numeric value. For non-numeric fields the token is replaced by nothing.

Possible values: bool.TryParse, byte.TryParse, decimal.TryParse, double.TryParse, int.TryParse, float.TryParse, long.TryParse, sbyte.TryParse, short.TryParse, uint.TryParse, ulong.TryParse, ushort.TryParse

See also: <FIELD_CSDEFAULT>, <FIELD_CSTYPE>

<FIELD_CSDEFAULT>

Inserts a C# default value based on the fields data type.

Possible values: "", 0, false, new DateTime(), null

See also: <FIELD_CSCONVERT>, <FIELD_CSTYPE>

<FIELD_CSTYPE>

Inserts a string indicating the C# equivalent data type of the field.

Possible values: bool, byte, double, float, int, long, decimal, DateTime, Nullable<DateTime>, sbyte, short, string, uint, ulong, ushort

See also: <FIELD_CSCONVERT>, <FIELD_CSDEFAULT>

<FIELD_CUSTOM_DBL_TYPE>

 

Inserts a custom DBL data type of a field, if present. Otherwise inserts the same value as <FIELD_SPEC>.

 

Developers can specify a custom value via a special token in the fields user text or long description, like this:

 

CUSTOM_DBL_TYPE=d5.2;

 

The name of the token MUST be specified in upper case and the value MUST be terminated by a semi-colon, as shown above.

 

See also: <FIELD_CUSTOM_SQL_TYPE>, <FIELD_CUSTOM_CONVERT_FUNCTION>, <FIELD_CUSTOM_STRING_FUNCTION>, <FIELD_SPEC>, <FIELD_SQLTYPE>

<FIELD_CUSTOM_SQL_TYPE>

 

Inserts a custom SQL data type of a field, if present. Otherwise inserts the same value as <FIELD_SQLTYPE>.

 

Developers can specify a custom value via a special token in the fields user text or long description, like this:

 

CUSTOM_SQL_TYPE=DECMIAL(5,2);

 

The name of the token MUST be specified in upper case and the value MUST be terminated by a semi-colon, as shown above.

 

See also: <FIELD_CUSTOM_DBL_TYPE>, <FIELD_CUSTOM_CONVERT_FUNCTION>, <FIELD_CUSTOM_STRING_FUNCTION>, <FIELD_SPEC>, <FIELD_SQLTYPE>

<FIELD_CUSTOM_CONVERT_FUNCTION>

 

Inserts the name of a custom data conversion function associated with a field., if present. Otherwise inserts nothing. The custom convert function should accept a single parameter which is of the actual data type of the real field, and have a return value which is the custom data type as defined by <FIELD_CUSTOM_DBL_TYPE>.

 

Developers can specify a custom value via a special token in the fields user text or long description, like this:

 

CUSTOM_CONVERT_FUNCTION=DivideBy100;

 

The name of the token MUST be specified in upper case and the value MUST be terminated by a semi-colon, as shown above.

 

You can test if a field has a custom convert function specified with <IF CUSTOM_CONVERT_FUNCTION>.

 

For example, if a field is a D5 and you wish to process it as a D5.2 then you might set the following values in the long description:

 

CUSTOM_DBL_TYPE=D5.2;

CUSTOM_SQL_TYPE=DECIMAL(5,2);

CUSTOM_CONVERT_FUNCTION=DivideBy100;

CUSTOM_STRING_FUNCTION=DivideBy100ToString;

 

And the custom convert function might look like this:

 

function DivideBy100, d.

    required in decimalValue, n

proc

    freturn decimalValue / 100.0

endfunction

 

See also: <FIELD_CUSTOM_DBL_TYPE>, <FIELD_CUSTOM_SQL_TYPE>, <FIELD_CUSTOM_STRING_FUNCTION>, <FIELD_SPEC>, <FIELD_SQLTYPE>

<FIELD_CUSTOM_STRING_FUNCTION>

Inserts the name of a custom data conversion function associated with a field., if present. Otherwise inserts nothing. The custom convert function should accept a single parameter which is of the actual data type of the real field, and have a return value which is the custom data type as defined by <FIELD_CUSTOM_DBL_TYPE> but formatted appropriately into a string value.

 

Developers can specify a custom value via a special token in the fields user text or long description, like this:

 

CUSTOM_STRING_FUNCTION=DivideBy100AsString;

 

The name of the token MUST be specified in upper case and the value MUST be terminated by a semi-colon, as shown above.

 

You can test if a field has a custom convert function specified with <IF CUSTOM_STRING_FUNCTION>.

 

For example, if a field is a D5 and you wish to process it as a D5.2 then you might set the following values in the long description:

 

CUSTOM_DBL_TYPE=D5.2;

CUSTOM_SQL_TYPE=DECIMAL(5,2);

CUSTOM_CONVERT_FUNCTION=DivideBy100;

CUSTOM_STRING_FUNCTION=DivideBy100ToString;

 

And the string convert function might look like this:

 

function DivideBy100ToString, string

    required in decimalValue, n

proc

    freturn %string(decimalValue/100.0)

endfunction

 

See also: <FIELD_CUSTOM_DBL_TYPE>, <FIELD_CUSTOM_SQL_TYPE>, <FIELD_CUSTOM_CONVERT_FUNCTION>, <FIELD_SPEC>, <FIELD_SQLTYPE>

<FIELD_DEFAULT>

Inserts the fields default value, if present.

<FIELD_DESC>

Inserts the description of the field.

See also: <FIELD_INFOLINE>, <FIELD_LDESC>

<FIELD_DIMENSION1_INDEX>

When CodeGen encounters array fields it expands them into multiple fields each of which is of the same type and size. When processing a field which was formally part of an array, this token can be used to insert the original dimension one index of the field. For non-array fields inserts a single zero (0).

See also: <FIELD_ELEMENT>, <FIELD_ELEMENT0>

<FIELD_DIMENSION2_INDEX>

When CodeGen encounters array fields it expands them into multiple fields each of which is of the same type and size. When processing a field which was formally part of an array with at least two dimensions, this token can be used to insert the original dimension two index of the field. For non-array fields or for array fields with only one dimension inserts a single zero (0).

See also: <FIELD_ELEMENT>, <FIELD_ELEMENT0>

<FIELD_DIMENSION3_INDEX>

When CodeGen encounters array fields it expands them into multiple fields each of which is of the same type and size. When processing a field which was formally part of an array with at least three dimensions, this token can be used to insert the original dimension three index of the field. For non-array fields or for array fields with less than three dimensions inserts a single zero (0).

See also: <FIELD_ELEMENT>, <FIELD_ELEMENT0>

<FIELD_DIMENSION4_INDEX>

When CodeGen encounters array fields it expands them into multiple fields each of which is of the same type and size. When processing a field which was formally part of an array with four dimensions, this token can be used to insert the original dimension four index of the field. For non-array fields or for array fields with less than four dimensions inserts a single zero (0).

See also: <FIELD_ELEMENT>, <FIELD_ELEMENT0>

<FIELD_DISPLAY_LENGTH>

 

If the current field has a non-zero display length specified then that length is inserted, otherwise nothing is inserted.

 

See also: <FIELD_INPUT_LENGTH>, <FIELD_SIZE>, <FIELD_VIEW_LENGTH>

<FIELD_DRILLM>

Inserts the name of the fields drill method if present, or by nothing if not.

Alternates:  <field_drillm> <Field_Drillm> <Field_drillm> <FieldDrillm> <fieldDrillm>

See also: <FIELD_ARRIVEM>, <FIELD_CHANGEM>, <FIELD_HYPERM>, <FIELD_LEAVEM>

<FIELD_DRILL_PIXEL_COL>

Inserts the pixel column for placement of a fields drill button on a form.

Example Output: 275

See also: <FIELD_COL>, <FIELD_PIXEL_COL>, <FIELD_PIXEL_ROW>, <FIELD_ROW>, <PROMPT_COL>, <PROMPT_PIXEL_COL>, <PROMPT_PIXEL_ROW>, <PROMPT_PIXEL_WIDTH>, <PROMPT_ROW>

<FIELD_ELEMENT>

For array fields inserts the one-based element number of the field currently being processed by the field loop. For multi-dimension arrays the token inserts a comma-separated list of current index numbers. For non-array fields the token does not cause anything to be written to the output stream.

Example Output:

For a non-array field:                              <no output>
For a single-dimensional array:           1
For a two-dimensional array:                    1,2
For a three-dimensional array:          1,2,3
For a four-dimensional array:           1,2,3,4

See also: <FIELD_DIMENSION1_INDEX>, <FIELD_ELEMENT0>

<FIELD_ELEMENT0>

For array fields inserts the one-based element number of the field currently being processed by the field loop. For multi-dimension arrays the token inserts a comma-separated list of current index numbers. For non-array fields the token inserts 0.

Example Output

For a non-array field:                              0
For a single-dimensional array:           1
For a two-dimensional array:                    1,2
For a three-dimensional array:          1,2,3
For a four-dimensional array:           1,2,3,4

See also: <FIELD_DIMENSION1_INDEX>, <FIELD_ELEMENT>

<FIELD_ENUMBASEVAL>

 

For enumerated fields, inserts the enumerated fields base value. The base value is the value assigned to the first member of the enumeration. For non-enumerated fields nothing is inserted.

 

Note: This token refers to UI Toolkit enumerated fields, which are numeric fields with an enumeration specified via the "Enumerated?" field on the fields Validation tab. This token does NOT refer to fields whose Type is set to Enum on the Field Definition page.

Example Output: 1

See also: <FIELD_ENUMLENGTH>, <FIELD_ENUMSTEPVAL>, <FIELD_ENUMWIDTH>

 

<FIELD_ENUMLENGTH>

 

For enumerated fields, inserts the maximum length of the fields’ enumerated values. For non-enumerated fields nothing is inserted.

 

Example Output: 12

See also: <FIELD_ENUMBASEVAL>, <FIELD_ENUMSTEPVAL>, <FIELD_ENUMWIDTH>

<FIELD_ENUMSTEPVAL>

 

For enumerated fields, inserts an enumerated fields step value. The step value is the number that is added to or subtracted from the base value for each of the second and subsequent enumeration members. For non-enumerated fields nothing is inserted.

 

Note: This token refers to UI Toolkit enumerated fields, which are numeric fields with an enumeration specified via the "Enumerated?" field on the fields Validation tab. This token does NOT refer to fields whose Type is set to Enum on the Field Definition page.

Example Output: 1

See also: <FIELD_ENUMBASEVAL>, <FIELD_ENUMLENGTH>, <FIELD_ENUMWIDTH>

 

<FIELD_ENUMWIDTH>

 

Inserts the pixel width for the maximum length of the fields’ enumerated values.

Calculated as the maximum length of the fields enumerated values multiplied by 12 pixels per character. This default character width can be overridden using the -cw command line option.

Example Output: 144

See also: <FIELD_ENUMBASEVAL>, <FIELD_ENUMLENGTH>, <FIELD_ENUMSTEPVAL>

<FIELD_FORMATNAME>

Inserts the name of the fields Repository format, or nothing if no format is specified.

See also: <FIELD_FORMATSTRING>

<FIELD_FORMATSTRING>

Inserts the format string value of the fields Repository format, or nothing if no format is specified.

 

See also: <FIELD_FORMATNAME>

<FIELD_GROUP_EXPAND>

 

This special field loop token should only be used in conjunction with the -g e or -g i command line options, which cause explicit and implicit group fields to me not expanded into individual fields. This token causes the remainder of template code in the current field loop to be processed for fields within the group field that is currently being processed. For additional information and examples, refer to Processing GROUP Fields.

 

<FIELD_GROUP_MEMBER_PREFIX>

 

For unexpanded group fields, inserts the name of the group member prefix, if defined. Otherwise inserts nothing.

 

Alternates:

<field_group_member_prefix> <Field_Group_Member_Prefix> <Field_group_member_prefix> <FieldGroupMemberPrefix> <fieldGroupMemberPrefix>

<FIELD_GROUP_STRUCTURE>

 

For unexpanded implicit group fields, inserts the name of the structure that defines the implicit groups members. Otherwise inserts nothing.

 

Alternates:

<field_group_structure> <Field_Group_Structure> <Field_group_structure> <FieldGroupStructure> <fieldGroupStructure>

<FIELD_HEADING>

Inserts the fields report heading. If no heading exists then the field prompt is used. If no prompt exists then the fields SQL name is used. Array fields will have the element number appended (e.g. Phone #1).

<FIELD_HELPID>

Inserts the fields help identifier if present.

<FIELD_HYPERM>

Inserts the name of the fields’ hyperlink method if present, or by nothing if not.

Alternates:  <field_hyperm> <Field_Hyperm> <Field_hyperm> <FieldHyperm> <fieldHyperm>

See also:  <FIELD_ARRIVEM>, <FIELD_CHANGEM><FIELD_DRILLM>, <FIELD_LEAVEM>

<FIELD_INFOLINE>

Inserts the fields’ information line text if present.

See also: <FIELD_DESC>, <FIELD_LDESC>

<FIELD_INPUT_JUSTIFICATION>

 

Inserts the input justification of the current field.

 

Possible Values:  Left, Right, Center

See also: <FIELD_REPORT_JUSTIFICATION>

<FIELD_INPUT_LENGTH>

Inserts the maximum number of characters that can be typed into a UI input field representing the current field.

For alpha fields the input length is the same as the field size.

For decimal fields the input length will be one byte longer than the field size if the field allows negative values.

For implied decimal fields the input length will be one byte longer than the field size to allow for the entry of a decimal point, and two bytes longer that the field size if the field allows negative values.

For integer fields the input length is based on the maximum number of bytes that are required in order to be able to enter the maximum value supported by the integer field, but bear in mind that this may allow your user to enter a value larger than that supported by the underlying field. For example, an I1 field which allows negative values is capable of storing values in the range of -128 to 127, so the input length for the field is 4, but when used to constrain the length of a UI field this would allows the user to enter a value in the range -999 to 9999.

See also: <FIELD_DISPLAY_LENGTH>, <FIELD_SIZE>, <FIELD_VIEW_LENGTH>

<FIELD_LDESC>

Inserts the fields long description.

See also: <FIELD_DESC>, <FIELD_LDESC2>, <FIELD_INFOLINE>

<FIELD_LDESC2>

 

Inserts a pre-processed version of the fields long description. The long description is actually an A1800 field, but the repository UI treats is as if it is a [30]A60 array. This token returns a string in which each element of the array that contains data is included in the resulting string, separated by two spaces.

 

For example, the following array:

 

    LDESC, [30]A60, "Option 1", "", "Option 2", "", "Option 3"

 

Would cause the following data to be inserted:

 

    Option 1  Option2  Option 3

 

See also: <FIELD_DESC>, <FIELD_LDESC>, <FIELD_INFOLINE>

<FIELD_LEAVEM>

Inserts the name of the fields leave method if present, or by nothing if not.

Alternates:  <field_leavem> <Field_Leavem> <Field_leavem> <FieldLeavem> <fieldLeavem>

See also: <FIELD_ARRIVEM>, <FIELD_CHANGEM>, <FIELD_DRILLM>, <FIELD_HYPERM>

<FIELD_MAXVALUE>

Inserts the maximum value which should be associated with a numeric field. The token should only be used for numeric fields, so you should only use it within an <IF NUMERIC> field loop expression.

See also: <FIELD_MINVALUE>

<FIELD_MINVALUE>

Inserts the minimum value which should be associated with a numeric field. The token should only be used for numeric fields, so you should only use it within an <IF NUMERIC> field loop expression.

if a field does not allow negative values then a minimum value of 0 will normally be returned. However if the field is also marked as required then a value of 1 is returned.

See also: <FIELD_MAXVALUE>

<FIELD_NAME>

Inserts the name of the field. Array fields are represented in Synergy real array format,  and group fields are represented by a full path.

Example Output:

ACCOUNT_NUMBER
PHONE[3]
ADDRESS.CITY
CONTACT[2].NAME

Alternates:  <field_name> <Field_Name> <Field_name> <FieldName> <fieldName>

See also: <FIELD_ALTNAME>, <FIELD_BASENAME>, <FIELD_NETNAME>, <FIELD_NET_ALTNAME>, <FIELD_ODBCNAME>, <FIELD_ORIGINAL_NAME>, <FIELD_SQL_ALTNAME>, <FIELD_SQLNAME>

<FIELD_NETNAME>

Inserts a .NET compatible name for the current field. Array fields are expanded to multiple individual fields, with the name being suffixed with the array element number, for example 'FIELDNAME1', 'FIELDNAME2' etc.

The token behaves identically to the <FIELD_SQLNAME> token.

Example Output:

ACCOUNT_NUMBER
PHONE3
ADDRESS_CITY
CONTACT2_NAME

Alternates:  <field_netname> <Field_Netname> <Field_netname> <FieldNetname> <fieldNetname>

See also: <FIELD_ALTNAME>, <FIELD_BASENAME>, <FIELD_NAME>, <FIELD_NET_ALTNAME>, <FIELD_ODBCNAME>, <FIELD_ORIGINAL_NAME>, <FIELD_SQL_ALTNAME>, <FIELD_SQLNAME>

<FIELD_NET_ALTNAME>

Inserts a .NET compatible version of the alternate name for the current field. Array fields are expanded to multiple individual fields, with the name being suffixed with the array element number, for example 'FIELDNAME1', 'FIELDNAME2' etc.

The token behaves identically to the <FIELD_SQL_ALTNAME> token.

Alternates:  <field_net_altname> <Field_Net_Altname> <Field_net_altname> <FieldNetAltname> <fieldNetAltname>

See also: <FIELD_ALTNAME>, <FIELD_BASENAME>, <FIELD_NAME>, <FIELD_NETNAME>, <FIELD_ODBCNAME>, <FIELD_ORIGINAL_NAME>, <FIELD_SQL_ALTNAME>, <FIELD_SQLNAME>

<FIELD_NOECHO_CHAR>

Inserts the character that should be used to represent each character typed into a field, in place of the actual character (think password fields).

If the current field being processed is a "no echo" field then the token will be replaced by the no echo character specified in the repository field definition, or by an asterisk (*) if no character is specified. If the field is not a "no echo" field then the token will be replaced by a null string.

See also: <IF ECHO>, <IF NOECHO>

<FIELD_OCDEFAULT>

Inserts an Objective-C default value based on the fields data type.

Possible values:

@""
0
0.0
NO
[NSDate new]

See also: <FIELD_OCTYPE>

<FIELD_OCTYPE>

Inserts a string indicating the Objective-C equivalent data type of the field.

Possible values:

BOOL
double
float
int
long int
NSDate
NSString
short int
unsigned int
unsigned long int
unsigned short int

See also: <FIELD_OCDEFAULT>

<FIELD_ODBCNAME>

Inserts an ODBC-compatible name for the current field. Array fields are expanded to multiple individual fields, with the name being suffixed with an underscore and the array element number, for example 'FIELDNAME_1', 'FIELDNAME_2' etc. Note however that using the alternate pascal-case (<FieldOdbcname>) or camel-case (<fieldOdbcname>) tokens will cause the underscore characters to be suppressed.

Alternates:  <field_odbcname> <Field_Odbcname> <Field_odbcname> <FieldOdbcname> <fieldOdbcname>

See also: <FIELD_ALTNAME>, <FIELD_BASENAME>, <FIELD_NAME>, <FIELD_NETNAME>, <FIELD_NET_ALTNAME>, <FIELD_ORIGINAL_NAME>, <FIELD_SQL_ALTNAME>, <FIELD_SQLNAME>

<FIELD_ORIGINAL_NAME>

Inserts the original name of the field as defined in the repository. A fields original name never changes, and does not include any array dimensions or paths resulting from the expansion of array or group fields.

Alternates:  <field_original_name> <Field_Original_Name> <Field_original_name> <FieldOriginalName> <fieldOriginalName>

See also: <FIELD_ALTNAME>, <FIELD_BASENAME>, <FIELD_NAME>, <FIELD_NETNAME>, <FIELD_NET_ALTNAME>, <FIELD_ODBCNAME>, <FIELD_ORIGINAL_NAME_MODIFIED>, <FIELD_SQL_ALTNAME>, <FIELD_SQLNAME>

<FIELD_ORIGINAL_NAME_MODIFIED>

 

Inserts the original name of the field as defined in the repository, modified to include any array dimensions or paths resulting from the expansion of array or group fields.

 

Alternates:  <field_original_name_modified> <Field_Original_Name_Modified> <Field_original_name_modified> <FieldOriginalNameModified> <fieldOriginalNameModified>

See also: <FIELD_ALTNAME>, <FIELD_BASENAME>, <FIELD_NAME>, <FIELD_NETNAME>, <FIELD_NET_ALTNAME>, <FIELD_ODBCNAME>, <FIELD_ORIGINALNAME>, <FIELD_SQL_ALTNAME>, <FIELD_SQLNAME>

<FIELD_OVERLAY_FIELD>

 

For overlay fields, inserts the name of the field being overlaid.

 

NOTE: This token should only be used when overlay fields are being included in processing via the -f o command line option.

 

Alternates:  <field_overlay_field> <Field_Overlay_Field> <Field_overlay_field> <FieldOverlayField> <fieldOverlayField>

See also: <FIELD_OVERLAY_OFFSET>, <FIELD_OVERLAY_SPEC>, <IF OVERLAY>, <IF OVERLAY_OFFSET>

 

<FIELD_OVERLAY_OFFSET>

 

For overlay fields, inserts the overlay offset within the field being overlaid, which might be 0 or a positive integer. For non-overlay fields, inserts nothing.

 

NOTE: This token should only be used when overlay fields are being included in processing via the -f o command line option.

 

See also: <FIELD_OVERLAY_FIELD>, <FIELD_OVERLAY_SPEC>, <IF OVERLAY>, <IF OVERLAY_OFFSET>

<FIELD_OVERLAY_SPEC>

For overlay fields, inserts the overlay specification that identifies what is being overlaid.

 

NOTE: This token should only be used when overlay fields are being included in processing via the -f o command line option.

 

Example Output:
@OTHERFIELD
@otherfield + 5

Alternates: <field_overlay_spec>

See also: <FIELD_OVERLAY_FIELD>, <FIELD_OVERLAY_OFFSET>, <IF OVERLAY>, <IF OVERLAY_OFFSET>

<FIELD_PAINTCHAR>

 

Inserts the paint character that would be used to represent each character if the current field is a paint field. The default paint character is an asterisk (*).

<FIELD_PAINTFIELD>

 

Inserts a string indicating whether the current field is a paint field.

 

Possible values:

Yes

No

 

<FIELD_PATH>

Inserts the path of the field. Array fields are represented in Synergy format, for example structure.fieldname[1]. 

Alternates:  <field_path> <Field_Path> <Field_path> <FieldPath> <fieldPath>

<FIELD_PATH_CONV>

Inserts the path of the field. Array fields are represented in Synergy format, for example structure.fieldname[1]. If the fields user text or long description contains an @UNMAPF=function; expression then the conversion function will also be applied.

Alternates: <field_path_conv>

<FIELD_PII_TYPE>

 

If a special "PII_TYPE" token has been added to the fields long description or user defined text field then this token extracts the specific type from that token and inserts it into the generated code.

 

The PII_TYPE token looks like this:

 

PII_TYPE=type;

 

The type  specified can be anything, and that value is what is inserted by this token. Common examples might be:

 

PII_TYPE=CREDIT_CARD_NUMBER;

PII_TYPE=PHONE_NUMBER;

PII_TYPE=SOCIAL_SECUTIRY_NUMBER;

 

See also: <IF PII_SCRUB>, <IF STRUCTURE_PII_FIELDS>

<FIELD_PIXEL_COL>

Inserts the pixel column for placement of the field within a UI form. If the field has a column position specified then this is used, otherwise the default of column 15 is used.

A default width of 12 pixels per character is used, and this can be overridden using the -cw command line option.

See also: <FIELD_COL>, <FIELD_DRILL_PIXEL_COL>, <FIELD_PIXEL_ROW>, <FIELD_PIXEL_WIDTH>, <FIELD_ROW>, <PROMPT_COL>, <PROMPT_PIXEL_COL>, <PROMPT_PIXEL_ROW>, <PROMPT_PIXEL_WIDTH>, <PROMPT_ROW>

<FIELD_PIXEL_ROW>

Inserts the pixel row for placement of the field within a UI form. If the field has a row position defined then this is used, otherwise the logical field number (which includes array elements) is used to calculate the default row.

A default height of 25 pixels per row is used, and this can be overridden using the -ch command line option.

See also: <FIELD_COL>, <FIELD_DRILL_PIXEL_COL>, <FIELD_PIXEL_COL>, <FIELD_PIXEL_WIDTH>, <FIELD_ROW>, <PROMPT_COL>, <PROMPT_PIXEL_COL>, <PROMPT_PIXEL_ROW>, <PROMPT_PIXEL_WIDTH>, <PROMPT_ROW>

<FIELD_PIXEL_WIDTH>

Inserts the pixel width for default sizing of the field when represented as a TextBox.

Calculated as the size of the field in characters multiplied by 12 pixels per character. This default character width can be overridden using the -cw command line option.

See also: <FIELD_COL>, <FIELD_DRILL_PIXEL_COL>, <FIELD_PIXEL_COL>, <FIELD_PIXEL_ROW>, <FIELD_ROW>, <PROMPT_COL>, <PROMPT_PIXEL_COL>, <PROMPT_PIXEL_ROW>, <PROMPT_PIXEL_WIDTH>, <PROMPT_ROW>

<FIELD_POSITION>

Inserts the one-based byte position of the field in the record.

<FIELD_POSITION_COL>

 

If the field has a field position specified, this token inserts the column position or offset value. Otherwise nothing is inserted.

<FIELD_POSITION_MODE>

 

Inserts the field position mode of the current field.

 

Possible Values:  None, Absolute, Relative

<FIELD_POSITION_ROW>

 

If the field has a field position specified, this token inserts the row position or offset value. Otherwise nothing is inserted.

<FIELD_POSITION_ZERO>

Inserts the zero-based byte position of the field in the record.

<FIELD_PRECISION>

Inserts the precision of an implied-decimal field or an empty string. Only the precision is inserted, with no leading period.

See also: <FIELD_PRECISION0>, <FIELD_PRECISION2>

<FIELD_PRECISION0>

Inserts the precision of an implied-decimal field or 0 for non implied decimal fields.

 

See also: <FIELD_PRECISION>, <FIELD_PRECISION2>

<FIELD_PRECISION2>

Inserts the precision of an implied-decimal field including a leading period, or an empty string.

See also: <FIELD_PRECISION>, <FIELD_PRECISION0>

<FIELD_PROMPT>

Inserts the fields prompt.

<FIELD_RANGE_MAX>

Inserts the numeric fields’ maximum value.

<FIELD_RANGE_MIN>

Inserts the numeric fields’ minimum value.

<FIELD_REGEX>

Inserts a regular expression that can be used to constrain and validate user input to a field based on the repository definition of the field. The regular expression inserted depends on the type of field.

Nature of field

Regular Expression

Description

A4

 ^.{0,4}$

Allows between 0 and 4 characters.

A4, required field

 ^.{1,4}$

Allows between 1 and 4 characters.

D4, no negatives

 ^[+]?[0]*[0-9]{0,4}$

Allows an optional + sign, followed by any number of leading zeros, followed by up to four numeric digits.

D4, allows negatives

 ^[+-]?[0]*[0-9]{0,4}$

Allows an optional + or - sign, followed by any number of leading zeros, followed by up to four numeric digits.

D4.2, no negatives

 ^[+]?[0]*[0-9]{0,2}(\.[0-9]{0,2}[0]*)?$

Allows an optional + sign, followed by any number of leading zeros, followed by up to two numeric digits, followed by an optional decimal point. If a decimal point is found then up to two numeric digits may follow, followed by any number of trailing zeros.

D4.2, allows negatives

 ^[+-]?[0]*[0-9]{0,2}(\.[0-9]{0,2}[0]*)?$

Allows an optional + or - sign, followed by any number of leading zeros, followed by up to two numeric digits, followed by an optional decimal point. If a decimal point is found then up to two numeric digits may follow, followed by any number of trailing zeros.

I4, no negatives

 ^[+]?[0]*[0-9]{0,10}$

Allows an optional + sign, followed by any number of leading zeros, followed by up to ten numeric digits.

I4, allows negatives

 ^[+-]?[0]*[0-9]{0,10}$

Allows an optional + or - sign, followed by any number of leading zeros, followed by up to ten numeric digits.

In the table above, the numbers shown in red are based on the size of the field being processed at the time.

Integer Fields

The regular expression for integer fields will constrain the number of characters entered, and restrict those characters to being numeric characters, but it will NOT restrict the user to only entering valid numeric values. For example, an i1 field can store up to 127, the regular expression will constrain the entry to 3 numeric characters but it will still be possible to enter an out of range value (e.g. 256).

Required Fields

Currently CodeGen only takes a fields "required" status into account for alpha fields. If an alpha field is required then the regular expression produced will require at least one character be present.

<FIELD_REPORT_JUSTIFICATION>

 

Inserts the report justification of the current field.

 

Possible Values:  Left, Right, Center

See also: <FIELD_INPUT_JUSTIFICATION>

<FIELD_ROW>

Inserts the screen row for placement of the field on the screen in a cell based environment. If the field has a row position defined then this is used, otherwise the logical field number (which includes array elements) is used to calculate the default row.

See also: <FIELD_COL>, <FIELD_DRILL_PIXEL_COL>, <FIELD_PIXEL_COL>, <FIELD_PIXEL_ROW>, <FIELD_PIXEL_WIDTH>, <PROMPT_COL>, <PROMPT_PIXEL_COL>, <PROMPT_PIXEL_ROW>, <PROMPT_PIXEL_WIDTH>, <PROMPT_ROW>

<FIELD_SAMPLE_DATA>

 

Inserts sample date for the field. This token is intended to be used for the generation of examples in documentation or API references.

 

The token first looks in the long description data for sample data defined like this:

 

    SAMPLE_DATA=123 Main Street;

 

If found then the value between SAMPLE_DATA= and the semi-colon is inserted. If not found then an appropriate generic value (ABC or 123, etc.) is inserted.

 

Sample data for alpha variables is surrounded by double quotes.

 

NOTE: This token only currently works with basic field types alpha, decimal, implied decimal, integer and boolean. For other field types nothing is inserted.

 

Possible Values:  "ABC", 123, 1.23, True, "Sample "

See also: <FIELD_SAMPLE_DATA_NOQUOTES>

<FIELD_SAMPLE_DATA_NOQUOTES>

 

Inserts sample date for the field. This token is intended to be used for the generation of examples in documentation or API references.

 

The token first looks in the long description data for sample data defined like this:

 

    SAMPLE_DATA=123 Main Street;

 

If found then the value between SAMPLE_DATA= and the semi-colon is inserted. If not found then an appropriate generic value (ABC or 123, etc.) is inserted.

 

Sample data for alpha variables is NOT surrounded by double quotes.<FIELD_SELECTIONS1>

 

NOTE: This token only currently works with basic field types alpha, decimal, implied decimal, integer and boolean. For other field types nothing is inserted.

 

Possible Values:  ABC, 123, 1.23, True, Sample

See also: <FIELD_SAMPLE_DATA>

<FIELD_SELECTION_COUNT>
 

Inserts the number of selection list values that are associated with the field. A value of 0 will be inserted for fields that do not have associated selection lists.

 

Example: 4

 

See also: <FIELD_SELECTIONS>, <FIELD_SELECTIONS1>

<FIELD_SELECTIONS>

If the field has a selection list defined, this token inserts a comma separated and quoted list of the fields’ selection list values, otherwise nothing is inserted.

Example: "Red","Green","Blue"

See also: <FIELD_SELECTION_COUNT>, <FIELD_SELECTIONS1>

<FIELD_SELECTIONS1>

If the field has a selection list defined, this token inserts a quoted string containing a pipe (|) delimited list of the fields selection list values, otherwise nothing is inserted.

Example:  "Red|Green|Blue"

See also: <FIELD_SELECTION_COUNT>, <FIELD_SELECTIONS>

<FIELD_SELECTIONS_COL>

 

If the field has a selection list or selection window and selection column defined, this token inserts the column position for the placement of the selection window. Otherwise nothing is inserted.

<FIELD_SELECTIONS_HEIGHT>

 

If the field has a selection list defined, this token inserts the maximum height in rows that the generated selection window should occupy vertically. Otherwise nothing is inserted.

<FIELD_SELECTIONS_ROW>

 

If the field has a selection list or selection window and selection row defined, this token inserts the row position for the placement of the selection window. Otherwise nothing is inserted.

<FIELD_SELLENGTH>

Inserts the maximum length of the fields’ selection list values.

<FIELD_SELWND>

Inserts the name of the selection window associated with the current field, always in uppercase.. If the field does not have a selection window then the token inserts nothing.

Bear in mind that if the -ws command line option is being used then CodeGen may have removed the selection window name from the field definition and replaced it with a selection list, based on the selection windows entries. In that case you can use a <SELECTION_LOOP> to process the selections.

Alternates:  <field_selwnd> <Field_Selwnd> <Field_selwnd> <FieldSelwnd> <fieldSelwnd>

Note that in repository the name of a fields selection window can be entered in a mixed case format. The <FIELD_SELWND_ORIGINAL> token allows you to use the name of the selection window exactly as it appears in the repository.

See also:  <IF SELWND>, <IF NOSELWND>

<FIELD_SELWND_ORIGINAL>

 

Inserts the name of the selection window associated with the current field exactly as defined in the repository (might be mixed case). If the field does not have a selection window then the token inserts nothing.

 

<FIELD_SIZE>

Inserts the size of the field in bytes.

See also: <FIELD_DISPLAY_LENGTH>, <FIELD_INPUT_LENGTH>, <FIELD_VIEW_LENGTH>

<FIELD_SNDEFAULT>

Inserts a Synergy .NET default value based on the fields data type.

Possible Values:  "", 0, false, new DateTime(), ^null,

See also:  <FIELD_SNTYPE>

<FIELD_SNTYPE>

Inserts a string indicating the Synergy NET data type of the field.

Possible Values:  boolean, byte, DateTime, decimal, double, float, int, long, @Nullable<DateTime>, short, String, ystem.SByte, System.UInt16, System.UInt32, System.UInt64

See also:  <FIELD_SNDEFAULT>

<FIELD_SPEC>

Inserts a Synergy data type definition for the field.

Example values: A15, D12.4, BOOLEAN

Alternates:  <field_spec> <Field_Spec> <Field_spec> <FieldSpec> <fieldSpec>

See also:  <FIELD_CSTYPE>, <FIELD_OCTYPE>, <FIELD_SQLTYPE>, <FIELD_TYPE>, <FIELD_TYPE_NAME>, <FIELD_VBTYPE>

<FIELD_SQLNAME>

Inserts a SQL-compatible name for the current field. Array fields are expanded to multiple individual fields, with the name being suffixed with the array element number, for example 'FIELDNAME1', 'FIELDNAME2' etc.

The token behaves identically to the <FIELD_NETNAME> token.

Alternates:  <field_sqlname> <Field_Sqlname> <Field_sqlname> <FieldSqlName> <fieldSqlName>

See also:  <FIELD_ALTNAME>, <FIELD_BASENAME>, <FIELD_NAME>, <FIELD_NETNAME>, <FIELD_NET_ALTNAME>, <FIELD_ODBCNAME>, <FIELD_ORIGINAL_NAME>, <FIELD_SQL_ALTNAME>

<FIELD_SQL_ALTNAME>

Inserts a SQL-compatible version of the alternate name for the current field. Array fields are expanded to multiple individual fields, with the name being suffixed with the array element number, for example 'FIELDNAME1', 'FIELDNAME2' etc.

The token behaves identically to the <FIELD_NET_ALTNAME> token.

Alternates:  <field_sql_altname> <Field_Sql_Altname> <Field_sql_altname> <FieldSqlAltname> <fieldSqlAltname>

See also:  <FIELD_ALTNAME>, <FIELD_BASENAME>, <FIELD_NAME>, <FIELD_NETNAME>, <FIELD_NET_ALTNAME>, <FIELD_ODBCNAME>, <FIELD_ORIGINAL_NAME>, <FIELD_SQLNAME>

<FIELD_SQLTYPE>

Inserts a SQL compatible data definition of the field. By default the data types for Microsoft SQL Server are used but you can select one of the other supported databases either by using the -database command line option, or by setting the CODEGEN_DATABASE_TYPE environment variable.

SQL Data Type Mappings

Synergy Data Type

SQL Server Type

MySQL Type

PostgreSQL Type

Alpha

VARCHAR(n)

VARCHAR(n)

VARCHAR(n)

Alpha (Binary)

CHAR(n)

VARBINARY(n)

CHAR(n)

Auto sequence

 

BIGINT

BIGINT

BIGINT

Auto time

 

BIGINT

BIGINT

BIGINT

Binary

 

CHAR(n)

VARBINARY(n)

CHAR(n)

Boolean

 

BIT

BOOLEAN

BOOLEAN

Date (YYYYMMDD)

 

DATE

DATE

DATE

Date (YYMMDD)

 

DATE

DATE

DATE

Date (YYYYJJJ)

 

DECIMAL(7)

DECIMAL(7)

NUMERIC(7)

Date (YYJJJ)

 

DECIMAL(5)

DECIMAL(5)

NUMERIC(5)

Date (YYYYPP)

 

DECIMAL(6)

DECIMAL(6)

NUMERIC(6)

Date (YYPP)

 

DECIMAL(4)

DECIMAL(4)

NUMERIC(4)

Decimal

DECIMAL(n)

DECIMAL(n)

NUMERIC(n)

Enum

 

INT

INT

INT

Implied Decimal

DECIMAL(n,p)

DECIMAL(n,p)

NUMERIC(n,p)

Integer (i1)

 

SMALLINT

TINYINT

SMALLINT

Integer (i2)

SMALLINT

SMALLINT

SMALLINT

Integer (i4)

INT

INT

INT

Integer (i8)

BIGINT

BIGINT

BIGINT

Structure field

 

VARCHAR(n)

VARCHAR(n)

VARCHAR(n)

Time (HHMMSS)

TIME(0)

TIME(0)

TIME(0)

Time (HHMM)

TIME(0)

TIME(0)

TIME(0)

User Defined Alpha

CHAR(n)

CHAR(n)

CHAR(n)

User Defined Numeric

CHAR(n)

CHAR(n)

CHAR(n)

User Defined Time-stamp (see below)

DATETIME2

TIMESTAMP

TIMESTAMP

User Defined Date (all others)

CHAR(n)

CHAR(n)

CHAR(n)

User-Defined Time-stamp Fields

User-defined time-stamp fields can be implemented in the same way as supported by xfODBC:

Define the field as a user-defined date type, length 20

Set the fields "user string" to ^CLASS^=YYYYMMDDHHMISSUUUUUU

Use the <IF USERTIMESTAMP> and <IF NOTUSERTIMESTAMP> expressions to detect the fields in field loops.

Use the SQL CONVERT function to convert a YYYYMMDDHHMISSUUUUUU string into a DATETIME2 value as required by SQL Server. Note that DATETIME2 fields are only supported from SQL Server 2008. An example of using CONVERT is shown below:

          a20field = %datetime

          a26field = %string(^d(a20field),"XXXX-XX-XX XX:XX:XX.XXXXXX")

Then when building your SQL statement you would do something like this

          sql = sql + "CONVERT(DATETIME2," + a26field + ",21)"

See also:  <FIELD_CSTYPE>, <FIELD_SPEC>, <FIELD_TYPE>, <FIELD_TYPE_NAME>, <FIELD_VBTYPE>

<FIELD_TEMPLATE>

Inserts the name of the Repository template from which the field inherited its attributes or by a null string if no template is referenced.

<FIELD_TKSCRIPT>

Inserts a UI Toolkit .field script file command for the field.

<FIELD_TSDEFAULT>

 

Inserts a TypeScript default value based on the fields data type.

 

Possible Values:  "", 0, 0.0, new Date(), false, null

<FIELD_TSTYPE>

 

Inserts a string indicating the VB.NET data type of the field.

 

Possible Values: string, number, Date, boolean

<FIELD_TYPE>

Inserts a character indicating the synergy data type of field.

Possible Values:  A, D, I

Alternates:  <field_type> <Field_Type> <Field_type> <FieldType> <fieldType>

See also:  <FIELD_CSTYPE>, <FIELD_OCTYPE>, <FIELD_SPEC>, <FIELD_SQLTYPE>, <FIELD_TYPE_NAME>, <FIELD_VBTYPE>

<FIELD_TYPE_NAME>

Inserts a string indicating the Synergy data type of field.

Possible Values:  ALPHA, AUTO SEQUENCE, AUTO TIME, BINARY, DATE, DECIMAL, IMPLIED, INTEGER, JULIAN, TIME, USER ALPHA, USER DATE, USER NUMERIC

See also:  <FIELD_CSTYPE>, <FIELD_SPEC>, <FIELD_SQLTYPE>, <FIELD_TYPE>, <FIELD_VBTYPE>

<FIELD_USER_TYPE>

 

For user-defined fields, inserts the fields user defined field type string, if present, otherwise inserts nothing.

<FIELD_UTEXT>

Inserts the fields’ user-defined text string.

<FIELD_VBDEFAULT>

Inserts a VB.NET default value based on the fields data type.

Possible Values:  "", 0, False, New DateTime(), Nothing

See also:  <FIELD_CSCONVERT>, <FIELD_VBTYPE>

<FIELD_VBTYPE>

Inserts a string indicating the VB.NET data type of the field.

Possible Values:  Boolean, Byte, DateTime, Decimal, Integer, Long, Nullable(Of DateTime), Short, String, System.Double, System.SByte, System.Single, System.UInt16, System.UInt32, System.UInt64

See also:  <FIELD_CSTYPE>, <FIELD_OCTYPE>, <FIELD_SPEC>, <FIELD_SQLTYPE>, <FIELD_TYPE>, <FIELD_TYPE_NAME>

<FIELD_VIEW_LENGTH>

 

If the current field has a non-zero view length specified then that length is inserted, otherwise nothing is inserted.

 

See also:  <FIELD_DISPLAY_LENGTH>, <FIELD_INPUT_LENGTH>, <FIELD_SIZE>

<MAPPED_FIELD>

Inserts the name of the mapped field in the mapped structure. To use this token you must use @MAP=structure; in the structures user text field or long description and @MAP=field; in each fields user text field or long description.

Alternates:  <mapped_field> <Mapped_Field> <Mapped_field> <MappedField> <mappedField>

See also:  <MAPPED_PATH>, <MAPPED_PATH_CONV>, Structure Mapping

<MAPPED_PATH>

Inserts the name of the mapped path in the mapped structure. To use this token you must use @MAP=structure; in the structures user text field or long description and @MAP=field; in each fields user text field or long description. 

Alternates: <mapped_path>

See also:  <MAPPED_FIELD>, <MAPPED_PATH_CONV>, Structure Mapping

<MAPPED_PATH_CONV>

Inserts the name of the mapped path in the mapped structure . To use this token you must use @MAP=structure; in the structures user text field or long description and @MAP=field; in each fields user text field. If there is also an @MAPF=function; in the user text or long description then that conversion function will also be applied.

Alternates: <mapped_path_conv>

See also:  <MAPPED_FIELD>, <MAPPED_PATH>, Structure Mapping

<PROMPT_COL>

Inserts the screen column for placement of the prompt on the screen in a character based environment. If the prompt has a column position specified in the repository then that value is used, otherwise the default of column 1 is used.

See also:  <FIELD_COL>, <FIELD_DRILL_PIXEL_COL>, <FIELD_PIXEL_COL>, <FIELD_PIXEL_ROW>, <FIELD_PIXEL_WIDTH>, <FIELD_ROW>, <PROMPT_PIXEL_COL>, <PROMPT_PIXEL_ROW>, <PROMPT_PIXEL_WIDTH>, <PROMPT_ROW>

<PROMPT_PIXEL_COL>

Inserts the pixel column for placement of the prompt on a windows form. If the prompt has a column position specified then this is used, otherwise the default of column 1 is used.

A default width of 12 pixels per character is used, and can be overridden using the -cw command line option.

See also:  <FIELD_COL>, <FIELD_DRILL_PIXEL_COL>, <FIELD_PIXEL_COL>, <FIELD_PIXEL_ROW>, <FIELD_PIXEL_WIDTH>, <FIELD_ROW>, <PROMPT_COL>, <PROMPT_PIXEL_ROW>, <PROMPT_PIXEL_WIDTH>, <PROMPT_ROW>

<PROMPT_PIXEL_ROW>

Inserts the pixel row for placement of the prompt on a windows form. If the prompt has a row position defined then this is used, otherwise the logical field number (which includes array elements) is used to calculate the default row.

A default height of 25 pixels per row is used, and can be overridden using the -ch command line option.

See also:  <FIELD_COL>, <FIELD_DRILL_PIXEL_COL>, <FIELD_PIXEL_COL>, <FIELD_PIXEL_ROW>, <FIELD_PIXEL_WIDTH>, <FIELD_ROW>, <PROMPT_COL>, <PROMPT_PIXEL_COL>, <PROMPT_PIXEL_WIDTH>, <PROMPT_ROW>

<PROMPT_PIXEL_WIDTH>

Inserts the pixel width for default sizing of the prompt when represented as a label.

Calculated as the size of the prompt in characters multiplied by 12 pixels per character. This default character width can be overridden using the -cw command line option.

See also:  <FIELD_COL>, <FIELD_DRILL_PIXEL_COL>, <FIELD_PIXEL_COL>, <FIELD_PIXEL_ROW>, <FIELD_PIXEL_WIDTH>, <FIELD_ROW>, <PROMPT_COL>, <PROMPT_PIXEL_COL>, <PROMPT_PIXEL_ROW>, <PROMPT_ROW>

<PROMPT_POSITION_COL>

 

If the field has a prompt position specified, this token inserts the column position or offset value. Otherwise nothing is inserted.

<PROMPT_POSITION_MODE>

 

Inserts the prompt position mode of the current field.

 

Possible Values:  None, Absolute, Relative

<PROMPT_POSITION_ROW>

 

If the field has a prompt position specified, this token inserts the row position or offset value. Otherwise nothing is inserted.

<PROMPT_ROW>

Inserts the screen row for placement of the prompt on the screen in a character based environment. If the prompt has a row position defined in the repository then that value is used, otherwise the logical field number (which includes array elements) is used to calculate the default row.

See also:  <FIELD_COL>, <FIELD_DRILL_PIXEL_COL>, <FIELD_PIXEL_COL>, <FIELD_PIXEL_ROW>, <FIELD_PIXEL_WIDTH>, <FIELD_ROW>, <PROMPT_COL>, <PROMPT_PIXEL_COL>, <PROMPT_PIXEL_ROW>, <PROMPT_PIXEL_WIDTH>

 

 


Copyright © 2021  Synergex International, Inc.