Ways to stop recording
User activity monitoring rules provide the following ways to control the start and stop of recording:
•The recording start condition, according to which the DeviceLock Service can start recording only if this condition evaluates to true.
The part of the recording start condition that includes only the system state criteria, referred to as the recording run condition, is also used to control when to stop recording. If the recording run condition evaluates to false, the recording stops.
Consider, for example, the following recording start condition:
Window “<title>” exists AND Content-Aware rule “<name>” is triggered
The recording run condition in this case is
Window “<title>” exists. It does not include
Content-Aware rule “<name>” is triggered as this is an event criterion rather than a system state one. For details on the two types of triggering criteria, see
System state criteria vs. event criteria.
•The Force stop capture setting causes the DeviceLock Service to stop recording once the specified time has expired, regardless of the recording run condition.
•The Do not run this rule again until its condition changes setting, according to which the DeviceLock Service does not restart recording, stopped after a specified time, until the value of the recording start condition changes to false and then back to true.
DeviceLock Service stops the recording of the user’s activity if:
•The recording run condition value has changed to false.
- OR -
•The time specified by the Force stop capture setting has expired.
This results in the following user activity monitoring rule features described:
•If the Force stop capture check box is not selected, the recording will continue as long as the recording run condition value is true. Suppose, for example, the recording start condition contains only the default criterion - User logged in, and the Force stop capture check box is not selected. In this case, the recording will continue until the user logs off.
•If the recording start condition contains only event criteria in addition to the default one, and the Force stop capture check box is not selected, then recording will start upon occurrence of the specified events and continue until the user logs off. In this case, for the recording to stop after a certain time, one should select the Force stop capture check box.
•If the Force stop capture check box is selected, the recording will stop when the time specified by this setting expires, even if the recording run condition value is true. In this case, the rule with the default recording start condition will stop the recording after the specified time, and then start the recording again as long as the user remains logged on. For the recording not to restart, one should select the Do not run this rule again until its condition changes check box. With this check box selected, the recording will not restart until the user logs off and then logs on again.
How the recording run condition is calculated
The recording run condition governs the end of the recording session. The recording stops when the value of this condition changes to false. At the beginning of the session, this value equals to the value of the recording start condition. During the session, this is the value of the logical expression representing the recording start condition in which the values of the event criteria are frozen as of the time that the recording started. The recording run condition is calculated by passing into that expression the current values of the system state criteria held in the recording start condition.
Formally, the value of the recording run condition is calculated as follows. Let’s denote the logical expression of the recording start condition by F(e, s) where e and s represent the current values of the event criteria and system state criteria, respectively. The recording run condition current value is the value of the logical expression F(e0, s) where e0 represents the values of the event criteria as of the time of the recording session start.