FOUR-16765: The API calls in modeler is execute twice

[henryjonathanquispe]

Issue & Reproduction Steps

1. Go to modeler
2. Create a process and a task with Screens and Display Next Assigned Task to Task Assignee enable
3. Open the debuger
4. Click on any task and see th calls in Network

Solution

• Add validation to Inspector Panel in Modeler

How to Test

• Go to modeler
• Create a process and a task with Screens and Display Next Assigned Task to Task Assignee enable
• Open the browser debugger
• Click on any task and see the calls in Network

Related Tickets & Packages

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

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:next

[cypress]

modeler    Run #1496

Run Properties:   Failed #1496  •  629c5ed8df: FOUR-16765: The API calls in modeler is execute twice

Project	modeler
Branch Review	feature/FOUR-16765
Run status	Failed #1496
Run duration	03m 03s
Commit	629c5ed8df: FOUR-16765: The API calls in modeler is execute twice
Committer	henryjonathanquispe
View all properties for this run ↗︎

---

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

---

Tests for review

  Pools.cy.js • 1 failed test

View Output

Test		Artifacts
Pools > moves boundary event to another process when dragged to that pool		Test Replay Screenshots

  MessageFlows.cy.js • 1 failed test

View Output

Test		Artifacts
Message Flows > should connect message end event to boundary message event in different pools		Test Replay Screenshots

  BoundaryTimerEvent.cy.js • 1 failed test

View Output

Test		Artifacts
Boundary Timer Event > moves to another task when dragged over		Test Replay Screenshots

  Tasks.cy.js • 1 failed test

View Output

Test		Artifacts
Tasks > Update task element destination		Test Replay Screenshots

  CopyElements.cy.js • 0 failed tests

View Output

Test		Artifacts

The first 5 failed specs are shown, see all 92 specs in Cypress Cloud.

[caleeli]

The change looks good, but seems needs a rebase, since some tests are failing

[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