Categories
Is it possible in OAS to use Javascript (markup) to change default behaviour of Classic Dashboards?
hi - Is it possible in OAS and even advisable to use Javascript (markup) to change default behaviour of Classic Dashboards?
For example , if you didn't want to click on the side of the page and click the gear cog to clear your dashboard customization from a dashboard? - say you would rather have the user be able to do it in on the dashboard page directly via one click? is there a guide to what you can do with JS in OAS? what you may do/ and what you should not do? Apologies for the general nature of the enquiry, however, if someone has examples of functionality that has been added to Classic OAS Dashboards without effecting the native behaviour of the dashboard adversely i would be interested in hearing about it.
Thanks Tim
Best Answers
-
thanks @SteveF-Oracle I think its weighing up the pros and cons of doing HTML/Javascript as well as the technical know how to do this in OAS. Appreciate there are blogs out there for OBIEE and Javascript examples. One thing i found regarding collapsable section prompts in OAS dashboard (below) was the ones i tried which apparently is a zombie thread (who knew! :) …. but i couldn't find the 'var sectionid' in the OAS source code. You will appreciate it gets frustrating when you try out things which perhaps are not transferable from OBIEE to OAS?
0 -
Timothy,
Yes, a 4 year old thread which was abandoned by the OP is called a zombie thread in common forum parlance. It's a general rule to post your question into a new thread so you can manage incoming responses.
And with regards to your question: Your company built a whole custom GUI on top of OBI already and build a visual plugin pack. You should have examples over examples at your disposal.
It's absolutely possible but the devil's in the detail and it comes with many caveats attached as Steve mentioned.
2
Answers
-
Hi @Timothy Dickinson ,
Thanks for asking your question in the community. General questions are fine and you provided a necessary amount of context and detail (Thanks for that!).
I will speak generally here, adding HTML/Javasript is possible (and it is documented in the context of formatting). There are many OBIEE blogs (OAS'es precursor) with very creative uses for Javascript (even a framework for a new front-end to OBIEE). Having said that, adding a customization such as what you are proposing adds an additional layer of complexity, the need for JS skills, support and maintenance by the customer (not by Oracle), potential issues with upgraded and patching (i.e. you may have to re-work), potential browser/performance issues).
I will let other SMe's comment on the technical aspects and "How to's". You may want to start with an internet search (if you have not already) to see many of the OBIEE blogs, most should translate to OAS.
Other comments, most welcomed.1 -
You already got the answers you were after based on the marking of the thread.
Keeping it short: Oracle doesn't provide any piece of documentation about the JS part of "classic". There are tons of event handlers all over the page, and many of the menus and interactions are often events instead of direct links.
This means that if you want to provide a feature yourself in the page (like a clear customization button in the middle of the page) you will first need to study the code of the page and track the events fired so that you can replicate that (if you replicate the event it is often easier than just finding what function is called, because the even will always have the whole context required by it).
But nothing is documented because it wasn't expected for people to play with these things.
As for OBIEE to OAS compatibility, if it's 12c code it will probably work without many changes. There have been some changes in paths if you need to load some libraries, but the rest should be fine.
If you find 11g code, then you are good to rewrite most of it because 11g to 12c had lot of changes in the page structure and logic. While between 12c and OAS the "classic" pages are more or less the same. Some libraries updated, moved to a different path but I would say 95% the same.
But again, it's all on you: no documentation, no official support, you are in charge to discover how something work, reproduce it, not break the page, test after each patch or upgrade if it does still work. Try to be the less intrusive as possible to not break the page, that's also why firing events is often the most transparent way to do things: the page expects to work like that already.
3 -
Just one final thought.
You are more than welcome to file an Ideas Lab request (enhancement) describing your use case in detail. I highly doubt it will be implemented on the classic dashboard side, but it may be implemented within a Workbook (which you can also use to build "dashboards").2 -
@SteveF-Oracle @Gianni Ceresa thank you for your thoughts / input. Very Much Appreciated
1
