Workflow systems and methods

• US 6,170,002 B1
• Filed: 01/25/1999
• Issued: 01/02/2001
• Est. Priority Date: 07/28/1997
• Status: Expired due to Term

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Solectron Corporation (Flex, Ltd.)
• Inventors: Ouchi, Norman Ken
• Primary Examiner(s): Maung, Zarni
• Application Number:
  US09/237,078
• Time in Patent Office: 708 Days
• Field of Search: 709/206, 709/219, 709/203, 709/217, 709/200, 709/245, 709/239
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

The present invention relates to message-based workflow systems and methods for computers operating on the World Wide Web. In one embodiment, the present invention provides a form route manager connected to an e-mail system and the World Wide Web. In another embodiment, the present invention provides a form route manager and computers connected to the e-mail system and the World Wide Web.

Claims

1. A workflow system for processing a document, wherein the workflow system is connected to the Web and to an e-mail system, comprising:

a first form route manager providing a Web page with a first URL, wherein the Web page includes the document, and a step field, wherein the first form route manager is capable of accessing a route, a sequence of e-mail addresses, comprising a first sequencer adapted to;

compare the step field with the route,

define the next e-mail address based on the compare,

update the e-mail address to the next e-mail address, and

update the step field to the next step; and

an out-box adapted to send an e-mail with a second URL to the next e-mail address.

2. The workflow system of claim 1, wherein the first form route manager is capable of accessing multiple routes, each route having an identifier and the Web page having a route indicator, and wherein the first sequencer is further adapted to compare the route indicator with the route identifiers until the route indicator matches one route identifier, and determine the route for the document based on the match.

3. The workflow system of claim 1 or 2, wherein the document has an identifier and the first form route manager further includes a location table with the document identifier and the next e-mail address of the document, and a move history table with a list of each e-mail address, which accessed the document.

4. The workflow system of claim 3, wherein the Web page includes a-user settable field for requesting status of the workflow and a document identifier, wherein the first form route manager includes a second sequencer adapted to match the document identifier of the Web page to a document identifier in the location table or in the move history table, and return status to the e-mail address requesting status.

5. The workflow system of claim 1, wherein the Web page includes a branch indicator settable by the user at the e-mail address, and the first form route manager is capable of accessing multiple routes, each route having an identifier, and the first sequencer is further adapted to match the branch indicator of the Web page with one identifier of the multiple routes, and determine the route for the document.

6. The workflow system of claim 1, wherein the Web page includes a user settable route modifier, which modifies the next e-mail address to be other than the next e-mail address as defined by the route.

7. The workflow system of claim 1, wherein a new route is made from the sequence of e-mail addresses in the move history table.

8. The workflow system of claim 1, further comprising a second form route manager, wherein the route is divided into a first segment and a second route segment, wherein the first form route manager accesses the first route segment and the second form route manager accesses the second route segment.

10. The workflow system of claim 1, wherein the first form route manager can access a form library, wherein the e-mail address in the route has a form field defining a form in the form library and the first sequencer is further adapted to select the associated form, and embed the selected form in the Web page.

11. The workflow system of claim 1, wherein the route splits into a plurality of branch routes at a fork e-mail address, wherein the first sequencer is adapted to compare the step field with the route at the fork e-mail address and for one of the plurality of branch routes copy the e-mail, set the step field to the next step of the one branch route, and set the e-mail address to the next e-mail address of the one branch route.

12. The workflow system of claim 1, the route further comprising a plurality of branch routes converging at a join e-mail address, wherein the first form route manager includes a receipt indicator for each branch route to determine the branch route of the Web page, set the receipt indicator of the branch route, and determine from a plurality of receipt indicators if an e-mail is to be sent to the join e-mail address.

13. The workflow system of claim 1, further comprising a timer, wherein the first form route manager is adapted to start the timer when the first form manager sends the e-mail to the next e-mail address and compare the timer count against a set value until the Web page is accessed at the next e-mail address or the timer count exceeds the set value.

14. The workflow system of claim 13, further comprising an e-mail notification address, wherein if the timer count exceeds the set value, then the first form route manager is adapted to send an e-mail to the e-mail notification address.

15. The workflow system of claim 1, further comprises a second form route manager, providing a Web page with a third URL, and adapted to access the route accessed by the first form route manager, wherein the first sequencer is further adapted to add the third URL to the e-mail, and wherein the second form route manager replaces the first form route manager when the first form route manager fails.

17. The workflow system of claim 1, wherein the first form route manager is adapted to redefine the route based on a new route submitted in the Web page.

18. The workflow system of claim 1, wherein the route includes a plurality of branch routes from a fork e-mail address, wherein the first form route manager is adapted to select a branch route based on the number of e-mail at the first e-mail address of each branch route.

9. The workflow system of 8, wherein the last e-mail address in the first route segment is the e-mail address of the second form route manager.

16. The workflow system of 15, wherein the next e-mail address is further adapted to access the Web page provided by the second form route manager.

19. The workflow system of 1, wherein the next e-mail address includes an in-box adapted to receive the e-mail from the first form route manager and an access to the Web page using the second URL in the e-mail.

20. The workflow system of 1, wherein the first form route manager includes a Web site.

21. A workflow system for processing a document, wherein the workflow system is connected to the Web and to an e-mail system, comprising:

a form route manager capable of providing access to a Web page containing the document, defining a route, a step-by-step sequence of e-mail addresses, sending an e-mail to an e-mail address in the route, and adapted to send the e-mail to the next e-mail address in the route.

22. The workflow system of claim 21, wherein the Web page has a route indicator and wherein the form route manager is further capable of defining multiple routes, each route having an identifier, comparing the route indicator with each route identifier, and determining the route for the Web page.

23. The workflow system of claim 21 or 22, wherein the document has an identifier and the form route manager further includes a location table with the document identifier and the next e-mail address of the document, and a move history table with the document identifier and a list of every e-mail address, which accessed the document.

24. The workflow system of claim 21, wherein the route includes a plurality of branch routes at a step in the route, wherein the Web page includes a settable branch indicator and wherein the form route manager is adapted to select the branch route based on the setting of the branch indicator.

25. The workflow system of 21, wherein the next e-mail address is adapted to access the Web page using the e-mail.

26. The workflow system of 21, wherein the form route manager includes a Web site.

27. A workflow system for processing a document, wherein the workflow system is connected to the Web, comprising:

a form route manager capable of providing access to a Web page containing the document, defining a route, a step-by-step sequence of Web addresses, sending Web page data to a Web address in the route, and wherein the form route manager is adapted to send the Web page data to the next Web address in the route.

28. The workflow system of 27, wherein the Web page has a route indicator and wherein the form route manager is further capable of defining multiple routes, each route having an indicator, comparing the route indicator with each route identifier, and determining the route for the Web page.

29. The workflow system of 27 or log, wherein the document has an identifier and the form route manager further includes a location table with the document identifier and the next Web address of the document, and a move history table with the document identifier and a list of every Web address, which accessed the document.

30. The workflow system of 27, wherein the route includes a plurality of branch routes at a step in the route, wherein the Web page includes a settable branch indicator and wherein the form route manager is adapted to select the branch route based on the setting of the branch indicator.

31. The workflow system of 27, wherein the next Web address is adapted to access the Web page using the Web page data.

32. The workflow system of 27, wherein the form route manager includes a Web site.

33. A workflow system for processing a document, wherein the workflow system is connected to the Web, comprising:

a first form route manager, providing a Web page with a first URL, wherein the Web page includes the document, and a step field, wherein the first form route manager is capable of accessing a route, a sequence of Web addresses, comprising a first sequencer adapted to;

compare the step field with the route,

define the next Web address based on the compare,

update the Web address to the next Web address, and

update the step field to the next step; and

wherein the first form route manager is adapted to send Web page data with a second URL to the next Web address.

34. The workflow system of claim 33, wherein the first form route manager is capable of accessing multiple routes, each route having an identifier and the Web page having a route indicator, and wherein the first sequencer is further adapted to compare the route indicator with the route identifiers until the route indicator matches one route identifier, and determine the route for the document based on the match.

35. The workflow system of claim 33 or 34, wherein the document has an identifier and the first form route manager further includes a location table with the document identifier and the next Web address of the document, and a move history table with a list of each Web address which accessed the document.

36. The workflow system of claim 35, wherein the Web page includes user settable field for requesting status of the workflow and a document identifier, wherein the first form route manager includes a second sequencer adapted to match the document identifier of the Web page to a document identifier in the location table or in the move history table, and return status to the Web address requesting status.

37. The workflow system of claim 33, wherein the Web page includes a branch indicator settable by the user at the Web address, the first form route manager is capable of accessing multiple routes, each route having an identifier, and the first sequencer is further adapted to match the branch indicator of the Web page with one identifier of the multiple routes and determine the route for the document.

38. The workflow system of claim 33, wherein the Web page includes a user settable route modifier, which modifies the next Web address to be other than the next Web address as defined by the route.

39. The workflow system of claim 33, wherein a new route is made from the sequence of Web addresses in the move history table.

40. The workflow system of claim 33, further comprising a second form route manager, wherein the route is divided into a first segment and a second route segment, wherein the first form route manager accesses the first route segment and the second form route manager accesses the second route segment.

42. The workflow system of claim 33, wherein the first form route manager can access a form library, wherein the Web address in the route has a form field defining a form in the form library and the first sequencer is further adapted to select the associated form, and embed the selected form in the Web page.

43. The workflow system of claim 33, wherein the route splits into a plurality of branch routes at a fork Web address, wherein the first sequencer is adapted to compare the step field of the Web page with the route at the fork Web address and for one of the plurality of branch routes copy the Web page data, set the step field to the next step of the one branch route and set the Web address to the next Web address of the one branch route.

44. The workflow system of claim 33, further comprising a plurality of branch routes converging at a join Web address, wherein the first form route manager includes a receipt indicator for each branch route and is adapted to determine the branch route of the Web page, set the receipt indicator of the branch route, and determine from a plurality of receipt indicators if Web page data is to be sent to the join Web address.

45. The workflow system of claim 33, further comprising a timer, wherein the first form route manager is adapted to start the timer when the first form route manager sends Web page data to the next Web address and compare the timer count against a set value until the Web page is accessed at the next Web address or the timer count exceeds the set value.

46. The workflow system of claim 45, further comprising a e-mail notification address, wherein if the timer count exceeds the set value, then the first form route manager is adapted to send an e-mail to the e-mail notification address.

47. The workflow system of claim 33, further comprises a second form route manager, providing a Web page with a third URL, and adapted to access the route accessed by the first form route manager, wherein the first sequencer is further adapted to add the third URL to the Web page data, and wherein the second form route manager replaces the first form route manager when the first form route manager fails.

49. The workflow system of claim 33, wherein the first form route manager is adapted to redefine the route based on a new route submitted in the Web page.

50. The workflow system of claim 33, wherein the route includes a plurality of branch routes from a fork Web address, wherein the first form route manager is adapted to select a branch route based on the number of Web page data at the first Web address of each branch route.

41. The workflow system of 40, wherein the last Web address in the first route segment is the Web address of the second form route manager.

48. The workflow system of 47, wherein the next Web address is further adapted to access the Web page provided by the second form route manager.

51. The workflow system of 33, wherein the next Web address includes a Web browser adapted to receive the Web page data from the first form route manager and an access the Web page using the Web page data.

52. The worklfow system of 33, wherein the first form route manager includes a Web site.