dms.GetOsEvents

Retrieves OS events from enaio®. All input parameters are optional filters — if multiple are specified, they are combined with AND. Without filter parameters, all events are returned.

The return format is described under JSON structure, the complete field reference under Fields.

This job accesses the internal scripting infrastructure of enaio® directly. Incorrectly configured events can cause unexpected behavior or serious malfunctions on the client or server side.

1. Input Parameters

Name Type Required Description

ID

STRING

No

Filters by the database primary key (id) of the event

EventCode

STRING

No

Filters by the event type (event_code).
Complete value description: Event code list

OsClassName

STRING

No

Filters by the target object type (os_class_name): type_id as a string or "Application"

ObjectClass

STRING

No

Filters by the UI context (object_class).
Complete mapping: object_class — Mapping

AppClass

STRING

No

Filters by the target platform (app_class): 1 = Client · 2 = Server · 3 = WebClient

EventParams

STRING

No

Filters by the context parameter (os_event_params): field GUID, job name, or library name.
Complete mapping: os_event_params — Mapping

2. Output Parameters

Name Type Dependency Description

JSON

BYTE[]

—

JSON with the retrieved events. The parameter is transmitted at the protocol level as a BASE64/BYTE[] parameter; the payload is the raw UTF-8 JSON text. It is not a STRING parameter whose text content is additionally base64-encoded — after decoding the BIN-RPC layer, the client receives the UTF-8 bytes of the JSON directly.
Format: JSON structure

Count

INT

—

Number of events returned

3. Return Value

(INT): 0 = Job successful, otherwise error code
Complete list of error codes