Broadleaf Microservices
  • v1.0.0-latest-prod

Tenant Services Release Notes for 2.1.4-GA

Tip
 The 2.x versions are Spring Boot 3 compatible.

Requirements

  • JDK 17 is required for Broadleaf release trains 2.0.0-GA, and beyond.

New Features & Notable Changes

  • Added new field DEFAULT_APPLICATION_ID to the BLC_TENANT table. The field value is used to pre-select application on user sign in. This setting can be overridden on user level. Makes sense only when user has access to applications and has applications assigned.

Enhancements

  • Removed the Content > Profiles view from the admin.

    • This view is chiefly utilized by Tenant users to configure profiles for Applications and did not make sense to surface to application level admins.

Bug Fixes

  • Added null handling on CatalogRef filters to prevent null value issues when reading from the DB.

Vendor Catalogs assigned in an Application’s Isolated Catalogs

Important

This is only relevant if broadleaf.common.data.application.configuration.allow-vendor-catalog-in-application-isolated-catalogs is enabled. Most clients do not use this feature, and can ignore these changes.

As of TenantServices 1.7.15+, 2.0.1+, and 2.1.0+, when a vendor catalog is assigned as one of an application’s isolated catalogs, the implicit catalog created for the relationship will also have its Catalog.vendorRef set to match its parent.

With these changes, we also included a migration script, which is responsible for ensuring any existing implicit catalogs in the datastore also have their vendorRef values correctly initialized.

If you have not already done so at the time you upgraded to one of those previous versions, please ensure to run that migration script now (it should still work on the current release). The changes in the current release rely on the datastore state being correct.

In the current release:

  • Updated the metadata to automatically filter/include vendor catalogs in the lookup results when assigning catalogs to an application, depending on the value of broadleaf.common.data.application.configuration.allow-vendor-catalog-in-application-isolated-catalogs

    • If you were previously overriding the metadata for this purpose, you can now remove your customizations as the default lookup should handle both scenarios

  • Relax the validations around vendor catalog assignments as isolated catalogs

    • Vendor catalogs can now be 'visible as assigned'

    • Vendor catalogs no longer have to be 'excluded from add'

Upgrade Guide

Migration notes

Note
 If using liquibase to pull in base Broadleaf changelogs, then it is not necessary to manually run this script.
Add column for Admin User default timezone
ALTER TABLE TENANT.BLC_TENANT ADD DEFAULT_APPLICATION_ID VARCHAR(36);