osevents
| The column list comes from the schema dump; the column meanings have been derived from the JSON returned by dms.GetOsEvents and the input parameters of dms.CreateOsEvent / dms.UpdateOsEvent. A few columns remain marked as uncertain. |
Holds the OS events defined in the enaio® application. One entry per event with the event
type (eventcode), the target object type (osclassname), the script code (vbcode) and
an optional context parameter (oseventparams). Meaning of the individual values, lifecycle
and the full format of the JSON representation: see
OS events in the DMS reference.
DMS API read path: dms.GetOsEvents; write paths: dms.CreateOsEvent / dms.UpdateOsEvent / dms.DeleteOsEvent.
1. Columns
| Name | Type | Length | Description |
|---|---|---|---|
|
|
— |
Primary key — corresponds to the field
|
|
|
— |
Event type — determines when the script is executed. Corresponds to the JSON field
|
|
|
100 |
Target object type — |
|
|
— |
UI context as a numeric representation ( |
|
|
— |
Numeric user ID — presumably the user who last edited the event (internal ID matching
the login name in |
|
|
— |
Target platform as a numeric representation ( |
|
|
max |
Executable script code of the event. Despite the column name, the content can be either
VBScript or JavaScript — see field |
|
|
100 |
Context parameter — content depends on the |
|
|
— |
Unix timestamp (seconds since |
|
|
255 |
Login name of the user who last edited (created or modified) the event. Corresponds to
the JSON field |
2. Related Tables
-
oseventcodes — lookup table of all known event codes with name,
objectclass(as text) andappclass(as text). -
oseventaccess — access permissions on events per user/group (
eventid→osevents.id).
3. Usage by Server API jobs
-
dms.GetOsEvents — reads events as JSON.
-
dms.CreateOsEvent — creates a new event.
-
dms.UpdateOsEvent — updates the script code of an event.
-
dms.DeleteOsEvent — deletes an event.