Laserfiche WebLink
<br />Page 43 of 58 <br /> <br />a. Date and time of the conflict. <br />b. Object name involved in the conflict. <br />c. Resolution method applied (manual or <br />automatic). <br />d. Error details, if any, encountered during <br />synchronization. <br />Store in a configurable location. R <br />The logs must be formatted in a structured format <br />(e.g., JSON or CSV) for easy analysis and integration <br />with external reporting tools. <br />R <br /> <br />Support the following automatic conflict resolution <br />strategies: <br />a. New Object Wins: always retain the object <br />with the most recent timestamp. <br />b. Source Always Wins: always prioritize the <br />source object in conflicts. <br />c. Destination Always Wins: always retain the <br />destination object in conflicts. <br />d. Always Skip Conflicts: retain neither object, <br />and skip processing the conflict. <br />R <br /> <br />If a conflict cannot be resolved using the selected <br />method, the system must: <br />a. Log the unresolved conflict with an <br />appropriate error message. <br />b. Notify the user of the unresolved conflict. <br />R <br /> <br />Users must be presented with a side-by-side <br />comparison of conflicting objects, including <br />metadata, such as timestamps, names, and content <br />preview. <br />D <br /> <br />Users must be able to approve or defer resolution for <br />individual conflicts. D <br />Allow administrators to configure the default <br />resolution strategy for automated processes. D <br />Provide an option to clear or archive old logs to <br />manage storage. D