Hummingbird Enterprise™ 2004
DM 5.1.0.5 Service Release 6
New Features
in Service Release 6
and Previous Releases
March 31, 2006
(Last update to this file: April 10, 2005)
© 2004-2006 Hummingbird Ltd.

Contents
1.
New Features in Service Release 6
DM Administration
DM Client
DM Customization
Client Deployment Utility Logging Options
2.
New Features in Previous Releases
DM Administration
DM Client
Automated E-mail Management
DM Workflow
DM Mobility
DM Customization

1 New Features in Service Release 6
DM Administration
Support for Microsoft SQL Server 2005
To enable support for Microsoft SQL Server 2005, you need to use a complex password the first time you run Library Generator. A complex password is a password that:
Does not contain the user's account name, either in full or in part.
Is at least six characters in length.
Contains characters from three of the following categories:
n
English uppercase characters (A through Z).
n
English lowercase characters (a through z).
n
Numbers (0 through 9).
n
Nonalphanumeric characters (for example: !, $, #, %).
After running Library Generator, you can disable password policy enforcement. Refer to your SQL documentation for additional information.
Dynamic Views for Oracle Installations
Dynamic Views in DM Extensions is a supported feature for sites running Oracle 9i and 10g. To enable this support, Oracle sites must run an SQL script file against the DM library. For more information, see the chapter titled "Installing Dynamic Views" in the document Dynamic Views in DM Extensions.
Prior to 5.1.0.5 SR6, Dynamic Views was supported only for Microsoft SQL Server sites.
Content Cache Lazy Write Feature
The cache server's synchronization of documents with the central DM Server is now transparent to users. When users working in remote sites save documents, instead of having to wait for documents to be transferred back to DM Server, the documents are immediately released back to the users while synchronization is being performed.
To implement the Content Cache Lazy Write feature:
1.
Click Start>Programs>Hummingbird>DM Server>DM Server Manager.
2.
In DM Server Manager, click the Server State tab, and then click Stop.
3.
Using a SQL Query tool, run the content_cache.sql script (located in \\Tools\DM Server) against all your DM libraries. If the library owner is not DOCSADM, replace DOCSADM in the SQL script with the name of the database owner.
4.
Click the Content Cache tab and ensure that Enable Content Cache is selected. In the Physical Location field, specify a location for storage of the Content Cache files. In the Maximum Cache Size field, enter a number to limit the size of the cache. In the Days to keep field, enter the number of days to keep the cached files. Click Apply to save your settings.
5.
Click the Server State tab and click Start to restart the DM Server service.
6.
Click Start>Run and type regedit. In the local system registry, create the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\DOCSFusion\ Content Cache.
Enter a new string value: Lazy Write. Set its value to Enable.
Or you can convert the following text into a registry file (*.reg) and then use the regsvr32.exe executable to place it into your DM Server's registry file. Change the Location field to the location you have selected to store the Content Cache files.
Lazy Write Registry File Example:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\DOCSFusion\Content Cache]
Cache=Enabled
Max Size=dword:000001f4
Lazy Write=Enabled
Location=C:\content_cache
SearchServer 6.0
SearchServer has been upgraded to version 6.0, which supports the indexing of .ZIP files and e-mail attachments in .MSG format.
The ftmf text reader can index first-generation attachments (such as Microsoft Word documents) in Microsoft Outlook 2003 e-mail message (.MSG) files; however, it cannot index attachments within an attachment. The ftmf text reader also cannot index first-generation attached Microsoft PowerPoint documents.
The ftmf text reader does not index the contents of a .ZIP file, but it does record the name of the .ZIP file. However, you can use the Archive Expansion (ftacrx) and Retrieval (ftarcr) text readers, which will index the contents of the .ZIP file. Information regarding the ftacrx and ftarcr text readers is located in the SearchServer 6.0 documentation.
See the Configuration Notes in the DM 5.1.0.5 Service Release 6 Release Notes for instructions on implementing SearchServer 6.0.
Client Deployment Utility Log-On and Log-Off Settings
When administrators enable the Pre-logon dialog box, they do not need to distribute a registry file to users.
DM Extensions Per User
In multiuser, terminal-server environments, administrators can configure DM Extensions application integration on a per-user basis. For instructions, see the document Configuring DM Extensions for Per-User Operation.
Support for Oracle 10g
To upgrade to DM 5.1.0.5 SR6 and later in an Oracle 10g environment, ensure that you have the latest Oracle ODBC drivers installed on your Oracle Server. Then synchronize your users. Installing drivers from Oracle 10g will work with Oracle versions 8.0 through Oracle 10g.
RedDot Setup and Configuration
Setup and installation instructions for DM Integration for RedDot CMS have changed. Refer to the document Integrating RedDot CMS with DM for information. An online manual containing administrator and end-user documentation (Hummingbird DM Interface 4.3_en.pdf) can be found in the RedDot installation folder in the SR6 download.
WAN Performance Optimization
In Service Release 6, SQL calls were reduced during server startup, document creation, and activity log creation. This was done to improve performance over wide-area networks.
Support for Integrated Windows Authentication
Integrated Windows Authentication (IWA) allows DM Webtop users to take advantage of single sign-on when accessing DM Webtop. IWA takes the user's credentials used to log on to the local machine and automatically logs the user on to DM Webtop without requiring the user to manually provide their credentials.
DM Client
Support for Acrobat 7
DM 5.1.0.5 SR6 and higher supports integration with Acrobat 7.0. No additional user configuration is required.
Support for WordPerfect 12
DM 5.1.0.5 SR6 and higher supports WordPerfect version 12.
DM Webtop for RedDot CMS
RedDot CMS users can now access their DM documents using the DM Webtop for RedDot CMS client. This client provides RedDot CMS users with a streamlined user interface that allows both Advanced Search and Quick Search functions for finding documents. Users can also view the profile, history, and version information for DM documents. And they can also select the appropriate version of a document to include in their RedDot CMS project and specify whether to use a current snapshot, a secured link, or a static snapshot of each DM document.
COM Automation Customized Footer for Word and Excel
The instructions for configuring customized footers in Microsoft Word and Excel have changed. Refer to the document COM Automation for Microsoft Word & Excel for more information.
Search Variables in DM Extensions
Here is a list of the variables that you can use in various types of searches in DM Extensions 5.1.0.5 SR6 and higher.
Searching on Dates
DATE
A variable representing a date you specify.
N
A variable representing any integer.
%TODAY
A variable representing the current date.
MINUS
An operator that lets you subtract a number of days from the specified date.
TO
An operator that lets you specify a range of dates.
Quick Searches
When using Quick Searches, you can use the %USERNAME variable, which represents the current user performing the search. When you add the %USERNAME variable to a shared Quick Search's search criteria, the user ID of the person performing the search is used as criteria in the field in which the %USERNAME variable is located.
Matter-Centric Security in Dynamic Views
In DM 5.1.0.5 SR6 and higher, you can create matter-centric models using Dynamic Views, which bases document security on the security defined for a Matter. When you define security for a Matter, all documents and/or folders that you store or save within that Matter will inherit the Matter's security. For more information about matter-centric security, see the "Matter-Centric Security" chapter in the document Dynamic Views in DM Extensions.
OUTLOG for E-mail Integration
After you apply SR6 to DM 5.1.0.5, you can enable logging for Microsoft Outlook E-mail Integration. Log files are generated from the EMICore.dll and DMExch.dll files, which record certain operations, such as saving. These log files can be used for troubleshooting purposes.
To enable logging, perform the following steps:
1.
Add the following entries to the local system registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\EMail Integration\Settings
LogFile {REG_SZ} = C:\EmailIntegration.log
LogMask {REG_DWORD} = 0xffffffff
LogFlush {REG_DWORD} = 0x1
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\Email Integration\CoreSettings
LogFile {REG_SZ} = C:\DMSManager.log
LogMask {REG_DWORD} = 0xffffffff
LogFlush {REG_DWORD} = 0x1
The LogFile parameter can be any valid path and file name.
The LogFlush parameter determines how often log entries are written to disk. The higher this number you enter, the better performance will be, because there are fewer and larger log file write operations. However, it is possible that the most recent events will not be recorded, because they have not been written to the file.
2.
Start Outlook.
3.
Select an e-mail message and click File>Save to Hummingbird DM.
4.
Two log files are created in the location you specified: EmailIntegration.log and DMSManager.log. These log files will be created each time Outlook is started.
DM Customization
DM API—GetPublishedOrLatestVersion Code
The following code demonstrates finding the most recent, published version of a document (which is not necessarily the most recently published version).
DOCNUM = "86"
Set objDOCSObjectsApplication = CreateObject("DOCSObjects.Application")
strDST = objDOCSObjectsApplication.DST
strLibraryName = objDOCSObjectsApplication.CurrentLibrary.Name
Dim e, haspubver, result, vlabel
result = get_most_recent_published_version(DOCNUM, strDST, _
strLibraryName, e, haspubver, vlabel)
msg = ""
msg = msg & "haspublishedversion = " & cstr(haspubver)
msg = msg & vbNewLine
msg = msg & "version ID = " & cstr(result)
msg = msg & vbNewLine
msg = msg & "version label = " & cstr(vlabel)
msgbox msg, vbOKOnly + vbInformation, "result"
Function get_most_recent_published_version _
( _
strDocNumber, strDST, strLibrary, byRef out_blError, _
byRef out_blHasPublishedVersion, byRef out_strVersionLabel_
)
Dim objPCDSearch
Dim retval
Dim intRowsFound
Dim i
Dim strVersionID
Dim strVersionLabel
Dim strVersionStatus
retval = ""
out_blError = FALSE
out_blHasPublishedVersion = FALSE
out_strVersionLabel = ""
Set objPCDSearch = CreateObject("PCDClient.PCDSearch")
objPCDSearch.SetDST strDST
objPCDSearch.SetSearchObject("VersionsSearch")
objPCDSearch.AddSearchLib(strLibrary)
objPCDSearch.AddSearchCriteria "%OBJECT_IDENTIFIER", strDocNumber
objPCDSearch.AddReturnProperty "VERSION_ID"
objPCDSearch.AddReturnProperty "VERSION_LABEL"
' A status of '20' indicates that the document has been published.
objPCDSearch.AddReturnProperty "STATUS"
' Sort by version ID and reverse the order of the returned list so
' that, when we loop through the results, the first published version
' is the most recent published version. Note that this is not
' necessarily the same as the most recently published version as
' documents can be published in any order.
objPCDSearch.AddOrderByProperty "VERSION_ID", 0
objPCDSearch.Execute()
If (objPCDSearch.ErrNumber <> 0) Then
retval = ""
get_published_version = retval
out_blError = TRUE
Exit Function
End If
intRowsFound = cLng(objPCDSearch.GetRowsFound())
For i = 1 to intRowsFound
objPCDSearch.SetRow(i)
strVersionID = objPCDSearch.GetPropertyValue("VERSION_ID")
strVersionLabel = objPCDSearch.GetPropertyValue("VERSION_LABEL")
strVersionStatus = objPCDSearch.GetPropertyValue("STATUS")
If (strVersionStatus = "20") Then
out_blHasPublishedVersion = TRUE
out_strVersionLabel = strVersionLabel
retval = strVersionID
get_published_version = retval
Exit Function
End If
Next
out_blHasPublishedVersion = FALSE
get_published_version = retval
End Function
RevokeRight and GrantRight Methods from the PCDDocObject
The DM API Reference Guide states that the PCDDocObject.GrantRight method is used to "set the named bit in the rights mask for the specified user or group." Actually, this method provides no means to specify a user or group; the purpose of this method is to calculate a rights mask based upon a rights-mask argument and a rights-token argument. The arguments and return values for this method have no inherent relationship to any user, group, or document, including the document represented by the current PCDDocObject instance. Any rights mask representing the rights of any user to any document may be passed to this method. The right specified by the parameter strRightName is added to the rights mask specified by the parameter intRightsIn, and the resulting value is returned. In other words, bits are turned on in the passed-rights mask and the result returned.
The DM API Reference Guide also states that the PCDDocObject.HasRight method is used "to determine if the specified user or group rights mask permits the right you specify." This is correct but needs clarification. This method does not indicate the rights of any user to any document. Rather, this method indicates whether or not the rights mask passed as the argument intRightsIn contains the right specified by the rights token argument strRightName. In other words, this method is used to determine if certain bits are turned on in the passed-rights mask.
DM Extensions API—Create ExplorerCore.BCSession Object to Avoid Lost Connections
In DM 5.1.0.5, a feature was added to prevent DM Extensions from remaining in memory when it is not needed. As a result, creating a globally scoped DOCSObjects.Application object is no longer always sufficient to maintain a connection to DM. Depending on the particular programmatic or user-interface actions taken in a custom DM Extensions API application, the DOCSObjects.Application might lose connection to DM. When this occurs, the result may be the loss of the DOCSObjects.Application variable as a valid reference, RPC errors, or other errors related to the loss of connection.
To prevent this, the application must create and maintain a global reference to an ExplorerCore.BCSession object. In Microsoft Visual Basic 6.0, this can be accomplished by adding a module to the project and adding the following code to the module to declare and initialize the ExplorerCore.BCSession object. This code requires that the Visual Basic project contain a reference to Explorer Core 1.0 Type Library (c:\Program Files\Hummingbird\DM Extensions\DM.EXE).
Public mobjBCSession As New DECoreLib.BCSession
After the initialization of the DOCSObjects.Application object, the application must log on to the session:
' Initialization of the DOCSObjects.Application object
Set mobjDOCSApplication = New DOCSObjects.Application
' Alternatively:
' Set mobjDOCSApplication = CreateObject("DOCSObjects.Application")
' Logging on to the session:
mobjBCSession.LogonEx
' Now one can access the DOCSObjects.Application object and child objects, e.g.:
' MsgBox mobjDOCSApplication.DST
Be aware that the Explorer Core type library name as it appears in Visual Basic is different from the Server Name (part of the ProgID) as it appears in the system registry. Thus, the following are equivalent ways of initializing a BCSession object:
' Requires a VB project reference to the Explorer Core 1.0 Type Library:
Set mobjBCSession = New DECoreLib.BCSession
' Uses the ProgID (stored in the system registry):
Set mobjBCSession = CreateObject("ExplorerCore.BCSession")
Client Deployment Utility Logging Options
The Logging Option in the Client Deployment Utility (CDU) allows you to enable a variety of logging options and change the location of the log file(s). In addition, you can log COM Automation functions.
These log files are used for troubleshooting purposes. Hummingbird Technical Support staff will advise you what logging options you should enable.
When you enable a log file, a registry key and value is placed in the System registry. Most of these registry values are located in:
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\PowerDOCS
See the individual module descriptions below for the complete registry key and value.
To enable a logging module in the CDU, click the Logging check box and select the module whose activity you want to log.
Acrobat Plug-in
File Name:
AcrobatPlugin.log
Location:
C:\AcrobatPlugin.log
Registry Key:
HKLM\Software\Hummingbird\PowerDOCS\AppIntegration\Acrobat Plugin\
Name: EnableLog Value: C:\AcrobatPlugin.log
This is the log file for the DM Acrobat plug-in PDPlugin.API.
Attaché Plug-in
File Name
UnPlugin.log
Location:
C:\UnPlugin.log
Registry Key:
HKLM\Software\Hummingbird\PowerDOCS\\Core\Plugins\Attache\
Name: LogFile Value: C:\UnPlugin.log
This log file should be enabled only when an issue involves DM going offline anytime during a working session.
If you enable this log file, you should also enable the Attache Plug-in API log file. Consult the following for more information.
NOTE: The Attaché Plug-in and Attaché Plug-in API log files work in conjunction with each other.
Attaché Plug-in API
Name:
UnPAPI.xml
Location:
C:\UnPAPI.xml
Registry Key:
HKLM\Software\Hummingbird\PowerDOCS\Core\Plugins\Attache\
Name: APILogFile Value: C:\UnPAPI.xml
This log file provides a more in-depth version of the Attache Plug-in log file. This XML-based log file provides the actual API calls that are being made, including the parameters that are being passed. Hummingbird Development and/or Technical Support might use this log in conjunction with the Attache Plug-in log file for troubleshooting issues. If you enable the regular log file (Unplugin.log), you should also enable the API version (UnPAPI.xml) log file.
When you enable the Attache Plug-in API module log file, an Overwrite check box appears next to the File Name field. If you select Overwrite, the log file's existing data will be replaced with new data.
Core
Name:
DECore.log
Location:
C:\DECore.log
Registry Key:
HKLM\Software\Hummingbird\PowerDOCS\Core\
Name: LogFile Value: C:\DECore.log
This log file is generated from DM.exe and shows the loading and unloading of plug-ins, the reference count of the core objects, and the locking and unlocking of modules. It is useful to review this log if the DM.exe process stops responding.
Directory Monitoring Integration Scheme
File Name:
DirMon.log
Location:
C:\DirMon.log
Registry Key:
HKLM\Software\Hummingbird\PoweDOCS\AppIntegration\DirMon\
Name: LogFile Value: C:\DirMon.log
This log file records activity pertaining to monitoring of the defined directory.
Document Management Plug-in
File Name:
FsPlugin.log
Location:
C:\FsPlugin.log
Registry Key:
HKLM|Software\Hummingbird\PowerDocs\Core\Plugins\Fusion\
Name: LogFile Value: C:\FsPlugin.log
This log records what actually happens inside the FsPlug-in. The Extended Log check box should be selected only if you have been instructed to do so by Hummingbird Technical Support. The Extended Log option tracks all locking and unlocking of code sections, and therefore increases the size of the log file.
If you enable this log, you should also enable the Document Management Plug-in API log file. See below for more information.
NOTE: The Document Management Plug-in and Document Management Plug-in API log files work in conjunction with each other.
Document Management Plug-in API
File Name:
FsPAPI.xml
Location:
C:\FsPAPI.xml
Registry Key:
HKLM\Software\Hummingbird\PowerDOCS\Core\Plugins\Fusion\
Name: APILogFile Value: c:\FsPAPI.xml
The Document Management Plug-in API is a non-standard XML-rendition of all FsPlugin API calls. Hummingbird Development and/or Technical Support might use this log in conjunction with the Document Management Plug-in log file for troubleshooting issues. If you enable the regular log file (FsPlugin.log), you should also enable the API version (FsPAPI.xml) log file.
Interceptor
File Name:
Interceptor.log
Location:
C:\Interceptor.log
Registry Key:
HKLM\Software\Hummingbird\PowerDOCS\AppIntegration\ Interceptor\
Name: EnableLog Value: c:\Interceptor.log
This is the high-level log for the Interceptor.exe process. It records operations such as the opening and closing of documents.
Interceptor Core
File Name:
InterceptorCore.log
Location:
C:\InterceptorCore.log
Registry Key:
HKLM\Software\Hummingbird\PowerDOCS\AppIntegration\ Interceptor\Settings\
Name: EnableLog Value: c:\InterceptorCore.log
This is the low-level log for the Interceptor.dll file. This log records the low-level activity that Interceptor sees while monitoring the document window.
ODMA Document Management System
File Name:
DOCS_DMS.log
Location:
C:\DOCS_DMS.log
Registry Key:
HKEY_CLASSES_ROOT\ODMA32\PCDOCS\Log\
Name: EnableLog Value: c:\DOCS_DMS.log
This log records all calls made from the ODMA32.dll file to the Hummingbird DOCS_DMS.dll file. The DOCS_DMS.dll file is the entry point into DM for calls made from the ODMA32.dll file. The information in this log can be helpful in troubleshooting issues with ODMA-integrated applications.
ODMA Manager
File Name:
ODMA32.log
Location:
C:\ODMA32.log
Registry Key:
HKEY_CLASSES_ROOT\\ODMA32.ConnectionManager\ Logging\
Name: File Value: c:\ODMA32.log
This log records all ODMA-call information made from an application to the ODMA32.dll file. This information can be useful in troubleshooting issues with ODMA-integrated applications.
Support Log
File Name:
Support.log
Location:
C:\Support.log
Registry Key:
HKLM\Software\Hummingbird\PowerDOCS\SupportLog
Name: LogFile Value: c:\Support.Log
This log tracks and records user actions in DM Extensions, which is useful for troubleshooting DM Extensions issues.
Viewer Add-on
File Name:
FulViewOCX.log
Location:
C:\FulViewOCX.log
Registry Key:
HKLM\Software\Hummingbird\PowerDocs\FulView\
Name: LogFile Value: c:\FulViewOCX.log
This log records operations by the DM Viewer, both from the viewer pane of the DM Extension for Windows Explorer and the standalone document viewer. In addition to recording the usual viewer operations, this log also records the document being downloaded and the file being opened by the viewer.
Windows Explorer DM Extension
File Name:
DOCSShl.log
Location:
C:\DOCSShl.log
Registry Key:
HKLM\Software\Hummingbird\PowerDocs\Explorer\Shell\
Name: LogFile Value: C:\DOCSShl.log
This log is generated from the DM plug-in for Windows Explorer. It records the main actions taking place inside the plug-in—such as the creation of windows—and tracking the focus. This log can be useful if there are behavior problems when using the DM Extension for Windows Explorer.
COM Automation Logging
File Name:
DM_DEBUG_APPINT_APPLICATIONAME_LOG.TXT (The Application Name is the integrated application for which the log is created)
Location:
C:\Program Files\Hummingbird\DM Extensions
Logging Options:
Off—No logging occurs.
Normal—Logs user actions, such as File>Open and File>Save As.
Extensive—Logs user actions and application actions, such as menu interception and registry reads.
At the bottom of the Client Deployment Utility's Logging window, you can enable COM Automation logging.
Return to Contents

2 New Features in Previous Releases
DM Administration
Increase to maximum number of documents in a library (SR5)
The maximum number of documents that can be held in a single DM/RM library has been increased to over 2 billion. This relieves customers from having to spread a large repository over multiple libraries at the same location. No action on the customer's part, other than installing SR5, is necessary to realize this new capability.
Controlling the display of lookup data (SR5)
Two registry settings have been modified to enhance performance when retrieving lookup data:
NotLoadOnStartup controls whether the Full List tab of a lookup dialog box is displayed empty or with all data displayed. If a user configures this setting for empty lists, the user need not wait for the entire lookup to be populated before selecting a value. This saves the user time and improves system performance by reducing requests to DM Server.
StartInRecent causes the lookup dialog box to open with the Recently Used Item tab selected. The user can set individual lookup dialog boxes to open with the Recently Used Item tab selected by selecting the Start in Recent Items tab check box on the lookup dialog box. All of the lookup dialog boxes can be set to open with the Recently Used Item tab displayed by setting a registry key value.
These settings can be applied to individual lookups or to all lookups.
NotLoadOnStartup Setting
NotLoadOnStartup controls whether the Full List tab of a lookup is populated on startup or if the tab remains empty. This setting applies to two types of lookups:
Lookups that have a parent-child relationship, such as Client and Matter: To understand the effect of NotLoadOnStartup, first consider how the lookup behaves without it being set. When the user selects a Client name and then clicks the Matter lookup button, only the Matters related to the selected Client are displayed. However, if the user clicks the Matter button without first selecting a Client, all Matters in the library are displayed in the Full List tab. If the user sets the NotLoadOnStartup DWORD registry value to 1 for the Matter lookup, selecting Matter without first selecting a Client displays an empty Matter list from which the user can search for the desired matter.
Lookups that have no other lookups associated with them, such as Author, Client, Document Type, Keyword, and Application: When NotLoadOnStartup is set to 1 and the user clicks the Author lookup button, no data will be displayed on the Full List tab. The user can simply search for the desired author without waiting for the list to be populated with all Author records in the library.
To set the NotLoadOnStart function:
1.
Locate the registry key for the lookup:
HKCU\Software\Hummingbird\powerdocs\Core\Plugins\fusion\forms\lookup\<library_name>\<lookup_name>
where library_name is the name of the DM library and lookup_name is the name of the lookup containing the lookup data.
2.
Add a new DWORD value named NotLoadOnStartup to the registry key. Set the NotLoadOnStartup value as follows:
Value
Description
1
Enabled
0
Disabled
StartInRecent Setting
To have all of the lookup dialog boxes open with the Recently Used Item tab selected:
1.
Locate this registry key:
HKCU\Software\Hummingbird\powerdocs\Core\Plugins\fusion\forms\lookup\
2.
Set the StartInRecent DWORD value as follows:
Value
Description
1
Enabled for all Lookups
0
Disabled for all Lookups
Note that a StartInRecent setting for an individual lookup will override the StartInRecent setting for the library. For example, if the user has deselected the Start in Recent Items tab check box on a particular lookup dialog box, that dialog box will open with the Full List tab selected.
3.
You can set an individual lookup dialog box to open with the Recently Used Item tab by selecting the Start in Recent Items tab check box on the lookup dialog box, or by editing the registry. The Start in Recent Items tab check box sets the StartInRecent registry value.
To set the value in the registry, locate this registry key:
HKCU\Software\Hummingbird\powerdocs\Core\Plugins\fusion\forms\lookup\<library_name>\<lookup_name>
where library_name is the name of the DM library and lookup_name is the name of the lookup containing the lookup data.
4.
If the StartInRecent DWORD value does not exist, add it and set one of the following values. If the StartInRecent DWORD value already exists, set one of the following values:
Value
Description
1
Enabled for this individual Lookup
0
Disabled for this individual Lookup
ODBC Database Driver (SR5)
ODBC driver support was added to DM Server.
Oracle Performance Improvements (SR5)
Improvements have been made to the performance of DM Server running on Oracle databases.
Support for Custom Full-Text Query via DM API (SR5)
Support for passing custom full-text query strings to the full-text search process is available in SR5 and higher. This feature is intended for use in custom applications.
The query string must follow this format:
select relevance('2:4') as FT_REL, PD_DOCNUMBER as FT_DOC from 'indexTableName' where ...
Notes:
The term SELECT must be the first term in the text string.
The substring PD_DOCNUMBER as FT_DOC must appear in the query in the location shown above.
The relevance algorithm can be changed.
The conditionals of the query may be free-form but must adhere to SearchServer syntax.
The query string is passed into the search API call as search criteria named FULLTEXT_QUERY.
Example:
select relevance('2:4') as FT_REL, PD_DOCNUMBER as FT_DOC
from TIANAVRRLA
where ((CONTENT CONTAINS THESAURUS('dive', WORD_MODIFY, 'word!ftelp/inflect/lang=english')) )
order by FT_REL DESC
The select clause selects the columns FT_REL (an alias for the relevance function) and FT_DOC (an alias for PD_DOCNUMBER) from the SearchServer index table named TIANAVRRLA.
The where clause specifies that the search should return hits for the word "dive" or any thesaurus-defined derivatives.
The order by clause sorts the results set in descending relevance order so the hits with the highest relevance number will be first in the results set.
NOTE: Certain files and registry keys are not removed by uninstalling the software. However, the presence of these items will not adversely affect the installation or performance of the upgrade.
Improved Performance for Hybrid Searches (SR5)
A new feature to improve the performance of hybrid searches—searches that contain both profile and content search criteria—is now available. The hybrid search enhancement changes the way in which the index table uses metadata when performing a hybrid search.
SQL scripts and Windows registry scripts for applying these changes to your system can be found in \Tools\DM Server\Profile-Content Search.
It is recommended that you contact Hummingbird Support for assistance in applying this enhancement to your system.
To apply the index table changes:
1.
Set the FULLTEXT flag for all metadata columns.
All metadata columns that are to be indexed must have their FULLTEXT flag in the DOCSADM.DOCSCOLUMN table set to Y. This can be done through DM Designer or through SQL scripting.
Two sample SQL scripts are provided to set the FULLTEXT flag for subsets of metadata columns that are candidates for indexing.:
INDEXED_COLUMNS_DM.SQL is for use with basic DM systems.
INDEXED_COLUMNS_RM.SQL is for use with RM systems.
Select and run the appropriate script for your system.
2.
Map metadata columns to index columns.
Indexed metadata columns must be mapped to a corresponding index table column. The column mapping is maintained under the HKLM\Software\Hummingbird\DOCSFusion\Indexer\FSSInitialization\Mapping registry key.
Two sample registry script files are provided to set up the index column mapping information:
INDEXED_COLUMN_MAP_DM.REG is for use with basic DM systems.
INDEXED_COLUMN_MAP_RM.REG is for use with RM systems.
The registry mapping information must be applied to the indexing server and all DM Servers that will be executing search requests.
Select and run the appropriate registry script for your system.
3.
Refresh the DM Servers schema cache.
Shut down and restart all DM Servers and indexing servers. This step is required to clear all of the cached schema data from the server caches.
Failure to perform this step will result in the failure for the index table schema to be properly defined, as well the inability for the search process to properly map metadata columns to index columns.
4.
Create and populate the index.
Create and populate a new index. This step is required to set the metadata information in the index. An existing index can be used, but it must be completely reindexed for the metadata information to be populated.
5.
Enable the new hybrid search enhancement.
Two registry script files are provided to enable or disable the new hybrid search enhancement:
ENABLEHYBRIDSEARCH.REG enables the new hybrid search enhancement.
DISABLEHYBRIDSEARCH.REG disables the new hybrid search enhancement.
The hybrid search enhancement must be enabled on all DM Servers that will be executing search requests. It is only necessary to enable the hybrid search functionality on the indexing server if it will also be processing search requests.
Select and run the a registry script to enable or disable the hybrid search enhancement.
Technical Notes
Searches that combine profile and full-text content search criteria tend to perform poorly, especially when the full-text content criteria is not well defined. For example, a search for a particular author from the profile criteria and the full-text criteria "banking" may take several minutes to return results. Further definition of the full-text criteria can improve performance by narrowing the search. For example, searching for "federal banking rules" would improve performance over simply searching for "banking".
The hybrid search enhancement improves search performance by indexing additional document metadata in the index table.
Changes made by the hybrid search enhancement
The hybrid search enhancement makes these changes to the DM system:
The column definition for each selected metadata property has its FULLTEXT flag set to Y in the DOCSCOLUMNS table.
The SQL path for each criteria property is mapped to an index column name.
The index column mapped to the SQL path of the criteria property is added to the index table schema.
The enhanced hybrid search functionality is enabled with a Windows registry setting.
Indexed Metadata
The forms LAWQBE and PD_EPROF were chosen as guidelines for identifying metadata columns whose usage makes them candidates for indexing. The SQL paths for the identified columns and their assigned or recommended index column names are shown below. The mapping of the SQL paths to index column names is maintained within the Windows registry.
Column name
SQL path
DOCNAME
TITLE *
ABSTRACT
SUMMARY *
LAST_EDIT_DATE
MODIFIED *
KEYWORDS_DISPLAY
KEYWORDS *
AUTHOR.FULL_NAME
AUTHOR *
DEFAULT_RIGHTS
PD_SECURED *
APPLICATION.APPLICATION
PD_APPLICATION
AUTHOR.USER_ID
PD_AUTHOR_ID
TYPIST.USER_ID
PD_TYPIST_ID
TYPIST.FULL_NAME
PD_TYPIST_NAME
DOCUMENTTYPE.TYPE_ID
PD_TYPE_ID
LAST_EDITED_BY.FULL_NAME
PD_LAST_EDITED_BY_NAME
LAST_EDITED_BY.USER_ID
PD_LAST_EDITED_BY_ID
MATTER.CLIENT_ID.CLIENT_ID
PD_CLIENT_ID
MATTER.CLIENT_ID.CLIENT_NAME
PD_CLIENT_NAME
MATTER.MATTER_ID
PD_MATTER_ID
MATTER.MATTER_NAME
PD_MATTER_NAME
PD_ADDRESSEE
PD_ADDRESSEE
PD_EMAIL_BCC
PD_EMAIL_BCC
PD_EMAIL_CC
PD_EMAIL_CC
PD_ORGANIZATION
PD_ORGANIZATION
PD_ORIGINATOR
PD_ORIGINATOR
PD_FILE_PART.PD_FILE_NAME
PD_FILE_NAME
PD_FILE_PART.PD_TITLE
PD_FILE_PART_TITLE
PD_FILE_PART.PD_PT2LOC_LINK.PD_LOCATION_CODE
PD_LOCATION_CODE
* Indicates columns that, by default, are already included in the index table. Certain functions within the overall DM system rely on having these columns in the index table. These default columns must not be removed from the index.
Storing foreign keys, not values
Due to the volatile nature of some metadata values, such as user names, the metadata storage mechanism does not actually store the metadata value for foreign columns. Instead, the mechanism stores the SQL row key column value. PROFILE table columns are still stored by value. During the search process, foreign table search properties are resolved to the appropriate foreign table row key value.
Effect on search strings
When the hybrid search enhancement has been applied, metadata criteria will be applied to the index table SELECT statement WHERE clause as an AND conditional, where the specified criteria value must be equal to the value in the index table row. For example:
WHERE CONTENT CONTAINS 'search term' AND PD_AUTHOR_ID='1001'
As mentioned above, the SQL row key values are stored for indexed foreign table metadata. Thus, this example shows the WHERE conditional for the PD_AUTHOR_ID column resolving to the DOCSADM.PEOPLE table SYSTEM_ID column value instead of the USER_ID column value.
Move Folders with Contents Enhancement for Storage Management (SR5)
You can now move folders and their contents using the Storage Management Move function. A new Move Folders With Contents check box can be added to the Storage Management Move dialog box by adding a new setting to the pcdocs.ini file.
To enable the Move Folders With Contents check box:
1.
Locate the pcdocs.ini file and open the file with a text editor. The file is typically located in Program Files\Hummingbird\DM Server\program.
2.
Add this text to the pcdocs.ini file:
[StorMan]
showWithContents=1
3.
Save and close the pcdocs.ini file.
When you use the Storage Management Move function, a Move Folders With Contents check box will appear on the Move dialog box.
To move folders with contents:
1.
Search for and select the folders you want to move.
2.
Click the Move button. The Move dialog box is displayed. The Move Folders With Contents check box will only be available if:
You only select folders from the search results. The Move Folders With Contents option will be grayed out and available for use if documents are selected.
The selected folders do not have parent folders or related items. The Move Folders With Contents option will be grayed out and available for use if the selected folders have parent folders or related items.
Documents within the folders are only used within a single folder. If a document is used in more than one folder, the Move Folder With Contents check box will be grayed out and unavailable for use.
3.
If the folders you have selected to move meet the above criteria, the Move Folder With Contents check box will be available for use. Select the Move Folder With Contents check box.
4.
Complete the Move function as you normally would. Refer to the Storage Management online help for instructions on performing a move.
Storage Management will move all of the selected folders and their contents.
Configuring to show paper profiles in recently edited list (SR5)
In DM 5.1.0.5 Service Release 4, DM can be configured so that Profiles of paper documents appear in the recently edited (RED) list upon being edited. Prior to SR4, paper-document Profiles appeared in the RED list only when they were first created but not when the profiles were subsequently edited.
To display edited Profiles of paper documents in the RED list:
1.
In the Client Deployment Utility, select Document Management Plugin and select the option Use DM Server RED. (This option is selected by default.)
2.
On the DM Server machine, add the following key to the Windows registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\DOCSFusion]
"Paper2Red"=dword:00000001
After DM Extension users edit a paper document's Profile, they should select View > Refresh to display the profile in the RED list.
Printer Monitoring (SR4)
For Service Release 4, printer monitoring is disabled by default when application integration is installed on a user workstation. DM administrators who want to turn on printer monitoring should define a deployment package with the option Enable Print Monitoring selected.
Ability to filter Members and Non Members in the Group Members dialog box (SR4)
Ability to filter Members and Non Members in the Group Members dialog box. Both wildcard searching/filtering and initial letter filtering are required.
Two text fields have been added to the Groups Members form, one for the Current Members list and one for the Non-Members list. Typing text into one of the fields will be applied as an initial string filter. The wildcards `?', `(`, any single letter, and * (any string) can be used.
To enable this feature:
1.
Navigate to the pcdocs.ini file. Open My Computer, then go to the default directory location:
C:\Program Files\Hummingbird\DM Server\Program
2.
Double click on the file to open it for editing in Notepad. Scroll to the end of the file and add the following entry:
[docsadmn]
members_filter=1
3.
Save the file and refresh the DM Server.
Log Files for DM Extensions on End-User Machines (SR2)
Log files pertaining to an installation of DM Extensions were not accessible to end users, so they were unable to use the information in these files for troubleshooting. With Service Release 2, the installation log files are created on the user's local machine in the folder \Temp\HUMCLogs.
Easy Removal of DM and RM Software (SR2)
DM and RM can now be removed from end-users' machines via a single operation by the DM and RM administrator. This allows the administrator to easily remove the software from all user machines prior to installing an upgrade.
To uninstall the software:
1.
Create a deployment package containing no software components.
2.
To allow end users to run the deployment package without being prompted for information, select the silent deployment option.
3.
If users do not have administrator rights on their machines, select the option to run as the administrator and provide the necessary administrator logon information.
4.
Save the deployment package to a source location on the network. Distribute the deployment package using one of the methods described in Chapter 11 of the DM Administration Guide.
NOTE: Certain files and registry keys are not removed by uninstalling the software. However, the presence of these items will not adversely affect the installation or performance of the upgrade.
Renaming E-mail Attachments in GroupWise (SR2)
By adding the following keys to the registry, you are able to rename a GroupWise e-mail attachment. There are two new registry keys under:
HKEY_CURRENT_USER\Software\Hummingbird\PowerDOCS\Core\Plugins\Fusion\Forms\Mail
AllowEditDocName — DWORD, Values of 1 or 0
AttachNameFormat — String.
If the first key exists and is equal to 1, the user can edit the Document name field.
If the second key exists and has the following format, then the attachment name is changed, regardless of the format values; otherwise, the behavior will be the same as in previous DM versions.
Here are a few examples of the values for this key:
Doc Number - [DocNumber]
Doc Name - [DocName]
Version - [Version]
Library - [Library]
My Library # - [Library]
Document Number # - [DocNumber]
Name - [DocName]
[Library] - [DocNumber]
There are four possible values that could be used and replaced with real document values:
[DocNumber] - document number
[DocName] - document name (the one that could be edited)
[Version] - document version
[Library] - library name
Redundant Content Cache File Upload (SR2)
Programmatic changes have been made to eliminate the redundancy.
DM WatchDog Support in Microsoft Word (SR2)
The WatchDog utility monitors Microsoft Word's attempt to create a new file for DM. Microsoft Word will create a new physical file when a user first saves a new document or when a user saves an existing document as a new document or new version.
When DM receives information from Word via ODMA that a Save As operation is about to take place, DM will launch WatchDog, which waits for the creation of the new physical file. If the file is not created within 10 seconds, WatchDog displays a message box with the following text: "It appears that Microsoft Word had a problem saving document <document title> into your DM library. Please contact your DM administrator for further assistance." Once the user closes this message box, WatchDog is terminated. If the document was created successfully, the WatchDog process will simply terminate.
DM cannot use WatchDog unless it is registered on the local machine. To register WatchDog, a user must double-click the executable file. No dialog boxes are shown during registration. The only way to know that WatchDog is operating is to open Windows Task Manager and look for WatchDog to appear when you save a file as a new document in Word.
Watchdog.exe is available in the Tools directory on the Enterprise 2004 CD. Copy the file to the user's DM Extension folder on the local machine and double-click the file to register it.
Document Recovery Screen Options (SR2)
When a workstation stops responding while a user is editing a document, upon recovery, the user is prompted with the following screen:
Hummingbird DM was terminated improperly and the following documents remain checked out. Select an action and click OK.
The three options available are:
Discard edits and unlock
Check in Edits
Continue Editing
The default value is Discard Edits and Unlock. To choose a different option, the user must select the option and then click OK. However, when multiple documents are shown in the dialog box, the option must be changed individually for each document. When you click the option button, it changes the information in the Action column only for the highlighted document. This is not clear to users. For example, they might select Check in Edits but not realize that this choice only affects the first document in the list. When they click OK, all other documents in the list still have Discard Edits and Unlock selected. Any edits made to the other documents will be lost.
The information in the Action column should be "Check in Edits" for all documents that appear in the list, thereby matching the default value in the option buttons.
The default option for Document Recovery dialog box options can be changed through the following registry setting:
[REG_DWORD]
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\PowerDOCS\Core\Plugins\Fusion: DefaultGPF=
Use the following values to change the behavior:
· 0 - Unlock
· 1 - Check in
· 2 - Continue editing
Remove Ability to Install Internet Mode DM API (SR2)
If Internet mode is already installed, a modification to the installation will not remove it.
Pre-caching for Lookups on Profile Forms (SR2)
Profile forms are now treated the same as search forms and are available for pre-caching. Refer to Chapter 13 of the DM Administration Guide for more information on caching.
Bypass Finish or Reboot Dialog Boxes During DM Extensions Installation (SR2)
To bypass the Finish or Reboot dialog boxes:
1.
Create a deployment package.
2.
Go to the .ini file for the package and add the following line to the [Hummingbird] section:
SkipFinishDlg=Y
Document Save in Microsoft Word (SR2)
This is a twofold issue regarding saving documents in Microsoft Word integrated through Active Integration or Passive Integration:
DM client stops responding during a Save operation. This typically happens when a user opens multiple documents and the DM client becomes unresponsive during a Save operation.
A DM client would close all opened documents even when a user has not closed them. This happens when a user has multiple documents open. When a user is in the process of saving a document, the other documents are closed by DM.
Activate the Quick Save feature in the Client Deployment Utility. Refer to Chapter 13 of the DM Administration Guide for further instruction on using the Quick Save feature.
DM Client
Addressable Folders (SR5)
Addressable Folders is a feature of DM Extensions that enables a user to profile an outgoing message (or forward an existing message) to a DM folder by adding an e-mail address to the message's recipients list.
Addressable Folders is made up of services that run on the DM Server machine, or a machine that has access to the DM Server machine. In addition to these services, functionality is provided in DM Extensions by which users can assign e-mail addresses to the specified DM folder.
See the following document for information on installing, configuring, and using DM Addressable Folders:
Using DM Addressable Folders
COM Automation for Microsoft Word and Microsoft Excel (SR5)
Microsoft Word and Excel can now be integrated using a new COM Add-in. This add-in is meant to remove the dependency on Microsoft's built-in ODMA implementation. The add-in communicates with DM through DM-managed COM interfaces and has no reliance on ODMA.
For detailed information on configuring and using this integration method, see the document:
COM Automation for Microsoft Word and Microsoft Excel.
Using COM Add-in Integration, Save As Menu Item from MS Word Native Recovery Pane Is Not Intercepted (SR5)
Per Microsoft, it is not possible to intercept this menu item using DM.
Quick Search Enhancement (SR5)
It is now possible to use the %USERNAME string in the Author field for Quick Searches. The following strings are also usable:
%USERNAME
English
%UTILISATEUR
French
%NOMEUTENTE
Italian
%BENUTZERNAME
German
%NOMBREDEUSUARIO
Spanish
Support for AutoCAD 2004 and 2005 (SR5)
DM 5.1.0.5 Service Release 5 provides updated support for AutoCAD 2004 and 2005 for DM Extension for AutoCAD.
Below is a list of updated files:
ACADDM2k4.mnu provides the integrated menu option SaveAs 2000 Drawing.
ACADDMExtension.arx was updated to provide support for AutoCAD 2004 and 2005.
After the updates to DM Extension for AutoCAD are installed on user workstations, AutoCAD's Support File Search Path must be updated to include the AutoCAD DM Extension directory for your version of AutoCAD. The table below lists the locations to which the integration files for your version of AutoCAD are installed. For details on this procedure, refer to the topic "Post-Installation Setup" in the online manual Using DM Extension for AutoCAD or the DM Extension for AutoCAD online Help.
AutoCAD Version
Integration Files Location
AutoCAD 2000, 2000i, and 2002
...Hummingbird\DM Extensions\acad
AutoCAD 2004 and 2005
...Hummingbird\DM Extensions\DM Extensions for AutoCAD 2k5
The following section describes the additional menu commands available with Service Release 5.
Save as R2K
Menu: DM>SaveAs 2000 Drawing
Command Line: SAVEASR2K
This command applies only to AutoCAD 2004 and 2005 and replaces the Save As R13 and Save As R14 commands. This command saves the current drawing as a new Document on the DM server, as an AutoCAD R2K drawing. You are prompted to complete a new Document Profile for this new Document. After you enter the required profile information and click OK, the Document is saved and you are returned to AutoCAD.
NOTE: When you return to AutoCAD, the drawing will now point to the profile created when you saved the R2K document, not the original Document Profile.
Additional Documentation Updates for DM Extension for AutoCAD
The sections below update the information provided in the DM 5.1.0.5 manual Using DM Extension for AutoCAD, the section, "Post-Installation Setup."
Post-Installation Setup for AutoCAD 2004
If you have two versions of AutoCAD, for example, AutoCAD 2000 and AutoCAD 2004, and want to integrate both versions with DM, you will need to create two different launch methods, one for each application: for example, ACADDM for AutoCAD 2000 and ACADDM2K4 for AutoCAD 2004. These launch methods should point to the appropriate application directory. For more information on modifying launch methods, refer to the DM Administration Guide.
Launch Method Changes for AutoCAD DM Extension
Before running DM Extension for AutoCAD, verify the Launch Method settings are correct using the Web Admin tab in DM or the Library Maintenance tool.
To check settings in Web Admin:
1.
Launch DM in your browser and log on to the administrator's account.
2.
Select the DM Admin tab.
3.
Select the Validation Tables tab.
The Applications tab will be visible. Click AUTOCAD. Verify the information is the same as described below:
Application Maintenance Settings
Setting
Value
Application ID
AUTOCAD
Description
AutoCAD DM Extension
Filing Scheme
UNIX-Compatible
MIME Type
application/dwg
Default Extension
DWG
Shows on Desktop
Selected
Valid on Profile
Selected
Launch Method
Setting
Value
Application ID
AUTOCAD
Description
AutoCAD DM Extension
Location
By default, this is set to ACAD.EXE. Enter the full path to the directory in which AutoCAD is installed. By default, this is C:\PROGRAM FILES\AUTOCAD 2004\acad.exe.
Command Line Parameter
%FULLPATH /p AutoCADDM
Integration
Full Integration
Enabled
Select this option to enable the application so that it shows in the Application pane in DM Extension for Windows Explorer and DM Extension for Microsoft Outlook.
4.
Click Save when done.
5.
Select Save again.
To check settings using Library Maintenance:
1.
From the Windows Start menu, select Programs>Hummingbird>DM Server>Server Admin Tools>Library Maintenance.
2.
Select Applications.
3.
Select AUTOCAD. Verify the information is the same as described below:
Application Maintenance Settings
Setting
Value
Application ID
AUTOCAD
Description
AutoCAD DM Extension
MIME Type
application/dwg
Filing Scheme
UNIX Compatible
Default Extension
DWG
Launch Method
Setting
Value
Application ID
AUTOCAD
Description
AutoCAD DM Extension
Location
By default, this is set to ACAD.EXE. Enter the full path to the directory in which AutoCAD is installed. By default, this is C:\PROGRAM FILES\AUTOCAD 2004\acad.exe.
Command Line Parameter
%FULLPATH /p AutoCADDM
Integration
Full Integration
Enabled
Select this option to enable the application so that it shows in the Application pane in DM Extension for Windows Explorer and DM Extension for Microsoft Outlook.
Options
Setting
Value
Shows on Desktop
Selected
Valid on Profile
Selected
Use UNC Name
Selected
4.
Click OK when done.
5.
Select Close, then OK to close the Application Maintenance window.
Setting Outlook E-Mail Integration and Outlook DM Extension on Per User Basis (SR5)
An enhancement was added to DM Extension for Microsoft Outlook that allows an administrator to configure an end-user machine for access to Microsoft Outlook E-mail Integration and Microsoft Outlook DM Extension based on the machine or the individual user logged onto the machine.
To create the setting to configure end-user access to Outlook E-mail Integration:
1. Select Start>Run from the Windows desktop.
2. Enter regedit in the Open field. The Registry Editor is opened.
3. Create the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\Email Integration
4. Select Edit>New>DWORD Value. In the Value field, enter OutlookPerUser.
5. Double-click the value you just created. Enter one of the following values in the Value data field:
Value data field
Description
0
Outlook E-mail Integration is accessible on a machine basis.
1
Outlook E-mail Integration is accessible on a per-user basis.
If the value for OutlookPerUser is set to 1, the administrator should log on as the user who will access Outlook E-mail Integration and create the key shown below.
1.
Create the following key:
HKEY_CURRENT_USER\Software\Hummingbird\Email Integration
2.
Select Edit>New>DWORD Value. In the Value field, enter OutlookInstalled. Double-click the value you just created. Enter the value of 1 in the Value data field.
To create the setting to configure end-user access to DM Extension:
1.
Select Start>Run from the Windows desktop.
2.
Enter regedit in the Open field. The Registry Editor is opened.
3.
Locate or create the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\Email Integration
4.
Select Edit>New>DWORD Value. In the Value field, enter DMPerUser.
5.
Double-click the value you just created. Enter one of the following values in the Value data field:
Value data field
Description
0
Outlook DM Extension is accessible on a machine basis.
1
Outlook DM Extension is accessible on a per user basis.
If the value for DMPerUser is set to 1, the administrator should log on as the user who will access DM Extension and add the following value:
1.
Locate or create the following key:
HKEY_CURRENT_USER\SOFTWARE\Hummingbird\Email Integration
2.
Select Edit>New>DWORD Value. In the Value field, enter DMInstalled.
3.
Double-click the value you just created. Enter the value of 1 in the Value data field.
API Method Extended for Refreshing DM Extensions Views (SR5)
A DM Extensions API method was extended for refreshing all DM Extensions views.
The following sample code should be used by custom applications for automatic refreshing of Windows Explorer list view, Outlook list view, and Quick Retrieve list view:
Dim pObjArray As New BCObjectArray
pObjArray.DoVerb "", "", "DOCSOPEN.RefreshAllViews", 0, Nothing
Improved Logging for Support Staff (SR5)
The logging options in Client Deployment Utility have been enhanced to provide the technical support staff with improved log files for troubleshooting.
To enable the new logging option for Hummingbird Support staff:
On your Windows desktop, click Start>Programs>Hummingbird>DM Extensions>Client Deployment Utility.
The DM Client Deployment Utility will launch.
Click the plus sign to expand the DM Client Deployment Utility tree.
Select Logging Options.
In the Module field, select Extended Log.
Select the log check box. The log file name field will be filled automatically.
Select the directory to which the file should be saved.
Improved Error Handling (SR5)
An enhancement was added that improved the handling of unhandled exception errors. When an unhandled exception error occurs, a dump file will be created in \DM Extensions\DmpLogs.
Enhancement: ability to modify the Attaché menu (SR5)
Enhancement: ability to modify the Attaché menu in particular the ability to remove/configure the Replace Original option when saving new documents, versions or sub-versions; or when you do not want to import a document.
This can be accomplished by the following registry change:
1.
Go to Start > Run and enter REGEDIT in the field. Click OK.
Navigate to:
HKEY_CURRENT_USER\Software\Hummingbird\PowerDOCS\Core\Plugins\Fusion\Settings
2.
Select Edit > New > DWORD Value. The value should be called:
NoReplaceOriginal
If NoReplaceOriginal=0 or is not present, the Replace Original option is available on the Import Undocked Documents window in the Action menu.
If NoReplaceOriginal=1, then Replace Original is not an available option.
3.
Save the registry file. If you need to export the file to use as a custom component in a deployment package, select File > Export and export the key to a .reg file.
Enhancement: ability to support the Microsoft Excel Indirect function (SR4)
Enhancement: ability to support the Microsoft Excel Indirect function. The Indirect function returns the reference specified by a text string. The structure of DM filenames interferes with this feature.
SR4 provids support for a FileName template registry setting which can be used to remove symbols from the DM file name.
To enable this feature:
1.
Go to Start > Run and enter REGEDIT in the field. Press OK.
2.
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\PowerDOCS\Core\Plugins\Fusion\Settings
3.
Add "FileName Template" REG_SZ value. Set it to something without the `#' symbol in it, for example:
%LibraryName%-n%DocumentNumber%-v%VersionLabel%-%DocumentName%
NOTES:
Do not change the order of the field values or the field values themselves.
You can only use alphnumeric characters.
You must use an underscore for blank spaces between the field values.
4.
Save the registry file. If you need to export the file to use as a custom component in a deployment package, select File > Export and export the key to a .reg file.
Mapping Keywords Column to Titleblock in DM Extension for AutoCAD (SR4)
To map keywords:
1.
Add the following to the TBSAMPLE.ini file. This file is found in the ..\Program Files\Hummingbird\DMextensions\Samples directory.
[KEYWORD_LABEL]
%KEYWORD
[KEYWORD_DESCRIPTION]
%KEYWORD;DOCSADM.KEYWORD.SYSTEM_ID
2.
Launch DM-integrated AutoCAD.
3.
At the AutoCAD command prompt, type DMMAP. This will start the mapping function.
4.
Click File and locate the TBSAMPLE.DWG file. The default location for this file is the ..\Hummingbird\DMExtensions\Sample directory. Three fields will be available:
Title Block Attributes (empty)
Mapping
Hummingbird DM Extensions for AutoCAD
5.
Remove the Mapping field you want to map to keywords. It will now be in the Title Block Attributes field.
6.
Highlight the attribute in the Hummingbird DM Extensions for AutoCAD field.
7.
Select the profile data you want to map to that field.
8.
Click Map.
You can now use this field to add titleblocks with the Keywords field showing in the space previously showing the document number. Remember, you must have a keyword value in the profile or it will be blank in the titleblock.
Perform an Easy Search (SR3)
For DM 5.1.0.5 SR3, an enhancement was added that enabled users to search for a document by entering a document number without including the pound sign (#) before the number. The topic, "Perform an Easy Search," from the file DMExtensions.hlp was updated accordingly:
Use the Easy Search feature to quickly search for a document number or a phrase or set of words in a document's content or Document Name. If you are searching using a phrase or set of words in the document's content or Document Name, the documents returned are ranked in the following order:
Documents containing the exact phrase in the title
Documents containing the exact phrase in the document
Documents containing one or more words in the title
Documents containing the words in the same sentence or in proximity to each other
Documents containing one or more words in the document
To perform an Easy Search:
1.
Select Search>Advanced Search.
2.
The Search Form is displayed with the Easy Search tab active.
3.
Enter your search words or phrase, or specific document number, in the Enter search criteria field.
If you want to locate a single document based on the document number, you can simply enter the number without the pound sign (#). For example, to find Document # 3458, you need only enter 3458 in the Enter search criteria field. If you want to locate multiple documents based on the document numbers, you must enter the pound sign in front of each number and separate the numbers with a comma, such as #3458, #3459, #3461.
4.
Click OK. A list of documents that meet all the criteria you provided is displayed in the Search Results tab.
Improved Usability When Saving Documents in Multiple Library Environments (SR3)
For DM 5.1.0.5 SR3, an enhancement was added that improved usability when saving a document in an environment where multiple libraries and library groups are available to the user. When the user saves a document, the Libraries list is now displayed with the focus on the default library to which the user is saving the document. This removes the need for the user to scroll through the list to ensure the document is being saved to the default library.
Setting Default View in Recently Edited Documents (SR3)
For DM 5.1.0.5 SR3, an enhancement was added to DM Extension for Microsoft Outlook that enables an end user to set the default view in the Recently Edited Documents list to all documents, only e-mail messages, or documents without e-mail messages. In order to implement this enhancement, a registry key must be added to the end-user workstation and another key modified in order to disable the use of the DM Server Recently Edited Documents list. Follow each set of steps below to implement this enhancement.
To create the setting to filter the Recently Edited Documents list:
1.
Select Start>Run from the Windows desktop.
2.
Enter regedit in the Open field. The Registry Editor is opened.
3.
Locate or create the following key:
HKEY_CURRENT_USER\Software\Hummingbird\PowerDOCS\Core\Plugins\Fusion\Settings\QuickSearches
4.
Select the key and select Edit>New>DWORD Value. In the Value field, enter RED Filter. Double-click the value you just created. Enter one of the following values in the Value data field:
Value data field
Description
0
Display all documents in the list. This is the default value.
1
Exclude e-mail messages from the Recently Edited Documents list.
2
Display only e-mail messages in the Recently Edited Documents list.
You must disable the DM Server Recently Edited Documents list in order to complete the implementation of this enhancement. Use one of the methods in the sections below.
To disable the DM Server Recently Edited Documents list using the Client Deployment Utility:
1.
On your Windows desktop, click Start>Programs>Hummingbird>Hummingbird DM Extensions 5.1.0.5>Client Deployment Utility.
2.
The Microsoft Management Console will launch.
3.
Click the plus sign to expand the DM Client Deployment Utility tree.
4.
Click to expand the Plug-ins tree. If necessary, log on to DM.
5.
Select the Document Management Plug-in>General tab.
6.
Clear the Use DM Server RED option.
To disable the DM Server Recently Edited Documents list via the registry:
1.
Select Start>Run from the Windows desktop.
2.
Enter regedit in the Open field. The Registry Editor is opened.
3.
Locate the following key:
HKEY_CURRENT_USER\Software\Hummingbird\PowerDOCS\Core\Plugins\Fusion\Settings\QuickSearches
4.
Double-click the key Use DOCSFusion RED. Enter 0 (zero) in the Value data field.
Sorting the Library List (SR3)
For DM 5.1.0.5 SR3, an enhancement was added to DM Extensions enabling the option to sort the library list alphabetically. In previous versions of DM, the Primary Library is displayed first in the list, and subsequent libraries are sorted alphabetically. If you implement the registry change detailed below, all libraries will be sorted alphabetically, regardless of your Primary Library.
To create the setting to enable sorting of all libraries alphabetically:
1.
Select Start>Run from the Windows desktop.
2.
Enter regedit in the Open field. The Registry Editor opens.
3.
Create the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\PowerDOCS\Explorer
4.
Select the Explorer key and select Edit>New>DWORD Value. In the Value field, enter SortPrimaryLibrary. Double-click the value you just created. Enter the number 1 in the Value data field.
Accessing the DM Context Menu (SR3)
For DM 5.1.0.5 SR3, DM Extension for Microsoft Outlook 2003 was enhanced to enable a user to right-click, in the tree view, any node under the DM node and receive the DM context menu. In previous versions, the DM context menu could not be displayed. Users are now able to open directories, conduct searches, create new folders, and manage workspaces using the DM context menu in Outlook 2003.
Requiring Users to Select a Destination Folder (SR3)
For DM 5.1.0.5 SR 3, an enhancement was added to DM integration for Microsoft Outlook that enables administrators to require users to select a destination folder when using the Profile on Send e-mail feature.
NOTE: The Profile on Send feature must be enabled for this enhancement to work. If the option Require profiling of sent e-mails is selected, when a user sends a new e-mail, he or she must select a folder to which the profiled message is added. If the Require profiling of sent e-mails option is not selected, the user may optionally cancel out of this process. The option Require profiling of sent e-mails can be accessed using the Client Deployment Utility on the Document management Plug-in>E-mail Integration>Profile on Send tab.
Follow the steps below to enable the new feature. The section "Using the Profile on Send Feature" from the DMExtensions.pdf file has been updated and is listed below.
To enable requiring users to select a folder to which a saved message will be added:
1.
Select Start>Run from the Windows desktop.
2.
Enter regedit in the Open field. The Registry Editor opens.
3.
Locate the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\Email Integration\1.5\Settings\LIBRARY
4.
Double-click the SaveToFolder value. Enter the number 1 in the Value data field.
Using the Profile on Send Feature
Your administrator can set DM to prompt you to profile your outgoing Microsoft Outlook e-mail messages and attachments. In addition, you may be required to select a folder to which your e-mail message is saved.
1.
Open Microsoft Outlook. If you are not already logged on to DM, do so now.
2.
Compose and send your e-mail. If your administrator has set your integration to require you to select a folder to which the saved message will be added, a Quick Retrieve list is displayed with all the available folders listed. In this case, select a folder and click OK. If the option is available to you, you may also click Cancel to skip this step.
3.
The Save to Hummingbird DM dialog box will appear.
4.
If your e-mail has attachments, they can be profiled as part of the main document or as separate documents. If you do not want to save attachments as separate documents, clear the Save attachments separately check box.
5.
You do not have the option to select which attachments are saved; the default setting is "all attachments".
6.
Save and profile the message and attachments as you would any other e-mail message, or if you do not want to profile the message, click Cancel.
NOTE: If the administrator has required you to profile all outgoing e-mail messages, you will be returned to the e-mail message. Click Send again and proceed with saving and profiling the message and attachments. Until you have profiled and sent the message, it will be stored in your Drafts folder.
Enabling or Disabling Auto Update Component (SR3)
During the DM Extensions setup, you are given the choice to include an optional Auto Update component that will enable automatic updates on end-user workstations when an update is installed on the DM Web Server. The update is triggered when the end user logs on. For DM 5.1.0.5 SR3, an enhancement was added that allows you to enable or disable the Auto Update component to a DM Extensions client installation. This is accomplished by adding a setting to the componentslist.ini file on the machine on which the DM Web Server is installed.
You must have at least DM 5.1.0.5 SR2 installed on your client machines for this feature to be enabled.
To disable the Auto Update feature:
1.
Implement DM 5.1.0.5 SR 3 DM Server and Web Server.
2.
Open the componentslist.ini file. This file is located in the DMExtensions directory on the machine where DM Web Server is installed.
3.
Add the following section to the componentslist.ini file:
[DMExtensions]
Version=5.1.0.5
Update=0
Update ValueDescription
0 Disables Auto Update and no subsequent updates will be entered into the autoupdate.log in the C:\Temp\HUMCLogs directory.
1 Enables Auto Update and a new autoupdate.log will be created in the C:\Temp\HUMCLogs directory.
4.
Save your changes to the componentslist.ini file. When users on SR 2 or higher log on to DM Extensions, Auto Update will not download updates from the server.
Editing E-mails in DM Extension for Microsoft Outlook (SR2)
When sending an e-mail from DM Extension for Microsoft Outlook, you can now switch between e-mails in different windows to copy and paste information from one message to another. Previously, you could not navigate between e-mail windows when sending an e-mail from DM Extension for Microsoft Outlook.
Naming Documents E-mailed as Attachments (SR2)
When e-mailing a document, you can rename the document file or the .drf file that links to the document. You can set the file name manually, or you can set DM Extensions to create a file name based on criteria you specify.
To set up the Rename on Mail feature:
1.
Install DM Extensions and DM Extension for Microsoft Outlook.
2.
Launch the Windows Registry Editor.
3.
Locate this node in the registry:
HKEY_CURRENT_USER\Software\Hummingbird\PowerDOCS\Core\Plugins\Fusion\Forms\Mail
If the Forms\Mail nodes do not exist in the registry, you can create them automatically by using the Mail function in DM Extensions or DM Extension for Microsoft Outlook:
3.1.
Close the Registry Editor.
3.2.
Launch DM Extensions or access DM Extension for Microsoft Outlook.
3.3.
Select a document and click the Mail icon or right-click on the document and select Mail. The Document Mailing Options dialog box is displayed.
3.4.
Click Cancel to close the Document Mailing Options dialog box.
3.5.
Launch the Windows Registry Editor and return to step 3 above; the Forms\Mail nodes will appear in the registry.
4.
Create a new DWORD value with the name AllowEditDocName.
4.1.
Valid values for AllowEditDocName are 0 and 1.
When set to 0, the user will not be able to edit the document name.
When set to 1, the user will be able to edit the document name.
4.2.
Enter a value for AllowEditDocName.
5.
Create a new String value with the name AttachNameFormat.
You can use these parameters in the AttachNameFormat string:
[DocName] - inserts the Document Name in the document file name.
[DocNumber] - inserts the Document Number in the document file name.
[Version] - inserts the document Version in the document file name.
[Library] - inserts the document Library in the document file name.
You can also enter plain text in the AttachNameFormat string to further describe the file. Example: The user is e-mailing the Word document named "Report" in the library "Main". The AttachNameFormat string – "[DocName] from the [Library] library" — will create a file name of "Report from the Main library.DOC.DRF". Enter a value for AttachNameFormat. When using the [DocName], [DocNumber], [Version], or [Library] parameters, ensure that the parameters are enclosed in [brackets].
NOTE: You must enter text in the AttachNameFormat string. If no text is entered, the file name will contain only the document file-type extension (such as ".DOC" for Word files or ".XLS" for Excel files). If a reference is being mailed, the file name will only contain the document file-type extension and the extension ".DRF".
The [DocName] parameter must be included in the AttachNameFormat string if you want user-edited document names to appear in the file name. If the [DocName] parameter is not used, the document name will not be included in the file name, even though the user may have edited the name.
6.
With the AllowEditDocName and AttachNameFormat keys defined, close the Registry Editor.
To edit the Document File Name when mailing a document or reference:
1.
Launch DM Extensions or DM Extension for Microsoft Outlook. Locate and select a document.
2.
Click the Mail icon or right-click on the document and select Mail. The Document Mailing Options dialog box is displayed.
3.
In the Type of send field, select a send option. In the Versions field, select Select. The Document Mailing Options dialog box expands, and the Document List is displayed.
4.
Click on the name of the document in the Name column in the Document List.
If editing of the document name is enabled, you will be able to change the name in the list. Enter text to change the name.
If editing of the name is not enabled, you will not be able to change the name in the list.
5.
Click OK. An e-mail message is created with the document or a .DRF reference file attached.
The document or .DRF file name will be based on the document name you entered on the Document Mailing Options dialog box. If other file name parameters have been set up, the file name will include other information, such as the Document Number, Version, Library, and other text.
Automated E-mail Management
General Note—Automated E-mail Management and the DM API (SR5)
This note applies to sites implementing Automated E-mail Management: whenever the DM API is updated in a Service Release, you must run the updated DM API installation on the machine on which the Automated E-mail Management Server is installed.
Display of Asian Languages (SR5)
For DM 5.1.0.5 Service Release 5, Automated E-Mail Management for Microsoft Exchange (AEM) has been enhanced to fully support display of Asian languages. Prior to Service Release 5, AEM did not create profiles for e-mail messages containing Chinese or Japanese characters in the subject line. Beginning with SR5, Automated E-Mail Management is equipped with full Unicode support, supporting all language characters.
Send a Substitute Message in Automated E-mail Management (SR5)
An enhancement was added to Automated E-mail Management (AEM) for SR5 that enables a stub e-mail message to be sent after the original message is saved to DM. This is an option that the administrator must set; it is not an option set by default. When an e-mail message matches a rule set by AEM, the message and attachment are saved to DM. A substitute e-mail message is then sent to all of the recipients containing a reference file (.DRF) that links to the saved e-mail message in DM and a URL link that can be used to access the e-mail message from the Webtop.
To enable this feature, follow the steps below.
1.
On the machine on which AEM is installed, select Run from the Windows Start menu.
2.
Enter regedit in the Open field and click OK. The Registry Editor is launched.
3.
Locate the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\DOCSExchange\Settings
4.
Double-click the value IsStubEnable. The Edit DWORD Value dialog box is displayed.
5.
In the Value Data field, enter 1 and click OK. Select File>Edit to close the Registry Editor.
6.
Restart the Automated E-Mail Management for Microsoft Exchange service.
In order to use the Webtop QuickLink to view e-mail content, you must specify the DM Web server name using a registry setting. Follow the steps below to enable this feature:
1.
On the machine on which AEM is installed, select Run from the Windows Start menu.
2.
Enter regedit in the Open field and click OK. The Registry Editor is launched.
3.
Locate the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\DOCSExchange\Settings
4.
Double-click the value StubMailTemplateText. The Value Data field will be populated with the following string:
http://DMWebServerName/CyberDOCS/quickstart.asp?show=VIEW:
5.
Replace DMWebServerName with the name of your DM Web server.
6.
Click OK to save your changes.
Enhanced Logging for Automated E-mail Management (SR5)
Service Release 5 of DM 5.1.0.5 provides enhancements to the information provided in the log file for Automated E-mail Management (AEM). The following items have been added:
Support for the Unicode standard.
More detailed information is posted to the log file when the Automated E-mail Management service incurs an error due to, for example, a problem with a rule, or the DM server being down. In previous versions of AEM, information would be posted to the Event Viewer on the Microsoft Exchange server as well as the log file. This enhancement moves the pertinent information to the log file to be able to more readily associate an issue with the originating action.
DM Workflow
Document.Unpublish Event (SR5)
IN DM 5.1.0.5 Service Release 4, a Document.Unpublish event has been added for DM WorkFlow. Prior to SR4, DM WorkFlow provided a Document.Publish event but no corresponding Unpublish event.
Performance and Stability Enhancements to the Routing Agent (SR4)
The DM Workflow Routing Agent has been optimized to perform better and use less resources, with improvements made to stability and recovery in the event of a server disconnect.
Multilingual History Support for DM Workflow Extension (SR4)
DM Workflow Extension has been modified so that Workflow Task History information can be shown based on client language locale settings.
Multilingual Caption Support for DM Workflow Extension (SR4)
DM Workflow Extension has been modified so that DM Workflow captions are shown based on client language locale settings.
Interface Support of Language Specification on Multilingual DM Workflow Servers (SR4)
Installing the DM Workflow Server Language Pack and configuring DM Web Server language parameters.
1.
There are four language packs provided with Service Release 4:
"Lang Pack - Enc" for installing English Canadian language pack
"Lang Pack - Frc" for installing French Canadian language pack
"Lang Pack - Enu" for installing English language pack
"Lang Pack - Fra" for installing French language pack
1.1.
For Canadian English or French, go to the Service Release folder and locate the following folder(s):
n
..\DM Workflow\Lang Pack-ENC
n
..\DM Workflow\Lang Pack-FRC.
1.2.
For standard English or French, go to the Service Release folder and locate the following folder(s):
n
..\DM Workflow\Lang Pack-ENU
n
..\DM Workflow\Lang Pack-FRA.
2.
Double click on the setup.exe file located in the desired language pack folder(s). You will need to install both English and French language packs provided on your DM Workflow Server machine.
NOTE: Install both Canadian or both Standard language packs as appropriate to your DM configuration.
3.
Log on to the English DM Webtop as an administrator and configure User Symbols for English DM Web Server:
3.1.
In DM Web Admin>DM Webtop Maintenance>Custom Parameters, click Add and create a new parameter with the following information:
Name: WF_DEF_LANGUAGE
Value (Canadian English): ENC
Value (Standard English): ENU
3.2.
Save this parameter and log off DM.
4.
Log on to the French DM Webtop as DM Administrator and configure User Symbols for French DM Web Server.
4.1.
In DM Web Admin>DM Webtop Maintenance>Custom Parameters, click Add and create a new parameter with the following information:
Name: WF_DEF_LANGUAGE
Value (Canadian French): FRC
Value (Standard French): FRA
4.2.
Save this parameter and log off DM.
Ability to Log Workflow Extensions Connections (SR3)
The ability to log Workflow connection data is done through the registry on the Workflow Extensions client machine and can be configured to send the information to the NT Event Log, a disk file you specify, or both.
NOTE: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs.
These instructions apply to versions 5.1.0.5 SR2 and above of the DM Workflow Client.
1.
Start the Windows Registry Editor. Go to Start>Run and type regedit. Press ENTER.
2.
Go to Edit>Find and enter the following:
[HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\PowerDOCS\Core]
3.
Select the value to be modified and select Edit>Modify or double-click the value to open the Edit dialog box. The following values can be modified:
Name
Type
Data
Value
LoggerFile
REG_SZ
C:\Program Files\Hummingbird\DM Extensions\DMExtensions.log
You can accept the default LoggerFile location/file name or change the location/file name.
LoggerMask
REG_DWORD
0x00000001 (1)
By default, the LoggerMask value is 1, which puts the connection info in the NT Event Log. You can change it to these values:·
2. Log will be generated to the location specified in the LoggerFile entry·
3. Log will be generated to the location specified in the LoggerFile entry and to the NT Event Log.
EnableLogger
REG_DWORD
0x00000000 (0)
Change the EnableLogger entry to 1 to start logging connections.
NOTE: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Use Registry Editor at your own risk.
4.
Make the edit and click OK.
5.
Close the Registry Editor when finished.
Improved Speed to Retrieve List of Monitors or Performers in DM Workflow Extensions (SR2)
Programmatic changes have been made to speed up the response time.
DM Mobility
DM Mobility on RIM BlackBerry (SR3)
The use of DM Mobility on Research In Motion BlackBerry devices is now supported.
Configuring DM Mobility to support BlackBerry devices causes these changes when displaying e-mail messages and DM Attachments:
Only plain text is contained in the e-mail message. No HTML content is displayed. The embedded Hummingbird header image is not displayed.
MIME types are not used for DM Attachments. Attachments will not be associated with display or editing applications.
To enable DM Mobility support for BlackBerry devices, ensure that these items in the MailResources.inc file (located in DM Web Server\ServerComponents\ClassLibrary) are set as follows:
this.AllowHtmlInMailMessage = false;
this.AllowMimeTypeForDMAttachment = false;
The default setting for both items is "false". See the Hummingbird DM Me-Clips.html Readme file for instructions on setting other options in the MailResources.inc file.
DM Customization
Renaming Workspace and Public Folder Nodes in the Explorer View (SR5)
It is now possible to rename the Workspace and Public Folder nodes in the Explorer View of DM Extensions. To do this, edit the file Program Files\Hummingbird\DM Extensions\Patchresources6.ini and make the following changes:
To rename the Workspace node, edit the value for 16=string.
To rename the Public Folders node, edit the value for 18=string.
Save the changed file. The edited string will now appear in the Explorer view.
NOTE: This will only change the visible labels in the tree. It will not change any menu or search labels.
Return to Contents

Copyright © 2004-2006 Hummingbird Ltd.
Hummingbird Enterprise is a trademark of Hummingbird Ltd.
All other names used herein are trademarks of their respective owners. All rights reserved.
http://www.hummingbird.com/