Email scheduling has been added to DV workbooks as a preview feature; however, this option does not support triggering the job with a condition (e.g. when a key metric falls below a threshold) .
This seems useful!
Agree - similar functionality as Condition defined for agent in Delivers (Classics).
This is a very critical feature that our customers will love to have. Conditional triggering is critical function to alert on outliers, deviation from thresholds and applying appropriate business rules. Can also we be used for date/time-based conditions as well.
That is a great idea, will help to improve on time delivery reporting and trace issues faster.
@BibinKumar Can you expand on use cases of date/time-based conditions? Some examples are helpful.
Excellent idea. I voted. + @Jacques V.-Oracle for awareness.
@Victor H — add few examples from your side.
@Alan Lee-Oracle - We need the functionality that exists in classic, where agent actions can be triggered based on day/time logic, conditionally depends on some SQL logic or business rules based of dataset attributes (for example #KPI value is >= Aggr(#measure) ) etc.
Great feature to be added. Please consider this great idea.
Has there been any update from Oracle? This is the feature we're looking for; we have to go back to the BI agent and do some additional work there before we can send emails to our customers based on certain conditions.
It'll be a great & useful feature to have.
Upvoted.
OAS Classic Report Results display the first 5000 rows and the OAS user needs to click the next button for the next 5000 rows and so on. The 5000 row limit is the maximum allowed to be setup in the OAS Console. OBIEE Report Results support display of the entire report results data set. Our users would like this feature in…
Background We recently identified an issue through an inconsistency in the number of records returned in an API response. This allowed us to notice, after the fact, that a fix had been applied that changed the behavior of an existing API. Problem We understand that information about resolved bugs is eventually made…
We need a way for non-admin users to view the backend/physical SQL queries executed by reports (via Session and Query Logs) without granting them full administrator access. OAC's custom Application Role model (Console > Roles and Permissions) allows selecting fine-grained permissions instead of assigning predefined roles.…
Customer would like to request that IBM DB2 12.x be added as a supported data source for Oracle Analytics Server. They hope that it will be included as a certified and supported data source in the next(Year 2027 ) OAS release. Background: The customer is currently operating a reporting and analysis platform using Oracle…
We would like to restrict the MCP to certain OAC application roles instead of all the users. Please help us to achieve this functionality.