Versions Compared

Old Version 24

changes.mady.by.user Terry van der Griend

Saved on

compared with

New Version 25

changes.mady.by.user Paul Hoeijenbos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Element typeType nameExplanation
FlowTypeFreeFlowThe main flow to detect if an application should be using the free navigable strategy
FlowType

SinglePageFlow

Sub flows of the FreeFlow to which the user can navigated between. Each SinglePageFlow will become a menu item.
ContainerType

AQ_NavigationMenu

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 

...

  1. The exposed flow must be of type FreeFlow.
  2. The SinglePageFlows should be directly connected to each other inside a free navigable flow.
  3. The FreeFlow can 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 display title of the first page of a SinglePageFlow will be used to populate the AQ_NavigationMenu container.
  6. The AQ_NavigationMenu container should always be modelled in the first page of the SinglePageFlow, or it will not be displayed.
  7. Condition nodes modelled in between SinglePageFlows will act 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 an EndNode or an non interactive FlowNode that leads to an EndNode 

Accelerator

An example project for this feature can be cound in the Accelerator section.