Angles Hub 26.2 Release Notes

New Features

Snowflake Replication

Angles Hub now supports replication from Oracle E-Business Suite (EBS) and Oracle Cloud Applications (OCA) to Snowflake. This feature enables you to replicate data into Snowflake using full load and incremental (CDC) replication with built-in status monitoring, single table refresh, and data validation. OCA replication includes support for Force Incremental Refresh, while EBS replication supports full load and standard incremental modes, providing a complete and reliable data pipeline for your reporting and analytics needs.

Snowflake Key-Pair Authentication

Angles Hub now supports key-pair authentication for Snowflake replication connections. This provides a secure alternative to username and password authentication, allowing replication connections to authenticate using a private key and passphrase without any changes to your existing connection configuration.

For more information, see Configure Snowflake Key-Pair Authentication.

Compatible with Latest Oracle E-Business Suite and Oracle Database Versions

NoetixViews 7.1 is compatible with the latest Oracle E-Business Suite and Oracle database versions:

• Oracle E-Business Suite 12.2.14 with Oracle Database 19c – Supported for both Angles Hub and NoetixViews Administrator
• Oracle E-Business Suite 12.2.15 with Oracle Database 26 AI – Supported for Angles Hub

For more information, see Configure Snowflake Key Pair Authentication.

PVOs Metadata Operations

Users can now create, retrieve, update, and delete Public View Objects (PVOs) metadata directly via API from the Angles Hub interface. Additionally, users can perform single or bulk refresh operations and single or bulk upload operations on PVOs metadata records, giving administrators precise control over metadata configurations without leaving the platform.

PVOs Descriptions and DataStoreName Field

Users can now view Public View Objects (PVOs) descriptions sourced directly from Oracle documentation within the Angles Hub interface. In the Configuration section, accessible while editing the replication package, descriptions appear as a read-only field on the PVO configuration page, with long descriptions truncated and accessible via tooltip. A new DataStoreName field has also been added and is accessible while editing PVOs, and PVOs without descriptions display an empty state by default.

PVOs Metadata Export and Import

The system validates the uploaded file's structure and data integrity, detects conflicts such as duplicate or existing Public View Objects (PVOs) metadata, and allows users to choose a resolution strategy such as overwrite, skip, or rename before the import completes.

Replication Log Filtering and Retention

Users can now filter replication logs by a specific time range such as the last seven days, last thirty days, or a custom range, making it easier to analyze relevant data without impacting UI performance. Logs are restricted to a defined retention window, and older logs beyond the retention period are automatically removed to keep the log view clean and up to date.

Create Replication Package User Interface (UI) Flow Update

Users can now create replication packages through a redesigned flow that follows a more logical sequence of the Information, Configuration, Content, and Scheduler tabs. New connections can be created from within the flow without navigating away, and the package description is editable when modifying an existing package.

Retry and Timeout Mechanism for Replication Flow

Angles Hub now includes a retry mechanism across all replication microservices. When a transient failure occurs during package run, the system automatically retries the operation based on configurable retry count and interval settings, without requiring manual intervention. All retry attempts, failures, and final run statuses are logged with meaningful error messages to support monitoring and diagnostics.

Confirmation Prompts for Critical Actions

Users now see a confirmation prompt before running critical actions such as Full Refresh, Incremental Refresh, and Save Package, preventing accidental run of high-impact operations. The Save Package prompt clearly indicates that the action reinitializes the BICC package and may trigger a full load, requiring users to explicitly confirm or cancel before proceeding.

Replication Reconciliation Logs

When you initialize, perform a full refresh, or run an incremental load on your Oracle Cloud Applications (OCA) replication packages, reconciliation records are automatically generated and stored in your target database (Snowflake or Oracle Autonomous Data Warehouse (OADW)). These logs capture detailed information about each table load, including records downloaded, inserted, updated, elapsed time, timestamps, and run status, as well as a summary of the entire package run. Mismatches are automatically identified and logged. The feature is enabled by default and can be disabled through a configuration script (appsettings.json) to prevent the reconciliation records from being created and maintained.

Enhanced Replication Logs Window

The replication logs window has been enhanced by removing the redundant Fetch all logs option. You can now retrieve logs more efficiently using the date range picker by specifying your desired date range, providing a streamlined and intuitive log retrieval experience.

Quick Table View from Replication Page

You can now view all tables in a package directly from the Replication page by clicking the table count in the Tables & Records column, without opening the package or navigating to the Content tab.

Blank Values Standardized to NULL in Replication

During Oracle Cloud Applications (OCA) to Oracle Autonomous Data Warehouse (OADW) replication, values containing only blanks or whitespace in all supported data types are now normalized to NULL. This standardization ensures empty values are consistently represented in the target database, improving data quality and simplifying downstream processing and reporting. Blank and whitespace-only values are treated as missing data rather than valid data entries, aligning with the target system's data handling practices.

Fixed Issues

Excel Report Extraction with Optional Date Parameter

When you attempted to extract a report to Excel using a Date parameter configured with the "between" operator and marked as Optional, the report failed to run when the date fields were cleared and left as the default placeholder (mm/dd/yyyy), despite the report executing successfully when valid start and end dates were provided.

Import Report with Order By Column

When you exported reports from the source environment and imported them into the target environment using the import/export feature in Angles Hub, the "Order By" column configurations were not carried over, despite being correctly set in the source environment.

Projects Billing and Projects Extension Views Assigned to Incorrect Module

When you navigated to the Projects Billing and Projects Extension views in Angles Hub, the views were assigned to the Noetix Technical module instead of the Projects role.

User Interface (UI) Issues

The following User Interface (UI) issues were identified and resolved across the Replication and Task Monitor screens in Angles Hub:

• When you searched on the Replication page, results were returned across all columns instead of being scoped to the Replication Task Name column only.
• When you searched on the Task Monitor screen, results were returned from the Description column instead of being scoped to the Task Name column only.

Last Extract Date Not Reset on Replication Failure

When a replication job failed after extraction but before the Autonomous Data Warehouse (ADW) load completed, the last extract date was not reset, causing subsequent runs to skip the failed data window and create gaps in replicated data.

Data Type Mapping

Numeric columns in Oracle Cloud Applications (OCA) and Oracle E-Business Suite (EBS) data sources were being incorrectly mapped as Numeric(18) instead of Numeric(38), which caused precision loss for columns requiring higher decimal values.

SSL Certificate Validation

A Secure Sockets Layer (SSL) validation issue occurred when connecting to Oracle Autonomous Data Warehouse (OADW) because the certificate was issued for a hostname, while the connection was attempted using an IP address. The configuration was updated to use the hostname instead of the IP address when establishing target database connections.

False Mismatch Alert Notifications

False mismatch alert notifications were being triggered during replication runs even when there were no actual reconciliation mismatches, causing customers to receive inaccurate alerts about their replication status.

Application Type Selection

When setting up a new custom workspace, the Application Type was automatically selected as E-Business Suite-Azure SQL. This caused users to miss the setting and create workspaces with the wrong configuration. The Application Type field is now blank by default, requiring users to actively choose the correct option for your needs.

Hub Query Tab Now Loads Oracle Views with Reserved Keywords

The Hub Query tab was failing when Oracle views used certain reserved keywords (such as To_Date or LOCAL) as column or table aliases. SQL is now normalized when it reaches the query builder and restored before execution, keeping your view definitions, report results, and saved SQL unchanged. If reserved keywords don't affect your views, you'll see no difference in behavior.

Known Issues

Missing Joins in RPD After Customizing a View in Angles Hub

When you add columns to the PO_Vendor_Sites view using Angles Hub and redeploy the updated view code, the RPD regeneration completes successfully but joins between PO_Vendor_Sites and related views are missing, causing Oracle Business Intelligence Enterprise Edition (OBIEE) reports to fail.

Hyperlink Not Working in Reports After OBIEE RPD Regeneration

When you perform an Oracle Business Intelligence Enterprise Edition (OBIEE) Repository Metadata File (RPD) regeneration after making customizations using Angles Hub, the Use for Display flag is disabled in the regenerated RPD, causing hyperlink drill-down functionality in reports to stop working.