...
- 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 below, for a full How To see: How To: configure <enabled> in Workflow based on location attributes
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<activity> <enabled locationId="CAP" attributeId="EXPORT"/> <moduleInstanceId>Export_CAP</moduleInstanceId> <description>Export CAP messages</description> </activity> </workflow> |
...
When using forecastingShellCount = n every underlying loop is split into n parts. Every FS instance is running the same specified activity but skipping the part of the ensemble loop / location loop that is meant for an other FS instance. It is not allowed to start a nested parallel when you are in a ensemble/location loop parallel. Since 2024.01 it is possible to use a global property for the forecastingShellCount instead of a integer. This property may not reference a task property / whatif / modifier. The scheduling info will only be updated after a new config revision.
| Info | ||
|---|---|---|
| ||
Before 2019.02 if an existing scheduled workflow is redefined as a parallel workflow, it needs to be rescheduled to prevent errors. In the worst case situation the MC may become unavailable. |
...