This includes improvements to interaction patterns, keyboard usability, screen-reader support, and ARIA semantics across newly revised components.

Drawer: Refined Interaction Pattern with Better Accessibility​

The Drawer has been revised as part of the broader UI refresh. The update improves visual consistency, makes common actions easier to understand, and strengthens the component's accessibility baseline for everyday use.

Figure: Previous Drawer vs. Updated Drawer

• More consistent component design
  The Drawer now follows the updated visual language more closely, creating a more uniform experience across different parts of the application.

• Clearer actions in compact layouts
  Icon-only buttons now provide better contextual guidance through tooltips, making the interface easier to understand without adding visual clutter.

• Improved accessibility support
  The component now includes improved accessibility semantics and better assistive-technology support, helping the Drawer behave more reliably for keyboard and screen-reader users.

Navigation Menu: Redesigned for a Cleaner and More Accessible Entry Point​

The ADITO navigation menu has been reworked to modernize one of the application's most central interaction points. The result is a cleaner structure, improved orientation, and stronger accessibility support in daily navigation.

Figure: The new ADITO navigation bar

• Cleaner overall structure
  Updated visuals and a larger popup create a calmer, more spacious layout.

• Accessibility-first navigation behavior
  Keyboard navigation and improved ARIA support make the menu easier to use with assistive technologies.

• Reduced interface complexity
  Rarely used elements such as the side menu and history button have been removed to keep the navigation more focused.

• Reorganized key actions
  Notifications have moved to the top right, and Userhelp is now directly accessible from the navigation bar.

• Smoother search continuity
  The index search now remembers previous results, making repeated searches faster and reducing unnecessary repetition during navigation.

For more details, see the full blog post: A New Menu is Coming

ADITO Designer: Standalone Transpile and Deploy Enters Beta​

The ADITO Designer plugin Standalone Transpile and Deploy moves Transpile v2 into beta and removes the previous dev-only limitation. Teams can now use Transpile v2 in production environments.

Figure: Choose between Transpile v1 and v2 on the first build

• Production usage is now enabled
  The previous dev-only restriction has been removed, allowing rollout on productive systems.

• Project-level transpile version control
  The transpile version can now be configured per project in .aditoprj via transpile.version.

• Project overrides are supported again
  If files exist in both module and project, the project version can override module content again.

• Safer rollout with guided fallback
  On first run after the update, users choose between v1 and v2. If the first v2 build fails, fallback to v1 is offered.

• Automatic tool updates
  The plugin now keeps transpile tools up to date automatically.

For more details, see the full blog post: Standalone Transpile and Deploy Enters Beta Phase

Rather than summarizing changes only at the next major release, the Release Notes now follow a monthly cadence. This changes how updates are communicated, not which kinds of changes belong in a minor or major release: minor versions remain focused on stability, while breaking changes or changes with higher rollout risk continue to be reserved for major releases. A fuller explanation is available in the accompanying blog post.

Each monthly edition highlights selected updates across the ADITO ecosystem. Because areas such as Designer, AI, or individual modules can follow their own version numbers and release independently of the core platform, individual entries may reference different versions to show exactly when a change became available.

The following highlights summarize selected updates from the current monthly release window. For a complete list of changes, see the full changelog.

BasicTable: Pagination & Accessibility (Experimental)​

Explore a new way to handle large datasets: the BasicTable component introduces pagination instead of endless scrolling: designed for better performance and improved accessibility.

This feature is available for testing and feedback. It is not yet intended for production use. Available on desktop only.

• Pagination instead of endless scrolling
  Load data in clearly defined pages to reduce rendering overhead and improve responsiveness, especially for large result sets.

• Performance by design
  Only the data you actually need is fetched and rendered. This leads to faster load times, lower memory usage, and a smoother user experience.

• New server-client communication with NATS
  BasicTable uses NATS as a modern, lightweight messaging technology for communication between server and client. This enables a more decoupled and responsive data delivery compared to traditional approaches.

• Built with accessibility (a11y) in mind
  The component is being developed with the goal of conforming to WCAG 2.1 Level AA and related standards (BITV 2.0 / EN 301 549), including improved keyboard navigation, focus handling, and screen reader support.

Try out the BasicTable in your projects and share your feedback to help us shape the final release.

CI/CD: Migration to GitLab Pipelines​

The build and release pipeline has been migrated from Jenkins to GitLab CI/CD with GitLab Runner, bringing more stability, speed, and maintainability to the development workflow.

• More stable builds
  GitLab Pipelines provide a more reliable execution environment, reducing flaky builds and unexpected failures that previously required manual intervention.

• Faster feedback for developers
  Build times have improved, giving developers quicker results after pushing changes and reducing waiting time in the development cycle.

• Pipeline configuration as code
  The pipeline is defined directly in the repository, making changes transparent, reviewable, and version-controlled alongside the source code.

• Tighter integration with GitLab
  Build status, test results, and pipeline logs are now directly visible in merge requests and commits — no context switch to a separate CI system needed.

• Easier maintenance
  A unified toolchain reduces operational overhead and simplifies onboarding for new contributors.

This is a purely internal change with no direct impact on end users.

Internal Graph Calendar Backend for Microsoft Exchange Calendar​

The Graph calendar backend is now feature-complete and can be used as a replacement for the EWS calendar backend in ADITO systems.

• Uses global iCalUid
  Calendar links work consistently across all users and processes with Graph, ensuring the end user doesn't lose their 360° customer view when switching from EWS to Graph.
• Easy migration
  The switch to the new Graph backend enables a seamless transition from EWS to Graph without interrupting calendar access for end users.
• EWS shutdown in October 2026
  After Microsoft discontinues the EWS interface in October 2026, customer systems can migrate to Graph and continue accessing the Microsoft Calendar within ADITO xRM.

ADITO LLM: Thinking, Tool Use & Agentic Capabilities​

The ADITO LLM can now independently reason through complex tasks, call external functions, and execute multi-step workflows.

• Thinking / Extended Reasoning
  The model runs an internal reasoning process before responding to complex tasks. This directly improves result quality for demanding requests.

• Tool Use
  The model can call external functions and APIs to query data or trigger actions.
  This capability is currently available on the model level and can already be used in controlled or custom setups.

• Agentic Workflows
  By combining reasoning and tool use, multi-step workflows become possible where the model continues working autonomously based on intermediate results.
  This lays the foundation for more advanced automation patterns that will be expanded with upcoming platform integrations.

Further Improvements​

• Chart components now support displaying numeric values directly on data points. Two new properties control this behavior: showDataLabelValues and dataLabelPositionInside 2025.2.2 Core
• Twitter dashlet updated with the new "X" logo 2025.2.3 Core
• ButtonStrip with Actions now supports responsive layout 2026.0.0 Core
• Updated to JDK 25 2026.0.0 Core
• Removed permissions for CKEditor AI features 2026.0.0 Core
• REST-Webservices with Authentication-Providers now use the scope of the alias as a fallback if not set explicitly. 2026.0.0 Core
• Login is blocked when the maximum number of licensed users is exceeded, and a message is displayed.2026.0.0 Core
• Designer: Deprecated JDito methods are now correctly marked as deprecated in the generated stubs, so VSCode and the Designer display their deprecation status properly

This release expands the technical foundation for Microsoft Graph integration, improves internal service and configuration access, and addresses several issues in runtime behavior. The result is a platform that is easier to extend and more robust in existing installations. For the full technical detail, see the full changelog.

The following sections highlight selected larger changes that have been introduced since the previous major release.

Calendar and Microsoft Graph: Continued expansion of the new backend foundation​

A major focus of this release is the continued evolution of the calendar stack. Several changes prepare the platform for the transition toward the newer Graph-based calendar backend and related APIs.

This includes calendar switch logic, new API building blocks, deeper integration across infrastructure and client modules, and expanded support for recurring appointments. Together, these changes reduce migration risk and support the continued development of Microsoft calendar integration.

Platform internals: New foundations for integrations and configuration access​

The release includes a range of backend changes that strengthen the internal platform architecture. Among them are new service interfaces, early read-only API groundwork, improved access to configuration data, and continued work around system database access.

These changes are mostly internal, but they help make the platform more modular, easier to extend, and better prepared for future service integrations.

Developer experience: Clearer guidance in scripting and documentation​

Several documentation gaps have been closed in this release, especially around validation helpers and JDito-related APIs.

This helps make platform behavior easier to understand and reduces ambiguity when working with scripts and extension points.

REST web services: More robust and better prepared for integration​

REST web services have also been improved across recent platform updates. These changes include clearer API behavior, better support for integration scenarios, and technical hardening in areas such as request handling and interface configuration.

Together, these improvements make external integrations more predictable and help reduce friction when connecting the platform to third-party systems.

Security and hardening: Reduced risk in critical integration areas​

Recent platform updates have also strengthened security and hardening in selected areas. This includes improvements around web service handling and editor-related processing, helping reduce the risk of faulty or unsafe behavior in security-sensitive integration scenarios.

These changes are mostly technical in nature, but they contribute to a more reliable platform foundation for productive use.

Stability improvements across mail, linking, and startup​

Alongside the larger structural changes, 2025.2.0 also includes a range of fixes across infrastructure and runtime behavior. These address issues in areas such as mail processing, remote calendar integration or startup stability.

The result is a release that not only adds important groundwork for future capabilities, but also improves robustness in existing installations.

Below is a brief overview of selected changes:
View the full changelog

CKEditor: First step toward AI-assisted content creation​

An AI assistant is now integrated directly into the editor. It is connected to ADITO’s own infrastructure, fully hosted in Germany and compliant with all GDPR requirements.

Microsoft Graph: New Exchange calendar integration​

For the first time, the platform can access calendar data via Microsoft Graph. This lays the foundation for broader Microsoft 365 integration.

JDito: Modern scripting with extended language support​

The embedded JavaScript engine (Rhino 1.8.0) has been updated, enabling the use of modern language features such as advanced control structures and functions.

REST web services: More robust, efficient, and predictable​

REST interfaces can now be configured more precisely and integrated more reliably with third-party systems. Several technical improvements enhance behavior under load and reduce unnecessary resource consumption. This simplifies external API integration and improves overall system stability.

Designer: Improvements for module development​

The Designer includes multiple enhancements that improve traceability and reduce maintenance effort. These changes support more reliable configuration, particularly in complex data models and rule-based logic.

Lookup, TreeTable, validation: Fewer inconsistencies, better defaults​

Various fixes improve the behavior of lookup fields, tree components, and validation logic. In particular, multi-value inputs now behave more consistently, with better handling of empty values and increased reliability in custom forms.

Infrastructure: Up to date and cleaned up​

Numerous technical dependencies have been updated in the background, including PostgreSQL, Ignite, Quartz, and all JDBC drivers. These updates reduce technical debt, improve long-term maintainability, and minimize the need for manual error handling at runtime.