Scense Administrator Guide

  1. Home
  2. Docs
  3. Scense Administrator Guide
  4. Tasksets
  5. Session Event Concept

Session Event Concept

Specific task groups.

The Session Event allows further specification of the actions within a Taskset.

Within a Taskset, several Session Events can be defined.

The following Session Events can be specified:

  • Logon
    Used for actions that should be executed whenever a Taskset is being selected for execution within the Logon script. (See Scripts…)
  • Logoff
    Used for actions that should be executed whenever a Taskset is being selected for execution within the Logoff script. (See Scripts…)
  • Delayed
    Used for actions that should be executed whenever a Taskset is being selected for execution within the Delayed script. (See Scripts…)
  • Session Control
    Used for actions that should be executed whenever a Taskset is being selected for execution within the Session Control script. (See Scripts…)
  • Application
    Used for actions that should be executed whenever a Taskset is being selected for execution when the user clicks a shortcut.
  • OnDemand
    Used for actions that should be executed whenever a Taskset is being selected during the execution of the OnDemand script. (See Scripts…), or an OnDemand action.
  • Install
    Used for actions that should be executed whenever a Taskset is being selected during the execution of a shortcut, while the application has not been installed yet (See Application object…)
  • Web
    Used for actions that should be executed whenever a Taskset is being selected by a Web script. (See Scripts…)
  • Error
    Used for actions that should be executed whenever a Session Event causes errors.No condition can be linked to the Error mode, since the Error mode inherits its condition from the calling Session Event.
  • Setting
    Used for changing settings that should be active or not before the explorer of Windows is started. Used to lock-down the workstation or limit end-user privileges.
  • Functions
    Used for hosting all function scripts. This ‘event’ has no runtime trigger and should not be invoked using a ‘Taskset Action’.
  • Action Templates
    Used for hosting all scripting Actions that are upgraded to ‘Action Templates’. This ‘event’ has no runtime trigger and should not be invoked using a ‘Taskset Action’.
  • UserMode 1…n
    Used for actions that should be executed the instant the Taskset is being selected for execution in a specific modus, defined by the Scense administrator.

Using User Defined Session Events.

A ‘User Mode’ or ‘User Defined Mode’ is a Taskset that is not automatically linked to a script or event. Consequently, a UserMode has to be started deliberately by means of a ‘Taskset Action’ (See Actions…)

The use of User Modes makes it possible to re-define the ‘RunMode’ within such a Session Event. In this way complex situations can be mastered, by ‘programming’ with Session Events.

Differentiation in Operating Systems.

Normally a Session Event fits each of the supporting operating systems. But it is also possible to create several Session Events of the same type, each suitable for execution on a different operating system. For example, you could create two ‘Logon’ events, one of which fits all operating systems, while the other is especially made for Windows XP.

This functionality enables the execution of deviating actions in e.g. Windows XP, without changing the way in which a Taskset is invoked.

Selecting more than one operating system is also possible.