FOUR-17272 tasks in a process without interstitial automatically skip to the next task

[devmiguelangel]

Issue & Reproduction Steps

Expected behavior:
If we do not have interstitial enabled in the tasks, we should not jump to the next form

Actual behavior:
As we see, the tasks are shown alone without opening in the Form Task

Solution

• Validate interstitial on redirect to the next task

How to Test

1. Log in
2. Create a process with a task
3. Verify that the tasks and the start event are not configured with interstitial
4. Start a new case

Requires

FOUR-17160

Related Tickets & Packages

FOUR-17272

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]

Passing run #1064 ↗︎

0

292

19

0

0

Details:

FOUR-17272 tasks in a process without interstitial automatically skip to the nex...
Project: screen-builder	Commit: c2a5f74530
Status: Passed	Duration: 30:07 💡
Started: Jul 22, 2024 8:02 PM	Ended: Jul 22, 2024 8:32 PM

Review all test suite changes for PR #1654 ↗︎

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

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

See analysis details on SonarQube