Kraft & Kennedy, Inc. provides technology and strategic consulting services to law firms, corporate legal departments and financial services firms. We can help you analyze, plan, implement and manage business and technology solutions to optimize your organization's functionality and processes.
| Brian Podolsky is a Senior Consultant in the New York office of Kraft & Kennedy, Inc. Brian joined Kraft Kennedy in 2004 after graduating from Stevens Institute of Technology with a B.E. degree in Computer Engineering. Brian drives Kraft Kennedy’s research on the latest ECM technologies and helps provide guidance and best practices for ECM implementations. He can be reached at podolsky@kraftkennedy.com. |
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.
After running into a couple issues with the iManage IDOL 8.5 SP1 release in our production environment, I was able to complete the index build using the 8.5 SP1 P1 release that was released last week. Our initial errors were found in our Content Engine logs referring to a lack of free disk space, even though we had successfully had our IDOL 8.5 (pre-SP1) index on the same volume earlier. In any case, I added some space and then recrawled using 8.5 SP1 P1. I’ve read some similar reports on user forums, so if you have a smaller volume for your IDOL indexer, just keep this in mind.
Continue reading…
As many of you may have heard, Autonomy officially released iManage 8.5 SP1 on Monday. This has been an eagerly awaited release for months now, and firms are looking to implement this pretty quickly. Here are the modules that have 8.5 SP1 releases thus far:
Our initial review is under the fold.
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.
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).
For those of you interested in running the iManage 8.5 IDOL Indexer, Autonomy recently released a new revision of the WorkSite Indexer Administrator’s Guide (8.5). It is available on the iManage support site, and includes an updated Chapter 6 on “WorkSite Indexer Maintenance.” The document goes into explicit detail on how to properly back up and restore an 8.5 IDOL index. (Note: you must exclude the entire WorkSite Index folder structure from normal backup agents, as this could corrupt the indices).
In summary, there are 3 types of items that need to be backed up, and then restored:
Security is always a concern in a law firm, and is especially important in the legal department of a corporation. Lawsuits sometimes include the company’s co-workers, competitors, or other sensitive information, where certain matter information needs to be completely hidden from all but a few matter assignees. Securing documents or DMS folders is often simply not enough protection.
Does the system hide the matter from appearing when doing a table look-up on a search form? Does it hide the matter when accessing the matter table via the DMS web module? For some cases, you want to hide the actual matter itself, so users won’t even know it exists.
Continue reading…
I recently performed an upgrade from iManage 8.2 to iManage 8.5 Update 4. Update 4 was released on January 14th and resolves several issues regarding service stability and wildcard searching. It adds support for the new WorkSite FileShare, iManage Workflow Manager, and iManage Digital Safe. I plan on blogging about these modules soon, so keep an eye out for that.
But the real reason for this post is that Update 4 sets the database schema version as 8.51 (all previous releases of 8.5 had set the schema version as 8.50). This value is listed as the MHVERNUM column in the MHGROUP.VERINFO table of the WorkSite database. For those of you looking to migrate from an environment with WorkSite Indexer 8.2 SP1 P2 (Verity), there is a compatibility problem with this change. Although Indexer 8.2 SP1 P2 was released in order to support iManage 8.5 servers for a transitional period, the 8.2 Indexer services fail to start when the database has been upgraded to the 8.5 Update 4 schema. Autonomy’s workaround for now is to modify the MHVERNUM value and set it to 8.50. This can be done by executing the following SQL query:
Continue reading…
A couple weeks ago I blogged about the XML patent infringement that Microsoft had to deal with. As mentioned in that post, they’ve released new code that removes some of the custom XML functionality that was built into the Office 2007 system, and brings them into patent compliance.
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.
(1)
(8)
(43)
(6)
(45)
(7)
0
Back to top
