Updates since 4.0 pre-releases

This page lists the changes since 4.0.0-alpha, and explains any changes required to migrate from 4.0.0-alpha to the stated version of Atoti Limits.

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 and workflow core to version 2.4.0.

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.

Context values

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.