KoVIS 4.1
|
Important Note: Support
for the Windows NT platform discontinued
|
With the release of
KoVIS 4.1, support for the Windows NT platform for any
KoVIS version
has been discontinued. Therefore, this platform will no
longer be tested for future KoVIS
releases, and defects isolated to this OS will not be
corrected.
Implemented Enhancements
Platform Support
Windows 2003 Server support
KoVIS and KoVIS Web 4.1 now fully support Microsoft
Windows 2003 Server.
KoVIS Web
Hit List Display of Lookup Table Fields
Fields with an associated lookup table (e.g. document
type) are displayable in the hit
list using the short or long forms of the name. This new
display option is configurable
through the USER.INI file
Hit List View Support
KoVIS Web now supports the new “Hit List View”
feature added with KoVIS 4.0.
Through this feature, customized hit lists can now be
presented at a user level.
Friendly Retrieval Template Field Names
Field names for the KoVIS Web retrieval templates are
now derived from the
template itself. Previously, raw field names were
presented.
Daeja Viewer update to v2.1.6591
System Administration
Storage Server
The Storage Server component allows workstations to be
completely secured from
KoVIS digital document archives (caches, jukeboxes,
etc.) by providing KoVIS with
the ability to perform retrieval and data entry requests
on the behalf of a user. This
new feature will allow workstations to be completely
secured from KoVIS document
archives (caches, jukeboxes, etc.). Multiple storage
servers may be defined within a
KoVIS system to provide for system scalability. The
Storage Server component is
fully functional for all document types except COLD
documents.
This component replaces the previous KoVIS Document
Server. Document Server
will be included in KoVIS 4.1, but, only to facilitate
migration requirements to the
storage server. Document Server will continue to be
supported on a “best effort”
basis until COLD documents are fully supported through
the Storage Server.
Document Server customers not utilizing COLD documents
will be directed to
Storage Server migration.
Features of the Storage Server component:
• Individual storage servers can configured to access
specific storage repositories
• Supports load balancing between storage servers
accessing the same
repositories
• Allows additional access security to be assigned to
the document storage
repositories
Lookup Table Expiration Rules
This is in addition to the system wide document
expiration rule that was added in
KoVIS 4.0. This function allows an administrator to
define specific expiration rules for
field values defined in a lookup table (e.g. document
type).
• Lookup table field assignments will set initial
document expirations
• ‘Reset All’ function updates all document expiration
dates based on the current
rule for a specific field value
• ‘Set’ function updates all unassigned document
expiration dates based on the
current rule for a specific field value
• View expired documents through special hit list
• Document expiration date is template ready
User Exit Program Location Independence
If a custom exit module is not located in the client
program directory, the exit will
search the server program directory for the module.
Command Line Invocation for DB Engine and Custom
Import
These utilities have been updated such that they can now
be started from a
command line that specifies a username and password.
System Integration
Export to G360 emPower (Identitech)
The KoVIS export feature has been expanded to optionally
create an MSB file that
can be used to import the KoVIS documents into a g360
emPower (Identitech)
workflow system through QA Import.
Addition of a Custom Import module to support the G360
Scan Manager
This new module will accept batches from the G360 Scan
Manager. It provides
configuration for the following options:
• First page delete
• Blank page delete (front or back)
• Convert JPG to TIFF
• Enable / disable batch verification
API Enhancements
Additional Web Service Methods
To expand upon the initial KoVIS 4.0 offering of the
basic Web Service methods
(Login, Logout, Get Hitlist, and Get Documents), the
following methods have been
added for KoVIS 4.1:
• Get Data Entry templates
• Get Hitlist views
• Get Remarks
• Get Groups
• Get Retrieval templates
• Get Users
• Get RP Requests
• Get KoVIS WSDL
Resolved PNs
PN Description
PN2694
If a template was created manually as opposed to the
default template, the new
template was not available as a choice in DBEngine.
PN4108
After documents from a CD were imported to a cache,
there were no images
available.
PN4125
When using an Oracle Database as a Static File for an
Application with Data Entry,
the system was returning an error "Cannot load
eporcl.dll"
PN4130
KoVIS was trying to access some SQL tables using the SQL
KoVIS userid as the
owner (kovis.tablename). Since in fact, dbo was the
owner, the call failed.
PN4143
KoVIS v4.0 was not able to find User Exit DLL files
unless they were copied to the
Client Bin directory.
PN4148
Callback user exits did not work with retrieval but did
with data entry. The error was
"Can't load eporcl.dll,isdb1"
PN4158
KoVIS Web and the KoVIS API did not allow a retrieval
template with duplicate
fields to perform correctly.
PN4173
Trying to view a multi-page tiff file through indexing
or retrieval was resulting in an
error message. "Page index is not in the range of page
count". Only the first page
was displayed.
PN4179
DBEngine would not load data into an application after
data fields had been added
to that existing application.
PN4195
KoVIS Web would not retrieve documents with a Master ID
greater then 32000.
PN4196
Using KoVIS Web, if a document was retrieved from a CD
or similar device where
the file had a read only attribute, the user would get
an error when they retrieved
that document a second time during the same session.
PN4198
When documents were logically deleted from the hit list,
they seemed to have been
removed. When the hit list was regenerated however, the
documents re-appeared.
PN4255
When exporting documents from KoVIS, if the user chose
to set the delete flag
after export, all documents in the application table
were deleted, not just those
matching the search criteria.
PN4258
If a manually created template was used in Data Entry
with documents having
idx.dat files with index data, the index data was put
into the wrong index fields.
KoVIS 4.0
Implemented Enhancements
1. KoVIS Web
To better reflect the capabilities, KoVIS Internet
Retrieval has been renamed to KoVIS Web.
KoVIS Web continues to converge on feature parity with
the PC client while providing this functionality within
the context of the browser-based environment.
Inbox
Displays requests for documents submitted through the
KoVIS Request Processor.
Internet users can retrieve and view the index data and
images of the documents in
processed folder requests.
Password management
Internet users can now manage their KoVIS password if
permitted through the OSsecurity settings.
Display of lookup table fields
Fields with an associated lookup table (e.g. document
type) are shown on the retrieval
template with both the short and long names (e.g. COR -
Correspondence).
Index data modification
Document indexes can now be modified through KoVIS Web
if the appropriate KoVIS
permissions have been granted to the user.
File data entry
Document image files can now be data entered directly
through KoVIS Web. The initial
offering of this feature supports single file documents.
Document remark view/management
Unformatted remarks can now be added, viewed or deleted
through KoVIS Web.
COM API utilization
This is a structural change that not only positions
KoVIS Web for future improvements,
but also demonstrates our commitment to expose KoVIS
functionality through APIs.
Installer
The KoVIS Web component now offers a full-featured
installer, which will greatly simplify
the installation and upgrade process for future
releases.
Windows 2003 Server support
KoVIS Web 4.0 now supports Microsoft Windows 2003 Server
as a Web Application
Server. The only restriction is that hit lists cannot be
generated with thumbnails.
System Administration
Features have been added to ease system
administration and deployment, to increase
performance, to provide additional resource control, and
to improve system security.
Field level security
Along with function, application, template, and document
security, KoVIS can now secure
information at the field level. This will allow an
administrator to restrict access to a field
such as salary only to secured users. This security
impacts template access, hit list
display, and index data modification.
Application hit list views
After using the KoVIS client to create hit list views
(layouts) for specific applications, the
system administrator can assign these views to users and
groups. Users that have been
assigned a hit list view will automatically utilize this
view if they have not created their
own custom hit list layout.
Group segmentation of license seats
The system administrator can now allocate system license
seats to KoVIS groups. This
will permit a department within an enterprise to reserve
a minimum number of license
seats specifically for their departmental usage. Any
system users can use unallocated
license seats.
Automated KoVIS client update
In order to ease the deployment of KoVIS, the KoVIS
client now offers a self-updating
feature. To take advantage of this feature for future
releases, the KoVIS administrator will
simply upgrade the KoVIS server. The KoVIS client users
will be automatically prompted
to update upon logon.
Client side binaries
The KoVIS client installation now installs the
application files directly to the local PC. This
enhancement to the KoVIS client will significantly boost
system performance.
Microsoft server clustering support
KoVIS is now supported in a Microsoft server-clustered
configuration. This allows KoVIS
to take advantage of the resource sharing and redundancy
of a Microsoft server clustered
environment.
3. Document Management
KoVIS now offers functionality for page level
document management. Access to the following features is
controlled through KoVIS security.
Document page delete
Users can delete pages within a document.
Add document pages
Users can add pages within a document.
Intra-document page move
Users can move pages within a document.
Inter-document page move Users can move pages between
documents.
Users can export a range of pages from a document.
Change index data
The previously available “Change Index Data” feature has
been extended such that
multiple hit list records may now be selected for
update. This feature extension provides new mass update
ability, which increases user productivity.
Document retention/expiration
Permits an administrator to define a system document
retention/expiration rule. When
documents mature to the expiration rule, they can be
retrieved and deleted.
4. Ease of Use
The following features have been added to KoVIS to
provide an improved user experience.
Retrieval – clear all fields
The KoVIS retrieval template now provides a feature that
will clear all template fields and
reset all logical operands and selection boxes.
Application sort
Wherever applications are displayed (retrieval, inbox,
data entry, etc), they will now be
shown in alphabetic order. Previous versions displayed
applications in order of creation.
Startup hourglass
Upon logon, an hourglass will be presented to the user
during the startup process.
Improved – “Cannot write to DB” messages
More extensive error messaging is included within the DB
Engine module.
Export and import of application definition
Application administration will now allow an
administrator to export a KoVIS application
definition. The resulting XML export can be imported
into another KoVIS system. The
import process will automatically create the application
and application fields. This feature
provides for the simple transfer of KoVIS application
definitions from one KoVIS system
to another.
Support for multiple Kodak DAW/i9600/i4800 devices
KoVIS can now support multiple Kodak DAW/i9600/i4800
devices within a single KoVIS
system.
Overwrite message for demo software
When upgrading a KoVIS demo system, the install program
will now allow the installer to
choose if the database should be overwritten or
preserved.
5. API Enhancements
A customer created program can now control
administration functions through the Administrative
APIs. In addition, the Retrieval APIs have been
enhanced, a new Retrieval Web Service is offered, and the
API logon performance has improved by at least 50%.
Admin API
A set of COM based API methods have been created that
expose KoVIS user and group
management functionality. The usage of these
Administrative APIs is limited to users
that have administrative rights. These APIs offer the
following abilities:
.. User management
.. Group management
.. User to ‘hit list view’ assignment
.. Group to ‘hit list view’ assignment
.. User to group assignment
• User password management
Retrieval API
• The COM based Retrieval API has been enhanced to
provide user request
information. This new interface has been used to provide
the ‘Inbox’ feature for
KoVIS Web.
• Functionality has been exposed though the COM APIs
that provide for document
thumbnail creation.
Web Services
Retrieval Web Services have been added for easy and more
flexible integration of Web
applications. KoVIS Web Services take advantage of XML
and SOAP technology.
6. Storage
Through the addition of EMC Centera support and the new
KoVIS Storage Server, the robustness
of the KoVIS document handling has evolved to a new
level.
Centera device support
KoVIS now supports document storage and retrieval to an
EMC Centera device. This is a
sophisticated integration using the Centera low level
API. Through KoVIS device
administration, an administrator can define an EMC
Centera device (or cluster) as a
KoVIS storage device. Once an EMC Centera device is
established within the KoVIS
system, document cache scan be migrated to the Centera
device. Document retrieval
through the Centera device will be transparent to the
end user.
Storage Server
KoVIS 4.0 offers the Initial Availability of the Storage
Server. This feature will be distributed in a controlled
manner to interested customers. The Storage Server will
allow
a server agent (storage server) to perform retrieval and
data entry requests on the behalf
of a user. This new feature will allow workstations to
be completely secured from KoVIS
document archives (caches, jukeboxes, etc). Multiple
Storage Servers may be defined
within a KoVIS system to provide for system scalability.
Key Flow Integration
KoVIS and Key Flow have been integrated to provide a
powerful imaging and workflow solution.
Key Flow 7.1 Integration
The integration is accomplished through a new KoVIS data
entry template user exit. This
user exit is controlled by an XML parameter file that
allows for the definition of business
rules for starting a flow. This flexible integration
allows image links and metadata to be
passed to the workflow
Resolved PNs
PN Description
PN3775 If a user was given permission to an application,
archive, or template, but that
modification was cancelled, KoVIS Admin crashed.
PN3805 If the DAW List File program was started, stopped
and then started again, duplicate
entries were put into the list file.
PN3824 With data entering microfilm documents, KoVIS was
not returning to the correct
frame after a logout & login.
PN3867 When the "Check CD./.Cache" button and then a
network CD device were selected,
Device Administrator was hanging.
PN3902 When importing documents with suffix records or
running Database Engine on
batches with suffix records, the Master ID put into the
suffix records was incorrect.
Suffix records should all have had the same Master ID as
the 0 suffix record. This affected updates of records
with suffixes when using the COM API
PN3935 If multiple DAW transfer files were selected in
the DAW Update module, a sharing
violation error occurred when processing the second
transfer file. Subsequent
transfer files were not processed.
PN3962 After using change data functionality to update a
document in the hit list, the hit list
entry for the document was not correctly updated. This
happened when using suffix
functionality.
PN3963 After using change data functionality to update a
document in the hit list, the LOG5
table contained incorrect data. This happened when using
suffix functionality. The
application and archive were missing.
PN3971 When returning to the hit list after using Change
Data functionality, the original
selected document had a remarks icon next to it, and all
of its index fields were
gone.
PN4003 Change data failed when trying to update a suffix
document originally created
through the hit list.
PN4011 When importing an external folder that was
created from a CD and choosing Indexes
Only, the system crashed.
PN4017 When importing an external folder and choosing
Indexes and Documents, the
documents were copied to cache, but the indexes were not
written to the database. |
