Difference between revisions of "CRUD observations"

Revision as of 15:12, 16 August 2018

Crud observations are produced when a thing type is created, updated or deleted

• The observations are sent if:
  • the thing type is configured as a crud producer in at least one activity
    • for creators, all activities he has created are analysed
    • for followers, all activities he is subscribed to are analysed
  • the thing instance has a valid status (not draft)
• The CRUD observations are sent to the topic /crud/<thingType> example "topic": "/crud/endCustomer"
  • Core types amtechM2mBridge and smartTracker always produce CRUD observations
• 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 change. If the same value is updated, the crud is not sent. For properties of type collection such as the guest tenant or guest users, the content of the list if 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
• When deleting multiple things at the same time via the platform UI, crud observations are not sent. They are only sent when deleting one resource at a time.