The Problem - Efficient way to electronically process documents and tasks

Based on our extensive experience in the financial services industry, we understand the business criticality of efficiently processing a high volume of documents. In order to improve throughput as well as decrease the compliance risk of pushing paper, many organizations are looking to manage these processes electronically. However, to mitigate the risk to the day to day business, these companies must consider implementing solutions that can be quickly adopted not only by their IT department but by the business community as well. Considerations such as user adaptability, system maintenance, and configurability all need to be taken into account.

The Solution - High Performance Interface

TSG has addressed these considerations in our OpenContent High Performance Interface (HPI) for Documentum and is able to offer our clients a high quality/performance content management application. HPI is the streamlined web interface layer for TSG’s OpenContent open source product.

How it works - High Level Summary

To keep the user experience simple and highly focused on their current workload, this light weight interface has three main components:

1. Dashboard – This component exposes inbox items to the user so they are quickly aware of what work they are currently managing. Based on business needs, the tasks in their inbox can come from a variety of input sources of which include a central scanner, Documentum or even their personal email account. The focus being to enable users to process transactions that come across their “desk” more efficiently.
2. Search – This component exposes advanced search functionality to the user so they can efficiently find content in the system.
3. Desktop – This component exposes core document management features to the user, such as:
   • Document and Folder Management - Adding content to the repository as well as maintaining versions and attributes.
   • Workflow – Collaborating with other users in the system by notifying them of certain work items that need to be addressed.
   • Templates – Standardizing the work product by providing common set of templates for users to work with.
   • Dual Pane Viewer - Comparing and viewing documents side-by-side.
   • Notes – Collecting key information to document the work that is being done.
   • Related Content – Viewing relevant information that may be stored elsewhere in the repository from a single screen, the desktop.

Below is a view of the Desktop in dual pane review mode.

How it Works - Under the Hood

HPI was designed to use leading edge technology according to latest standards and best practices in industry.

• OpenContent SOAP Web Services - Isolates HPI from Documentum to ease maintenance burden and provide cost efficiencies during version upgrades and development of new features.  As business changes and new enhancements are identified, the interface can easily be extended to expose the new web service.
• Spring Framework - Supports highly configurable nature of the application
• Yahoo User Interface Library (YUI) - Provides streamlined look and feel across all browsers
• J2EE Standard - Implements industry standards for enterprise level applications

A sample implementation of this interface is available to demonstrate the core functionality.

Documentum TaskSpace Comparison

Both the OpenContent High Performance Interface (HPI) and Documentum TaskSpace were created to be out-of-the-box, highly-configurable user interfaces.  Key Differences include:

• TaskSpace provides the ability to layout the interface leveraging Forms Builder and WDK/TaskSpace configurations specifically focused at BPM viewing solutions.  OpenContent HPI provides a more generic interface based on TSG experience for a more full-function viewing and editing interface.
• TaskSpace requires BPM and Documentum FormsBuilder.  OpenContent does not require BPM or FormsBuilder relying only on OOTB Documentum workflow.
• TaskSpace requires WDK and specific TaskSpace understanding for customizations.  OpenContent HPI relies on XML, WebServices and standard Java development for any customizations.

Please reference the TaskSpace User Guide, TaskSpace Example Build documentation for specific knowledge in regards to TaskSpace.  Additional detail in regards to HPI will be posted to our download site.