An awesome collection (not curation) of helpful Siebel OpenUI API Methods to help you debug your OpenUI application.
NB: Siebel may or may not be awesome.
Clicking on a component/list/applet and running the below JS will return the View Name, which you can then lookup in π οΈ Siebel Tools
SiebelApp.S_App.GetActiveView().GetName()
SiebelAppFacade.ComponentMgr.DisplayTree()
Will return a Node tree, for example:
VM712:1 Proxy Node -> o
VM712:1 Proxy Node -> et
VM712:1 Proxy Node -> p
VM712:1 Component Node -> Left Pane Menu Items Applet
VM712:1 Component Node -> Manage Practice Standards Outcome Form Applet
VM712:1 Component Node -> Practice Standards Outcome List Applet
VM712:1 Component Node -> Left Pane Details Form Applet
VM712:1 Component Node -> Portal Practice Standards Header List Applet
VM712:1 Component Node -> Practice Standards Outcome Export List Applet
VM712:1 Component Node -> Application Playbar Applet
VM712:1 Component Node -> Practice Standards Header Export List Applet
VM712:1 Component Node -> Site Container Page
VM712:1 Component Node -> Pages Standalone Applet
VM712:1 Component Node -> Portal Application Practice Standards List View
SiebelApp.S_App.GetActiveView().GetAppletMap()
SiebelAppFacade.ComponentMgr.FindComponent(/*SiebelApp.S_App.GetActiveView().GetName()*/)
SiebelAppFacade.ComponentMgr.FindComponent(/*SiebelApp.S_App.GetActiveView().GetName()*/).GetPM()
SiebelAppFacade.ComponentMgr.FindComponent(/*SiebelApp.S_App.GetActiveView().GetName()*/).GetPR().constructor
Depending on your version of OpenUI, you may encounter several WCAG defects. Hopefully these snippets help you zero-in on those defects:
$(function() {
$('[id]').each(function() {
var ids = $('[id="' + this.id + '"]');
if (ids.length > 1 && ids[0] == this)
console.warn('Multiple IDs #' + this.id);
});
})