This document provides an overview of the current viewing technology that DocuNECT uses in v4.6.
Document management falls into two categories:
1. Collaborative – Documents that are changed by more than one author
2. Transactional – Documents that result from a transaction, such as a Purchase Order or Invoice, which are not typically edited
DocuNECT’s overall approach is to support collaborative documents in their native format (so they can be changed) and transactional documents via a viewer.
With this in mind, DocuNECT does have a built in viewer for transactional documents in the DocuNECT Web application and in the Client Tools – Desktop Capture application.
The viewer for the DocuNECT Web application is Java based that can be run on multiple version of Java, whereas the Client Tools – Desktop Capture application viewer is based on Microsoft .NET v4.0 technology.
The following table describes how different document types are managed:
Document Format | Type | Viewer Used |
TIFF Image BMP Image PNG Image GIF Image JPG Image TGA Image PCX Image | Transactional | The DocuNECT built in view supports the viewing a multiple different images types. Note, this is a Java based view and requires Java to be enabled in the browser. |
Text Files | Transactional/ Collaborative | The DocuNECT viewer also supports the viewing of text files to provide a more intuitive viewer for reports. |
Adobe PDF | Transactional | Adobe PDF documents use the Adobe ActiveX control and require Adobe Reader X (v10) to be installed on the client machine. |
Microsoft Office | Collaborative | Documents are viewed in their native format. The documents are still displayed in the viewer frame. |
XML and HTML Files | Transactional | These documents are displayed in an internet browser inside the viewer frame. |
Other Document Types and Non - Viewable Documents (such as DLLs) | Transactional/ Collaborative | When these documents are display they the system will detect that image viewing is not supported and the document will be downloaded. Once downloaded then another open operation will be attempted to see if the user has the native application installed on their local machine. |
The following screenshots provide examples of how different document types are displayed:
Note, the following screenshot is from v4.6. In v4.7 there is also a page rotation feature.
There may be some situations where documents are a combination of Transactional and Collaborative. For example, a Standard Operating Procedure (SOP) is authored by a small group of people, but read by potentially a large community of users. In this instance DocuNECT supports Adobe PDF renditions for viewing.
When users are authoring the document (check out/in) they edit the document in its native format, but when the user views the Adobe PDF rendition is displayed. The rendition conversion process is triggered by the document check-in action.
The following list provides an overview of the DocuNECT image viewer features:
In addition to the actual image functions, displayed in the previous section, the following document functions can be perform against documents in any format: