Skip to content

fix(FOUR-33538): resolve FormInput at runtime in PDF inspector - #9078

Merged
nolanpro merged 1 commit into
developfrom
bugfix/FOUR-33538
Sep 28, 2026
Merged

nolanpro merged 1 commit into
developfrom
bugfix/FOUR-33538

Conversation

@rodriquelca

@rodriquelca rodriquelca commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

Issue & Reproduction Steps

After the modeler Vite migration, the PDF Generator inspector does not render PDF File Name — only a small empty box appears. Name and Screen select still work.

Reproduce: Modeler → add PDF Generator → open Configuration → PDF File Name is missing.

Cause: window.VueFormElements exposed only the plugin ({ install }), not FormInput. The connector bundle needs window.VueFormElements.FormInput.

Solution

  • processmaker: Load shared vueFormElements.js / modelerInspector.js in globals.js and loaderModeler.js so FormInput is on the global before connector scripts run.
  • connector-pdf-print: Resolve FormInput in beforeCreate() from window.VueFormElements instead of importing at bundle load time. Rebuild pdf-connector.js.
image

How to Test

npm run dev + publish connector assets.
Modeler → PDF Generator → confirm PDF File Name shows (label, input, helper).
Set a file name and screen, save, reload — values persist.
Console: window.VueFormElements?.FormInput should not be undefined.

Related Tickets & Packages

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.

@cursor

cursor Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

PR Summary

Medium Risk
Touches modeler entry/bootstrap and global APIs (window.VueFormElements, inspector globals) that packages like the PDF connector rely on at runtime.

Overview
Fixes the PDF Generator inspector missing PDF File Name after the modeler Vite migration by ensuring window.VueFormElements (including FormInput) is set up before connector bundles run.

globals.js and loaderModeler.js now side-import next/libraries/vueFormElements and next/libraries/modelerInspector instead of wiring window.VueFormElements / window.ModelerInspector inline or only importing the vue-form-elements package in globals. loaderModeler.js also registers the vue-form-elements plugin with Vue.use(VueFormElementsPlugin.default ?? VueFormElementsPlugin) so the correct default export is used under the new bundler.

Reviewed by Cursor Bugbot for commit 35ef3f9. Bugbot is set up for automated code reviews on this repo. Configure here.

@decisions-sonarqube

Copy link
Copy Markdown

Quality Gate passed 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

@nolanpro
nolanpro merged commit 5be26a3 into develop Sep 28, 2026
14 of 24 checks passed
@nolanpro
nolanpro deleted the bugfix/FOUR-33538 branch September 28, 2026 21:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants