Documentation Index
Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt
Use this file to discover all available pages before exploring further.
For information on upgrading from previous versions, see the
Atoti Limits Migration Notes
Download the distribution files
hereYou can download the following zipped distribution files:
- UI source code
- UI build
- Source files to build the module
- Sample bookmarks
- Maven repository required to build the project and run the tests. The Atoti Server 6.0.9 Maven repository files can be downloaded from here.
Summary
- Improved table filtering : Filters have been moved to the column headers and have been extended to more columns, including the Location and Scope of a limit.
- Status screen : The Breaches screen has been renamed Status. It has also been enhanced to allow you to view the utilization of passed limits if they are stored.
- Linked dashboards : A dashboard can be linked to a limit structure to let you view the utilization for a given limit. Viewing the utilization of an incident will apply scope and as of date filters to the dashboard.
- Added Utilization : The Utilization measure has been added to the Limits cube. This measure can be extended by clients.
- Custom User Workflow Actions Improvements : We have simplified the addition of custom user actions in workflows. Please see
Adding Customizing Workflow Tasks.
- Upgraded Java version: We have upgraded the Java version used to compile Atoti Limits to 17.
As a result, we have removed the sample Atoti Server 5.10 from our distribution, as it does not support Java 17. Atoti Limits is still compatible with this version.
- Updated Atoti Server and Spring Boot dependency versions: Updated the version of Atoti Server that Atoti Limits runs on to
6.0.9 and Spring Boot version to 2.7.16.
- Spring Security upgrade : We have upgraded Spring Security to version 5.8.7 to resolve vulnerabilities and prepare for the upgrade to Spring Security 6.0 (via Spring Boot 3).
- Common Parent POM: The Atoti Limits module now inherits third-party plugin versions from the Common Parent POM version 1.2.0, in line with other solutions. Details can be found in the migration notes.
Known issues
| Issue Key | Details |
|---|
| BAS-1330 | Deleting the last limit value deletes the limit structure. As a workaround, don’t delete all limits on a limit structure unless you are sure that the structure won’t be used again. Alternatively, if you do need to reuse the structure, you can create a limit on it using the endpoint /modules/limits-module/limits/rest/v2/limitDefinition/limits/save. The key of the limit structure will still be visible in the admin-ui. |
| LIM-846 | Complex Scopes: Currently, a limit with an aggregated scope and a limit with a non-aggregated scope cannot be created on the same limit structure. As a workaround, create the limits on two separate structures. |
| LIM-840 | Complex Scopes: Currently, limits can’t be defined with an aggregated scope location and another scope location. As a workaround, create two separate limits on two separate structures. |
| LIM-813 | Managers can incorrectly upload Limit Structures through the REST endpoint. |
| LIM-594 | Having email notifications enabled for breaches causes decreased limit evaluation performance. See Configuring the breach email on how to disable breach emails. |
| LIM-357 | The Six Eyes workflow is currently not implemented. |
| LIM-346 | Limits on calculated measures only work through File Upload, not through the UI. |
| LIM-320 | Calculated measures need to be included in Pivot Table Query in order to view a Limit’s KPI in the Pivot Table. See Measures for more on how to create a query for Limits on calculated measures. |
Dependency versions
Unlike other solutions or modules, Atoti Limits requires Atoti UI version 5.1.2 or higher.
Added
| Issue Key | Details |
|---|
| BAS-1514 | Updated the README.md files in the parent and starter modules. |
| BAS-1537 | When attempting to auto-configure Atoti Limits we now only log the connection exception at debug level to avoid polluting the logs. |
| LIM-823 | Added utilization dashboard ID field to the limit structure. This allows you to link a limit structure with a dashboard based on its ID in the content server. |
| LIM-848 | Updated the version of Atoti Server that Atoti Limits runs on to 6.0.7 and Spring Boot version to 2.7.14 to patch CVE-2023-20883 and CVE-2023-33008. |
| LIM-863 | Added the option to store passes when evaluating limits. |
| LIM-870 | Added a utilization measure to the Limits cube. |
| LIM-872 | Created read-only REST endpoints to get row entries for the Limits Status screen. |
| LIM-879 | Created REST endpoints to update non-key fields of a limit structure. |
| LIM-901 | Upgraded Java version used to compile Atoti Limits from 11 to 17. |
| LIM-905 | Added an endpoint to query the distinct as of dates for limit evaluations. |
| LIM-907 | Upgraded to Spring Security 5.8.7 to resolve CVEs and prepare for the upgrade to Spring Security 6.0 (via Spring Boot 3). |
| LIM-908 | Added an endpoint to return if the user is storing passes when evaluating limits. |
| LIM-910 | Improved support for custom user actions in workflows. |
| LIM-911 | Added a hook for custom workflow keys to execute user actions. |
| LIM-916 | Upgraded Spring Boot to version 2.7.16 by inheriting from the Common Parent POM version 1.2.0. |
| LIM-923 | Workflows for limit evaluations now exist for distinct as-of-dates. |
| LIM-943 | Updated the version of Atoti Server that Atoti Limits runs on to 6.0.9. |
| LIM-946 | Updated the version of the solutions-tools-bom to 2.0-AS6.0 to support Java 17 and Atoti Server 6.0.9. |
| LIM-956 | Added a new endpoint /inventory-structures/filter to reduce the amount of data sent to the limits inventory screen. |
| UIACL-577 | Added the action to inspect the utilization from the Inventory and Status screens. |
| UIACL-592 | Added ANTD built-in table filtering for the Limits screens. |
| UIACL-623 | Renamed the Breaches screen to Status screen and added ability to fetch all passed limits. |
| UIACL-671 | Enabled the workflow action button for authorized users only. |
| UIACL-680 | Enabled sticky headers in the limits tables. |
| UIACL-737 | Results are now cached for a minute inside the Status screen to prevent constant loading when browsing. |
Changed
| Issue Key | Details |
|---|
| LIM-827 | Changed the limit type from String to an enumeration LimitType that allows only “OFFICIAL” and “TEMPORARY” values. |
| LIM-912 | Renamed the LimitWorkflowActionDTO to WorkflowTaskActionDTO and updated it to improve custom workflow actions on the UI. |
| LIM-934 | Updated the version of Atoti Server that Atoti Limits runs on to 6.0.9. |
| UIACL-654 | Replaced limit column action buttons with icons and a tooltip. |
| UIACL-659 | Re-arranged the Status screen columns. |
| UIACL-690 | Renamed the Workflow section to Review Process and updated the labels within the limit structure viewer. |
| UIACL-707 | Rows are no longer de-selected when changing client-side filters. |
| UIACL-714 | When creating a limit structure, the breach when field is disabled when the kpi type is not selected. |
Removed
| Issue Key | Details |
|---|
| UIACL-580 | Removed the “utilizationDashboards” limit setting. Utilization dashboards can be added to the limit structure directly in the UI instead. |
| UIACL-640 | Removed server and cube columns from the Inventory screen. |
| UIACL-685 | Removed the “exceptionAuditTrailNodeColors” limit setting. The “auditTrailNodeColors” should be used instead. |
Fixed
| Issue Key | Details |
|---|
| BAS-1437 | Incident files on deleted limits no longer break the status screen on startup. |
| BAS-1449 | Equivalent scope strings now generate the same Limit keys. |
| BAS-1463 | UI evaluation now correctly evaluates servers where the server keys don’t equal the server name. |
| LIM-740 | Evaluating a limit structure containing only expired limits or structures with no data results in an error. |
| LIM-815 | Limit structures loaded without limits will now load successfully, limits loaded without limit structures and incidents loaded without limits will be skipped. |
| LIM-854 | The Status screen now shows the value of the active temporary limit, instead of the official limit. |
| LIM-856 | The value of the discovery-manager.polling-delay property is now used. |
| LIM-857 | Connecting to Atoti Server version 5.x. generated useless logs. |
| LIM-869 | An error occurred if the incident directory didn’t exist. |
| LIM-894 | Limits of the same structure with mismatching scope levels will now be skipped on loading so they don’t break the limits management screen. |
| LIM-913 | New limits can now be correctly created after deleting a complex scoped limit. |
| LIM-914 | Incidents that fail workflow validation appear in the status screen. |
| LIM-922 | Workflow action buttons are no longer visible for deleted limits. |
| LIM-925 | The breach audit history endpoint no longer contains details about limit changes. |
| LIM-926 | Fixed a bug which prevented editing limits when the order of scopes posted in the UI request was different to the order retrieved from the datastore. |
| LIM-927 | Improved the exception handling on Limit evaluation. |
| LIM-936 | Workflow action buttons are no longer returned if they are disabled. |
| LIM-954 | Limits evaluated by managers are no longer visible in the status screen. |
| LIM-955 | Explicit scope matches on limits are now not over-ruled by temporary limits. |
| LIM-957 | Fixed the date-roll endpoint which was not correctly updating the as-of-date. |
| UIACL-593 | The limits table was not displayed correctly when a limit structure didn’t contain any limits. |
| UIACL-669 | The Select all checkbox now selects all rows across multiple pages. |
For Removal
| Issue Key | Details |
|---|
| LIM-794 | Support for the Legacy Limits file will be removed in Atoti Limits version 4.0.0 |
