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.
We're attempting to upgrade to 8.2.04, and I thought I'd see if anyone has any ideas on this challenge before I open a case.
We have a custom style sheet with an extension of .sty. We've been using it since 7.7, I think although it predates my time using WebFocus which is the past four years.
When we migrated the stylesheet.sty file to 8.2.04, we ran into a strange color issue. It affects all our files. Our custom color does not appear for Series 0. Anytime Series 0 is used we get a purple shade of sorts, similar to the purple used by the legacy home page in lower releases.
Here's what I can say definitively:
We use an INCLUDE statement to place the appropriate colors on all our graphs, tables, etc.
Series 0 has the correct RGB values (0-58-99) in the actual .sty file.
I changed the RGB values of Series 1 to those of Series 0. The color for Series 1 changed accordingly to the blue.
Based on the above, I ruled out the possibility of RGB values being converted incorrectly from 8.1.05 to 8.2.04. I also ruled it out because we use the same RGB values for that particular shade of blue in other parts of the portal and in tables where it renders correctly.
I tried to change Series 0 to another color altogether by inputting different RBG values. It did not change the color.
So, clearly Series 0 seems to be the issue.
To test another possibility, I omitted the "0" after Series. Nothing changed.
I reviewed the code further to determine if there is a duplicate line of code for setFillColor(getSeries(0),new Color(0,58,99)); There is not.
I spoke with our technical manager. She suggested opening a case, but like I said earlier, I just wanted to see if anyone had an idea before I opened a case later today.
Thanks in advance. The forum is always such a helpful community, and I've learned a lot all those who share solutions.This message has been edited. Last edited by: FP Mod Chuck,
Did you change your default stylesheet in App Studio to be your custom stylesheet? You can also set the default stylesheet for InfoAssist from the client administration console under the infoassist properties.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005
We have not tried that as of yet. I found the setting with ease, but might you point us in the direction of finding the stylesheet.sty file in the directory so it can be chosen and set as the default?
When I open the Change Stylesheet setting, it only opens the predefined templates. I need to use our stylesheet.sty file which we created. I need to find its stored location. I know its full name. I might add we have a case going right now because InfoAssist is not working for us.
Thank you, Chuck, for the filepath. I was able to place it there and changed the AdminConsole setting. It still did not solve the issue for us as we are working with InfoAssist functionality challenges, but it might help us in the future.