Skip to main content

Angles Hub 26.2.2 and 26.3 Release Notes

The new features in Angles Hub 26.2.2 is as follows:

Generate Semantic Layer (RPD) for OAC and OAS Generators

Angles Hub's semantic layer (RPD) generation now supports both Oracle Analytics Cloud (OAC) and Oracle Analytics Server (OAS) generators, expanding your analytics platform flexibility. Users can now generate a single RPD file that works with both cloud and on-premise Oracle Analytics deployments. You can now download the RPD files and deploy them to OAC or OAS generators environment, enabling faster self-service analytics activation for business users.

Note: The ability to generate semantic layers (RPD) for OAC and OAS will also be available as part of the 26.3 upgrade.

The new features in Angles Hub 26.3 are as follows:

Angles Hub Certified for OCA 26C

Angles Hub is certified for Oracle Cloud Applications (OCA) 26C, with the replication engine and business views fully validated, enabling you to upgrade your Oracle Cloud Applications to 26C without rebuilding your reports.

Oracle EBS to OADW Replication

Angles Hub enables end-to-end replication from Oracle E-Business Suite (EBS) to Oracle Autonomous Data Warehouse (OADW) allowing you to migrate your entire EBS dataset to OADW using the Full Load option. You can automatically sync only the changes from EBS, maintaining current data without expensive full transfers using the Incremental Load option. You can selectively reload specific tables without affecting other replicated data using the Single Table Refresh option.

Pre-Built EBS Views for Snowflake

Angles Hub delivers pre-built Oracle E-Business Suite (EBS) business views designed for Snowflake, connecting your Oracle EBS data to Snowflake without custom development, which enables you to analyze financial and operational data immediately. You can also choose to customize the pre-built views to fit your specific business requirements.

Automatic Index Creation for Oracle Cloud Applications (OCA) Financial views

Angles Hub automates index management for Oracle Cloud Applications (OCA) financial views replicating to Oracle Autonomous Data Warehouse (OADW), eliminating manual index creation after every load. You can define indexes once by editing a Public View Object (PVO) and selecting the Indexes tab. During each replication load, Angles Hub automatically disables indexes for faster insertion and re-enables them once the replication completes. You can update or drop indexes anytime from the Indexes tab without stopping replication, and the updated indexes will be picked up automatically in the next replication run.

Enhanced Search in the Replication and Application Registration Areas

Search capability has been introduced across dropdowns in the Information and Configuration tabs of the Replication area, and the Application tab of the Application Registration area, eliminating the need to manually scroll through extensive lists. Users can now quickly locate and select the required modules, objects, and items with a simple search query.

Business Views and Reports Page UI Changes

The following are the changes made to the Business View and Reports page:

Business Views page changes

  • Removed the tile view option from Business Views page.

  • Renamed the "Edit View" button to "Open View" button.

  • Removed Copy icon from Business Views page.

  • Business Views always open in read-only mode by default.

  • In read-only mode, you see Cancel, Copy view, and Edit view buttons. In edit mode, you see Save view and Cancel buttons.

  • When you click Save view, your edits are stored permanently and the business view automatically exits edit mode to return to read-only view.

  • Removed the Next button that appears when you open a business view.

Reports page changes

  • Removed tile view option from Reports page.

  • Renamed Edit Report button to Open Report button.

  • Reports always open in read-only mode by default.

  • Copy and Create report options open reports in edit mode.

  • When you click Save Report, your edits are stored permanently and the report automatically exits edit mode to return to read-only view.

  • In read-only mode, you see Help?, Cancel, and Edit report buttons. In edit mode, you see Help?, Save report and Cancel buttons.

Duplicate Public View Objects (PVOs) Prevented Across Packages

Angles Hub now prevents duplicate PVO assignments across packages during creation and import. This keeps your package configuration consistent across Oracle Cloud Applications and Oracle database environments. During package creation, the application checks if selected PVOs already exist in other packages and blocks creation if duplicates are found. The same applies to imports. If an imported package contains a PVO already assigned elsewhere, the import is prevented with an error identifying the conflict. When adding a PVO, you receive a warning if that name already exists. When importing a package, the application automatically overrides the existing PVO. The application treats PVO names as case-insensitive. "MyPVO" and "mypvo" are recognized as the same object and prevented from duplicate assignment. If a duplicate is detected, the package is not partially created or imported, and existing packages remain unchanged.

Role-Based Access Modes for Views and Reports

Angles Hub now implements role-based access controls for business views and reports, preventing accidental overwrites while enabling team collaboration. Users can open in read-only mode by default, allowing multiple team members to view the same resource simultaneously. When modifications are needed, users can request exclusive edit mode access by clicking Edit View or Edit Report. Only one user can hold edit access to a specific resource at any given time. If another user already has an active edit session, the edit request is denied and the resource opens in read-only mode instead.

Edit sessions are automatically released when the user closes the resource, or admins can manually terminate sessions from Administrator > Manage Sessions to prevent locked resources. Sessions automatically expire after thirty minutes of inactivity, terminating only the inactive tab's session while other active sessions continue. Additionally, all existing sessions in application memory and the database are cleared when the server is restarted for upgrades or patches.

Edit restrictions apply only to the specific resource being edited, so multiple users can simultaneously edit different business views and reports without conflict, enabling parallel development workflows. Each business view or report supports unlimited read-only sessions with a maximum of one active edit session. Each browser tab is treated as an independent session.

Customize Business Views Without Losing Changes

Angles Hub now includes a business view customization framework that preserves metadata, relationships, joins, and lists of values across deployments and replication cycles. Instead of losing customizations when the application updates, Angles Hub maintains all dependencies and your persistent customizations. Customize business views with confidence knowing your changes will be preserved through application updates and data replication.

Query Builder Performance Optimizations Reduce Loading Times

When loading tables and views on the Query Builder screen, overall loading time is reduced. The Create Schema Cache operation for Oracle EBS now completes faster, enabling quicker query building and more efficient schema initialization.

Fixed Issues

The fixed issues in Angles Hub are as follows:

Deploy Views with Extended Usernames

When a user attempted to deploy a business view in Angles Hub and their username exceeded thirty characters, the view deployment process failed with an ORA-12899 error.

Angles Hub Excel Add-In Report Browser Performance and Dark Mode Display

When users clicked the Report Browser button, initial loading took longer than expected and a warning message appeared stating, "Excel is waiting for another application to complete the OLE action." Additionally, button icons and text labels were not displaying clearly in Windows dark mode due to insufficient contrast.

Snapshot Reports Performance Optimization in Angles Hub Excel Add-In

Snapshot Reports with large datasets (40,000+ rows) were taking 6–10 hours to complete in Angles Hub Excel Add-in. The ODBC driver was fetching data in small batches, Excel was recalculating the workbook during row writes, and connection timeouts were interrupting long-running queries.

Columns Now Populated for Views Using SELECT * Queries

When creating a view with a SELECT * FROM <table> query, the Columns tab remained empty, making it difficult to verify which columns were being included.

Global Lock Blocked Concurrent Query Builder Loads

When multiple users attempted to open Query Builder simultaneously, they would block each other as all requests used a global static lock. Only one user could load Query Builder at a time, forcing others to wait until the previous session completed.

Switching Views Removed Active Query Builder Sessions

When you opened a different view in another tab, the active Query Builder session was removed from memory, leaving the Query Builder UI empty and non-functional even though the session reference still existed locally.

Query Builder with Same Name Already Exists

When navigating between multiple tabs with different views, reopening Query Builders triggered a naming conflict error, preventing you from accessing the Query Builder interface.

Excessive API calls Degraded Performance After Session Removal

When performing operations on the Query Builder screen after a session was removed, the page would blink repeatedly and trigger 120+ unnecessary API calls per minute to the server, causing significant performance degradation.

Known Issues

The known issue in Angles Hub in as follows:

Parallel Schema Expansion Interrupts Schema Loads

When you attempt to expand multiple schemas simultaneously in the Query Builder, the system interrupts the first schema's load request when you trigger a second expansion. This results in only a partial list of tables and views being displayed for the first schema, as the load completes only for items retrieved before the interruption. As a workaround, expand one schema at a time to ensure all tables and views are fully loaded before expanding additional schemas.

Was this article helpful?

We're sorry to hear that.