Page History

...

To not interrupt the user's flow, when using the free flow mechanism, the validation engine handles all validation rules as non-blocking. An additional change in the validation engine when using free flow is the validation of read-only fields. The usecase use case for such a validation is for  for read-only attributes that represent a conclusion based on multiple inputs. For instance a user can make deposits from multiple accounts, but the sum of the deposits must be 10.000 euros or more to proceed. In that case a validation on the read-only field 'sum of the deposits' could be used.

...

Each free flow menu item will correspond to a flow of type SinglePageFlow. This suggests that the single page flow can only contain a single page, which is not entirely true. We do expect the single page flow to have one 'landing' page for the menu item. From that landing page users can navigate to other pages in the single page flow, but they can not navigate to other menu items while doing that. So in the model the menu should be disabled. A typical usecase use case for this type of navigation is when the menu landing page contains an instance list and new instances will be added on a separate page. In this case the menu can temporarily be disabled when the user fills out the information in the instance and returns to the menu landing page to continue the free flow.

...