Page History

...

The order of the SinglePageFlow in the FreeFlow determines the ordering of the navigation menu. In case that a branch of SinglePageFlow is behind a condition node and it evaluates to false the whole branch is disabled is in the navigation menu, once the condition becomes true the branch is navigable from the navigation menu. 

A free navigable application still allows the user to navigate the application sequentially from SinglePageFlow to SinglePageFlow. To achieve this each first page of the SinglePageFlow must contain a button with either no event attached to it, or and event with the name "NextPage". This button event should connect to the to EndNode of the SinglePageFlow or a non-interactive FlowNode which leads to the EndNode. In order to navigate to the previously visited page a button can be placed on the page with event "PreviousPage", this button does not need to be connected.

...

1. The FreeFlow must be an exposed flow.
2. The FreeFlow consists several flows of type SinglePageFlow that should be directly connected to each other.
3. The FreeFlow can also contain other flow types before entering of the first SinglePageFlow, and after the last SinglePageFlow but not in between SinglePageFlows.
4. All validations on pages modelled in SinglePageFlows become non-blocking validation errors.
5. The name first page of a SinglePageFlow will be used to populate the AQ_NavigationMenu container.
6. The AQ_NavigationMenu container should always modelled inside the pages of the SinglePageFlow, or it will not be displayed.
7. Condition nodes modelled in a FreeFlow will acts as preconditions for buttons that make up the AQ_NavigationMenu container.
8. The SinglePageFlow's first page default (empty) or "NextPage" button event must be connected to a non interactive FlowNode for the navigation to work as expected.