...
| No Format |
|---|
<?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> |
NoteNote1: a one off task requires a cardinal time step and a reference time to establish a correct T0 for the run. The new T0 will be the latest valid T0 for the specified cardinal time step. Suppose task is triggered at 11:59 GMT with a 3 hour cardinal timestep from midnight, T0 will become 09:00 GMT, when triggered at 12:00 GMT, T0 will become 12:00 GMT. 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 an event (it . It will only run once every cardinal timestep, even though there are multiple events in that period.
Note2: It is recommended to use taskTags and workflowIds no longer than 24 characters since that part of the workflowId is used for checking that a task has already been scheduled.
Note3: It ); it is recommended to set this the interval to 1 second if the action should be executed for every event code (e.g. in the case of sending alert messages). This can , but should be increased if it is not desirable to executed execute 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 singesingle/one-off task.
Related information on Event-codes
...