Page History

...

Boolean flag to indicate if the activity is considered to be independent of other activities in the workflows. If the flag is set to "false" (default) then the failure of this activity will cause the complete workflow being considered as having failed. No further activities will be carried out. If the flag is set to "true", then failure of an activity will not cause the workflow to fail. The next activity in the workflow will also be attempted. An indication is given to the user in the Forecast Management display if one or more workflow activities have failed.

enabled

This feature is added since FEWS The <enabled> element (since 2017.02 and ) can be used to in- or exclude an activity in a workflow run. This feature is based on a location attribute. If you configure a modifier for this, the forecaster can in- or exclude activities (modules or sub-workflows) from a workflow run from the OC. 

The enabled element contains a locationId and a location attributeId. The location attribute Id must be a boolean attribute that can be TRUE or FALSE. When the attribute value is TRUE 2 attributes:

• locationId
• attributeId, which is a BOOLEAN attribute for that location (i.e. TRUE or FALSE)
  • when TRUE:  the activity will be

...

• • included,
  • when

...

• • FALSE: the activity will not be included.

Example:

	<activity>
		<enabled locationId="CAP" attributeId="EXPORT"/>
		<moduleInstanceId>Export_CAP</moduleInstanceId>
		<description>Export CAP messages</description>
	</activity>
</workflow>

Enable

enable

The <enable> element (since 2024.01) can be used in- This feature is added in FEWS 2024.01 and allows to include or exclude an activity in a workflow, similar to the "enabled" feature<enabled> element. However in , this case the functionality element is not coupled to location attributes.  A , instead a boolean value is used, which can be set hardcoded as in the example below or defined through a global property in the file global.properties. 

	<activity>
        <enable>true</enable>
		<moduleInstanceId>Run_Model</moduleInstanceId>
	</activity>

...