Unify and manage your data

Events configuration

Learn about the events configuration section of the Subscriptions API.

The Subscriptions configuration includes the eventsConfiguration section where you can specify which event type should be processed on the DT.

Each event type can be set to one of the following two values:
  1. Ignore - No action will be taken for the event
  2. Activate - The event should be processed when it's triggered.

The following events are triggered in the DT that are monitored by the DTSS application service:
  • entityCreated
  • entityModified
  • entityDeleted
  • entityMerged
  • entityUnmerged
  • entityMatch
  • relationCreated
  • relationModified
  • relationDeleted
  • entityCrosswalkDeleted
  • relationCrosswalkDeleted
These events that can be processed by DTSS when something changes in the DT are categorized into three groups:
  1. When entities are created, modified, deleted, merged, unmerged or a match is triggered in the DT (the first six mentioned above).
  2. When relations are created, modified, or deleted in the DT (seven, eight and nine from the list above).
  3. When crosswalks on an entity or relation are updated or deleted (the last two mentioned above).
The handling of events for deleted crosswalks is different from entities or relations. There are three options when a DT crosswalk is deleted:
  • Ignore - make no change to the CT.
  • Delete - Delete the corresponding crosswalk in the CT, this also deletes any attributes associated with that crosswalk in the CT. This is equivalent to a hard delete of the DT values from the CT.
  • Set end date - Set the CT end date on the crosswalk from the DT. The DT attribute values will be present in the CT, but they will not be available to participate in the survivorship rule evaluation. So they will never become the operational value. This is equivalent to a soft delete of the DT values from the CT.

These options can be set individually for each source on the customer tenant. If the source is not specified, the value in the default action in CT will be used.

If the event type is not defined in the subscription, a default value is applied as shown here. The default depends on the event type. So note that if you don't specify anything in the event type selection, these default values are applied.