FOUR-26908: Update the range to CSS to improve the development for tce screens implementations

[henryjonathanquispe]

Issue & Reproduction Steps

Update the range to css to improve the development for tce screens implementations

Related Tickets & Packages

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

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

---

Note

Removes the hard cap that threw "CSS is too long" during CSS AST walking in src/components/vue-form-renderer.vue.

^{Written by Cursor Bugbot for commit 21b46b5. This will update automatically on new commits. Configure here.}

[cypress]

screen-builder    Run #2062

Run Properties:   Passed #2062  •  2a61e93757: FOUR-26908: Update the range to CSS to improve the development for tce screens i...

Project	screen-builder
Branch Review	feature/FOUR-26661
Run status	Passed #2062
Run duration	09m 39s
Commit	2a61e93757: FOUR-26908: Update the range to CSS to improve the development for tce screens i...
Committer	henryjonathanquispe
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 ↗︎

[pmPaulis]

Team,
I reported the issue to generate a DEPLOY for qa-test purposes
https://processmaker.atlassian.net/browse/SCO-31455

[vladyrichter]

QA server K8S was successfully deployed https://ci-73dd728246.engk8s.processmaker.net

[vladyrichter]

QA server K8S was successfully deployed https://ci-73dd728246.engk8s.processmaker.net

[vladyrichter]

QA server K8S was successfully deployed https://ci-73dd728246.engk8s.processmaker.net

[ana-mauricio]

The fix is correct. The following tests were tested

• Verify if long CSS doesn't show errors with a screen Check Mark
• Verify if long CSS is used with requests Check Mark
• Verify if long CSS is used with WE Check Mark
• Verify if long CSS is used in the import/export screen Check Mark
• Verify if CSS is displayed in screen templates Check Mark
• Verify if more than one long CSS is used on the same screen Check Mark
• Verify if long CSS is used in a nested screen Check Mark
• Verify if long CSS is used in a screen email Check Mark
• Verify if long CSS is used in a display screen Check Mark
• Verify if long CSS is used in a conversational form Check Mark

[vladyrichter]

QA server K8S was successfully deployed https://ci-73dd728246.engk8s.processmaker.net

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[pmPaulis]

Team,
This PR is not necesary because we found other way to manage a large CSS