Page History

With a Dashboard_FlowWidget a flow in another module can be started. The module has to be a part of the same project. Data can be added to the widget when starting, using a data mapping. A Dashboard_FlowWidget can respond to PortalMessages. Using containers of this type, a user is able to model a dashboard containing widgets that influence and react on to other widgets. The container acts as a placeholder in which a flow can be started.

This container reacts on a portal message can react to those portal messages that you define indicate inside the widget. The portal message is available from the message bus. As soon as the portal message is received, the connected flow is restarted.

The widget can possibly react on to more than one portal message, but not on more portal messages at the same time. The data from the portal message is placed in the profile before flowingthe flow is restarted.

When you use this container you have to specify the following elements in the first tab (flow):

• The module that contains the flow
• The (exposed) flow
• The configuration module of the data mapping (optional)
• The data mapping (optional, only needed used when the flow is started without portal message)

In the second tab (portal messages) you have to specify specify to which PortalMessages the widget will respond, and which target attributes should be used for the selected portal message.

It is only possible to refresh the content of the widget based on a portal message. If the complete dashboard needs to react, you should use the AQ_Dashboard_PortalMessageListener.

See 3. Dashboards for information on how to build a dashboard.