7.0 Changelog

When we switch to form through view toolbar from calendar/cards view then it should open first available record in form. If no records are available then it should skip navigation to form view.

When we switch to form through view toolbar from grid view Then if any row is selected then it should open in form else open the first available record in grid. If no records are available then it should skip navigation to form view.

When tree view nodes are on same model, this allow to move nodes to root, using draggable area in bottom of the view.

This fix several issues in tree view :

Reduce collaboration avatar height so that it does not increase toolbar height once shown. Also fix grouped avatars icon width.

When click on card to open form from kanban column then it should allow to do pagination(prev/next) for that column set of records in form view.

Formatting with x-currency was working on grid, but missing on decimal form widget.

Resetting domain on relational fields by returning null domain on onSelect event is not takes into account and existing domain is still used.

Changing fields focus attrs hasn’t any effect if refocus same field again. This also fix unfocusable M2O fields.

When showIf/hideIf is specified with nav-select widget on m2o field Then it was displaying m2o selection along with nav-select. It should only display nav-select widget.

This also fix wrong values displayed in grid for custom fields.

Make sure to map values from the previous concatenation that was using Comma-separated + space.

When single tab is enabled, any tab is already opened then it should first close the current tab and open new tab as single tab only.

Don’t display radio/checkbox select items onto one line but wrap them depending on available space (break into multiple lines).

In grid, RadioSelect/CheckboxSelect widget can’t be used for obvious display reason. When they are used, use default selection widget for RadioSelect and MultiSelect widget for CheckboxSelect.

SQL injection is possible when using the non-default connection property preferQueryMode=simple in combination with application code that has a vulnerable SQL that negates a parameter value.

See https://www.cve.org/CVERecord?id=CVE-2024-1597

As we are using the default query mode, we aren’t impacted. But administrators can still change the JDBC URL themself to use the impacted query mode.

Issue happened when there is a dotted field without its parent, eg. "product.code" field, but no "product" field.

api.pagination.max-per-page was taken into account on page text only. api.pagination.default-per-page was not taken into account.

If a dashlet or a collection field isn’t visible (either hidden or in a non active panel-tab), data should’t be fetched. Data should then fetched (if required) as soon as the widget is visible.

To avoid flashing issue on dotted field change, dotted field value is rendered and updated through state and state update will be defer during action execution.

Kanban card record should have preference over the action view context. Also improve context by removing unnecessary values like renderer etc.

When setting values from actions (both action-attrs or action-record), cause the id field value to be erased. In most cases, this shouldn’t be an issue but on new record (without id), and having id in context cause the id in context do be erased.

Relational fields displayed in editor wasn’t saved with main record due to missing version fields when value set through action. Moreover, after the value as saved, the new version value wasn’t sync, so subsequent update triggerred concurrent update errors.

Issue happened in two cases on o2m grid.

First one is when changing from a m2o record that has a translation to another one that has no translation. Translation from previous record was wrongly kept.

Second one is when changing from a m2o record that has a dotted value to another one that has no dotted value. Dotted value from previous record was wrongly kept.

Action was receiving o2m items in fetched order, not grid order.

Instead of comparing with previous row values to determine if the record is dirty, we now pass dirty state from popup record and editable row record.

This avoids fields blinking when entering in editable grid because they switch quickly from edit to read only mode.

When a grid has both a relational field (ie product.category) and na associated dotted field (ie product.category.code), enter in editable mode cause the grid widget to crash (object is not extensible error).

As soon as a row record is updated from popup view, reopening the popup for the same row will not trigger another fetch request, as the record is already fetched. This reduce number of requests.

If a O2M field with an editable grid is a non-dirty field, row changes were lost after committing. Need to compare record equality instead of the _dirty flag (not relevant in that case).

On existing row, after edit, dotted fields were reverted to previous value. Nested values were updated, but grid relies on dotted fields.

Issue happened when opening an existing record in form view then clicking on create new record. O2M values from previous record were kept.

Issue happens when o2m values are set through actions and those values are not persisted (either computed or id is set to null) and on initial re-ordering, grid gets empty.

This allow to use TagSelect widget in grid. It will display records as badge. Full list will be displayed on mouse over when records can’t be displayed in the grid cell. target-name is at this time not supported.

On the message stream widget, users can choose the messages types to display.

Moreover, on the view definition, the filter attribute can be used to specify messages type to show by default : all (default), comment, notification.

If the view field is marked as x-dirty="false", the field value change will not mark current record dirty.

The old dirty checking behavior of the $ prefixed fields is now deprecated and will be removed during next major release.

Drop current Angular front-end in favor of new front-end build on top of React.

The {user.dir} refers to the current working directory. It is useful during development where you have many different instances to test with.

For example:

will store upload files under data/axelor found under current working directory.

The $fmt helper accepts an optional props param to pass custom field props (currency, scale, second, …​) : $fmt("myField", { scale: 6 })

Provide a Gradle plugin to simplify changelog management.

Each entry of the CHANGELOG.md file is generated from files in the changelogs/unreleased/ folder.

To use the plugin, in your build.gradle :

To generate the CHANGELOG.md with unreleased entries, run following Gradle task: ./gradlew generateChangelog

Open dashlet edit in popup (instead of new tab). (This is currently for grid dashlet only. Other dashlet types always open popup.) After closing, dashlet has up-to-date data for the record that was opened and edited. (Search request may be performed by some dashlet types to achieve that result, but it’s room for later improvement.)

Reload current tab after closing popup from dashlet. If the tab is dirty before opening the popup, save confirmation dialog is shown before proceeding.

Normally, form client is the default client used for authentication. When an authentication provider is defined as exclusive, form client is not loaded at all.

Now, with auth.provider-default configuration, you can specify another non-exclusive client as default.

Example:

You can specify another client via the client_name query parameter in login URL.

Example:

Add x-can-export attributes on O2M metaFields on MetaModel form view

With canMove, the field used for sequencing does not have to be a field named sequence anymore, but can be any field specified by orderBy.

Sequencing is done on field specified by orderBy, and it must be only one integer field. If not specified, not sequencing is done.

On top-level grid, canMove requires orderBy.

action-menu elements can now be defined inside a search view to specify that they are specific to that view, and not available to all search views.

These settings allow to define an application icon used for website favicon and small logo. They can be used similarly to the application.logo and context.appLogo settings. The icon must be a multiple of 48px square for favicon compatibility with most browsers.

Rating widget can be used on Integer,Long and Decimal field. It provides ability to collect measurable opinions/experiences/feedbacks/…​

Example :

/ws/public/app/info either gives application login info or session info if the user is logged in. /ws/app/info is deprecated and will be dropped in a future release.

The flag associated to the user and message is now retrieved on backend. This avoids duplicated mail flags after reflagging messages. As part of the change, the message is also required and indexes as been reviewed.

Run following SQL script to adjust MailFlag table changes :

Restructured _domainContext for collection field search request:

As part of the new v7 front-end built on top of React, x-code-theme is no more supported. It will be re-added in a future version.

Remove special case for User/Group records where we added a dummy __actionSelect field. Instead, use ref-select widget on homeAction.

Instead of checking using module name, use specific feature to discover if studio module is used. This can be enabled using Studio feature.

Example of how to enable the Studio feature from the module:

or using features.studio = true in `axelor-config.properties.

Checkbox selection in grid is now enabled by default.

Change to view.grid.selection = none to disable it globally.

For collection fields, if the editor isn’t marked with x-viewer="true" and doesn’t have any viewer defined, the editor is no more used in readonly mode. The default rendering behavior will be used instead (ie grid). This is more consistent with others fields behavior.

x-show-bars actions used to affect parent form. Now, they affect local grid context only.

Here are the changes of the shortcuts :

Changed :

Added :

Due to historical reason, any users passwords stored in plain text in the database are encrypted on startup. On databases having large number of users, it is unnecessary time consuming on startup.

To reset a forgotten admin password, update or insert an active admin user with a temporary password 'admin123' in database using the hashed password :

Another way to generate passwords, is to use the Apache Command Line Hasher :

Also, if you import users with passwords from any source, either password must be hashed or you can use helpers methods to encrypt it :

The create on the fly feature control by the x-create attribute is used to quickly create records and/or pre-filled values base on the current search input.

Previously, any fields named code, name and the namecolumn of the object were filled by default. This is no more the cases: only the field names provided in the x-create attribute will be.

The setting view.grid.editor-buttons has been removed. It was use to show confirm/cancel buttons from grid row editor.

This was never intended to be used. Stick to direct field access: myField, not $context.myField.

DMS spreadsheet is not implemented in community version of new frontend.

Enable or disable internal features using AppSettings.enableFeature or AppSettings.disableFeature.

Example of how to enable the DMS spreadsheet feature from the module:

or using features.dms-spreadsheet = true in `axelor-config.properties.

The setting view.confirm-yes-no has been removed. It was used to show confirm dialog with yes/no buttons (else is Cancel/OK).

Custom Style (provided from special context setting context.appStyle) has been dropped. There is no replacement at this time.

StaticResourceProvider, used to register custom css or js files, has been dropped. There is no replacement at this time.

Custom theme is no more supported and has been dropped. There is no replacement at this time.

Extra partial JSP templates support is no more supported and has been dropped. There is no replacement at this time.

In this new version of the frontend, top menus aren’t supported anymore.

Run following SQL script to drop unnecessary columns :

The setting view.menubar.location has been removed. It was used to set menu style (left, top, both). There is no more support of top menus.

In a CSV data import, we can log the rows with an error in a new CSV file. They used to be logged in the XML config file.

When fetching the menus, if a menu is parent of itself or having wrong parent references, it load indefinitely. A log will be displayed in console for menus that can’t be added to N-ary Tree.

In a CSV data import, if we log the error rows in a file, a StackOverflowError was thrown when more than 2 CSV files have some errors.

If an error occurs when evaluating menu conditions (ie script errors), it shouldn’t fail the all process, but don’t display the failed menus.

For datetime field, the tracking value stored in database should be in UTC so that it will be displayed depending on user timezone.

In search request, need to check parent really has requested items. Otherwise, it is possible to specify unrelated parent and bypass permissions.