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.
I have a report that outputs to HTML with drilldowns to more detailed reports, all of this works fine.
When I change the output to EXL2K, the drilldowns also work fine no matter if I chose to "Save" the .xls or to "Open" the .xls in browser.
However, when I schedule the report to go in EXL2K in Reportcaster, the hyperlinks change to reference file://c:\ rather than http://.
Note, I have checked my folder options in windows and Browse in current window is selected for xls files (as mentioned in other threads on focal point).
Any ideas?This message has been edited. Last edited by: Kerry,
Prod: Single Windows 2008 Server running Webfocus 7.7.03 Reporting server Web server IIS6/Tomcat, AS400 DB2 database.
When we played with the focexurl, we added this to the top of the .fex SET FOCEXURL = 'http://svr99wfrs/ibi_apps/WFServlet?'
And our drilldowns look like this... TYPE=DATA, COLUMN=N41, FOCEXEC=ar_opentickets.fex(CUST_NUM=ACCT), $ TYPE=DATA, COLUMN=N42, FOCEXEC=ar_opentickets(CUST_NUM=ACCT), $ TYPE=DATA, COLUMN=N31, FOCEXEC=app/ar_FinanceChgDue(CUST_NUM=ACCT), $
All of the drilldowns give us an error of "Can't find Fex"... as you can see we took the app/ off one drilldonw, the .fex and app/ off the next and left another the same. All of them give the same error.
Prod: Single Windows 2008 Server running Webfocus 7.7.03 Reporting server Web server IIS6/Tomcat, AS400 DB2 database.
After taking the drilldown fexes out of MR and putting them in the EDASERVE, adding the FOCEXURL and dumping the App/ from stylesheet code in the master .fex, it all seems to be working now.
Prod: Single Windows 2008 Server running Webfocus 7.7.03 Reporting server Web server IIS6/Tomcat, AS400 DB2 database.
You solved the problem of making them work, but you must realize that because you have added these procedures to your EDAPATH, these procedures are now available to anyone who has access to the server with that same edapath setting. If those procedures produce reports with any sort of sensitive information, you need a more secure approach. There are many examples on the forum if you search drill-down, Exl2k, ReportCaster, etc.This message has been edited. Last edited by: Darin Lee,
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
At minimum, you should be able to leave them inside of MRE and use the IBIMR_drill='RUNNID' which would limit access to the drill report to those who can access the top-level report.
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
If your drilldown fexes are in mre and your host is in mre, you should have no problem whatsoever. the links should contain the mre domain name. and the edapath is not an issue. humor me... write the fex with an HTML output and an HTML drilldown. Keep the FOCEXURL statement in the fex when the output shows up, right click, view source, and look for the http:\\SERVERNAME\..etc of one of the drilldowns. Copy it, and paste it here. (within CODE tags, of course)
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003