☰
Navigation :

What's New

This page provides a brief overview of the user-facing new features and improvements in the latest version of Atoti Limits.

info

For developer-facing changes, see the Release notes
For the list of issues covered in this release, and known issues, see the Changelog.
For information on upgrading from previous versions, see the Atoti Limits Migration Notes.

4.1.1

Improvements

Improvements

Evaluation performance

KPI evaluations have been made faster and more responsive. They now run more efficiently through smarter caching, and earlier detection when limits and locations are incompatible.

Evaluations executed via the UI have also been optimized, with MDX requests now split into smaller batches to avoid performance slowdowns or freezing.

Bulk workflow transactions

The following new services have been introduced to start Activiti workflows in bulk, significantly improving performance when handling large volumes of data:

  • IBulkLimitsWorkflowCreationService starts multiple limits workflows in bulk.
  • IBulkIncidentWorkflowCreationService starts multiple incident workflows in bulk.

This bulk approach is more efficient than sequential processing and delivers noticeable performance improvements. This is particularly so when creating multiple limits or when a large number of incidents are generated after limit evaluations.

These new services are enabled by default. However, if required for compatibility or specific configurations, the previous sequential behavior can be restored by setting:

limits.workflow.enable-bulk-activiti-transactions=false

Further performance optimization

Several improvements have been made to speed up data processing and event handling:

  • LimitsJpaToDatastoreImporter now reloads persisted limits into the datastore faster on server restart, reducing downtime and improving responsiveness.
  • ScopeCacheService optimizes cache refreshes by only updating scopes that aren’t already cached.
  • DefaultServerEventIssuerService sends events in batches of 10,000, helping to avoid restrictions or slowdowns on the listening server and improving overall event processing performance.

4.1.0

New features

Improvements

New features

Dedicated Audit History screen

The Audit History screen is now included out of the box. This dedicated screen shows you all your audit entries in a single screen. You can tailor the data displayed to your needs using filters, and easily export it into a CSV file.

See Audit History screen for details.

Notification Center

The Notification Center is now included out of the box. The Notification Center displays messages sent by Atoti Limits during the limit workflow, for example, when a limit evaluation is completed, or another user requests approval.

See Notifications in the UI screen for details.

Workflow file attachments

You can now save files as attachments at each step of the default workflows. This way you can upload files such as emails, screenshots, or other relevant documents directly to the workflow as evidence.

For details on adding this to your workflow see Defining Task Spring Beans.

View expired limits

You can now see expired limits within the limits screen by filtering on “All limits”.

See View, edit, copy and delete limits page for details.

Historical difference in Audit

The audit log for each incident now includes a record of historical differences, letting you easily track what has changed between the current and previous evaluations and understand the impact on the incident.

Streamlined breach review

The incident review process has been enhanced. When you access a linked dashboard from an incident for more information, you can now review the incident directly within the dashboard, eliminating the need to navigate back to the incident screen and streamlining your workflow.

See Review incidents page for details.

Improvements

Error handling

The handling of server errors in the UI has been significantly enhanced. When uploading a limit or limit structure CSV file, any errors encountered will be highlighted within the offending cell in the preview, along with detailed error information. Additionally, when creating a limit structure, any server-side errors are displayed directly beneath the relevant field within the form. These improvements provide clearer feedback, making it easier for users to identify, understand, and resolve errors efficiently.

UI recoverability

Non-limit features will remain accessible even if the Atoti Limits server is unavailable.

Performance

Additional enhancements have been made to improve the performance of limit evaluation and creation.