Issue

When checkboxes with initiallyChecked: true are unchecked in a loop and the user returns to the process task, all checkboxes appear checked despite correct false values in the data.

Solution

Two locations in DataManager.js and DefaultValues.js used falsy checks instead of explicit undefined checks. Replaced falsy checks with explicit undefined checks to preserve false boolean values.

How To Test

1. Create a Process with a Task that has a Screen
2. Add a Gateway after the Task that routes back to the same Task (creating a loop)
3. Within the Task Screen, add a Form Loop component
4. Inside the Form Loop, add one or more Checkbox components
5. Configure the Checkboxes with initiallyChecked: true (checkboxes should appear checked by default)
6. Save and start a new Process Request
7. On the initial Task screen, observe that all checkboxes within the loop are checked (as expected)
8. Uncheck some (but not all) checkboxes
9. Submit the Task to proceed to the Gateway
10. Complete the Gateway to route back to the same Task
11. Expected Result: When the Task screen loads again, the checkbox states should be preserved:
    • Checkboxes that were unchecked should remain unchecked
    • Checkboxes that were checked should remain checked

ci:deploy

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.