Conversation
devmiguelangel
approved these changes
Sep 5, 2025
|
1 similar comment
|
|
QA server K8S was successfully deployed https://ci-4005483fe0.engk8s.processmaker.net |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue & Reproduction Steps
Case Status still In-Progress in All-Cases Page After Terminate End Event Triggered by Boundary Signal
Solution
Added a case sync status when a request end with a signal
How to Test
Import the process attached - test_boundary_event (1).json
Start a new case using the “Test boundary event” process.
Submit the first form that displays the Case Number.
On the next task, do not submit the form.
Start a second new case using the same “Test boundary event” process.
Submit the first form to proceed to the second task and submit it
Return to the All-Cases Page.
Observe the status for both cases:
The second case should show as Completed.
The first case still shows as In-Progress in the All-Cases view, but when opening the case details, it shows as Completed.
Screen.Recording.2025-09-05.at.15.23.06.mov
Related Tickets & Packages
https://processmaker.atlassian.net/browse/FOUR-25165
ci:deploy