CRUD observations

Crud observations are produced when a thing instance is created, updated or deleted. The observations are sent if:

• The resource is an instance of the core types AmtechM2mBridge or SmartTracker. The observation is sent to the topic /crud/<typeId> , ex. /crud/smartTracker, or /amtechM2mBridge/bridge1/crud
• The resource is contained inside a bridge instance (observation production, reasoners, actions, etc). They are sent to the same topic used for bridge crud, /crud/amtechM2mBridge/<bridgeInstanceId>, ex. /crud/amtechM2mBridge/bridge1
• The resource is a thing of a type configured to send crud observations in at least one activity
  • for creators, all activities he has created are analyzed
  • for followers, all activities he is subscribed to are analyzed

Notes :

• The resource must have a valid status (not draft), otherwise the crud is not sent
• The CRUD observations are sent to the topic /crud/<thingType> example "topic": "/crud/endCustomer"
• For things of type AmtechM2mBridge, the CRUD observation of a DELETE operation is not generated (for consistency with the logic that the deletion of a bridge deletes the topic /amtechM2mBridge where the crud observations for the bridge and its instances are)
• Crud observations are only sent if the value of a property changes
  • For properties of type collection such as the guest tenant or guest users, the content of the list is analyzed to determine if it changed. So an update of guest tenants [tenant1, tenant2] to [tenant2, tenant1] will not generate a crud observation.
• When creating things with a topology execution using a reasoner, are created via a PUT operation with the parameter createIfNotExist=true, so the crud observation generated will have the operation PUT