-
Notifications
You must be signed in to change notification settings - Fork 243
FOUR-22600: Issues with stages #8486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
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
…shed. ## Description: Create a process Add Start Event → Task Form → End Event Create two stages and assigned these to flow to each task Publish the process Open the process by launchpad Create a case Return to process Delete the stages in the process Does not publish the changes Go to process launchpad Check that stages are not present after the changes Create new cases The new cases are created with stage but it is not visible in process launchpad Current Behavior: To stages are visible to start a CASE is necessary to publish the process with stages To stages are visible in LAUNCH PAD does not necessary to publish the process with stages which causes confusion when displaying case information Expected Behavior: The information in launch pad should be sync If there are stages the new cases should be created with the corresponding stage If there are not stages the new cases should be created without stages To this it necessary that stages will be publish to avoid errors and confusions ## Related Tickets & Packages https://processmaker.atlassian.net/browse/FOUR-25926
FOUR-25905: Error in alternatives when changing the position of the stages
FOUR-23421 There is confusion with the stages when they are not publi…
|
QA server K8S was successfully deployed https://ci-e99bdcbf88.engk8s.processmaker.net |
## Description - Steps to Reproduce Create a process Add Start Event → Task form → End Event Add new stages Assign the stages in the flow Create alternative B Delete one alternative Publish the changes - Current Behavior Stage labels are not lost in both alternatives, this remain in alternative B - Expected Behavior Stage labels should lost in both alternatives ## Related Tickets & Packages https://processmaker.atlassian.net/browse/FOUR-25979
FOUR-25979 Label are not lost in alternative B
|
gproly
approved these changes
Sep 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
There is confusion with the stages when they are not published.
Error in alternatives when changing the position of the stages
Solution
How to Test
Describe how to test that this solution works.
Related Tickets & Packages
Code Review Checklist
ci:deploy