26.1.2 Release Notes
Set out below is a summary of the highlights, fixes and improvements in the 26.1.2 cloud version of Angles for SAP.
End User - Fixes And Improvements
| Feature | Description |
|---|---|
Fixed the Intermittent Internal Server Error When Exporting Angles to Excel. |
An issue has been resolved where users intermittently encountered an internal server error when attempting to export an Angle to Excel in the Cloud (R2) environment. The error prevented the download from completing and required an AppServer service restart as a temporary workaround. This fix addresses the underlying cause of the instability, ensuring that Angle exports to Excel complete successfully and reliably. |
IT User - Fixes and Improvements
| Feature | Description |
|---|---|
Improved Data Type Resolution Consistency Between SAP Extraction and Repository Layer. |
The Platform User Import in ITMC now filters users by their Angles for SAP product assignment. Previously, all Platform users were imported regardless of which ISW products they were licensed for, resulting in unintended user pollution in Angles for SAP and a manual cleanup burden for administrators. Only users with an active Angles for SAP assignment in Platform are now included in the import. |
Integrity Check Performance Improved via Caching in Cloud (R2). |
The Integrity Check process in the Cloud (R2) environment has been improved by introducing caching, consistent with a fix previously applied to the on-premise environment. This change reduces redundant processing during Integrity Check execution, resulting in improved performance and increased stability when running or displaying Angles. Users who previously experienced intermittent internal server errors during Angle Display execution may notice improved reliability as a result of this change. |
Security Fix: Cross-Site Scripting (XSS) Vulnerability Resolved. |
A security vulnerability identified during penetration testing has been resolved. A Persistent Cross-Site Scripting (XSS) vulnerability in the application allowed an authenticated user to inject malicious script content that, if triggered by a privileged user, could result in unauthorized privilege escalation. The fix applies proper context-sensitive output encoding to user-supplied data, preventing script injection. Customers are advised to upgrade to this release to benefit from this security improvement. |
[05543577] Collector Class Not Populated When Migrated from On-Premise (R1) to Cloud (R2). |
An issue has been resolved where a Collector class configuration that functioned correctly in the on-premise environment (R1) failed to populate when the same configuration was applied in the Cloud environment (R2). The class was not being exported to the database, and no errors were reported in the logs, making the issue difficult to detect. This fix ensures that Collector class configurations migrated from R1 to R2 are correctly processed and populated as expected. |