Item level updation in one instance of data object in doe

[Former Member]

Dear Experts,

I am very confused with the updation and deletion scenario in doe.

what is process of the creation ,updation and deletion scenario in doe.

is it possible item level updation and deletion in doe if yes would you please explain the procedure.

Thanks & Regards,

-

---

Ashok Reddy Jalapu

Edited by: ashok reddy jalapu on Jan 11, 2011 12:17 PM

[Former Member]

Thank you very much for your reply.

[Former Member]

Hi Ashok,

Creation process in DOE is explained as below:

(if you create a header record on device it follows the following creation process, but if you create only a line item for an existing header record then it follows the update process mentioned after creation process).

=>When a device creates a data object instance(header) in its local store and does a synchronization,

this new record is first validated by the backend and then created in the backend. After that it is also created in CDS .

=>Once confirmation of validation and create is received by the DOE it sends a confirmation back to the device which initiated the "create".

=> The device then commits the creation permanently into its local data store.

=>If a rejection was received due to validation failure, then the device has to rollback the creation.

Updation process in DOE is explained as below:

=>When a device updates a data object instance(header or line item ) in its local store and does a synchronization,

then this change is not only communicated to the backend, but also validated

and confirmed by the backend.

=>In first step DOE receives the modification request and performs conflict detection to ensure that multiple devices are not causing an inconsistency by parallel updates of the same instance.

=>It then forwards the modification request to the backend which performs the validation and update of data.

=>Once confirmation of validation and update is received by the DOE it sends a confirmation back to the device which initiated the update.

=> The device then commits the update permanently into its local data store.

=>If a rejection was received due to conflict or validation failure, then the

device has to rollback the update.

=>In case the modification request leads to an update of backend data, DOE checks if the

Subscription state is modified and if it is needed then subscriptions will be recalculated so that other devices subscribed to the data object also receive the updated data object Instance.

Deletion process in DOE is explained as below:

(if you delete a header record on device it follows the following deletion process, but if you delete only a line item for an existing header record then it follows the update process mentioned above).

=>When a device deletes a data object instance(header) in its local store and does a synchronization,

this record deletion is first validated by the backend and then deleted from the backend. After that it is also deleted from CDS .

=>Once confirmation of validation and delete is received by the DOE it sends a confirmation back to the device which initiated the "delete".

=> The device then commits the deletion permanently into its local data store.

=>If a rejection was received due to validation failure, then the device has to rollback the deletion.

Regards

Shweta