Page History

...

Any logic which is modelled at the start and the end of a SinglePageFlow will be executed every time the SinglePageFlow is visited. Logic that is handled in between pages of the SinglePageFlow will only be executed when visited just like a normal sequential flow.  

To navigate between SinglePageFlow in a free navigable application the first page must contain a button with default (empty) exit event or a named exit event called "NextPage", this exit event must be either directly connected to the EndNode of the SinglePageFlow or a non-interactive FlowNode leading to the EndNode. In the sitauation that the SinglePageFlow contains multiple pages a second button event should be created connecting the first page to second page. 

To navigate to the previous SinglePageFlow in a free navigable application the first page must contain a button with anamed exit event called "PreviousPage", this exit event does not have to be connected in flow.

Constraints

1. Validations on a first page in a SinglePageFlow are non blocking.
2. The title of the first page in a SinglePageFlow is used in the AQ_NavigationMenu.
3. Logic which is modelled before the first page and before the EndNode of the SinglePageFlow will be executed every time the flow is visited.
4. The "NextPage" or default exit event of the first page must be connected to EndNode or a FlowNode that leads to the EndNode.