Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Each LCM state change triggers a notification to the user to notify about the state change.
  • When a cm handle Cm-Handle is registered it will be in 'ADVISED' state.
  • If the module sync watchdog operation starts to work on an 'ADVISED' Cm-Handle, the Cm-Handle state will transition to 'READY' or 'LOCKED' based on if the module-sync has succeeded or failed respectively.
  • If the module sync watchdog operation is successful, state and data-sync-enabled will be set to false by and the module-sync watchdogdata sync-state will be 'NONE_REQUESTED'.
  • If the user wants to enable set data-sync-  enabled to true, it has to enable it be enabled on its dedicated API endpoint.
  • Once data sync-enabled is set to true, the data sync-state will be set to 'UNSYNCHRONIZED'.
  • Only the handles with enabled an 'UNSYNCHRONIZED' data sync-sync state will be picked up by the data - sync watchdog operation.
  • If the handles are to be deleted during update then their states will be set to 'DELETING' before the deletion happens, then after it to 'DELETED'If the data-sync watchdog starts to work with on a cm Handle state transitions to 'READY' or 'LOCKED' whether data-sync succeeded or failed respectively.
  • If the data-sync watchdog was able to do complete the sync successfully then the dataStoreSync state will changed to SYNCHRONIZED.

Diagram of the possible transactions between CM-Handle states

...