Hiding URL on mouseover on drilldowns in PDF (2nd Try)

Please help here. we are using ver 523
We want to hide the url and data passed when mouse over on drilldown in PDF reports. For HTML formats we can hide it by using javascript but what do we do for pdf reports?

I do not want to use global variables.

Any ideas...

Vipul

susannah

Expert

posted

Hide Post

if your html launch page form uses method=post, you'll get only the call to the wf cgi inthe status bar, not the parms nor the fexname
if your html launch page form uses method=get, you'll get the whole shebang in the status bar: fexname, parms, whole thing.
So maybe you can work with the method attribute of the cgi call in your drill downs, to at least hide the parms.

Posts: 3811 | Location: Manhattan | Registered: October 28, 2003

Ignored post by susannah posted

Show Post

slfmr

Platinum Member

posted

Hide Post

Susannah,

Is there any way to hide the Web Focus code when a use clicks view source through Web Focus?

I have removed the open and close carats.
-HTMLFORM BEGIN
html
head
title>My reportMETA HTTP-EQUIV="Cache-Control" CONTENT="no-cache"
META HTTP-EQUIV="Pragma" CONTENT="no-cache"
META HTTP-EQUIV="Expires" CONTENT="0"
head
body
!IBI.FIL.REPORT;
body
html
-HTMLFORM END
-EXIT

That is my HTML in a FEX following a report. When I click View Source, it shows me the HTML and then all the focus code even parameters that are passed to drill downs that should not be seen. Can I hide those parameters somehow or have the code hidden?

Dev, SIT, UAT, Production:7.6.6
Dev Sandbox:7.6.11

Dev Studio - 7.6.6

Posts: 178 | Registered: May 11, 2005

Ignored post by slfmr posted

Show Post

susannah

Expert

posted

Hide Post

sure, slfmr.
just make sure -SET &ECHO = OFF
and the fex code won't show when a user clicks ViewSource; with ECHO=ON, you see the fex code, but not the response status, like how many lines get extracted at each pass, etc.
When ECHO = ALL, you can view source the whole sheebang, which is useful when you're testing, and find stuff that goes wrong; but for production, you would always want ECHO=OFF, sends less stuff thru to the user's browser anyway, wee bit faster.