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’m working to put together a report requirements specification document that our business analysts will use to document the requirements for a report that the development team will then build. We need to have the analysts do a better job of collecting specification information such as # of drill down reports (some analysts view 1 report with 5 drills downs as 1 report and we don’t uncover that until later in development/testing, which throws off the estimate versus actual development time). Does anyone have such a template/process and could you share with me?
Thanks!
Gene Gauthier Business Intelligence Team Lead World Wide TechnologyThis message has been edited. Last edited by: Kathleen Butler,