What's New
This page provides a brief overview of the user-facing new features and improvements in the latest version of Atoti Limits.
For bug fixes and developer-facing changes, see our Changelog.
4.0.0-BETA
Summary
- Permission your limits
- Bypass limit filters
- Improved analysis
- Get started faster
- Paginated limits
- Improved scope analysis
- UI update
- Improvements
New features
Permission your limits
Unlock - or lock - the power to control who can view and action your limits and incidents with Atoti Limits 4.0.0-beta. Administrators can now define a more granular level of access, ensuring that only the right people have the ability to view and action limits and incidents. This enhanced control applies to both the cube and the Limits screens, providing a secure and efficient way to manage your limits.
For details, see Roles and permissions.
Bypass limit filters
With Atoti Limits 4.0.0-beta, you can effortlessly configure limit sensitivity to filters, tailoring your data insights like never before and enabling you to make more informed decisions and maintain compliance seamlessly.
For details, see Cube Filters on Limit KPIs.
Improved analysis
Elevate your business cube using the new Available amount
and Limit Utilization %
measures. Created out-of-the-box, this update supercharges your analysis
capabilities, providing deeper insights and enhanced decision-making.
See Business cube measures for more details.
Get started faster
Atoti Limits 4.0.0-beta is powered by the latest versions of Atoti Server and Spring. This inherits several Atoti Server Spring Boot Starters that let developers get started quicker with less code. Less code means less maintenance, easier upgrades, and more time to work on the features you care about.
Paginated limits
The Limits viewer now lets you display your limits on multiple pages, making it effortless to navigate and organize large amounts of limits for maximum efficiency and control.
Improved scope analysis
If you care about the scope of your limits just as much as the limits themselves, then this release is for you. We’ve added new services that empower you to analyze the scope of their limits with ease, giving you a completely different lens of analysis.
For details, see Scopes.
UI update
Atoti Limits now uses Atoti UI 5.2. For more details on this version, see the Atoti UI documentation.
Improvements
- Easier integration: It is now easier than ever to connect to an Atoti server with Atoti Limits. For details, see Atoti Java.
3.3.1
Summary
This release includes artifacts for connecting with instances of Atoti Server on
version 6.0.x
using Java 11,
in addition to the already supported 6.0.x-sb3
version using Java 17. For details, see
the Release notes.
There have been no other changes.
3.3.0
Summary
- Limit persistence
- Instant monitoring
- Easy document access
- Upload preview
- Simplified limit creation
- Enhanced extendability
New features
Limit persistence
Experience enhanced data management with Atoti Limits. We now offer robust support for persisting limit structures, limits, and incidents directly to your external databases using JDBC. This feature ensures your data is always up-to-date, organized, and readily accessible.
To find out more, see Persistence.
Instant monitoring
Stay on top of your breaches with our new real-time breach monitoring feature. In the Status screen, you can now monitor and review your breaches as they occur. Experience real-time insights and stay ahead of the curve with our enhanced monitoring capability.
For details, see Real-time updates
Easy document access
You can now attach document links directly to your limit workflows. This means you can now easily access related documents from within your workflows, improving efficiency and ensuring that all relevant information is at your fingertips.
See Breaches and Approve limits on how you can take advantage of this intuitive and convenient feature.
Upload preview
Experience a smoother, more intuitive upload process with Atoti Limits. You can now preview your limit files in a user-friendly table format before uploading. But that’s not all - upon upload, any errors are immediately highlighted and accompanied by detailed descriptions for quick and easy fixing. This ensures you can effortlessly submit valid files, enhancing your productivity and user experience.
For details, see Upload limits.
Simplified limit creation
Creating limit structures just got easier with our new custom templates. Configure custom templates to pre-populate fields, making limit creation a breeze. This not only saves you time but also ensures consistency across your limit structures.
Explore the Adding Custom Limit Structure Templates to learn more.
Enhanced extendability
Unlock the full potential of Atoti Limits with our enhanced support for validation, data-loading, and evaluation. We’ve made extending Atoti Limits simpler than ever, empowering you to customize and optimize your workflows with ease.
See Extending the Module to discover how you can take your productivity to the next level.
3.2.0
Summary
New features
Custom error handling
Atoti Limits now gives you the ability to display custom error messages on its screens. This feature not only improves the look-and-feel of Atoti Limits, but lets you pinpoint issues using your own terminology.
See Adding Custom UI Exceptions for details.
Enhanced table features
In the Inventory and Status screens the columns can now be resized, reordered, and hidden. The styling of the table has also been updated to improve the visibility of active filters and increase the real estate available to display data.
New engine
Atoti Limits 3.2.0 is powered by the latest version of Atoti Server and Spring. The result is a faster, safer application, which you can customize using the most modern stack available.
Smarter startup
When starting out, creating and loading files to start Atoti Limits can be tricky. To help with this, Atoti Limits now generates empty default files if it doesn’t find yours on startup, allowing you to get to work quicker.
3.1.0
Summary
- Holistic limit status overview
- Improved breach root cause analysis - Linked dashboards
- Improved limit reporting in the Limits Cube
New features
Holistic limit status overview
The all-new Status screen replaces the previous Breaches screen. This design aims to enhance efficiency and streamline your workflow. The new screen provides a comprehensive view of limit statuses and utilization across your entire limit inventory. All the essential breach-processing functionality has been seamlessly integrated into the new Status screen, retaining the core capabilities you rely on. The Status screen leverages a brand-new table design, providing an intuitive and user-friendly interface. You can easily filter limit evaluations based on specific limits and their attributes.
For more details on the new UI, see Status screen.
Improved breach root cause analysis - Linked dashboards
Atoti Limits now provides seamless navigation from limits and limit breaches to dashboards, enhancing your ability to dissect and analyze limit usage data. This feature is leveraging Atoti’s native BI capabilities for flexible data exploration to enable drill-down to the most granular level - trade, risk factor, or scenario - and help analyze the root cause of breaches or drivers of limit utilizations on a daily basis.
Check out Linked dashboards on how to get started.
Improvements
Improved limit reporting in the Limits Cube
The Limits Cube is your canvas for visualizing limit evaluations alongside essential limit attributes in a dynamic dashboard. To further enrich your analysis, a new Utilization measure has been added to the Limits Cube. This measure succinctly displays utilization for every limit.
3.0.0
Summary
New features
On-demand limit evaluations
This feature enables you to re-evaluate limits whenever needed. In addition to the evaluations triggered automatically, you can now request evaluations directly from the UI. This is especially useful when underlying risk data might have changed and you want to ensure that you have the most up-to-date results.
To start leveraging the benefits of on-demand limit evaluations, see Evaluate limits.
Improvements
Smarter limit definitions
Now you can use various functions for limit scope selection and add limits based on specific criteria. Discover the simplicity and flexibility of this enhancement today. See Advanced scopes to get started.
Enhanced audit trail
You can now easily view before and after values for modified fields, gaining better insights into limit changes. For workflows involving four or six-eyes approval processes, we’ve added requester and approver details, ensuring complete visibility and accountability. Stay in control of your limits with this improved audit trail feature.
For details, see View the limit history.
2.0.1-ui-update-2
Summary
This is a UI-only release that allows you to exclude values from the Limit Scope dropdown when creating limits.
warning
This version of Atoti Limits can only be used with Business Cubes that are on Atoti UI 5.1.x.
2.0.1-ui-update-1
Summary
This is a UI-only release that makes Atoti Limits compatible with Atoti UI version 5.1.0 or higher.
warning
This version of Atoti Limits can only be used with Business Cubes that are on Atoti UI 5.1.x.
2.0.1
Summary
Bug fixes.
2.0.0-ui-update-1
Summary
This is a UI-only release containing performance improvements for creating limits for very large cardinality hierarchies.
2.0.0
Summary
- Redesigned Inventory for easier limit management
- Temporary limits, in a fully governed way
- Dedicated breach management view
- Improved limit audit
- Limits in top navigation bar
New features
Redesigned Inventory for easier limit management
A risk appetite framework may require managing a large number of limits, which can be time-consuming and overwhelming. That’s why we’ve revamped our limit * Inventory* to help you add multiple similar limits. This feature will help increase productivity and streamline the process of managing hundreds or even thousands of limits. For more details, see the following topics:
Temporary limits, in a fully governed way
Atoti Limits now offers a solution to automate temporary limit increases, to facilitate business needs in a controlled manner.
A temporary limit is a Limit that co-exists with an official limit for a given period of time. On evaluation, a temporary limit will take precedence over the official limit.
A temporary limit will have the same lifecycle as the official limit, but will terminate before the official limit terminates. A temporary limit must spawn from an official limit, it cannot be created as a standalone limit.
In practice, a temporary limit is used to handle extraordinary non-lasting events. For example, a trader may have an official limit of 1mm on Book A, with no expiration. The trader has an open position on Book A of 900,000, so she is not in breach of her limit. However, due to market volatility, prices have increased and her position has risen to 1.1mm, putting her in breach. She consults her risk manager, and the risk manager envisages that volatility in the market will subside in the next month, but he grants her a temporary limit on Book A of 1.15mm for 6 months. Now, the temporary limit will take precedence over the official limit for 6 months, so the trader’s position of 1.1mm is no longer in breach.
The difference between a temporary limit and an update to an official limit is that official limits are usually set periodically by the Risk department of a firm. If the terms upon which the official limit was agreed change, for example, the credit rating on Counterparty X was Aaa at the time the official limit was set and it has since been reevaluated to Ba, then the logical step is to update the official limit. However, if the limit only needs to be adjusted to account for a change that is deemed to be non-lasting, the temporary limit is the best approach.
For instructions on how to set a temporary limit, see Set a temporary limit.
Dedicated breach management view
The new Breach management view simplifies the workflow to help you focus on the root cause analysis and resolution of the incident. Breach management gathers breach occurrences and requests stakeholder input in detailing, categorizing, and addressing breaches. For details, see the following topics:
Improvements
Limits in top navigation bar
You can now navigate to limits and breaches from anywhere in the application using the menu in the top navigation bar:
1.1.0
Summary
- Email notifications on limit breaches.
- Context menu action to view utilizations of a limit.
- Limits Auto-Configuration
- Copy action
- Swagger UI is available at {base.url}/swagger-ui/index.html. This will display some REST endpoints exposed by the Limits server. It can
be enabled/disabled by setting property
swagger.enable
totrue
/false
. - Performance improvements.
New features
Email notifications
The Limits Module can be configured to send email notifications about limit breaches.
See Configuring breach email notifications for details.
View Utilizations context menu action
A new context menu action has been added that lets you view the utilization of limits from a pivot table. This is helpful when investigating exceptions. The feature works on all pivot tables in the Limits project, including the Limits Inventory widget.
See View Utilizations for details.
Auto-Configuration
You can now use auto-configuration to integrate the Limits Module with atoti+. See Auto-configuration for details.
Copying Limits
You can now click the Copy button in the Limits Inventory to duplicate an existing limit.
For more information, see Copy a limit.