Page History

...

A FreeFlow can be implemented using the set of following elements. 

FreeFlows are used when the sequential flow does not fit the means to navigate through your application. Using the FreeFlows you are able to create a flow for your application where the user can freely navigate between pages without triggering the any blocking validation warnings.  This can be achieved by modelling a FreeFlow as an entry point of your application where you desire free navigation, it works in conjunction with the flow type SinglePageFlow, which is always a subflow of the FreeFlow. By modelling SinglePageFlows after each other and configuring a AQ_NavigationMenu container on the first page of each SinglePageFlow the FreeFlow is able to populate the AQ_NavigationMenu container with menu items. The menu items contain the name of the first page that resides in SinglePageFlow.

Constraints

The new navigation concept is introduced as Runtime concept, that is triggered by a specific model structure and naming convention.The constraints are:

1. The FreeFlow

...

1. must be an exposed flow.
2. The FreeFlow consists

...

1. several flows of type SinglePageFlow

...

1. that should be directly connected to each other.
2. The FreeFlow can also contain other flow

...

1. types before

...

1.  entering of the first SinglePageFlow, and after the last SinglePageFlow but not in between

...

1. SinglePageFlows.
2. All validations on pages modelled in SinglePageFlows become non-blocking validation errors.
3. The name first page of a SinglePageFlow will be used to populate the AQ_NavigationMenu container.
4. Condition nodes modelled in a FreeFlow will acts as preconditions for buttons that make up the AQ_NavigationMenu container.