Granted Patent B1

US 8,799,174 · App. 11/763,904 · Granted Aug 5, 2014

Inventors: Jason J. Mitchell (Draper, UT); Marty Kurzinski (Jacksonville, FL); Richard Thomson (Salt Lake City, UT); Brian J. Kerr (Pleasant Grove, UT)

Assignee: Crimson Corporation

G06Q10/103

Abstract

Claims (31)

1. A computing device that implements a business process management system, comprising:

a processor;

memory in electronic communication with the processor;

a parent workflow process stored in the memory;

a child workflow process stored in the memory, wherein the parent workflow process includes a call to the child workflow process, wherein the parent workflow process comprises a first action and a second action, wherein the child workflow process comprises a third action and a fourth action, and wherein the actions are executed initially in the order of the first action, the second action, the third action and then the fourth action; and

a workflow engine that is configured to execute within a thread of execution the parent workflow process and the child workflow process, and that is configured to determine an undefined characteristic of the child workflow process with reference to data that corresponds to the parent workflow process in order to continue execution of the child workflow process, wherein the characteristic is a value of a field or a behavior of an action, wherein determining the undefined characteristic of the child workflow process comprises traversing the thread of execution in a reverse direction until the data is located that allows the undefined characteristic of the child workflow process to be defined, wherein traversing the thread of execution in the reverse direction comprises going back to previous actions starting at the fourth action in the order of the third action, the second action, and then the first action.

2. The business process management system of claim 1 , wherein the workflow engine is configured to use the data to define the characteristic of the child workflow process.

3. The business process management system of claim 1 , wherein the data corresponds to an action within the parent workflow process.

4. The business process management system of claim 3 , wherein the workflow engine is configured so that, upon locating the data, the workflow engine:

searches for additional data corresponding to one or more other actions that are positioned at a same level of the parent workflow process; and

uses the additional data to define the characteristic of the child workflow process.

5. The business process management system of claim 1 , further comprising:

a workflow core, wherein the parent workflow process, the child workflow process, and the workflow engine are located on the workflow core;

a plurality of core servers in electronic communication with the workflow core; and

a plurality of nodes in electronic communication with the core servers.

6. A method for facilitating the reuse of a child workflow process with multiple parent workflow processes, comprising:

during execution of the child workflow process within a thread of execution, determining, by a computing device, that a characteristic of the child workflow process is undefined, wherein the characteristic is a value of a field or a behavior of an action, wherein a parent workflow process comprises a first action and a second action, wherein the child workflow process comprises a third action and a fourth action, and wherein the actions are executed initially in the order of the first action, the second action, the third action and then the fourth action;

in response, traversing, by the computing device, the thread of execution in a reverse direction until data that allows the characteristic to be defined is located, wherein traversing the thread of execution in a reverse direction until the data is located comprises going back to previous actions starting at the fourth action in the order of the third action, the second action, and then the first action; and

using, by the computing device, the data to define the characteristic of the child workflow process in order to continue execution of the child workflow process.

7. The method of claim 6 , wherein the data corresponds to an action within a parent workflow process that called the child workflow process.

8. The method of claim 7 , further comprising, upon locating the data:

searching for additional data corresponding to one or more other actions that are positioned at a same level of the parent workflow process; and

using the additional data to define the characteristic of the child workflow process.

9. A non-transitory computer-readable medium comprising instructions that are executable to:

during execution of a child workflow process within a thread of execution, determine that a characteristic of the child workflow process is undefined, wherein the characteristic is a value of a field or a behavior of an action, wherein a parent workflow process comprises a first action and a second action, wherein the child workflow process comprises a third action and a fourth action, and wherein the actions are executed initially in the order of the first action, the second action, the third action and then the fourth action;

in response, traverse the thread of execution in a reverse direction until data that allows the characteristic to be defined is located, wherein traversing the thread of execution in a reverse direction until the data is located comprises going back to previous actions starting at the fourth action in the order of the third action, the second action, and then the first action; and

use the data to define the characteristic of the child workflow process in order to continue execution of the child workflow process.

10. The computer-readable medium of claim 9 , wherein the data corresponds to an action within a parent workflow process that called the child workflow process.

11. The computer-readable medium of claim 10 , wherein upon locating the data the instructions are also executable to:

search for additional data corresponding to one or more other actions that are positioned at a same level of the parent workflow process; and

use the additional data to define the characteristic of the child workflow process.

Assignments (29)