Screen components are not displayed

[marcoAntonioNina]

Issue & Reproduction Steps

The list of components is not displayed correctly when a component is found that does not have the group to which it should be registered defined.

Expected behavior:
The component list should be displayed normally.

Actual behavior:
If a component is registered from a package and does not have a group defined, the component listing is blocked.

Solution

• Add a default group if the group is not defined.

How to Test

Test the steps above

Related Tickets & Packages

• FOUR-17914

ci:next

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]

---

Test summary

296 • 0 • 19 • 0

---

Run details

Project	screen-builder
Status	Passed
Commit	797c4a2
Started	Aug 16, 2024 12:20 PM
Ended	Aug 16, 2024 12:28 PM
Duration	07:30 💡
OS	Linux Ubuntu -
Browser	Chrome 127

View run in Cypress Cloud ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Cloud

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[rodriquelca]

the validation works fine

[boliviacoca]

@ryancooley this would need to be merged with priority please.