Nodes can be used to define a group node. A group node contains other group nodes or leafs
Since 2014.01. This element will enable that modifiers are shown and editable at groupNodes
by default nodes (parent node) are run at the server by selecting the run at server-button. By setting this option to true the workflow will run locally
Since 2015.01. Allow the user to make a temporary local run permanent and upload it to the server, commit the modifiers, approves the forecast and makes it
current.
if this option is enabled the run approved forecast button is also show for a local node
Child element in the topology structure. Workflows of child nodes are run locally
one or more parent nodes in the topology structure
It is possible to split the configuration of the topology in different files. The topology.xml is always the main configuration file. Parts of the topology (topology groups) can be configured in separate files. These topology groups are identified by a group id. This element can be used to configure which topology group should be injected.
Since 2019.02 It is possible to configure the background color for selected individual and group nodes on the Forecast panel.
Since 2019.02 It is possible to configure the background color for non-selected individual and group nodes on the Forecast panel.
Since 2019.02 It is possible to configure the text color for selected individual and group nodes on the Forecast panel.
Since 2019.02 It is possible to configure the text color for non-selected individual and group nodes on the Forecast panel.
Define the forecast length for a node. The forecast length is configured as a time span relative to T0. The user will be able to edit the forecast in the user interface (topology)
This option can be used to define a cardinal time step for the end time or forecast length of a node.
This option will determine the initial time of the end time by fitting the time to the cardinal time step
If this option is set to false the forecast length will be determined by the workflow
Define a relative period for this node. The workflow will run with a cold state equal to the start time of the node. The forecast length will be determined by calculating the difference between the end time and T0. The GUI will show a start time and an end time. This option can, for example, be used when the workflow only contains transformations.
Since 2017.02. The user can only determine the start time (cold state selection of the run). The forecast length will be determined by the workflow.
This option can be used to define a cardinal time step for the start time or state selection of a node.
This option will determine the initial time of the start time by fitting the time to the cardinal time step
This option can be used to define a cardinal time step for the end time or forecast length of a node.
This option will determine the initial time of the end time by fitting the time to the cardinal time step
With this option can be configured which initial state selection should be used by
default.
With this option can be configured that the run will start with a cold state equal to
the start of the previous run of the configured workflow
With this option a cold state can be configured with a fixed start date/time
Time window used to search for a warm state.
With this option can be configured which initial state selection should be used by
default.
With this option can be configured which initial state selection should be used by
default.
With this option can be configured which initial state selection should be used by
default.
Since 2023.01 The location id which provides the attributes in which the selected cold state will be stored
Since 2023.01 The modifier type id which will be used to store the pinned cold state
Since 2023.01 The location attribute (should be a date/time attribute) in which the selected cold state date/time will be stored
Since 2023.01 The location attribute (should be a date/time attribute) in which the selected cold state group will be stored
These properties can be referenced in workflow files and module config file with $key$, similar to global properties. These properties are overruling the global
properties and module properties.
The id of the workflow which is connected to this node. When configured in a parent node, this workflow will only be executed when running on the server. When running the parent node locally, the workflows of the child nodes will be executed.
If true, for the client type Computational Framework, the configuration is automatically reloaded after a successful run of the workflow.
Since 201801. This group defines several options for the (optional) secondary workflow
When no module instance ids are specified all module instances in the workflow are executed. Specifiying the module instances that should be executed only works
for local runs
Since 2019.02. If this option is set to true, an Approve checkbox will appear on the run options panel. With this checkbox the forecaster can determine if the forecast should be approved automatically after the run. The initial value of the check box is determined by the autoApprove setting of the workflowDescriptor. Note: the Approve check box will never appear if the approving of the forecast is not allowed ( allowApprove=false in workflowDescriptor). In this case also a Config.Error is logged.
This option can be used to set a prefixed time zero for a group or a single node. If this option is not configured the system time will be used as time zero.
By default the time zero of the shown in the IFD is non-editable. If this option is chosen the t0 is editable and is shifted with the configured timeZeroShift.
The id of the workflow from which the state is selected
This option can be used to define which cold state to use when no default run is available
Since 201801. The id of a secondary workflow which can be started from the IFD. Only the first configured workflow id will be used in the OC or SA. Additional worfklows will only be available in the WebOC.
Since 201801. By default the secondary workflow will be a server run if the primary workflow also runs at the server
Since 2019.02 (And the EA branch). By default the secondary workflow will ignore the taskrun properties in the IFD and run with configured properties in the workflow. When this option is set to true the taskrun properties of the IFD will be used.
Since 2021.02 Defines when the secondary workflow button is enabled
Overview of supported export types
If this option is selected, the secondary workflow button will only be enabled if the main workflow has successfully ran at the server.
Specifies that the forecaster notes, created for this node, should be always visible in the ForecasterNotesDisplay. By default, the ForecasteNotesDisplay shows the
notes for the the node (and its parent) that is selected by the user in the Topology GUI. This list of forecast notes can be extended with the notes that are created for the
node with option alwaysVisibleInForecasterNotes=true
optional element to define a zoomExtent. When a node with this element defined is selected the map will automatically zoom to this extent
The configured filter will automatically be selected when the node is selected in the topology.
displayGroupId references the id of a configured displayGroup element in the DisplayGroups.xml
Since 2019.01 The display id references the id of a configured display element in the DisplayGroups.xml
Since 2019.01 define the plot from which the display should be generated. The plot id and the location id define the display which should be displayed
Since 2024.01. Only used in the WebOC! The id of the data download display which is coupled to this node.
Since 2014.01. Reference to time series button panel that becomes visible when this topology node is activated. For this functionality you need to configure the time
series button panel in explorer.xml and to add timeSeriesButtonsPanels.xml in the display config files..
Since 2018.02 show a custom text in the IFD. It is allowed to use attributes in the text
Since 2018.02 if a date time attribute is unmodified it is possible to overrule the default (unmodified value) with a calculated time
Since 2018.02 if a node has a custom info label defined then the defined text will be shown below the time zero in the IFD run options section. It is allowed to use attributes in the custom info label.
Since 2016.02 show a textbox in which the user can enter a description for the workflow
Since 2016.01 Disable the run edit options button when this node or one of its children is selected
Since 2015.02 hide the overview panel when this node or one its children is selected.
This element can be used to group this node and it children to the area
With this option a node can be set to readonly. Which means that modifiers can be viewed, but not created, editted or deleted.
set a permission to control who can view this node
Permission to run the workflow for a node locally
Permission to run the workflow for a node at the server
Since 201801. Permission to run the secondary workflow
Optional element to define a default modifier for a node. When a node is selected and a default modifier is defined the section in the modifiers display in which a
modifier can be created will automaticly initialize to the defined default modifier.
Since 2014.02. This element will enable that if a default modifier is configured that
only the default modifier an be editted
If this option is not configured, than all applicable modifiers can be used. With this option it is possible to restrict which modifier groups can be used
Since 2018.02 Restriction for the locations whose attributes should be modified. If ommitted attributes of all locations associated with this node can be modified
If ths element is not defined only the runs from which the T0 is equal to the system time are used to define show the icons in the topology panel. However with a
grace time configured also runs which fall within the period T0 - grace time are used
If this option is set to true a server run can only be started if the status of the previous run is fully successful
this option can be used to show a macro button which can be used to start a server task with a predefined taskproperties-xml
This options can be used to configure which display should be activated after selecting the topology node
this option can be used to configure which toolwindow should be activated or de-activated after selecting this node
Since 2016.01. Configure a URL related to the node. Can be used by the Web Browser Display to open the URL. For file based URLs the file:/// convention should be used.
Since 2017.01 If the node has a server run and the parent node has a more recent server run the status of the parent node will be used. If this is set to false, then the server run of the parent node will be ignored.
Since 2018.02 The forecast tree shows by default icons which show the run status of the workflow associated with the node.
The forecast tree however also has the possibility to show threshold related icons. This option can be used to configure for which threshold value sets icons should be showed.
Configure the ID of a scada display to open. Can be used by the Scada (SSD) Display to open a specific display when mainPanel is set to "schematic status display". The ID of a scada/SSD display if the same as the name of its config file (without the xml extension).
Configure the ID of a scada panel to open. Can be used by the Scada (SSD) Display to open a specific scada panel when mainPanel is set to "schematic status display". If no scada panel Id is configured, the first scada panel configured will be opened.
Since 2022.01. The message which will be shown when a server run is started from this node.
Since 2022.01. The message which will be shown when the leaves a node with uncommitted modifiers.
Optional element to define upstream connectivity between individual nodes.
Optional element to define downstream connectivity between individual nodes. The same connectivity can be achieved by having the downstream node defining a previous
node.
Optional element to associate one or more locations to the node. When a filter is associated as well, these locations are highlighted on the map and in the data
viewer.
Optional element to associate one or more locations to the node for use with the Tabular ConfigFiles Display.
by default workflows of child nodes will run locally. This can be overrules by this setting the localRun option to false
Allow the user to make a temporary local run permanent and upload it to the server, commit the modifiers, approves the forecast and makes it current.
if this option is enabled the run approved forecast button is also show for a local node
The id of the node. The id should always be unique!
The name of the node. When this option is not used the id of the node will be used as the name. The configured name will be shown in the topology tree.
Display can be specified using a key from the enumeration
Display can be specified using its display config file name
Since 2021.02, display can be specified using the name specified for an explorer task.
Since 2023.01, selection in grid display can be specified with group and plot ids.
Display config file name of the display that should be activated
Additional options , available only for specific displays. If a display does not support any additional options, then the possibly configured option are ignored
Addition options , available only for specific displays d
Id of a specific SystemMonitor tab to open. If no Id is configured, the logBrowser tab will be opened
Id of a specific SSD panel to open. If no Id is configured, the first SSD will be opened