Versions Compared

Old Version 18

changes.mady.by.user Roy Bissels

Saved on

compared with

New Version 19

changes.mady.by.user Terry van der Griend

Saved on

Key

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

This Flowtype is only intented intended for:

a. Non-DCM applications

This Flowtype is not intended for:

ab. DCM case modelling architecture including DCM Dashboards

cb. Non- External flow applications

All other older structures (in page modelling) are not supported.

As we intend to make this feature a native component, also design time, at that moment in time it will become impossible to model this. Therefor we strongly advise to not model it in this way if you wish to remain using only out of the box features.

...

Inside the FreeFlow itself, or one of its sub flows, a connected group of SinglePageFlows can be modelled to create a free navigable flow. These SinglePageFlows act as the entry points of navigation actions. It is advised to not have any logic in between the SinglePageFlows other than condition nodes.

When navigating between SinglePageFlows by using the navigation actions, the outer flow of that connects the SinglePageFlows is not used as , the Runtime jumps between the SinglePageFlows. If logic is required make sure that it either resides in the SinglePageFlow (as it will be executed every time the flow is visited) or before first SinglePageFlow and after the last SinglePageFlow. 

...

The navigation menu of a free navigable flow is build by using first the name of the first page in a SinglePageFlow. For the navigation menu to be displayed the pages of a SinglePageFlow should contain a AQ_NavigationMenu container. Navigating in a free navigable flow can achieved via two ways:

...

  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 name first page of a SinglePageFlow will be used to populate the AQ_NavigationMenu container.
  6. The AQ_NavigationMenu container should always be modelled inside in the pages first page of the SinglePageFlow, or it will not be displayed.
  7. Condition nodes modelled in between SinglePageFlows 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 an EndNode or an non interactive FlowNode that leads to an EndNode