hp trim release notes€¦ · hp trim 7 document and records management solution is extensible and...

HP TRIM Software Version: 7.2

HP TRIM Release Notes

Document Release Date: December 2011

Software Release Date: December 2011

Legal Notices

Warranty

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notices

© Copyright 2008-2011 Hewlett-Packard Development Company, L.P.

Trademark Notices

Adobe® is a trademark of Adobe Systems Incorporated.

Microsoft®, Windows®, Windows® XP and Windows Vista® are U.S. registered trademarks of Microsoft Corporation.

Oracle® is a registered trademark of Oracle and/or its affiliates.

Documentation Updates

The title page of this document contains the following identifying information: • Software Version number, which indicates the software version. • Document Release Date, which changes each time the document is updated. • Software Release Date, which indicates the release date of this version of the software.

To check for recent updates or to verify that you are using the most recent edition of a document, go to:

http://h20230.www2.hp.com/selfsolve/manuals

This site requires that you register for an HP Passport and sign-in. To register for an HP Passport ID, go to:

http://h20229.www2.hp.com/passport-registration.html

Or click the New users - please register link on the HP Passport login page.

You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.

http://h20230.www2.hp.com/selfsolve/manuals�

http://h20229.www2.hp.com/passport-registration.html�

Support

Visit the HP Software Support web site at:

www.hp.com/go/hpsoftwaresupport

This Web site provides contact information and details about the products, services, and support that HP Software offers.

HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to: • Search for knowledge documents of interest • Submit and track support cases and enhancement requests • Download software patches • Manage support contracts • Look up HP support contacts • Review information about available services • Enter into discussions with other software customers • Research and register for software training

Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to:

http://h20229.www2.hp.com/passport-registration.html

To find more information about access levels, go to:

http://h20230.www2.hp.com/new_access_levels.jsp

http://h20229.www2.hp.com/passport-registration.html�

http://h20230.www2.hp.com/new_access_levels.jsp�


i

Contents

1 HP TRIM 7.2 Release Notes ....................................................................... 1

Introduction to Version 7 ................................................................................................................................... 1

Overview of HP TRIM 7.2 .................................................................................................................................. 1

2 New HP TRIM 7.2 Features........................................................................ 3

Standard Metadata Elements ............................................................................................................................ 3

Using the Media Type metadata elements ................................................................................................. 4 Record Creation Form ........................................................................................................................... 4 Record Type Default .............................................................................................................................. 5 Assigning a Media Type after Record Creation ................................................................................... 6

Records Authority ............................................................................................................................................... 7

Basic Concepts of Records Authority .......................................................................................................... 8 Configuring HP TRIM as a Records Authority System ............................................................................. 8 Example of the Document Flow ................................................................................................................ 12

Multi Jurisdiction Retention ............................................................................................................................ 13

Jurisdictions ............................................................................................................................................... 13 Default Jurisdictions .................................................................................................................................. 14 Jurisdictions and Records .......................................................................................................................... 14 Jurisdictions and Retention Schedules ..................................................................................................... 15 Jurisdiction and Trigger Rules .................................................................................................................. 17

3 HP TRIM Feature Enhancements ................................................................ 20

HP TRIM Core Product .................................................................................................................................... 20

Localization of HP TRIM ........................................................................................................................... 20 MSI Re-design ............................................................................................................................................ 20

Removal of Demonstration Database from Installation ................................................................... 20 License Details ..................................................................................................................................... 20 TRIM Configuration file no longer installed/upgraded ..................................................................... 21 Client Setting Configuration .............................................................................................................. 21

Management Reporting ............................................................................................................................. 22 Record Creation Summary Statistics ................................................................................................. 22 Examples of Record Creation Statistic Reports................................................................................. 25 Audit Event Statistical Aggregation .................................................................................................. 27 Examples of Audit Events Statistic Reports ...................................................................................... 28

Document Storage Enhancement .............................................................................................................. 29 Improved Store Allocation................................................................................................................... 29 Deployment Status .............................................................................................................................. 31 Increased Efficiency of Storage Space ................................................................................................ 31 Document Store Capacities ................................................................................................................. 33 Synchronous Document Transfer ....................................................................................................... 33 Minimizing Pending Folder Backlogs ................................................................................................ 34 Improved Error Handling ................................................................................................................... 34

ii

Event Processing Scalability ..................................................................................................................... 35 Processing Word Indexing and Content Indexing on Multiple Workgroup Servers ....................... 35 Serialization of Processing Steps ........................................................................................................ 35 Additional Configuration Options ...................................................................................................... 35

Document Content Index – IDOL ............................................................................................................. 36 HP TRIM Viewer ........................................................................................................................................ 37

HP TRIM for SharePoint Integration ............................................................................................................. 37

Support for MS SharePoint 2010 .............................................................................................................. 37 Support for Office365 Dedicated ............................................................................................................... 37 Support for Claims Based Authenticated Web Applications .................................................................. 37 Term Set Integration: HP TRIM Synchronized Term Sets ..................................................................... 37 Term Set Integration: Custom Term Set Providers ................................................................................. 38 Extending the Content Organizer ............................................................................................................. 38 Handling Disposed Records ....................................................................................................................... 38 Propagating Configuration ........................................................................................................................ 38 Localization ................................................................................................................................................ 38 Documentation ........................................................................................................................................... 39

HP TRIM Web Client ....................................................................................................................................... 39

Online Help Localization ........................................................................................................................... 39 Tag and Task Support ............................................................................................................................... 40

Records ................................................................................................................................................. 40 Locations .............................................................................................................................................. 40 Saved Search ........................................................................................................................................ 41 To Do Item ............................................................................................................................................ 41

Links in the View Pane .............................................................................................................................. 41 Introduction of a Stateless Model ............................................................................................................. 41 Refine Search .............................................................................................................................................. 42 New Configuration File ............................................................................................................................. 42

4 General Enhancements............................................................................ 43

A Technical Note ....................................................................................... 48

Support Matrix ................................................................................................................................................. 48

What operating system and database platforms will HP TRIM Version 7.2 support? ......................... 48 HP TRIM Server Support (32-bit) ...................................................................................................... 48 HP TRIM Server Support (64-bit) ...................................................................................................... 48 HP TRIM Rich Clients (Administration & Desktop) (32-bit) ........................................................... 48 HP TRIM Rich Clients (Administration & Desktop) (64-bit) ........................................................... 48 Supported RDBMS (32-bit) ................................................................................................................. 48 Supported RDBMS (64-bit) ................................................................................................................. 49

What e-mail and Microsoft Office versions will be supported? ............................................................... 49 Supported e-mail applications (32-bit) ............................................................................................... 49 Supported e-mail applications (64-bit) ............................................................................................... 49 Microsoft Office Support ..................................................................................................................... 50


Page 1 of 56

1 HP TRIM 7.2 Release Notes

Introduction to Version 7

HP TRIM 7 is a scalable, policy driven enterprise document and records management solution with automated rules, classification and workflow capabilities. It allows customers to easily capture, search and manage business information from any source, including all Microsoft SharePoint® content.

HP TRIM 7 is built on a single code base and manages physical and electronic content regardless of source from creation to disposal. Designed to the international standards of records management ISO 15489, HP TRIM software is proven in large Government and regulated industries and can meet the needs of any business. HP TRIM 7 is certified against US DoD 5015.2 V3:

• Mandatory Requirements – Chapter 2 and Chapter 5

• Management of Classified Records – Chapter 3

• Managing Records for the Privacy Act and the Freedom of Information Act – Chapter 4

• Non-mandatory Features – Chapter 6

HP TRIM 7 for SharePoint integration seamlessly manages all SharePoint content including blogs, wikis, discussions, documents, and sites, according to established business rules providing a scalable, policy-driven foundation to your information governance strategy. HP TRIM is transparent for the user, drives efficiency for your business and integrity of your records.

HP TRIM 7 document and records management solution is extensible and can capture and manage content regardless of source in one organizational information governance platform. Powerful web services and SDK.NET integration toolkits provide organizations with the tools to capture all business records into one authoritative document and records management solution.

HP TRIM 7.2 contains many improvements to existing HP TRIM functionality, there are interface as well as database schema changes. This document gives you an overview of the changes included in HP TRIM 7.2.

For details on supported upgrade paths and changes to supported environments, please see Appendix A.

Overview of HP TRIM 7.2

This second minor release of Version 7 is part of the planned release cycle and includes fixes to some of the problems that have been reported, but also includes improvements based on findings during the ongoing testing by the HP TRIM product quality assurance team.

HP TRIM 7.2 is all about scalability for the Enterprise – both large numbers of users and large numbers of documents.

The development and compilation of this minor release has been undertaken using Microsoft’s latest development environment. This means that to deploy this release you will


Page 2 of 56

require Windows Installer 3.1 as a minimum. If this version is not present in your environment, an update pack can be downloaded from the Microsoft Web site.

This minor release includes all fixes and enhancements that were shipped in the previous release. For details of the previous release, please refer to the relevant release notes. For details on fixes to HP TRIM 7.2, please refer to the TRIM7.2_Fixes.htm file. For technical details refer to TRIM7.2_Spec.pdf and TRIM7.2_Install.pdf


Page 3 of 56

2 New HP TRIM 7.2 Features

Standard Metadata Elements

A new standard property, Media Type, has been added as a Record Object in HP TRIM 7.2. The Media Type property is a customizable record property metadata field that allows the user to identify the object type the metadata represents. This can be useful for organizations whose records holdings include a wide range of physical formats to identify, retrieve and manage the long term storage and destruction of this data.

Media Type is an enumerated list with 10 defined elements and 10 Custom elements that can be set by HP TRIM Administrators to meet their unique business requirements. The custom elements can be defined in the HP TRIM Caption editor as follows:

Figure 1 - Media Type Elements


Page 4 of 56

Using the Media Type metadata elements

Record Creation Form

The new metadata field, Media Type, can be added to the Record Creation form in HP TRIM 7.2.

Figure 2 - Standard Metadata Field - Adding the field to a Record Creation form

The properties of the field can be set to Optional, Mandatory or Read Only.


Page 5 of 56

Figure 3 - HP TRIM Record Creation form with Media Types added

Record Type Default

A default Media Type is specified on a Record Type in HP TRIM 7.2. All records created will inherit this default Media Type from the Record Type.

When upgrading to the HP TRIM 7.2 schema, all records will be created with a Media Type of Unknown.


Page 6 of 56

Figure 4 - Setting a default Media Type on a Record Type

Assigning a Media Type after Record Creation

Defining the Media Type of a record can be done after a record has been created. The Media Type field is modified from the right-click Details > Other Record Fields menu option.


Page 7 of 56

Figure 5 - Assigning a Media Type after Record Creation

As seen on Figure 5 - Assigning a Media Type after Record Creation, the fields (Accession Number, External ID and Priority) that were accessed from the right-click Details > Additional Fields menu on records have been moved to the Other Record Fields menu option in HP TRIM 7.2.

Records Authority

HP TRIM 7.2 introduces a new concept – Records Authority. The Records Authority feature enables a customer to utilize the rich disposition management features of HP TRIM to safely and legally dispose documents held in separate document archival systems.

In this concept, a document archiving system is a computer system to store documents for a period of time. Typically, it stores a minimal set of metadata and is usually more dedicated to minimize storage cost than solving record retention issues. With the Records Authority feature, HP TRIM can act as a disposal management system to determine when documents can and should be deleted from the document archive system, according to HP TRIM’s records management settings.

For the integration of these two computer systems to work, the document archive system must feature:

• The capability to record an authority ID against each document

• The capability to search for and find documents based on the authority ID

• The capability to prevent documents from being deleted unless specifically instructed via the HP TRIM Records Authority messaging infrastructure.

Records Authority is a licensed module.


Page 8 of 56

Basic Concepts of Records Authority

There are 3 components of the HP TRIM Records Authority:

• Records Authority system (RA) – this is a management system that can determine when an item should be deleted based on a set of rules designed to satisfy all legal compliance rules relating to the item. HP TRIM is the RA.

• Document Archiving system (DA) – this is a system for storing documents for a period of time. Typically, it will have a minimal set of metadata and usually is more dedicated to solving the problems of storage costs. New features have been added to HP TRIM to allow it to be used as a DA.

• Data Collector (DC) – this is a general name given to a process that transfers documents into a DA. In the Records Authority system, the DC is responsible for allocating a records authority in the RA to a set of documents being stored in the DA.

Configuring HP TRIM as a Records Authority System

There are a number of processes required to enable HP TRIM as a Records Authority System:

• An external Document Archive system must be registered in HP TRIM (via the Tools > External Document Archive Systems menu)

Figure 6 - Records Authority - Creating a new External Document Archive System – HP TRIM as an Archive tab


Page 9 of 56

Figure 7 - Records Authority - Creating a new External Document Archive System - Add-In (RA Delete) tab

• Record Type(s) with a Behavior of Records Authority must be created

Figure 8 - Creating a Record Type to be used by Records Authority

– Complete and define the fields on the Records Authority tab on the Record Type(s)


Page 10 of 56

Figure 9 - Record Types - Available Record Authority Type options

To allow a Data Collector to efficiently store and implement a consistent Records Authority policy, a special type of Origin has been designed. Whilst not mandatory for a Records Authority system, it is expected that most implementations will use an Origin to record characteristics for how a particular data collection job will work. By using an Origin object, a TRIM administrator can use the TRIM interface to configure the data collection process with respect to what the records authority records will look like, etc.


Page 11 of 56

• Create one or more Origins (from the Tools > Records > Origins menu)

Figure 10 - Origins - Creating a new Records Authority Origin

Figure 11 - Origins - Records Authority Create Style options


Page 12 of 56

• Configure HP TRIM Enterprise Studio to run the event Records Authority and Job Controller processes

– Records Authority: The Records Authority processor looks at all Records Authority records in the RA and sees if they are due for destruction. It then creates a Job to represent the deletion of the documents in an archive system. This “job” contains: - The records authority id - Any addition date criteria that also must be met

– Job Controller: The Job Controller runs asynchronously and in parallel with the Records Authority processor type. The Job Processor monitors the state of the job(s) and updates TRIM appropriately when it is complete (storing log files, updating counters and setting job statuses). Jobs can be viewed in HP TRIM from the Tools > HP Administration > Jobs menu.

Figure 12 - HP TRIM Enterprise Studio - Configuring the Records Authority and Job Controller Events

Example of the Document Flow

1. A data collector process identifies a new set of documents to save to the document archive system. For example, all word documents in John Doe’s My Documents folder

2. The data collector process creates an authority record in HP TRIM which will be used for all of these documents

3. The data collector process adds each of the documents to the document archive system, attaching the recordsAuthorityID from the TRIM record created in step 2.

As a result, there is now an authority record in HP TRIM that represents a collection of documents in the document archive system.

The document archive system now prevents these documents from being deleted because it has a HP TRIM recordsAuthorityID attached. HP TRIM now determines when the


Page 13 of 56

document in the document archive system should be deleted by applying its business rules to the corresponding HP TRIM authority record.

4. When HP TRIM determines that a HP TRIM authority record is due to be destroyed, it assumes that the documents under its authority in the document archive system are also due for destruction. An addition feature of a Records Authority is for it to support “Individual Deletion” of documents within the collection. This means that instead of immediately deleting all records with the specified authority, a further test is applied and deletes are conditional on this extra date-based criteria being satisfied. HP TRIM sends a message to the document archive system indicating that all documents with the specified recordsAuthorityID can now be destroyed. (For collections with the “Delete Individually” setting, this message will contain details of what date criteria needs to be additionally satisfied before the document can be deleted)

5. The document archive system identifies and destroys the documents that match the records authority ID (and any specified date criteria), creating a log of all items that were deleted.

6. The HP TRIM message infrastructure monitors the progress of this delete request, once it is complete the log file is transferred to TRIM for long-term storage. At this stage, if there are no more documents left in the archive system with the matching authority id, the TRIM records authority will be marked as Destroyed, effectively ending its purpose.

It is likely the same Records Authority record could be used for continuing data collections so the Authority is only destroyed if marked as Closed for further use.

Multi Jurisdiction Retention

The Multiple Jurisdiction Retention model introduced in HP TRIM 7.2 supports the concept of record retention based on the jurisdiction of the record, that is, for a Personnel record to derive its retention policy from the Personnel schedule relevant to the Country or Region of the specific document.

For the purpose of this module, a jurisdiction is a legal entity that has the power to compel an Organization to retain its records in a particular manner. Typically, a jurisdiction corresponds to a Country, but it may also be a State, Council or International body that administers an International treaty.

The multi-jurisdiction retention features are a licensed module.

Jurisdictions

There are 3 types of Jurisdictions that can be created in HP TRIM 7.2 (from the Tools > Retention > Jurisdictions menu):

• Single – this is a single Jurisdiction, as an example, this could be a State or Territory name

• Group – this is a Jurisdiction that can have members. The members of a Jurisdiction Group can be a single Jurisdiction or another group Jurisdiction

• Federation – this is a Jurisdiction that can have members. The members of a Federation Jurisdiction can be a single Jurisdiction or a Jurisdiction that has members


Page 14 of 56

Figure 13 - New Jurisdiction dialog box

Default Jurisdictions

A default jurisdiction may be associated with a Record Type, a Classification and a Location. When a new record is created, HP TRIM checks the record details for a default jurisdiction in the following order:

1. The jurisdiction associated with the record’s Classification

2. The jurisdiction associated with the record’s Record Type

3. The jurisdiction associated with the creator of the record

4. The jurisdiction associated with the default Organization of the user creating the record

HP TRIM applies the first default jurisdiction to the record. If no default jurisdictions are found, a user with appropriate user permissions can add a jurisdiction to the record from the right-mouse button menu, Administrative Tools > Add Jurisdiction.

Jurisdictions and Records

When a record is created in HP TRIM, or modified after creation, the record is designated as being under the control of zero, one or multiple jurisdictions.


Page 15 of 56

Figure 14 - Jurisdictions and Records in HP TRIM 7.2

Jurisdictions and Retention Schedules

An HP TRIM Retention schedule is composed of zero or more retention triggers, which determine the time for the archival or destruction of records associated with that schedule. A jurisdiction of any kind may be attached to a retention trigger, designating that the trigger is only applicable to records within that jurisdiction.

Figure 15 - Adding a Jurisdiction to a Retention Schedule Trigger


Page 16 of 56

Figure 16 - A Retention Schedule with Multiple Triggers and Jurisdictions


Page 17 of 56

Jurisdiction and Trigger Rules

If there is a single jurisdiction retention trigger applicable to the jurisdiction attached to a record, then that trigger will apply to the record regardless of the presence of Group jurisdictions that may contain the specific jurisdiction.

Examples

Record A

Jurisdiction: US

Retention Schedule: Destroy Trigger 10 years after Date Closed for Jurisdiction US

Destroy Date of Record A: 10 years after Date Closed

Record B

Jurisdiction: US


Destroy Trigger 20 years after Date Closed for Group Jurisdiction USCAN (both US and Canada are members)

Destroy Date of Record B: 10 years after Date Closed

If there are group jurisdiction retention triggers applicable to jurisdiction(s) attached to a record, then the most severe retention trigger will apply to the record (unless there is a specific trigger for a jurisdiction applied).

Example

Record C

Jurisdiction: US

Canada


Destroy Trigger 20 years after Date Closed for Group Jurisdiction USCAN (both US and Canada are members)

Destroy Date of Record C: 20 years after Date Closed


Page 18 of 56

If there are federation jurisdiction retention triggers applicable to the jurisdiction attached to a record, then the calculation of the most severe retention will be based on the federation retention triggers and any specific triggers applicable to the jurisdiction applied to the record.

Example

Record D

Jurisdiction: US

Retention Schedule: Destroy trigger of 10 years after Date Closed for Jurisdiction US

Destroy trigger 20 years after Date Closed for Federation Jurisdiction USCAN (both US and Canada as members)

Destroy Date of Record D: 20 years after Date Closed

If there are no jurisdiction retention triggers applicable to the jurisdiction attached to a record, then any retention triggers without a jurisdiction applied will be used to determine the most severe retention for the record.

Example

Record E

Jurisdiction: Canada

Retention Schedule: Destroy trigger of 10 years after Date Closed for Jurisdiction US

Destroy trigger 20 years after Date Closed (no Jurisdiction attached)

Destroy Date of Record E: 20 years after Date Closed

If a Retention Schedule has multiple retention triggers with Trigger Types of Archive (with jurisdiction) and Destroy (with or without jurisdiction), the Archive trigger will be applied to the record.

Examples

Record F

Jurisdiction: Canada, US

Retention Schedule: Destroy trigger of 10 years after Date Closed for Jurisdiction Canada

Permanent Archive trigger of 5 years after Date Closed for Jurisdiction US

Archive Date of Record F: 5 years after Date Closed


Page 19 of 56

Record G

Jurisdiction: Canada, US

Retention Schedule: Permanent Archive trigger of 5 years after Date Closed for Jurisdiction US

Archive Date of Record G: 5 years after Date Closed

Although there is no trigger for Canada it can never have a greater severity than the US therefore the calculation can be made.


Page 20 of 56

3 HP TRIM Feature Enhancements

HP TRIM Core Product

Localization of HP TRIM

HP TRIM 7.2 provided language support for:

• English (International)

• English (United States)

• French

• Dutch

• German

• Italian

• Spanish

• Portuguese (Brazilian)

HP TRIM 7.2 language support has been extended to include:

• Russian

MSI Re-design

In HP TRIM 7.2 the HP TRIM_x.msi has been redesigned to simplify the process.

For details on installing HP TRIM 7.2 please refer to TRIM7.2_Install.pdf

Removal of Demonstration Database from Installation

In HP TRIM 7.2 the ability to install the Demonstration Database has been removed from the installation process. A compressed copy of the Demonstration Database is included on the HP TRIM_CDImage.ISO.

For details on how to restore the Demonstration Database in HP TRIM 7.2 please refer to the TRIM7.2_Install.pdf

License Details

In HP TRIM 7.2 the dialog to enter the HP TRIM License details has been removed from the installation wizard. HP TRIM licensing information will be added (or modified) in HP TRIM Enterprise Studio (TES).

To access the License dialog box, expand the General node and right-click on License and click Properties.


Page 21 of 56

Figure 17 - HP TRIM Enterprise Studio - License dialog box

TRIM Configuration file no longer installed/upgraded

In previous releases of HP TRIM, to enable an installation of HP TRIM with the DemoDB installed to work ‘out of the box’ a TRIMconfig.tcfg file was installed. In HP TRIM 7.2 we have removed the DemoDB from the installation process so there is no longer a requirement to install a TRIMconfig.tcfg file.

On a fresh install of HP TRIM the user will need to set up the TRIM Configuration through the HP TRIM Enterprise Studio, and when the configuration is saved a TRIMConfig.tcfg file is created. If HP TRIM is being upgraded the existing TRIMConfig.tcfg file will not be modified.

Client Setting Configuration

An additional dialog has been added to the HP TRIM installation package in HP TRIM 7.2. This dialog box allows organizations to configure the paths for the Client Folder locations. If the fields are left blank during installation default settings will be applied.


Page 22 of 56

Figure 18 - HP TRIM Install - New Client Folder Settings Configuration dialog

Management Reporting

HP TRIM enables users to generate statistics related to records, Workflows and Actions attached to records within the dataset. These generated statistical reports are exported to an external application (for example, Microsoft Excel) for viewing and printing.

In HP TRIM 7.2 we have extended the available statistical reports to include two new reporting options – Record Creation Summary Statistics and Audit Event Statistical Aggregation. Both new reporting options are accessible by users with HP TRIM Administrators, Information Managers and Information Workers access, from the Tools > Reports menu.

Record Creation Summary Statistics

The new Record Creation Summary report allows Organizations to generate 9 different reports to show how many records are being created with a particular time frame.


Page 23 of 56

Figure 19 - Record Creation Statistics Reporting dialog

This report is designed to provide tallies of the number of records created within a particular date range. The aggregation is available with the following options:

Primary Grouping

This will allow the user to select a top level grouping as one of:

• Classification

• Retention Schedule

• Jurisdiction

• Record Type

• None

Location Grouping

Within the primary grouping, a sub-grouping will be provided by location. This location will be based on one of the selected locations types:

• Owner

• Creator

• Home

• Assignee


Page 24 of 56

• None

For a chosen location type, statistics will be generated as either:

• Aggregated by each distinct location

• Aggregated by statistically significant locations

The flagging Locations for statistical aggregations is a new concept that Locations to be defined for statistical purposes. Organization Location types can be flagged as Use For Statistical Aggregations. To determine the “statistical” group that a Location belongs to, the Member Of relationship is navigated upwards (to the parent), using the Default Member Of relationship, until an Organization flagged as Use For Statistical Aggregations is found. If no such parent is found the Location belongs to an Unknown statistical group.

Figure 20 - Flagging an Organization for Statistical Aggregation

Date Range

The statistics will be produced by counting the number of records that belong to the various categories described above. Records will be selected by selecting a date range for either:

• Date Created

• Date Registered

Record Search String

A User can further filter the report content by specifying a Record Search String which records must also satisfy to be included in the report.

Output Options

The Record Creation Statistical report can be output to either:

• Excel CSV file

• HTML

SDK

The aggregated Record Creation Statistical data is also accessible through the HP TRIM SDK.


Page 25 of 56

Examples of Record Creation Statistic Reports

Classification

To make classification more consistent with the other reports, we will not sum up the values to the parent classification. Parent classifications will also not appear if they have no records.

Classification Title Classification Number Records Created General 001-001-001 10 Rental 001-001-002 20 International 001-002 5 Accounting Automatic 002-001 3

Retention Schedule

Schedule Number Schedule Title Records Created - - 2 1 Internal Audit 1 2 Audit 10 3 Birth Certificates 20 4 Deficiencies and Losses 56

Jurisdiction

Jurisdiction Name Jurisdiction Description Records Created ANZ Australia and New Zealand 1 ASIA Asia 10 AUS Australia 20 CAN Canada 56

Record Type

Record Type Name Records Created Document 1 1 Document 2 10 Document 3 20 Document 4 56

Location

Location Records Created [Other] 324 HP 148 HP – EB 48 HP – EB – SW 11 HP – EB – SW – IM 5 HP – EB – SW – BIO 6 HP – EB – HW 22 HP – EB – HW – ABC 10 HP – EB – HW – DEF 12


Page 26 of 56

HP – EB – XX 15 HP – CORP 100

Location by Classification

Location Classification Number

Classification Name

Records Created

HP 001-001-001 General 10 HP – SW 001-001-001 General 4 HP – HW 001-001-001 General 6 [Other] 001-001-001 General 2 HP 001-001-002 Rental 28 HP – SW 001-001-002 Rental 23 HP – HW 001-001-002 Rental 5 [Other] 001-001-002 Rental 3

Location by Retention Schedule

Location Schedule Number

Schedule Title Records Created

HP 1 Internal Audit 30 HP – SW 1 Internal Audit 10 HP – HW 1 Internal Audit 20 [Other] 1 Internal Audit 4 HP 4 Deficiencies and

Losses 56

HP – SW 4 Deficiencies and Losses

56

Location by Jurisdiction

Location Jurisdiction Name

Jurisdiction Description Records Created

HP ANZ Australia and New Zealand 30 HP – SW ANZ Australia and New Zealand 10 HP – HW ANZ Australia and New Zealand 20 [Other] ANZ Australia and New Zealand 1 HP AUS Australia 6 HP – SW AUS Australia 1 HP – HW AUS Australia 5 [Other] AUS Australia 2


Page 27 of 56

Location by Record Type

Location Record Type Name Records Created HP Document 1 30 HP – SW Document 1 10 HP – HW Document 1 20 [Other] Document 1 1 HP Document 2 3 HP – SW Document 2 2 HP – HW Document 2 1 [Other] Document 2 45

Statistically Significant Location

Location Records Created [Other] 324 HP 148 HP – SW 11 HP – HW 22 HP – [Other] 115

Audit Event Statistical Aggregation

The Audit Event Statistical Aggregation allows an Organization to produce a report that gives them a snapshot on HP TRIM usage. The report generates data against many HP TRIM Events types. The categories of Events that can be reported:

• HP TRIM Events, e.g. Unique Logins – adds +1 to the report each time a new user logs into HP TRIM

• Document Events, e.g. Checked In (Attached) – adds +1 to the report each time an electronic document is attached to an HP TRIM record

• Workflow Events, e.g. Activity Skipped – adds +1 to the report each time an Activity is skipped in a Workflow

• Audit Events, e.g. Record Security Breach – adds +1 to the report each time there is a Security Breach on Records


Page 28 of 56

Figure 21 - Audit Event Statistics Reporting dialog

Data related to HP TRIM events is collected, aggregated and stored in SQL tables for later extraction and reporting.

The aggregation is done on the basis of events occurring per day. An HP TRIM System Option (Tools > HP TRIM Administration > System Options > Events) is used to specify the time zone to be used to determine what day an event occurs on. This System Option will allow the Administrator to set the time zone in which the statistics are generated, rather than the data being collated from midnight to midnight UTC time, it will be summarized against the time zone selected.

Figure 22 - System Option - Time Zone Offset

Output Options

The Record Creation Statistical report can be output to either:

• Excel CSV file

• HTML

SDK

The aggregated Audit Event Statistical data is also accessible through the HP TRIM SDK.

Examples of Audit Events Statistic Reports

Daily Totals

Date Records Added

Record Modifications

Finalized Unfinalized Container Changed

…

2011-02-28 10 0 0 0 0 2011-03-01 15 0 0 102 34 2011-03-02 16 2 0 1 1 2011-03-03 41 1 1 3 2


Page 29 of 56

Daily Totals + Monthly Totals

Date Records Added

Record Modifications

Finalized Unfinalized Container Changed

…

2011-02-28 10 0 0 0 0 2011-02 10 0 0 0 0 2011-03-01 15 0 0 102 34 2011-03-02 16 2 0 1 1 2011-03-03 41 1 1 3 2 2011-03 72 3 1 106 37

Document Storage Enhancement

HP TRIM has the ability to ingest large quantities of documents over a short period of time. As organizations look to increase the numbers of documents pushed into HP TRIM, the operation of the HP TRIM document storage services needed to be improved to decrease the amount of stress placed on the storage layer.

In HP TRIM 7.2, we have improved the allocation of documents to document stores, improved the efficiency of use of the store, and minimized bottlenecks in the storage process.

Improved Store Allocation

In HP TRIM 7.2, document stores can be added to a document storage pool. A HP TRIM 7.2 dataset will, by default, have a store pool with 1 document store (the main document store defined in the previously installed version of HP TRIM) and will behave as it did in HP TRIM 7.1.

If new stores are created (within the HP TRIM client - Tools > HP TRIM Administration > Document Stores) and added to the document storage pool in HP TRIM 7.2 (see Figure 23 on page 30), the Workgroup server will apply a store allocation algorithm to determine which store a particular document should be added to based on the defined Electronic options on the Record Type (see Figure 24 on page 30).


Page 30 of 56

Figure 23 - Adding a new Document Store to the Document Storage Pool

Figure 24 - Assigning the Document Store on a Record Type

If the Record Type for the document specifies that the document stores pool should be used, then we rotate through the first N stores in the pool, filling them evenly. When those N stores finally fill up, they will automatically become marked as "No Additions" (see Deployment Status on page 31 for details), and a new batch of N stores will be selected for pool allocations. When we select the first N stores, it is done in alphabetical order based on the Store Names. By default N is 1, but N can also be set to larger values in the HP TRIM Enterprise Studio, Dataset > Properties (see Figure 25 on page 31).


Page 31 of 56

Figure 25 - HP TRIM Enterprise Studio - Defining the Number of Document Stores in a Pool

Deployment Status

To assist organizations in optimizing backup strategies, in HP TRIM 7.2 we’ve introduced the concept of a deployment status. Document stores will have a status property that defines its current deployment status. The available status’ are:

• Available (with the Store belongs to the general document storage pool option selected) – this indicates that the store has underlying storage allocated and is either currently accepting documents or will be available for automatic deployment if all the current storage facilities are full.

• No Additions – this indicates that the store cannot have new documents added but will accept delete requests.

• Read Only – this indicates that the store is no longer accepting documents.

Backup strategies can be developed based on the deployment status’ of stores, for example stores that that have a deployment status of No Additions will need to be backed up less frequently than a store in the document storage pool that has a deployment status of Available.

Increased Efficiency of Storage Space

In HP TRIM 7.2 a new option has been introduced on the Document Stores properties which, when selected, will compress all electronic documents added to that Store (see Figure 26 on page 32).


Page 32 of 56

Figure 26 - HP TRIM Document Store Properties - Compress documents to reduce storage size option

This option indicates whether documents should be stored compressed. When selected, a document is first compressed using the standard Zip compression algorithm, and then it is added to the store. The reference information will indicate that a decompression will be required before the document is extracted from the store.

If an organization wishes to suppress the compression of particular File Types, this can be done via the HP TRIM Enterprise Studio, General > File Types > Properties menu.


Page 33 of 56

Figure 27 - HP TRIM Enterprise Studio - Suppressing the Compression of File Types

Document Store Capacities

In previous releases of HP TRIM, the size of the store was measured in Megabytes (MB). In HP TRIM 7.2, we’ve introduced the option of selecting different units of measure for the store size. Organizations can now select from:

• Bytes

• Kilobytes (KB)

• Megabytes (MB)

• Gigabytes (GB) or

• Terabytes (TB)

Synchronous Document Transfer

In HP TRIM 7.2, we have introduced a new option on the Workgroup server properties – Synchronous Document Store transfers (see Figure 28 point 1 on page 34). This option changes the document transfer process for the Workgroup server to the document store from asynchronous to synchronous, therefore bypassing the Pending Folder on the Workgroup server. While this means the client will have to wait while the Workgroup server transfers the document to the store, it eliminates the possibility of building up a backlog in the Pending folder.

In previous releases of HP TRIM the number of documents that were transferred to the Document store at any one time was 1, so the queue of documents in the pending folder would be copied to the store one at a time. In HP TRIM 7.2, a new option has been added to allow organizations to set the number of documents to be transferred to the store


Page 34 of 56

simultaneously – Maximum number of simultaneous Document Store transfers (see Figure 28 point 5 below). This can be a number between 1 and 50.

Figure 28 - HP TRIM Enterprise Studio - Workgroup server Properties - Document Store Transfers tab

Minimizing Pending Folder Backlogs

In HP TRIM 7.2 if the Pending folder exceeds 300 files, the Workgroup server will automatically bypass the Pending folder until the backlog is reduced to below 300 files (by default). A new option – Maximum number of queued Document Store transfers - has added to the Workgroup server Properties > Document Store Transfers tab. This option allows organizations to change the default maximum number of documents queued in the Pending folder; this can be a number between 10 and 1000 (see Figure 28 point 4 above).

The process described above only occurs if the Synchronous transfer option (shown in Figure 28 point 1 above) is not selected; if this option is selected the Workgroup server will always bypass the Pending folder.

Improved Error Handling

In HP TRIM 7.2, two new folders have been introduced – Pending Failures and Pending Quarantine in the (default) folder location c:\HPTRIM\ServerLocalData\TRIM. When a file fails to transfer from the Pending folder to the store, it is moved to the Pending Failures folder. The transfer is then retried several times; if it continues to fail, the file is moved to the Pending Quarantine folder where no more action is taken for that file. The Maximum number of attempts for a Document Store transfer can be set on the Workgroup server Properties > Document Store Transfers tab (see Figure 28 point 2 above); this can be a number between 1 and 15. The interval between each transfer attempt can also be set (see Figure 28 point 3 above); this can be a number between 1 and 3600 and is measured in seconds.


Page 35 of 56

An HP TRIM administrator needs to monitor the Pending Quarantine folder and manually move any files from Pending Quarantine back to the Pending folder and the Workgroup server will then start trying the transfers again.

Event Processing Scalability

Processing Word Indexing and Content Indexing on Multiple Workgroup Servers

The TRIM Event Processing model was redesigned in HP TRIM 7.0 to overcome difficulties with large backlogs of rows in the TSEVENTDAT table. This improvement allowed these event rows to be deleted as soon as they had been processed, rather than being held around just in case they may still need further processing. These improvements also allowed each Workgroup to undertake event processing which provided for a better distribution of the workload. While there were improvements to the design of the Event processing model, there were still Events that were only able to be processed on single Workgroup servers. In HP TRIM 7.2 further improvements have been made to include Word Indexing and Content Indexing trigger event processor types to the existing list of event processor types (Schedule Events and Alerts Service) that can be run on multiple Workgroup servers.

Figure 29 - Event Processing - Enabling Word and Content Indexing on Multiple Workgroup servers

Serialization of Processing Steps

To allow for this multiple machine processing, a serialization mechanism has been included in HP TRIM 7.2. A date value will be inserted to the TSTWRSYS table which essentially allocates a LOCK to one process. Other processes will wait until this LOCK is removed, or becomes older than its timeout value, and then they will attempt to claim it for themselves. To enable organizations to set optimal indexing parameters for their own environments, new options have been added to Configure Event Processing dialog box in the HP TRIM Enterprise Studio.

Additional Configuration Options

To enable organizations to set optimal indexing parameters for their own environments, new options have been added to the Configure Event Processing dialog box in the HP TRIM Enterprise Studio.


Page 36 of 56

Figure 30 - Event Processing: Configure Event Processing - Options tab

Event processing batch size

This option indicates how many events will be read from the Event queue at any one time. Some Event processors can work more efficiently by processing a batch of Events at once. In this case, these processors will process all events read in one batch by the Workgroup server Event queuing mechanisms.

Event queue polling interval (seconds)

This option indicates how long the Workgroup server queue filling mechanism should wait before looking for more events that need processing. The queue filling process can be resource intensive so not having the Workgroup server polling continuously provides a more efficient Workgroup environment.

The Workgroup will immediately seek more Events if it knows there are more Events waiting in the queue.

Processor serialization lock timeout (seconds)

This option specifies the time period for which a serialization lock is considered to be valid.

Document Content Index – IDOL

In HP TRIM 7.2, the previous document content index engine has been replaced with a new index engine, Autonomy’s Intelligent Data Operating Layer™ (IDOL). The DCI functionality in HP TRIM 7.2 is equivalent to the previous version’s functionality.

For further details refer to the HP TRIM Enterprise Studio Help file.


Page 37 of 56

HP TRIM Viewer

In HP TRIM 7.2, the previous document viewer technology has been replaced with a new document viewer, Autonomy’s KeyView™ Viewing SDK. The HP TRIM Viewer functionality in HP TRIM 7.2 is equivalent to the previous version’s functionality.

For further details refer to TRIM7.2_Spec.pdf and the HP TRIM Help files.

HP TRIM for SharePoint Integration

Support for MS SharePoint 2010

HP TRIM for SharePoint integration 7.2 will only support SharePoint 2010. Earlier versions of SharePoint have not been validated and are not supported for HP TRIM for SharePoint integration 7.2.

Support for Office365 Dedicated

Office365 Dedicated is a Microsoft offered Cloud service. In essence, the intention of this functionality is to allow organizations to utilize MS SharePoint without the overhead of maintaining the necessary infrastructure using internal IT resources.

HP TRIM for SharePoint integration 7.2 is designed to support the Microsoft Office365 Dedicated environment.

Support for Claims Based Authenticated Web Applications

Version 7.2 of the HP TRIM for SharePoint integration introduces support for claims based authentication.

Term Set Integration: HP TRIM Synchronized Term Sets

HP TRIM has sets of information that are reused throughout the application. Examples of these are:

1. Classifications

2. Thesaurus terms

3. User defined lookup sets

4. Locations

These sets of values are presented to users in HP TRIM to allow selection of a valid value. This behavior is similar to a SharePoint term set.

The concept of a “synchronized term set” (STS) can be described using the following steps:

1. Create a term set in SharePoint to represent a set of information located in HP TRIM

2. Initialize the term set with terms to represent each item contained in the HP TRIM information set


Page 38 of 56

3. When a value is added, modified or removed from the HP TRIM information set, update the term set to reflect the change

An STS allows SharePoint users to utilize term sets that represent an HP TRIM information set.

The HP TRIM for SharePoint integration 7.2 supports the creation of STS to represent Classifications in HP TRIM.

Term Set Integration: Custom Term Set Providers

The HP TRIM for SharePoint integration 7.2 also includes a “pluggable” model that allows third party vendors to write their own code to provide values for synchronized set terms. These are referred to as “custom term set providers” (CTSP).

Extending the Content Organizer

The content organizer is a feature introduced in SharePoint 2010. It allows the definition of a set of rules that are used to automatically move (or “route”) electronic documents to another location dependant on which rule is satisfied.

The “out of the box” rules can only perform a single action i.e. move the document to another document library. The HP TRIM for SharePoint Integration 7.2 functionality extends the capabilities of the content organizer allowing a user to specify that when the conditions of a rule are satisfied, the document should be managed by HP TRIM.

Handling Disposed Records

If an HP TRIM record that is exposed in SharePoint has its Disposition changed to Destroyed, then any and all instances of record (as a managed list item) in SharePoint are also removed.

Propagating Configuration

SharePoint 2010 introduced the ability to use the “managed metadata service” to share content types across multiple site collections in multiple web applications. This allows for organizations to centrally manage a repository of content types and have them propagated out to other site collections.

As part of content type propagation, site columns used by content types are also propagated to subscribing site collections.

Since HP TRIM can already map Content Types to Record Types (and vice versa) and also SharePoint columns to TRIM fields; we’ve provided the same functionality to identify one authority across multiple site collections and push all mappings out to other ‘subscribing site collections’.

Localization

Microsoft SharePoint supports multiple languages as well as local region specific formatting. The HP TRIM for SharePoint integration 7.2 provided language support for:



Page 39 of 56


• French

• Dutch

• German

• Italian

• Spanish


In HP TRIM for SharePoint integration 7.2 language support has been extended to include:

• Russian

Documentation

The HP TRIM for SharePoint integration documentation is now published as four separate documents. These documents will continue to be updated after the initial release of TRIM 7.2:

• TRIM7.2_SPIntegrationInstall.pdf

• TRIM7.2_SPIntegrationConfiguration.pdf

• TRIM7.2_SPIntegrationUserManual.pdf

• TRIM7.2_SPIntegrationDevelopersGuide.pdf

Please check these links in the Software Support Online database to ensure you have the latest version (requires registered username and password to access):

http://support.openview.hp.com/selfsolve/document/KM1280820/binary/TRIM7.2_SPIntegrationInstall.pdf

http://support.openview.hp.com/selfsolve/document/KM1280821/binary/TRIM7.2_SPIntegrationConfiguration.pdf

http://support.openview.hp.com/selfsolve/document/KM1280822/binary/TRIM7.2_SPIntegrationUserManual.pdf

http://support.openview.hp.com/selfsolve/document/KM1280824/binary/TRIM7.2_SPIntegrationDevelopersGuide.pdf

HP TRIM Web Client

Online Help Localization

The existing HP TRIM Web client help files will be localized to provide language support for:



• French

• Dutch

• German

• Italian

http://support.openview.hp.com/selfsolve/document/KM1280820/binary/TRIM7.2_SPIntegrationInstall.pdf�

http://support.openview.hp.com/selfsolve/document/KM1280820/binary/TRIM7.2_SPIntegrationInstall.pdf�

http://support.openview.hp.com/selfsolve/document/KM1280821/binary/TRIM7.2_SPIntegrationConfiguration.pdf�

http://support.openview.hp.com/selfsolve/document/KM1280821/binary/TRIM7.2_SPIntegrationConfiguration.pdf�

http://support.openview.hp.com/selfsolve/document/KM1280822/binary/TRIM7.2_SPIntegrationUserManual.pdf�

http://support.openview.hp.com/selfsolve/document/KM1280822/binary/TRIM7.2_SPIntegrationUserManual.pdf�

http://support.openview.hp.com/selfsolve/document/KM1280824/binary/TRIM7.2_SPIntegrationDevelopersGuide.pdf�

http://support.openview.hp.com/selfsolve/document/KM1280824/binary/TRIM7.2_SPIntegrationDevelopersGuide.pdf�


Page 40 of 56

• Spanish


• Russian

Tag and Task Support

HP TRIM Web client 7.2 supports the ability to select (tag) multiple records in the data grid and perform tasks using the right-click context menu (see below for available options). The ‘Tag All’ option selects all the records listed in the current page only.

Records

• Details

o Set Security/ Access

• Locations

o Set Assignee

o Set Home Location

o Set Owner Location

• Send To

o Favorites

o Add to Recent Documents

o Add to My Containers

o Add to Records Work Tray

o Add to User Label

• Remove From

o Remove Favorites

o Remove Record from Recent Documents

o Remove Record from My Containers

o Remove Record from Records Work Tray

o Remove from User Label

Locations

• Set Active Date Range

• Send To

o Favorites

o Add to User Label

• Remove From

o Remove from Favorites

o Remove from User Label


Page 41 of 56

Saved Search

• Send To

o Favorites

• Remove from Favorites

To Do Item

• Complete

Links in the View Pane

The HP TRIM Web client now supports links in the View Pane. HP TRIM Objects such as Assignee, Author, Latest Parts, and Workflow etc. are displayed as links and the HP TRIM Web client will search for the clicked object text and open the result in a new tab.

Figure 31 - Examples of Links in the HP TRIM Web Client View Pane

Introduction of a Stateless Model

The architecture of earlier releases of the HP TRIM Web client used the ASP.net session management features provided by the Microsoft .NET framework to cache the TRIM database object to maintain the state of the logged on user. Once a database connection was made via a valid Workgroup server, the connection was persisted using the ASP.net session objects. As the TRIM database object cannot be easily serialized, this is a major obstacle in scaling the HP TRIM Web client to large web farm implementations.

The HP TRIM Web client in version 7.2 has removed the reliance on the ASP.net session management to ensure that the HP TRIM Web client is easily scalable to larger web server implementations.


Page 42 of 56

Refine Search

The HP TRIM Web client in version 7.2 provides users with the ability to Refine an existing Search query from within the displayed set of results using the Search > Refine Search menu. Upon building and executing the refined search, the new search result will be displayed in the same search tab from which the search was triggered.

New Configuration File

In previous releases of the HP TRIM Web client, the web.config file was deployed to allow users to change HP TRIM specific settings. In the 7.2 version of the HP TRIM Web client a new configuration file called hptrim.config has been introduced. This additional file prevents any unintentional changes by the user to the system specific web.config file; all HP TRIM specific configuration changes – such as Workgroup server name, Dataset ID, Web Sever Work Path - are all now specified in the hptrim.config file.

Further information about the hptrim.config file can be found in the TRIM7.2_Web-Client-Install-x.pdf documentation.


Page 43 of 56

4 General Enhancements

1345 HP TRIM Enquiry users using the Outlook integration were presented with the same selection of buttons as users with Create permissions. When an enquiry user tried to use a HP TRIM feature that required create permissions, an error would be returned from the TRIMSDK. All buttons that require Write access to the HP TRIM database have been disabled.

1388 Searching - Actions - users should be able to search for records by the location that completed an action. New String based search engine allows users to search actions completed by a particular location.

1762 HP TRIM Setup Information – Software Build details need to be more visible. The About HP TRIM now has the build details in the title, for example 7.2.0.1150

3746 The title bar for the 'Workflow Statistical Reports’ and the 'Action Statistical Reports' dialogs do not specify what type of Statistical reports are being listed. The title bar now specifies either 'Workflow' or 'Action' statistical reports.

9845 HP TRIM Event Server - When using an Oracle Database the Load Balancing of Word Indexing events is not possible when using multiple Workgroup servers. The Load Balancing of Word Indexing events is now possible through multiple Workgroup servers.

12218 Caption Change - Assignee Including Container caption is misleading. Search method caption changed to “Assignee Including Contained Records” and documentation updated.

12558 HP TRIM to send e-mail notifications alerts before actions/activities become overdue. HP TRIM is now able to be configured to deliver e-mail notification of actions and activities coming due.

12836 Documentation - In topic HP TRIM Software Help > Chapter 28 - Additional Fields > Additional Fields administration > Creating Additional Fields > Additional Field formats > String Additional Fields, under bullet point Maximum Length, the following sentence - 'String fields lengths cannot be changed once the string field has been used on a record' needs to be removed. Documented. The Help file has been updated so that the bullet point of “String fields lengths cannot be changed once the string field has been used on a record” has been removed.


Page 44 of 56

12912 HP TRIM Client – Unable to search and display records for E-mail catalogued into HP TRIM with attachments. User can perform both Boolean and String based search on e-mails catalogued into HP TRIM with attachments.

33765 Workflow Activity - A new icon is needed to indicate when an Activity Result's 'Was Reached' state in Activity graphic and property views. A new icon for the Activity result “Was Reached” has been drawn

34161 HP TRIM Client - Disclaimer regarding HP TRIM Offline Records needs to be updated in the installation PDF files. “TRIM7.2_Install.pdf” file is now updated with the disclaimer contents in page 44. “By design, HP TRIM Offline Records is intended for deployments where the Offline Records folder is located on the Windows client computer, in the user's profile folders. Although it is possible to modify this configuration to locate Offline Records in a different location such as a network drive, such a configuration may have a negative impact on performance and reliability of the check-in/check-out function of Offline Records due to environmental network and/or network file system issues and limitations, e.g. file name length restrictions on some Novell file server operating systems, that are beyond the control of HP TRIM. For this reason, HP recommends not changing the default location of Offline Records.”

34956 Customer requests that our electronic document removal message give more details about the record's electronic document that is being removed. They would prefer for it to be in-line with the Microsoft message which displays details about the file you are deleting. Customer states a familiar warning message will prevent more accidental deletions. The warning message when removing a document now contains more information. “Description: This task will remove the current revision and all previous revisions. This operation cannot be undone. File: adfadf.txt Revisions: 0 Are you sure you want to delete all revisions?”

37209 HP TRIM Client - Keyboard shortcuts such as CTRL+V, CTRL+C, CTRL+X, CTRL+A were populating invalid characters in the Number field for Record Types. The shortcuts perform the functions correctly while editing the Number field for Record Types.

38076 SharePoint - log error messages to the SharePoint ULS log. The Unified Logging System (ULS) Log has been made the default location for logging HP TRIM SharePoint Integration exceptions.

38304 HP TRIM in Outlook Add-In - When dragging multiple e-mails into a "Linked Folder", if you don't want to save all e-mails into HP TRIM, the user has to manually cancel each and every e-mail one at a time. Would like to be able to "Cancel All". If the user drags multiple e-mail messages into a linked folder, and chooses not to save an entry, a prompt is then presented to the user asking them to continue if there are still more messages remaining to be catalogued.


Page 45 of 56

38772 Customer would like to see an option added to the Web client to change only the Home Location of a record. This feature is available in the HP TRIM Web client in version 7.2+.

39456 HP TRIM Workgroup server - Failover functionality: if all WGS fail, the TRIM Context Client crashes. If connection to the Workgroup fails, a 'HP TRIM Workgroup Connection' message will be displayed.

39938 The customer would like the possibility of removing a security level completely. Deletion of security levels made possible by providing a replacement option "No security level".

40098 Capture the SMTP address from e-mails where the Exchange format is the default. The 'E-mail Contact Location' e-mail address format now displays [email protected]

40157 SharePoint 2010 - Management Details page is missing the lifetime management section. Details on any lifetime management policies that have been applied to an Item are now included on that Item’s “Management Details” page.

40258 Word Reindexing - The performance of "Text Index" utility in HP TRIM Enterprise Studio must be improved and also provide more information/control on what gets reindexed. There are more options in the "Text Index" utility. Indexes are deleted and reloaded in the Index tables based on the selection of the options.

40436 There is a limit of 20 External Links when the documentation states there is no practical limit. Limit for External Links increased from 20 to100.

40570 Date fields with Text Inputs values in Web client did not match with the date fields in HP TRIM. Date Registered field saves only the default pre-populated values even after saving the record with new values. The text date input values in both Web client and HP TRIM date fields matches. Date Registered field retains user defined values after saving the record.

40580 When the File > Save As integration is invoked in an application such as Microsoft Word, a list of record types is given, but the dataset in use isn't obvious. When the File > Save As integration is invoked in a supported Microsoft Office application the title on HP TRIM Record Type selection dialog now contains the dataset name. E.g. "Save To HP TRIM (DemoDB)".

40599 SharePoint 2010 - Inclusion of the "HP TRIM Record Type" CFT. “HP TRIM Record Type” has been added as an available HP TRIM Integration column type in SharePoint.


Page 46 of 56

40603 Documentation - The upgrade path for the HP TRIM Web client 7.2 was not included in the installation PDF document to explain the upgrade process. Documented. New section - Upgrade HP TRIM Web client has been included in the installation files TRIM7.2_Web-Client-Install-2003-IIS6.pdf and TRIM7.2_Web-Client-Install-2008-R2-IIS7.pdf.

40606 Documentation - The HP TRIM Web client Online user manual does not document the context menu functionality for the open tab. Fixed. Documentation has been implemented and validated. The Web client Online User Manual has all the documentation in regards to the context menu functionalities.

40614 SharePoint 2010 – Improve messages when the HP TRIM Privileged Account or SharePoint Privileged Account are not valid. During validation of these accounts, the specific issue as it relates to either the values entered into the fields, or insufficient permissions for a certain role, is now detailed on the page.

40665 Offline Records were being preloaded into the cache for a BulkLoad session which caused TRIMWatcher to be invoked. This caused permission problems when running a Bulkload operation as a service. Offline Records are no longer preloaded into the cache for a BulkLoad session so TRIMWatcher is not invoked. This has removed the permission problems when running a Bulkload operation as a service.

40698 Schema Upgrade - There are no default values to replace NULL values in 7.x schema. A new repair utility is now available in HP TRIM Enterprise Studio which will execute SQL to replace all NULL value's

40724 HP TRIM Web client – All Server configuration settings are saved within web.config file. Configuration settings are now saved in hptrim.config file which will retain any variables like DBID, Workgroup server name or Port Number etc.

40725 HP TRIM Web client – Server configuration settings for Web client are stored in Web.config file and if any settings are changed then all those changes were lost when upgrading Web client. A new file is installed (hptrim.config) that will store configuration settings and these settings will not change after upgrading.

40752 HP TRIM In Outlook - Catalogue Attachments Only now catalogues background images. Selecting 'Catalogue attachment Only' on an e-mail with an imbedded image and a ZIP file will only create one record with the zip file attached.

40834 Documentation - Online Help must be extended to include information about functions available in the context menu of a TAB within Web client. 4 new HTML files are included in Online Help which explain the functionality of the available context menus on a TAB within the HP TRIM Web client.

40846 HP TRIM Web client - All User Defined Properties are lost upon upgrading HP TRIM Web client. Documented. User Defined properties like DBID, Port number and Workgroup server name will be retrieved from hptrim.config file when upgrading Web client.


Page 47 of 56

41106 HP TRIM client - When the Foreign Barcode field was added as a column of a List Pane, the results would take a long time due to the lack of a Prefetch option. There is now a System Option (under the Object Cache tab) which, when activated, prefetches the Foreign Barcodes for a List of objects and thereby enables them to be returned in a much more timely manner.

41213 Hold - User must be able to remove all records from a Hold in bulk. New feature called Release Records is available in the context menu of a Hold to remove records in bulk.

41225 HP TRIM Database - Implement a stored procedure for fetching user-defined field values. A new stored procedure called “Prefetch UserDefinedFieldValues” has been implemented in SQL and Oracle to replace 7 SQL statements

41287 Locations - Two new fields attached to locations if Enterprise Features is turned on were in the wrong place on the dialog. The two new fields 'Default Jurisdiction' and 'Use for Statistical Aggregations' have been placed on a new 'Governance' tab on the Location Properties dialog.

41497 Microsoft Office Integration - Unable to finalize a HP TRIM Record for documents checked in from a Microsoft Office Integrated Application. User able to finalize a HP TRIM Record successfully for documents checked in from a Microsoft Office Integrated Application.

41522 The Association tab on the property dialog of a location show the associations for the location. The behavior was confusing as a default association was always shown however this was not being recorded in the database. What was actually happening is that HP TRIM was simply displaying the first item as the default. Functionality updated to ensure correct behavior. Default associations are now operating as expected.

42032 HP TRIM Client - Saved searches that are created in the HP TRIM client can't be seen in the list of saved searches in the Web client. Old style saved searches now appear alongside new style string searches and can be treated the same. If you edit and save an old style saved search it will be converted to a new style saved search.

42293 When perform a search, the records which satisfy the searching criteria but doesn't have an electronic document attached is not returned, for example, container record will not be returned. A drop-down option is available within the HP TRIM Office Select dialog in Microsoft Word, Excel, PowerPoint and Project called 'All Records (-)', this displays All records valid to the search created.


Page 48 of 56

A Technical Note

Support Matrix

What operating system and database platforms will HP TRIM Version 7.2 support?

HP TRIM Server Support (32-bit)

• Windows Server 2008 SP2 (32-bit)

HP TRIM Server Support (64-bit)

• Windows Server 2008 SP2 (64-bit)

• Windows Server 2008 R2

HP TRIM Rich Clients (Administration & Desktop) (32-bit)

• Windows Vista SP1 32-bit (Home Edition not Supported)

• Windows 7 - 32-bit (Home Edition not Supported)

HP TRIM Rich Clients (Administration & Desktop) (64-bit)

• Windows 7 - 64-bit (Home Edition not Supported)

Supported RDBMS (32-bit)

• SQL Server 2008

• SQL Server 2008 R2

• Oracle 11g R2


Page 49 of 56

Supported RDBMS (64-bit)

• SQL Server 2008

• SQL Server 2008 R2

• Oracle 11g R2

What e-mail and Microsoft Office versions will be supported?

Supported e-mail applications (32-bit)

The following list shows the level of integration from e-mail clients to the HP TRIM rich client:

E-mail client functions

Microsoft Outlook 2007 SP2 & 2010

Novell GroupWise 8

Lotus Notes 8.0 and 8.5

Checking in to HP TRIM

Yes Yes Yes

Checking in automatically from folder Yes Yes

Yes, using queue

processing

Checking in on send Yes No No

Attach HP TRIM record to new message Yes Yes Yes

HP TRIM functions

E-mail notification

Yes Yes Yes

HP TRIM File/Send

Yes Yes Yes

Mail message form/Send

Yes Yes Yes

Mail setting in Tools → Options → E-mail tab Microsoft Outlook GroupWise Notes Mail

Other

Supported e-mail applications (64-bit)

The following list shows the level of integration from e-mail clients to the HP TRIM rich client:


Page 50 of 56

E-mail client functions

Microsoft Outlook 2010

Checking in to HP TRIM

Yes

Checking in automatically from folder Yes

Checking in on send Yes

Attach HP TRIM record to new message Yes

HP TRIM functions

E-mail notification

Yes

HP TRIM File/Send

Yes

Mail message form/Send

Yes

Mail setting in Tools → Options → E-mail tab Microsoft Outlook

Microsoft Office Support

Version Support Method

MS Office 2007 SP2 (Word, Excel, PowerPoint and Project)

Native Add in

MS Office 2010 (Word, Excel, PowerPoint and Project)

Native Add in

For further detail on the specifications and limitations of HP TRIM 7.2 see TRIM7.2_Spec.pdf