...
| Code Block | ||
|---|---|---|
| ||
<workflow xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews
http://fews.wldelft.nl/schemas/version1.0/workflow.xsd" version="1.1">
<parallel>
<activity logStartedAsDebug="true" logFinishedAsDebug="true">
<runIndependent>false</runIndependent>
<moduleInstanceId>RTCTools_KOT_Check_$RUNTYPE$</moduleInstanceId>
<moduleConfigFileName>RTCTools_Check_Qinc_Fx</moduleConfigFileName>
</activity>
<activity logStartedAsDebug="true" logFinishedAsDebug="true">
<runIndependent>false</runIndependent>
<moduleInstanceId>RTCTools_KOT_Check_$RUNTYPE$</moduleInstanceId>
<moduleConfigFileName>RTCTools_Check_QO_Seed</moduleConfigFileName>
</activity>
<activity logStartedAsDebug="true" logFinishedAsDebug="true">
<runIndependent>false</runIndependent>
<moduleInstanceId>RTCTools_KOT_Check_$RUNTYPE$</moduleInstanceId>
<moduleConfigFileName>RTCTools_Check_FB</moduleConfigFileName>
</activity>
</parallel>
</workflow> |
loopLocationSetId
For a workflow, a location-loop can be defined in which each location (site) in a location set is run separately. The $LOOP_LOCATION_ID$ tag in the configuration can be used to point to the corresponding locationID of the current location. This is useful in combination with (related location) Constraints, because then it is possible to filter a locationSet on the basis of the $LOOP_LOCATION_ID$.
...