The presented button uses a small part of the horizontal space assigned to the entire field. As a result, the total width of the item is slightly reduced in order to accommodate this button.

The button is only displayed when the item has focus.

The button cannot be customized. This lovButton should not be used in conjunction with the item property, Conceal Data Button.

When enabled, the design-time item property, LOV Button, is not honored at runtime.

Default: FALSE

Valid values: TRUE, FALSE

Default: FALSE

Enabled by setting app.ui.requiredFieldVA to TRUE. Enabling this overrides the design-time item property, Background Color.

The color value must be entered using the RGB format (such as 255,0,100).

Default: 255,0,0

When set to a valid RGB color (such as 255,0,0) and the item's Data Required property is set to YES, the item's border displays the set color for that item in the current record.

Upon navigating away from the current record, the border returns to its previous appearance.

This border setting takes precedence over other border settings.

The required border color appears on all four sides of the item, regardless of the selected border sides.

The Forms applet parameter, customColorScheme=<NAME> is required to enable this palette.

All colorScheme entries must have valid values. If any values are invalid or null, customColorScheme is ignored.

This parameter is not supported with the "Generic" look-and-feel.

The color value must be entered using either RGB (for example 255,0,100) or hex (for example 0xFF0064) format.

The Forms applet parameter, customColorScheme=<NAME> is required to enable this palette.

All colorScheme entries must have valid values. If any values are invalid or null, customColorScheme is ignored.

This parameter is not supported with the "Generic" look-and-feel.

The color value must be entered using either RGB (for example 255,0,100) or hex (for example 0xFF0064) format.

The Forms applet parameter, customColorScheme=<NAME> is required to enable this palette.

All colorScheme entries must have valid values. If any values are invalid or null, customColorScheme is ignored.

This parameter is not supported with the "Generic" look-and-feel.

The color value must be entered using either RGB (for example 255,0,100) or hex (for example 0xFF0064) format.

This is only visible when run embedded in a browser.

The Forms applet parameter, customColorScheme=<NAME> is required to enable this palette.

All colorScheme entries must have valid values. If any values are invalid or null, customColorScheme is ignored.

This parameter is not supported with the "Generic" look-and-feel.

The color value must be entered using either RGB (for example 255,0,100) or hex (for example 0xFF0064) format.

The Forms applet parameter, customColorScheme=<NAME> is required to enable this palette.

All colorScheme entries must have valid values. If any values are invalid or null, customColorScheme is ignored.

This parameter is not supported with the "Generic" look-and-feel.

The color value must be entered using either RGB (for example 255,0,100) or hex (for example 0xFF0064) format.

The Forms applet parameter, customColorScheme=<NAME> is required to enable this palette.

All colorScheme entries must have valid values. If any values are invalid or null, customColorScheme is ignored.

This parameter is not supported with the "Generic" look-and-feel.

The color value must be entered using either RGB (for example 255,0,100) or hex (for example 0xFF0064) format.

The Forms applet parameter, customColorScheme=<NAME> is required to enable this palette.

All colorScheme entries must have valid values. If any values are invalid or null, customColorScheme is ignored.

This parameter is not supported with the "Generic" look-and-feel.

The color value must be entered using either RGB (for example 255,0,100) or hex (for example 0xFF0064) format.

Specifies the color to be used for the Forms virtual color, OLAF3.

"pinstripe1" refers to the first stripe color of the two used when row banding is enabled.

The Forms applet parameter, customColorScheme=<NAME> is required to enable this palette.

All colorScheme entries must have valid values. If any values are invalid or null, customColorScheme is ignored.

This parameter is not supported with the "Generic" look-and-feel.

The color value must be entered using either RGB (for example 255,0,100) or hex (for example 0xFF0064) format.

Specifies the color to be used for the Forms virtual color, OLAF4.

"pinstripe2" refers to the second stripe color of the two used when row banding is enabled.

The Forms applet parameter, customColorScheme=<NAME> is required to enable this palette.

All colorScheme entries must have valid values. If any values are invalid or null, customColorScheme is ignored.

This parameter is not supported with the "Generic" look-and-feel.

The color value must be entered using either RGB (for example 255,0,100) or hex (for example 0xFF0064) format.

The Forms applet parameter, customColorScheme=<NAME> is required to enable this palette.

All colorScheme entries must have valid values. If any values are invalid or null, customColorScheme is ignored.

This parameter is not supported with the "Generic" look-and-feel.

The color value must be entered using either RGB (for example 255,0,100) or hex (for example 0xFF0064) format.

The Forms applet parameter, customColorScheme=<NAME> is required to enable this palette.

All colorScheme entries must have valid values. If any values are invalid or null, customColorScheme is ignored.

This parameter is not supported with the "Generic" look-and-feel.

The color value must be entered using either RGB (for example 255,0,100) or hex (for example 0xFF0064) format.

The item property. Show Border Sides, must be set to Yes to enable this feature.

When running with the Oracle look-and-feel, this parameter applies to edit/text items, display items, poplists, combo-boxes, tlists, spinlists, and image items.

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.border.bottom

Valid values: TRUE, FALSE

Default: TRUE

The color value must be entered using the RGB format (such as 255,0,100).

The Text item property, Show Border Color, must be set to Yes to enable this feature.

When running with the Oracle look-and-feel, this parameter applies to edit/text items, display items, poplists, combo-boxes, tlists, spinlists, and image items.

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.border.color

Default: 255,0,0

This parameter is intended to bring attention to an item, for example, when a user enters an invalid password.

The color value must be entered using the RGB format (such as 255,0,100).

When running with the Oracle look-and-feel, this parameter applies to edit/text items, display items, poplists, combo-boxes, tlists, spinlists, and image items.

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.border.highlightColor

Default: 255,0,0

The item property. Show Border Sides, must be set to Yes to enable this feature.

When running with the Oracle look-and-feel, this parameter applies to edit/text items, display items, poplists, combo-boxes, tlists, spinlists, and image items.

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.border.left

Valid values: TRUE, FALSE

Default: TRUE

The item property. Show Border Sides, must be set to Yes to enable this feature.

When running with the Oracle look-and-feel, this parameter applies to edit/text items, display items, poplists, combo-boxes, tlists, spinlists, and image items.

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.border.right

Valid values: TRUE, FALSE

Default: TRUE

The color value must be entered using the RGB format (such as 255,0,100).

The Text item property, Rollover Border Color, must be set to Yes to enable this feature.

When running with the Oracle look-and-feel, this parameter applies to edit/text items, display items, poplists, combo-boxes, tlists, spinlists, and image items.

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.border.rolloverColor

Default: 255,0,0

The item property. Show Border Sides, must be set to Yes to enable this feature.

When running with the Oracle look-and-feel, this parameter applies to edit/text items, display items, poplists, combo-boxes, tlists, spinlists, and image items.

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.border.top

Valid values: TRUE, FALSE

Default: TRUE

Value can be one of most typeable characters such as x.

Some non-typeable special characters can be used. To do so, enter \u followed by the Unicode identifier for the character. For example, use \u25cf to display a large dot.

Syntax: <serverApp value>.concealedData.character

Represents the font names that most closely match those used in the application at design-time.

The number of entries in the appFontnames list must match the number in the javaFontnames list.

The elements of the list are comma separated and all characters are taken literally. Leading and trailing spaces are stripped from face names.

Syntax: <serverApp value>.fontMap.appFontnames

The value for defaultFontname must be a font name that appears in the list of Java font names (from javaFontnames).

Syntax: <serverApp value>.fontMap.defaultFontname

Valid values:

• FULL: The built-in Java font mapping is used.

  If a specified font is not found in the appFontnames list, then the default font is used.

• PARTIAL: If an application's specified font is not found in the appFontnames list, the application's requested font is passed directly to Java

  Java attempts to use the specified font if found on the user's computer.

• NONE: The built-in Java font mapping is disabled, and the requested font is passed directly to Java

  Java attempts to use the specified font if found on the user's computer.

Syntax: <serverApp value>.fontMap.defaultMapping

Default: FULL

The value for font size is the desired point size multiplied by 100. For example, 9 pt should be entered as 900.

Syntax: <serverApp value>.fontMap.defaultSize

Syntax: <serverApp value>.fontMap.defaultStyle

Valid values: PLAIN, ITALIC

Syntax: <serverApp value>.fontMap.defaultWeight

Valid values: PLAIN, BOLD

The number of entries in the javaFontnames list must match the number in the appFontnames list.

The elements of the list are comma separated and all characters are taken literally. Leading and trailing spaces are stripped from face names.

There is a one-to-one positional relationship between the appFontnames and javaFontnames. Therefore, it is possible that some Java logical font names may be used more than once in the list.

For more information about Java logical fonts, see Physical and Logical Fonts in the Java documentation.

Syntax: <serverApp value>.fontMap.javaFontnames

Uses a range of -255 to 255. Any value that results in the color value going beyond either 0 or 255 is automatically limited to 0 or 255.

Using a positive value, such as 200, causes the color range to extend toward white. A negative value, such as -200, causes the color range to extend in the black direction.

Syntax: <serverApp value>.gradient.blueDelta

Default: 200

Uses a range of -255 to 255. Any value that results in the color value going beyond either 0 or 255 is automatically limited to 0 or 255.

Using a positive value, such as 200, causes the color range to extend toward white. A negative value, such as -200, causes the color range to extend in the black direction.

Syntax: <serverApp value>.gradient.greenDelta

Default: 200

Uses a range of -255 to 255. Any value that results in the color value going beyond either 0 or 255 is automatically limited to 0 or 255.

Using a positive value, such as 200, causes the color range to extend toward white. A negative value, such as -200, causes the color range to extend in the black direction.

Syntax: <serverApp value>.gradient.redDelta

Default: 200

Valid values: GIF, JPG, PNG

Syntax: <serverApp value>.icons.iconextension

Default: gif

The application level icon files are located relative to the DOCUMENTBASE. Either a relative or fully-qualified path can be used for the value.

Syntax: <serverApp value>.icons.iconpath

Setting to LEGACY results in the use of icons from versions prior to 12.2.1.x. Leaving unset results in the use of higher resolution and updated icons.

Syntax: <serverApp value>.icons.style

Valid values: LEGACY

Default: NULL

The color value must be entered using the RGB format (such as 255,0,100).

If no value is provided or an invalid value is provided, lines will not appear in the LOV. Each line is presented as a row of small dots. Solid lines are not supported.

Syntax: <serverApp value>.lovRowLine.color

This parameter is used by Forms to determine whether the background color for some item types is light or dark.

Forms uses this value to choose appropriately between two colors for the foreground in order to ensure readability: using a light color when the background is "dark" and a dark color when the background is "light".

The luminance value is on a scale of 0 to 255 with darker colors having lower values.

If this variable is not set, Forms uses 139 as the default threshold for that determination.

Valid values: 0-255

Default: 139

The color value must be entered using the RGB format (such as 255,0,100).

If no value is provided, the current foreground color is used, although muted.

Syntax: <serverApp value>.placeholder.color

Specifies whether the tabbed canvas tab bar background should be transparent.

When set to TRUE, any object behind the bar is visible in areas where there are no tabs (typically at the end of the bar).

This setting does not change the behavior of the tab labels or the tabbed canvas.

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.tabBar.transparent

Default: FALSE

The color value must be entered using the RGB format (such as 255,0,100).

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.tabLabel.selectedBgColor

The color value must be entered using the RGB format (such as 255,0,100).

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.tabLabel.selectedFgColor

The color value must be entered using the RGB format (such as 255,0,100).

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.tabLabel.unselectedBgColor

The color value must be entered using the RGB format (such as 255,0,100).

This parameter is not supported with the "Generic" look-and-feel.

Syntax: <serverApp value>.tabLabel.unselectedFgColor