[Solved] Forcing a Dedicated Last Page for Long Text and Hiding Page Headers/Footers

[Marcel]

Dear Telerik Support Team,

I am reaching out to request technical assistance regarding the implementation of a "Terms and Conditions" section that should function as a completely independent additional page at the end of my report.

Current Report Structure: My main report includes Page Header, Detail, and Page Footer (containing total calculations) sections.

Current Configuration (Attempted without success): To force the legal text into an independent final page, I have configured the following:

• Section used: ReportFooterSection to contain the legal text.
• PageBreak Property: Set to Before.
• Text Component: HtmlTextBox with CanGrow set to True.
• KeepTogether Property: I have tested both True and False settings.

Persistent Issues: Despite these settings, the text is not being isolated correctly:

• Section Merging: The long text starts rendering immediately after the Details section on the main page, ignoring the page break or fragmenting erratically.
• Page Footer Conflict: The Page Footer elements (invoice totals and page numbers) from the main invoice continue to print on the pages where the legal text appears, causing visual overlaps.

Questions for the Support Team:

1. What is the cleanest way to add this final page? Given the standard report flow, how can I insert this block so it "breaks" the flow and takes over a full page without inheriting the layout (Header/Footer) of the previous pages?
2. Conditional Visibility Control: How do you recommend hiding the Page Header and Page Footer specifically on these final "Terms" pages?
3. Report Architecture: For text that spans one or more full pages, is it better to continue using the ReportFooterSection, or would you recommend using a SubReport or a Group Footer without a grouping expression?

Special Request: I have attached my report definition file (.trdp). Could you please review my current structure and modify the attached report using the most robust configuration to solve this behavior?

[Dimitar]

Hi Marcel,

Thank you for the attached report and the additional information!

Let me start by mentioning that the attached report uses JSON files for its data that I cannot access. Considering this, I will be making my comments and suggestions based on the report design and how the report previews locally without data.

With that being said, when I previewed the report without data, the first thing I noticed was that the page break set on the Report Footer section seems to be applied. I have colored the sections to be able to more easily distinguish them:

Before making any suggestions, I will try to answer your questions, asked at the end.

What is the cleanest way to add this final page? Given the standard report flow, how can I insert this block so it "breaks" the flow and takes over a full page without inheriting the layout (Header/Footer) of the previous pages?

The cleanest way is usually the approach that you already seem to have tried with the Report Footer section, since that section is rendered only once at the end.

The PageBreak property should allow for the section to start at a new page, and it seems to do so locally, while the PrintOnLastPage property of the page footer should allow it to be hidden on the last page of the document, which also seems to work in my local testing.

The problem here is that the "Terms" text is large and cannot fit on a single page. So the first page with the "Terms" text contains the page footer, while the second does not, which fulfills the requirement only halfway.

Conditional Visibility Control: How do you recommend hiding the Page Header and Page Footer specifically on these final "Terms" pages?

The visibility of those sections can be controlled dynamically via a binding on the Visible property. The problem is creating an expression that would reliably hide the section on the correct pages.

There is no way to check via an expression whether "htmlTextBox3"(the item with the terms) is currently on the page, and thus hide the page footer.

We can check the current page number and hide based on that, but unless your data always produces the same number of pages, this approach would be incredibly unreliable.-

Report Architecture: For text that spans one or more full pages, is it better to continue using the ReportFooterSection, or would you recommend using a SubReport or a Group Footer without a grouping expression?

If the text will always be of a size that can fit on a single page, the Report Footer section approach is the one that I would use, alongside hiding the page footer at the last page via the PrintOnLastPage property.

But if the text is too large to fit on a single page, as it seems to be the case here, and hiding the page footer on the last page is part of the requirement, the mentioned alternatives with the subreport and group section won't work either.

Suggestion for multi-page "Terms" text - Report Book

For "Terms" text that is too large, you can create a separate report only with the "Terms" text, and you can put it together with the first report in a report book - Telerik Reporting Report Book Overview - Telerik Reporting.

This will allow for the "Terms" text to start on a new blank page, leaving enough space to possibly fit the text on a single page, since the page header and footer sections of the first report won't be there to occupy space.

I have attached a zip with such an example to my reply. Please take a look at it and let me know if you have any additional questions.

Regards,
Dimitar
Progress Telerik

[IntegraTools]

Thanks for you answer Dimitar. It is very useful