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.

We’ve just heard that there is at least one vendor whose product is now basically non-functional due to the code change.   This sort of problem can result in products needing to be completely re-engineered to work with the new XML limitations.

Organizations who have already implemented or are looking to implement Office 2007 should reach out to any third-party vendor who would be integrating with the Office 2007 XML format to determine compatibility with the new rules.  In addition, any custom code that has already been written would need to be tested and possibly re-written if any issues come up.

Kraft Kennedy has worked with numerous third-party vendors that integrate with Office 2007.  If you find yourself in a tough spot due to this issue, let us know and we can help walk you through the process of finding the right solution.

Today, Microsoft announced that they have released a patch which corrects the patent infringement, bringing the Office 2007 code under compliance:

The 2007 Microsoft Office OPK Master Kit Download, available on Microsoft’s OEM Partner Center, strips Word and other Office programs of custom XML editing capabilities.

“The following patch is required for the United States,” Microsoft said in a message on the site.

The 2007 Microsoft Office OPK Master Kit Download (12.9 MB) can be found at the Microsoft OEM Partner Center.  The site also says:

After this patch is installed, Word will no longer read the Custom XML elements contained within DOCX, DOCM, or XML files. These files will continue to open, but any Custom XML elements will be removed. The ability to handle custom XML markup is typically used in association with automated server based processing of Word documents. Custom XML is not typically used by most end users of Word.

Pretty quick turnaround, but I have a feeling they were working on this for a while…