As mentioned before several Scense object types automatically come with an attached Scope.
These Scopes are created with the object, e.g. when creating a TaskSet, Scense will automatically create a Scope for this object.
This ‘local’ Scope can be edited in the property page of the TaskSet object.
Next to the ‘local’ Scopes the administrator can make use of ‘global’ Scopes.
Global Scopes can be very useful / powerful in many scenarios.
Global scopes can be created explicitly in the ‘scopes’ system folder, but they can also be derived from local scopes.
|Advanced Scope operations allow the administrator to promote, link, copy or demote Scopes.
These advanced options can be opened by clicking the ‘Advanced’ button on the Scope property page of any local Scope.
|The ‘Promote or Link’ dialog enables and disables functions based on the context.
If the object has its own ‘local’ Scope, the options to ‘Promote’ or ‘Link’ will be available.
If the object is attached to a ‘global’ Scope the options to ‘Link’ and ‘Disconnect’ will be available.
|After initiating an Advanced Scope operation this operation must first be either committed or cancelled.|
Promoting a local Scope
|An administrator might want to promote a local Scope to global because he has created a combination|
|of Criteria that he would like to use with other objects as well.|
|A new scope name can be typed which will be the name under which the new global scope will be saved. The newly created Scope can be found in the root of the Scopes system folder.
After the promotion, the Scope can no longer be edited in its previous ‘owner’.
After the promotion other objects can be linked to the newly promoted global Scope.
Linking to a global Scope
|Multiple Scense objects, like Applications, TaskSets and Printers can be linked to a single global Scope.|
|To accomplish this, the advanced Scope operations dialog should be opened from the target object’s Scope property page (e.g. an Application).
The administrator can then select the ‘Link’ option and browse for the appropriate global scope.
Once the object is linked to the global Scope, the previously attached local Scope is being deleted permanently.
|On a global Scope’s property page, the administrator can always see which objects are linked to it by clicking the ‘Scope Usage’ button.
Disconnecting a global Scope
A Scense Object (e.g. TaskSet) can be disconnected from a global Scope.
To disconnect from a global Scope, the advanced Scope operations dialog should be opened from the target object’s Scope property page (e.g. an Application).
The administrator can then select the ‘Disconnect’ option.
When disconnecting from a global Scope there are two options:
- Demote the global Scope
- Copy the global Scope to a new local Scope
- Detach the global Scope and create a new empty one and link the current object to it
Demoting a global scope is only possible if the ‘current’ Scense object is the only object linked to the global Scope.
- If a global Scope is demoted, it will actually become the local Scope of the ‘current’ Scense object and after the operation is completed, the scope will no longer be visible in the Scopes system folder.
- If a global Scope is copied to a new local Scope, then the ‘current’ Scense object will have a local Scope with exactly the same content as the global scope it was previously linked to.
- If a global Scope is detached, it will no longer use the global Scope and instead get its own empty local Scope. The result of this action might be that the object is no longer directly assigned to users.
Modifications to the global scope will no longer affect the ‘current’ object and the local Scope of the ‘current’ object can now be modified independently.