Page History

Anchor
_Toc154574497 _Toc154574497

Anchor
_Toc95297330 _Toc95297330

Setting up event-action configurations

...

Example of Action Config to resume a suspended task

<?xml version="1.0" encoding="UTF-8"?>
<actionxml type="task">
	<enhance>
		<tag name="AIRE_FORECAST"/>
		<resume/>
	</enhance>
</actionxml>

Example of Action Config to suspend a task

<?xml version="1.0" encoding="UTF-8"?>
<actionxml type="task">
	<enhance>
		<tag name="AIRE_FORECAST"/>
		<suspend/>
	</enhance>
</actionxml>

Example of Action Config to enhance a task

<?xml version="1.0" encoding="UTF-8"?>
<actionxml type="task">
	<enhance>
		<tag name="EDEN_FORECAST"/>
		<repeatinterval interval="3600"/>
	</enhance>
</actionxml>

Example of Action Config to run one instance of a task

<?xml version="1.0" encoding="UTF-8"?>
<actionxml type="task">
	<oneoff>
		<cardinaltime interval="900" reference="2004-01-01T00:00:00.000+00:00"/>
		<tag name="EXPORT_CURRENT"/>
	</oneoff>
</actionxml>

Note: a one off task requires a cardinal time step and a reference time to establish a correct T0 for the run. The cardinal time step is important as it also controls how often the master controller will run an instance of the task if triggered by and an event (it will only run once every cardinal timestep, even though there are multiple events in that period); it is recommended to set this to 1 second if the action should be executed for every event code (e.g. in the case of sending alert messages). This can be increased if is not desirable to executed several workflows in a short period (e.g. the case of creating web reports). It also needs the "template task" with the relevant tag scheduled (in suspended mode) as a singe/one-off task.

...