defect/FOUR-25983: [47027] Ellucian - Printed Form cuts fields after PDF Preview when it starts at top of a new page

[CarliPinell]

Issue & Reproduction Steps

Current Behavior:

• In the print preview, the fields located after the PDF Preview are partially or completely cut off.
• The issue occurs consistently when the Loop Control count is set to multiples of 32 (e.g., 32, 64, 96, 100).
• For values starting around 25 up to 34, the issue also occurs, (some fields are slightly cropped).
• At other values (e.g., 50), the behavior is normal because the File Preview starts in the middle of a page, not at the very beginning of a new page.
• The bug seems tied to how page breaks are handled when the File Preview starts at the top of a page.

Solution

All fields after the File Preview are now fully visible in the print output, regardless of the controls used before it or the page where the File Preview begins.

Page not crop or hide fields.

How to Test

Process file Is attached in the ticket

Create a new process with 2 tasks:

Task 1: Upload a PDF (or any file).
Task 2: Design a form with the following structure:
Add a Loop Control and inside it insert a Rich Text control with some placeholder content (e.g.,

-----

).
After the loop, insert a File Preview control linked to the uploaded file.
Add several additional fields below the PDF Preview (screenshot as reference)

In the Loop Control, set the Default Loop Count to 32.
Run the process:
Complete Task 1 by uploading a PDF.
Continue to Task 2 and complete it, then go to the FORMS option for the request and open the last form
Use the Print Form option to generate the print preview.

Related Tickets & Packages

https://processmaker.atlassian.net/browse/FOUR-25983

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

ci:deploy

[CarliPinell]

Some Tests were performed with 25,32 and 64 iterations for loop (They All work well)

Screen.Recording.2025-10-14.at.8.38.01.AM.mov

Screen.Recording.2025-10-14.at.8.30.14.AM.mov

Screen.Recording.2025-10-14.at.8.35.52.AM.mov

[eiresendez]

👍 👍 👍

[vladyrichter]

QA server K8S was successfully deployed https://ci-09d178dd0e.engk8s.processmaker.net

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube