nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Trigger-Based Email Support and 19c Connection Support in OAC Classic

User_WO3ML

We request two product enhancements in Oracle Analytics Cloud (OAC):

Support email notification on trigger for reports/workbooks in both OAC DV and Classic.
Support Oracle Autonomous Database 19c connection in OAC Classic without version mismatch issues or confusion caused by the current 12c connection label.

Current Limitation

In OAC DV, there is no native way to send an email when data changes or when a trigger condition is met.
In OAC Classic / BI Publisher, trigger-based email/report execution is not available for content created in DV, and users cannot define event-driven email behavior for DV-based content.
When connecting to Autonomous Database, OAC Classic shows the connection type as 12c, even when the source database is 19c, which creates concern and confusion for users.

Business Need

We need the ability to:

Send an email automatically when a report trigger condition is satisfied.
Use the same trigger-driven notification capability across OAC DV and Classic.
Connect OAC Classic cleanly to Oracle Autonomous Database 19c with clear and supported connection behavior.

Impact

This enhancement would help teams build:

Event-driven reporting
Data-change notifications
Operational alerts
Better integration between OAC and Autonomous Database 19c

Suggested Priority

High, because this is a common enterprise reporting requirement and currently requires workarounds using external OCI services or custom automation.

Find more posts tagged with

Submitted

Analytics

OAC

OAS

Oracle Analytics Cloud

OAC Classic

Status: Submitted

Comments

Gianni Ceresa

The database type in the semantic model isn't expected to exist for all database version. That list would be extremely long if it should list every existing Oracle database version. That's also not the meaning of it.

Based on your request, there should be 4-5 database type for 19c, another 1-2 for 21c, another 4-5 for 23c, then for 23ai, then for 26ai. You see where I'm going with this?

The meaning of that field is to use the right driver, and then set a predefined set of details for the connection (that can be overridden to customize the behaviour if needed).

Victor H

You can do this in classic already, for DV there is an open enhancement request that needs votes:

Add Conditional triggers for DV email scheduler - Oracle

User_WO3ML

In classic, We have only option to 12c driver and my ADW is 19c. So there is driver incompatibility.

Gianni Ceresa

It isn't a literal driver, and anyway: Oracle database drivers are backward and forward compatible.

OAS comes with the drivers it has, have you faced an issue by using a database connection with database type 12c in your semantic model? No, because it isn't what you imagine it is…

It is first and foremost about the details that are set by default when selecting one over the other.