Block going to next step, also affects previous step? #4579
Comments
joeribekker
added
bug
|
Refinement: likely related to the |
sergei-maertens
added
needs-backport
|
Refinement: We will probably need to discuss this and scenarios to see what happens and what people expect to happen. |
|
Discussed with Sergei: I'll try to reproduce this and check if the
|
|
@sergei-maertens I checked this locally with the form from Hoorn, in their logic a user defined variable is set to
and then in step 2 if this userdefined variable is
which does mean that you cannot go to the next step anymore, because the step is considered reached if you reach it once and the variable can only be modified when going to the next step. I'm not sure if this kind of logic is commonplace (setting a variable based on values from the previous step), but I think you're right that determining the current step in the logic is not working as it should |
previously the current step was inferred by looking at the last completed step and considering the step after that the current step. This does not work however if you complete a step and go back to the previous step, so instead we explicitly pass the current form step via the serializer context
previously the current step was inferred by looking at the last completed step and considering the step after that the current step. This does not work however if you complete a step and go back to the previous step, so instead we explicitly pass the current form step via the serializer context
previously the current step was inferred by looking at the last completed step and considering the step after that the current step. This does not work however if you complete a step and go back to the previous step, so instead we explicitly pass the current form step via the serializer context
…-to-next-step-bug 🐛 [#4579] Ensure triggerFromStep uses the correct current_step
previously the current step was inferred by looking at the last completed step and considering the step after that the current step. This does not work however if you complete a step and go back to the previous step, so instead we explicitly pass the current form step via the serializer context Backport-of: #4967
previously the current step was inferred by looking at the last completed step and considering the step after that the current step. This does not work however if you complete a step and go back to the previous step, so instead we explicitly pass the current form step via the serializer context Backport-of: #4967
Product versie / Product version
2.6.13
Customer reference
Taiga Hoorn 37
Omschrijf het probleem / Describe the bug
Je kunt na een keuze / waarde ervoor zorgen dat je niet verder mag gaan door: blokkeer doorgang naar volgende stap.
Hiervoor moet je aangeven dat dat blokkeren pas ingaat als je in een bepaald stap komt.
Maar als je terug gaat naar de Vorige stap (Uw gegevens) wordt de button daar geblokkeerd.
Waarschijnlijk omdat je al bij Aanvraag bent geweest. Het werkt blijkbaar niet vanaf Aanvraag
Heb van alles geprobeerd om dit op te heffen, maar het lukt mij niet om dit te de-blokeren.
Stappen om te reproduceren / Steps to reproduce
No response
Verwacht gedrag / Expected behavior
No response
Screen resolution
None
Device
None
OS
None
Browser
No response
The text was updated successfully, but these errors were encountered: