With a quick hack of a javascript function, we can easily find the source XML behind any OTM UI screen.
STEP 1: Navigate to the page before the page of interest
STEP 2: Open your browsers debugger
We can quickly see that the search button in the RIQ screen calls the javascript function find().
STEP 3 Find find
Find the find() function in the JS sources from your browser's debugger and copy all but the definition to your clipboard.
STEP 4: View in Debug!
In your browser's JS console (in the debugger), run the code in the function but with the following appended to the url String: +"&debug=y"
Like this:
Voila! Behold your source XML!
STEP 1: Navigate to the page before the page of interest
STEP 2: Open your browsers debugger
We can quickly see that the search button in the RIQ screen calls the javascript function find().
STEP 3 Find find
Find the find() function in the JS sources from your browser's debugger and copy all but the definition to your clipboard.
STEP 4: View in Debug!
In your browser's JS console (in the debugger), run the code in the function but with the following appended to the url String: +"&debug=y"
Like this:
Code:
if(document.management_main.findDropDown.value == 'rate'){
url ="glog.webserver.util.QueryResponseServlet?state=rateresults&cmd=query&srhType=rate&srcLocFil="+srcLocFil+"&destLocFil="+destLocFil+"&rateGroupFil="+rateGroupFil+"&fav_query_name="+fav_query_name+"&debug=y";
document.management_main.action=formatUrl(url);
}
else{
url ="glog.webserver.util.QueryResponseServlet?state=routeresults&cmd=query&srhType=rateRoute&srcLocFil="+srcLocFil+"&destLocFil="+destLocFil+"&rateGroupFil="+rateGroupFil+"&fav_query_name="+fav_query_name+"&debug=y";
document.management_main.action=formatUrl(url);
}
disableButtonByName('search', Searching);
document.management_main.submit();