Record list does not retrieve the selected value/data in the next task.

[CarliPinell]

Solution

• When a record is selected from the Record List, the value persists when moving to the next task.

How to Test

1. Create/import process attachaed in ticket
2. Create a simple screen
3. Add record list and add a collection to the configuration
4. Create a case, select an option in the record list, complete task 1

Related Tickets & Packages

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

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.

[cypress]

screen-builder    Run #2318

Run Properties:   Passed #2318  •  783df9dad4: Record list does not retrieve the selected value/data in the next task.

Project	screen-builder
Branch Review	bugfix/FOUR-27264
Run status	Passed #2318
Run duration	44m 58s
Commit	783df9dad4: Record list does not retrieve the selected value/data in the next task.
Committer	CarliPinell
View all properties for this run ↗︎

---

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

[eiresendez]

@CarliPinell the fix addresses the original issue, and I confirmed it no longer reproduces in manual testing.

However, this PR introduces a new pagination issue through the added selectedRow watcher: the existing @change path already provides a page-relative index, while the watcher passes a global index into the same handler, causing an incorrect selectedRowIndex and duplicate updates on page 2 and beyond. This behavior was not present before this change, could you please review it?

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
5 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube

[eiresendez]

The new helper extraction is clean and keeps the component’s selection contract explicit. form-record-list.vue:626 now receives a page-relative index and delegates the single conversion to production-tested code 👍 👍