You are viewing the documentation for Blueriq 13. Documentation for other versions is available in our documentation directory.
The AQ_FlowOnRefresh container makes it possible to trigger a flow after refresh within the same page. In this flow you can execute all kind of service types, subflows and repeat flows (pages are not supported).
Parameters
You can define one flow per container, this flow will be started on every refresh attribute that is included in this container.
| Name | Description | Type |
|---|---|---|
| Flow | Select flow to start on refresh. | Flow |
| Validation | When nothing is selected, validation is done before flowing | Before flowing / After flowing |
Validation
With this parameter value it is possible to specify the timing of the page validation. Default behavior (when the parameter is not set) is to validate before flowing.
Runtime
When using the FlowOnRefresh in runtime, keep in mind that the started flows will be queued and started one another. In case of executing web-services this can result in long waiting times.
The flow on refresh doesn't support rollback method within the executed flow on refresh.
Overview
Content Tools
3 Comments
Unknown User (w.van.den.berg)
If a button on the page has the 'refresh' property, while it also has an associated (flow)event, this event will be ignored if the page contains a FlowOnRefresh container.
Daniel Venema
We have several of these containers in our model. I was looking for them in the Blueriq application log for the flows that are triggered by these containers but I couldn't find them. Is it possible that these are indeed not logged?
Unknown User (a.jansen)
Hi Daniel Venema, I have created a little test model (in BQ13) to double check this. The flow-on-refresh-flow is logged. For example in the (live) logging of this little test model I see "Starting flow on refresh: FlowOnRefreshFlow". Have also created a support ticket on your behalf to have a closer look at this.