FOUR-27077: Conditions are not working when Display Next Assgined Task option is selected as condition

[rodriquelca]

Issue & Reproduction Steps

Expected behavior:
Task destination should be displayed according to each condition
Actual behavior:
All conditions are not displayed according to each matching only the Screen Interstitial is displayed

Solution

• add displayNextAssignedTask validation

How to Test

please review the steps in the related ticket

Related Tickets & Packages

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

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:modeler:feature/FOUR-26707
ci:screen-builder:feature/FOUR-26707
ci:processmaker:feature/FOUR-26707

[cypress]

screen-builder    Run #2071

Run Properties:   Failed #2071  •  a4d1d7ed5e: FOUR-27077: Conditions are not working when `Display Next Assgined Task` option ...

Project	screen-builder
Branch Review	feature/FOUR-26707
Run status	Failed #2071
Run duration	09m 45s
Commit	a4d1d7ed5e: FOUR-27077: Conditions are not working when `Display Next Assgined Task` option ...
Committer	David Callizaya
View all properties for this run ↗︎

---

Test results
Failures	1
Flaky	0
Pending	19
Skipped	7
Passing	381
View all changes introduced in this branch ↗︎

---

Tests for review

  tests/e2e/specs/ValidationRules.spec.js • 1 failed test • CI - Chrome

View Output

Test		Artifacts
Validation Rules > Validations should be skipped for readonly fields		Test Replay Screenshots

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube