Changes between Version 67 and Version 68 of BluePrint/Synchronisation

Timestamp:

05/17/10 07:21:35 (15 years ago)

Author:

Fran Boon

Comment:

--

BluePrint/Synchronisation

@@ -43 +43 @@
 
  * NB Most Users shouldn't need to be aware of sync at all
-  * a Big 'Sync Now' button should be all that is required for users with poor access to the Net or when they are requested to make an out-of-schedule sync.
+  * a Big 'Sync Now' button should be all that is required for users with poor access to the Net or when they are requested to make an out-of-schedule sync.  Pressing this button needs to return a normal status:
+   * Green for 'Completed w/o conflicts'
+   * Amber warning for 'Complete - Conflicts logged'
+   * Red error for any of the 3 trapped errors (Network problem, Authentication problem, Code crash), ideally distinguishing between them.
 
  * Sync Partners
@@ -70 +73 @@
    * Schedule
     * Since last date
-  * We need to be able to see if a sync has failed
-   * due to network problems
-   * due to permission problems
+  * Conflict storage
+   * New 'conflict' boolean column added to all syncable tables
+   * Hide this from all normal queries (like 'deleted')
+   * Modify UUID field to UUID_orig/sync_parter_id/version (or similar? Suggestions welcomed)
+  * Sync Log
+   * We need to view conflictsto launch conflict-resolution UI
+   * We need to be able to see if a sync has failed
+    * due to network problems
+    * due to permission problems
+    * due to code crash
   * We need to be able to retry failed syncs
    * Ideally continuing from where we left off, although having to redo that whole sync again is OK
@@ -92 +102 @@
 
  * UI to manually resolve conflicts which aren't covered by policy
+  * Displays both records side-by-side & allows selection of which version to base the result on & copying fields across from the other into it.
 
  * Sync Pools (Groups of Partners which share a common policy &/or username)