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.
The Product Division has reviewed as follows: The requested behavior would require a major reworking of core border code therefore we can not accept this as a new feature request.
Case closed.This message has been edited. Last edited by: Francis Mariani,
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
When HTMLCSS is set to ON, a line is generated when there is no HEADING because of a WHEN statement. Also, why is an extra row of blank data generated at the bottom of the report when BORDER is set to 1?
If the WHEN causes no heading line, a line is displayed, which I think is an empty table cell with a border.
The blank line at the bottom of the report is comprised of a table row with empty cells (you have to drag your cursor over the report with the mouse button pressed down to select).
This is extremely annoying when trying to build precise dashboards with multiple reports in iframes. This appears to happen when HTMLCSS is set to ON and BORDERS are used, which seems quite arbitrary.
WebFOCUS code:
TABLE FILE CAR
SUM
SALES
COMPUTE DOWK/A3 = DOWK(&YYMD,'A3');
BY COUNTRY
HEADING
"REPORT HEADING"
WHEN DOWK NE 'WED'
ON TABLE SET PAGE NOLEAD
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLE *
TYPE=REPORT, SQUEEZE=ON, FONT='ARIAL', SIZE=9, BORDER=1, BORDER-COLOR=SILVER, $
ENDSTYLE
END
Updated code:
TABLE FILE CAR
SUM
SALES
BY COUNTRY
HEADING
"REPORT HEADING"
WHEN COUNTRY EQ 'INDIA'
ON TABLE SET PAGE NOLEAD
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLE *
TYPE=REPORT, SQUEEZE=ON, FONT='ARIAL', SIZE=9, $
TYPE=DATA, BORDER=1, BORDER-COLOR=SILVER, $
TYPE=TITLE, STYLE=BOLD, BORDER=1, BORDER-COLOR=SILVER, $
TYPE=HEADING, BORDER=1, BORDER-COLOR=SILVER,
-****
-***** below is the line to make the BORDER styling conditional
-*****
WHEN=COUNTRY EQ 'INDIA' ,
$
ENDSTYLE
END
quote:
I have been informed that this is not a bug but is expected behavior. There is no way to remove these lines. Per Product Management, Bordered HTML reports have always presented with these blank lines between the heading / footing and body nodes in border mode.
Any mention of border styling in the Stylesheet will cause this behavior. Additionally HTMLCSS is required for borders to present so the behavior of any borders or associated blank lines will correspond to the presence of this syntax.
When a HEADING is conditionally displayed or not displayed the blank line that would normally appear between the HEADING and the body of the report are not conditionally removed.
I have requested that this be documented but can also submit a NFR on your behalf to have the blank line conditionally display.
Please let me know if you would like me to submit the new feature request and if there are any further questions on the above information.
I will place the case into customer testing and await your update.
For the second issue, this is a long standing Core FOCUS issue. The long standing solution is to use a SUBFOOT or SUBHEAD, if you prefer, with subtotals. This should not occur with FORMAT HTML but would occur for FORMAT PDF.
quote:
Thanks for the update. Just because it is "expected behavior" doesn't mean it's not a bug. Yes, please request a NFR for this. This issue had been mentioned many times on FocalPoint and there are quite a few people that would like this fixed. Another example of "expected behavior" that is extremely annoying is the TOTAL line split into two because there's a BY XYZ NOPRINT - now I'm sure that there is no WebFOCUS developer that wants that to happen and yet it's been there since the beginning of FOCUS.
For the second problem - yes, it shouldn't happen, but it does, and that is where the frustration is.
quote:
Thank you for bringing this problem to our attention. We have reviewed it with our engineering staff and it has been determined that it will not be implemented in the WebFOCUS product. Therefore, we will close the case. If this decision substantially impacts your business, please discuss with your local account support team.
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