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 need some advice. I have been tasked with taking 60 plus SQL reports contained in a DB and converting them into WebFocus. All reports have parameters that are different between each one. I'm not sure what is the best way to approach this task. Should I make a HTML page with tons of parameter elements that passes the data to a .fex? Is there a portal approach that would work better than the HTML approach. Thank you in advance for any advice.
Daniel
In Focus since 2012 WebFOCUS 8.0.07 Windows, All Outputs
Daniel, You could create a Launch page for all the reports. When a user selects report to run, you can then display another Launch page that prompts for the Report-specific parameters
WF 7.6.11 Oracle WebSphere Windows NT-5.2 x86 32bit
Or you can have only one page with everything and play with controls hide/show depending on the selected report.
You'll have less pages to develop, but the one will be more complex.
I suggest first to do the full inventory of all parameters and have the list of the ones that are globally used; it will show you the path to follow.
IMHO, if most of the parameters are globally used and only some are specific, I think that it's better to centralized on one page. This way you'll avoid duplicating the same controls/parameters/validation across multiple pages. And in the future, less maintenance...
But either approach is good.
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
Sounds like you have a big task ahead of you. I agree with RSquared, it sounds like what you need is to create a launch page for running each report. With 60 reports, thats a lot to convert over. Along with RSquared's suggestion, I would suggest to look for commonalities between the reports. Group all of the similar reports together. Small variations in the selection criteria for each report lends itself well to optional filters. If your output varies greatly, its going to be better to do those individually.
Creating 1 mega report page is probably not the way you want to go (again, I have no idea whether these are 60 reports of the same thing or 60 wildly different reports). The amount of "If this is selected do that, or do this when x" logic you would probably have to put into it, may not be worth the time it takes to write it.
Eric Woerle 8.1.05M Gen 913- Reporting Server Unix 8.1.05 Client Unix Oracle 11.2.0.2
Posts: 750 | Location: Warrenville, IL | Registered: January 08, 2013
The reports are sql statements in a db that require parameters. So I first envisioned a sql pass through when the user selects a report and entered the parameters. All the reports run for different data. Some use the same parameters as other reports some use totally different ones. I am still new to WebFocus could you guys explain what exactly is the launch page?
In Focus since 2012 WebFOCUS 8.0.07 Windows, All Outputs
When looking at the reports I might also look to see if they could be grouped by end users. Sixty reports split over three or four departments could make a single launch page for each department / report type less confusing.
WebFOCUS 8.0.05 Windows- Excel, PDF
Posts: 21 | Location: Crystal City, VA & Kalamazoo, MI | Registered: October 11, 2010
Yes the reports are grouped by departments so that will make dividing up the reports easier. Now I am trying to figure out App Studio and how to make an HTML page that follows these steps:
1. user selects a report 2. user clicks on a "Next" button 3. user enters parameters on the parameter page 4. user click the run report button.
In Focus since 2012 WebFOCUS 8.0.07 Windows, All Outputs
Daniel, I am not sure about App Studio, but in Dev Studio I would create the report, publish it to create a Launch Page and then add it to the main Launch Page. All the 'Parameters' are on the individual Launch Pages.
WF 7.6.11 Oracle WebSphere Windows NT-5.2 x86 32bit