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 am building a WF8 Portal and have an intro tab with text, I am trying to use multiple fonts on this tab, but the tool is only allowing 1 found, 1 color, all bold or nothing bold, ect. Are there any work arounds to this?This message has been edited. Last edited by: <Kathryn Henning>,
Lynsi, the even more ridiculous aspect of inserting a BIP "Text" panel as an HTML textarea element is that the user can edit the text - type anything into the textarea. I cannot think of a single reason for letting the user do this.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
I'm with Francis. You'll learn that the tool layers provided by IBI have loads of nuances and bugs, and will tend to hinder more than help. The one thing that will ensure a great looking, working application and UX, if you can work through the tool layer's limitations and bugs, will be your ability to use HTML, CSS, Js, jQuery, etc. where possible. Now that IBI has decided to make it even harder by taking the HTML away from us, I have utilized -HTMLFORM and !IBI commands to work around HTML Composer. The BIP designer is very clunky as well. I hope things eventually turn course and get better for the developer down the road.