Update Attributes and State with a Single API

this api enhancement enables developers to update both the state of an entity and its attributes in a single idempotent api call this is useful when both actions need to be performed in the same flow to ensure that they are validated together and handled atomically key benefits idempotency it ensures the same request can be made multiple times without causing unintended side effects atomic operations both state transition and attribute updates are processed as a single transaction simplified workflow reduces the number of api calls and validation steps for common use cases integrating single api in state transition and attribute updates when integrating, you will need to include both properties (for attribute updates) and the statetransition object (for state changes) in the request body if only one of these is needed, you can omit the statetransition or use the api as usual with just the properties field the system will validate both the state transition and attribute update together this ensures consistency and accuracy when performing both operations at once to update entity attributes and perform state transitions in a single call, pass the statetransition object along with the existing properties object in the api request body step 1 include a statetransition object in the request body in addition to the existing properties, you can now include a statetransition object in the request body json { "properties" { }, "statetransition" { "eventcode" "e 351", "reasoncode" "r 5334" } } eventcode code representing the state transition event reasoncode code representing the reason for the state transition sample request json put {{baseurl}}/entities/{{entitytype}}/{{entityinstanceid}} content type application/json { "properties" { "size" "large", "color" "blue" }, "statetransition" { "eventcode" "e 351", "reasoncode" "r 5334", } } the above request body explains the following properties the properties object contains the key value pairs of attributes that need to be updated for the entity instance this is the same behavior as the standard attribute update statetransition the statetransition object is new and allows you to specify details about the state transition this is an optional field, but when included, both the state transition and the properties will be validated and updated together statetransition object fields eventcode specifies the event associated with the state transition (e g , "e 351") reasoncode provides the reason or justification for the state transition (e g , "r 5334") event handling response events step 2 when the api is invoked with a statetransition object, the system will produce one of two events based on the outcome the two new events have been introduced to handle the result of this combined operation entityattributeandstateupdationsuccessevent this event is triggered when both the attribute update and state transition are successful entityattributeandstateupdationfailedevent this event is triggered if either the attribute update or the state transition fails both success and failure events will include two new fields smeventcode reflects the event code of the state transition smreasoncode reflects the reason code for the state transition json examples event response example success { "businesscommand" "platform\ coreos\ entityattributeandstateupdationsuccessevent", "entityname" "testtype", "entityinstanceid" "testtype 123456789", "data" { "eventcode" "e 351", "smeventcode" "e 351", "smreasoncode" "r 5334" }, "requestid" "request123", "tenantid" "tenantid123", "updatedat" "2024 10 15t08 00 00z" } event response example failure { "businesscommand" "platform\ coreos\ entityattributeandstateupdationfailedevent", "entityname" "testtype", "entityinstanceid" "testtype 123456789", "data" { "eventcode" "e 351", "failurereason" "invalid state transition", "smeventcode" "e 351", "smreasoncode" "r 5334" }, "requestid" "request123", "tenantid" "tenantid123", "updatedat" "2024 10 15t08 00 00z" }