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 have text that is rotated vertically using the following define: PROGRAM_AREA_DESC_FLIP/A70 = '
' | PROGRAM_AREA_DESC | '
';
This has been working in 7.6 -- In our test environment in 7.7 the define itself is printing and not the values in rotated form. Does anyone have a suggestion how to do this in HTML? I have tried to put rotate in a cascading style sheet, calling in the style sheet and then adding CLASS=rotate and that did not seem to work.
Thanks,This message has been edited. Last edited by: Vivian,
Vivian Perlmutter Aviter, Inc.
WebFOCUS Keysheet Rel. 8.0.2 (Almost) 1001 Ways to Work with Dates thru Rel. 8.0.2 Focus since 1982 WebFOCUS since the beginning Vivian@aviter.com
TABLE FILE CAR
SUM
COMPUTE PROGRAM_AREA_DESC_FLIP/A100 = '<div STYLE="writing-mode: tb-rl;filter: flipv fliph;">' | MODEL | '</DIV>';
BY COUNTRY
ACROSS CAR
END
I am going to pass this to the testing team. I myself do not have access to test -- the server version is 7.7.04 -- I wonder if that is making a difference. Will keep you posted and thanks.
Vivian Perlmutter Aviter, Inc.
WebFOCUS Keysheet Rel. 8.0.2 (Almost) 1001 Ways to Work with Dates thru Rel. 8.0.2 Focus since 1982 WebFOCUS since the beginning Vivian@aviter.com
I pass your info on to the test team -- I am just wondering if it is the EXACT combination of 7.7.04 - IE9 and Windows 7 ---
Hopefully they will be able to view the source code and see what the problem is -- In the mean time, if someone in the IBI community has access to the exact combination of WebFOCUS and Windows and IE and could run the simple car file test, that would be great ---
Thanks Vivian
Vivian Perlmutter Aviter, Inc.
WebFOCUS Keysheet Rel. 8.0.2 (Almost) 1001 Ways to Work with Dates thru Rel. 8.0.2 Focus since 1982 WebFOCUS since the beginning Vivian@aviter.com
I just checked with the testers - This is our exact combination:
Windows 7 IE 9 WF Client - 7.7.094 WF Dev Studio 7.7.03
We really need this to work -- We have it in several programs .... so it looks like it needs to be tested on that exact combination -- In the maean time, we are doing a view source to try to identify the problem.
Vivian Perlmutter Aviter, Inc.
WebFOCUS Keysheet Rel. 8.0.2 (Almost) 1001 Ways to Work with Dates thru Rel. 8.0.2 Focus since 1982 WebFOCUS since the beginning Vivian@aviter.com
Yep - that was the culprit! Our administrator had it set in edasprof to on -- we turned it off in the program and now it is fat and happy.
SET HTMLENCODE=ON to encode the HTML output that is data.
This setting will disable the rendering of HTML tags within a browser when these tags are stored within the actual data, or created using a DEFINE or COMPUTE command. ThanksThis message has been edited. Last edited by: Vivian,
Vivian Perlmutter Aviter, Inc.
WebFOCUS Keysheet Rel. 8.0.2 (Almost) 1001 Ways to Work with Dates thru Rel. 8.0.2 Focus since 1982 WebFOCUS since the beginning Vivian@aviter.com
Your administrator may have added this setting at the reporting server level because of a security requirement. Having the setting on makes your html reports less vulnerable to cross site scripting. I would let him know that you are overwriting the setting at the report level.