Problem description
Currently to configure blocks users are required to operate what is essentially a complex multi-tab form with various fields which may have subtle dependencies and constraints. It requires too much knowledge from users of where to navigate and what/how to configure values, what is mandatory and what is not.
Requirements
Recent improvement in #1655 and #1687 introduced high-level wizards for Policy creation. Similar approach can be taken for configuring individual blocks - wizards can guide users via the flow and provide contextual description/documentation of UI items to avoid referring to the official documentation for user convenience:
- implement (mini-) wizards for block configuration
- ensure there is a brief description of each step to guide user understanding of actions
- allow users to save and exit wizards at any time
Definition of done
- Wizard workflow is available for at least some of the blocks
- The option to use a wizard for block configuration (when available) is clearly indicated
- Documentation is updated accordingly
Acceptance criteria
- Users have an option to use wizards for configuring at least some of the block types.
Problem description
Currently to configure blocks users are required to operate what is essentially a complex multi-tab form with various fields which may have subtle dependencies and constraints. It requires too much knowledge from users of where to navigate and what/how to configure values, what is mandatory and what is not.
Requirements
Recent improvement in #1655 and #1687 introduced high-level wizards for Policy creation. Similar approach can be taken for configuring individual blocks - wizards can guide users via the flow and provide contextual description/documentation of UI items to avoid referring to the official documentation for user convenience:
Definition of done
Acceptance criteria