Does anyone know where the following code is generated or controlled by

setRunWindowParams("")

i can see it in the source code for a BID public view?

I think this is where it's added to a BID window:

Drive:\ibi\WebFOCUS53\webapps\webfocus53\components\woas\report\WOAS_list.jsp

thanks.... it looks like it is exactly where I need to change the values...

again, thanks

Be careful! Make a backup! Also, depending on how the webapp was defined in the Web container app (IIS, Tomcat, etc.) you may need to recycle the Web container app for the change to be recognized.

we use AIX with WebSphere so I believe we have to "recycle"..



as to backing up, based on how I type, I always backup.



Thanks again.

Server was re-cycled but I do not see the changes when I view source!

any ideas?

OK, I don't know the correct terminolgy here. The app that's defined to the web container app - is it pointing to the app folder (C:\ibi\WebFOCUS53\webapps\webfocus53), or the web archive file (O:\ibi\WebFOCUS53\webapps\webfocus53.war)?

If it's pointing to the web archive file, the file needs to be recreated, or you can change the web app definition to point to the app folder.

We point to the web folder...

Our WebSphere techies do the recycle.

Well, I'm flummoxed. dhagen may be able to help.

perhaps there's a cache in WebSpehere that needs emptying...

in retrospect, i really didn't describe where i was trying to get this to work correctly.. My apologies.

when you create an output window as a "LINK"... this is were I want to control the popup.

does this make a difference?

John, what behaviour are you trying to modify?

one of the options that you have for content are "links". you can list multiple fexs that a user can launch.

these links are what i want to control.

Yes, John, but what is it you want to control in the links?

when a user clicks on a report link, they get a full access window, I wish to limit the window the report opens in. actually any report that is executed after a user gets a screen (drill downs, URLs, etc.) i would like to control so that there is never a location/address, toolbar or menubar.

John, you *may* be able to do this by altering some JavaScript instead of the JSP files.

I created a block with some Liks in a BID view. This is the trail I've followed so far:

Click a Link hyperlink.

Function showPopupNoTree in file C:\ibi\WebFOCUS53\ibi_html\javaassist\worp\js\menu\worp_menu-adapter.js is triggered.

Function showPopupNoTree calls function showMenu in file C:\ibi\WebFOCUS53\ibi_html\javaassist\worp\js\menu\worp_menu.js.

The line eval(onClickEvent); in function showMenu calls openLink in file C:\ibi\WebFOCUS53\ibi_html\javaassist\worp\js\util\worp_runtime.js.

Some code in function showMenu actually opens the window, I haven't figured out that part yet.

I hope this gets you a little closer to achieving what you require.

Good Night, and Good Luck.

Function openLink calls function run_it, and it is this function that opens the new window.

At the top of file worp_runtime.js, variable runWindowParams is declared with a blank value. I modified that blank value to 'location=no,menubar=no,toolbar=no,status=no,resizable=yes,scrollbars=no'.

For some reason I cannot understand (the JS is quite convoluted), the value of runWindowParams is blank when it is used in the window.open commands. So I just replaced the 'window features' part of the window.open: wherever there is a window.open, replace the third argument with 'location=no,menubar=no,toolbar=no,status=no,resizable=yes,scrollbars=no'.

For instance, where you see
window.open(run_url, something, winParms); replace winParms with the above code.
Where you see window.open(run_url, something, this.getRunWindowParams()); replace this.getRunWindowParams() with the above code.

BE CAREFUL! These functions are used to open all kinds of windows, you will have to find the window.open lines that deal with links in views. The one for a URL is in function openNewWindow.

Does it have to be so complicated?

yes... it has to be this hard, otherwise, i would not have had the opportunity to find a knowledgable resource like you. I can't begin to tell you how thankful i am for your assistance.

if you are ever near Trenton, NJ let me know and maybe we can have lunch or something.

We struggle with the javascript quite a bit in our installation, especially in debugging browser behavior differences between IE and Firefox.

Resources that have been suggested by IBI tech support wizards for debugging javascript code are

Internet Explorer - DebugBar and CompanionJS
http://www.debugbar.com

http://www.my-debugbar.com/wiki/CompanionJS/HomePage


Firefox - Firebug extension
http://www.getfirebug.com

I've used Firebug with Firefox. It is an incredible tool allowing breakpoints, step-through tracing, examining variables and properties, changing them on the fly, and handles JS, CSS, DOM, etc -- my personal favorite.

Be advised if you use Firefox to debug WF javascript, it won't help a lot for IE debugging, as the DOMs are different (got to love Microsoft's "independence" in using W3C standards), so the JS code has different code paths for IE.

But I agree, the code is complex and convoluted. Tracing down problems or trying to apply custom mods are always a challenge for us.

Regards,

-- Dan
University of Nebraska at Omaha
WF 7.1.6 Linux -- Test: WF 7.6.1 Linux

This message has been edited. Last edited by: Dan Kenny,

this worked......

I believe making the changes in function openNewWindow(run_url)

was the one that made it work.

Again, my Thanks.

John, I'm glad it worked out! I learnt something too. I pormise to contact you if I'm ever in Trenton.

Cheers.