OAC does work with Chrome 84+. The issues described in the articles affect embedding use cases. We are working on that scenario. ( Doc ID 2665373.1 ) Can you share more details with support about your issue as it is not generally affecting other customers. 

I can't reproduce this on 84.0.4147.135 with SSO. Will investigate. 

You can add these via authoring (as an image or text). Does that work? Is this idea just about making it a default on new projects/canvas?

Is this experience like showing a canvas floating over another canvas (so you don't change navigation)? Does it need to be hover or could it be other gestures like click or hover and click?

Is this mostly about setting a standard theme/colors across Projects in your OAC instance or is it more about what you can and cannot customize in a single Project? Maybe there are two ideas -- a global theme setting and improvements in colors/theming?

100 sections is a lot. 500K is not possible. You indicate you cannot refactor the reports to have less than 100. Is there a specific number that would work? From our knowledge 100 is far more than almost all customers use and we would like to get more insight on why the section count cannot be reduced.

Dileep's comment is correct. We integrate with the identity system's groups and this is the recommended way to manage access and permissions. 

We have an item on the roadmap to allow a simple method to keep an OAC data set up to date. One question here is how fresh the data needs to be for the business case. Some connections (such as to Fusion Apps) do not support LIVE connections where each query is sent to the source for each query. For your scenario, what is a…

These seem like useful additions. It would be interesting to know the full list of ones you would likely use. 

The remote data gateway is optimized for moving data from on-premises to the cloud. If you are moving the data, is there a reason this cannot be written to a cloud source?

This does seem useful.

We were thinking more of a WYSIWYG approach than adding print preview. Although both could be useful. Is this for actual printing or more for export to PDF/image/pptx, etc. 

Export to PDF today is a client-based operation which is dependent on the user’s screen DPI. The users can try adjusting the printing size to find a layout that looks correct with the PDF export. We are working on a improvement to make this easier but it is not yet available.

This capability is on the roadmap.

What would be needed to convert this page to DV project? You can export and print individual visualizations in DV Projects.

Can we get more insight in to the scenario? How many rows can a user realistically read on a page? Or is the main scenario export or are they searching for specific items? Assuming we have to have a limit, what limit would work for your users?

Your usage data may fit on an always free DB instance if the only issue you have is getting an instance. It might be sufficient or could at least help you evaluate how Usage tracking in OAC works and determining your retention needs.

Usage tracking does track activity routed through the RDG. It is conceptually an extension of the connector to a data source. You cloud also evaluate "always free" to get started. https://www.oracle.com/cloud/free/#always-free

Usage tracking does track activity routed through the RDG. It is conceptually an extension of the connector to a data source. You cloud also evaluate "always free" to get started. https://www.oracle.com/cloud/free/#always-free

I see -- you want the cloud service to write to an on-premises DB via the gateway. It is unlikely we will take this approach. The data gateway is very focused on satisfying queries for live analytics and is not intended as a channel for writing. What is the challenge with using a cloud DB? Seems like the real issue is not…