Dynamic human workflow task assignment using business rules

• US 9,852,382 B2
• Filed: 05/14/2010
• Issued: 12/26/2017
• Est. Priority Date: 05/14/2010
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Rangaswamy, Ravi, Stallard, Will, Lam, David C., Sharma, Sachin
• Primary Examiner(s): Fleischer, Mark A
• Application Number:
  US12/780,356
• Publication Number:
  US 20110282709A1
• Time in Patent Office: 2,783 Days
• Field of Search: 705 727, 705 726, 705 721, 705 711
• 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/0633 Workflow analysis
• CPC Class Codes: G06Q 10/103 Workflow collaboration or project management

Abstract

A system and method for dynamic human workflow task assignment using business rules. In accordance with an embodiment, a human workflow system is integrated directly with business rules, to determine human task routing patterns, and participants in human tasks. Routing of tasks can also be determined by business rules. In accordance with an embodiment, at business process modeling time the workflow process designer creates human tasks in the process and specifies the business rules that determine the pattern, participant and routing information. These are integrated into the workflow task in the process. The integration of rules into human workflow can be performed using service component architecture, so that other rules engines can be plugged-in as required.

Claims

1. A system for dynamic workflow task assignment using business rules, comprising:

a repository;

a graphical user interface (GUI) for defining one or more business process execution language (BPEL) process definitions each including a set of tasks and each usable to define a workflow process,

wherein the one or more BPEL process definitions are persisted in the repository;

a computer including a workflow process executing thereon, wherein the workflow process generates tasks for assignment to users according to patterns of a workflow defined by a BPEL process definition,

wherein the tasks are accessible to the assigned users via a client connected with the system;

a plurality of tasks generated by the workflow process,

wherein each task from the plurality of tasks is represented by an object stored in the repository,

wherein each task from the plurality of tasks includes one or more stages and a payload that includes real-time data necessary to complete the task, and

wherein a payload for a task from the plurality of tasks is modifiable during the workflow process, including in response to execution of any of the plurality of tasks, and the payload as modified travels with the task as the task is assigned to users responsible for completing the task;

a business rules service component architecture (SCA) interface that allows for a plurality of business rules engines to each be selectively made accessible to the workflow process via a plugin,

wherein each of the plurality of business rules engines specifies rules that control how tasks should be processed or routed,

wherein the plurality of business rules engines specify rules specific to roles within an organization and each of the plurality of business rules engines is associated with a different role within an organization, and

wherein each of the plurality of tasks is assigned to one or more roles; and

wherein during execution of the workflow process, the system accesses one or more business rules engines of the plurality of business rules engines plugged into the business rules SCA interface according to one or more roles assigned to a particular task that is being executed to determine processing or routing of the particular task to users, including using rules specified by the one or more business rules engines to

determine the patterns of the workflow,

dynamically modify the workflow process based on a payload for the particular task at the time the particular task is executed,

access a list of users constructed by a list builder for each of one or more stages of the particular task based on the payload for the particular task at the time the particular task is executed,

assign each of the one or more stages of the particular task to an appropriate user from the list of users according to the dynamically modified workflow process, and

provide access to each of the one or more stages to an assigned user via a client connected with the system.

2. The system of claim 1, wherein one or more of the plurality of business rules engines are business process engines.

3. The system of claim 2, wherein the rules provided by the plurality of business rules engines are business rules and are used to specify the patterns in a workflow.

4. The system of claim 3, wherein the plurality of business rules engines, and the patterns they specify, control the workflow process to the extent of determining which users should be assigned to which tasks, and the routing thereof.

13. The system of claim 1, wherein the contents of the payload of a particular task are initially provided when the particular task is first created, and can be one of statically defined by workflow system data, or dynamically modified during the workflow process, and wherein the payload as retrieved or modified then travels with the particular task as it is assigned to users responsible for completing the particular task.

5. A method for dynamic workflow task assignment using business rules, comprising:

providing a graphical user interface (GUI) for defining one or more business process execution language (BPEL) process definitions each including a set of tasks and each usable to define a workflow process,

wherein the one or more BPEL process definitions are persisted in a repository;

executing, by a computer including a microprocessor, a workflow process, wherein the workflow process generates tasks for assignment to users according to patterns of a workflow defined by a BPEL process definition, wherein the tasks are accessible to the assigned users via a client connected with the system;

parsing a plurality of tasks generated by the workflow process,

wherein each task from the plurality of tasks is represented by an object stored in the repository,

wherein each task from the plurality of tasks includes one or more stages and a payload that includes real-time data necessary to complete the task, and

wherein a payload for a task from the plurality of tasks is modifiable during the workflow process, including in response to execution of any of the plurality of tasks, and the payload as modified travels with the task as the task is assigned to users responsible for completing the task;

providing a business rules service component architecture (SCA) interface that allows for a plurality of business rules engines to each be made accessible to the workflow process via a plugin,

wherein each of the plurality of business rules engines specifies rules that control how tasks should be processed or routed,

wherein the plurality of business rules engines specify rules specific to roles within an organization and each of the plurality of business rules engines is associated with a different role, and

wherein each of the plurality of tasks is assigned to one or more roles; and

during execution of the workflow process, accessing one or more business rules engines of the plurality of business rules engines plugged into the business rules SCA interface according to one or more roles assigned to a particular task that is being executed to determine processing or routing of the particular task to users, including using rules specified by the one or more business rules engines to

determine the patterns of the workflow,

dynamically modify the workflow process based on a payload for the particular task at the time the particular task is executed,

access a list of users constructed by a list builder for each of one or more stages of the particular task based on the payload for the particular task at the time the particular task is executed,

assign each of the one or more stages of the particular task to an appropriate user from the list of users according to the dynamically modified workflow process, and

provide access to each of the one or more stages to an assigned user via a client connected with the system.

6. The method of claim 5, wherein one or more of the plurality of business rules engines are business process engines.

7. The method of claim 6, wherein the rules provided by the plurality of business rules engines are business rules and are used to specify the patterns in a workflow.

8. The method of claim 7, wherein the plurality of business rules engines, and the patterns they specify, control the workflow process to the extent of determining which users should be assigned to which tasks, and the routing thereof.

14. The method of claim 5, wherein the contents of the payload of a particular task are initially provided when the particular task is first created, and can be one of statically defined by workflow system data, or dynamically modified during the workflow process, and wherein the payload as retrieved or modified then travels with the particular task as it is assigned to users responsible for completing the particular task.

9. A non-transitory computer readable storage medium, including instructions stored thereon, which when read and executed by a computer cause the computer to perform the steps comprising:

providing a graphical user interface (GUI) for defining one or more business process execution language (BPEL) process definitions each including a set of tasks and each usable to define a workflow process,

wherein the one or more BPEL process definitions are persisted in a repository;

executing a workflow process, wherein the workflow process generates tasks for assignment to users according to patterns of a workflow defined by a BPEL process definition, wherein the tasks are accessible to the assigned users via a client connected with the system;

parsing a plurality of tasks generated by the workflow process,

wherein each task from the plurality of tasks is represented by an object stored in the repository,

wherein each task from the plurality of tasks includes one or more stages and a payload that includes real-time data necessary to complete the task, and

wherein a payload for a task from the plurality of tasks is modifiable during the workflow process, including in response to execution of any of the plurality of tasks, and the payload as modified travels with the task as the task is assigned to users responsible for completing the task;

providing a business rules service component architecture (SCA) interface that allows a plurality of business rules engines to each be made accessible to the workflow process via a plugin,

wherein each of the plurality of business rules engines specifies rules that control how tasks should be processed or routed,

wherein the plurality of business rules engines specify rules specific to roles within an organization and each of the plurality of business rules engines is associated with a different role, and

wherein each of the plurality of tasks is assigned to one or more roles; and

during execution of the workflow process, accessing one or more business rules engines of the plurality of business rules engines plugged into the business rules SCA interface according to one or more roles assigned to a particular task that is being executed to determine processing or routing of the particular task to users, including using rules specified by the one or more business rules engines to

determine the patterns of the workflow,

dynamically modify the workflow process based on a payload for the particular task at the time the particular task is executed,

access a list of users constructed by a list builder for each of one or more stages of the particular task based on the payload for the particular task at the time the particular task is executed,

assign each of the one or more stages of the particular task to an appropriate user from the list of users according to the dynamically modified workflow process, and

provide access to each of the one or more stages to an assigned user via a client connected with the system.

10. The non-transitory computer readable storage medium of claim 9, wherein one or more of the plurality of business rules engines are business process engines.

11. The non-transitory computer readable storage medium of claim 10, wherein the rules provided by the plurality of business rules engines are business rules and are used to specify the patterns in a workflow.

12. The non-transitory computer readable storage medium of claim 11, wherein the plurality of business rules engines, and the patterns they specify, control the workflow process to the extent of determining which users should be assigned to which tasks, and the routing thereof.

15. The non-transitory computer readable storage medium of claim 9, wherein the contents of the payload of a particular task are initially provided when the particular task is first created, and can be one of statically defined by workflow system data, or dynamically modified during the workflow process, and wherein the payload as retrieved or modified then travels with the particular task as it is assigned to users responsible for completing the particular task.