Change events in the data model (modelevents)

Table of contents

Description

Events about changes to the data model (both embedded in the domain center and the product-design model created via design-API). These events are generated to subscribers and posted to the change history in KAFKA (if a connection is configured).

Class event subscriptions do not allow wildcards to be specified, and require explicit values of the event type and data class to be mandatory.

Sending an event to subscribers is differentiated by applying a filter and mask defined in the subscription properties. Each subscription filter is applied to the previous and new instances of the affected entity. An event is sent if the condition specified in the filter is met for any of them. Field masking is applied to the entity instance sent to the subscription channel.

The subscription filter can also contain conditions that are automatically generated based on the access policy configured for the class.

Example 1. Example of setting subscription properties

"events":["modelevents.data_changed"], "objects":["users"], "exargs":{"mask":"id,name", "filter":"…​"}

Table 1. System Characteristics

Class

modelevents

Domain type

master, worker

Destination types

kafka (class domain), wssubscr(*), plugins

Logical roles sources

mdc, dms

Events