Page History
...
Element type | Type name | Explanation |
---|---|---|
FlowType | FreeFlow | The main flow to detect if an application should be using the free navigable strategy |
FlowType | Sub flows of the FreeFlow to which the user can navigated between. Each SinglePageFlow will become a menu item. | |
ContainerType | The menu container which displays menu-items using the page display title of the first page in the SinglePageFlow | |
ContentStyle | NavigationMenu | Default contentstyle of the AQ_NavigationMenu container |
...
- The exposed flow must be of type FreeFlow.
- The SinglePageFlows should be directly connected to each other inside a free navigable flow.
- The FreeFlow can contain other flow types before entering of the first SinglePageFlow, and after the last SinglePageFlow but not in between SinglePageFlows.
- All validations on pages modelled in SinglePageFlows become non-blocking validation errors.
- The display title of the first page of a SinglePageFlow will be used to populate the AQ_NavigationMenu container.
- The AQ_NavigationMenu container should always be modelled in the first page of the SinglePageFlow, or it will not be displayed.
- Condition nodes modelled in between SinglePageFlows will acts act as preconditions for buttons that make up the AQ_NavigationMenu container.
- The SinglePageFlow's first page default (empty) or "NextPage" button event must be connected to an EndNode or an non interactive FlowNode that leads to an EndNode
Overview
Content Tools