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'm attempting to generate some dynamic HTML from a WF request, with some elements hidden (using CSS), but, because of the extra TABLE tags, unneccesary blank space is appearing on the HTML page.
WebFOCUS create separate TABLE when HEADING is not aligned with data.
For example, this report generates separated TABLE:
TABLE FILE CAR HEADING "MY HEADING" BY CAR BY COUNTRY END
The following example, aligning heading columns with data (using HEADALIGN=BODY) and deactivating automatic pagination (SET PAGE=OFF/NOLEAD), don't create additional TABLE:
TABLE FILE CAR HEADING "MY HEADING" BY COUNTRY BY CAR ON TABLE SET PAGE NOLEAD ON TABLE SET STYLE * TYPE=REPORT, HEADALIGN=BODY, $ TYPE=HEADING, LINE=1, ITEM=1, COLSPAN=2, $ END
Regards, MikelThis message has been edited. Last edited by: <Mabel>,
Pietro-- You asked why the subhead is in a separate table; the reason is that we use that to allow the heading to span multiple columns. At the time we designed this, colspan wasn't supported on all browsers. You can manually control column spanning in v 4.3.x and higher.
There's also a technique that turns the separate table off, of course, but it's not intuitive. Setting ACCESSIBLE to 508 (for Section 508 compatibility) disables the creation of separate tables for headings. This was done so the headings would not be seen by screen reading software as separate from their data.