Unified model for authoring and executing flow-based and constraint-based workflows

• US 8,103,536 B2
• Filed: 08/13/2010
• Issued: 01/24/2012
• Est. Priority Date: 10/01/2004
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Green, David G., Mehta, Bimal K., Thatte, Satish R., Shukla, Dharma K., Parasnis, Abhay Vinayak
• Primary Examiner(s): Jasmin, Lynda
• Assistant Examiner(s): Singh, Gurkanwaljit
• Application Number:
  US12/855,756
• Publication Number:
  US 20100306000A1
• Time in Patent Office: 529 Days
• Field of Search: None
• US Class Current: 705/7.27
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 10/0633 Workflow analysis

Abstract

Designing and executing a workflow having flow-based and constraint-based regions. A user selects one or more activities to be part of a constraint-based region. Each constraint-based region has a constraint associated therewith. The workflow is executed by executing the flow-based region and the constraint-based region. The flow-based region executes sequentially. The constraint is evaluated, and the constraint-based region executes responsive to the evaluated constraint.

Claims

1. A computer-implemented method for modeling a workflow, said workflow representing a business process, said method comprising:

presenting a plurality of activities to a user;

receiving from the user a first selection of the activities and a flow specification associated therewith;

grouping, by a computer, the received first selection of activities;

receiving, by the computer, from the user another selection of the activities and a constraint associated with each of the activities from the other selection, said constraint including a function that enables the activity associated therewith for execution when the constraint is satisfied, said activities from the received first selection being different from the activities from the other selection; and

generating, by the computer, a constrained activity group (CAG) including one or more of the activities from the other selection, said CAG defining at least one of the following conditions for the one or more of the activities from the other selection in the CAG;

the constraint can be disabled at any time after the constraint has been enabled;

when an enabled constraint becomes true, the enabled constraint declares that the activity associated therewith is ready for execution and must be enabled;

when a completion condition of an executing activity is evaluated to be true at any time, any and all executing activities contained within the CAG are immediately canceled;

merging, by the computer, the received other selection of the activities with the grouped selection of activities to create a workflow;

executing, by the computer, the activities from the first selection in the merged workflow;

during executing the activities from the first selection, determining, by the computer, a change in the constraint for each of the activities from the other selection in the merged workflow, said change resulting from changes to data in the function included in the constraint; and

enabling, by the computer, the execution of each of the activities from the other selection in the CAG when the constraint associated therewith is satisfied as a function of the determined change, wherein a course of execution of the merged workflow is guided by the constraints associated with the activities from the other selection of the user contained within the CAG.

2. The method of claim 1, wherein grouping the received first selection of activities occurs in accordance with the received flow specification, said received first selection of activities being well-defined control flow activities that are processed based on the flow specification and that are complete when an endpoint for the activities is reached.

3. The method of claim 1, wherein each of the activities from the other selection is an activity that is executed not based on the flow specification, is executed in any order, and is executed whenever the constraint associated with an activity from the other selection is satisfied.

4. The method of claim 1, wherein executing the activities from the first selection in the merged workflow occurs according to the flow specification.

5. The method of claim 1, further comprising defining the constraint.

6. The method of claim 1, further comprising executing the created workflow by:

evaluating the constraint; and

executing the activities from the other selection as a function of said evaluating.

7. The method of claim 1, further comprising executing the created workflow by executing the activities with the received selection of activities in accordance with the flow specification.

8. The method of claim 1, wherein presenting the plurality of activities to the user comprises displaying the plurality of activities on a display.

9. A system comprising a plurality of computer executable components tangibly embodied on computer-readable storage media that, when executed by a computer, model a workflow having a flow-based region and a constraint-based region, said system comprising:

a display component for presenting a plurality of activities to a user;

an interface component for receiving from the user a first selection of the activities, said interface component further receiving from the user another selection of the activities and a constraint associated with each of the activities from the other selection, said constraint for each of the activities associated therewith from the other selection including a function that enables the activities for execution when the constraint is satisfied, said activities of the received first selection being different from the activities of the other selection; and

a designer component for grouping the received selection of activities in accordance with the received flow specification, said designer component generating a constrained activity group (CAG) including one or more of the activities from the other selection, said CAG defining at least one of the following conditions for the one or more of the activities from the other selection in the CAG;

the constraint can be disabled at any time after the constraint has been enabled;

when an enabled constraint becomes true, the enabled constraint declares that the activity associated therewith is ready for execution and must be enabled;

when a completion condition of an executing activity is evaluated to be true at any time, any and all executing activities contained within the CAG are immediately canceled, said designer component further merging the received other selection of the activities with the grouped selection of activities to create a workflow;

wherein the designer component determines a change in the constraint in each of the activities from the other selection in the merged workflow during executing the activities from the first selection, said change resulting from changes to data in the function included in the constraint; and

wherein the designer component enables the execution of each of the activities from the other selection in the CAG when the constraint associated therewith is satisfied as a function of the determined change, wherein a course of execution of the merged workflow is guided by the constraints associated with the activities from the other selection of the user contained within the CAG.

10. The system of claim 9, wherein the interface component has a flow specification associated therewith.

11. The system of claim 9, said received first selection of activities being well-defined control flow activities that are processed based on the flow specification and that are complete when an endpoint for the activities is reached.

12. The system of claim 9, wherein each of the activities from the other selection is an activity that is executed not based on the flow specification, is executed in any order, and is executed whenever the constraint associated with each of the activities from the other selection is satisfied.

13. The system of claim 9, wherein the designer component presents the activities from the first selection in the merged workflow according to the flow specification.

14. The system of claim 9, further comprising a runtime component for executing the created workflow by:

evaluating the constraint; and

executing the activities from the other selection of the activities as a function of said evaluating.

15. The system of claim 9, further comprising a runtime component for executing the created workflow by executing the activities from the received selection of activities in accordance with the flow specification.

16. The system of claim 9, wherein the display component, interface component, and the designer component execute within an execution environment of an application program.

17. The system of claim 9, wherein the constraint comprises a completion semantic.