Updates since 3.2 pre-releases
This page lists the changes since 3.2.0-BETA, and explains any changes required to migrate from 3.2.0-BETA to the stated version of Atoti Limits.
warning
Please note that Atoti Server versions 5.9 and 5.10 are now out-of-support. Therefore, we will no longer support connections to servers of these versions as of the next release of Atoti Limits.
Changes since 3.2.0-RC1
Changes to ILimitsProcessInstanceWorkflowService
If you implement a custom ILimitsProcessInstanceWorkflowService, modify the initiate method to match the new signature.
| Old signature | New signature |
|---|---|
AHistoryRecordDTO initiate(LimitsProcessInstanceDTO object, String comment, boolean refreshKpis) |
AHistoryRecordDTO initiate(LimitsProcessInstanceDTO instanceObject, String comment, boolean publishTuples, boolean refreshKpis) |
The new publishTuples parameter determines if updated tuples should be published immediately to the datastore.
If false, the invoker of this method should manually publish tuples after the method completes.
This is more performant for large updates.
Added
| Issue Key | Details |
|---|---|
| LIM-1127 | Added a performance improvement when uploading limits through the UI. |
| LIM-1129 | Upgraded Data Connectors to version 4.1.0-AP6.0-sb3. |
Fixed
| Issue Key | Details |
|---|---|
| LIM-1125 | Fixed an issue where the starter jar didn’t start from the command line, by reverting to the CLASSIC loader implementation for Spring’s Nested Jar Support. |
Changes between 3.2.0-BETA and 3.2.0-RC1
Added
| Issue Key | Details |
|---|---|
| LIM-1056 | Added the action property to the ProblemDetails error response. See Adding Custom UI Exceptions. |
| LIM-1060 | Updated the version of Admin UI that Atoti Limits uses to 5.1.7. |
| LIM-1080 | Added a new ILimitsRetrievalService interface and LimitsQueryPayload object |
| LIM-1086 | Added the lombok-maven-plugin to ensure the decompilation of the source code matches the Lombok annotated classes. |
| LIM-1089 | Added performance enhancements when loading structures and limits from files and when evaluating limits. |
| LIM-1090 | Added Spotify code formatter plugin to Atoti Limits. |
Changed
| Issue Key | Details |
|---|---|
| LIM-1007 | Centralized all HttpRequests in limits-activeviam and limits-stater modules to the WebClientService Spring service and migrated them to the RestClient API. |
| LIM-1075 | Upgraded Atoti Limits to 6.0.12-sb3 |
| LIM-1084 | Migrated HttpClient invocations in limits-atoti-server/limits-atoti-server-60 modules and all test classes to RestClient API. |
| UIACL-931 | React-query is now handled as a peer dependency. See UI activation for more details. |
Removed
| Issue Key | Details |
|---|---|
| LIM-1038 | Removed unused declarations of classes, fields, methods and variables. |
Fixed
| Issue Key | Details |
|---|---|
| LIM-1066 | Fixed an issue where users were unable to approve/reject a limit if another limit in the same structure was rejected. |
| LIM-1085 | Fixed an issue where limits defined with a time period that did not include the as-of-date were sometimes evaluated incorrectly from the UI. |
| LIM-1087 | Fixed a file loading issue that would cause the UI to break due to missing a scope. |
| LIM-1092 | Attempting to modify key fields now results in a meaningful HTTP 400 response instead of a generic 500 one. |
Fixed issues introduced in 3.2.0-BETA
None.
Migrate to 3.2.0 from Beta
Upgrading from version 3.2.0-beta, see Atoti Limits 3.2 Release Notes.
Atoti Limits uses Atoti Server 6.0.12-sb3 and Atoti UI 5.1.x. For new features and fixes included in these releases, please see the Atoti UI documentation and Atoti UI Migration Notes, and the release notes for Atoti Server.
Breaking Changes
None.
Summary
- UI Activation : An import of
react-queryis required when usinglimits-sdk. See UI activation for more details. - Spotify Code Formatter : We now use Spotify’s code formatter plugin to format and validate our code. For more details, see Spotify Code Formatter.
Input file formats
No changes.
Configuration files
No changes.
Datastores
No changes.
Cube schema
No changes.
Measures
No changes.
Context values
No changes.
Other changes
Spotify Code Formatter
We now use Spotify’s code formatter plugin to format and validate our code. To format your code you, may use the format Maven profile, for example by running mvn clean install -P format. To validate that your code is correctly formatted as per the plugin, which uses Google’s code standards, you may use the validate Maven profile, for example by running mvn clean install -P validate.