Version Control Overwriting

Zoom Window Out
Larger Text | Smaller Text
Hide Page Header
Show Expanding Text
Printable Version
Send Mail Feedback
Save Permalink URL

Navigation: Office Suite Integration > TeamConnect Outlook > TeamConnect Outlook Documents and Emails > Moving Documents > Overwriting Documents

Version Control Overwriting Details

Scroll Prev Top Next More

Versioning of documents and email messages is improved in Office Suite 2.0.

Users are able to drag-and-drop new files onto an existing target file.

These are the following scenarios users may encounter when versioning documents:

Action	Target	Result
Dropping a file from an email onto an existing file within the TC plug-in (see below)	File of same type (.eml or .msg for emails) that is not checked out	Pop-up window requests version comment. Save will version the targeted file and Cancel will cancel the versioning. Both choices close the new window.
Dropping a file from an email onto an existing file within the TC plug-in	File of a different type	Prompts a warning message that notifies you of extension mismatch. Click Yes to proceed with the versioning or No to cancel
Dropping a file from an email onto an existing file within the TC plug-in	File that is currently checked out	Prompts a message stating that you cannot version a checked out file. This message includes the name of the user who has checked out the document. Provides an option to save a copy with a unique added identifier (sample.doc -> sample(1).doc) instead.
Dropping one or more local documents into the plug-in directory	Hovering over individual file	Cannot upload or version
Dropping one or more local documents into the plug-in directory	Hovering over folder or subfolder	Uploads or begins versioning process as planned

Versioning Files

Dragging files directly from an email to a file in the document bank can provide direct versioning. The file will always take the name of the destination file in the document bank. Clicking the file in the document bank twice (not double-clicking it) will open up the version history. Users can also version a file with a document of a different extension.

For example, users can drag a .docx file to a .doc file for versioning. The file extension will still be .doc for TeamConnect or locally downloaded files, but this feature can allow users with legacy files better version control. Users can also version an entirely unrelated file type, such as adding a .pptx file over a .pdf. TeamConnect will attempt to open the file as a .pdf and locally downloaded versions of the .pptx.pdf file will have errors.