GBC 1.00.53 new features and upgrade notes

A summary of new features and changes in functionality introduced with Genero Browser Client (GBC) 1.00.53. Note the changes you may need to make when moving to this version of the GBC.

Important:

This version of GBC is desupported, use a more recent version of the product.

Important:

This page covers only those new features introduced with the Genero Browser Client version specified in the page title. Check prior new features pages if you migrate from an earlier version.

For a detailed list of GBC 1.00.53 changes, please refer to the list of fixes on our issue tracker.

Consolidated documentation

All documentation is now consolidated into a single manual, the Genero Browser Client User Guide.

Theme conditions

Two new theme conditions are available:


`isBrowser`	The running platform is a browser running in Native Rendering mode.
`isUR`	The running platform is a Genero front-end (the GDC desktop client or the GMA/GMI mobile client) running in Universal Rendering mode. Universal Rendering provides a common rendering solution for all front-end clients based on the GBC.

Important:

These two new conditions conflict, and cannot be used at the same time.

For more information, see Theme conditions.

New default themes

GBC 1.00.53 introduces four new default themes to differentiate browser-based rendering (Native Rendering) and Universal Rendering:


`ur_default`	Default GDC theme for Universal Rendering. Equivalent to the `default` theme, but enabling the context menu by default (see `theme-disable-context-menu`).
`ur_highcontrast`	Accessible GDC theme for Universal Rendering. Equivalent to the `highcontrast` theme, but enabling the context menu by default (see `theme-disable-context-menu`).
`ur_default_mobile`	Default GMI/GMA theme for Universal Rendering. Equivalent to the `default_mobile` theme.
`ur_highcontrast_mobile`	Accessible GMI/GMA theme for Universal Rendering. Equivalent to the `highcontrast_mobile` theme.

For more information, see Default themes.

Record and replay a session log

The methodology for recording and replaying a session log has changed. In addition, the log player now includes a pause button, and images can now be saved with the session log. For complete details, see the following topics:

Personalize customization version suffix

Personalize the version number suffix in your customizations builds. The default suffix is c (i.e. 1.00.53.c). To change it, define customizationSuffix in the root object of the config.json file of your customization.

Note:

The GBC runtime package name (created with the grunt option --create-zip) will now include this suffix, or c if not defined. For example, if you define the customizationSuffix as "mycust", the GBC runtime package filename will be fjs-gbc-1.00.53.mycust-build201904261023-customization_sample.zip.

For more information, see Change the version customization suffix.

Messages and Error behavior

Message and Error are now persistant by default. The message or error displays until the Close icon is clicked.

To have messages and errors close automatically, specify how long (in seconds) to display the message or error before closing with the themes variables theme-message-display-time and theme-error-display-time.

Collapsible GROUPS and accordion FOLDERS icon position

By default, the collapsible GROUPS and accordion FOLDERS icon is set to the left. To change this position, use these theme variables:


Variable	Comment
`theme-collapser-position`	Default behavior, set to "left" by default
`gbc-GroupWidget-collapser-position`	Default set to `theme-collapser-position` ("left")
`gbc-AccordionFolderWidget-collapser-position`	Default set to `theme-collapser-position` ("left")

This can also be achieved using the collapserPosition presentation style attribute, set on a Group or on an accordion folder. This style can be set to left (default) or right.

DISPLAY ARRAY and DOUBLECLICK

Prior to 1.00.53, a doubleclick on a row in a DISPLAY ARRAY would trigger the "accept" action, whether mobile or desktop. For a mobile application, this meant a double tap on a row would trigger the "accept" action.

Since 1.00.53, a doubleclick on a row in a DISPLAY ARRAY only triggers the "accept" action for a desktop application.

To trigger the "accept" action on a mobile device, add the DOUBLECLICK=ACCEPT attribute to the DISPLAY ARRAY statement. When set, the "accept" action is triggered by a single tap on the row. To trigger the "accept" action with a double tap on a mobile device (replicating the behavior of the pre-1.00.53 version), you must also add the "rowActionTrigger" style attribute and set it to "doubleClick".

For more information, refer to the Genero Business Development Language User Guide.