Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     JavaScript with Report Caster

Read-Only Read-Only Topic
Go
Search
Notify
Tools
JavaScript with Report Caster
 Login/Join
 
<Bandi>
posted
I am scheduling a Report in which I insert some details generated from the JavaScript code I have in the head section.

The JavaScript seems to be working fine when I run the Report seperately but when it is emailed through a schedule from Report Caster, the output which is generated from JavaScript is not seen on the Report.

Can anybody give me a clue why?

Thanks!
 
Report This Post
Expert
posted Hide Post
well, the simplest reason is that Outlook isn't a browser. and javascript is executed client-side, by the browser. Of course, bill gates will probably fix that! Big Grin
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
Expert
posted Hide Post
Babitha, Susannah,

Not all caster jobs use the instream HTML for viewing via Outlook or any other email Client but use the "Send as attachment" option which will use a web browser client for HTML attachments (if the target machine is set up that way of course!).

A lot of "problems" when using Report Caster are due to way RC actually runs the fex, in that it parses the code stripping out certain items.

Next time you run a fex with Javascript that works when run via a client or SSA, set &ECHO to ALL and compare the HTML source with that produced when run via Caster and you'll see what I mean.
 
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004Report This Post
Expert
posted Hide Post
Tony, Caster doesn't show the Echo. That's one thing we've been NFRing. We'ld like to have a way to save the echo to a file somewhere.
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
Expert
posted Hide Post
Susannah,

That's one difference that I meant! Altough, if I had mentioned that fact then many readers probably would have accepted it and not checked it! I had hoped people would try it for themselves (if they use Caster) and get used to checking outputs for debugging purposes.

You'll also notice that the usual Javascript entry is not present. Alledgedly it's due to security considerations according to Tony Li. Reasoning that I can appreciate even though I do not necessarily agree with it (entirely). I believe that the security implications should be left to the WebFOCUS installation.
 
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004Report This Post
<Joe Treliin>
posted
Thanks for the input and insights. They are truly appreciated. I was reading through this thread and thought I perhaps could add a couple of pieces of information.

&ECHO and -TYPE in logs will be supported in ReportCaster 5.3.

Also, as per my last conversation with development, ReportCaster doesn't strip out anything from a FEX. It actually might add a necessary command or two, as well as a few reserverd informational &variables (these are listed in the best practices guide), and then it hands the FEX off to the Reporting Server for processing. The only parsing it will do is to look for markers on burst reports.

There are, however, differences in the way ReportCaster will pre-process a job as opposed to MR. MR *will* parse and process a FEX prior to submission. This might be the discrepancy you are seeing and why it appears as if ReportCaster is 'parsing and removing certain items.'

Bottom line, JavaScript should work with ReportCaster and display properly if the report is rendered in a JavaScript friendly environment.


Joe Trelin
-Senior Product Manager, ReportCaster
 
Report This Post
<mhuber>
posted
While we're on the subject of things that don't work with Caster...

FOC_NONE doesn't seem to work. It's been a pet peeve, and we've had to use Dialogue Manager to work around the issue.

Hopefully this will be fixed in 5.3 also.

-Michael
 
Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     JavaScript with Report Caster

Copyright © 1996-2020 Information Builders