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.

...

• 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)