You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
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