Page History

...

The locationLoop also works in combination with "run for selected locations", this will only run for the locations that are in the locationSet AND selection

completed

...

(since 2021.01)

At the end of a sub-workflow the simulated time series for Mark one or multiple module instances can be made visible for other workflows and users with an Operator Client before the workflow completes successfully. This can be achieved by adding a "completed" element at the end of a sub-workflow. 

<completed>
	<moduleInstanceId>TRITON_WestSussex</moduleInstanceId>
</completed>

or 

<completed>
	<moduleInstanceIdPattern>TRITON_*</moduleInstanceIdPattern>
</completed>

This functionality is useful when a workflow consists of sub-workflows with activities that take long to run and that you want to see or use before the main workflow is completed.

It must be noted that the module instances as completed for the running workflow. The module instances become read-only for the rest of the workflow. When auto approve is configured for the workflow the simulated database time series becomes visible for other workflows and users before the complete workflow completes. The workflow can also continue on a different forecasting shell shells if needed.

See deleteTemporary if you want to transfer temporary data timeseries to the next partition forecasting shell.

...