Scheduling a Data Visualization or Project

Gabby Rubin-Oracle

@Michal Zima to be clear, I did not say that it is not planned for OAS; what I said is that to deliver the feature to OAS it will need additional OAS-specific development, which will not make it to OAS 2024. The nuance might not matter to the immediate outcome, but we aim to bring every OAC capability to OAS and vice-versa. In some cases, this can be a very complex task, up to developing two completely separate features for the same use case, which would mean that one might be ahead of the other. Our commitment to OAS is equal to OAC; as a product team, we do not make product decisions based on what we would prefer the customer deployment choice to be.

I acknowledge your feedback about the early notice; this is something we can improve. There was no intent to hide the information or create false assumptions. PMs never promote an enhancement as 'OAC only'; it is only based on engineering and technical design specs when we identify dependencies or the need for separate efforts. It still means that we can be more explicit earlier when we have the information, and I will make sure we will do better.

As always, I appreciate your direct and honest feedback. We can discuss in more detail why this feature is not OAS-ready and what we are considering. As OAC architecture becomes increasingly sophisticated as a cloud service, we see a future risk of increased dual effort and debating scenarios that might help mitigate existing and future gaps. Hearing your feedback on some of these future OAS ideas will be valuable.

Best Regards,

Gabby

Michal Zima

@Gabby Rubin-Oracle thanks for your comprehensive and honest reaction, I appreciate it. I understand, that it can be difficult to "implement" all features in OAS, especially those, bounded to other cloud services (like integration with AI services, OCI functions etc...). But in my humble opinion, features like REST API, DV Scheduling should be designed from the early beginning to be "agnostic" to other cloud services, thus allowing smooth transition to on-prem OAS. I also welcome, that you will consider providing some early notice for planned features, which will not be immediately available in OAS and I still hope, that despite enhanced effort for implementing, those features, we are discussing now (REST API and DV Scheduling), will be implemented in OAS. I am open for further discussion on those topics and definitely would like to know more details about reasons why those features cannot be that easily "transferred" to OAS and your plans how to achieve it.

Thanks and best regards

Michal

Victor H

This feature does not support conditional triggering.

Do we need a separate idea for this?

Gabby Rubin-Oracle

Yes, please. It is helpful for us and the community to track individual ideas.

Victor H

Thanks Gab, I have submitted a new idea for this:

https://community.oracle.com/products/oracleanalytics/discussion/21408/add-conditional-triggers-for-dv-email-scheduler