Content
View differences
Updated by Jan Sandbrink over 1 year ago
Currently there is a strong coupling between preceding and succeeding steps during setup.
Problem is that our steps will now differ depending on authentication method:
```text
Two-Way-OAuth:
general -> oauth app -> oauth client -> automatic management
SSO:
general -> audience -> automatic management
```
This means in one case "oauth client" precedes "automatic management" and in the other case "audience" precedes it. We thus need to reduce the coupling between the steps, so that we can easily skip single steps without influencing the rest of the "step-by-step" guide.
### QA hints
This ticket is about not really changing user visible behaviour, but to give some more hints than "it should behave the same as before":
1. The affected views are reachable from `/admin/settings/storages`
2. Both flows are affected, creating a new storage and editing an existing storage
3. The _new_ flow should behave like a wizard, moving the user forward after each successful form submission
4. the _edit_ flow should go back to the "all collapsed" view after a successful form
5. Things like "showing errors" can potentially break behaviour because they reload parts of the UI
6. Moving in unexpected order can break things (e.g. canceling the wizard and continuing in the edit version)
Problem is that our steps will now differ depending on authentication method:
```text
Two-Way-OAuth:
general -> oauth app -> oauth client -> automatic management
SSO:
general -> audience -> automatic management
```
This means in one case "oauth client" precedes "automatic management" and in the other case "audience" precedes it. We thus need to reduce the coupling between the steps, so that we can easily skip single steps without influencing the rest of the "step-by-step" guide.
### QA hints
This ticket is about not really changing user visible behaviour, but to give some more hints than "it should behave the same as before":
1. The affected views are reachable from `/admin/settings/storages`
2. Both flows are affected, creating a new storage and editing an existing storage
3. The _new_ flow should behave like a wizard, moving the user forward after each successful form submission
4. the _edit_ flow should go back to the "all collapsed" view after a successful form
5. Things like "showing errors" can potentially break behaviour because they reload parts of the UI
6. Moving in unexpected order can break things (e.g. canceling the wizard and continuing in the edit version)