...
| Code Block | ||
|---|---|---|
| ||
<nodes id="exampleGroupNode">
<workflowId>workflowA</workflowId>
<enableAutoApprove>true</enableAutoApprove>
<node id="exampleChildNode">
<workflowId>workflowB</workflowId>
</node>
</nodes> |
TopologyGroup.xml
It is possible to split the configuration of the topology in separate configuration files.
The main configuration file is always the topology.xml. The other (supporting) configuration files are the topology group files. The topology group files should be placed in the RegionConfigfiles folder. The name of a topology group file should start with TopologyGroup.
An example of a topology group file is shown below.
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="utf-8"?>
<topologyGroup xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews https://fewsdocs.deltares.nl/schemas/version1.0/topologyGroup.xsd">
<group id="ForecastGroup_Bear">
<nodes id="Bear" name="Bear">
<workflowId>Bear_Forecast</workflowId>
<node id="MergeMAPBear" name="MergeMAP and Outflow">
<workflowId>Bear_Forecast</workflowId>
<moduleInstanceId>SetTimes_Forecast</moduleInstanceId>
<moduleInstanceId>MergeMAP_Bear_Forecast</moduleInstanceId>
<moduleInstanceId>Merge_RiverWare_Observed_QT</moduleInstanceId>
<visibleModifierGroup>None</visibleModifierGroup>
</node>
</nodes>
</group>
</topologyGroup>
|
The defined topology groups can be used in the topology.xml by using the element <groupId>. An example is shown below.
| Code Block | ||
|---|---|---|
| ||
<nodes id="InflowForecast" name="Inflow Forecast">
<warmState unit="day" multiplier="11"/>
<groupId>ForecastGroup_Bear</groupId>
|
Interaction with other displays
...