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 multiple graphs on my page, and whenever I move my mouse over any of the graphs, it gives the message "Click to activate and use this control"
Once I click on the same, the dotted line vanishes and I can now use the graph (all links and all)...
Can anyone please tell me what needs to be done, so that this message does not appear at all, and thegraph is completely ready for use as is comes into the page?
Yes, its true that it is just about a click (or pressing the spacebar), but the problem would come up if you have too many graphs (say a dashboard sort of thing).
For exaplme I have designed a page where, when I take my mouse over a gauge graph, I show a different 3D Cylinder graph.
In this case, the screen flickers every time I move the mouse over the gauge graphs.
Once I go and click on every graph I have generated in the page, thereby activating the same, this problem ceases to exist. That is why I am desperately looking for it.
In any case, I have found out how this needs to be done. Seems like there is not much we can do about it from our side. We need to open a case with the Customer Support, and then they would provide a patch for the corresponding release. This would take care of the problem.