| Virtual Software Archives.Applications of type ‘Virtual Layer’ are usually associated with a Virtual Software Archive. Scense will store the information from these archives separately from the application objects. This will allow multiple applications to be associated with a single Virtual Software Archive. When Scense Explorer runs in ‘Expert Mode’, the option to manage the Virtual Software Archives will be available from the ‘Tools’ tab in the ribbon. |
 |
| Manage Virtual Layers.The ‘Manage Virtual Layers’ window lists all registered virtual layers and the associated applications and actions. Besides the overview, this window provides the option to remove the registration of unused packages. The ‘Manage Global Excludes’ button opens the edit-window for the global excludes definitions (See: Virtual Layer Excludes management) |
 |
Double clicking an entry in the list will open a new window that shows current connections to the selected package. This window will also allow you to relocate or rename a package.
The registered archives will be available to Virtual Layer actions. This makes it possible to configure virtual layer applications outside the application object, e.g. in another Taskset.
Virtual Layer Excludes Management
Virtual Layer Excludes.
When working with a virtual layer application, by default all documents the application creates will be stored within the layer. This is generally speaking an unwanted side-effect.
To prevent this from happening, the virtual layer excludes have been implemented.
Items to be excludes can be:
- Folders
- Folders and subfolders
- File extensions
Scense offers a ‘best practice’ solution to the ‘excludes situation’.
| Global Excludes. The globally defined excludes will be effective for all virtual layer applications within the Scense system. Unless the administrator specifically configured the application to ignore the global excludes. If a new virtual layer application, containing no excludes within the VSA-file, is introduced to the Scense system the most important excludes will already be in place. This will prevent the administrator and the users from losing their files somewhere within the layers. |
 |
| Application Level Excludes. The excludes defined at application level complement the globally defined excludes. The application excludes typically are file extensions used by the concerned application. The application’s exclusion list can be automatically generated at the moment the VSA-file is attached to the application object, or later on by clicking the ‘Construct’ button. |
 |
Apply Configuration
Conforming the Application configuration.
Windows Installer- and Virtual Layer applications support the ‘Apply Configuration’ operation.
This operation is automatically invoked by the Scense whenever the administrator has made changes to the configuration details of an application.
E.g. If a windows installer application has been modified to install an additional feature, Scense will automatically apply the configuration changes whenever a user for this application logs on to a workstation.
Also, if an administrator makes changes to the global- or application level excludes, all workstations will automatically receive the configuration changes at next logon from an application user.
In some cases however, the administrator might want to invoke the ‘Apply Configuration’ operation explicitly.
E.g. when two application objects use the same MSI-file, but have a different feature-set.
For this application, the administrator might always want to apply the configuration at user logon.
This will reconfigure the application for each specific use of both application definitions.