Release Notes

A job scheduler and an auto-retry mechanism have been introduced to generate dashboard snapshots asynchronously, handling cases where the process may take too long.

A new onlyLocalLibrary option in the App BI config allows restricting usage to the local library only, preventing elements from being fetched from remote servers.

The roles considered as the BI administrator can now be configured directly from the App BI config form, removing the hard-coded dependency on the bi.admin role name.

Users with the perm.bi.dashboard.rwd permission (Read/Write/Delete) can now delete dashboards. Only users with the bi.admin role have this permission by default.

BI dashboard menus now respect the roles and groups configured on the dashboard, ensuring access control is consistently applied.

Please check the change log for detailed list of changes and the 3.4 migration guide.

A new role bi.viewer has been introduced to control access to dashboards via menus.

A new field dbDisplayName has been added to manage the display name of a database connection.

Embedded dashboards are now filtered based on the allowed domains. Only dashboards authorized for the ERP domain can be embedded.

Dashboard menus are no longer dependent on axelor-studio. Existing menus are migrated from the studio-menu-dashboard- prefix to bi-dashboard-.

Please check the change log for detailed list of changes and the 3.3 migration guide.

Action buttons have been added to the LibraryDashboard form view.

A new toggle allows the App BI advanced settings to be editable.

Business-logic constants previously held in BiConstants have been refactored. API endpoint constants are now grouped in the new class BiEndpoint.

Please check the change log for detailed list of changes and the 3.2 migration guide.

It is now possible to configure an alternative URL for embedding dashboards from BI Studio, giving more flexibility in deployment scenarios.

BI database connection roles in BI Studio can no longer be automatically updated or assigned. A new field biDbRoleName must be set in the App BI configuration to specify the unique database access role.

Please check the change log for detailed list of changes and the 3.1 migration guide.

BI Studio configuration is no longer managed via axelor-config.properties. All configuration is now done through the App BI configuration page, supporting multi-tenant deployments out of the box.

Several legacy layers have been removed: BiUser model, auto-login to BI Studio, BI Local feature, AppBiInstance, LibraryInstance, and various related services and controllers.

The reader username and password are now pre-filled automatically when the App BI configuration is opened for the first time, simplifying the initial setup.

Please check the change log for detailed list of changes and the 3.0 migration guide.