Migrate to 5.2.1
Headline announcement
- Modified UI settings : Added
adjustmentCubeSettings, changedfieldsand removedadjustmentsAsOfDateLevelandadjustmentsTaskLevel.
Configuration files
SignOffSettings.ts
Migrate to 5.2.0
Upgrading from version 5.1.0 See Atoti Sign-Off 5.2.0 Release Notes. Atoti Sign-Off is using Atoti Server 6.0.13-sb3, Atoti UI 5.1.x, and Sign-Off API 4.0.1 . For new features and fixes included in these releases, please see:- Atoti UI documentation and Atoti UI Migration Notes
- Release notes for Atoti Server
- Release notes for Signoff API
Headline announcement
- Atoti Server upgrade : Atoti Sign-Off has been upgraded to Atoti Server 6.0.13-sb3.
- Spring Boot upgrade : We have upgraded Spring Boot to version 3.2.0, which uses Spring Framework 6.
- Common Parent POM and Common Dependencies BOM upgrade: The Common Parent POM and the Common Dependencies BOM have both been upgraded to version 2.0.0.
- Activiti upgrade : We have upgraded Activiti to version 8.1.0 to be compatible with Spring Boot 3.
- UI Activation : An import of
react-queryis required when usingsignoff-sdk. See UI activation for more details.
Breaking changes
- Upgrades:
- The version of Spring Boot has been upgraded to version 3.2.0, which includes breaking changes. See the Spring migration guide for more information.
- In order to be compatible with Spring Boot 3.2.0 we have upgraded Activiti to version 8.1.0. This requires including
extension.jsonfiles with each workflow file.
Spring Boot 3 upgrade
The main change in the Spring Boot 3 upgrade involves migratingjavax.** imports to jakarta.xx imports.
Activiti upgrade
In order to upgrade Activiti users must now supply an**-extensions.json file for each of their workflows. These extension files externalize information about the workflow
and provide it to Activiti’s runtime engine. An example **-extension.json file may look as follows:
process-definition-idcorresponds to the ID of a process definition. This maps to a single BPMN file.start.event.idcorresponds to the ID of a Start Event.user.task.idcorresponds to the ID of a User Task.service.task.idcorresponds to the ID of a Service Task."mappingType": "MAP_ALL"tells Activiti to map all input and output variables throughout the workflow.