Scopes are containers for Criteria. The Criteria are the important objects inside the Scopes.
A Criterion basically is a condition definition that produces either ‘True’ or ‘False’.
There can be unlimited Criteria in one Scope.
The Criteria collection is extensible. New Criteria can be added by Scense or the Administrator.
|All Criteria are evaluated at runtime on the workstation within the user’s security context.
This relieves the Scense server from doing all the work and allows better balancing of the workload.
Scense has several Criteria types already built-in and immediately available after setup.
Built-in Criteria are part of the Scense system and cannot be changed or removed. These criteria are compatible with previous and next versions.
Built-in criteria are optimized for speed and the runtime Scope checking algorithm is optimized to handle these Built-in Criteria.
There are several categories in which the Criteria are organized.
Besides the Built-in Criteria the administrator can define Criteria of his own.
The Criteria builder can be used to define and fine tune custom Criteria.
Custom Criteria are not supported by Scense and may not be compatible with future releases of the Scense software. See ‘Creating and Managing Custom Criteria’ for more information
How to use Criteria
Using Criteria is fairly easy. Navigate to the Scope page of a Scense Object and simply start adding them…
|Open the Scope property page of the Scense object you want to assign to a user or computer.
Initially the Scope may be empty and will look like the one on the right.
To add one or more Criteria the ‘Add’ button can be clicked.
After clicking the ‘Add’ button the Criteria Selector window will pop up.
|In the Criteria Selector all available Criteria are listed.
Select a Criterion by checking the checkbox in front of the Criterion name.
More than one Criterion can be selected at once and after clicking the ‘OK’ button all selected Criteria will be added to the Scope.
Double-clicking the name of a Criterion will select it and immediately close the Criterion Selector. This will increase productivity when there’s only one Criterion to be selected.
|Next the Criteria can be configured to match the requirements.
Each Criterion has the main configurable element ‘Condition’.
The Condition determines how the Criterion should be evaluated.
Most Criteria have 2 or more Conditions that offer a different angle on the Criterion.
E.g. Testing the user’s membership of an Active Directory group will always produce either ‘True’ or ‘False’. You are a member of the group or you are not a member of a group.
So, this Criterion has 2 Conditions.
|Other Criteria, like e.g. the ‘Check Variable’ has more Conditions because there are more possible outcomes when comparing values, and more ways to compare values.|
|So, this Criterion has 11 Conditions:|
|Configuring Criteria can be copied and pasted from and to Scopes (including Global scopes).
Once Criteria are pasted to a scope these changes are immediately persisted in the Scense database (this means; the property page will not roll-back the changes when clicking [Cancel]).
Only properly configured Criteria can be copied.