You can automate flows and dashboard deployment, update, and activation by adding special tags to it. An automated app is automatically started when the app is installed or when Flow Director server is started. Further, flows and dashboards changed after a Git
pull (automatic or manual) are deactivated without data loss, updated, and reactivated automatically.
Each app has a start/stop button that takes effect if flows and dashboards have automation tags set. If the button is green, the app is started:
Click to stop it:
You can see the corresponding entries in the app log:
Without automation tags set, the button does not affect.
You can set the following automation tags:
automate-all(automate for all routers)
automate-<connectedrouter>; per default the connected router has name
flowdirectorbut that can be changed)
Automatic Flow Restart
To ensure that a flow handles temporary failures such as connection loss to a database or messaging system, add tag
restart to the flow. When a failure happens, the flow is stopped and repeatedly restarted after one minute until the failure condition disappears.
When a Git
pull is performed (automatically or manually), all flows and dashboards are selected that have
automate set. Flows that have not yet been activated are deployed and activated.
pull produces a list of diffs. It is determined which flows and dashboards are affected, and those with
automate are updated.
When a router becomes available, all flows and dashboards are selected with either
automate-all and are deployed/activated resp. updated if they are already activated and are affected by the diffs from the last Git
Example: Web API Demo App
A dashboard can be tagged with
default and it is automatically displayed when the user logs into the app.
For example, the Web API Demo app displays a Shell Terminal as default:
When the user logs into Web API Demo, it is displayed: