FOUR-26340 | ”about:blank” Displays From the Preview Pane of a Manual Task Using a List Table

[mcraeteisha]

Issue

Ticket: FOUR-26340

When a manual task used a display screen with a List Table configured for cases/requests, opening the task from the modeler preview and clicking the cases navigation control opened a blank about:blank page.

Root cause: preview set window.Processmaker metadata but not user, while form-requests.vue read Processmaker.user.username during mounted(). That threw before dataControls were emitted, so form-list-table.vue called window.open(undefined) → about:blank.

Solution

• Bootstraped the current user in the manual-task modeler preview shell (tasks.preview) so List Table / cases screens can resolve ProcessMaker.user / Processmaker.user.
• Hardened screen-builder List Table requests rendering: safely read user context, always emit dataControls with url: "/cases", and guard external-link opens when no URL is available.
• Added regression coverage for preview user bootstrap and List Table preview navigation behavior.

How To Test

• Run tests/Feature/TasksTest.php --filter testPreviewBootstrapsCurrentUserForListTable
• Run screen-builder FormListTablePreview.spec.js
• Create a process with a manual task and a display screen containing a List Table set to cases.
• From the modeler, open task preview and confirm the table renders without JS errors.
• Click the cases navigation control and confirm it opens /cases (not about:blank).
• Confirm the same screen still works in normal screen preview and standard runtime task pages.
• Confirm Start New Case / My Tasks / My Cases List Table behaviors remain intact.

ci:screen-builder:bugfix/FOUR-26340
ci:deploy

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.

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[nolanpro]

QA server K8S was successfully deployed https://ci-21cc12ffb8.engk8s.processmaker.net

[eiresendez]

Working as expected! 👍