7.4 Changelog

Previously, the React template component was being remounted entirely whenever the record context changed. This caused visible UI flicker and unnecessary teardown/re-initialization of the component, even when only the record data was updated.

This fix ensures that the template component now mounts only once, and instead of remounting, it will re-render efficiently in response to changes in the record context. This preserves component in dom by react and eliminates the flicker, resulting in a smoother user experience during form changes.

This impacts all fields viewers, label/static/help widgets, fields tooltip, kanban/cards/calendar/custom views.

The way from context was prepared was creating issues. The form context is a concatenation of the action view context values and the view/record values. But it was created in the wrong order : instead of appending view/record context values first and then the action view context values, it is now the reverse. The view/record context values should be priority over action view context values.

Means that if passing some data in action view context that can have the same names as the view/record context values, the latter will have priority.

This fixes an issue with chart/search views search-field requests : the model was coming from the action view instead of the form itself. In case of chart and search views (without search-form), the model is by default com.axelor.script.ScriptBindings.

When a "save" action occurs from a button inside an grid line, the save is now handle by the main record whatever if the grid is in edit or non-edit mode. It also ensure data integrity and correct state updates. The following sequence occurs :

It is not recommended to update the record after the save. action-view/report/validate can still occurs.

This fix few styles issues on NavMenu. As part of the changes, it also comes with improvements on NavMenu theming capabilities.

Modifying a view XML file that doesn’t contain view extensions incorrectly triggered a recomputation of all extended views.

Finding paths was not thread-safe and could occasionally cause missing paths to watch.

refresh-tab signal should be applied on active tab view, not on active view. Means that popups are excluded and only active tab view is reloaded (whatever view type is).

Allow to provide additional java mail properties for smtp and imap from properties file. Any java mail properties can be added using mail.<protocol>.properties. prefix.

For example : mail.smtp.properties.mail.smtp.ssl.trust = <host-name-of-mail-server>

It will prevent executing multiple time the same action if already in progress. Mostly related to save click in form view or popup dialog buttons.

In the grid customization popup, the reset and save buttons should first trigger the process. Then, if the action completes, close the popup. So that in case of error, the popup doesn’t close prematurely.

read record by id using GET method (ws/rest/<model>/<id>), should call the entity repository like any other web services that returns data.

Avoid grid unmount/mount during search requests causing some grid state resetting (scroll positions, …​)

On widgets using a mask (date/time,…​), previously adding characters causes existing characters to advance. And deleting characters causes existing characters to move back. Now adding or deleting characters will not affect the positions of existing characters.

On date/datetime, it also validates date parts (days/months/years) for valid inputs.

can* attributes (canNew, canEdit, …​) on form view allow javascript expressions and should be evaluated against the associated context.

The maven group id of the module is now stored in axelor-module.properties.

The view schema types are designed with JSON serialisation in mind. However, with the new studio designer, we also need proper JSON deserialisation support.

You can define maintenance mode behavior by implementing MaintenanceService:

Default maintenance page is error-503.html located in src/main/webapp directory. Note that you are free to override it if needed, by putting your own error-503.html in the src/main/webapp directory of your module.

Optimized the saving of audit tracking messages and followers by implementing batch processing. This improves performance, especially during operations that generate many tracking entries.

For the upcoming advance import/export feature (enterprise only), we need more fine grained data import permissions support.

This change adds an additional canImport permission option for objects and fields.

Run following SQL script to adjust auth_permission and meta_permission_rule tables changes :

Usage of the enterprise edition of the platform is evolving: it is no longer a matter of a single com.axelor:axelor-enterprise-edition module to rely on, but of different variant of the core modules.

As of now, to use enterprise edition, remove the dependency com.axelor:axelor-enterprise-edition and add the property axelor.platform.ee = true in your gradle.properties. This will automatically update your dependencies to use requires and right EE modules.

The last popup view should be used as the target view tab.

The Query instance obtained with MetaJsonRecordRepository#all(String) should filter custom records even if no additional filter provided.

When selection widget is rendered in readonly, it should open selection through any interactive events like key press, key up/down or element click.

Adding new hilite rules to fields were not working.