Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


IconActionVisibleEnabled (not greyed out)Available since

Switches to IFD between read-only mode and edit-modewhen <enableAutoRun> is truealways
Starts the workflow of the node in IFD-mode (as local run, runs in the Operator Client)).always

when the node has <localRun> set to true, and
user has the permission to <runWorkflowLocallyPermission> (when this is configured)

promotes a local IFD run to a server run.alwayswhen the node has an IFD-run and when <saveLocalRunEnabled> is set to true.
starts a workflow in server mode.always

when the node has <localRun> set to false, or
<showRunApprovedForecastButton> is set to true

 starts the secondary workflow of the selected nodewhen a secondary workflow is configuredwhen a node with a secondary workflow is selected2018.01

If the button is selected the threshold icons will be shown instead

of the regular run status icons

by default, unless <hideThresholdsButton> is truealways2019.02

If this button is selected a modifier icon will be shown for a topology node if active modifiers are visible in the modifiers panel if that topology node is selected. This means that if you disable for a topology node that modifiers are visible in the modifiers panel that the modifier icon will also not be default, unless  <hideModifiersButton> is truealways2020.01


The philosophy: Local runs are used by the operator to interactively run a workflow on the operator client, check the results and potentially optimize a forecast by means of modifiers. Once the operator is satisfied with the forecast results, a server run is started and the results are sharedcan be shared between operators.  Local runs will not store any time series in the central Delft-FEWS database, only time series from server runs are stored in the central database

This is implemented as follows:

  • Local run results are only available in the local OC and are removed from the database when the application is closed.
  • Server run results (and the modifiers of this run) are stored in the central database and are available from any OC.
  • Local run results overrule server runsrun results on the operator client. Even when a server run is started after a local run. This means server run results won't be visible in displays.

The fact that local run results overrule server runs means run results mean that the server run results won't be visible in graphs or spatial display, even for the operator who started the server run.  As As this behavior is not always wanted, this can be changed with the topology chosen in the IFD. Below are two different approaches to this.



On the left right is a schematic diagrams of a topology with nested nodes, which we will use to describe a different use case.