Scense Task Structure
A Taskset is the most important object within the Scense runtime system.
A Taskset is a kind of folder in which a Scense task structure of related tasks is saved in the form of ‘Session Events’.
Conditions and time restrictions can be linked to a task set. These conditions and restrictions are preset for lower levels.
Every task the Scense Client software executes is part of a Taskset.
Assignment.
A Taskset will only be executed if it’s assigned through a Scope (see Scopes), a Script (see Scripts) or a direct invoke through a TaskSet Action.
If a TaskSet is not assigned in any way it will never be executed unless it is invoked from an external system using the Symbolic Name.
Runtime status.
A Taskset is assigned a certain ‘Runtime status’ that determines how the runtime system handles the Taskset.
The status can have the following values:
- Alternate
Only one Taskset can be assigned the ‘Alternate’ status, and will therefore be called the ‘Alternate Taskset’. This alternate Taskset plays an important role in certain ‘RunModes’ (see RunMode and Advanced task structures…). - Functions
Only one Taskset can be assigned the ‘Functions’ status. This is the Taskset that serves as the Script Container. This Taskset holds two Session Events: - Function Scripts
This Session Event holds all Scripting Actions that can be called as a function by a ‘Function variable’ - Action Templates
This Session Event holds all scripting Actions that can be copied to other Session Events in other Tasksets through the ‘right-click’ context menu ‘New’
This ScriptContainer Taskset is essential when using ‘Function Variables’ (see Query Variables…). And Custom Actions
- Final, Approval and Test
Defines the TaskSet’s context. In other words, these statuses are used to define whether a Taskset is applied in a Test, Approval or Final context. The ‘context’ of a Taskset consists of network locations etc. - Block All and Block Application
The administrator can block a Taskset. There are two types of blocks: ‘Block All’ and ‘Block Application’.
Block All will block all Session Events, while Block Application only blocks ‘non passive’ Session Events. (See Session Events…). - Disabled
A Taskset can be removed from the runtime system by assigning it the status ‘Disabled’. A Taskset with status ‘Disabled’ will never be executed by the Scense Client software.
Runtime level.
A Taskset can be assigned a Level. The default level is ‘User’.
The Taskset level could also be ‘System’.
The Taskset level determines the rank of a Taskset in the sequence of execution of a script.
On a Windows server it is only possible to execute TaskSets with ‘system’ level, with the exception of the Terminal Server. Scense primarily considers the Terminal Server as a workstation where multiple users can simultaneously be logged on to, all using their ‘own’ Scense Client.
Symbolic Name.
A Taskset can be assigned a symbolic name which can be used for invoking a specific Taskset from an external system using the Scense.exe command line.
This way a Taskset can be invoked by name rather than by GUID.
The symbolic name is unique in the Scense system.
This example shows how an external system can install Scense Explorer using the Scense system.
First the Scense Explorer Taskset should be given a Symbolic Name
Next we can define the command line to be used in the external system
To start a named Taskset using the command line we need to execute Scense.exe.
Scense.exe is located in the %SystemRoot%\System32 folder on 32-bit systems, and in %SystemRoot%\SysWOW64 on 64-bit systems.
The syntax:
Scense.exe [scense server],Taskset,{symbolic name},
{session event name},[parameters]
Scense server and parameters are optional.
To start the install event of Scense Explorer the command line would be this:
Scense ,Taskset,ScenseExplorer,Application Install Actions,
This command line can be tested in a CMD box.
Now it is ready to be executed
Place the tested command in the appropriate location in the external system.
A named Taskset can also be started using the ‘ExecuteTaskSet’ command in the ScenseExecute syntax in scripting actions. (see the Scense Embedded Scripting Guide)