This application is related to the following copending and commonly assigned patent filed on the same date herewith, which are incorporated herein by reference in their entirety:
1. Field of the Invention
The present invention relates to a method, system, and program for generating a workflow.
2. Description of the Related Art
A workflow program allows businesses and other organizations to define their business operations as a computer model known as a workflow. A workflow defines a series of processes to be performed by users at a client computer. The user activities at the client computers may involve updating an electronic form, reviewing information, etc. After one user in the workflow performs a specified action, the work item or other information is then routed to one or more further nodes where further action may be taken. For instance, an on-line purchase of a product may involve numerous steps, such as receiving the customer order, routing the customer order to the credit department to process the bill and then routing the order to the shipment department to prepare the shipment. Once the shipment is prepared, the product may be shipped and information on the purchase is then transferred to the customer service department to take any further action. Each of these processes may be defined as nodes in a workflow. A workflow program would then route the customer order to the business agents designated to handle the job. For instance, the initial order would be received by the order department and then routed to a person in shipping and billing. Once the bill and package are prepared, a further invoice may be forwarded to shipping. After shipping sends the package, the shipping agent may then enter information into the invoice and forward the electronic invoice to customer service for any follow up action.
A workflow is designed using workflow software, such as the International Business Machines (IBM) MQSERIES** workflow software product. A process modeler is a person that analyzes the business operations, determines how the information related to the operations is routed electronically to client computers, and then defines a workflow model of the operations. The workflow model may be coded in the FlowMark Definition Language (FDL). The workflow model is then imported into a Runtime program that verifies and translates the workflow model into a process template. An instance of the process template can then be invoked to automates the sequence of events defined by the model.
There is a continued need in the art to provide improved techniques for building and utilizing workflow models.
Provided is a method, system, and program for generating a workflow. A plurality of graphical user interfaces (GUI) panels are displayed through which a user may define nodes of a workflow and associate at least one action and user with each node. During workflow execution of each node, the associated user performs the associated action. Further, multiple nodes define actions that process at least one object that is routed through multiple nodes of the workflow. A workflow model is generated from information entered into the GUI panels including the nodes and workflow defined by the user through the GUI panels that process the at least one object. The workflow model is transformed into a workflow definition language (WDL) file. The WDL file is then transferred to a workflow server, wherein the workflow server interacts with a database to implement the workflow model defined in the WDL file in the database.
The workflow definition language (WDL) may comprise the FlowMark Definition Language (FDL).
In further implementations, the displayed GUI panel illustrates a layout of the workflow, including graphical representations of nodes and paths between the nodes. The user may manipulate instances of the graphical representations of the nodes and paths in the workflow within the GUI panel to design a layout of the nodes of the workflow.
In still further implementations, a request by one user associated with one node is received to access the node when no other user is accessing the node. The user requesting access to the node is granted access to the node to perform the action associated with the node. The node is locked to prevent other users associated with the node from accessing the node. The lock on the node is released when the user granted access to the node completes the action associated with the node, wherein other users can access the node after the lock is released.
Still further, the at least one object routed through the nodes for processing comprises at least one electronic document that is modified by users and routed through the nodes of the workflow.
Moreover, the object processed at the nodes is included in a work packet, wherein the work packet is capable of including multiple objects. Modifications to at least one object in the work packet is received by one user performing actions associated with one node, wherein multiple users perform actions at different nodes to process objects in the work packet routed through the nodes.
The described implementations provide a GUI builder to allow a user to generate a workflow that is automatically translated into a workflow definition language (WDL) for use by a workflow server. In this way, the workflow model generated by the GUI builder may be transformed and used with different vendor workflow engines that are compatible with the workflow definition language (WDL). Further, with the described implementations, the nodes may be designed to be document centric, in that the processing occurs with respect to work items assigned to each node.
Referring now to the drawings in which like reference numbers represent corresponding parts throughout:
In the following description, reference is made to the accompanying drawings which form a part hereof and which illustrate several embodiments of the present invention. It is understood that other embodiments may be utilized and structural and operational changes may be made without departing from the scope of the present invention.
The workflow server 6 coordinates and manages the execution of processes for a defined process template 8. The workflow server 6 executes any programs associated with a process defined for the workflow, interprets the process definitions, creates process instances and manages their execution, manages processes and states, logs events, communicates with users as part of the workflow, etc. The workflow server 6 may include a database client program (not shown) to access and update records related to the workflow being processed maintained in the runtime database 4. The workflow server 6 processing may be distributed across multiple computers to achieve work load balancing.
The workflow clients 12a, b . . . n represent the client computers that execute workflow application program interfaces (APIs) to perform workflow related actions and activities and return messages to the workflow server 6. The workflow clients 12a, b . . . n thus comprise instances of the workflow code on the client computers that allow users to interface with the executing workflow and the workflow server 6. The workflow server 6 would execute activity programs as part of executing the workflow and transmit messages and data to the workflow client 12 to request user action to proceed with the workflow. The actions associated with the nodes and executed by the workflow server 6 may comprise Java servlets. The workflow client 12 may comprise a Web browser capable of executing Java scripts transferred from the Java servlet executing on the workflow server 6. Further, details on implementations and interactions of the workflow server 6 and client 12 are described in the IBM publication “IBM MQSeries Workflow: Concepts and Architecture, Version 3.3”, IBM document no. GH12-6285-03 (March, 2001), which publication is incorporated herein by reference in its entirety.
A workflow builder 20 comprises a system including a buildtime program 22 that implements a plurality of graphical user interface (GUI) panels in which a user may define the components of a workflow model 24. A workflow translator 26 converts the workflow model 24, with the defined workflow components, into a workflow definition language (WDL) file 10 that implements the workflow model 24. The workflow definition language (WDL) may comprise the FlowMark Definition Language (FDL), Workflow Process Definition Language (WPDL) or any other workflow definition language known in the art that is used to define workflows. The workflow translator 24 would transfer the WDL file 10 to the workflow server 6 to transform into a process template 8 in the runtime database 4 in a manner known in the art.
The workflow engine 2, and each of the program components therein, such as the runtime database 4 and workflow server 6, may be implemented in one or more computing machines. The workflow clients 12 which provide the workflow interface to users may be implemented on one or more client machines. The workflow builder 20, including the buildtime program 22 and workflow translator 26 programs, may be implemented on one or more computing machines. Any portion of the workflow engine 2, workflow builder 20, and/or workflow client 12, and program components therein, may be implemented on the same computing machines or separate machines. The computing machines used to implement the workflow engine 2, workflow clients 12, and workflow builder 20 may comprise any computing device known in the art, such as a server, workstation, mainframe, personal computer, laptop computer, hand held computer, telephony device, etc.
As discussed, the buildtime program 22 generates a series of graphical user interface (GUI) panels through which the user may define a workflow. Before utilizing the buildtime program 22, the process modeler would plan the workflow and analyze the work the business performs, how it is performed, and by whom. The process modeler may then develop a workflow to generate a final product, which may comprise the result of the effort of a single business unit or the cumulative efforts of multiple users and units within an organization. To produce the final product, a workflow packet comprised of one or more documents would transfer through various user work stations in the company defined as nodes in the workflow to require the user associated with such node to handle and process and forward to another user to handle. A document is comprised of a multimedia item that has digital content.
For instance, an insurance company may have to process numerous documents related to an insurance claim, such as photographs, appraisals, expert reports, etc. Employees may spend a substantial amount of time sorting through documents and associating the documents with particular claims. In the workflow model, all the documents related to a single claim would be part of a work packet that may move through various user stations to review and process. The workflow would comprise the flow of work and actions that are performed on the documents or workflow packet by multiple users in the system.
The workflow defines the sequence and boundaries of how the work is performed with respect to the documents in the workflow packet, and any restrictions on the order in which documents in the workflow packet must be processed. For instance, before the claim can proceed to a further step, a claims adjuster might be required to ensure that certain documents are included in the workflow packet for the claim before the workflow packet can proceed to further nodes in the workflow, e.g., determining the amount of compensation.
In workflow terminology, a worklist is a queue of work items. Each work item comprises a unit of work for a node in the workflow that is performed by the users associated with that node. Each work item may be associated with one work packet, which comprises documents or objects that are processed during the work defined for that work item. When a user at one node accesses the work item to perform the work defined therein, that workitem is locked, thereby preventing others at that node from accessing the work item.
A worklist, which is a queue of work for the users of the organization to perform with respect to the workflow packet. The work items within the worklist can be handled by any of the employees/users assigned to the worklist. An action list defines the actions that a user can perform on the work packet objects associated with the work item, such as selections or data that may be entered in the work packet. For example, an adjuster in the claim process workflow can select an option to continue consideration of the claim if it appears valid or select an option to reject the claim. The workflow further consists of the paths defined as the connections between nodes which indicate the order of execution of nodes in the workflow.
As mentioned, the start 54 and end 56 icons may be automatically added to the workflow 52 when the user starts a blank workflow model 24. The user may move the start 54 and end 56 icons to any location on the drawing surface. The user may select the control icons 66 and 68 to add work and user exit nodes, respectively, to the workflow. Control icon 70 is used to define a path between two nodes defining the sequence in which the nodes are processed, and the order in which the work items are processed. The path lines, which are shown as the arrows between the start 54, end 56, work and user exit icons 58, 60, 62, and 64 illustrate the operation flow from one node to another.
Once the process modeler has defined the general layout of a workflow using the control icons 66, 68, 70, and 72, as shown in the workflow 52 in
After defining the properties for the new workflow and placing icons in the drawing area and path arrows to define the workflow, the user would then use the GUI panels shown in
Using all the above described panels shown in
In certain implementations, the workflow model 24 defined using the buildtime program 22 is document centric in that the actions performed at the node concern the processing of work packages that may comprise any content or object that is processed and routed through the workflow.
If (at block 314) notification is enabled for the current node and the deadline has passed (at block 316) without receiving a response from the user, then the workflow server 6 notifies the user specified with the enable notification that the deadline has passed. Upon receiving (at block 318) a response from the user, which may comprise entering information, modifying a work item, adding a work item to the work package, selecting an option, etc., the workflow server 6 unlocks (at block 320) the work item(s) previously locked for the user. If (at block 322) the current node is the stop node, then control ends; otherwise, if there are further nodes to process in the workflow, then the workflow server 6 determines (at block 324) from the path from the current node the next node in the workflow and accesses (at block 326) the next node. Control then proceeds back to block 326 to process the next node.
The workflow logic of
With the described implementations, the workflow builder 20 generates a WDL file 10 that may be compatible with workflow engines from different vendors because different vendors may design their workflow engines to be compatible with the WDL format of the WDL file 10. This allows the workflow model defined in the WDL file 10 to be transportable across different vendor workflow engine platforms.
Additional Implementation Details
The preferred embodiments may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software or code. The term “article of manufacture” as used herein refers to code or logic implemented in a computer readable medium (e.g., magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, firmware, programmable logic, etc.). Code in the computer readable medium is accessed and executed by a processor. The code in which preferred embodiments are implemented may further be accessible through a transmission media or from a file server over a network. In such cases, the article of manufacture in which the code is implemented may comprise a transmission media, such as a network transmission line, wireless transmission media, signals propagating through space, radio waves, infrared signals, etc. Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope of the present invention, and that the article of manufacture may comprise any information bearing medium known in the art.
The workflow client and server may be implemented within any vendor workflow program known in the art.
In the described implementations, the actions were implemented as Java methods. Alternatively, the actions may be implemented in any programming language known in the art.
In the described implementations, particular icons were used to represent different information in the workflow, such as work nodes, exit nodes, etc. However, any icon design may be used to represent the workflow components. Further, additional graphical representations may be provided for different types of work nodes, e.g., collection work nodes, assign value node, decision point node, etc.
The foregoing description of the preferred embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
Number | Name | Date | Kind |
---|---|---|---|
5301320 | McAtee et al. | Apr 1994 | A |
5535322 | Hecht | Jul 1996 | A |
5572673 | Shurts | Nov 1996 | A |
5596744 | Dao et al. | Jan 1997 | A |
5596750 | Li et al. | Jan 1997 | A |
5634053 | Noble et al. | May 1997 | A |
5634127 | Cloud et al. | May 1997 | A |
5644768 | Periwal et al. | Jul 1997 | A |
5721912 | Stepczyk et al. | Feb 1998 | A |
5721913 | Ackroff et al. | Feb 1998 | A |
5734837 | Flores et al. | Mar 1998 | A |
5745683 | Lee et al. | Apr 1998 | A |
5745687 | Randell | Apr 1998 | A |
5752027 | Familiar | May 1998 | A |
5774661 | Chatterjee et al. | Jun 1998 | A |
5790789 | Suarez | Aug 1998 | A |
5794250 | Cariño, Jr. et al. | Aug 1998 | A |
5826086 | Arima et al. | Oct 1998 | A |
5826239 | Du et al. | Oct 1998 | A |
5860066 | Rouse | Jan 1999 | A |
5864843 | Cariño, Jr. et al. | Jan 1999 | A |
5873083 | Jones et al. | Feb 1999 | A |
5892905 | Brandt et al. | Apr 1999 | A |
5913214 | Madnick et al. | Jun 1999 | A |
5926636 | Lam et al. | Jul 1999 | A |
5930512 | Boden et al. | Jul 1999 | A |
5937388 | Davis et al. | Aug 1999 | A |
5951649 | Dobbins et al. | Sep 1999 | A |
5960420 | Leymann et al. | Sep 1999 | A |
5987422 | Buzsaki | Nov 1999 | A |
5991733 | Aleia et al. | Nov 1999 | A |
6006193 | Gibson et al. | Dec 1999 | A |
6012067 | Sarkar | Jan 2000 | A |
6044378 | Gladney | Mar 2000 | A |
6061667 | Danford-Klein et al. | May 2000 | A |
6065009 | Leymann et al. | May 2000 | A |
6073109 | Flores et al. | Jun 2000 | A |
6073111 | Leymann et al. | Jun 2000 | A |
6115646 | Fiszman et al. | Sep 2000 | A |
6151583 | Ohmura et al. | Nov 2000 | A |
6170002 | Ouchi | Jan 2001 | B1 |
6226641 | Hickson et al. | May 2001 | B1 |
6278977 | Agrawal et al. | Aug 2001 | B1 |
6308163 | Du et al. | Oct 2001 | B1 |
6338074 | Poindexter et al. | Jan 2002 | B1 |
6349238 | Gabbita et al. | Feb 2002 | B1 |
6430538 | Bacon et al. | Aug 2002 | B1 |
6453320 | Kukura et al. | Sep 2002 | B1 |
6487607 | Wollrath et al. | Nov 2002 | B1 |
6578006 | Saito et al. | Jun 2003 | B1 |
6606740 | Lynn et al. | Aug 2003 | B1 |
6665674 | Buchanan et al. | Dec 2003 | B1 |
6665814 | Hobson et al. | Dec 2003 | B1 |
6681243 | Putzolu et al. | Jan 2004 | B1 |
6691299 | Hart et al. | Feb 2004 | B1 |
6721713 | Guheen et al. | Apr 2004 | B1 |
6769113 | Bloom et al. | Jul 2004 | B1 |
6769124 | Schoening et al. | Jul 2004 | B1 |
6816902 | Bandat et al. | Nov 2004 | B1 |
6853974 | Akifuji et al. | Feb 2005 | B1 |
6877153 | Konnersman | Apr 2005 | B1 |
6920456 | Lee et al. | Jul 2005 | B1 |
20020032783 | Tuatini | Mar 2002 | A1 |
20020038357 | Haverstock et al. | Mar 2002 | A1 |
20020040312 | Dhar et al. | Apr 2002 | A1 |
20020059411 | Barnhouse et al. | May 2002 | A1 |
20020103811 | Frankhuser et al. | Aug 2002 | A1 |
20020120685 | Srivastave et al. | Aug 2002 | A1 |
20020143949 | Rajarajan et al. | Oct 2002 | A1 |
20030023472 | Lee et al. | Jan 2003 | A1 |
20030023662 | Yaung | Jan 2003 | A1 |
20030023728 | Yaung | Jan 2003 | A1 |
20030023773 | Lee et al. | Jan 2003 | A1 |
20030033415 | Graylin et al. | Feb 2003 | A1 |
20030131075 | Bear et al. | Jul 2003 | A1 |
20040015821 | Lu et al. | Jan 2004 | A1 |
Number | Date | Country |
---|---|---|
982675 | Aug 1999 | EP |
10-081425 | Mar 1998 | JP |
10-326314 | Dec 1998 | JP |
11-003298 | Jan 1999 | JP |
11-175644 | Jul 1999 | JP |
11-249983 | Sep 1999 | JP |
9963463 | Sep 1999 | WO |
0014618 | Mar 2000 | WO |
Number | Date | Country | |
---|---|---|---|
20030004770 A1 | Jan 2003 | US |