Sandbox Release Notes for 2.1.2-GA

Table of Contents

Requirements

As of Broadleaf Release Train 2.1.3-GA, all microservices have been upgraded to Spring Boot 3.3

This version includes all changes up to 2.0.5 Release Notes
Add index in JpaChangeSummary for the combination of LAST_DEPLOY_RELATION, SANDBOX, and STATE columns to improve change summary querying.

As of Broadleaf Release Train 2.0.4-GA, all microservices have been upgraded to Spring Boot 3.3
The ChangeDeploy unschedule feature now works for failed deployments marked with the ERROR_DEPLOY status
- This effectively removes the deployment failure from the deployment screen in the admin
- The failed deployment header message will also be removed from the one or more entity forms associated with the deployment
- ChangeDetails associated with the failed transition sandbox entities in the resource tier are marked obsolete in order to make them inactive
- If all ChangeDetails are made inactive, the sandbox state for the entity is archived
- This serves as a method to remove deploy failures from visibility in the admin. The feature is usually engaged via the unschedule button in the deployments screen in the admin under the scheduled tab.

Fixed a bug causing a NPE when rejecting translation at the approval step when the provided translation operated as a CREATE vs UPDATE.