Page History
Description
Normal flow navigation is
...
designed to guide
...
users through a form or
...
application along a predefined
...
path. However,
...
not every application follows a fixed route. In these cases, the system should support users by keeping track of
...
their navigation history and the current state of the application
...
.
To
...
address this need, we
...
've introduced
...
FreeFlow navigation.
...
FreeFlow allows users to navigate freely through the application while still benefiting from structure and guidance. By using familiar building blocks like flows, pages, and containers
...
, FreeFlow
...
can be
...
implemented without the need for new concepts.
An enhanced validation engine in the Blueriq Runtime supports this flexible navigation. It ensures users receive timely validation messages on relevant pages, which they can resolve at their convenience—either immediately or later in the process. This way, users are empowered to complete the flow at their own pace, without being restricted by a fixed order.
Three parts of Blueriq are used to implement the FreeFlow navigation:
- There are two specific flowtypes required to use this type of navigation and change to behaviour of the validation engine while in these type flows.
- A container type to use as the navigation menu,
- An event named 'previous' to support flowing back to the last visited menu item.
To not interrupt the user's flow, when using the free flow mechanism, the validation engine handles all validation rules as non-blocking. An additional change in the validation engine when using free flow is the validation of read-only fields. The use case for such a validation is for read-only attributes that represent a conclusion based on multiple inputs. For instance a user can make deposits from multiple accounts, but the sum of the deposits must be 10.000 euros or more to proceed. In that case a validation on the read-only field 'sum of the deposits' could be used.
...
Overview
Content Tools