Browse Prior Art Database

OfficeVision/400 Host Object Handling Platform

IP.com Disclosure Number: IPCOM000107984D
Original Publication Date: 1992-Apr-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 3 page(s) / 105K

Publishing Venue

IBM

Related People

Padzieski, RJ: AUTHOR [+2]

Abstract

This article describes a method for providing specific, user-defined procedures for documents in a seamless manner. The procedures are specified by user, action, and document type.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

OfficeVision/400 Host Object Handling Platform

       This article describes a method for providing specific,
user-defined procedures for documents in a seamless manner. The
procedures are specified by user, action, and document type.

      Currently, OfficeVision*/400 (OV/400) only supports some
document types.  If a user wants to work with other object types, the
user must leave OV/400 and enter another application.

      This invention also provides the capability to pull all the
applications that a user uses with documents under a single
interface.  That is, no matter what application the user needs to use
with a document, the system will determine the proper application to
invoke to get the work done.  The end user will only select the
action that he wants to perform.

      The OV/400 Host Platform is an enabler for other applications
to snap-in to the document-handling capabilities of OV/400.  It is
intended to provide a seamless interface to the end user when working
with applications that use the platform.  After the application has
been configured, the end user should be able to work the objects that
are generated by that application as he has always worked with those
objects with the OV/400 application.

      This is accomplished by configuring the application to the
system and defining the application(s) that the users will use.
There are four tables used to configure the application.  These
tables are:
-  Class Definition Table
   This table defines the document types that an application will
use.  Each class of documents will be composed of one or more
document types.  For example, the class WPDOC (Word Processing
Document) may consist of the document types RFTDCA, RFTDW4, RFTAS400,
and WPINT.  This table is also used for applications to register
their own document types with the system (as with WPINT in the
previous example) and to group the IBM-defined document types into
logical categories.
-  User Registration Table
   This table defines the applications that a user will use. Given a
document class and the user id, the system will determin...