Filter
Top Products
First installation 62
No trigger settings defined
If you do not check any of the trigger settings, the task will not start
automatically, even when it has become due. The task can be run
manually only.
2.11 When will a task start?
First condition: Task is due
The first condition for a task to start, is that it is or becomes due. In other
words, a task will never start as long as it is not due.
The time that the task becomes due, is determined by defining the Q/A
schedule.
Therefore, in the Q/A Setup, select frequency, time and (if appropriate)
date you wish the task to become due.
Example:
Let us suppose today is Wednesday, and the Automatic I-Guard Check
task is scheduled weekly, on Thursday at 10 PM.
This means that tomorrow at 10 PM, the task will become due.
Will it also be executed at that time? That depends on the trigger settings.
Second condition: Trigger settings
Once a task is due, its execution depends on the Trigger settings.
In that way you can prevent that certain tasks would be executed while
the workstation is occupied by a user.
Some tasks require a user interaction or temporarily replace the image by
a test pattern. E.g., while the Measure Quality Level task is executed, the
displays on which the task runs, are completely dimmed, apart from a
white text being displayed.
In most cases, when you set up the task schedule, you cannot predict that
the workstation will always be free when the task becomes due. Suppose
that the Measure Quality Level task starts to run while a doctor is
examining medical images. In that case, the doctor would not be able to
continue viewing the images as long as the task is running.
To prevent situations like described above, you can set trigger settings.
By setting trigger settings, you can prevent tasks to be executed at the
time that they become due. They will be executed when they are due
AND a certain condition (trigger setting) is true.