-
Story
-
Resolution: Done
-
Medium
-
None
Currently an exception is thrown when a CM Handle that already has been module -synchronized attempt to (module)synchronize again!
The root cause is something like schemaset already exists. The sync process needs to be modified to allow this. e.g. by overwriting the previous schemaset (and reusing its ID) or delete the old schemaset before attempting to insert the new schemaset
- Consider
- only schemaset already created but anchor wasn't
- Event handling (not implemented)
- event should be the same for this
Resolution
- Reset the stat to 'Advised'
- Normal module-sync process should delete schemaset if it already exists
- Normal module-sync process should anchor can/should be re-used, make use its DB id when linking to new schemaset already
A/C
- Demo change the state of a cm-hande in registry to Advised and show using logs and DB GUI that re-sync was completed