Autonomy Records Manager 12.6.2 Update 7 Release Notesh30359. Governance/Autonomy... · Autonomy...

R E L E A S E N O T E S

8-Oct-14 Copyright 2014 Autonomy Corporation plc and all its affiliates. All rights reserved.

Autonomy Records Manager ™

Release Notes 12.6.2 Update 7

This document describes new features and resolved issues for Autonomy Records Manager Version 12.6.2 Update 7.

Contents

Documentation ..................................................................................................... 4

New in This Release ............................................................................................ 5

New in Release 12.6.2 Update 7 .................................................................... 5

Support for Exchange 2013 ...................................................................... 5

Resolved Issues--ARM 12.6.2 Update 7 ......................................................... 6

New in Release 12.6.2 Update 6 .................................................................... 8

Support for Windows Server 2012 ............................................................ 8

Support for Windows 8 and 8.1 ................................................................ 8

Support for Office 2013 ............................................................................. 8


2 Autonomy Records Manager ™ Release Notes

Support for Lotus Notes 9 ......................................................................... 9

Resolved Issues--ARM 12.6.2 Update 6 ......................................................... 9

New in Release 12.6.2 Update 5 .................................................................. 10

Warehouse Integration Support for Oracle ............................................. 10

Outlook Integration - Duplicate Filing Markings ...................................... 11

Resolved in Autonomy Records Manager 12.6.2 Update 5 ................... 11


New Warehouse Integration Functionality .............................................. 12

Web Interface Security Enhancements .................................................. 12

Control of Manual Uploads in the Web Interface .................................... 13

Support for SQL Server 2012 ................................................................. 13



Support for WorkSite 9.0 ........................................................................ 15

Copy as New Version in WorkSite Integration ........................................ 15

Support for IDOL DiSH License .............................................................. 16

Modify Records On Hold in Desktop ...................................................... 16

Configurable Sender for Repository Management Service Notification . 16

Support for Crystal Reports on 64-bit Workstations ............................... 16



Copy Documents from Browse Tab to Another Location ....................... 24

Refresh Detail Pane After Changes in Detail Window ........................... 24

Automatically Exclude On-Hold Items from Disposition ......................... 25

Set Preferences for Default Printers ....................................................... 25

New Features for Outlook and Exchange Integration............................. 25

Autonomy Records Manager IDOL Integrity Check ............................... 27

Customizable Label for File To Button ................................................... 27

Support for Symbol MC-75 Hand-held Scanner ..................................... 27

Disposition Workflow Integration with APA ............................................. 27

Autonomy Records Manager CFS Connector ........................................ 28

Resolved in Autonomy Records Manager 12.6.2. Update 2 .................. 28

Documentation Updates ......................................................................... 31

Documentation

Autonomy Records Manager ™ Release Notes 3


Microsoft .NET Framework 4 Required .................................................. 31

Option for Persistent Expanded Desktop User Detail Tabs View ........... 32

Custom Dictionary for Spell Checking .................................................... 32

Global Security Set Append Option ........................................................ 32

Create a New Document With a Default Media Type ............................. 33

Inactivate Rooms Option ........................................................................ 33

New Field for Category Full Code........................................................... 34

Reverse Option for Lookups ................................................................... 34

Table Field Information Displayed on Template Tab View ..................... 34

New Procedures for Upgrading from Previous Versions ........................ 34

Changes to Existing Features in Release 12.6.2 Update 1 .......................... 34

Installation Setup Enhancements ........................................................... 34

Indicator for Protected Date Fields ......................................................... 35

Copy Auto-Declared Messages .............................................................. 35

Users Can Manage Outlook Preferences ............................................... 35

Outlook Privilege Controls Enhancements ............................................. 35

Document Import Utility Enhancements ................................................. 36

New in Release 12.6.2 .................................................................................. 36

IDOL Replaces dtSearch Indexing Engine ............................................. 36

Support for Windows Server 2008 R2 .................................................... 36

Support for SQL Server 2008 R2............................................................ 36

Support for Windows 7 ........................................................................... 37

Support for Exchange 2010 .................................................................... 37

Support for Office 2010 ........................................................................... 37

Support for SharePoint 2010 .................................................................. 37

Support for Lotus Notes 8.5 .................................................................... 37

Display a Tree View in the Detail Pane of the Desktop User Interface .. 37

Automatically Attach a Crystal Report to an Email ................................. 38

KeyView Support for Viewing Record Information .................................. 38

Report Tab .............................................................................................. 38

Requirements ..................................................................................................... 38

Application Server ......................................................................................... 38



Hardware ................................................................................................ 38

Database Server ........................................................................................... 39

Hardware ................................................................................................ 39

Web Server ................................................................................................... 40

Hardware ................................................................................................ 40

Workstations .................................................................................................. 40

Hardware ................................................................................................ 40

Autonomy Records Manager Indexer Deployment ....................................... 41

Documentation You can retrieve the most current product documentation from Autonomy’s Knowledge Base on the Customer Support Site.

A document in the Knowledge Base displays a version number in its name, such as IDOL Server 7.5 Administration Guide. The version number applies to the product that the document describes. The document may also have a revision number in its name, such as IDOL Server 7.5 Administration Guide Revision 6. The revision number applies to the document and indicates that there were revisions to the document since its original release.

It is recommended that you periodically check the Knowledge Base for revisions to documents for the products your enterprise is using.

To access HP Autonomy documentation

1. Go to the HP Autonomy Customer Support site at

https://customers.autonomy.com

2. Click Login.

3. Type the login credentials that were given to you, and then click Submit.

The Knowledge Base Search page opens.

4. Search or browse the Knowledge Base.

■ To search the Knowledge Base:

In the Search box, type a search term or phrase and then click Search.

New in This Release


■ To browse the Knowledge Base:

Leave the Search box empty and click Search. On the resulting page, select one or more of the categories in the Browse list. You can browse by:

– Repository. Filters the list by Documentation produced by technical publications, or Solutions to Technical Support cases.

– Product Family. Filters the list by product suite or division. For example, you could retrieve documents related to the iManage, IDOL, Virage or KeyView product suites.

– Product. Filters the list by product. For example, you could retrieve documents related to IDOL Server, Virage Videologger, or KeyView Filter.

– Version. Filters the list by product or component version number.

– Type. Filters the list by document format. For example, you could retrieve documents in PDF or HTML format. Guides are typically provided in both PDF and HTML format.

– Format. Filters the list by document format. For example, you could retrieve documents in PDF or HTML format. Guides are typically provided in both PDF and HTML format.

5. To open a document, click its title in the results list.

To download a PDF version of a guide, open the PDF version, click the Save icon in the PDF reader, and save the PDF to another location.

To download a documentation ZIP package, click Get Documentation Package under the document title in the results list. Alternatively, browse to the desired ZIP package by selecting either the Packages document Type or the ZIP document Format from the Browse list.

New in This Release This section lists the enhancements to Autonomy Records Manager.

New in Release 12.6.2 Update 7

Support for Exchange 2013

Autonomy Records Manager is certified for Microsoft Exchange 2013.



Resolved Issues--ARM 12.6.2 Update 7

This section lists the resolved issues to Autonomy Records Manager Version 12.6.2 Update 7. Reference Number

Description

17128

Users without override security unable to insert boxes or folders in any matter. This was resolved.

17126 Not able to open declared documents that were declared through the webclient. This was resolved.

17123 Not able to create folder in the web client when Office Security is enabled but office ID is null for the matter. This was resolved.

17121 Autodeclaration does not allow a user to file to a folder on hold. This was resolved.

17120 Incorrect return results occur if a query has keywords in lower case for Oracle db. This was resolved.

17119 For the Scan for Retention > Destroy option, after scanning the Jacket with a virtual/electronic document the ARM client crashes. This was resolved.

17118 Courier Email Subject for delivery report is hardcoded to start with the word 'ARM.' This was resolved.

17117 Export from browse does not have Excel option for Office 2013. This was resolved.

17115 The Web client uses office security for employees and rooms even though Office security is turned off. This was resolved.

17114 The Archive form associates a foreign barcode with an existing box when it should create a new box. This was resolved.

17113 Move Document to Folder using Desktop Client removes rule. This was resolved.

17112 Rule is not Inherited by documents created using the Web Client. This was resolved.

17111 No error message in Desktop Client when trying to circulate object to user without rights. This was resolved.

17110 No error message in Web Client when trying to circulate object to user without rights. This was resolved.

17109 Error clicking Cancel in folder wizard. This was resolved.

New in This Release


Reference Number

Description

17108 Universal Import routine generates an error when importing categories. This was resolved.

17107 12.6.2.6 w3fs.dll access denied when trying to print a label to the labeler. This was resolved.

17106 Problem mapping to WorkSite field Last_seen(nrAccess_time). This was resolved.

17104 Crystal Web site does not update data for reports. This was resolved.

17103 User with CheckOut Record On Hold rights unable to change folder status to Circulating on Detail screen. This was resolved.

17102 User must select folder to Efile even though the selected location is populated with the newly created folder. This was resolved.

17098 Account Summary Report fails to launch in Desktop client. This was resolved.

17095 Files on-hold could be deleted if the hold was on the matter. This was resolved.

17091 Data from Date field not always saved when creating a folder. This was resolved.

17089 Worksite Integration: Allow folder matrix filing without folder synchronization. This was resolved.

17087 New members added to group on the group form are not saved after sorting members. This was resolved.

17086 Exchange autodeclaration causes message of message class: IPM.Note.SMIME.MultipartSigned not to open after being filed. This was resolved.

17085 Lotus Notes - Email with large attachment fails with out of storage error. This was resolved.

17077 Boxes can be checked out on the Scan > Checkout form to users who do not have rights to the box. This was resolved.

17070 Security not updated for matters updated by CMS Import. This was resolved.

17064 Report on Sessions Form Results Tab incorrect for Disposition with Process Candidates Only. This was resolved.

17061 Redweld tab on Folder form > Reldweld is not red. This was resolved.



Reference Number

Description

17056 Login Name not converted to upper case on insert of new user. This was resolved.

17050 Opening a Word document can cause an fsoffice run-time error 5. This was resolved.

17048 The Last Modified Date not updated for a rule. This was resolved.

17045 'Check Rule' is not enabled on the Session Results tab when Disposition Mode is set to Partial Disposition. This was resolved.

17037 The Inspector email that is sent out with the link to the session report contains grammatical/ spelling errors. This was resolved.

17035 Client identity not updated when Client Num for matter is updated by Aderant import. This was resolved.

17032 Autodeclare does not check for duplicate emails when declaring a message. This was resolved.

17031 In the Web Client, users can create boxes in a category to which they do not have place rights. This was resolved.


Support for Windows Server 2012

Autonomy Records Manager is certified for Microsoft Windows Server 2012 for the following editions: Datacenter, Standard, and Server Core.

Support for Windows 8 and 8.1

Autonomy Records Manager is certified for Microsoft Windows 8 and 8.1.

Support for Office 2013

Autonomy Records Manager is certified for Microsoft Office 2013.

New in This Release


Support for Lotus Notes 9

Autonomy Records Manager supports IBM Lotus Notes 9.

Resolved Issues--ARM 12.6.2 Update 6


Description

17081 Keyview reversed the orientation of some PDFs from portrait to landscape, or landscape to portrait. This was resolved.

17080 The Detail column was set to F6O for redweld_id but the Lookup Query was missing the dbo.fn_file_numb_numc(redweld_id). This was resolved.

17079 The Main client asked for a room when a request for a box or folder was made, even though the user had a room. This was resolved.

17078 The Request dialog showed the user's emp_id instead of the full name. This was resolved.

17077 Boxes could be checked out on the Scan > Checkout form to users who did not have rights to the boxes. This was resolved.

17069 Pleadings document sequence numbers were incorrect for documents Inserted using the Web Client. This was resolved.

17068 The Detail view automatically closed when an object was Inserted from the Browse tab. This was resolved.

17067 Users could approve destruction even though that permission was unchecked. This was resolved.

17066 An open parenthesis in a DisplayName without a closing parenthesis caused an exception and failure of AD Import. This was resolved.

17065 The Documents Duplicate button was not functioning. This was resolved.

17064 The Report on Sessions form Results tab was Incorrect for Disposition with Process Candidates Only. This was resolved.

17061 For the Redweld tab on the Folder form, the Reldweld was not red. This was resolved.



Reference Number

Description

17060 The Office was not updated for documents in a folder when the office of the folder was changed. This was resolved.

17056 The login name was not converted to upper case on the insert of a new user. This was resolved.

17055 The logout link in the Web Client title bar for SiteMinder Integration was removed. This was resolved.

17050 The opening of a Word document could cause an fsoffice run-time error 5. This was resolved.

17048 When a rule was updated, the Last Modified Date was not updated for the rule. This was resolved.

17047 A multi-box create action did not propagate security to all boxes. This was resolved.

17046 When a user exited the main client, the dialog refered to CA Records Manager. This was resolved.

17045 When a disposition was run, the Check Rule option on the Session Results tab was not checked. This was resolved.

17039 The Web Client allowed users to file documents to closed folders. This was resolved.

17037 There were grammatical errors in the Inspector job email message. This was resolved.

17032 Autodeclare did not check for duplicate emails when declaring a message. This was resolved.

17031 Security limitations were not respected in the Web Client. This was resolved.

17028 When the Calculator was run, a rule that was assigned to a parent category was not propagated to folders and documents in child categories. This was resolved.


Warehouse Integration Support for Oracle

The Warehouse Integration feature now supports Oracle databases.

New in This Release


Outlook Integration - Duplicate Filing Markings

When the Outlook integration is configured to not allow duplicate filing of messages to Autonomy Records Manager, you can configure the integration to mark any message that a user has tried to file that was identified as a duplicate. This notation indicates to users that a duplicate of the message has already been filed. This supports individual and batch filing.

Resolved in Autonomy Records Manager 12.6.2 Update 5


Description

17030 The error count is doubled when doing a bulk declare in the SharePoint integration. This was resolved.

17027 The Handler service does not recognize the Oracle 11 database. This was resolved.

17024 When Handler processes an Inventory scan, the redweld ID is set to 0 for the folders in the scanned boxes. This was resolved.

17023 An error occurred when choosing a requestor on the Checkout form. This was resolved.

17022 Option to delete auto declared messages based on date created rather than date filed. This was resolved.

17021 Update SharePoint Web Part GAC version to 12.6.2.4. This was resolved.

17018 The DBupgrade utility fails for the triggers tr_box and tr_file. This was resolved.

17005 The SharePoint integration was unable to undeclare documents that were declared in SharePoint but not in Autonomy Records Manager. This was resolved.

17003 Outlook recent folders do not get updated unless you do a refresh. The problem only occurs if the AppendDestinationOld method is used. This was resolved.

17001 An error occurred when users with a large number of Security Groups or Offices performed a search in the Web client. This was resolved.



Reference Number

Description

17000 DM5 and Outlook integration compatibility problem. This was resolved.

16996 An error occurs when declaring all the documents in a folder when there is a default Autonomy Records Manager location assigned to the folder. This was resolved.

16995 An error occurred when users with a large number of security groups or offices performed a search in the main client. This was resolved.


New Warehouse Integration Functionality

The Warehouse Integration module of Autonomy Records Manager was redesigned and now offers additional functionality. It lets you integrate your records management operations with external vendor warehousing of physical records. In addition to automatically transmitting requests for delivery from Autonomy Records Manager to your vendor, you can seamlessly perform the following records management actions:

■ Add new boxes to the inventory of the vendor

■ Submit new box pickup requests

■ Return boxes to the warehouse

■ Submit a disposition order

■ Update the status and location of boxes from transaction confirmation data returned from the vendor

The new Warehouse Integration module is very flexible and can be configured to accommodate your business process and to comply with the protocols of warehouse vendors for transmitting information.

Web Interface Security Enhancements

The Autonomy Records Manager Web Interface has been hardened to withstand SQL injection attacks and CSS cross-site scripting attacks.

New in This Release


Control of Manual Uploads in the Web Interface

The ability to perform manual uploads of data from a handheld scanning device can be controlled from the Autonomy Records Manager Web Administrator, using the Allow Debug option in the Miscellaneous controls on the General tab. When the Allow Debug option is not selected, the uLoad button is not displayed on the Handheld Upload form of the Web Interface. This prevents users from performing manual uploads from the form.

Support for SQL Server 2012

Autonomy Records Manager supports Microsoft SQL Server 2012.


This section lists the resolved issues to Autonomy Records Manager Version12.6.2 Update 4. Reference Number

Description

17004 A Server Administrator syntax error occurred when saving an iManage search rule that had a query in it. This was resolved.

17003 Outlook Recent folders did not get updated unless you performed a Refresh. This was resolved.

17001 An error occurred when users with a large number of security groups or offices searched in the Web Interface. This was resolved.

16999 An FSfile error dialog contained incorrect branding and a misspelled word. This was resolved.

16995 An error occurred when users with a large number of offices and security groups launched the Desktop client. This was resolved.

16992 There was a problem with the Overdue Web Report for Oracle not functioning correctly. This was resolved.

16987 On the Scan, Checkout form in the Desktop client, when a requestor with a large number of offices was chosen, an error occurred. This was resolved.

16981 When using a handheld scanner to create a new box with a foreign barcode, a character was dropped when the barcode number was added to the f_box.external_name field. This was resolved.



Reference Number

Description

16980 An incorrect folder was displayed for SharePoint integration. This was resolved. The folder label was changed to "Library ARM Default Folder."

16970 Updating Security for a Client with a large volume of Matters and Volumes caused a timeout. This was resolved.

16968 The Autonomy EAS API did not work with the Autonomy Records Manager Viewer. This was resolved.

16966 The Calculator service timed out when a rule was changed and a large number of folders needed to be changed. This was resolved.

16965 The Move document dialog in the Desktop client required the manual entry of the client name and matter ID instead of the client number and matter number. This was resolved.

16963 The comment field was not cleared on exit from the Scan, Retention form. This was resolved.

16962 When installing iManage DeskSite 9 integration on the Desktop client, the DeskSite 9 right-click context menu did not appear. This was resolved.

16961 Repository information was set to null when modifying document metadata. This was resolved.

16959 When using the efile option, typing a plus sign (+) in any field from the number pad moved the cursor focus to the bottom of the screen. This was resolved. The F12 key now lets you toggle the use of the plus sign in a text field from the number pad.

16955 An error occurred with Microsoft Office integration when the declaring and logging options were set to Errors Only or Minimal. This was resolved.

16954 Folders and documents created by the ArmIdolConnector were not inheriting a rule from a category. This was resolved.

16953 There was a problem with the FsExchange utility and processing of emails for a specific user. This was resolved.

16950 The Repository Management service was not able to connect to an eDocs repository. This was resolved.

16944 There was incorrect documentation for adding and editing folder types in the Autonomy Records Manager Desktop Administrator Guide. This was resolved.

New in This Release


Reference Number

Description

16941 The sort by Type double-click on header action did not work as expected in the Outlook integration web grid. This was resolved.

16921 Documentation for mandatory changes to web configuration after upgrade from pre-SR5 version was missing from the Autonomy Records Manager Installation and Upgrade Guide. This was resolved.

16878 Documentation update request regarding the email tickler notifications for the Autonomy Records Manager Desktop Administrator Guide.. This was resolved.

16777 The Autonomy Records Manager Installation and Upgrade Guide revision 2 mentioned an incorrect version of Web Administrator. This was resolved.


Support for WorkSite 9.0

Autonomy Records Manager supports integration with WorkSite 9.0 Server, FileSite 9.0, and DeskSite 9.0 for record declaration. Autonomy Records Manager 12.6.2 Update 3 remains compatible with WorkSite 8.2/8.5 Server and Desktop clients. WorkSite MP (Multi-platform) is not supported. The WorkSite integration must be installed on a 32-bit Autonomy Records Manager server. If you are currently using the WorkSite integration with DeskSite/FileSite 8.2 or 8.5 and plan to upgrade to DeskSite/FileSite 9.0, it is recommended that you first uninstall the WorkSite integration before you upgrade to WorkSite 9.0 and then install the WorkSite integration from the 12.6.2 Update 3 CD. Refer to the Autonomy Records Manager iManage WorkSite Integration Guide for detailed installation instructions.

Copy as New Version in WorkSite Integration

Users can now create a new version of declared documents from FileSite or DeskSite. To create a new version of a declared document, users can right-click the document or click the ARM menu and select the Copy as New Version option. This feature is available for FileSite/DeskSite 8.5 or 9.0.



Support for IDOL DiSH License

Support is provided for the Autonomy Distributed Service Handler (DiSH) license for Autonomy Records Manager Indexer services powered by IDOL. Autonomy DiSH provides a central point from which you can manage multiple Autonomy applications.

Modify Records On Hold in Desktop

Users can modify the metadata of an object that has been placed on hold, such as a folder or box, without having to be members of a group that has permissions to override ethical walls and access controls. Administrators can use the Modify Records On Hold in Desktop parameter in the System parameters of the Desktop Administrator to control this feature.

Configurable Sender for Repository Management Service Notification

System administrators can now configure the Repository Management Service to use an alternate sender for e-mail notifications. This is useful if the account used to run the service does not have an e-mail account.

Support for Crystal Reports on 64-bit Workstations

Support is provided for printing Autonomy Records Manager Crystal Reports on 64-bit workstations.



Description

16935 When an Autodeclare operation occurred, the audit log was updated with an incorrect user. This was resolved.

16929 The Porter Service did not use the Document Location Template when filing documents. This was resolved.

16925 The upgrade utility for Autonomy Records Manager 12.6.2 Update 2 inactivated the Take/Request action. This was resolved.

New in This Release


Reference Number

Description

16919 The FSOffice.dll for Microsoft Office integration was not digitally signed. This was resolved.

16918 Elite Import did not update the country for maddr6 and it imported the client contact when not checked. This was resolved.

16914 The PST crawler did not work when the oracle_username of the service account was used to run the job. This was resolved.

16913 Deleting a Group with a long name failed for an Oracle database. This was resolved.

16912 Rule parts listed on the Rules page in the Web client were missing information if the rule was not event-based. This was resolved.

16910 The fsExchange program could not handle journal emails with very large recipient lists. This was resolved.

16909 Deleting a Hold with a long name failed for an Oracle database. This was resolved.

16907 The hot key (Alt-Shift-X) for Change Status did not work without Advanced Action permission. This was resolved.

16906 A handheld scanning error occurred when processing a sweep of multiple rooms during one scan. This was resolved.

16905 An error occurred when efiling a PowerPoint 2010 presentation that had not been saved, in a Windows 7 environment. This was resolved.

16903 The hot key (Alt-) for File To on the eFiling window was not available. This was resolved.

16900 ColorBar integration did not print Spanish characters such as á and ñ. This was resolved.

16899 Paper documents created by duplicating from a detail form with repository_id were assigned a repository_id. This was resolved

16898 Very large transaction files occurred due to an excessive number of inserts and deletes to the V_user table which is used for audits, in an Oracle environment. This was resolved.

16896 An FXUAXOOP error occurred when profiling a message in Outlook integration. This was resolved.

16894 The fsExchange routine entered a continuous loop if it ever failed to perform a rollback. This was resolved.



Reference Number

Description

16893 The Autonomy Records Manager Server Administration utility was unable to display the fsindex.ini file for IDOL indexes. This was resolved.

16892 The Inspector Service failed to create a session in Oracle environments. This was resolved.

16891 The IDOL Indexer restart routine had reverse logic, starting from the beginning when asked to continue, and continuing when asked to start over. This was resolved.

16890 Outlook integration for batch filing of messages showed one message selected no matter how many were chosen, on Windows 7 in a 64-bit environment using 32-bit Outlook. This was resolved.

16889 A user was not able to efile a document with a fully qualified name login. This was resolved.

16888 Active Directory Import failed if there was an alphanumeric character in the floor value of an existing room. This was resolved.

16887 An incorrect destruction date was calculated for a box from its contents when there was a two-part rule. This was resolved.

16886 The ARM IDOL connector did not import documents if they did not have an extension, and if a document failed to be stored in the repository, the record in the database was not rolled back. This was resolved.

16885 A collation error occurred in the FSexchange service and a message was not autodeclared. This was resolved.

16884 In the Desktop client, when a user selected the Destroyed option from the Scan, Scan for Retention menu, and the specified folder had a home box that was archived, a message appeared asking the user to select an alternate location for the folder. After the user closed the message without specifying a location, the destruction process continued. There is no need to select an alternate folder. This was resolved.

16883 When a voicemail was autodeclared in Outlook, the message could no longer be opened in the voicemail system. This was resolved.

16882 When Security is set at the Category, Office Security did not work. This was resolved.

New in This Release


Reference Number

Description

16881 In an Oracle database environment, if you had a large file description (around 250 characters) and you tried to delete the file with audits of Deletes active, an error occurred indicating that the character string buffer was too small. This was resolved.

16880 An error was produced when printing a Crystal Report with a large number of items from the Web client even when the hits limit was set to a large number. This was resolved.

16877 There were invalid links to objects in session reports that were filed to Autonomy Records Manager. This was resolved.

16876 If a custom column was defined with a function in f_box, a user could not create multiple boxes. This was resolved.

16874 The document location was not always showing client/matter/folder type/folder volume. This was resolved.

16873 An incorrect message occurred in the Web client when requesting items that cannot be requested. This was resolved.

16871 Extended ASCII characters printed on a BarTender Label as a question mark. This was resolved.

16870 The SharePoint Search Web Part failed to deploy. This was resolved.

16869 Installing Outlook integration only on a Windows 64-bit client produced an error. This was resolved.

16866 An invalid condition occurred when a template had a reference in a field in f_disp_date and f_record_session. This was resolved.

16865 The Web client did not allow users to cancel a request. This was resolved.

16864 When using envelope journaling in Exchange, the Autonomy Records Manager integration bcc rules did not work. This was resolved.

16861 The fsExchange Service did not properly sequence messages when autodeclaring multiple messages to a new folder. This was resolved.

16860 Content search did not consistently find a hit in an email or attachment, or both. This was resolved.

16859 Universal Import did not work for an Oracle database. This was resolved.



Reference Number

Description

16857 and 16783

There was an error in Checkout to requestor with a large number of security groups. This was resolved.

16852 Printing from the Desktop client produced an error and closed the application. This was resolved.

16850 When the Document Import utility was set to create a folder for each document, it assigned the SQL_Audit user to the created_by value for the first folder. This was resolved.

16849 and 16809

Navigating back and forth between Forms in the Desktop client reset the user view. This was resolved.

16848 A handheld scanner move operation of a file to a redweld did not update the redweld ID of the folder. This was resolved.

16847 When a document that is restricted was moved from a restricted folder to an unrestricted folder, the security remained on the document. This was resolved.

16842 When using the Advanced, Change Client option to change the client for a matter, the office of the matter, folders, and documents was not updated to match the office for the client. This was resolved.

16839 When a folder or box was inserted or duplicated, the Authority field was not populated. This was resolved.

16838 The default location from a SharePoint library was not populated on the document profile view when declaring a document. This was resolved.

16836 Outlook integration may have taken a considerable time to open if it scanned a large number of mailboxes. This was resolved.

16834 When using efile on a Windows 7 64-bit machine, changing the date was not saved. This was resolved.

16833 Confidential settings were lost when using the Advanced, Change option to change Client for Matters. This was resolved.

16832 Unable to open linked documents in Web client. This was resolved.

16831 When a box was deleted, the space in the warehouse was incremented by 2 rather than 1, in an Oracle database. This was resolved.

16830 An inconsistent date and time appeared for Last Seen Date for Checkout and Return. This was resolved.

New in This Release


Reference Number

Description

16829 There was no metadata for use with ViewServer. This was resolved.

16828 A Courier Service warehouse job did not create the correct output file if only one box was approved. This was resolved

16827 An error was encountered when a user attempted to view email attachments. This was resolved.

16825 Active Directory Import incorrectly imported the domain name when fully qualified domain names were imported. This was resolved.

16823 All folders up to the hits limit were displayed on the Browse view after creating folders using the Folder Wizard. This was resolved.

16822 The functionality for the Advanced, Change a Column action was missing for rooms. This was resolved.

16821 The default client office was not auto-populated with the office of the employee. This was resolved.

16820 The rule for a box was not updated when changing a category if a category rule was inherited from a parent category. This was resolved.

16819 In a legal hierarchy, a timeout occurred when trying to change the category of a matter. This was resolved.

16818 Unable to reset voice mail messages using Copy Declared Message option in Outlook. This was resolved.

16817 A tickler email notification problem occurred when retrieving box information because the operation was trying to use a field that no longer exists. This was resolved.

16816 Employee-Room Barcode Crystal label printed a comma for a room numbered with a 4. This was resolved.

16815 Filing of .pdf files by drag and drop to the Outlook 2010 My Records folder did not populate the form. This was resolved.

16814 The Fsexchange crawler failed to crawl mailboxes where the user was a member of a very large number of security groups (over 2,000). This was resolved.

16813 In a Windows 7 64-bit environment, when declaring a record from Outlook and updating fields on the profile, the changes were not saved. This was resolved.



Reference Number

Description

16812 For e-mail integrations with Outlook 2010, the Declare Folders privilege was not available in Windows 7 64-bit environments. This was resolved.

16806 and 16661

An Outlook 2003 error occurred when exiting Outlook if Autonomy Records Manager integration was installed. This was resolved.

16805 Declaring a document from SharePoint failed if ShowProfile = N. This was resolved.

16800 Active Directory Import created a new floor when rooms exceeded 9999 per floor and failed to create rooms when it started a new floor. This was resolved.

16799 An error occurred when placing a large number (over 1,000) of objects on hold in an Oracle database. This was resolved.

16798 For an Oracle database, the Handler Service failed to create a report file if there were more than 32,767 characters in the report. This was resolved.

16797 A new Oracle session was created each time a Crystal report was selected for printing and was not released when the report was closed. This was resolved.

16796 An error occurred when a session was manually created with more than 1,000 records in an Oracle database. This was resolved.

16791 When adding a custom or standard field in the Web Administrator to be included on the document profile for declaring a record from Outlook, the field was displayed but the database was not updated. This was resolved.

16789 A script error occurred when using up or down arrows to reposition files in the Default File Set in the Web client using Internet Explorer browser. This was resolved.

16787 Room labels printed barcodes with an incorrect drawer number. This was resolved.

16776 and 16433

The Document Import utility failed to create a folder if one of the folder fields was Null in the source data. This was resolved.

16771 When selecting multiple records on the Responsible tab for Session, all values were copied from one record to all selected records. This was resolved.

16770 The Inspector Service did not implement the flag to exclude items on hold. This was resolved.

New in This Release


Reference Number

Description

16769 If a user set up an Inspector Service job to run on a particular day/time, the system ignored the time. This was resolved.

16768 Custom configuration of the Browse view in the Desktop client was not propagated to all users. This was resolved.

16765 When declaring a record from Outlook or Office integration, the document profile did not display the folder level after selecting the File To option. This was resolved.

16763 Created_by and Changed_by fields were not populated in the detail tab for boxes and folders. This was resolved.

16762 Current Room was not populated for Folders with Boxed on Site status. This was resolved.

16760 When trying to reassign a user from the Advanced, Reassign User option, a message was received to first remove the files for the user. Reassign User should reassign the objects associated with the user and then delete the user. This was resolved.

16759 The FSRic utility did not check if entered_by was populated for Matters in a Corporate database. This was resolved.

16758 The entered_by column for a Matter was populated in a Corporate database. This was resolved.

16757 The Print Control did not work when running Crystal Web through the Desktop client on a Windows 7 64-bit machine. This was resolved.

16756 The icon for PowerPoint in virtual directory \appl was named 9.gif. It should be powerpoint.gif. This was resolved.

16753 Some columns were not available when you performed an Advanced, Change column action on a folder in the Desktop client. This was resolved.

16752 If a user did not have the delete permission for File, the Folder Wizard in the Desktop client did not allow you to delete a folder before it was saved. This was resolved.

16750 The location on the Desktop client Folder Detail view for a circulating folder was not displayed as the Room Code. This was resolved.

16749 Unable to email Crystal Reports from the Desktop client. This was resolved.



Reference Number

Description

16748 An incorrect date was displayed for Disposition Date on the Details view. This was resolved.

16745 The ADERANT Import did not save records with military time. This was resolved.

16744 The Desktop client did not support printing TabQuik labels. This was resolved.

16743 Unable to add a comment for items scanned on the Scan for Retention form. This was resolved.

16720 In Outlook 2010, if a user did not have sufficient permission to complete the autodeclaration setup process on a mailbox, the user was not informed until after the folder to map to had been selected. The user should be notified when the user selects the Outlook folder for Autodeclare. This was resolved.

16618 Steps 159 and 160 in version 7.5 of FSRic were querying against obsolete tables. This was resolved.

16529 The web client did not allow authorized users to change ethical wall security when a hold was placed on the item. This was resolved.


Copy Documents from Browse Tab to Another Location

Use the Copy button on the Browse tab toolbar to copy one or more selected documents to a different location. This lets you specify a different document category and folder ID for the copied item.

Refresh Detail Pane After Changes in Detail Window

The Refresh button on the toolbar of the details pane lets you refresh the display of information in the detail pane tabs. This is useful if you double-click an item on the Browse tab to open the detail window and make changes in the properties in that window and the detail pane is open at the same time. Click Refresh to display the same change in the detail pane tabs.

New in This Release


Automatically Exclude On-Hold Items from Disposition

Administrators can use the Disposition parameter Exclude On-Hold Items from Candidacy in the Desktop Administrator to exclude disposition candidates that are on hold from being processed for disposition. The Inspector service recognizes that the item is on hold and that it should not be processed.

Set Preferences for Default Printers

Use the Preferences options in the Client Configuration Utility to set default printers to use when printing detail information from the Desktop User interface and for printing Bartender labels.

New Features for Outlook and Exchange Integration

Release 12.6.2 Update 2 includes new features for Outlook and Exchange integration.

Customized Ribbon for Outlook 2010

The Autonomy Records Manager integration for Outlook 2010 lets users manage record declaration from Outlook using a customized Outlook ribbon. The same options that are available from the integrated Autonomy Records Manager menu in earlier versions of Outlook are now available on the Outlook ribbon. Administrators can customize the menu label for the ribbon and the menu label for re-declaring messages.

Custom Icons in Outlook 2010

Custom icons for Autonomy Records Manager integrated mail folders and declared records are displayed in the mail folder tree structure in Outlook 2010. These custom icons reflect the hierarchy of the folder or declared message.



Autodeclaration Problem Reporting for Audits

Records administrators can use the Audit function in the Desktop Interface to view audit information if a problem occurs during an attempt to auto-declare a message from Outlook. Formerly, this information was only available in the Autonomy Records Manager Exchange service log, which is typically only reviewed by system administrators.

An error in auto-declaring a message can occur when a folder becomes ineligible for autodeclaration because of a change in permissions on the folder, or if the folder has been closed to new records. The audit report provides information about the error, including a reason why the folder is ineligible, so that the records administrator can take action to resolve the problem.

Autodeclaration Delegation and Permissions

The autodeclaration delegation feature lets Outlook users delegate autodeclaration permissions to another user. For example, an attorney may want a legal secretary to manage a mailbox. Outlook allows you to give access permissions for another user to view and edit mailbox folders, but not to change the name of the folder. The autodeclaration process requires changing the folder name and description. If the autodeclaration fails because of insufficient permissions, the Autonomy Records Manager Exchange Server gives full owner permissions to the delegated user, and displays a message that Autonomy Records Manager will complete the auto-declaration process.

New Variable for Autodeclaration Folder Name

The @parent variable has been added for naming the autodeclaration folder in Outlook. Use the Auto Declaration Folder Indicator field on the Outlook options of the E-mail Integrations tab in the COM Setup options to specify this and other variables, alone or in combination.

Depending on the hierarchy in use, the @parent variable appends different information. For a corporate hierarchy, the value is the category code. For a legal (client/matter) hierarchy, the value is a combination of the client code and matter code. For a legal (matter only) hierarchy, the value is the matter code. The category code, client code, and matter code are code variables configured in the Web Administrator for the tree presentation of the appropriate object in the Web Interface.

Re-declare Messages Archived in Enterprise Vault

Messages that have been archived in Enterprise Vault can be re-declared to Autonomy Records Manager.

New in This Release


Autonomy Records Manager IDOL Integrity Check

The Check IDOL index status option provides integrity checking for the Autonomy Records Manager data in the IDOL index. When this option is in effect, the Repository Management Service verifies that all of the documents in the Autonomy Records Manager repository have been indexed. The results are recorded in a log file. This can be useful for troubleshooting purposes.

The check box for this feature is located on the Repository Location dialog of the Edit Repository Parameters options.

Customizable Label for File To Button

The label can be customized for the File To button on the profile form that opens when you declare a record from an Autonomy Records Manager integration, for example, from Windows Explorer.

Use the File To Button Label field to specify a label, in the Integrations group on the General tab of the COM Setup options.

Support for Symbol MC-75 Hand-held Scanner

The Autonomy Records Manager Real-time Tracking application supports the Motorola Symbol MC-75 hand-held scanning device.

Disposition Workflow Integration with APA

Autonomy Records Manager provides a sample template for creating an approval process for the destruction disposition of records. This process can be customized according to your requirements, using Autonomy Process Automation (APA) to modify the template for your workflows.

This approval process can be triggered in two ways:

■ In the Autonomy Records Manager Desktop User interface, on the sessions form, you can display details about a destruction session. If the workflow is enabled, click the Start Workflow button on the toolbar of the detail tab of the session to start the approval process.

■ If the workflow is globally enabled, the workflow is triggered for every destruction session created by the workflow. To enable the workflow globally, in the Server Administration utility under Registered RM Databases right-click a database and select Properties. In the Database Properties dialog, on the Workflow tab, check the box for Enable Workflow.



Autonomy Records Manager CFS Connector

The Autonomy Records Manager Content Framework Server (CFS) Connector lets other applications share an Autonomy Records Manager index. When installing the Autonomy Records Manager server, there is an option to install the service. After the Autonomy Records Manager server is installed, the IDOL CFS Connector service appears under RM Services in the Server Administration utility, where it can be configured and started.

This Autonomy Records Manager CFS Connector provides support for Autonomy Legal Hold (ALH) to access the Autonomy Records Manager index and collect copies of Autonomy Records Manager records to put the copies on hold in ALH.

The connector also supports an enterprise DiSH license for Autonomy Records Manager indexes.

Resolved in Autonomy Records Manager 12.6.2. Update 2

This section lists the resolved issues in Autonomy Records Manager version 12.6.2 Update 2. Reference Number

Description

16733 Category change on Box does not propagate to the folders inside. This was resolved for SQL Server, Oracle 9i, and Oracle 10g.

16729 When upgrading to Microsoft Outlook and Exchange 2010, the integration inserted the My Records folder even if the MY FileSurf folder is defined in the database. This was resolved.

16721 The time was incorrect on reports generated by the full client. This was resolved.

16712 The File To form generated an error if the Notes field for a folder contains the ASCII character of the value of zero. This was resolved.

16696 The status of folders not scanned on the Scan Return form are changed to Archived instead of Unknown. This was resolved.

16694 Error searching for boxes by session ID. This was resolved.

16693 Folders created when declaring from Outlook display titles with strange characters in the tree in Outlook. This was resolved.

16686 The Current Box field on the Folder detail tab does not look correct. This was resolved.

New in This Release


Reference Number

Description

16684 If the Selection criteria is too long when using the File type lookup on the folders form, the following error occurs: "Invalid Length Parameter passed to the SUBSTRING function." This was resolved.

16680 Error on the Folder form when the Document tab is selected: "Invalid Cast error." This was resolved.

16679 When scanning a second redweld to check out, an error occurs. This was resolved.

16677 Sub-volume field not being populated. This was resolved.

16676 Emails with multiple attachments are not filing all the attachments. This was resolved.

16667 The scan report after the Archive/On-site task does not show all items that were not scanned that should have been scanned. This was resolved.

16664 A folder not scanned that belongs to a scanned redweld gets last_seen updated, but the status is not updated. (The status must be changed to U). This was resolved.

16656 During a checkout, when you select the person the next screen should default to the associated room. This was resolved.

16654 Context sensitive help does not work in full client. This was resolved.

16652 Emails are filed in incorrect sequence number. This was resolved.

16651 The Folder wizard displays an error message when the folder type is set to Empty. This was resolved.

16649 A column overflow error message displays when using the Archive function to create a new box. This was resolved.

16648 The autodeclare process does not allow delegates to assign a folder unless they have owner rights to the mailbox. This was resolved.

16647 FsExchange service should log messages to Autonomy Records Manager so that multiple persons can manage errors. This was resolved.

16646 The autodeclaration service is case sensitive for the database alias. This was resolved.

16645 Count(*) invoked before retrieval of data on forms. This was resolved.



Reference Number

Description

16643 Items scanned on Checkout and Return forms are not processed. This was resolved.

16642 The Refile option for an autodeclared KVS stub message does not clear certain message properties. This was resolved.

16641 The autodeclaration service does not check the current eligibility of a folder for filing. This was resolved.

16636 The autodeclaration function coming from an Autonomy Records Manager Application server running under Windows 2008 Server to a Windows 2003 Exchange Server encounters MAPI errors. This was resolved.

16627 Error printing BarTender labels through Citrix when user cannot access printer in value of PrinterUsedLastTime key. This was resolved.

16620 The Party tab on a Matter form retrieves the party twice for each party. This was resolved.

16613 The Courier service creates a schedule for the service itself. This was resolved.

16607 When editing the properties of an FsExchange job in the Server Administration utility, on the General tab, for the Logon as option, the password does not appear, and clicking cancel clears the password. This was resolved.

16599 Handler error when processing a Move with a redweld or folder. This was resolved.

16598 The default folder matrix is not saving when a change is made. This was resolved.

16597 The Document Import options for subfile_numa and sub_file_numc do not include the %constant option. This was resolved.

16596 Setting an application to use basic authentication results in a message indicating that the user is unauthorized when trying to browse the tree in the Desktop User interface. This was resolved.

16514 Missing option to copy documents. This was resolved.

16464 eDocs DM5 declaration to eRecords, read only access declaration issues. This was resolved.

New in This Release


Documentation Updates

The following product documentation was updated for this release:

■ Autonomy Records Manager Installation and Upgrade Guide

■ Autonomy Records Manager Desktop User Guide

■ Autonomy Records Manager Desktop Administrator Guide

■ Autonomy Records Manager Server Administration Utility User Guide

■ Autonomy Records Manager Web Interface Configuration Guide

■ Autonomy Records Manager Exchange and Outlook Integration Guide

■ Autonomy Records Manager Hand-held Scanning Devices Integration Guide

■ Autonomy Records Manager Documentum Integration Guide

■ Autonomy Records Manager iManage WorkSite Integration Guide

■ Autonomy Records Manager Supported Platforms

Check Autonomy’s Knowledge Base on the Customer Support site for documentation updates:

https://customers.autonomy.com


Microsoft .NET Framework 4 Required

Autonomy Records Manager 12.6.2 Update 1 requires Microsoft .NET Framework 4 for the server and workstations. When you install the server and the workstation, the installation process detects the current version of .NET and installs .NET Framework 4 if you do not have this version installed.



Option for Persistent Expanded Desktop User Detail Tabs View

You can set a preference for how the Desktop User interface displays the Details tabs pane by default.. This option determines whether the Details tabs pane persists as expanded or not.

To set the preference for viewing the Details tabs pane

Use the Autonomy Records Manager Client Configuration Utility to set this option.

On the Actions menu, select Preferences.

Check the Detail View Hidden option to have the Details tabs pane not expanded. When this option is not checked, the expanded pane displays persistently by default.

Note: You can always expand and collapse the Details tabs pane using the Expand and Collapse control.

Custom Dictionary for Spell Checking

A custom dictionary for spell checking is provided with this release.

Global Security Set Append Option

When performing a Global Security Set action, you can use the Append option to keep the existing security settings when you add new security settings to the selected object or objects.

To append existing security settings

1. On the Browse tab, select one or more items.

2. Click the Advanced icon.

3. From the menu, choose Global Security Set.

4. The Global Security Set dialog opens.

5. Click Insert Group, or Insert Employee and select the group or employee you want to add.

6. The specified group or user is displayed in the list.

7. Select Include or Exclude, and specify the permissions.

8. Click Append.

9. The existing security settings are added to the list.

New in This Release


10. Click Yes to update the security of descendant folders and documents.

11. The display returns to the Browse tab.

Create a New Document With a Default Media Type

Use the Insert Default Media Type button to create a new document with a default media type specified. This option is available when the Default Media Type parameter is configured with a media type value in the All Parameters list under the Configuration node in the Administrator. This button is available for the Document Template tab, Browse tab, and the Documents detail tabs of the File, Matter, and Category forms.

When you use this option instead of the Insert button, the Document Detail form is displayed with the default media type specified. This lets you create a document without having to first select a media type from the Media Type dialog.

Note: Media types are defined in the Administrator under Codes & Types, Media Types.

Inactivate Rooms Option

Use the Is Active option to indicate whether a Room is active or not. This lets you search for and identify rooms that are active or inactive. A room that is marked as inactive should not be used for adding new records, but it may be needed because records or users are still assigned to it, and for historical purposes.

This option can be configured for the Rooms search template form and for the Detail tab for rooms.

To make the Is Active option available to search

1. Click the Configure button on the Rooms template toolbar.

2. Move the Is Active option from the list of Available Columns to the list of Allocated Columns.

To make the Is Active option available for rooms

1. Click the Configure button on the Rooms Detail tab toolbar.

2. Move the Is Active option from the list of Available Columns to the list of Allocated Columns.



New Field for Category Full Code

A new database field for category full_code searches has been introduced in this update. The full_code field has been added to the f_category table. The use of this field instead of the function fn_full_code (category_id) speeds up the search by category full_code.

Reverse Option for Lookups

The Reverse option for lookup lists lets you reverse the selection of items in a lookup list. When you browse for a value on a template, you can select from the list of values on the resulting select dialog. By clicking Reverse, you can clear the selected items and instead select all of the items that had not been selected. This can be useful for managing the items selected from the list.

Table Field Information Displayed on Template Tab View

When you select an item in a search column on a template in the Desktop User interface, the associated table.field information is displayed on the line above the column headings, at the right of the pane.

New Procedures for Upgrading from Previous Versions

There are new procedures for upgrading from previous versions of the product. Refer to the upgrade sections of the Autonomy Records Manager Installation and Upgrade Guide for detailed information about upgrading.

Changes to Existing Features in Release 12.6.2 Update 1

Installation Setup Enhancements

During the installation of the server and workstation, the setup program detects whether the current versions of Microsoft .NET Framework 4 and Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) are present. If they are not installed, the setup program displays a notification and installs the current version.

New in This Release


Indicator for Protected Date Fields

If the property of a date field is set to protected by an administrator, the date information in the Desktop User interface is displayed dimmed in gray, and the value of the field cannot be changed.

Copy Auto-Declared Messages

The Copy Declared Messages option in the Autonomy Records Manager Outlook integration lets users copy previously declared messages to another folder. The default label for this menu option in the Outlook integration is Copy Declared Messages. Administrators can configure the Re-Declare Messages menu label to suit the needs of the organization in the E-Mail Integrations options for Outlook in the COM Setup of the Desktop Administrator.

When the user invokes this option, the custom .CARM suffix is removed from the message class, to make the message eligible for declaration again.

The administrator controls the availability of this option based on the Outlook parameter privileges specified for the privilege group that the user is a member of. This is done by selecting the Allow Re-Declare Messages option on the Outlook Parameters By Privilege dialog in the E-Mail Integrations options for Outlook in the COM Setup of the Desktop Administrator.

Users Can Manage Outlook Preferences

Users can manage the Preferences in the Outlook integration from the integration menu. Administrators control the availability of this option by selecting the Show Preferences option on the Outlook Parameters By Privilege dialog in the E-Mail Integrations options for Outlook in the COM Setup of the Desktop Administrator.

Outlook Privilege Controls Enhancements

The following enhancements have been made to the privilege controls for Outlook integration:

Allow Re-Declare Messages

Specifies that users in the selected group have permission to copy previously declared messages to another folder in Outlook.

Show Preferences

Specifies that users in the selected group can configure the choices on the Preferences menu in the Outlook integration.



Document Import Utility Enhancements

The Autonomy Records Manager Document Import Utility has been enhanced with new variable values for use when performing imports.

■ Folder variables MAX, NEW, and NEXT let you manage import values for Folder Volume (f_file.subfile_numb) and Subvolume (f_file.subfile_numc).

■ Text file variables MAX, NEW, NEXT, and <Empty> let you manage how values for Folder Volume (f_file.subfile_numb) and Subvolume (f_file.subfile_numc) are imported from text files.

Refer to the Autonomy Records Manager Document Import Utility User Guide for more information about these variables.

New in Release 12.6.2

IDOL Replaces dtSearch Indexing Engine

Autonomy Records Manager is now powered by Autonomy's Intelligent Data Operating Layer (IDOL). With IDOL as the core search technology for Autonomy Records Manager, customers can now also leverage IDOL's advanced conceptual search capabilities with support of more than 1,000 file types and over 100 languages, improving search performance and relevancy.

For information about installing the Autonomy Records Manager Indexer, powered by IDOL, see the Autonomy Records Manager Indexer Administrator Guide.

After the Autonomy Records Manager Indexer is installed, use the Server Administration utility to configure the indexer services. For information about configuring the Autonomy Records Manager indexer services, see the Server Administration Utility User Guide.

Support for Windows Server 2008 R2

Autonomy Records Manager is certified for Microsoft Windows Server 2008 R2.

Support for SQL Server 2008 R2

Autonomy Records Manager supports Microsoft SQL Server 2008 R2.

New in This Release


Support for Windows 7

Autonomy Records Manager supports Microsoft Windows 7.

Support for Exchange 2010

Autonomy Records Manager supports Microsoft Exchange Server 2010. This includes support for Exchange Data Access Group servers.

Support for Office 2010

Autonomy Records Manager supports Microsoft Office 2010 32-bit version.

Support for SharePoint 2010

Autonomy Records Manager supports SharePoint 2010.

Support for Lotus Notes 8.5

Autonomy Records Manager supports IBM Lotus Notes 8.5.

Display a Tree View in the Detail Pane of the Desktop User Interface

The Tree tab view in the Details pane of the Desktop User Interface lets you see a structured hierarchical view of the selected object or objects and the related parent objects and child objects.

To see the Tree view

1. Select one or more objects in the Browse results tab.

2. Expand the Details pane if it is not already expanded.

3. Select the Tree tab.

The parent objects and child objects of the item or items selected in the Browse pane appear on the Tree tab in the Details pane.

4. Select an object in the tree to see detailed information about the object in the right pane.



Automatically Attach a Crystal Report to an Email

Click the email button in the Crystal Reports viewer to automatically attach a report in PDF format to an email.

KeyView Support for Viewing Record Information

Support for Autonomy KeyView has been added for viewing record information. This replaces the Oracle Stellent HTML Export viewer support.

Report Tab

The Report tab in the Details pane of the Desktop User Interface lets you view a report about the selected object. This tab is available for all types of objects. Your administrator specifies the availability of this tab and the report assigned to the tab. You can assign one report to the tab.

Requirements This section describes the system requirements for Autonomy Records Manager Version 12.6.2 Update 7.

For information about software requirements, see the Autonomy Records Manager Supported Platforms data sheet.

Application Server

The following are the hardware requirements for the Autonomy Records Manager Application Server.

Hardware

The following are the hardware requirements for the system running the Autonomy Records Manager Application Server: Component Minimum Recommended

Processor The minimum required for your operating

One Intel Core 2 Duo processor or

Requirements


Component Minimum Recommended system. comparable.

RAM The minimum required for your operating system.

4 GB

Storage The minimum required for your operating system.

Sufficient storage to meet your expected requirements.

Note: The application server can also be installed on a virtualized application server, such as VMware ESX or VMware Server.

For information about hardware recommendations for using the Autonomy Records Manager Indexer, powered by IDOL, see the Autonomy Records Manager Indexer Administrator Guide.

Database Server

The following are the hardware requirements for the Autonomy Records Manager Database Server.

Hardware

The following are the hardware requirements for the system running the Autonomy Records Manager database.

Note: The hardware requirements for the database depend on the size of your installation footprint. Component Minimum

Processor Refer to the DBMS vendor's documentation

RAM Refer to the DBMS vendor's documentation

Storage Refer to the DBMS vendor's documentation

Note: While the database can be hosted on a virtualized application server, we do not recommend doing so.



Web Server

The following are the hardware requirements for the Autonomy Records Manager Web Server.

Hardware

The following are the hardware requirements for the Autonomy Records Manager Web Server: Component Minimum Recommended

Processor The minimum required for your operating system.

One Intel Core 2 Duo processor or comparable.


2 GB



Workstations

The following are the hardware requirements for Autonomy Records Manager workstations.

Hardware

The following are the hardware requirements for Autonomy Records Manager workstations: Component Minimum Recommended

Processor The minimum required for your operating system.

One Intel Core 2 Duo processor or comparable.


2 GB



Requirements


Autonomy Records Manager Indexer Deployment

Before deploying Autonomy Records Manager Indexer, contact the Autonomy Sizing Service at [email protected] or HP Autonomy Technical Support. You will be asked to complete a questionnaire with information about your deployment, such as the number, size, and location of your Autonomy Records Manager databases, average document size, and hardware specifications. You will be given recommendations for settings and network architecture for your Autonomy Records Manager Indexer deployment.

Autonomy Records Manager 12.6.2 Update 7 Release Notesh30359. Governance/Autonomy... · Autonomy...

Documents

Transcript of Autonomy Records Manager 12.6.2 Update 7 Release Notesh30359. Governance/Autonomy... · Autonomy...