26.2.2 Release Notes

Set out below is a summary of the highlights, fixes and improvements in the 26.2.2 cloud version of Angles for SAP.

End User - Fixes and Improvements

FeatureDescription
PDScheduleLine: The ordered quantity is incorrect when the received quantity exceeds the quantity ordered.

Resolved an issue where the Ordered Quantity on the Purchase Order Schedule Line could show an incorrect value when the received quantity exceeded the ordered quantity. In affected cases, the schedule line's Ordered Quantity was miscalculated, which also inflated the corresponding total at the Purchase Document item level (since that value is a summation across schedule lines).

Ordered Quantity now correctly reflects what was actually ordered on each schedule line.

[05590620] Fixed application crash during metadata indexing.Resolved an issue where the application could crash unexpectedly during the metadata indexing phase of a model import, with no application logs generated to explain the failure. The crash occurred when an underlying search-index error was not handled correctly, causing the process to terminate abruptly. Error handling has been improved so this category of failure is now caught correctly and logged, preventing the crash and allowing the root cause to be identified if it recurs.
[05585918] Fixed search label sort order in filter section.Resolved an issue where search labels in the filter section could appear in the wrong order compared to previously configured environments. The sort sequence is now applied correctly and consistently, so search labels display in the expected order.

IT User - Fixes and Improvements

FeatureDescription
Modeling + Designer Workbench – User ID and Timestamp Logging for Critical Actions.Critical actions in the Designer Workbench (Commit, Import, Create, Edit, Delete) are now logged server-side with the user ID, timestamp, action type, and affected resource — including when the action fails. Logs follow a consistent, filterable format, making it faster to trace who made a change and investigate unexpected or unwanted edits.
Prevent Default Assignment of SYSTEM_ALL Role for Production Environments.The default role assignment has now been changed so that SYSTEM_ALL is no longer applied automatically to all users. Only users with the platform's Account Manager privilege continue to receive elevated (admin) access; other users receive a more restrictive default role, reducing unnecessary exposure of administrative capabilities.
Audit Log Improvement: Reduced Duplicate Entries Across Display, Export, and OData Actions.

The Audit Log previously recorded multiple entries for a single logical user action, making logs harder to interpret and consuming unnecessary storage. This has been streamlined across three areas:

  • Display execution: Executing a display previously wrote two entries - one for the display itself and a redundant one for the underlying Angle. Only a single entry is now written.
  • Manual and automatic export: Exporting a display previously generated three entries fora single action. The redundant "Execute" entry accompanying an export is no longer written.

This makes the Audit Log easier to read and reduces unnecessary log storage growth.

EA4IT: Warning count mismatch between ITMC and Angle Warning properties.

An issue where warning counts shown in ITMC's Angle Warnings page did not match the corresponding Count(ErrorAndWarningType) property on Angle and Display objects in EA4IT has been resolved. The mismatch was caused by three separate issues in the warning count logic:

  • A key-generation collision that caused distinct Angle/Display warning pairs to be incorrectly treated as duplicates, understating the count.
  • Displays incorrectly inheriting angle-level warnings (such as jump, filter, and start-object warnings), which inflated display-level counts with warnings that should only be attributed at the angle level.
  • Internal, developer-facing warning type labels being used instead of the user-facing labels shown in ITMC.

Warning counts in EA4IT now consistently match what is shown in ITMC's Angle Warnings page, at both the angle and display level.

Fixed data loss when saving admin messages with pasted images.Resolved an issue in ITMC > Global Settings > Home Page where saving an administrator message that included a pasted image (for example a screenshot copied directly into the editor) could fail and remove previously entered content. Pasted images are now saved correctly, and existing message content is preserved.
[05600095] Fixed extraction failure for SAP systems on FM 431 requiring SimpleRFC.Resolved an issue where model refreshes failed on SAP 700/FM 431 environments that rely on the SimpleRFC copy method, which had been unintentionally removed. Extractions now complete successfully again for environments using this configuration.
Restored missing sales item category field for S/4 standard content.Resolved an issue introduced in R2 v26.2 where the VBAP-PSTYV (Sales document item category) field was missing from the standard content for S/4 systems, which could generate Angle warnings for content relying on this field. The field has been restored to the default configuration.
[05602297] Fixed delta replication failure for RFC_NET connections.Resolved an issue introduced in v26.2 where delta replication could stop working for models using the RFC_NET copy method, causing tables to fall back to full extraction only. Delta extractions now run correctly again after refresh.
[05602361] Fixed content activation failure caused by missing SQL info for email fields.Resolved an issue where activating new standard content could fail on environments with SQL validation enabled (Skip SQL disabled), due to missing SQL declarations for the EmailID_New and EmailID_Old fields. These fields are now correctly declared, allowing content activation to complete successfully.
[05605192, 05605196] Fixed delta table restructuring failure during refresh.Resolved an issue where certain tables included in Delta Triggers (e.g., STXH, VBPA, JEST) could fail to update during a refresh, with the delta merge step failing silently while the rest of the refresh continued. Delta merging for these tables now runs correctly.

Was this article helpful?

We're sorry to hear that.