Form route manager for workflow systems and methods

Details Form route manager for workflow systems and methods Form route manager for workflow systems and methods

2001-12-12

2003-04-22

Maung, Zarni (Department: 2154)

Electrical computers and digital processing systems: multicomput

Computer conferencing

Demand based messaging

C709S203000, C709S207000

Reexamination Certificate

active

06553407

ABSTRACT:

BACKGROUND OF THE INVENTION
The present invention relates to the field of computer networks, and in particular to workflow systems and methods used in computer networks to control, access, process, track, and modify documents.
A workflow system automates processing of documents in computer networks by defining the sequence of users with access to documents transmitted in the computer network. One application suitable for workflow is business travel reimbursement, having the following steps: (1) the traveler sends a request for reimbursement to a manager, (2) the manager reviews it; and (3) the manager either sends the approved request to accounting for payment or returns the request to the traveler for clarification. During the process, the users of the workflow system may want certain information. The manager may want information from the traveler before approval, accounting may want the total number of requests submitted by the traveler within the year, and the traveler may want to know where the request is in the process, especially if it is delayed.
A route describes the step-by-step sequence of a given workflow. The route may have a linear sequence and/or complex conditional branching. The latter type may require databases to store the independent parallel routes which later join to form a linear route. Simple workflow may require only an e-mail system to emulate paper-based procedures using mail and routing slips. As shown in
FIG. 1
a
, a database workflow system stores the document, the route, and the sequence of access in data tables. Because the information is stored in the memory of the database system, database systems can provide for complex routes, supply information on the document, and alert users to process delays. Many databases also have failure detection and recovery mechanisms to assure reliability. However, databases require that users employ specific programs to process the workflow, and remain connected to the database for the entire session, which can result in expensive long distance phone calls when users are remote from the database. Because the users may participate in many workflow processes, database workflow systems may require a number of specific programs to be loaded in their PCs and require access to a number of database. This may unnecessarily confuse users who must then identify the programs and the databases associated with a given workflow.
As shown in
FIG. 1
b
, an e-mail workflow system transmits the document and the route in the e-mail. This has the advantage that users only need e-mail programs such as Lotus cc:Mail or Microsoft Exchange. Further, a remote user such as a traveling manager can approve documents as remote e-mail. However, since key information about the document is in the e-mail, the workflow process fails if the e-mail is lost. Because there is no central memory, even basic information such as location of a document may be lost. In addition, since there is no access to global information, the e-mail workflow routes are limited to simple linear routes. Further, because the route is part of the e-mail and coded for a particular system, each PC must have a specific program to send the e-mail to the next user. So while users may have the advantage of easy access in e-mail workflow systems, they must have specific programs loaded in their PC before participating in the workflow process. This makes ad hoc creation of a workflow route impracticable, because the participants must have prepared in advance by loading all of the appropriate software in their PCs. As with the database workflow system in which many users participate in the workflow, an e-mail workflow requires many workflow programs be loaded in each PC, lacks capability to perform complex routes and track documents. Thus, the overall benefit of using current e-mail workflow systems is limited.
It would be desirable if workflow systems existed which could perform complex database functions, provide the easy accessibility of e-mail, avoid the need for specific programs in each PC, and insulate the user from the need to identify the pertinent server for a given workflow process.
SUMMARY OF THE INVENTION
The present invention relates to message-based workflow systems and methods. In one embodiment, the present invention provides three elements: (1) an e-mail system; (2) PC's, terminals, or workstations connected by the e-mail system; and (3) a form route manager connected by the e-mail system.
In one embodiment, the present invention provides an e-mail-based workflow system for processing a document, where the system is connected to a computer network and an e-mail system, comprising:
(1) a form route manager, connected to the computer network, capable of receiving and sending the e-mail, and capable of defining:
(2) a route, a step-by-step sequence of e-mail addresses, in the network; and wherein a computer with an e-mail address in the network is adapted to send the e-mail to the form route manager which is adapted to send the e-mail to the next e-mail address in the route.
In another embodiment, the present invention provides a method for centrally distributing an e-mail to a step-by-step sequence of e-mail addresses, comprising:
(1) receiving the e-mail with an indicator of the step in the sequence;
(2) determining from the indicator and the sequence, the successor e-mail address in the sequence;
(3) updating the e-mail indicator to the successor step; and
(4) sending the e-mail to the successor e-mail address.


REFERENCES:
patent: 4503499 (1985-03-01), Mason et al.
patent: 4799156 (1989-01-01), Shavit et al.
patent: 5040142 (1991-08-01), Mori et al.
patent: 5113393 (1992-05-01), Kam et al.
patent: 5182705 (1993-01-01), Barr et al.
patent: 5191522 (1993-03-01), Bosco et al.
patent: 5311438 (1994-05-01), Shellers et al.
patent: 5329626 (1994-07-01), Klein et al.
patent: 5436730 (1995-07-01), Hube
patent: 5457797 (1995-10-01), Butterworth et al.
patent: 5466159 (1995-11-01), Clark et al.
patent: 5469353 (1995-11-01), Pinsky et al.
patent: 5490097 (1996-02-01), Swanson et al.
patent: 5499364 (1996-03-01), Klein et al.
patent: 5513101 (1996-04-01), Pinsky et al.
patent: 5535322 (1996-07-01), Hecht
patent: 5548506 (1996-08-01), Srinivasan
patent: 5557515 (1996-09-01), Abbruzzese et al.
patent: 5586252 (1996-12-01), Bamard et al.
patent: 5623600 (1997-04-01), Ji et al.
patent: 5627764 (1997-05-01), Schutzman et al.
patent: 5632018 (1997-05-01), Otoril
patent: 5655084 (1997-08-01), Pinsky et al.
patent: 5666481 (1997-09-01), Lundy
patent: 5666492 (1997-09-01), Rhodes et al.
patent: 5675745 (1997-10-01), Oku et al.
patent: 5706452 (1998-01-01), Ivanov
patent: 5710921 (1998-01-01), Hirose
patent: 5716213 (1998-02-01), Clark et al.
patent: 5726920 (1998-03-01), Chen et al.
patent: 5732200 (1998-03-01), Becker et al.
patent: 5734837 (1998-03-01), Flores et al.
patent: 5735694 (1998-04-01), Clark et al.
patent: 5745687 (1998-04-01), Randell
patent: 5745901 (1998-04-01), Etner et al.
patent: 5751960 (1998-05-01), Matsunaga
patent: 5754857 (1998-05-01), Gadol
patent: 5761404 (1998-06-01), Murakami et al.
patent: 5765033 (1998-06-01), Miloslavsky
patent: 5765038 (1998-06-01), Flannery et al.
patent: 5767847 (1998-06-01), Mori et al.
patent: 5768506 (1998-06-01), Randell
patent: 5774656 (1998-06-01), Hattori et al.
patent: 5774661 (1998-06-01), Chatterjee et al.
patent: 5781857 (1998-07-01), Hwang et al.
patent: 5781901 (1998-07-01), Kuzma
patent: 5787175 (1998-07-01), Carter
patent: 5790789 (1998-08-01), Suarez
patent: 5790790 (1998-08-01), Smith et al.
patent: 5790847 (1998-08-01), Fisk et al.
patent: 5794039 (1998-08-01), Guck
patent: 5799297 (1998-08-01), Goodridge et al.
patent: 5802253 (1998-09-01), Gross et al.
patent: 5802493 (1998-09-01), Sheflott et al.
patent: 5805810 (1998-09-01), Maxwell
patent: 5822526 (1998-10-01), Waskiewicz
patent: 5826020 (1998-10-01), Randell
patent: 5826239 (1998-10-01), Du et al.
patent: 5826269 (1998-10-01), Hussey
patent: 5832455 (1998-11-01), Hayashi et al.
patent: 5838923 (1998-11-01), Lee et al.
patent: 5845255 (1998-12-01), May

Affiliated with

Also associated with

Rating

Form route manager for workflow systems and methods does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Form route manager for workflow systems and methods, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Form route manager for workflow systems and methods will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3049715