Bugfix/FOUR-32292-b: Validation of required fields does not work correctly in Record List controls with checkboxes

[CarliPinell]

Solution

Problems addressed

• Required Record Form fields were not validated correctly on parent Submit (values live in list rows, not at root).
• Add/Edit modal renderers polluted global valid/submitted state, so empty modal defaults could block parent Submit.
• Error message double-counted the same controls (vdata + schema / vocabularies → e.g. 4 fields → “8 validation errors”).
• PageNavigate on the Record Form page (e.g. “back to page 0”) pulled the main page into Record List row rules, creating ghost listName__* keys and inflating counts further (e.g. 10 vs 6).

Expected behavior after fix

• N required checkboxes (root + Record Form) → about N errors when invalid (not 2×N).
• Screens with PageNavigate on the Record Form page no longer inflate the count.
• Modal Add/Edit still validates locally; parent Submit validates list rows correctly.

How to Test

Follow steps detailed in ticket

Related Tickets & Packages

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

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

[cypress]

screen-builder    Run #2507

Run Properties:   Failed #2507  •  64d1bb0c20: Bugfix/FOUR-32292-b: Validation of required fields does not work correctly in Re...

Project	screen-builder
Branch Review	bugfix/FOUR-32292-b
Run status	Failed #2507
Run duration	42m 49s
Commit	64d1bb0c20: Bugfix/FOUR-32292-b: Validation of required fields does not work correctly in Re...
Committer	CarliPinell
View all properties for this run ↗︎

---

Test results
Failures	2
Flaky	0
Pending	19
Skipped	0
Passing	391
View all changes introduced in this branch ↗︎

---

Tests for review

  Loop.spec.js • 1 failed test • CI - Chrome

View Output

Test		Artifacts
Loop control > Verify validation on visible fields		Test Replay Screenshots

  DefaultValues.spec.js • 1 failed test • CI - Chrome

View Output

Test		Artifacts
Default values > Javascript default value		Test Replay Screenshots

[nolanpro]

QA server K8S was successfully deployed https://ci-016a15d52c.engk8s.processmaker.net

[nolanpro]

QA server K8S was successfully deployed https://ci-016a15d52c.engk8s.processmaker.net

[eiresendez]

Manual testing confirms that the reported scenario is fixed 👍 I'm just leaving a few observations:

1. Remove first-row-dependent conditional validation
2. Clarify empty-list semantics

[eiresendez]

🔴

• src/ValidationsFactory.js:409 — Record Form validation rules depend on the first row’s visibility state.
  • The rule tree is constructed using firstRow. FormElementValidations.isVisible() can therefore omit a conditionally visible required field when it is hidden in the first row.
  • If that field is visible and invalid in a later row, no rule exists to validate it and the parent form can submit invalid data.
  • Build the validation rules independently of one representative row, while evaluating conditional visibility separately for every row during validation.

Screen.Recording.2026-09-08.at.5.06.26.p.m.mov

[eiresendez]

🔴 The PR makes an empty Record List fail once for every required field in its Record Form. This behavior is explicitly covered by the new unit test, but it is outside the expected behavior of FOUR-32292.

@CarliPinell Could you confirm whether required fields inside the Record Form are also intended to require at least one row? Otherwise, this changes the previous behavior and may make existing screens with an optional empty Record List invalid.