Angles Hub 25.1 Release Notes
This topic describes the new features, fixed issues, and known issues for Angles Hub 25.1, released in March 2025.
New Features
The new features in Angles Hub 25.1 are as follows:
Simplifying Analytics for Oracle Cloud with Angles Hub
Angles Hub now simplifies BI model creation and management for Oracle Analytics Cloud (OAC) when using Oracle ERP Cloud (Fusion) and Autonomous Data Warehouse (ADW). With this update, users can quickly select data views, configure settings, and generate models with minimal effort. Built-in validation ensures data consistency, while automatic row-level security enforces access controls. By eliminating manual setup, this enhancement helps teams save time, reduce errors, and scale reporting with confidence.
Secure Reporting with Replica EBS Database Support
Organizations can now leverage Replica EBS databases for secure, segregated reporting, ensuring optimized performance and compliance. This feature centralizes view management and security configuration, isolating reporting workloads from production to enhance system efficiency. With offloaded reporting and stronger data access controls, teams can meet stringent security and compliance requirements while maintaining seamless operations.
Enhanced On-Premises User Management
Angles Enterprise for Oracle 25.1 simplifies user provisioning and license management for on-premises deployments, removing complexities caused by Azure Active Directory B2C (ADB2C) URL whitelist constraints. This update enables centralized user management through ISW integration, improves license allocation, and enhances compatibility with federated identity providers and ADB2C, ensuring a more seamless access control experience.
Certified Content with Oracle’s Cloud ERP 25A Release
Angles Enterprise for Oracle 25.1 is fully certified with Oracle Cloud ERP 25A, ensuring uninterrupted reporting and analytics across Financials, Supply Chain Management, Project Portfolio Management, and Human Capital Management. The Oracle Cloud ERP 25A certification allows customers to confidently upgrade to the latest Oracle Cloud release while maintaining reporting integrity.
Base users can customize report configurations
Base users can now create and customize both snapshot and non-snapshot reports.
[ANGO-3830]
Fixed issues
The fixed issues in Angles Hub 26.1 are as follows:
Synchronize users
When you tried to synchronize users, the status on the task monitor page showed as failed, and no information was found on the logs page due to the expiration of the client secret value.
[ANGO-3853]
Snapshot workflow streamlined
You were unable to create a table for several snapshot based reports.
[ANGO-3825]
Schedule snapshots using cron expressions
If reports were scheduled using cron expressions, the scheduled snapshots did not run as expected.
[ANGO-3825]
Personalized reports inherit snapshot tables and filters
Personalized reports based on snapshots failed to inherit the base snapshot tables and filters. This failure caused data discrepancies and performance issues.
[ANGO-3826]
Inconsistent behavior of IN operator
The IN operator behaved inconsistently when filtering string-based numeric values. In a custom report, querying with account values (for example, 1311, 1312, 1315) incorrectly returned only a subset of the expected results (for example, 1311), leading to missing records.
[ANGO-3845]
Support reports with calculated fields for extraction
Reports containing calculated fields were not supported for extraction from the Noetix Platform. As a result, users who rely on calculated fields for reporting faced limitations when extracting reports and importing content to Angles Hub.
[ANGO-3810]
Run prebuilt reports in Excel Add-in
The prebuilt Angles for Oracle reports failed to run in the Excel Add-in. As a result, users could not directly utilize standard reports in the Excel Add-in without making adjustments.
[ANGO-3811]
Run imported reports from Noetix Web Query (NWQ)
The imported reports from Noetix Web Query (NWQ) to Angles Hub failed to run in the Excel Add-in. As a result, users, who migrated reported from NWQ, could not directly utilize standard reports in the Excel Add-in without making adjustments.
[ANGO-3812]
Excel Add-in locked all open Excel Add-in workbooks while running reports
When a report was running in the Excel Add-in, the current workbook was locked and all other open workbooks became unusable until the process finished. This prevented users from switching between workbooks and disrupted managing multiple reports.
[ANGO-3848]
Column sorting in the SQL query or columns criteria tab
Users were unable to sort report columns in the SQL Query or Column Criteria tab, which restricted flexibility in report structuring and required post-extraction sorting.
[ANGO-3846]
On-Premise or Offline Hub with single sign-on (SSO) prevented Excel Add-in usage
Customers using an on-premises or offline Hub with single sign-on (SSO) authentication could not use the Excel Add-in.
Certification Update for Excel Add-in Compatibility with Visual C++ Redistributables
The Excel Add-in is certified to function with the Microsoft Visual C++ 2015-2022 Redistributable, which includes support for 2015, 2017, 2019, and 2022 versions as part of a unified package. For the latest version, refer to Microsoft Visual C++ Redistributables.
[ANGO-3863]
Known issues
The known issues in Angles Hub 26.1 are as follows:
Excel Add-in crash due to data type mismatch in extracted reports
The Excel Add-in crashed when extracted report data did not match the expected data type, causing disruptions when working with reports containing unexpected or inconsistent data types. To prevent this issue, modify the data type of the affected column using TO_NUMBER, TO_CHAR, or TO_DATE functions to ensure consistency before running the report in the Excel Add-in.
[ANGO-3802]
Excess Metadata Extraction in Platform Report Extractor
The Platform Report Extractor retrieves metadata for multiple views, even when extracting a single report, which may lead to unnecessary data retrieval, causing confusion and inefficiencies in metadata management.
[ANGO-3809]
Date Fields as Optional Parameters Cannot Be Cleared in Excel Add-in
Users are unable to clear the default value for a date field when it is set as an optional parameter. This restricts flexibility in report execution when working with date-based filtering. As a temporary solution, users can modify the default date value instead of clearing it entirely.
[ANGO-3814]
Error occurs when the Property icon is selected
When the Properties icon is selected in the Excel Add-in, an error occurs, hindering users from modifying report configurations effectively. As a workaround, users should avoid selecting the Properties icon or restart the application if an error occurs.
Report Header Row in Excel Add-in gets overwritten after modifying column labels
If column labels are modified in an Excel Add-in report, the header row is overwritten upon running the report, causing users to lose customized headers and leading to inconsistencies in report formatting. As a workaround, save a separate version of the report after modifying column labels. Alternatively, modify the report SQL with appropriate column aliases to reflect the headers, or define the column names in the Column Criteria tab.
Prolonged initial load time for reports in Excel Add-in
When you try to load the reports for the first time in the Excel Add-in, it takes longer than expected. This delays user workflows, especially when there are a large number of reports. As a workaround, optimize the number of reports assigned to the appropriate workspaces. Alternatively, retrieve the report list in advance, and subsequent report retrieval will quicker.
Addressing Excel Generator Limitations with Excel Add-in
The Excel Generator functionality related to filters, parameters, and data retrieval has some limitations, preventing users from generating reports with advanced filters and parameters. To address this, use the Excel Add-in instead, which provides equivalent functionality.
Export to Excel not working as expected
The Export to Excel feature does not function as expected, preventing users from exporting reports directly to Excel. To address this, use the Excel Add-in for exporting and working with reports in Excel.
Automatic Fill-Down not supported in Excel Add-in
The Excel Add-in does not automatically fill down formulas based on the retrieved line count, requiring users to manually apply formulas to additional rows. To address this, perform a manual fill-down after running reports.
Automatic data range adjustment for pivot tables and diagrams not supported
The Excel Add-in does not automatically adjust data ranges for pivot tables or diagrams based on the retrieved line count, requiring users to manually update pivot table ranges and diagram references after data retrieval. To address this, adjust data ranges manually when new data is retrieved.
Sorting reports based on module, workspace, or view name not supported
Users cannot sort reports based on module, workspace, or view name, making it difficult to organize and locate reports efficiently. To address this, use manual filtering or search functions as an alternative sorting method.
Snapshot-Based Reports do not allow column aliases
Reports that rely on snapshot-based data retrieval do not support column aliases, preventing users from renaming or customizing column headers dynamically. As a workaround, use standard reports where aliasing is supported or modify the report output manually.
Complex SQL queries not supported in report definition's SQL Query
The reporting engine does not support complex SQL query structures, limiting advanced query customization. Users who rely on nested queries, CTEs, or subqueries may face execution failures. As a workaround, break down queries into simpler structures, pre-process data within the database, or use snapshot-based reports.
Snapshot rescheduling not reflected in user interface (UI)
When rescheduling a snapshot-based report, the changes do not reflect immediately in the user interface (UI), causing users to assume the schedule has not been updated. As a workaround, refresh the page manually or search for "Current Scheduler is" in the Scheduler tab.
[ANGO-3843]
Personal workspaces must be manually created by administrators
User-specific personal workspaces do not generate automatically and must be manually configured by an admin, delaying onboarding and increasing the administrative workload. As a workaround, implement a workspace creation policy as part of user provisioning.