7.3 Changelog

Due to latest change on json fields processing improvements, some json fields (either a field or panel, separator, …​) were missing in the view.

Native select used for time selection hangs on some browsers in popup. This is now renders in same way as year/month selection.

When requiredIf or validIf is used on relational field (with editor) then it should validate those conditions.

When any dummy field is not defined in view then it’s value shouldn’t be restore in form record state.

Here is the list of backend dependencies upgraded :

Special variables like _showSingle, _showRecord should not be forwared to form contexts.

When popup is opened from another popup with popup=reload then it should reload the tab view instead of reload closed popup view.

When popup editor is used directly on data views like grid, kanban, cards, calendar, gantt, dms etc then it should pass action context to popup editor.

As soon as clearing values on an editor item that is shown by default on records, the changes aren’t propagated to the parent record. So the parent don’t see the user changes and used wrong previous data that the one displaying in the editor.

Context app logo/icon methods can return an absolute url (ie a string). This fix parsing the url if it contains query params (merge with the default app base url).

It should be possible to render nested fields like <field name="user.code" /> in gantt view. Also that dotted field should be allow to use as taskSequence.

Contextual fields are filtered out in advance so that json fields aren’t processing every time at rendering.

This managed templates and expressions parsing errors (mostly due to incorrect syntax) : instead of crashing the view, errors are now caught and appropriate value returned depending on context.

Previous version introduce json field processing improvements. Due to the nature of the change, this introduced issue in json fields behavior. This has been reverted and will be re-added on further version.

A new JpaScanner#findEnums method added to find all value enums in the classpath.

A change in an internal hook, by using queueMicrotask instead of setTimeout improve queue task execution. This avoids unnecessary re-rendering if the callback updates state (mostly if used when fetching data).

Caught NPE when first loading logo seems to cause initial delay.

Contextual fields are filtered out in advance so that json fields aren’t processing every time at rendering.

Display formatted value of time widget in readonly. This will take into account if the field should display the seconds.

The data export directory is not multi-tenancy compatible. It should follow the multi-tenancy data upload directory structure by including the tenantId as child path.

When we add new record in grid then if we try to add more subsequent record by clicking again on + button by expecting to commit current edited row and add new row. But it was adding/commiting duplicate records.

MetaPermissions.canWrite should check CAN_WRITE instead of CAN_EXPORT

On decimal fields, the default step was determined by the current scale of the field. If a field with scale set to 2, default step would be 0.01. As it haven’t been adopted, it reverts back previous behavior, with a default step to 1 for decimal fields. So it is no more allowed to have a step depending on the dynamic scale of the field.

On not saved records in form editor popup, it shouldn’t show the attachment icon. Same for some custom form editor popups like user preferences.

Introduced new configuration properties to include/exclude classes/packages from OpenAPI scanning with following rules : class-level settings take precedence over package-level settings, exclusions take precedence over inclusions and the longest matching rule applies for packages. By default all classes are scanned (allow all, exclude some), except if some inclusions are defined (exclude all, include some).

Added properties: application.openapi.scan.exclude.packages, application.openapi.scan.exclude.classes, application.openapi.scan.packages, application.openapi.scan.classes

Set a custom dark logo for the login page if require a different one from application.logo-dark.

This allows to overwrite logUpdates attributes of entities. It can only enable change tracking feature for an entity.

Entities with logUpdates="false" doesn’t have change tracking enabled. So the created(On|By) and updated(On|By) fields aren’t available. When showing audit log popup, rely on createdOn field to check if change tracking is available for the entity. If not, display a notification instead of showing a popup with empty data.

ws/public/app/logo and ws/public/app/logo accept mode query parameter (light or dark). Application configuration context.appLogo and context.appIcon accept String mode parameter. Removed logo and icon from ws/public/app/info.

Previously, theme-builder used in template with custom component support. Now theme-builder is implemented as form widget and can used in form-view directly.

This fix API Swagger documentation error due to jackson version mismatch

When dms popup view is opened through custom process action-view then on clicking on file to view in tab, it should close popup view (same as attachment click behavior on form-view)

When constructor injection is used, search for events in the injection point class hierarchy.

This widget provides the ability to display a string value as a barcode in readonly mode. To customize the Barcode, use optional attributes height, x-barcode-width, x-barcode-line-color, x-barcode-display-value, x-barcode-background-color and x-barcode-format. The barcode is only displayed if the value is accepted by the format.

Barcode is also supported on viewers with the same attributes.

Add the ability to customize the increment and decrement amount using x-step attribute. Decimal and negative values are accepted. The default value is determined by the scale attribute if it exists, otherwise it is set to 1.

The linked grid view should have editable="true" to allow edit records in grids. To disable this behavior, you have to pass canEdit="false".

On MailMessage form, render recipient as SelectionTag. Allow to remove recipient from Tag.

When adding followers, validate recipients is filled, else it will display warning notification. Without any recipients, nothing will be done. The process only send message to the newest recipients.

This widget provides the ability to display a string value as a QR Code in readonly mode. To customize the QrCode size in px, use height attribute with a number value. Default to 140.

QrCode is also supported on viewers with attribute value.

Two new view params are added: popup.show-header and popup.show-footer.

This is for advance use cases where we want to show custom views inside a popup with it’s own header and footer.

The help variant is extracted from the css attributes values. Now, help widget has a new attribute variant that can be used, Accepted values are info, success, warning and error. Default value is info.

Here is the list of backend dependencies upgraded :

The help variant is extracted from the css attributes values. Now, help widget has a new attribute variant that can be used, css attribute usage to determinate the variant is deprecated.

On number fields, when changing sign, 0.5 was decremented to -1.5 instead of -0.5.

The gantt line should be aligned to table task row.

When any nested field of editor field is defined in form then it should fetched as editor field instead of form field.

On a form view, when first tab of panel-tabs contains showIf/hideIf expression, so initially it will be hidden and staring focus will be on tab which doesn’t contain showIf/hideIf expression. In this case, it should re-focus active tab to starting tab if starting tab is accessible.