Page History

...

Normal flow navigation is meant to guide the user through a form or an application along a predefined route. However, when no such predefined route exists, they system should support the user in navigating the application, by keeping track of the path they have travelled and current status of the application as well. To help achive this we have now introduced the FreeFlow navigation.

By applying specific construcs constructs of flows, pages and containers the FreeFlow mechanism can be applied using the building blocks we all already know. An adaptation in the validation engine of the Blueriq Runtime helps the user to navigate freely, while being attented to validation messages on pages, that can be solved along the way whenever the user wants to or is able to. After which the whole flow can be completed.

...

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 usecase use case for such a validation is for  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.

...

Each free flow menu item will correspond to a flow of type SinglePageFlow. This suggests that the single page flow can only contain a single page, which is not entirely true. We do expect the single page flow to have one 'landing' page for the menu item. From that landing page users can navigate to other pages in the single page flow, but they can not navigate to other menu items while doing that. So in the model the menu should be disabled. A typical usecase use case for this type of navigation is when the menu landing page contains an instance list and new instances will be added on a separate page. In this case the menu can temporarily be disabled when the user fills out the information in the instance and returns to the menu landing page to continue the free flow.

...

• external flows, because the external flow creates its own session it doesn't have the same validation context ánd cannot provide the same user experience as this session dóes apply blocking validation 
• widgets using the AQ_DashboarDashboard_FlowWidget and AQ_DashboarDashboard_ProjectWidget. The same reasons as per the external flows apply.
• applying a repeat condition to a SinglePageFlow. This flowtype is not meant to be repeatable (in order to create a undefined number of menu items in the AQ_NavigationMenu container)