FOUR-6787 If more than two tasks end in an Intermediate Signal Throw Event Element, the flow will not be correctly completed

[devmiguelangel]

Summary

If more than two tasks end in an Intermediate Signal Throw Event Element, the flow will not be correctly completed

An Intermediate Throw Event with two or more incoming sequence flows behaved like an AND-join. TransitionTrait::hasAllRequiredTokens only fired the shared transition when every incoming state had a token, and one firing consumed one token from each incoming flow. When an exclusive or parallel split delivered a token on only some of those flows, the event never fired and the request stayed In Progress.

The event is no longer a join. IntermediateThrowEventTransition fires as soon as any incoming flow has a token and consumes exactly one token per firing, so each arriving token triggers the event and continues downstream. The graph is unchanged: one incoming state per sequence flow, all connected to the same transition. Token persistence and ThrowEventTokenPassed still happen on that transition, which keeps the previous event order for boundary and message tests.

Before this change the transition waited until inA, inB, and inC all held a token. Now a token on any one of them is enough.

Related Tickets

FOUR-6787
ProcessMaker/nayra#240

ci:nayra:FOUR-6787

.

[cursor]

PR Summary

Low Risk
Test-only changes (fixture plus feature tests); no application or engine code modified in this diff.

Overview
Adds regression coverage for FOUR-6787: an Intermediate Message Throw Event fed by three exclusive-gateway branches must not behave like an AND-join and block completion.

Introduces tests/Fixtures/four_6787_intermediate_throw_event.json (exclusive gateway → Form Task 1/2/3 → shared node_19 → message end) and IntermediateThrowEventMergeTest, which imports the package, starts a request, completes the gateway branch for select 1, 2, or 3, and asserts the process request reaches COMPLETED in each case.

^{Reviewed by Cursor Bugbot for commit b194341. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 2e9aed3. Configure here.}

[decisions-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube