You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
Important
This Flowtype is only intented for:
a. Non-DCM applications
b. DCM case modelling architecture including DCM Dashboards
c. 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.
FreeFlows are used when the sequential flows does not fit the means to navigate through your application. Using the FreeFlows the user is able to navigate via a menu to any chosen page that is modelled in a sequential flow, using this way of flowing the validations are executed on every page but they are not blocking when navigation between pages, and only become blocked when end of the FreeFlow is reached.
How to use a FreeFlow
A FreeFlow can be implemented using the set of following elements.
| Element Type | Type name |
|---|---|
| FlowType | FreeFlow |
| FlowType | SinglePageFlow |
| ContainerType | AQ_NavigationMenu |
| ContentStyle | NavigationMenu |
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 FreeFlow must be an exposed flow.
- The FreeFlow consists several flows of type SinglePageFlow that should be directly connected to each other.
- The FreeFlow can also 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 name first page of a SinglePageFlow will be used to populate the AQ_NavigationMenu container.
- Condition nodes modelled in a FreeFlow will acts as preconditions for buttons that make up the AQ_NavigationMenu container.
Overview
Content Tools