Atoti Limits 4.0: Enhanced customization and improved data control 

With the release of Atoti Limits 4.0.0, gain access to new features designed to enhance customization and improve data control. Here’s what’s in store for those building with Atoti Limits.

Role-based permissions

Atoti Limits now supports custom role-based permissions, allowing to restrict access to the Limits cube and screens based on user roles. This feature, configured via properties in the application.yml file, provides granular control over data visibility and operations for each role.

Set Permissions for different fields, like structure-groups, structure-names, structure-measures, and limit-ids.

For example, to restrict access to specific limit groups, define the structure-groups for a role in the configuration. Tailor roles by defining unique permissions based on business needs, such as limiting Equity Desk users to only view limits under the “Equity Desk” group.

The configuration is structured in a nested map with top-level server names. This enables separate permissions for each server and second-level keys for role-specific access.

limits:
  data-access-control:
    MyServer:
      role-permissions:
        ROLE_EQUITY_DESK:
          structure-groups:
            - Equity Desk

This setup allows Atoti Limits to filter data and actions available to users dynamically, based on their assigned role. This ensures that access aligns with an organization’s data security policies.

Limit sensitivity to runtime filters

Atoti Limits 4.0 enables developers to control KPI sensitivity to runtime filters within the business cube, offering control over how KPIs respond to filtered data. Manage this through the limits.cube.kpi-filters-enabled property in the application.yml configuration file. Setting this property to true makes KPIs respect runtime filters during evaluations. Setting it to false ensures KPIs ignore any filters.

This feature is valuable in environments where specific KPIs must consistently provide unfiltered results for standardized reporting, while others should adapt dynamically to real-time filtered data. This configuration ensures that KPIs reflect the context essential for the user’s objectives, whether for compliance or operational needs.

Improved experiences with scope

The Limits input CSV files now accept simplified scopes, a more straightforward syntax, allowing developers to set up scopes efficiently without extraneous configurations. Move away from configuration like this

Book = Book 1

To this:

Book 1

Your turn to try

The Atoti Limits 4.0.0 release provides fine-grained control, flexibility, and a streamlined project environment. Whether it’s implementing role-based permissions, fine-tuning KPI filters, or embracing a simplified project layout, Atoti Limits 4.0.0 is designed to enhance productivity and support evolving needs.