System and method of executing and controlling workflow processes

• US 20040153350A1
• Filed: 01/31/2003
• Published: 08/05/2004
• Est. Priority Date: 01/31/2003
• Status: Active Grant

• Current Assignee: Bizflow Corporation
• Original Assignee: HandySoft Corporation (HANDYSOFT, Inc.)
• Inventors: Kim, Yeong-Ho, Lee, Misuk
• Granted Patent: US 7,168,077 B2
• Time in Patent Office: Days
• US Class Current: 705/8
• CPC Class Codes: G06Q 10/0633 Workflow analysis
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A method of executing and controlling a workflow process includes a request-response control process for coordinating activities between a plurality of entities, whereby an entity creates and sends a message requesting execution of an activity and another entity receives, parses and responds to the request. The message includes activity-specific data and activity status data. The activity status data signifies, for example, whether a corresponding activity has been successfully performed (i.e., completed) or failed. Process information, including control logic for the workflow process, is specified in an at least one uncompiled document, which may include an extensible stylesheet and an extensible markup language document. A document type definition defines the structure of the document. The control logic may include serial, AND-parallel, OR-parallel, XOR-parallel, CON-parallel and iterative instructions and a definition of successful completion and/or failure for an activity according to the control logic. The control logic also specifies a forward transition for a completed activity and a backward transition for a failed activity. A parser processes the message according to the control logic for the workflow process and the document type definition. A compiled workflow engine and database are not required.

Claims

1. A method of building, executing and controlling a workflow process without using a compiled workflow engine to execute and control the workflow process comprising steps of:

providing a control logic for the workflow process;

providing a process model for the workflow process;

creating a message that requests execution of an activity, the message including activity-specific data and activity status data; and

processing the message according to the process model and control logic for the workflow process.

2. The method of claim 1, wherein the process model is defined in a first uncompiled document and the control logic is defined in a second uncompiled document.

3. The method of claim 2, further comprising a step of creating a document type definition that defines the structure of the first uncompiled document.

4. The method of claim 3, wherein the activity status data further includes at least one flag from the group consisting of successful, failed, resume, suspend and terminate.

5. The method of claim 4, wherein the control logic further includes a first instruction for performing a forward transition if the activity status data includes a “

successful”

flag and a second instruction for performing a backward transition if the activity status data includes a “

failed”

flag.

6. The method of claim 5, wherein the control logic further includes a serial instruction indicating that the activity should be executed promptly.

7. The method of claim 5, wherein the activity is comprised of one activity or a plurality of sub-activities, and the control logic includes at least one logic instruction from the group consisting of:

a serial instruction indicating that the activity should be executed promptly, and if the activity executes successfully then a completed status is associated with the activity, and if the activity does not execute successfully then a failed status is associated with the activity,

an AND-parallel instruction indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed concurrently, and if all of the sub-activities execute successfully then a completed status is associated with the activity, and if any of the sub-activities do not execute successfully then a failed status is associated with the activity,

an OR-parallel instruction indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed concurrently, and if a sub-activity executes successfully then a completed status is associated with the activity, and if all of the sub-activities do not execute successfully then a failed status is associated with the activity,

an XOR-parallel instruction indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed in order of decreasing priority, from highest priority to lowest priority, until either a sub-activity executes successfully or the sub-activity having the lowest priority does not execute successfully, and if a sub-activity executes successfully then a completed status is associated with the activity, and if all of the sub-activities do not execute successfully then a failed status is associated with the activity,

a CON-parallel instruction indicating that, if the activity is comprised of a plurality of sub-activities, a determination is made if each sub-activity meets a specified condition, and if all sub-activities that meet the specified condition execute successfully then a completed status is associated with the activity, and if all of the sub-activities that meet the condition do not execute successfully then a failed status is associated with the activity,

an iteration instruction indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should be executed cyclically until a determination is made if a specified iteration condition is satisfied, and if the iteration condition is satisfied then a completed status is associated with the activity.

8. The method of claim 7, further comprising a step of performing a forward transition if a completed status is associated with the activity, or a backward transition if a failed status is associated with the activity.

9. A system for executing and controlling a workflow process without a compiled workflow engine to execute and control the workflow process, comprising:

means for providing a control logic for the workflow process;

means for providing a process model for the workflow process;

means for creating a message that requests execution of an activity, the message including activity-specific data and activity status data; and

means for processing the message according to the process model and control logic for the workflow process.

10. The system of claim 9, wherein the means for providing a process model is a first uncompiled document and the means for providing a control logic is a second uncompiled document having a structure.

11. The system of claim 10, further comprising a document type definition that defines the structure of the first uncompiled document.

12. The system of claim 11, wherein the activity status data further includes at least one flag from the group consisting of successful, failed, resume, suspend and terminate.

13. The system of claim 12, wherein the control logic further includes a first instruction for performing a forward transition if the activity status data includes a “

successful”

flag and a second instruction for performing a backward transition if the activity status data includes a “

failed”

flag.

14. The system of claim 13, wherein the control logic further includes a serial instruction indicating that the activity should be executed promptly, and means for associating a completed status with the activity if the activity executes successfully, and means for associating a failed status with the activity if the activity does not execute successfully.

15. The system of claim 14, wherein the activity is comprised of one activity or a plurality of sub-activities, and the control logic includes at least one logic instruction from the group consisting of:

a serial instruction indicating that the activity should be executed promptly, execution of the activity is completed if the activity is performed, and execution of the activity is failed if the activity does not perform,

an AND-parallel instruction, the AND-parallel indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed concurrently, and if all of the sub-activities execute successfully then a completed status should be associated with the activity, and if any of the sub-activities do not execute successfully then a failed status should be associated with the activity,

an OR-parallel instruction indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed concurrently, and if a sub-activity executes successfully then a completed status is associated with the activity, and if all of the sub-activities do not execute successfully then a failed status is associated with the activity,

an XOR-parallel instruction indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed in order of decreasing priority, from highest priority to lowest priority, until either a sub-activity executes successfully or the sub-activity having the lowest priority does not execute successfully, and if a sub-activity executes successfully then a completed status is associated with the activity, and if all of the sub-activities do not execute successfully then a failed status is associated with the activity,

a CON-parallel instruction indicating that, if the activity is comprised of a plurality of sub-activities, a determination is made if each sub-activity meets a specified condition, and if all sub-activities that meet the specified condition execute successfully then a completed status is associated with the activity, and if all of the sub-activities that meet the condition do not execute successfully then a failed status is associated with the activity,

an iteration instruction indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should be executed cyclically until a determination is made if a specified iteration condition is satisfied, and if the iteration condition is satisfied then a completed status is associated with the activity, and

the system further includes means for associating a completed status with the activity if the activity executes successfully, and means for associating a failed status with the activity if the activity does not execute successfully.

16. The system of claim 15 further comprising a means for performing a forward transition if a completed status is associated with the activity, or a backward transition if a completed status is associated with the activity.

17. The system of claim 16, wherein the means for performing a first activity includes an extensible markup language parser, the means for creating a message requesting execution of an activity includes an extensible markup language command, the message includes an extensible markup language document, and the means for providing control logic for the workflow process includes an extensible stylesheet document.

18. A method of building, executing and controlling a workflow process without using a compiled workflow engine to execute and control the workflow process, comprising steps of:

analyzing the workflow process into a unit;

arranging the unit under a set of rules;

associating the unit with a workflow control logic;

creating a process model;

requesting an activity;

processing the activity based on the process model and the workflow control logic; and

sending a response when the activity is complete,

wherein the process model is specified in a document type definition language,

wherein the activity is specified in a extensible mark up language, and

wherein the workflow control logic is specified in an extensible style sheet language.

19. The method of claim 18, wherein the processing step further comprises steps of:

performing a first activity;

creating a message requesting execution of a second activity, the message including activity-specific data and activity status data; and

specifying control logic information for the workflow process,

wherein the message can be processed according to the control logic information for the workflow process.

20. The method of claim 19, wherein the unit is a general-purpose component and independent of any specific process model.

21. The method of claim 20, wherein the workflow control logic is comprised of at least one instruction from the group consisting of:

a serial instruction indicating that an activity should be executed promptly, and if the activity executes successfully then a completed status is associated with the activity, and if the activity does not execute successfully then a failed status is associated with the activity,

an AND-parallel instruction indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed concurrently, and if all of the sub-activities execute successfully then a completed status is associated with the activity, and if any of the sub-activities do not execute successfully-then a failed status is associated with the activity,

an OR-parallel instruction indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed concurrently, and if a sub-activity executes successfully then a completed status is associated with the activity, and if all of the sub-activities do not execute successfully then a failed status is associated with the activity,

an XOR-parallel instruction indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed in order of decreasing priority, from highest priority to lowest priority, until either a sub-activity executes successfully or the sub-activity having the lowest priority does not execute successfully, and if a sub-activity executes successfully then a completed status is associated with the activity, and if all of the sub-activities do not execute successfully then a failed status is associated with the activity,

a CON-parallel instruction indicating that, if the activity is comprised of a plurality of sub-activities, a determination is made if each sub-activity meets a specified condition, and if all sub-activities that meet the specified condition execute successfully then a completed status is associated with the activity, and if all of the sub-activities that meet the condition do not execute successfully then a failed status is associated with the activity,

an iteration instruction indicating that, if the activity is comprised of a plurality of sub-activities, the sub-activities should be executed cyclically until a determination is made if a specified iteration condition is satisfied, and if the iteration condition is satisfied then a completed status is associated with the activity.

22. The method of claim 21, wherein the analyzing step further comprises steps of:

creating a document type definition for describing a general structure of the process model;

transforming the process model into an extensible markup language-friendly structure; and

describing the workflow control logic in extensible stylesheet language.

23. The method of claim 22, wherein the extensible markup language friendly structure is a tree structure.

24. A system for executing and controlling a workflow process without a compiled workflow engine to execute and control the workflow process, comprising:

a message processor;

a process unit that defines a process model;

a control unit that provides a workflow control logic; and

a message unit that sends and receives a message between activities.

25. The system of claim 24, wherein the message processor is an extensible markup language parser.

26. The system of claim 25, wherein the process unit has a document type definition that describes structures of the process model.

27. The system of claim 26, wherein the control unit is described in an extensible stylesheet language.

28. A method for defining a process control logic and a process model for a workflow, the method comprising steps of

creating a block model representing a workflow process, and

transforming the block model into one or more uncompiled computer processable documents that do not require a compiled workflow engine for processing, with the one or more uncompiled computer processable documents defining a process control logic and a process model.

29. A method according to claim 28, wherein the block model is comprised of a tree-structured model of blocks.

30. A method according to claim 29, wherein the blocks in the tree of blocks include units of representation that specify a behavioral pattern of process flow.

31. A method according to claim 30, wherein the blocks in the tree of blocks include one or more blocks from the group comprising:

an AND-parallel block indicating that, if an activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed concurrently, and if all of the sub-activities execute successfully then a completed status is associated with the activity, and if any of the sub-activities do not execute successfully then a failed status is associated with the activity;

an OR-parallel block indicating that, if an activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed concurrently, and if a sub-activity executes successfully then a completed status is associated with the activity, and if all of the sub-activities do not execute successfully then a failed status is associated with the activity;

an XOR-parallel block indicating that, if an activity is comprised of a plurality of sub-activities, the sub-activities should promptly be executed in order of decreasing priority, from highest priority to lowest priority, until either a sub-activity executes successfully or the sub-activity having the lowest priority does not execute successfully, and if a sub-activity executes successfully then a completed status is associated with the activity, and if all of the sub-activities do not execute successfully then a failed status is associated with the activity;

a CON-parallel block indicating that, if an activity is comprised of a plurality of sub-activities, a determination is made if each sub-activity meets a specified condition, and if all sub-activities that meet the specified condition execute successfully then a completed status is associated with the activity, and if all of the sub-activities that meet the condition do not execute successfully then a failed status is associated with the activity; and

an iteration block indicating that, if an activity is comprised of a plurality of sub-activities, the sub-activities should be executed cyclically until a determination is made if a specified iteration condition is satisfied, and if the iteration condition is satisfied then a completed status is associated with the activity.

32. A method according to claim 31, wherein the one or more uncompiled computer processable documents include one or more documents from the group comprising:

an XML document;

an XSL document; and

a DTD document.