This bug is fixed in the next update to FileSite and DeskSite, which is currently in field test.   However, if you are plagued by this, there is a workaround for now.  It involves disabling the iManage Print Logging.  This means that if documents are printed, the Document History iManage will NOT be updated with a Print Activity.  This can affect firms that track printing for cost-recovery purposes.   But this will allow users to print an individual page of a Word 2010 document successfully.    So you probably save more money on saved paper than the cost-recovery of that one page you needed to print.

The workaround is adding three registry keys.  The keys below assume a 64-bit version of Windows 7:

[HKLM\Software\Wow6432Node\Interwoven\WorkSite\8.0\ Integration\Options]
“EnableWordPrintLogging”=dword:0
“EnableExcelPrintLogging”=dword:0
“EnablePowerPointPrintLogging”=dword:0

If enabling this workaround, remember to remove these keys after deploying and testing the next client version in order to re-enable print logging.

NOTE: Adobe Acrobat Reader X includes a feature called Protected Mode that limits an application’s access to registry and file systems. This feature is enabled by default. Because WorkSite Integration requires full access to the local machine, you must disable this feature.

The feature can be disabled from the General Preferences in Adobe Reader X, and should be included into your MST transform package.

Regarding Update 2, there are a handful of issues resolved, but one in particular stands out to me because I’ve already witnessed it.   From the Release Notes:

NT-26001: When dragging an e-mail to a WorkSite folder using Outlook 2010 with Cached Exchange Mode disabled, the user receives the following error; ‘Cannot move the items. The item cannot be moved. It was either already moved or deleted, or access was denied.’

This can easily be avoided on Windows 7 desktops simply by enabling Cached Mode (which is a good idea for a number of reasons that you should already know about, so I won’t get into them).  However on XenApp servers, where Cached Mode is not available, this can be an annoying bug.  The email does in fact get filed, but the error just isn’t pretty at all.   If you are planning an Office 2010 roll-out with iManage, this update is a must-have.

These are all well and good, but most firms have some third-party applications that provide advanced features sets.  There’s WorkShare Compare and pdfDocs CompareDocs to name a few that have direct integration with iManage; and most template packages include integration into iManage for automatic stylized document footers.    In these instances, you may want to hide or disable the iManage integration with native Office 2007/2010.

iManage 8.5 SP2 allows you to make these customizations through the modification of XML files on the client workstation, but you need the client customization documentation to do it.  No, I mean, you REALLY need the documentation in PDF form, because the XML files are attached to the iManage 8.5 SP2 Client Customization PDF.   The files are:  ExcelIntegrationCustomUI_20xx.xml, PowerPointIntegrationCustomUI_20xx.xml, and WordIntegratioCustomUI_20xx.xml, where 20xx is either 2007 or 2010.    Save the versions of the files you need, rename each appropriately and remove the “_20xx” from the name of the file (i.e., WordIntegrationCustomUI.xml).

Now that you have your files, create a %ProgramFiles%\Interwoven\WorkSite\IntegrationCustomUI folder and place your files within.    Edit the XML file in a text editor to remove the buttons/items as needed.  For example, to delete the Compare and Merge WorkSite Documents button in Word, delete (or comment out) the text highlighted in red below from the WordIntegrationCustomUI.xml file:

<group id=”WordWorkSiteMailMergeGroup2″ getLabel=”getLabel” getVisible=”getVisible”>
<button id=”WordWorkSiteMailMerge2″ getLabel=”getLabel” onAction=”OnActionWordButton” size=”large” image=”merge2_32″ getSupertip=”getSuperTip”/>
</group>
<group id=”WordWorkSiteReviewGroup2″ getLabel=”getLabel” getVisible=”getVisible”>
<button id=”WordWorkSiteCompareMergeDocuments2″ getLabel=”getLabel” onAction=”OnActionWordButton” size=”large” image=”compare32″ getSupertip=”getSuperTip”/>
</group>
<group id=”WorkSiteHelp” getLabel=”getLabel”>
<button id=”WordWorkSiteAbout” getLabel=”getLabel” onAction=”OnActionWordButton” size=”large” image=”about32″ getSupertip=”getSuperTip”/>
</group>

Save your file, close and re-launch Word, and that button is gone.  It works pretty well, and I don’t think too many customers even know that this is customizable.

What they may not have realized is that even though the Advanced Find option is listed under the new Instant Search menu, it is really the old iteration of Outlook searching.    There are a couple of workarounds, including copying the Advanced Find search results into a new subfolder, and then printing that folder in Table Style.  However, the best thing they can do is use the Instant Search bar of their mailbox itself.  The syntax of this search can include metadata criteria in addition to keywords, and when using Cached Mode with Windows 7, the search truly is instant.

Outlook 2007 Instant Search

The other nice feature is the suggestion to search All Mail Items if you aren’t happy with the results.    And printing in Table Style from these results works like a charm.

So what about Outlook 2010?  Is this still a bug?  No!  So did Microsoft fix it?  No!  Looks like they simply removed the File menu options in the Advanced Search dialog, so you can’t print from here.   They are sneaky like that…..   See for yourself:

Outlook 2010 - Advanced Find

In summary, for your email searching needs, you should advise your users to begin using the Instant Search feature.  The Advanced Find is dying a slow death.

There are a few caveats.  At this point, only 32-bit Office 2010 is supported.  No word yet on 64-bit support, but they say it’s coming.   You also need to be running the latest version, Worldox GX2, and you should contact Worldox support to download the updated integration files.

• WorkSite iManage 8.5: “We will look to certify/support Office 2010 within 90 days with the current 8.5 Worksite clients and later”
• Open Text eDOCS DM 5.3:  “We will release v5.3 beta this summer and the final release is scheduled to be launched in late September”
• Worldox GX2:  “Office 2010 integration files should ship within 30 – 45 days of the official general release of Microsoft Office 2010″
• Microsoft SharePoint 2010:  “Come on, we’re Microsoft.  It’ll work day one!” (Disclaimer: NOT a real quote)

So as of right now, it looks like Worldox may win the horserace to support Office 2010.  As soon as official release announcements are made, we will be sure to test functionality in our research lab.  Of course, simply supporting integration with the application doesn’t mean that the DMS product will be able to leverage any of the extra features of Office 2010, such as the Backstage view or simultaneous editing (which requires the document live on SharePoint 2010).

Below are some screen shots of what you’ll see if you try to simultaneously edit a document in SharePoint 2010:

Word

Word will only let multiple people edit a document at the same time if you’re using the full client.  In the Word 2010 web app, the second person will get this error:

PowerPoint

PowerPoint will only let multiple people edit a presentation at the same time if you’re using the full client.  In the PowerPoint 2010 web app, the second person will get this error:

Excel

The Excel 2010 web app is the most advanced web application and allows multiple users to edit a spreadsheet at the same time.  Other users will see changes as they are made by someone.  If two users try to edit a cell at the same time, then the second edit will be the one that saves.

The Excel web app is shown in the screen shot below.

In the bottom-right, the web app tells you how many users are currently editing the spreadsheet.

Surprisingly, the Excel desktop client cannot participate in simultaneous editing.  This collaboration feature is only available from the web app.

OneNote

The OneNote web app does allow simultaneous editing, however edits should be limited to separate pages.  As long as users are working on separate pages, they will see updates that someone else made when clicking on the page.  When we tried to edit the same page between several users however, we were presented with “conflicting changes” errors as shown below, with the only option being to delete the page.

The simultaneous editing features in Office 2010 open up a lot of possibilities for collaboration, however it’s disappointing that only Excel can fully utilize it in the web application.  Our hope is that the next version of Office will fully support multi editing in both the web apps and the client versions.

After installing the Office Web Apps, the first thing you’ll notice is a few new options when accessing the context menu of a document in SharePoint 2010.  The new options include View in Browser, Edit in Browser, and Edit in Microsoft Word.

SharePoint 2010 with Office Web Apps

Clicking on Edit in Microsoft Word will simply launch the version of Word that you have installed locally on your workstation.  But what if you don’t have Word installed?  What if you are on a hotel kiosk computer or a netbook?  In that case, you can click on Edit in Browser to access the Word 2010 Web App.  This will open the document for editing with your browser.  This is designed to work in IE, Firefox, and Safari; but will require the SilverLight plug-in to be installed for the best user experience.

The look and feel of the Word 2010 Web App is quite impressive.  There are navigation links across the top of the browser that can take you back to Client or Matter sites if you have those.  There is also the Office Ribbon Bar built right-in, and a link to launch the document with the locally installed Word client.    Tired of working with the current browser window?  Simply click the Pop-Out icon, highlighted in red in the upper right of the document, to open a new browser window without all the other browser toolbars cluttering the view.

Word 2010 Web App

Until Office 2010 is officially released, you will need to edit the document in the browser using the Word 2010 Web App if you want to take advantage of the simultaneous editing feature.    It will also be interesting to see which other features of the full Word 2010 product Microsoft incorporates into the Web App — Document Comparison?  Track Changes?    We’ll keep our ears to the wall.

Office 2010 brings this concept to Word, Excel and PowerPoint documents.  For a  preview of the look and feel, check out this Microsoft Office Word Team Blog post.

However, in the legal industry, the transition to allow simultaneous editing is not as simple as you may think.    Even after leading DMS products such as Open Text eDOCS DM, Autonomy iManage, or Worldox announce their compatibility with the Office 2010 platform, companies and firms won’t be able to just upgrade to 2010 and start editing documents simultaneously.   These systems are built on the idea of one person accessing a live document at a time — check it out of the system, work on it, check it back in.   So let’s assume developers did re-write their code.  Even that wouldn’t be enough for this functionality to work.  According to what we’ve heard from Microsoft, the simultaneous editing will likely require working in either a Microsoft-hosted cloud, or having SharePoint 2010 on the back-end.    This doesn’t mean that a migration from a DMS product to SharePoint is necessary, but it could mean that the DMS vendors would have to support a SharePoint document repository.  Open Text has already hinted that their releases in latter half of 2010 may support this.

As an aside, the whole idea of checking-out and checking-in documents has been ingrained into the minds of all attorneys, paralegals and administrative assistants for more than 20 years.   It won’t be easy to shake, and it might not even be accepted in the legal vertical.   Anyone know of any attorneys out there interested in this feature?