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.
Run a small Active HTML report and view the source. You may be surprised by how much JavaScript there is. IE needs to digest this JavaScript before rendering the page.
The warning pop-up gives the user a chance to stop rendering if it's taking too long. Some pages my trigger the pop-up more than once.
To prevent this pop-up, you can modify the registry:
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles\MaxScriptStatements set to 0x04c4b400
This value increases the number of Javascript statements that is allowed to execute before the warning pops up. To completely avoid the dialog try 0xFFFFFFFF.
I was afraid of that. Is there any way to improve the performance of larger AHTML reports? They are a fantastic way of presenting data except their performance puts users off.