FOUR-19579: [41110] Bitia S.R.L. - Input in collection edit screen not showing 0 variable

[henryjonathanquispe]

Issue & Reproduction Steps

1. Log into ProcessMaker, go to the Admin tab, click on Collections, and create a new one.
2. in the screen of creation put an input type Integer and Select with value as well integer.
3. use the same screen to edit a collection
4. add a new record and put values 0.
5. now edit a collection

Current Behavior:

The input type integer with value 0 is not showing either the select, but then the input/select has a value different to 0 is showing the value

Expected Behavior:

Inputs should show values in 0

Related Tickets & Packages

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

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

[cypress]

screen-builder    Run #1736

Run Properties:   Failed #1736  •  956c66f751: FOUR-19579: [41110] Bitia S.R.L. - Input in collection edit screen not showing ...

Project	screen-builder
Branch Review	bugfix/FOUR-19579
Run status	Failed #1736
Run duration	09m 02s
Commit	956c66f751: FOUR-19579: [41110] Bitia S.R.L. - Input in collection edit screen not showing ...
Committer	henryjonathanquispe
View all properties for this run ↗︎

---

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

---

Tests for review

  LoadComplexData.spec.js • 1 failed test • CI - Chrome

View Output

Test		Artifacts
Validation Rules (Advanced test) > Verify all validation rules within loops		Test Replay Screenshots

  DefaultValuesWithComputedFields.spec.js • 1 failed test • CI - Chrome

View Output

Test		Artifacts
Computed field and default values > Test default values with computed fields		Test Replay Screenshots

  DeviceVisivilityInspector.spec.js • 1 failed test • CI - Chrome

View Output

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

  ComputedFields.spec.js • 1 failed test • CI - Chrome

View Output

Test		Artifacts
Computed fields > Focuses the first field that has an error		Test Replay Screenshots

[tokensPM]

QA server K8S was successfully deployed https://ci-50a097789d.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-50a097789d.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-50a097789d.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-50a097789d.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-50a097789d.engk8s.processmaker.net

[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

[pmPaulis]

We closed this PR becasue the ticket related was moved to MORE INFORMATION and this change will cause impact
Regards,