Page History

This container allows you to react on to portal messages. It is an invisible container that gives you exits on a page which can be restarts the flow in which the page is located, when the container is triggered by a portal message. The container has no parameters. The containments consists of one or more portal messages, each with a 'mapping' between the message field fields and the corresponding attribute.You want to use this container when the complete dashboard has to flow to a different page. When staying on the same page, only the widgets need to refresh, and this container is not needed

It is typically used on a dashboard page that contains widgets (e.g., a Container type: AQ_Dashboard_ProjectWidget or a Container type: AQ_Dashboard_FlowWidget). One of the widgets throws a PortalMessage, to which the flow should respond in which the dashboard page is found. A typical use case is to flow to another dashboard page, for example one that shows a widget in which a task is executed.

This container is not needed when only the widgets on the dashboard page need to refresh. The Container type: AQ_Dashboard_ProjectWidget and Container type: AQ_Dashboard_FlowWidget have parameters to respond to portal messages.