You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the middle of the wizard's workflow, the user abandon it by clicking a "cancel" button, since it has no interest in continuing.
Later the user come back and enter the wizard's workflow, on the same session.
Current behavior
The user will be directed to the point where it stopped last.
Desired behavior
The user should start at the workflow's beginning since it has canceled the last one.
Workarounds
It is possible to implement this behavior by subclassing SessionWizardView and overloading the post handler. On the template, add an extra "cancel" button with a known value (something like "cancel-workflow"). On the overloaded post handler, evaluate the POST data by checking if value "wizard_goto_step" has the known cancel value on it (i.e. "cancel-workflow"). If not, call the superclass implementation. Otherwise, reset the storage and redirect to a pre-defined web page.
Reasons
Although the workaround implementation is quite simple, this is an interesting behavior that should be added to the code base in order to consider such cancellation scenarios.
The text was updated successfully, but these errors were encountered:
Scenario
Current behavior
Desired behavior
Workarounds
It is possible to implement this behavior by subclassing
SessionWizardView
and overloading thepost
handler. On the template, add an extra "cancel" button with a known value (something like "cancel-workflow"). On the overloadedpost
handler, evaluate the POST data by checking if value "wizard_goto_step" has the known cancel value on it (i.e. "cancel-workflow"). If not, call the superclass implementation. Otherwise, reset the storage and redirect to a pre-defined web page.Reasons
Although the workaround implementation is quite simple, this is an interesting behavior that should be added to the code base in order to consider such cancellation scenarios.
The text was updated successfully, but these errors were encountered: