Drag and Drop Replacement in Windows Web Folder Views
If a file is under version control, every replace operation creates a new version. Since the "replace contents" option is not available in the File Details view for a file unless it is checked out, the replace operation we are referring to here must be a drag and drop operation using a Windows Web Folder view.
Windows Explorer will confirm that you want to replace the file:
Macintosh Finder Warning
The above usage applies to Microsoft Windows users only. When using Macintosh webdavfs, clicking and dragging in Finder on a Macintosh to a webdavfs connection to TeamPage will delete the existing file's version history! Therefore, the autoversioning system is not useful for Macintosh users.
Autoversioning with Direct Editing in Microsoft Office Applications on Windows
Editing some Microsoft Office file types directly over WebDAV in Microsoft Office on Windows allows users to skip the explicit check out and check in operations, and still maintain a version history for version controlled files. (To learn how to edit files directly over WebDAV, please see Editing Microsoft Office Files from Windows with IE.
When you edit a version controlled Microsoft Office document directly in the associated application on Windows, check out and lock operations are performed on the file for you. One version will be created per editing session; an editing session is defined as the time from the initial lock to the time the document is closed (Microsoft Office locks for 3 minutes at a time, renewing the lock as many times as necessary). For example, suppose we directly edit this document:
This would cause Word to obtain a lock on this file in the name of your Windows user ID, which may or may not be the same as your TeamPage ID:
You can save the file as many times as you like; the file is not checked out until the first save operation is performed on the document. When that happens, as with a manual check out operation, TeamPage creates a working version that is used for all subsequent save operations during the session. The check out is done in the name of the correct TeamPage user ID:
The new version is created only when the document is closed, because this is when the lock is released and the session ends:
If no changes were saved during the editing session, no new version is created because no check out took place, and therefore no check in took place.
When the user's TeamPage ID is not the same as the user's Windows user ID, it might be difficult to tell which TeamPage user has locked the file. But the new finalized version will be associated with the correct TeamPage user ID because the check out is in the name of the TeamPage user ID. (The lock is associated with the Windows user ID because Word performs the operation by communicating directly with the WebDAV module, using the credentials it collects from Windows. The check out is in the name of the TeamPage user because it is performed by TeamPage using the credentials sent with the HTTP communications from Word.)
Attachments:
image270.gif
image271.gif
image266.gif
image267.gif
image268.gif
image269.gif
Article: Doc17 (permalink)
Date: March 22, 2008; 3:46:20 PM Eastern Daylight Time
Author Name: Documentation Importer
Author ID: importer
Date: March 22, 2008; 3:46:20 PM Eastern Daylight Time
Author Name: Documentation Importer
Author ID: importer