Release 26.1 includes a broad set of quality and robustness improvements across the Angles for SAP platform:

• Addressed security vulnerabilities identified through automated scanning.

• Added resource monitoring to improve system visibility and diagnostics.

• Enhanced logging for faster troubleshooting.

• Improved reliability of the model commit process.

• Streamlined setup scripts and optimized HttpClient usage for better efficiency.

• Improved performance and responsiveness under load.

• Completed general code quality and maintainability improvements.

Together, these improvements make Angles for SAP more secure, stable, and maintainable. Users benefit from a more reliable system during refreshes, upgrades, and peak usage — while administrators gain better visibility into import and deployment operations, reducing time spent diagnosing issues.

Several improvements have been made to the stability and reliability of the OData service: Improved OData resilience and overall reliability.

• Added stronger validation to help prevent common error scenarios.

• Enhanced exception handling to provide clearer user feedback.

• Improved resource cleanup in both successful and failed operations.

• Optimized display metadata caching to reduce issues with stale data.

• Improved management of cached collections and readers for more consistent performance.

Together, these improvements make the OData integration significantly more stable and predictable. Users relying on OData feeds in tools like Excel or Power BI can expect fewer unexplained failures, more meaningful error feedback, and greater confidence that their data connections will continue to work reliably — even under adverse conditions.

The OData service has been extended to support the EA4IT model, as well as any other real-time, non-refreshable model in database servers Yellowbrick or SQL Server.

The Management Console now includes a user-configurable feature that allows administrators to define custom retry duration and retry interval settings for SAP extraction failures. This provides greater control over extraction failure handling and resilience and reduces the need for manual intervention during SAP data extraction processes. These settings are configured directly in the Management Console, applied to the app server, and passed to the SAP Extractor API.

When using Quick Filters on the Angles Search Page and clicking the "Clear filter(s)" button, active Quick Filters remained applied. Users had to manually deselect each Quick Filter as a separate action, causing confusion and unnecessary extra steps.

The "Clear filter(s)" button now deactivates all active Quick Filters in addition to clearing other applied filters. Search results refresh immediately to reflect the unfiltered state, and Quick Filter buttons correctly return to their inactive appearance.

This makes filter clearing consistent and intuitive — users can now reset all active filtering in a single click, exactly as expected.

Managing angles just got significantly more efficient. Users can now select and remove multiple displays from an angle in a single action, eliminating the need to delete them one by one. This is especially valuable when working with angle templates that come pre-loaded with displays — users can now quickly trim them down to exactly what they need.

Key Capabilities:

• Execute your angle, then open the Display Overview panel using the button in the top-right corner of the display area
• In the panel, check the boxes next to the displays you want to remove
• Use Select All to quickly mark all eligible displays at once
• Click Delete and confirm the action in the popup dialog to remove all selected displays in one step

Key Benefits:

• Faster angle maintenance — Remove multiple unwanted displays in seconds rather than repeating individual deletions.

• Cleaner, more focused angles — Quickly tailor angle templates to your specific workflow, reducing clutter and improving navigation.

• Simple, accessible interface — The Display Overview panel gives a clear overview of all displays, making it easy to select and manage them without losing context.

• Confident deletions — A confirmation dialog ensures you always review what will be removed before committing.

Aggregated queries like pivot and chart were limited to 500,000 rows to preserve performance in the cloud architecture. The hard limit has been increased to 2,000,000 rows.

Administrators can now gain direct visibility into display health within the EA4IT model. Three new fields — Has Warnings, Has Errors, and Errors and Warnings — have been added to the Displays object, enabling targeted reporting and proactive troubleshooting at the individual display level. A dedicated template display is also included to help you quickly identify and diagnose problematic displays across your environment.

Key Capabilities:

• Has Warnings — a boolean field that flags displays where fields or references no longer exist in the model
• Has Errors — a boolean field that flags displays whose definition contains structural errors, such as references to classes that no longer exist
• Errors and Warnings — an enum set field that shows the specific type of error or warning for each affected display
• All three fields are available for use in custom angles built on the Displays object, and support filtering, sorting, and export
• A new template display on the Displays object provides an out-of-the-box view for identifying and analyzing display issues, including Display name and Angle name
• Field values stay in sync with ITMC Angle Warnings data, ensuring consistent error and warning status across both interfaces

Key Benefits:

• Pinpoint display issues faster: Identify exactly which display within an angle has warnings or errors, eliminating the need to investigate at the angle level first.
• Build tailored health reports: Create custom angles and dashboards on the Displays object to monitor display validity across your entire environment.
• Proactive system maintenance: Use the new fields to continuously track display health and address issues before they impact end users.
• Consistent, reliable data: Warning and error information aligns exactly with the ITMC Angle Warnings feature, giving you a single source of truth across tools.
• Ready to use immediately: The included template display gives administrators an instant starting point for troubleshooting workflows, without the need to build from scratch.

The EA4IT model now tracks whether fields are used in filters, pivot options, and chart options within your angles, extending beyond the existing display usage tracking. Three new boolean fields in the Fields class help you identify fields that aren't actively used in any angle component:

• Is Used In Filter Options
• Is Used In Pivot Options
• Is Used In Chart Options

A new pre-configured display, ‘Fields not used in Displays’, has been added to the Fields template to quickly identify unused fields.

Key Benefits:

• Optimize Custom Content: Identify and remove unused fields to streamline your data model
• Improve Performance: Exclude unused fields from downloads to reduce data volume and improve processing speed
• Better Governance: Make informed decisions about field management based on actual usage patterns across all angle components
• Quick Start Analysis: Use the ready-made display to immediately view fields not used in any angle component

Administrators can now manually import Platform users with status Active or Pending into Angles for SAP via a new button on the ITMC > Users > All Users page. This allows roles to be assigned immediately upon import, without requiring users to log in first.

It was found that on clicking ‘Check action’ the action would end up duplicated in the task. This has been resolved.

When viewing SAP table or field descriptions with multiple language options enabled, the wrong language was displayed regardless of your selected user language. The system consistently showed the first alphabetically sorted language from enabled options instead of matching your user preference.

Language-dependent descriptions now correctly display in your selected user language, ensuring SAP table and field descriptions appear in the language you're working in. If your selected language is not available, the system will display the description in the fallback language.

It was found that the export to Excel or CSV would fail for EA4IT report ‘Fields per Display’. This has been resolved.

It was found that some OData links would suddenly stop working, with the OData log reporting duplicate fields in the display. This was ultimately caused by the angle integrity check process linking to the same field when the technical info would be the same. Resolution was provided in that process as well as additional logging to improve debugging abilities.

Pivot displays configured with an Action List field in the Row Data area and a first-character bucket applied returned a 500 internal server error on execution.

Server-side processing of this Pivot configuration has been corrected. Affected displays now execute and refresh without errors.

It was found that the display page would keep showing the loading icon when exporting to Excel after drilldown to item. This has been resolved.

When configuring an Angle History task in the IT Management Console and selecting Event as the schedule type, clicking Save returned a 404 error ("Instance not found, event with id ''"), preventing the task from being saved.

This issue has been resolved. Users can now successfully create and save Angle History tasks using the Event schedule type. Event-driven data exports can be configured as intended, ensuring automated reporting workflows based on event triggers are no longer blocked.

It was found that an error would be shown when removing a calculated field that was including in sorting the results. This has been resolved by adapting the sorting when removing the calculated field.

It was found that the field selection for a Pivot would be restricted by the Field Chooser filter of an unsaved display. This has been resolved.

It was found that in some scenarios an unsaved display would still be present in the angle after the angle was re-executed. This has been resolved.