7.1 Changelog

On actions executed from grid views, we can fetch current filters applied on the view using request.getCriteria(). it was initially only available if there are no records selected. To be consistent, it should also be available whatever records are selected or not. This shouldn’t have any impact. Selected records are available thought _ids in context, the current filter through request.getCriteria().

When a custom field has same name of model field, action called from form view was updating field in form but action called from json editor was updating field in the json editor. This was creating confusion depending on where the action was called. To uniformize behavior, form field gets preference over custom field (if same name). This can be breaking change, but use a custom field name same as the model field one isn’t recommended.

When widget defines both expression i.e. showIf and hideIf then it will first eval hideIf expression, if it returns true then it is considered to be hidden true else it will take and eval result of showIf expression.

This fixes updating custom fields attributes in views.

Custom field that are part of the default attrs json field, attributes can be updated either without prefix (<attribute for="test" name="hidden" expr="eval: true"/>) or without prefix (<attribute for="attrs.test" name="hidden" expr="eval: true"/>), no matter where the action is triggered in the view. This means that whether the action is triggered from a field event or a button in the main form or from a field event or button inside a json field, it works same.

For custom fields that are part of other json fields, attributes have to be updated with their respective prefix (<attribute for="myOtherJsonField.test" name="hidden" expr="eval: true"/>) or if the action is executed inside the json field, attributes can also be updated without prefix (<attribute for="test" name="hidden" expr="eval: true"/>).

When form contains dummy fields or x-dirty="false" items then when record is saved by clicking on ok, it should save record when those fields get changed regardless of form is not dirty.

js expressions have the priority over attributes set with action-attrs.

When written vertically, multiline text should grow from right to left.

When multiple records are selected in grid view then details view should be not open and should be close if opened.

Viewers are rendered when the form is ready, means that record is fetched. This avoids flashing issue, especially with Image inside viewers.

This fixes updating custom fields in views. Custom field that are part of the default attrs json field can be updated either without prefix (<attribute for="test" name="value" expr="eval: "some""/>) or without prefix (<attribute for="attrs.test" name="value" expr="eval: "some""/>), no matter where the action is triggered in the view. This means that whether the action is triggered from a field event or a button in the main form or from a field event or button inside a json field, it works same. For custom fields that are part of other json fields, they have to be updated with their respective prefix : <attribute for="myOtherJsonField.test" name="value" expr="eval: "some""/>. Both action-attrs and action-record are supported.

When we switch between grid to form and form back to grid, first time prev/next was having no effect.

Add support of readonly, hidden, hideIf, showIf, readonlyIf on tree-view button.

Starting from v7, the header logo doesn’t rely on the application.home link anymore but on the user home action if configured. application.home link is now added in the user dropdown menu as Home page item.

In calendar view, when we select some user filters, then on change of month/week/day, it should be restored.

Instead of hiding tab on unselect or deactivate by seleting different tab, Then it will use visibility:hidden style instead of display: none. Visibility will keep container height/width, so no re-calculation of style on select or activate.

This use pre-build color names hexadecimal code from axelor-front instead of the ones defined in axelor-ui. Also provide sass variables for all colors in order to re-use them.

This fixes default SSO authentication request blocked because of CORS policy.

When a group of actions return values, instead of using the last action result, merge the values.

This fixes cid field not marked as transient when Model class is enhanced. It was notably breaking advanced search export all.

Widget is supported on form and grid view. The phone widget renders the field as a phone number link in readonly mode, and as a phone number input with a country/region selector in edit mode.

Compared to implementation in previous front-end, x-custom-placeholder option is no longer supported.

Allow to use any printable characters in local part. Also remove upper limit on domain tld size.

View processors allow to programmatically add view widgets. They are automatically discovered on application startup, and they are executed in module resolution order, after finding view in MetaService::findView, which is used by view API endpoint.

Example:

Example:

This adds support to search if the target model as a target name available (ie namecolumn). Multi values search is also supported using ` | ` separator.

This adds support to use following domain : self.myM2O.attrs.myCustomFied = 'some'. It was restricted to first level only.

Two types of expandable widgets are supported with collection field/grid view

1.tree-grid (widget="tree-grid") (only supported on form collection field)

Options:

Note: onChange action will only work on top-level collection grid, while other actions defined like onNew/onLoad will work on nested editable grid line as well.

2.expandable (widget="expandable")

Options:

Notes:

Actions like onChange, onNew, onLoad will work as per schema definition defined in order-form or order-line-nested form. Options like x-tree-field, x-tree-limit, x-tree-field-title have no impact in case of expandable widget. If widget/summary-view are defined in specified grid-view, then it will automatically be used in panel-related, we don’t need it to specify. To disable it we can pass widget="one-to-many/many-to-many" depending on type of field.

We can now pass select map to the save and fetch requests to return object graph. If fields and related options are also given, they will be merged with the graph.

The format of the select map is as follow:

Support <hilite> elements on calendar view to define hiliting rules.

The hilite attributes are:

On password fields, this add a toggle icon at the end of the input in order to effortlessly hides/reveals password for enhanced security and convenience.

Collection fields can now be exported. This can be enabled using data.export.collections.enabled property. The default separator used is ` | . This can be changed using `data.export.collections.separator property.

Add missing getters and setters for view element attributes in package com.axelor.meta.schema.views.

The client can now set cid (collection id) to unsaved collection items to identify the same from the save and action responses.

Kanban columns can now be collapsed. An 'x-collapse-columns' property has been added, accepting a comma-separated list of column names that should be collapsed by default (reference fields not supported). This comes with other visual changes such as pagination and minor fixes.

OpenAPI v3 specifications are available at %URL%/ws/openapi Swagger UI is available at %URL%/#/api-documentation

This upgrade Gradle from 7.5.1 to 8.7.

Upgrade the Gradle Wrapper to benefit from new features and improvements : ./gradlew wrapper --gradle-version 8.7

This also include upgrade of Gradle plugins used.

Clients without session support (e.g. basic auth) should provide X-Tenant-ID header with every requests to select a tenant.

Clients with session support should send X-Tenant-ID header with login request.

copyWebapp Gradle task used to exclude development files used by previous axelor-web front-end. Now, it excludes hidden files only.

This align rendering and styles between card and kanban views. Mostly impact kanban views, some predefined styles as been removed in react template (img, h4). See migration notes.

At the initial stage of the multi-tenant implementation, it was allowed for a user to switch tenant. It was a convenient for testing and debugging. At this point it doesn’t seems to good option anymore, due to security risk and goal of multi-tenant. So the feature has been removed and no replacement is expected. db.%tenant%.roles property has been removed.

Search filter should exclude searching on id field. Even if it’s mentioned in targetSearch, it should be excluded.

When relational field is searched using popup in advanced search or in mass update popper, the popper should remain open and should not affect any click event happens in selector popup wizard.

When we have already search on some columns in grid view then if try to change limit in pagination(pager) then it is sending payload without searched criteria.

When user cleared the value manually through backspace/delete After that if value is set through action then it should use/display that value in date/datetime input.

When M2O is used as a selection (NavSelect widget or in Kanban#columnBy), exclude archived records.

When focus is set through action-attrs, select input text.

This fixes dirty form handling for both editable and non-editable grid.

This add support to scrollable year dropdown (+/- 50 years) and display the upcoming/previous arrows.

If parent container has a scroll, it create dragging row issue : the dragging element isn’t at the right position. wheel scroll is now disabled to avoid unexpected behavior.

If permission is found, access should be granted in case of no id. Without id, AuthSecurity::isPermitted had ids [null] and access was granted if permission filter result count happened to equal 1.

When exporting data, it should check permissions on each fields. For example, when exporting currency.symbol, it should first check if user can export currency field in Order entity, then if user can export symbol field on Currency entity.