26.3.2 Release Notes

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

End User - Fixes and Improvements

FeatureDescription
[05659427] Performance: Large OData and web client queries on wide angles no longer time out
 
Angles with many fields and many joined tables, such as sales document item angles, no longer time out when you request large result sets through OData or open them in the web client. Previously, these requests could take more than 300 seconds to return the first row, and clients received ServiceUnavailable or timeout (500) errors. Filters on columns from joined tables continue to work as before.
[05671174] Angles Creation: Angle names with an ampersand (&) are saved and displayed correctlyAngle names that contained an ampersand (&) were saved with extra characters, so the name did not match what the user typed. Ampersands in angle names are now saved and displayed as typed.
[05671246] Angle Execution: Jumps with a filter on a reference field work again
 
Running a jump on a result that is filtered on a field from a reference no longer fails with an SQL error (“missing FROM-clause entry”). The jump now runs and returns its results.
[05671365] Angle Execution: Date filters after a jump or on a calculated date field no longer failAn issue has been resolved where date and time filters could fail with a database error. This happened when a date filter was applied after a jump to an object type without the filtered field, and when a filter used a calculated date field. Both cases now work. Number, text, enum and boolean filters were not affected.
[05672124] IT: OData field names containing ":" or "/" no longer cause errors
 
An issue has been resolved where OData requests for angles could fail with a 500 error when a field name contained a colon or a forward slash. Requests for these fields now complete without error.
[05672149] Calculated Fields: Multi-class angles no longer cause "Data is not queryable" errorsAn issue has been resolved where angles based on multiple classes could fail with a "Data is not queryable" error when they used a calculated field, either as a column or in a filter. Calculated fields now work on multi-class angles.
[05679804] Workbench: Dictionary refresh no longer fails for newer Yellowbrick hostsAn issue has been resolved where Workbench dictionary refreshes could fail during the upload to Yellowbrick when the connection used a newer Yellowbrick host name. Dictionary refreshes now complete for these hosts.
[05679938] IT: Unexpected sign-out about an hour after signing in
 
An issue has been resolved where some users were signed out of Angles for SAP about an hour after signing in. This happened when signing in from a bookmarked or restored sign-in link, or after an application pool recycle. Sign-in from these links now completes correctly.
[05682007] Automation Tasks: prevent duplicate concurrent manual executions
 
Previously, a manually triggered Automation Task could be started again while an earlier execution was still running. This created several instances of the same task at once, adding load on the server and creating duplicate exports and SharePoint uploads. ITMC now checks whether an Automation Task is already running before accepting a manual trigger. If it is, you see a message asking you to wait until the current execution finishes, or to abort it, before you retry.
AI search: filter values no longer match loosely
 
An issue has been resolved where AI Search matched filter values loosely, so results could include values the user did not mean. Filter values now match as the user intended.
AI search: no longer shows an internal server error after the session has been idleAI search could return a “500: Internal Server Error” after a period of inactivity, and the error continued for every later prompt until the user refreshed the session. AI search now returns results after inactivity without this error. If the session has expired, the user is asked to sign in again.
Angles Search: Executed On column sorts never-executed angles correctlyAn issue has been resolved where sorting the Angles Search page by Executed On returned incorrect results. Angles that had never been executed showed "Never" and were not sorted by date. When sorting on Executed On, the sorting is based on when the current user has executed angles. When a user has created an angle but has never executed it after the initial creation, the execution date is now equal to the creation date.
Angles Search: Info popup shows all angle informationOn the Search page, the info popup for an angle with a long description could cut off the end of the text, and the hidden content, such as the start object specification, was only visible after the user resized the popup. The popup now shows all of the angle’s information without resizing.
Calculated Fields: Sorted calculated fields can be exported to ExcelAn issue has been resolved where exporting to Excel failed with an error when the data was sorted on a calculated field. Sorted calculated field data now exports to Excel without errors.
Datastores: SharePoint Document Library is now optionalAn issue has been resolved when creating an Excel or CSV datastore with “Save to: SharePoint,” leaving the Document Library field empty no longer shows a “This field is required” error. The field is optional, as its description states, and you can save the datastore without choosing a library.
ITMC: Application log downloads complete instead of redirecting to the error pageAn issue has been resolved where downloading application logs from ITMC or the web server redirected to the error page. Log downloads now complete as expected.

End User - Usability Improvements

FeatureDescription
AI Search: Sort results by column headers, just like classical searchThe AI Search feature now supports sorting search results directly from column headers, matching the familiar experience of classical search. Users can click any column header to sort the results in ascending or descending order. The selected sort order is retained as users continue the conversation until they manually select a different sort or start a new conversation. When a user's prompt explicitly requests a sort, the AI-requested sort takes precedence, and any subsequent header click resumes manual sorting control.
Automation Tasks: configurable export page size and Microsoft Graph upload block size in ITMC

ITMC now lets administrators configure two performance settings in System Settings, without editing server files or code.

  • Default maximum export page size sets how many rows are requested from the Model Server per batch during automation exports. Default is 10,000; valid range is 1 to 25,000. Larger batches speed up exports of large datasets but use more memory on the Application Server and Model Server.
  • Microsoft Graph maximum upload block size (MB) sets the block size used when automation tasks upload files to SharePoint. Default is 10 MB; valid range is 1 to 50 MB. The new value takes effect after the Application Server service is restarted.

Changing either setting shows a confirmation prompt before saving.

Query engine: CTE engine available as a per-model settingRTMS now includes the CTE query engine for query complexity reduction alongside the legacy engine. Administrators choose the engine for each model with the query_manager_query_engine setting (CTE or Legacy (default)). Switching a model to Legacy restores the SQL generated in 26.3.1. The change applies to new queries straight away, with no RMS restart. Each query runs on one engine from start to finish, so changing the setting during a query can’t mix the two. CTE SQL includes an engine=cte trace comment, so you can see which engine ran a query.

 

Was this article helpful?

We're sorry to hear that.