Fix contradictory note about duplicate Stage weights#774
Fix contradictory note about duplicate Stage weights#774promptless-for-oss wants to merge 2 commits into
Conversation
The Moving Contacts note claimed multiple Stages could share the same weight across funnels, which contradicts the unique-weight constraint introduced in mautic/mautic#15404 and documented in the Weight field description. Correct the note to state each Stage must have a unique weight across all funnels.
| .. note:: | ||
|
|
||
| You can have multiple funnels with different Stages, and multiple Stages across those funnels with the same weight. A Contact can only ever be in one Stage at a time. It's not possible to move a Contact to a Stage which has a lesser weight than their current Stage. For example if they're currently in Stage B which has a weight of 50, you can't move them to Stage A which has a weight of 25. | ||
| You can have multiple funnels with different Stages, but each Stage must have a unique weight across all funnels. A Contact can only ever be in one Stage at a time. It's not possible to move a Contact to a Stage which has a lesser weight than their current Stage. For example if they're currently in Stage B which has a weight of 50, you can't move them to Stage A which has a weight of 25. |
There was a problem hiding this comment.
mautic/mautic#15404 adds a global UniqueEntity constraint on the Stage weight field (mautic.stage.weight.unique = "Another stage with this weight already exists."), so the prior claim that "multiple Stages across those funnels with the same weight" are allowed is now false. Rewrote the note to say each Stage must have a unique weight across all funnels.
Source: mautic/mautic#15404
|
This is related to #758 resp mautic/mautic#15404 @andersonjeccel can you please check if the change is correct? |
|
@andersonjeccel, can you please follow up? Thanks! |
|
We double-checked this against the source change. The unique-weight constraint from mautic/mautic#15404 is a class-level One note for completeness: this uniqueness is enforced at the application/validation layer (no DB-level unique index), which is an app-level guarantee and appropriate for the user-facing docs. The edit reads correctly as-is. |
3 participants
Open this suggestion in Promptless to view citations and reasoning process
Corrects the "Moving Contacts between Stages" note, which incorrectly stated that multiple Stages across funnels could share the same weight. The unique-weight constraint added in mautic/mautic#15404 (and already documented in the Weight field description) makes each Stage's weight unique across all funnels. Targets the 7.2 user-docs branch.
Trigger Events
Tip: Tag @Promptless in a GitHub issue to turn it into a documentation update 🐙