It is possible to link conditions and time restrictions to a Session Event, replacing any presets at Taskset level.
The actual condition is determined at Session Event level.
This means that if the condition at Session Event level produces ‘True’, only actions having a RunMode ‘True Condition’ or ‘Any Condition’ will be selected for execution. If the condition on Taskset level produces ‘False’, only actions having a RunMode ‘False Condition’ or ‘Any Condition’ will be selected for execution.
This process is named ‘Defining the RunMode of a Taskset’, and is important for the execution of tasks by the Scense Client software.
In case the Taskset Status directly influences the execution of actions (Blocked, Disabled, or a time restriction), this status will have priority in the determination of the RunMode, instead of the conditions on Taskset level.
For example, when a Taskset has been ‘Disabled’, it will never be executed (except within Scense Explorer…)
In case a Taskset is ‘Blocked’, Scense will search for an action with RunMode ‘Blocked’ within the related Session Event.
If an action with RunMode ‘Blocked’ or ‘TimeRestricted’ is not found within the Session Event, Scense will search for actions within the corresponding Session Event of the Alternate Taskset.
In a ‘Blocked’ or ‘Time Restricted’ situation the user is usually sent an informational message.