Scense Administrator Guide

⌘K
  1. Home
  2. Docs
  3. Scense Administrator Guid...
  4. Error Handling
  5. Scense Error Object

Scense Error Object

Concept.

To identify an error Scense uses the Error object.
At the moment Scense starts the Error Recovery an Error object is created, named ‘LastError’, in which details of the last error are saved.
This error object is transmitted to the ‘Error’-mode within the Taskset.See: Error Mode…)

Layout.

The Error object is a collection of data describing the error, consisting of the following items:

    • TimeStamp
      The exact moment in time the error arose.
    • Source
      Source of the error (often the module in which the error was detected).
    • ProcedureName
      Name of the procedure in which the error was detected.
    • AdditionInformation
      Additional information. (Often a description of what the procedure was trying to do at the moment the error arose.)
    • Number
      Runtime error code.
    • Description
      Description of the runtime error code.
    • NativeNumber
      System error code.
    • NativeDescription
      Description of the system error code.

Use.

The Error object can be used in a Scripting Action.
In the scripting action the error can be evaluated, after which action could be taken.
An example of a script using the error object is shown below.

The script above writes the contents of the Error object in the Executive Log, but obviously you could do almost anything with the data from the error object.