Framework Events
Purpose
This process describes how you can send create, update, and delete (CRUD) framework events from any entity service automatically created at runtime. The goal of this process is to show how you can create a generic Java Messaging Service (JMS) structure to send these operations using the JMS topic for framework events.
Process Flow
Entity services, which can send framework events, do not contain any application specific semantics. They only contain information about the object instance, type, and the old and new values of an attribute if it has been modified. Any arbitrary application should be able to subscribe to changes in entity services without any action performed by the application developer at design time.
To set generic eventing parameters that automatically notify an application using entity services that these objects have changed, see the following information:
2. Event Data Recording, which includes detailed information on:
¡ Notification Service Connection
3. JMS Deployment Descriptors in the CAF Runtime, which includes coding tips about the following Java classes:
¡ Structure of Class: ValueObjectChangedData
¡ Structure of Class: EntityChangedEvent
¡ Structure of Helper Class: EventHelper
Example
You can use this process to trigger TREX indexing and de-indexing processes automatically if an entity instance was created, updated or deleted. You can also offer the possibility for third-party applications, such as other SAP xApps, to react to changes or modifications made to entity services.