Dan’s Dev Corner March 2017

This month we were pleased to announce that we have added another connector to our robust collection – Microsoft OneDrive.  Included in this release of the connector there is full support for both reading and writing files and folders.  In addition to the connector itself, we enabled it within Echo to do all types of synchronization including bi-directional.  Since OneDrive is generally a personal cloud-based storage and sharing solution, we also have enabled Echo user sync in both the iManage and eDOCS client extensions.  This means that users can initiate and monitor synchronizing content to OneDrive, Box, NetDocuments, and many other systems directly from their daily work environment.

What are the differences between using OneDrive’s local sync application and SeeUnity Sync?

  • Users can sync documents and folders directly from their ECM’s native application interface.
  • Echo synchronization is a server-based process. It will continue to sync back and forth between OneDrive and your ECM system when you are not connected.  If you are away from the office for a while, updates to OneDrive documents will sync back and forth with your DM anyway.
  • System administrators have complete visibility and control over all of an organization’s sync rules. If there is a problem for whatever reason, IT will be able to see exactly what is wrong and fix it.
  • No additional client-side products are required so that user desktops can be more easily maintained.

We expect OneDrive synchronization to become a popular use case with our customers. We currently support user synchronization from within both eDOCS and iManage client extensions. This allows users to initiate document or folder level synchronization to their favorite file sharing and collaboration systems including, but not limited to, OneDrive, HighQ, Firmex, SharePoint, and Box.

Posted on: March 30, 2017