April 2, 2015
Contents
1 Introduction .................................................................................................................................... 5
2 About OpenText eDOCS DM 5.3.1 Patch 6 .................................................................................. 5
2.1 New Features ............................................................................................................................ 5
2.1.1 DM Security Vulnerability Update (DM-32057) ............................................................ 5
2.1.2 Folder Metadata Inheritance (DM-9588) ...................................................................... 7
2.1.3 DM Footer Enhancements (DM-22572) ....................................................................... 7
2.1.4 Encrypted Email Support (DM-26423) ....................................................................... 12
2.1.5 DM API Support for the Advanced Search Interface (DM-26835) .............................. 12
2.1.6 DM Extension API Refresh Specific Frames (DM-27441) .......................................... 12
2.1.7 Request for DM 5.3 documentation on the DM Library Database Indexes.
(DM-28627) ................................................................................................................ 12
2.1.8 DM Interceptor Support for 64 Bit Applications (DM-28937) ...................................... 13
2.1.9 DM Content Cache – Pre-Cache Enhancement (DM-32278) .................................... 18
2.1.10 Search Across Multiple Libraries with Different Schema’s (DM-33169) ..................... 19
2.1.11 Office 2013 Translations (DM-33576) ........................................................................ 20
2.1.12 Outlook Startup Change – Delay Logon (DM-34435) ................................................ 20
2.1.13 Email Filing QuickFile Options (DM-34829) ............................................................... 20
2.2 Language-Neutral Patch .......................................................................................................... 21
2.3 Backwards Compatibility ......................................................................................................... 21
This is the latest patch for the eDOCS DM 5.3.1 release. Consult the eDOCS DM 5.3.1 Patch 1
Release Notes for complete information about the eDOCS DM 5.3.1 software.
Important
The eDOCS DM 5.3.1 Patch 1 is a complete ISO image and the baseline
install for the DM 5.3.1 version. This software can be applied as an
upgrade on top of DM 5.1.0.5, 5.2.1, 5.3 and 5.3.1. This software is also
the image to use for new installs of the DM 5.3.1 product line. If
upgrading from a release prior to DM 5.3.1 Patch 1, you must first
upgrade to DM 5.3.1 Patch 1 and then apply DM 5.3.1 Patch 6.
eDOCS DM 5.3.1 Suite Patch 6 is a cumulative update which contains all updates from previous
patches for each component.
For more information, refer to the Knowledge Base Article 58528481 or contact your local Customer
Support office.
The DM Server 5.3.1 Patch 6 update is installed with the fixes in the PCDServerIF.dll and
PCDClient.dll and configured to use the DM Security Token logic that addresses the security
vulnerability by default. This also requires that the DM client desktops contain the supplied DM API
PCDClient.dll if you want to continue to use DM Extensions with the Allow Auto Logon feature
enabled.
If you are not able to update your DM Extensions in a short period of time and want to keep the Auto
Login feature enabled for the DM Extensions in your environment, perform the following.
The DM Server can be configured not to use the new DM Security DST logic and continue to use the
Auto Login feature with the previous DM extension clients.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hummingbird\DOCSFusion\Security
Note:The DM Server DisableSecureDST setting needs to be set back to 0 as soon as you have
updated your DM Extensions with 5.3.1 Patch 6.
This functionality can be enabled by setting the following registry on the client desktop:
DWORD "InheritAuthorDocType" registry key and set the value to 0 to not inherit the Author
and Document Type fields.
HKEY_CURRENT_USER\Software\Hummingbird\PowerDOCS\Core\Plugins\Fusion\Settings
If this key is not present or present and set to 0, DM Extensions will continue to inherit the Author and
Document Type from the folder.
Note: The eDOCS DM 10 version includes additional functionality for controlling metadata inheritance
where the DM administrator can define additional fields that they do not want to inherit from a folder.
See the eDOCS DM 10 Release Notes for additional details.
To insert a DM footer:
Notice that as you select the check boxes, the associated XML text dynamically populates in the text
pane. You can edit the XML by clicking the Edit check box.
Document Number
Document Version
Document Name
Page Numbers – This allows you to insert page numbers. You can use RIGHT, CENTER, and
LEFT for page number alignment.
Document Author
Document Type
Application
Font – This allows you to specify the font name and size. You can use any font and size that
Word recognizes.
Description
Date
Library
Text – This allows you to insert customized text.
Tip: To select all items, select the Select All check box.
Conversely, to clear all items, select the Select All check box twice. Or, select the XML text and
delete.
In the XML text, you can change the font, page number alignment, and the field alignment. You can
use NewLine, Tab, or None for field alignment.
Note: The order you select the check boxes determines the order of appearance in the DM footer.
4. When you select the Edit check box, the Validate XML link becomes available. Click this to
validate the XML text. If successful, a green circle with a check mark appears; if unsuccessful,
a red circle with an exclamation point appears. Hover your mouse over the red circle to view
additional error details.
5. Select the Auto-Update check box to make the application update the footer when new
versions, subversions, or new documents are created within the application.
6. Select the Don't show this dialog check box to bypass this dialog box and use the selected
settings for subsequent footers.
7. Click OK. The footer information appears at the bottom of each page.
8. To edit the footer, click INSERT>Footer>Edit Footer.
The PAGENUMBERS portion of the XML includes the following attributes: FONT, SIZE, TEXT1, and
TEXT2.
To insert a DM footer:
Tip: To select all items, select the Select All check box.
Conversely, to clear all items, select the Select All check box twice. Or, select the XML text and
delete.
In the XML text, you can change the font, page number alignment, and the field alignment.
Note: The order you select the check boxes determines the order of appearance in the DM footer.
4. When you select the Edit check box, the Validate XML link becomes available. Click this to
validate the XML text. If successful, a green circle with a check mark appears; if unsuccessful,
a red circle with an exclamation point appears. Hover your mouse over the red circle to view
additional error details.
5. Select the Auto-Update check box to make the application update the footer when new
versions, subversions, or new documents are created within the application.
6. Select the Don't show this dialog check box to bypass this dialog box and use the selected
settings for subsequent footers.
7. Click OK. The footer information appears at the bottom of each page.
8. To edit the footer, click INSERT>Footer>Edit Footer.
The PAGENUMBERS portion of the XML includes the following attributes: FONT, SIZE, TEXT1, and
TEXT2.
The DM API has been enhanced to present the user with the Advanced Search interface instead of
the custom interface when they perform an Advanced Profile Search.
The DM Extensions API has been enhanced to support updating the frame/view that has the current
focus.
A 'RefreshREDView' property has been added to use in DOVerb calls so that Application Integration
code can call this right after the QuickSave API call.
The eDOCS DM 5.3.1 Administration Guide has been updated with the following chapters:
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/26345148
When applying the DM Extensions (x64) Patch 6, the 64 bit version will be installed in conjunction
with the 32 bit Interceptor application.
HKEY_CURRENT_USER\Software\Hummingbird\PowerDOCS\AppIntegration\Interceptor
HKEY_CURRENT_USER\Software\Hummingbird\PowerDOCS\AppIntegration\Interceptor_x6
4
The Windows Task tray will show the DM icon, the 32 bit Interceptor, and the new 64 bit Interceptor
icon with the number 64 as an overlay on the icon.
NOTE: The Interceptor 64 bit version only integrates with 64 bit applications. The Interceptor 32 bit
version still needs to be used to intercept 32 bit applications.
Note: This example shows C:\Windows\Notepad.exe which is the 64 bit version of the application. If
you previously integrated the 32 bit version of Notepage the settings would be
C:\Windows\System32\Notepad.exe.
3. From the DM Extension select Right Click on the Interceptor 64 bit icon
12. Select OK
13. Select Save As
14. Select Edit and confirm the properties
15. Select the Launch Methods tab
16. Select Notepad
19. The Notepad application will have a green status indicator and is ready to intercept the
Notepad commands.
The DM Extensions user interface is used to create the searches that will be used by the content
cache pre-population process. Simply define the search as you would any other search and save the
search to the library. You might want to rename the search so that its purpose is more clearly visible
within the user interface. The search must then be added to the content cache registry to be picked
up by the pre-population process (see below).
The eDOCS DM 5.3.1 software release does not provide an administration user interface for the
content cache pre-population feature. To enable the process the following registry keys/values must
be added. These values only need to be added to a single server with content cache installed. In
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hummingbird\DOCSFusion\Content
Cache
PreCache
A String value that can be set to either “Enabled” or “Disabled” to turn the pre-cache process
on or off. The default is “Disabled.”
PreCache Time
A String value that contains a time in 24-hour format at which the pre-population process
should execute. For example “02:30” means that the pre-population process will run at 2:30
AM each day. The default is “00:00” (Midnight).
PreCache Search List
A Multi-String value containing a list Library/QuickSearch or */QuickSearch pairs that will be
used to select documents to be added to the content cache directory. For example,
“EXLIB1/MS WORD,Test” where “EXLIB1” is the library name and “MS WORD,Test” is the
name of a quick search that will select all MS WORD documents with the word ‘Test’ in the
document content.
The */QuickSearch format is used to specify that a QuickSearch of the given name resides in
more than one library and the pre-cache process should execute the QuickSearch for each
library within which the QuickSearch resides. The actual QuickSearch definition does not
have to be the same in each library, just the name. The search for each library is executed
individually so the actual QuickSearch definition can be tailored to the library within which it
resides.
The recommendation when setting up multiple Libraries to be remote to each other is to always use
the same schema and Library type (Legal with Legal) for this type of configuration to allow the users
to perform searches across all the Libraries.
In environments where the Library schemas do not match you will now be able to perform a search
across multiple Libraries instead of receiving an error message relating to the different SQL
structures.
The translated files for Dutch, French, German, Italian and Spanish are included.
Installation
20. The AppTrans.ini and AppTrans1.ini files replace the English ones that were installed with
the eDOCS DM 5.3.1 Office 2013 Integration v2.2 (x64) or (x86).MSI installation
21. Copy the translated AppTrans.ini and AppTrans1.ini files to the C:\Program Files (x86)\Open
Text\DM Extensions directory and replace the existing versions
22. Copy the EIRes.dll to the C:\Program Files (x86)\Open Text\DM Extensions\EMail Integration
directory and replace the existing file
23. Restart the Office Applications and DM.exe.
The eDOCS DM 5.3.1 Silent Install Samples document provides additional information on the
scripting and configuration options that can be used for silent deployments. This document can be
referenced for modifying the eDOCS DM 5.3.1 Office 2013 Integration v2.2 (x64) or (x86).MSI
programs to include the translated files for your respective language.
https://knowledge.opentext.com/knowledge/cs.dll/Open/26411687
The Delay Logon feature can be configured by the following registry key:
HKEY_CURRENT_USER\Software\Hummingbird\EMail Integration\1.5\Settings
DelayLogon (DWORD) -> 0:off/ 1:on
If the logon dialog box is canceled, then the user will not have the opportunity to log into DM
Extensions until Outlook has been restarted.
When using the DM Extension for Outlook and Email Filing together users can drag and drop emails
from Outlook to DM, or save to a DM Folder using the QuickFile feature and the emails would be
copied to the Email Filing Service and saved into DM in the background.
The Registry setting to control this with DM 5.3.1 Patch 5 and Email Filing 4.2:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Hummingbird\EMail Integration\1.5\Settings
With this setting if the Exchange Cached Mode setting was disabled in Outlook the save was
successful but the user receive a warning message that the operation “Can’t move the items” from
Outlook.
SaveToEmailFiling = 2 Save using Email Filing with Exchange Cached Mode disabled in
Outlook.
This configuration option no longer presents the user with the “Can’t move the items” warning
message.
Note: The new Unicode metadata feature for profile fields is not enabled by default
because it is not backwards compatible with the previous versions of DM Extensions. If
you upgrade the DM Server and Library to support this new feature, you can only use
DM 5.3.1 Patch 1 (or later) Extensions in the environment.
Note: The DM 5.3.1 Patch 1 Installer Update.exe runs updates against the Patch 1 *.msi
that will reflect the correct Patch number in the install dialog. This update needs to be run
prior to running any of the updates included in Patch 6 if you are upgrading from DM 5.3.1
Patch 1. If you have previously run the DM 5.3.1 Patch 1 Installer Update.exe while applying
Patch 2 or later you do not need to run this update again with patch 6.
Note: The DM Web Server Installer Update.exe runs updates against the 5.3.1 Patch 1
*.msi that corrects an issue uninstalling the Webtop Server. This update needs to be run
prior to running the DM Web Server Patch 6.msp if you are upgrading from DM 5.3.1 Patch
1. If you have previously run the DM Web Server Installer Update.exe while applying Patch
2 or later you do not need to run this update again with patch 6.
eDOCS DM 5.3x This new guide contains a comprehensive list of registry keys and
Registry Settings settings used with DM 5.3x. This standalone guide is available at the
following location:
https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=408
37074&objAction=Download
eDOCS DM 5.3.1 The eDOCS DM 5.3.1 Administration Guide has been updated with the
Administration following chapters:
Guide
APPENDIX H: Microsoft SQL Table and Index Listing
APPENDIX I: Oracle Table and Index Listing
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/26345148
When documentation is updated, new guides are posted immediately to the location listed above. The
Knowledge Center will always contain the most recent updated guides.
To perform a Rollback of a DM patch from the Control Panel’s Program and Features, you will need to
select the Show Updates check box on the window dialog, and then select the respective Open Text
eDOCS module. The patch that is currently applied will appear under the selected item; select the
Uninstall option to uninstall the Patch.
If upgrading from a DM 5.3.1 Web Server that has already been upgraded to Patch 3 or
greater, you can apply the DM 5.3.1 Web Server Multilingual Patch 6.
If upgrading from an initial DM 5.3.1 Web Server Patch 1 or installing a new Web Server
1. Installs the eDOCS DM 5.3.1 French Web Server.msi (Patch 1) (Or other translated
language)
2. Run the DM WebServer Installer Update.exe
3. Apply the eDOCS DM 5.3.1 Web Server Multilingual Patch 6.msp
Server Roles:
Application Server
.NET Framework 4.5
COM+ Network Access
Web Server (IIS) support
Web Server (IIS)
Web Server
Application Development
.NET Extensibility 3.5
.NET Extensibility 4.5
ASP
ASP.NET 3.5
ASP.NET 4.5
ISAPI Extensions
Server Side includes
Features:
3. Restart IIS.
http://www.microsoft.com/en-us/download/details.aspx?id=20479
http://www.microsoft.com/downloads/details.aspx?familyid=59DAEBAA-BED4-4282-A28C-
B864D8BFA513&displaylang=en
If Office 2010 is already installed on the computer, go to the Control Panel, select Program and
Features, then select Office 2010>Change. Select the sub-item “.NET Programmability Support” for
the installed Office applications.
For DM 5.3.1 Patch 1 and later, Application Integration requires that the Office 2010 Primary Interop
Assemblies be installed on the user’s desktop for the DM integration to work.
1. Double-click the eDOCS DM 5.3.1 Suite Patch 6.msp file for the component you want to install
(for example, the eDOCS DM Server 5.3.1 Patch 6.msp).
2. Complete the installation.
If you double-click the *.msp file, the Windows Installer Shell dialog box will appear with the option to
Change, Repair, or Remove. To apply the patch, click Repair.
4. If you want the installation progress bar to appear, type the following:
Note: The above file names are examples and should be replaced by the actual file name,
depending on which component is being applied.
For more information about eDOCS DM 5.3.1 and the Microsoft Windows Installer (MSI), refer to the
Champion Toolkit document "eDOCS DM 5.3.1 MSI Silent Install Samples" located here.
5.1.1 DM Server
1
For Optimal SQL server performance, we recommend a dedicated server-class machine with a
minimum of 2GB of RAM.
2
OpenText will support customers who run DM products on supported operating systems, irrespective
of whether they are running in a virtual environment or not.
OpenText supports "operating systems," not specific hardware configurations. Accordingly, OpenText
does not explicitly support the virtualization application since it operates as a hardware abstraction
layer.
The virtualization applications, such as VMware, Microsoft Hyper-V and Citrix XenServer, support a
set of certified operating systems and hardware, and the customer and the virtualization vendor will
be responsible for any interactions or issues that arise at the hardware or operating system layer as a
OpenText will not require customers to recreate and troubleshoot every issue in a non-virtual
environment; however, OpenText does reserve the right to request our customers to diagnose certain
issues in a native certified operating system environment without the virtual environment. OpenText
will only make this request when there is reason to believe that the virtual environment is a
contributing factor to the issue.
While DM products are expected to function properly in virtual environments, there might be
performance implications, which can invalidate DM's typical sizing and recommendations. Analysis
must be performed within the context of the specific application to be hosted in a virtual environment
to minimize potential resource contention, which can have significant impact on performance and
scalability, particularly under peak load.
Microsoft Word 2003 3 ,2007, 2010 (32 and 64 bit), 2013 (32
and 64 bit), 2013/365 subscription with the
desktop clients (32 and 64 bit)
Microsoft Excel 2003 3 ,2007, 2010 (32 and 64 bit), 2013 (32
and 64 bit), 2013/365 subscription with the
desktop clients (32 and 64 bit)
Microsoft PowerPoint 2003 3 ,2007, 2010 (32 and 64 bit), 2013 (32
and 64 bit), 2013/365 subscription with the
desktop clients (32 and 64 bit)
Microsoft Project 2003 3 ,2007, 2010 (32 and 64 bit), 2013 (32
and 64 bit), 2013/365 subscription with the
desktop clients (32 and 64 bit)
Microsoft Visio 2003 3 ,2007, 2010 (32 and 64 bit), 2013 (32
and 64 bit), 2013/365 subscription with the
desktop clients (32 and 64 bit)
Adobe Reader and Acrobat (Interceptor) X4, XI4
Adobe Reader and Acrobat (Passive) X4, XI4
Freedom Scientific JAWS 15
Dragon Naturally Speaking 10.1 and 12
Corel Presentations X3 and X5
Corel Quattro Pro X3 and X5
Corel WordPerfect X3 and X5
Lotus 1-2-3 9.7 and Millennium Edition 9.8
Lotus Word Pro 9.7 and Millennium Edition 9.8
3Although Microsoft Office 2003 is listed as a supported application for DM 5.3.1 Patch 6, we have
performed minimal testing with Microsoft Office 2003 and determined that integration is possible. The
OpenText encourages customers to upgrade to Microsoft Office 2010; however, if that is not possible,
we will continue to accept support cases from customers using DM 5.3.1 Patch 6 with Microsoft Office
2003.
4As of eDOCS DDM 5.3.1 Suite Patch 4, Adobe Reader and Adobe Acrobat version X and XI are
supported using Passive Integration. Integration using the DM Interceptor module is still available for
9.0, X, and XI.
Microsoft Outlook 2003 3 ,2007, 2010 (32 and 64 bit), 2013 (32 and
64 bit), 2013/365 subscription with the desktop
clients (32 and 64 bit)
Lotus Notes 5 7.0.4, 8.5.3
Novell GroupWise 7.0, 8.0
3 Although Microsoft Office 2003 is listed as a supported application for DM 5.3.1 Patch 6, we have
performed minimal testing with Microsoft Office 2003 and determined that integration is possible. The
new Unicode feature in DM 5.3.1 is not available with Office 2003 in the environment and you will be
required to upgrade to a more current version of Microsoft Office to enable the Unicode feature.
5 The DM Extension for Lotus Notes, which provides Drag and Drop from the user’s inbox to the DM
Node in the left hand pane tree view, is supported only in the Notes Basic client. The Notes Eclipse
client supports the small footprint email integration that does not support Drag and Drop.
OpenText Records Management for eDOCS Enterprise Library Services 10.2.1, 10.5
6 Fixed Issues
You can find the issues that have been resolved in this release by searching the Open Text
Knowledge Base for “5.3.1 Suite Patch 6” or “This issue is resolved in DM 5.3.1 Suite Patch 6” from
https://knowledge.opentext.com/knowledge/llisapi.dll/open/12678460.
You will also need to clear the check box for All Products and select the DM RM check box for your
search.
https://knowledge.opentext.com/knowledge/llisapi.dll/open/11568658
DM Server Web Services The DM Server Web Services API requires that the user supply
Auto Login credentials from custom applications that use this integration method
due to the changes that were required to address the DM Security
Vulnerability Update (DM-32057).
DM Interceptor 32 bit and The eDOCS DM 5.3.1 Patch 6 includes a 64 bit Interceptor version to
64 bit application support integrate 64 bit applications with DM. The 64 bit version only
intercepts 64 bit applications. The Interceptor 32 bit version still
needs to be used to intercept 32 bit applications.
DM Designer – Custom If you add a custom filter to the "DOCUMENT TYPE" lookup to
Filter is ignored when remove a specific Document Type from the list like “Folder” and then
dragging to a folder and use the custom form in the DM Extensions and you manually type the
inheriting DOCUMENT value "FOLDER" it is not accepted in the DOCUMENTTYPE Field.
TYPE ( DM-34139)
The DM client raises the standard error:
Content Suite10.5 - This issue does not occur with a Microsoft SQL database this issue
Unable to make only occurs with an Oracle database for the DM Library.
documents read-only
when the read-only We are still investigating the issue for an Oracle environment.
document server
operating system is
“OTRM for eDOCS using
EL / OTDS”
DM-33126
DM Extensions MSI for The integration file is missing from the DM 5.3.1 Patch 1 master
Microsoft Office, the installer.
macro
DMIntegration_2010.ppa The missing file is available here on the Knowledge Center
Possible delay while A potential delay up to 2 seconds may be observed when typing text
typing text on search form into a search form. After typing 2 or 3 characters, the text may not
(DM-32269) appear for a few seconds. This issue is only observed with Windows
8 and Windows 8.1 Operating Systems and client machines with an
I7 processor.
Potential memory leak A potential memory leak has been found within .NET Framework 4.0
with .Net Framework 4.0 which, in turn, affects the DOCSFusion process. An upgrade to .Net
4.5 on all DM servers where the operating system permits will resolve
the issue.
DM Imaging Does Not If an Imaging document has any double-byte characters in the
Support Unicode (DM- document name, the file is never uploaded on a Save, resulting in a
28459) zero byte file.
Outlook Logging Does Not When enabling Outlook Logging in the Client Deployment Utility
Work when Enabled in the (CDU), the log file will not be created.
Client Deployment Utility
Steps to Reproduce:
Workaround:
HKLM\SOFTWARE\Wow6432Node\Hummingbird\PowerDOCS\Outlo
ok Client
For 32-bit operating systems, this should be in same place minus the
‘wow6432node’ portion.
Workaround:
Resolution:
Error:
Workaround:
<ProfileSelectComboVisible>True</ProfileSelectComboVisible>
<ProfileFormComboEnabled>False</ProfileFormComboEnabled>
When editing existing Profiles, if you want the user to see the Profile Form selection, but not be able
to edit it, use the following settings:
8.1.9 Document Attachments Open with Launch Method for the Attachment
Type Rather than the Parent Launch Method
As of eDOCS DM 5.3.1 Patch 1, you can now open an attachment to an eDOCS DM document with
the attachment's launch method, rather than using the attachment's parent launch method. For
example, if you perform a Compare operation on a Microsoft Word document and save the results as
a PDF file (as an attachment to the Word document), when you open it within the DM Extensions, the
attachment opens in Adobe Acrobat instead of Word.
The eDOCS DM app can be downloaded from the Microsoft App Store at this location:
http://apps.microsoft.com/windows/en-us/app/opentext-edocs-dm-app/ff224079-0aef-402e-a6f4-
d43c092bc751/m/ROW
Note: The installation of Passive Integration for Adobe Acrobat and Adobe Reader is a
manual process and is not part of the Suite Patch 4 MSP’s for eDOCS DM Explorer
Extensions.
You will need to manually add the eDOCSAcrobat.api/eDOCSReader.api file to the Adobe
directory. Locations for each supported version are listed below:
To achieve successful integration with Adobe Acrobat and Adobe Reader with eDOCS DM 5.3.1 Patch
4, the following launch method settings need to be configured, which are also available in the eDOCS
DM Administration Guide.
Topic Name:
Command:
Command: Print
Note: You must disable the Acrobat splash screen (which shows recently edited documents)
by creating the cWelcomeScreen registry key and a new DWORD value,
bShowWelcomeScreen in HKLM\SOFTWARE\Policies\Adobe (product name)
(version)\FeatureLockDown\cWelcomeScreen\bShowWelcomeScreen. Set the
bShowWelcomeScreen value to 0.
You must disable the Protected View feature in Acrobat; otherwise, native dialogs will appear
instead of eDOCS DM dialogs.
To disable Protected View:
In Acrobat Pro 11, select Edit>Preferences>Security (Enhanced), and then set Protected
View to Off.
In Acrobat Reader 11, select Edit>Preferences>Security (Enhanced), and then clear the
Enable Protected Mode at startup check box.
In Acrobat Reader 10, select Edit>Preferences>General, and then clear the Enable
Protected Mode at startup check box.
Important
Microsoft SQL Server 2005 does NOT support this multi SQL insert
capability introduced in Suite Patch 4 and needs to be disabled. To
disable this feature the following DWORD value needs to be added to the
registry on all DM Servers in the environment:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Hummingbird\Docsf
usion\NoForInsertMultiples=0
NoForInsertMultiples (DWORD)
This number defines the default behavior for how we handle Full Text
searching when inserting temporary rows into the FULLTEXT_JOIN table.
This value is active by default (even when the key is absent). To disable
the multi insert mode set this value equal to 0.
Value = 0 – indicates that all full text joining records will NOT use
batching of INSERT commands
Value > 0 – indicates that full text joining, will use batch SQL INSERT
statements – and the value indicates the size of the INSERT batch
This value indicates the size of the batch inserts (max. 1000 – anything
higher than 1000 will use 1000). The default value is 1000.
If the multi-value attribute is missing from the application-metadata.xml file, the data will be stored
as a string in Content Server rather than multi-value fields.
For more information on the configuration of the application-metadata.xml file, please refer to the
Open Text Records Management Integration with eDOCS DM Version 1.0 Installation and
Configuration Guide:
https://knowledge.opentext.com/knowledge/cs.dll/open/20452288
8.5.2 Ability to Hide Document Type in Dynamic Views for Groups and Not
Only Users
Prior to eDOCS DM 5.3.1 Suite Patch 5, in Dynamic Views DM Extensions you can hide Document
Types on a user by user basis. As of eDOCS DM 5.3.1 Suite Patch 5, the ability to hide Document
Types for a group is now available and supported.
NOTE: Manual manipulation of the eDOCS DM Database is required to use this new feature.
In the eDOCS DM Database, in the Subscriptions table, the PERSONORGROUP column which
currently holds the ID of the user that the Document Type is hidden for needs to be updated with the
ID of the group that will now have the Document Type hidden.
Email: support@opentext.com
Knowledge Center: https://knowledge.opentext.com
Copyright ©2013 Open Text Corporation. Visit online.opentext.com. OpenText is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not exhaustive of other
trademarks, registered trademarks, product names, company names, brands and service names mentioned herein are property of Open Text SA or other respective owners.
49