Updates since 4.0 pre-releases

This page lists the changes since 4.0.0-alpha and 4.0.0-beta, and explains any changes required to migrate from these early releases to the stated version of Atoti Limits:

• Migrate from 4.0.0-alpha to beta
• Migrate from 4.0.0-beta to 4.0.0

Changes since 4.0.0-beta

Added

Issue Key	Details
LIM-987	You can now drill down by a limit scope’s level name and level values in a pivot table.
LIM-1318	Updated the Workflow Common Library to version 2.4.1 and H2 to version 2.2.220 to fix CVEs.
LIM-1340	Permission roles are now enforced on REST requests, blocking the action from being processed by the server if the user does not have the required permissions.
LIM-1341	Permission roles for the workflow actions of approving/rejecting limits and processing incidents are now supported.
LIM-1355	Added /limits/rest/v2/limitDefinition/limits/status/get endpoint to get limits status & server setting to include status for limit structures.
LIM-1357	Added new property to set the default-scope-match-mode for scope permissions.
LIM-1369	Added new property to set the owner role(s) for KPIs and calculated members Limits creates in connected Atoti servers. This property is optional and can be auto-configured.
LIM-1373	Updated Data Connectors to version 4.2.0-AS6.1.
LIM-1377	Added a service in the connected servers to be triggered on limit events. See Sending events to your connected server.
LIM-1382	Atoti Limits has been upgraded to Atoti Server 6.1.1. The 6.0.X and 6.0.X-sb3 modules have been upgraded to use Atoti Server 6.0.17 and 6.0.17-sb3 respectively.
LIM-1390	Permissions for uploading/downloading limits are now supported.
LIM-1395	Added Alive field to the Limits store to indicate if a limit is active or deleted/expired.
LIM-1356	Separate loading of workflow statuses by setting -Dlimits.workflow.workflow-status-fetched-with-limit=false.
LIM-1418	The datepicker for the limit start date in the Limits viewer screen now defaults to the server’s as of date.
LIM-1449	Added re-evaluate action for reviewed incidents to allow them to be re-evaluated.
LIM-1466	Updated Common Library to version 2.1.0-AS6.1.

Changed

Issue Key	Details
LIM-1359	The limits-shared-properties module has been renamed to limits-common and the limits-lookup-postprocessors modules have been merged into the limits-integration and limits-common modules.
LIM-1410	Merged RemoteLimit, RemoteLimitEntity and LimitGoal into the new SimpleLimit class.

Removed

Issue Key	Details
LIM-000

Fixed

Issue Key	Details
LIM-1303	Fixed the admin-ui database tab by adding @EnableWebMvc and removing custom message converters.
LIM-1371	Limits are now correctly evaluated via the Inventory screen or REST services when cube filters are disabled.
LIM-1375	The “Available amount” and “Utilization perc.” measures are now available for limits created both on startup and at runtime.
LIM-1416	The Re-Evaluate icon for incidents in the Status screen is now disabled for users with no permission to evaluate limits.
LIM-1429	Fixed an issue where restarting Atoti Limits in persistent mode did not restore the object and workflow states.
LIM-1430	Corrected Limits roles documentation for roles that were previously prefixed by GROUP_, but are now prefixed by ROLE_.
LIM-1439	Fix limits viewer column configurator allowing reordering columns.

Fixed issues introduced in 4.0.0-beta

Issue Key	Details
LIM-1392	Fixed the utilization percentage measure created in the business cube.
LIM-1428	Fixed an issue where role permissions were only partially enforced when creating limits.
LIM-1431	Fixed an issue where a user with restricted data access could create a new structure with the same name as an existing structure.

Migrate to 4.0.0

Upgrading from version 4.0.0-beta, see Atoti Limits 4.0.0 Release Notes.

Atoti Limits uses Atoti Server 6.1.1 and Atoti UI 5.2.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

No breaking changes.

Summary

• Limit statuses : faster loading times when displaying a limit structure with a large number of limits by enabling a property to fetch the statuses in a separate process.
• Enhanced scope levels : Users can now drill down by a limit scope’s level name and level member in a pivot table.

Input file formats

No changes.

Configuration

Configuration Properties

limits-activeviam module

Properties added

Property Name	Comment	Value
limits.data-access-control.servers..default-scope-match-mode	Sets the match mode to use for scope permissions when it is omitted.	MATCH_ALL
limits.autoconfiguration.content-server.limits-created-measures-owners	The roles that will be the owner/reader for the calculated members that were created based on the KPIs. The value should be auto-configured from the KPI owners in the content server.
limits.workflow.workflow-status-fetched-with-limit	When set to true, retrieving limit structures also updates the limit status with the current workflow status.	true

Configuration files

No changes.

Datastores

Modified stores

Modification	Store	Field	Type	Description
Added	Limits	Alive	Boolean	This field indicates whether the limit is still alive (not deleted or expired). For more details, see Alive field in Limits store.

Cube schema

Added

Cube	Dimension	Hierarchy	Levels	Datastore fields	Details
Limits	Limit	Scope Level Name	Scope Level Name	ScopeKeys	The level name of a limit’s scope, for example Book@Books@Booking.
Limits	Limit	Scope Level Member	Scope Level Member	ScopeValues	The level member of a scope, for example Book 1.

Measures

No changes.

Changes since 4.0.0-alpha

Added

Issue Key	Details
LIM-1200	An “Available Amount” and “Utilization %” measure for each KPI has been added to the limits-auto-config, calculating the difference and quotient between a KPI’s goal and the KPI’s value, respectively.
LIM-1205	Added a property to configure whether or not filters are applied on evaluation.
LIM-1275	Added debug logs when evaluating Atoti Limits KPIs detailing eligible limits, exposures, and evaluation location.
LIM-1302	Added support for restricting access on scopes in the role permissions.
LIM-1324	Pagination has been added to the Limits viewer.
LIM-1328	Added new matchMode values for scopes to support more flexible retrievals in the IScopeRetrievalService. For details, see Match mode.
LIM-1339	Added permission roles to control user access to UI actions.
LIM-1345	Improved performance in the Limits viewer screen by using the ScopeCacheService to help retrieve scope objects.

Changed

Issue Key	Details
LIM-1096	KpiCrudService and KpiCrudRestService have been updated, separating the two classes into a Spring Service and a REST Controller wrapper.
LIM-1298	Improved property handling in Atoti Limits auto-configuration.
LIM-1314	Improvements have been made to the validation framework. See the custom validator page for more information.
LIM-1323	Improved performance of filters in Limits tables.
LIM-1344	The ILimitsRetrievalService methods have been updated and the implementation modified to avoid executing methods recursively and to reduce the number of transactions in methods. For more details, see Changes to IlimitsRetrievalService.
LIM-1372	Updated common library to version 2.1.0-alpha-AS6.1.

Removed

Issue Key	Details
LIM-285	Between and Not Between KpiTypes have been disabled. For more information, see Removing Between and Not Between KPI types.
LIM-1274	private_ and internal imports have been removed from Atoti Limits.
LIM-1312	Removed support for Atoti Server version 5.11 as it is no longer supported by ActiveViam.

Fixed

Issue Key	Details
LIM-1325	Fixed the scope selector overflowing the popover for large lists of scope members.
LIM-1349	Removed the incorrect usage of the thread pool when creating/dropping KPIs in the KpiCrudService.
LIM-1358	Updated calculated member creation to set ROLE_USER as the default owner and reader so all users can see the measures.
LIM-1366	Fixed issue with evaluation errors not being cleared when retrying the evaluation.

Migrate to 4.0.0-beta

Upgrading from version 4.0.0-alpha, see Atoti Limits 4.0.0-beta Release Notes.

Atoti Limits uses Atoti Server 6.1.0 and Atoti UI 5.2.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

Auto-Configuration changes

• LimitsCoreConfig has been renamed to LimitsCoreAutoConfiguration, is now an @Autoconfiguration class and is no longer explicitly imported in LimitsAppConfig.

Input file formats

No changes.

Configuration

Configuration properties

Properties modified

limits-integration-common module

Property Name	Comment	New Value	Old Value
limits.autoconfiguraton.limits-base-url	Contains the base, for example, http://localhost:3090 instead of the full rest URL, such as http://localhost:3090/limits/rest/v2	limits.autoconfiguraton.limits-base-url	limits.autoconfiguraton.limits-rest-url

Files Modified

Property files

limits-activeviam module

New properties:

Property Name	Comment	Value
limits.cube.kpi-filters-enabled	True if cube filters are enabled for Limits KPIs, false otherwise.	true

Datastores

No changes.

Cube schema

No changes.

Measures

No changes.

Other changes

ROLE_LIMITS is no longer a required role

The ROLE_LIMITS role is no longer required for all users of Atoti Limits. This role has been repurposed as the full-access role in the permission roles to maintain backward compatibility. Users with this role will continue having full access to all actions in the UI as they previously did.