FOUR-22083: Preserve data object select values on refresh

[eiresendez]

Issue & Reproduction Steps

FOUR-22083 fixes data loss in a dependent Select List after refreshing a task screen.

To reproduce:

1. Configure a screen with one Select List populated by a data connector.
2. Configure a second multi-select Select List populated from a request data object, such as albumData.
3. Add a watcher on the first Select List that runs on screen load and maps the data connector response into albumData.
4. Start a task, select values in both fields, wait for autosave, then refresh the task page.

Before this fix, the draft still contained the selected values for the dependent Select List, but the component cleared them during initial render because albumData had not been repopulated yet.

Solution

• Preserve existing Select List values while dataObject options are still pending.
• Avoid emitting a reset when a dependent dataObject Select List has a draft value but its option source is still null or undefined.
• Keep the existing reset behavior once options are available and the selected value is truly invalid.
• Add unit coverage for pending data object options, resolving preserved values after options load, and resetting invalid values after options are available.

How to Test

• npm run build
• Manual verification in ProcessMaker:
  1. Build vue-form-elements.
  2. Copy the built dist into the core app's node_modules/@processmaker/vue-form-elements/dist.
  3. Run the core frontend build.
  4. Open the reproduced task screen.
  5. Select values in both dropdowns and wait for autosave.
  6. Refresh the task page.
  7. Confirm the watcher runs on load and the dependent Select List keeps the saved chips.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-22083
• Package: @processmaker/vue-form-elements

ci:deploy

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[eiresendez]

Just a heads up: the PR checks are currently blocked by the CI deploy server, not by the package build or tests. So please check this change locally for now.

[eiresendez]

@CarliPinell @mcraeteisha QA server for testing here:

• https://ci-ac93d439bf.engk8s.processmaker.net