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 created a Business View and then created a Business Rule on the reporting console in resource management tab and applied it to the master. I wanted to force the user to use at least one "Where" statement on one of 5 fields contained in the master for filtering. This worked great running from Dev Studio, but Info Assist seems to ignore the business rule and lets the report run wide open. Does anyone have an idea or solution to this issue? Thanks MattThis message has been edited. Last edited by: <Emily McAllister>,
This has been resolved. We need to add the AD Group to the Access Control tab on the reporting console. Once we created a role and registered the AD Group, the business rule worked. Thanks