FOUR-19778 Encrypted field does not have read-only mode

[julceslauhub]

Issue & Reproduction Steps

Expected behavior:
"readonly" attribute should be considered when a value is revealed/plain

Actual behavior:
"readonly" attribute is omitted

Solution

Keep a copy of the original values in order to restore the correct "readonly" mode

Related Tickets & Packages

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

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 #1635

Run Properties:   Passed #1635  •  4661f6ebcc: FOUR-19778 Encrypted field does not have read-only mode

Project	screen-builder
Branch Review	FOUR-19778
Run status	Passed #1635
Run duration	08m 48s
Commit	4661f6ebcc: FOUR-19778 Encrypted field does not have read-only mode
Committer	julceslauhub
View all properties for this run ↗︎

---

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

[caleeli]

@julceslauhub please include the test for the Encrypted Field + Read-only scenario