FOUR-33485: Launch Screen is not updated on processes page

[henryjonathanquispe]

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-33485

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

[cursor]

PR Summary

Low Risk
Change is limited to the processes catalogue JS entry point and aligns bootstrap with the Screen Builder package; main caveat is skipping screenBuilderNext cache/script setup if that page relied on it.

Overview
Fixes FOUR-33485 by changing how Screen Builder is bootstrapped on the processes catalogue entry (loaderProcessesCatalogue.js).

The loader no longer calls the local screenBuilderNext() wrapper. It now imports @processmaker/screen-builder (and vue-form-builder.css) and registers the plugin with window.Vue.use(ScreenBuilder.default) after setupMain(), so launch screens on the processes page pick up the packaged builder instead of staying on the deferred/async registration path.

^{Reviewed by Cursor Bugbot for commit 498bbcc. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 96a557d. Configure here.}

[vladyrichter]

QA server K8S was successfully deployed https://tenant-1.ci-6f7c86008b.engk8s.processmaker.net

[vladyrichter]

QA server K8S was successfully deployed https://tenant-1.ci-6f7c86008b.engk8s.processmaker.net

[decisions-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

[vladyrichter]

QA server K8S was successfully deployed https://tenant-1.ci-6f7c86008b.engk8s.processmaker.net