Feature/FOUR-18337: FOUR-18113 - Implement logic to insert into screen data

[CarliPinell]

How to Test

Login PM4
Create new Screen
Drag Record List control
Choose new option Collection
Select Collection
Add columns from collection
In Data Selection dropdown select Single Record, Record or Multiple records
Use a rich text to Use the output Variable Name from record list like {{form_record_list_1.ColumnName}}
Save Screen and start a new Case

Related Tickets & Packages

https://processmaker.atlassian.net/browse/FOUR-18337

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:next

[cypress]

screen-builder    Run #1393

Run Properties:   Failed #1393  •  8b9173c1a8: Feature/FOUR-18337: FOUR-18113 - Implement logic to insert into screen data

Project	screen-builder
Branch Review	feature/FOUR-18337
Run status	Failed #1393
Run duration	07m 36s
Commit	8b9173c1a8: Feature/FOUR-18337: FOUR-18113 - Implement logic to insert into screen data
Committer	CarliPinell
View all properties for this run ↗︎

---

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

---

Tests for review

  tests/e2e/specs/DeviceVisivilityInspector.spec.js • 1 failed test • CI - Chrome

View Output

Test		Artifacts
Device Visiblility Inspector > Disabled device visiblility		Test Replay Screenshots