Workflow as data-transition driven, scriptable state machines

• US 7,607,130 B2
• Filed: 03/08/2004
• Issued: 10/20/2009
• Est. Priority Date: 07/01/1999
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Johnson, David C., Singh, Kaviraj, Toma, Tudor, Gellock, Scot J., Gomes, Carlos P., Wei, Min, Fernando, Joseph P.
• Primary Examiner(s): Nguyen; Van H
• Assistant Examiner(s): Tang; Kenneth
• Application Number:
  US10/795,591
• Publication Number:
  US 20040172445A1
• Time in Patent Office: 2,052 Days
• Field of Search: 718/1, 718/100, 718/101, 718/102, 709/202, 709/248, 707/1, 707/10, 707/100
• US Class Current: 718/100
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A computing workflow system has a workflow process definition contained in a workflow table as script functions. The workflow table is part of an extended database schema operating with an extended store, a workflow engine and a script engine. The novel workflow system includes a server database having a data table and an associated workflow table. A workflow extended store is communicatively coupled to the server database. A workflow engine is also communicatively coupled to the server database and to the workflow extended store. Further, a script engine is communicatively coupled to the workflow engine. The workflow table includes workflow rules and associated code to be executed by the workflow engine. Each row of the workflow table represents a workflow step. Script functions are defined in the workflow table to evaluate the condition and execute the action of each workflow step. The rules and associated code in the workflow table is both declarative and procedural. The workflow engine compares the data change information from the extended store procedure with the workflow definition in the workflow table and determines the appropriate step that needs to be executed. Then it checks execution permissions on that step. If execute permission is granted, the workflow engine evaluates the workflow step condition against the workflow table and, if true, it executes the step action. Upon completing the step action, the workflow engine commits all the changes made to the current item or to other items in the database.

Claims

1. A workflow system embodied on a computer-readable storage medium, comprising:

a workflow enabled data table that includes workflow triggers;

a workflow table that includes workflow rules and associated code;

a workflow extended store coupled to the workflow enabled data table and the workflow table, the workflow extended store includes extended store procedures;

a workflow engine coupled to the workflow enabled data table, the workflow table and the workflow extended store; and

a script engine coupled to the workflow engine;

wherein the workflow enabled data table and the workflow table are part of a database server, the database server including at least one timeout agent implemented as a server job, the at least one timeout agent scans the database server and executes at least one timeout workflow event when the database server indicates such a workflow event is due.

2. The workflow system of claim 1, the at least one timeout agent coupled to the workflow enabled data table and to the workflow engine.

3. The workflow system of claim 1, the at least one timeout agent scheduled to run with a definable frequency.

4. The workflow system of claim 1, the workflow triggers analyze a data modification request submitted to the workflow enabled data table.

5. The workflow system of claim 4, the workflow triggers invoke an extended store procedure.

6. The workflow system of claim 1, the workflow engine executes the workflow rules and associated code.

7. The workflow system of claim 1, the workflow engine invokes the script engine.