...
...
...
...
...
Tasks in PhixFlow perform various jobs, including, running analysis on streams, archiving, and clearing old managed file and performance log records.
Tasks are bundled into task plans and are configured to run in a specific order. Task plans can be requested by users, triggered by actions or schedule to run on a specific date and time.
For tasks that affects streams, you have a choice in how you structure the tasks.
Either each task affects one stream
Create a set of tasks, each one to operate on a single stream. Add the set of tasks to the task plan. In this case PhixFlow will process the tasks, and therefore the streams one by one, in order. It will wait for the previous task to complete, before starting the next.
For example, a task plan contains:
- TaskA for stream-a
- TaskB for stream-b
- TaskC for stream-c.
PhixFlow will process TaskA until it stream-a is finished, then TaskB until stream-b is finished, then TaskC until stream-c is finished.
This is the safest way to set up tasks that affect streams. Always use this method when there are dependencies between streams.
Or one task affects multiple streams
Add multiple streams to a task, then add the task to the task plan. In this case you have no control over the order in which streams will be processed.
For example, a task plan contains a single task. The task affects stream-a, stream-b and stream-c. PhixFlow will process all the streams at the same time.
Only use this method if there is you are sure there are no dependencies between the streams.
If a mandatory task fails, then the next task should not be started.
See Also
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
...
Tasks
A list of tasks in the task plan. To add a task, click 
and select the type of task you want to add; see Types of Task.
Schedule
This section only appears if the Scheduled box in Basic Settings is ticked.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Day of Week and Day of Month are mutually exclusive. One must be set to '?' (meaning no value specified), and the other defines the days that this Task Plan runs on.
...
Month element of the scheduled date/time, e.g. 1-12
Month can also be specified as short names e.g. JAN,OCT-DEC
...
Day of week element of the scheduled date/time, e.g. 1-7. The week starts on Sunday. So Sunday = 1, Monday = 2, etc.
Day of Week can also be specified as short names e.g. MON,WED-FRI
A day of week name or number followed by an 'L' means the last day of week in the month e.g. 'FRIL' means the last Friday, '2L' means the last Monday.
A day of week name or number followed by a hash ('#') and a number means the Nth day of week in the month e.g. '2#2' means the 2nd Monday in the month, 'FRI#5' means the 5th Friday in the month - if there is no 5th Friday in the month, that is equivalent to specifying no day of week.
If the '#' character is used, there can only be one expression in the day-of-week field, so "3#1,6#3" is not valid, since there are two expressions.
Day of Week and Day of Month are mutually exclusive. One must be set to '?' (meaning no value specified), and the other defines the days that this Task Plan runs on
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
This section contains the additional button 
- this will bring up the list of users in PhixFlow. Drags users into this list to add them as an email recipient.
Doing this will add the users with a blank notification rule, which means that the users will get an email every time this task plan runs. Edit the users in the list to update the notification rule, or add users manually using the 
button. For each user notification rule configure the following settings:
...
Choose one of:
- To
- Cc
- Bcc
...
An Expression which governs whether the recipient will receive the email generated by the Task Plan on completion. The internal variables _errors, _warnings, _messages and _suspended can be used in the User Notification Expression.
In particular, the _suspended variable can be used to send an email to a recipient only if a Task in the Task Plan failed - leading to the Task Plan being suspended. While a Task Plan is suspended, no further emails will be sent even if the Task Plan is scheduled to run.
...