The DataEvents<(Of <(<'TData>)>)> type exposes the following members.

Methods

  NameDescription
Public methodStatic memberFireExternalStoreChangeEvent
Fire the event that signals that data in an external store has changed.

Events

  NameDescription
Public eventStatic memberOnAfterAdd
This event is fired just after a data item has been added to the C1 CMS data store. See Add<(Of <<'(TData>)>>)(TData)
Public eventStatic memberOnAfterUpdate
This event is fired just after a data item has been updated in the C1 CMS data store. See Update<(Of <<'(TData>)>>)(TData)
Public eventStatic memberOnBeforeAdd
This event is fired just before a data item is added to the C1 CMS data store. See Add<(Of <<'(TData>)>>)(TData)
Public eventStatic memberOnBeforeUpdate
This event is fired just before a data item is updated in the C1 CMS data store. See Update<(Of <<'(TData>)>>)(TData)
Public eventStatic memberOnDeleted
This event is fired after a data item has been deleted from the C1 CMS data store. See Delete<(Of <<'(TData>)>>)(TData)
Public eventStatic memberOnNew
This event is fired just after a new data item is created. See New<(Of <<'(TData>)>>)()()()()
Public eventStatic memberOnStoreChanged
This event is fired after changes has happened to the C1 CMS data store. This may be atomic actions or a larger change to the underlying data store. The StoreEventArgs class describe the change in broad terms, including a flag indicating is detailed data event have been raised or not. You can use this event as a simple way to react to data changes (like clearing a cache) or you can mix this with atomic data events (add, delete, update) to make a build a more advanced cache. You should listen to this event in order to support scale out across multiple servers, since this event is meant to be signaled when changes happen on another server. In such situations detailed data events will not fire on other machines.

See Also