Selective Variable Submission in Screens

[rodriquelca]

Issue & Reproduction Steps

Solution

• add src/mixins/VariablesToSubmitFilter
  Original diagram

Feature diagram

add variables to submit component

How to Test

Test the steps above

Related Tickets & Packages

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

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

Run Properties:   Passed #2086  •  f418c2e190: Selective Variable Submission in Screens

Project	screen-builder
Branch Review	feature/FOUR-27783
Run status	Passed #2086
Run duration	09m 39s
Commit	f418c2e190: Selective Variable Submission in Screens
Committer	Rodrigo Quelca
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 ↗︎

[rodriquelca]

Issue & Reproduction Steps

Solution

• add src/mixins/VariablesToSubmitFilter
  Original diagram

Feature diagram

How to Test

Test the steps above

Related Tickets & Packages

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

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.

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube

[caleeli]

Consider to remove the console.logs for prod mode