26.2.1 Release Notes

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

End User - Fixes and Improvements

Feature Description

Currency mapping issue resolved in billing document condition values.

An issue where the condition value currency (KONV_V-KWERT) in billing document reports was displaying incorrectly has been resolved. Users previously saw the condition value amount in a default currency (such as EUR) rather than the actual billing document currency. The currency mapping logic has been corrected to ensure that the condition value field now displays the appropriate currency matching the billing document. This fix applies to all report scenarios involving price condition sales documents and billing amounts.

IT User - Highlights

Feature Description

SQL Server Encrypted Connection Support.

This feature enables Angles for SAP to work with enterprise SQL Server instances that have mandatory encryption policies enabled. The implementation includes:

  • Encrypt Connection toggle in ITMC SQL Server datastore connection settings.

  • Trust Server Certificate toggle for self-signed certificate environments.

  • Connection string modifications that append Encrypt=True and/or TrustServerCertificate=True as configured.

  • Full backward compatibility with existing datastores (defaults remain off).

  • Successful connections to Force Encryption-enabled SQL Servers.

IT User - Fixes and Improvements

Feature Description

Improved Yellowbrick Query Performance via Replicated Lookup Tables.

Small materialized view lookup tables were redefined from DISTRIBUTE RANDOM to DISTRIBUTE REPLICATE in Yellowbrick. This aligns with Yellowbrick best practices and eliminates unnecessary data redistribution steps at query execution time.

F2R Package Activation Fixed.

The issue caused by missing language codes in the template file within the F2R package has been resolved. When activating the package, the system tried to insert multilingual text referencing a language that didn't exist in the SYSTEM_LANGUAGES table.

Fixed Incorrect Auto-Triggered Refresh Action and Task History Visibility.

What Was Fixed:

Two related issues in the auto-trigger mechanism for refresh actions:

  1. Incorrect Action Triggered: After running EATest, the system incorrectly triggered EAInitialize instead of the expected WorkbenchDictionary refresh. This was caused by the auto-trigger lookup using BusinessId ({{ {modelId} _InitializeWorkbenchDictionary}}) which could match a task whose action_list argument had been manually modified via ITMC while the BusinessId remained unchanged.

  2. Task History Not Visible: When automatic refreshes were triggered, the Refresh Cycle history tab did not reflect or show the running status of the triggered task, making it difficult for users to track refresh progress.

Root Cause & Solution: The system now validates that the action_list argument matches the expected "WorkbenchDictionary" value before starting the task. If the argument has been edited via ITMC and no longer matches, the auto-trigger safely skips execution. The fix also: Reverted the auto-trigger condition that checked if the last WorkbenchDictionary task had failed (preventing interference) Removed unnecessary task saving before auto-triggering (resolves intermittent visibility issues)

Impact: This fix unblocks customers experiencing refresh action loops and ensures visibility of auto-triggered tasks in the Refresh Cycle history.

Was this article helpful?

We're sorry to hear that.