I am a solutions engineer for Alfresco Software covering the northeastern United States. As such, I believe it is important to clearly communicate the many ways in which our enterprise content management platform can be used in the financial services industry, which is very prevalent in the northeast. Therefore, I have done some research on current customer use cases as well as potential use cases discovered from a few sources. Namely, the annual reports of some of the biggest banks in the world, and discussions with several colleagues internally and at some of our partner companies. One of those partners agreed to work with me to flesh out the bits and bytes to be able to demonstrate one of the use cases, and so of course I created a site in Alfresco’s cloud at http://my.alfresco.com and invited a few folks from the partner company to join and collaborate with me there. I uploaded the document in which I was collecting use case research, and another that included details of the design for the first use case.
And therein lies the problem.
Both of those documents were already in their own folder within our U.S. Solutions Engineering Share site in our on-premise deployment of Alfresco, because I’ve been collaborating with some of my colleagues on them as well. Now I’m collaborating with two different groups of people on the same documents, and I have to carefully manage updates in both directions. This is why I need Alfresco cloud sync.
Fortunately, Alfresco’s product management, engineering, quality assurance, and release management teams are inching ever closer to releasing this capability to the world, upon which time I will gladly begin to take advantage the automatic nature of Alfresco cloud sync. I’ll set up synchronization of the folder containing the two documents within our on-premise deployment of Alfresco with the document library of the site I created in the Alfresco cloud to collaborate with our partners. And forever after, I can collaborate on this project seamlessly both internally and externally while maintaining changes and versions from both places.
Seriously, how cool is that?