4.0 Migration Guide

In this document, we will see the major steps to migrate from 3.4 to 4.0.

Please check the change log for detailed list of fixes, changes and improvements introduced in 4.0.

Database migration

Migration scripts are available there.

Breaking Changes

If you have not overridden the code of BI module, you can ignore this section.

Upgrade dependencies

The following dependencies have been upgraded:

  • AOP to 8.0.0

  • Java to 21

  • Tomcat to 10

  • Gradle to 8.14.3

  • axelor-utils to 4.0.0

  • axelor-message to 4.0.0

  • axelor-studio to 4.0.0

  • axelor-guardian to 3.0

  • axelor-bi-library to 3.0.0

  • bi-studio-api-client to 3.0

  • snakeyaml to 2.5

  • embedded-sdk to 0.3.0

  • lombok to 1.18.42

  • httpmime to httpclient5 5.5.1

Constants removal

The following constants have been removed:

  • BiMapper.DONT_APPLY_FILTER

  • BiAuthUtils.BI_USER_ROLE_NAME

  • BiAuthUtils.BI_ADMIN_ROLE_NAME

Methods removal

The method BiAuthUtils.isUserWithRole has been removed.

Fields change

The string field BiDashboardFilter.operator has been replaced by an enumeration Operator.

Password encryption

To improve client security, the database password is now stored in encrypted form.

It is recommended to apply the SQL script below and then re-enter the database password in the app-bi-config form. This will ensure that the previously unencrypted password is replaced with the encrypted version.

UPDATE studio_app_bi SET db_password = NULL;