Welcome to Kraft Kennedy

In working with iManage 8.5 SP2 Update 2 and Update 2a, we’ve identified a bug when printing page ranges with Word, Excel and PowerPoint 2010.  The problem is that if a user goes to File –> Print, and chooses a Print Range (a single page, or “Pages 2-4”, for example), the ENTIRE document will print.  This is REALLY annoying (and wasteful) for documents that can have 100s of pages.

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.

Recently, Autonomy released the 8.5 SP2 Update 2 versions of iManage FileSite, DeskSite, OffSite, Email Management for FileSite, and Email Management for Outlook.   The key new feature is support of Adobe Acrobat Reader X.    However, due to a new feature of Reader X, a configuration change within the Reader application is needed.  From the Release Notes:

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.

iManage 8.5 SP2 clients come with some really great integrations into Office 2007/2010 out of the box.   As you probably know, Office 2007 introduced a pretty nice native document comparison function that makes small firms think twice about WorkShare Compare.   iManage provides the ability to use the native Office 2007/2010 document comparison engine for documents living in WorkSite.  It also allows the user to manually insert a WorkSite Footer into the document.

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.
Continue reading…

I was always amazed when attorneys first got Outlook 2007, they quickly uncovered that well known bug when trying to print search results from the Tools -> Instant Search -> Advanced Find feature in Table Style.   It’s almost as if they were trying their best to stump the product.

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.

In an announcement today, World Software Corporation — makers of the Worldox document management system — shared the news that their latest release now supports Office 2010.   According to my notes here, this makes them the first DMS vendor in the legal space to officially support integration with Office 2010.

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.

With Office 2010 being unleashed on the world, many customers are asking when their DMS products will support it.   No need to ask around, because we’ve gathered the official stances for some of the major vendors.

• 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).

Simultaneous editing for collaboration is one of the most hyped features in Office 2010, however it’s only supported over the web in the Excel 2010 web app.  For Word and PowerPoint simultaneous editing, you’ll need to have the full client versions of the Office 2010 products.  This will likely be a disappointment for people who were hoping to collaborate on documents from kiosks anywhere in the world.

Continue reading…

Continue reading…

One of the most anticipated new features of Microsoft’s upcoming Office 2010 release is the ability to perform simultaneous editing on documents – in other words, allowing two authors to work on a document at the same time.   Those of you who have used Microsoft Office OneNote 2007 are already familiar with the concept.   A OneNote 2007 file can be placed onto a network share, and multiple people can access the live version.   I’ve personally found OneNote’s co-authoring functionality an extremely valuable tool for note-taking during a group meeting or brainstorming business ideas.

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?