The OData model for angles/displays for R1/on-premise used to be cached in memory and synchronized on request or set intervals. This has been replaced by a dynamic load of the definitions. Displays are still cached for a limited amount of time (two minutes) to optimize load times for running queries. However, when a display is changed in the Web Client, the changes of the display will already be available in OData upon new request. The previously active limit to the number of angles returned in the UI (500) is no longer observed as the Application Server will search for all the angles when searching.

This new feature allows specifying overrides on ExchangeRateType, used when converting currency values into the configured standard (translation) currency.This can be used when for instance the mid-market exchange rate type 'M' doesn't provide the required Exchange Rates, but another one.To configure this, navigate to IT Management Console, Content Parameters, Enterprise Configuration, “Overrides on ExchangeRateType” setting.

Administrators can now uniquely identify which specific Angles and Displays are scheduled or executed as automated tasks. Previously, when multiple Angles or Displays shared the same name, it was challenging to determine which exact object was automated. Enhancements:✅ Added a reference link from Automation Task Actions and Automated Task Action History to the corresponding Angle and Display objects.✅ Angle ID & Display ID are now available for analysis, providing precise identification of automated tasks. This update helps administrators accurately track and analyze the automation of Angles and Displays, eliminating confusion caused by duplicate names.

This feature introduces an ‘Include Empty Values’ checkbox to every angle and display filter in the UI. Previously, filtering on date fields in R2 excluded empty values by default, creating inconsistencies compared to R1 and making it difficult to include records with missing dates. With this enhancement: ✅ Users can now choose to include empty values when applying a filter, ensuring greater flexibility and alignment with R1 behavior.✅ The checkbox is available for each individual filter step, allowing for precise control over filtering behavior.✅ This feature enhances predictability and usability, making it easier to filter data without complex workarounds. This improvement reduces discrepancies when upgrading from R1 to R2 and simplifies filtering across multiple business scenarios.

This feature introduces two key enhancements for automated tasks when saving to SharePoint, bringing it in line with other data store export options. New features include:✅ Appending files – Allows users to create a data history, making it easier to track changes and analyze trends in external applications like Power BI and Excel.✅ Attaching output to email notifications – Enables users to receive automated email notifications with the exported file attached, improving task execution monitoring. Previously, these functionalities were only available for other export types like Excel and CSV. With this update, SharePoint exports now offer the same level of flexibility and usability, ensuring better data tracking and enhanced automation workflows.

This feature introduces email attachment size validation for automated task emails, ensuring attachments do not exceed a configurable size limit before sending. New features include:✅ Configurable max-attachment-size setting – Default set to 20MB, adjustable by admin users in the system settings page to align with different email system limitations.✅ Pre-send validation – Prevents oversized attachments from being sent, avoiding email failures.✅ Clear error notifications – If an attachment exceeds the limit, users receive:- A descriptive error message explaining the issue- Email notification to intended recipients informing them of the problem- Detailed log entries for troubleshooting- Automation task status update, indicating the task ran successfully but the file was too large to send This enhancement improves reliability, transparency, and troubleshooting for automated email tasks, ensuring smoother workflow execution and error handling.

With this feature, administrators now have greater control over the Calculated Fields feature in Angles for SAP. Previously available to all users, this feature can now be restricted based on user roles within the authorization model. Administrators can allow, deny, or leave access undefined, ensuring that only authorized users can create or edit calculated fields while maintaining visibility of shared, validated fields. This enhancement strengthens security, ensures consistency in role-based access control, and aligns with other configurable user permissions.

The latest updates to the GUE Dashboards include a refreshed design that improves usability and visual appeal. These enhancements aim to provide users with a more intuitive and engaging experience when interacting with their dashboards. These changes not only enhance the aesthetic quality of the dashboards but also improve user engagement, supporting users in making data-driven decisions more efficiently.

The Designer Workbench is a self-service Angles for SAP model customization tool, allowing customers and partners to create custom model extensions by adding new data, properties, and relationships to the standard Angles for SAP model. We have added the following enhancement:✅ Extend Standard Module Classes by adding references and sublists to your modelAdding references and sublists enables deeper customization of the Angles for SAP model to fit your specific needs. By creating non-SAP data source classes within Angles for SAP and seamlessly integrating them through standard references and sublists, you can perform cross-functional analysis and drill down into your data with greater flexibility. This enhancement empowers you to gain richer insights into your business questions, driving more informed decision-making.

The Multi-Level Jumps functionality is now available in Angles for SAP (Cloud Saas).This feature was already available in the on-premise version of Angles for SAP and is now aligned across both products.Multi-Level Jumps enable navigating beyond direct object relationships by providing visibility into end-to-end dependencies across multiple steps in the process flow. This supports more comprehensive analysis of process execution, dependencies, and potential issues. Examples of Multi-Level Jumps:✅ Delivering OrdersProvides visibility into all upstream orders that are supplying the current order. For example, a sales order may depend on a work order, which in turn requires a purchase order. This jump traces such upstream links across all levels. ✅ Dependent OrdersIdentifies all downstream orders that are dependent on the current one. For example, a purchase order may be linked to a production…