25.4.4 Release Notes
Set out below is a summary of the highlights, fixes and improvements in the 25.4.4 cloud version of Angles for SAP.
End User - Fixes and Improvements
| Feature | Description |
|---|---|
Designer Workbench | Validation on presence of spaces for key properties like 'Name'. |
The presence of spaces in key properties like ‘Name’ causes a refresh to fail. To prevent this, validation rules have been added in the UI as well as in the commit process. |
Web Client | Save All option not enabled when executing angle with execution parameter. |
It was found that on executing an angle with execution parameter the Save All option would not be enabled. This has been resolved. |
Duplicate fields reported in angle by integrity check. |
The integrity check would report duplicate fields within angles for some templates. This has been resolved. |
Web Client | Execute at login does not work. |
It was found that in some scenario the angle configured to execute at login would not actually do so. This has been resolved. |
Web Client | Internal server error when filtering on Angles Changes After. |
An Internal Server Error would be shown when attempting to filter by Angles Changes After in the search page. This has been resolved. |
[05473907] Changing description of private new display in validated angle is not possible. |
It was found not to be possible to change the description of a private new display in a validated angle. This has been resolved. |
[05483347] Error with calculated field in column area of Pivot. |
An error would be shown when using a calculated field in the column area of a Pivot display. This has been resolved. |
[05474959] Inconsistent result after setting filter on field in 'ask at execution'. |
It was found that the result would behave inconsistently after setting a filter on a field in ‘ask at execution’. This has been resolved. |
[05493433] OData | Serving old data after upgrade. |
It was found that the OData service would serve old data for some time following a product upgrade. A caching mechanism was in place for performance reasons. This mechanism has been changed to reduce the risk of using old definitions for too long. |
IT User - Usability Improvements
System health insights available in ITMC. |
The system health insights can be viewed by clicking the ‘Health’ button in the Components page in ITMC. |
IT User - Fixes and Improvements
| Feature | Description |
|---|---|
|
OData | Small improvements.
|
The OData service has received small improvements:
|
Refresh | Small improvements. |
The refresh process has received some small improvements:
|
RMS | Improvements on query complexity. |
The Realtime Model Server has been improved to reduce query complexity. This has a positive impact on both robustness as well as performance in the data warehouse. |
EA4IT | Improvement on enumset creation. |
Analysis on degraded performance with the Application Server database identified multiple views where the enumset creation could be improved significantly. These enumsets were dynamically created based on views like the audit log and other history tables, where the enumsets themselves could actually be declared statically. This has been done now. |
Commit failed intermittently due to timeout in Workbench. |
It was found that the commit in Workbench would intermittently fail on a timeout in the validation process. As a side effect, an error on some file path not existing could be shown as well. Since this specific action is notoriously long-running, the timeout has been increased to prevent future failures. |
Deployment | Robustness improvements. |
The deployment process has received some improvements for robustness:
|
[05479119] Inconsistent behavior in field selector during role creation in ITMC. |
It was found that the field selector from role creation in ITMC would show inconsistent behavior on displaying sources and field info. This has been resolved. |
[05477049] Work Order status cannot be configured in Workbench. |
It was found that statuses could no longer be configured for Work Order in the Workbench. This has been resolved. |