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.
Would someone please be so kind as to direct me to some documenetation which explains the "Sizing Requirement Height" within compound reports, as shown in this image:
I cannot seem to find it here or in F1 help...
Thanks...This message has been edited. Last edited by: Doug,
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
I found this in Creating Compound Reports with Document Composer 77.pdf Is this what you're looking for ???
-Fred
Reference: Rules for Setting Relationships Between Objects
The following rules apply when setting relationships between objects:
Setting relationships (relate top left to bottom left)
This sets a relative distance between the flowing report and a surrounding object. The
surrounding object is rendered immediately following the end of a flowing report with the
related distance between the end of the flowing report and the beginning of the
surrounding object.
Fixed objects
A fixed object cannot be broken across a page break, it needs enough vertical space
to fit on the last page of the flowing report.
If the surrounding object is fixed in size, such as a graph or a fixed report, then you
must set the Sizing Requirement property to ensure that there is enough space to
display the object. If not, the object is automatically rendered at the top flow margin
of the next page.
Flowing object (reports)
A flowing report can be broken across pages. The reporting server determines if
there is enough room to begin rendering the surrounding flowing report.
You can optionally set the sizing requirement for a report that is relatively positioned to ensure that the report is not broken at the wrong spot.
For example, to ensure
that the heading appears with information below it.
Note: The sizing requirement is only applicable to a report that is relatively positioned
to another flowing report. It does not apply to any other object.
Draw object
Relationships do not apply to draw objects such as images, lines, and text. Draw
objects (not repeating objects in the Page Master) can be placed above flowing
reports in a page layout, but draw objects placed below a flowing report (not repeating
objects in the Page Master) should be placed outside of the bottom flow margin.
Setting a relationship between a report and a graph
If the overflow property of the report is set to flowing and there is no set relationship
between the graph and report, then the report will overlap and display on top of the graph
at run time. There is no way for the Document Composer to automatically set
relationships, so you must set the relationship between the report and the graph.
Note: A surrounding object can only be related to one flowing report. However, a flowing
report can have multiple surrounding objects related to it. The surrounding object is that
which is related to the primary object.