HOME | WEBCAM | CONTACT
 

DM 5.3 Patch 4 is now available

November 8, 2011 by Matt Hotujec

On Nov. 2, Open Text released DM 5.3, Patch 4.  It contains over 40 fixed issues.  Among the highlights:

  • DM Viewer now works in Windows 7, 64-bit
  • SearchServer fixes to prevent index corruption, particularly when building a new index
  • Default format for new documents now configured at the workstation level rather than at the library level.  This means you can have workstations with Word 2003 default to saving in .doc format and Word 2007/2010 default to saving in .docx format.

After applying Patch 4, you must also manually run an update to the C++ runtime prior to running DM Server Manager.  You may also need to reboot your server after applying Patch 4.

eDOCS 5.3 Indexer Issue

October 7, 2011 by Brent Langford

We’ve been seeing some issues with 5.3 Indexes and wanted to share the resolution with everyone.

 The first issue is that sometimes profile metadata can be improperly indexed due to an Oracle Inside Out Viewer issue. This issue can result in an incomplete Results List when using a Hybrid search. The fix is included in 5.3P3 but you’ll need to Re-Index all your documents.

The second issue is that index compression can fail. One or more hot fixes are available for this issue but you’ll have to request them from support.

OpenText has been diligently working on fixes for these issues once they have been identified but you’ll still have to apply a patch and hot fix. If you’re on 5.3 you need to get your Index to P3 with the hot fixes.

EDV now supports Oracle!

June 21, 2011 by Sarah Salo
The wait for Oracle support is over!

 

It’s a bird! It’s a plane! Beneath the mild mannered spectacles and savvy suit, it’s there for the calling: Oracle Database Server for EDV!

 Want to know more? Contact us and we’ll jump in the nearest phonebooth…

 

 

 

 

 

 

 

 

Product Brief: iManage WorkSite FileShare

May 18, 2011 by ADV Guest

submitted by ADV Guest Blogger ~ Eli DeLosSantos, Partner Manager for Autonomy.

Work directly with WorkSite using Windows Explorer and non-integrated applications to Open and Save documents and Import files

iManage WorkSite FileShare is an application that provides access to WorkSite from a user’s desktop simply by mapping a network drive. FileShare enables WorkSite to be accessed like a network file server, allowing direct access from Windows Explorer and the standard Windows Open and Save dialogs used by most Windows applications.

This enables users to Open, Modify, and Save documents directly from applications that have no WorkSite integration, drag-and-drop files into and out of WorkSite using Windows Explorer, upload files from WorkSite directly into Web applications, and save files directly into WorkSite from Web applications. FileShare also facilitates working with linked files and provides a way for scanned content to be saved directly into WorkSite.

Work from a Familiar and Convenient User Interface

To access WorkSite FileShare, users simply map a network drive letter to the WorkSite FileShare Server. No client software installation is required on a user’s workstation. From Windows Explorer, all of the current Client Files, Matters, Engagements, and Projects that a user is working on are displayed as a folder. Users can navigate WorkSite in the same way folders can be accessed on a file server. Right clicking on a document enables a user to perform the same actions as they can on a document stored on any other drive such as Open, Copy, and Send. With little to no training, end users can access the “zero-footprint” client and begin contributing content without any change in how they work.

Get all the Benefits of WorkSite without any Change in Behavior

Users can continue to work from desktop applications in the same way they always have. The WorkSite FileShare server brokers all interaction with the WorkSite server. The WorkSite server continues to control the content, provide access, apply folder-based metadata, administer security, and maintain a comprehensive audit trail. FileShare combines the easiest to learn user interface with the peace-of-mind you get from knowing content is managed securely in WorkSite.

The simplicity of accessing content with FileShare encourages and reinforces the use of WorkSite. Even non-integrated applications can now manage content in WorkSite, enabling the complete client or matter file to be managed effectively.

The zero-footprint client also means less maintenance investment in patching and updating client images. WorkSite FileShare is a low total-cost of ownership option that allows users to incorporate good document management practices even for non-integrated client applications.

A World of Possibilities

WorkSite FileShare enables organizations to leverage WorkSite for applications that previously could not open or save content directly in WorkSite; and, WorkSite FileShare extends WorkSite’s reach to users that require fast access to content from anywhere on their desktop.

Customer Benefits

As firms invest in productivity applications, and enforce company policies regarding the management and retention of information, it is imperative that the integrity of client, matter, engagement, and project files is maintained with current and complete content. In addition, users need to be able to work efficiently and in familiar ways to be productive. WorkSite FileShare helps accomplish both simultaneously with benefits for both the firm and the business users.

Productivity, efficiency, and consistency

– Easy to use, familiar Network File Share interface

– Compatible with broader set of applications, end user roles, tasks

– Quickly able to import contents, even file hierarchies via drag and drop

Compliance

Content is less likely to be stored and lost on individual computers or file servers

Soft Cost Savings

– Reduced training investment, works like a standard file share

– Leverage common DMS infrastructure across more departments for more value  

 - Content imported into WorkSite via FileShare will have the appropriate security, auditing, versioning, and back-up strategies

Hard Cost Savings  

– No need to invest in custom, application-specific integration work

– Less time spent on client-side rollouts, coordination of client image updates

– Faster server-side maintenance for patches, updates

Please visit www.autonomy.com to find out more.

eDOCS 5.3 MSI Scripting Tips + Tricks

May 16, 2011 by Dave Kane

Since Open Text moved from using the “setup.exe” to a MSI file, things have gotten easier. However, customizing that MSI for individual installations still takes some work. Then there is the whole issue of deploying it out to your workstations. Make that them out to your workstations. There are separate MSI’s depending on if your workstation is 64 or 32 bit.

1. Find yourself a good editor. Open Text in their presentations have suggested Orca MSI editor. I’ve been using InstEd. I can’t compare the two because I haven’t used Orca, but I’ve been happy with InstEd.

2. Use Transforms. It is quicker and easier to create and edit Transforms. You can have different Transforms for different installations. Say you only want to install DM Imaging on certain machines, create a separate transform. You don’t mess with the original MSI distributed by Open Text and it keeps your command line a lot shorter.
Sample: msiexec.exe /i “%dmfiles%\eDOCS DM 5.3 Extensions (x86).msi” TRANSFORMS=”%dmfiles%\eDOCS53Transform86.mst” /qn /l*v “%TEMP%\DMInstall.log”

3. Testing for your processor. I write command files for doing the installation for our clients. If they have an automated way to distribute the installation, they can either pick what they like from the command file or use the command file to push the install. Because many of our clients are in a mixed environment with new machines being 64 bit and the old ones still being 32, we needed a good way to test which MSI to install. I borrowed this test from someone else because it works well.
IF /i .%PROCESSOR_ARCHITECTURE% == .x86 GOTO Install32Bit
IF /i .%PROCESSOR_ARCHITECTURE% == .AMD64 GOTO Install64Bit

4. We always had a separate step for applying the custom registry keys. Here is the other thing that is great about using transforms, you can import them directly into the transform. That way, MSIEXEC takes care of applying them for you. With InstEd, you simply right-click on a component and import your registry file.

Please feel free to share your own tips and tricks. Lord knows I’m still learning myself. What do you find useful?

iScrub: Metadata Management Software

April 29, 2011 by ADV Guest

submitted by ADV Guest Blogger ~ Susan McClellan, Marketing Manager for Esquire, Inc.

What is Metadata? Before determining how your business is going to manage metadata, it is important to understand some basic facts about document metadata.

Succinctly defined, metadata is “data about data.” Metadata is embedded in all Microsoft Office documents Microsoft Word, Excel and PowerPoint include automated features to aid in document production and collaboration. These features embed electronic information (metadata) in a file, which can reveal the identity of those who edited the document (revision authors); track the time, date, and frequency of edits (track changes and revisions); reveal inserted comments and the document template; and other data employed to control the document’s text and format.

The metadata contained in a Word document doesn’t necessarily create risk of adverse disclosure. In fact some document metadata is necessary for formatting or for automation macros within a document. Some document metadata, such as tracked changes, may be used to collaborate with co-authors, but one might not wish to share such information with one’s adversary or client. The commonly held opinion is that information should be removed before a file is shared outside a business’s electronic walls to avoid violating client privilege, disclosing sensitive information to third parties and so on.

iScrub is an enterprise metadata management software. The software a business uses to clean metadata should be flexible enough to execute internal metadata policies, automated enough to enforce those policies and easy enough for users to understand and utilize.

There are times when a user may want to send out a document with tracked changes intact, but with old author information removed from the document. Another time a user may want to remove all metadata from a document, and convert it to PDF to prevent any further edits. With iScrub you can set up different levels of “scrubbing” for your users to provide these options.

A business’s metadata policy will be more successful if staff can grasp what metadata is, when it can be useful, when it can be harmful and can easily manage the metadata in documents.

For more information on iScrub go to http://www.esqinc.com/section/products/2/iscrub.html

To learn more about metadata go to our news page which has links to several published articles on metadata: http://www.esqinc.com/section/products/2/iscrub.html

Press Release: Word Enhanced Ribbon!

April 12, 2011 by Sarah Salo

Education Partners Inc., one of ADV’s prized training relationships, announces Word Enhanced Ribbon!

Word ER is a set of customizations to the Word 2010 and Outlook 2010 environments that help users work more efficiently within the new ribbon-based user interface. Eureka! It’s here!

Deploying eDOCS 5.3 with Windows 7 64-Bit

March 11, 2011 by Dave Kane

Deploying eDOCS with Windows 7 64-Bit has presented some unique challenges. The first of which is pushing out custom registry settings to users.

Most of the settings which are in HKLocalMachine are now located in the Wow6432Node portion of the registry. Most, but not all. And, some of the setting need to be in both places. Unfortunately, the use of the Client Deployment Utility confuses the issue because it hasn’t been updated for use with a 64-Bit OS.

We have opened a case with Open Text concerning the issue with the Client Deployment Utility. Hopefully, that will be included in the first CU for eDOCS 5.3. In the mean time, we send you back to the recommendation to TEST, TEST, TEST. Especially when it comes to auto profiling emails using drag and drop, whether it’s done in Outlook or the Windows extensions the information is stored in different places and needs to be duplicated.

The second issue is deploying using the MSI file. The batch file used can be rather long unless you go in and edit the MSI itself. Depending on the tool that you use to edit the MSI it can be a little tricky. In the Open Text webinars they have used Orca, my personal preference has been InstEd. I have yet to find an editor that can import those custom registry keys easily, but I’m still looking. Whichever tool you use, creating a transform (MST) to implement with the MSI is your safest solution and can save you a lot of headaches.

eDOCS 5.3 ID Generation Change in MS SQL

January 10, 2011 by Brent Langford

You may be aware of some changes with eDOCS 5.3.  Did you know that the backend generation and storage of the key id’s (SYSTEM_ID, DOCNUMBER, VERSION_ID, and NEEDS_INDEXING) has been changed when using MS SQL?

The DOCS_UNIQUE_KEYS table has been replaced with four separate tables:  SEQ_SYSTEMKEY, SEQ_PROFILE, SEQ_VERSIONS, and SEQ_NEEDS_INDEXING.  For most environments this change is not an issue.  However, if you have functions, stored procedures, triggers, or external applications that insert rows into an eDOCS table that need a new ID, you need to verify that your code is not accessing the DOCS_UNIQUE_KEYS table directly to derive the new ID, but rather uses the sp_nextkey stored procedure. 

Here is an example on how to get the next SYSTEM_ID using sp_nextkey in a SQL Server 2005:

DECLARE @SystemID int
CREATE TABLE #KEY (NEWKEYCOL int)
/*
  … Your code
*/
DELETE #KEY
INSERT INTO #KEY(NEWKEYCOL) EXEC DOCSADM.SP_NEXTKEY ‘SYSTEMKEY’
SELECT @SystemID = (SELECT NEWKEYCOL FROM #KEY)
/*
  … Your code
*/
DROP TABLE #KEY

Tina Fey needs content management

November 4, 2010 by Sarah Salo

I have wee-children.  A job.  A husband who perpetually looses his glasses.  I have a more than 3 things per day that need my attention, and despite the best of intentions, I cannot stay up past 9pm without a caffeine IV.   In result, the fastidious, hyper-organized (and admittedly, judgemental) habits of my 20′s have given way to a type of controlled chaos in my 30′s.  The stacks of paper, the 1087 unread emails, the 1 folder on your C:\ drive that has become a universal dump: ahhhhh…I see.  You just had better things to do with your time.  NOW I get it. 

But I’m right-brained.  Though trained as a creative, I am prone to think and do ”outside the box”, so long as the box resides comfortably inside a larger, well-defined parameter (a parameter that is, perhaps, electrified or sporting some sort of barbed wire).  I may have artsy thoughts, but I’m tidy in nature, and have gone a bit soft.  So be it.  But what about the left-brainers?  The creative think tanks and big picture visionaries, who look to the future while unable to see their desktop?  What tools, in the name of productivity, do they have to fall back on when they need to reel it on in?  From experience, I know: there is extreme euphoria lost when diving into that 1-dump C:\ drive, trying to reconstruct the paper trail of a brilliant idea. 

So I pose the question: document and records management solutions – how can we cater to the creative?  The graphic, interior and architectural designers, branding and advertising firms, studio artists and fashion design houses.  These are huge industries that produce huge (I daresay, excessive) amounts of documentation, oftentimes with gajillion-byte file sizes.   How can dm, rm and content management solutions cater to their file types (AutoCad, Revit, SketchUp, InDesign to name a few)? 

Most importantly: could the brilliant, left-brain content management resolutions we come up with get plugged during Project Runway?

Older Posts »
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/