...

.

Setting up the import module

...

<?xml version="1.0" encoding="UTF-8"?>
<moduleInstanceDescriptors 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/moduleInstanceDescriptors.xsd" 
version="1.0">
	<!--Import Module Instances-->
	<moduleInstanceDescriptor id="Import">
		<description>Import Our new data</description>
		<moduleId>TimeSeriesImportRun</moduleId>
	</moduleInstanceDescriptor>
</moduleInstanceDescriptors>

Step 3: Add the module to a workflow (ImportExternal 1.00D efault.xml)

In order to use the module (to be able to run it from the manual forecast dialog) you will need to list the module as an activity in a workflow. Assuming this workflow is already registered (see the Delft-Fews configuration manual on how to register workflow) the only thing to do is to add in to the workflow. IN In the following example the new module is the only activity in the workflow:

<?xml version="1.0" encoding="UTF-8"?>

...

<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">

...

	<activity>
		<runIndependent>true</runIndependent>

...

		<moduleInstanceId>Import</moduleInstanceId>

...

	</activity>

...

</workflow>

Set up Id Mapping

Step 4: Make the idmap file

...