Data model change events (modelevents)

Contents

Description

Events about data model changes (both the domain center built-in model and the product-project model created via the design API). These events are generated for subscribers. Domain center built-in model events are also sent to KAFKA (if a connection is configured); dynamic model events are not sent to KAFKA — the class change stream to KAFKA is provided by the transactionlog storage mode (see Kafka and dynamic data model changes).

Subscription to class events does not allow wildcards and requires explicit event type and data class values. More about subscription, operations, and exargs parameters in the article Notification channels from the system.

Sending events to subscribers differs by applying the filter and mask specified in the subscription properties. Each subscription filter is applied to the previous and new instances of the affected entity. The event is sent if the filter condition holds for either of them. Field masking is applied to the entity instance sent to the subscription channel.

The subscription filter may also contain conditions generated automatically from the access policy configured for the class.

Example 1. Example subscription property specification

"events":["modelevents.data_changed"], "objects":["users"], "exargs":{"mask":"id,name", "filter":["==",["property","code"],"aaa"]}

Table 1. System characteristics

Class

modelevents

Domain type

master, worker

Destination types

kafka (class domain; domain center built-in model only), wssubscr(*), plugins

Source logical roles

mdc, dms

Events