Following on from a previous blog where I discussed what happens when users move items around in their Virtual Vault, the question this time is what happens if users move whole folders around in their Virtual Vault. Again the change takes place during the next manual or automatic synchronisation of Virtual Vault, and in detail we see:
The Outlook Add-in gets a slot on the Enterprise Vault server:
11/11/2013 11:42:25.506[2036][H]: HDR: Requesting page: Slot.aspx?ArchiveID=1A14BEF784CF2D94F88B73CDCA138D7DF1110000evserver&TimeOut=0
And a request to get a synchronisation point so the Add-in knows where changes are processed up to:
11/11/2013 11:42:25.941[2036][H]: HDR: Requesting page: SyncPoint.aspx?Slot=3abe3887-2614-430e-9848-92711522fc4d&ArchiveID=1A14BEF784CF2D94F88B73CDCA138D7DF1110000evserver&SyncPoint=510&SiteID=16194C25939C8BC4D964B922428BFAB571d10000evserver
The hierarchy is obtained for the archive:
11/11/2013 11:42:25.973[2036][H]: HDR: Requesting page: GetArchiveFolderHierarchy.aspx?archiveId=1A14BEF784CF2D94F88B73CDCA138D7DF1110000evserver
And then the change is sent to the server:
11/11/2013 11:42:26.243[2036][M]: HDR: Posting XML: <?xml version='1.0' encoding='utf-8'?>
<UpdateArchiveFolderHierarchy Slot='3abe3887-2614-430e-9848-92711522fc4d' ArchiveId='1A14BEF784CF2D94F88B73CDCA138D7DF1110000evserver'>
<UpdateFolder pvid='1A9D0823237EECB42BE4C747DD32F5C221110000evserver' parentpvid='13620A33433638C43BCC73FEA2C45DB561110000evserver' icon='0' name='x1'/>
</UpdateArchiveFolderHierarchy>
