US20080300928A1 - Publishing and deploying business processes - Google Patents

Abstract

Publishing a business process includes accessing a business process that includes activities, where each activity is associated with an abstract role. Organizational roles are accessed. Each abstract role is matched with an organizational role. The business process is published to a data repository by creating a plurality of object classes representing the business process having the matched organizational roles.

Description

RELATED APPLICATIONS
• This application claims benefit under 35 U.S.C. § 119(e) of U.S. Provisional Application Ser. No. 60/280,622, filed Mar. 30, 2001, entitled “METHOD AND SYSTEM FOR AUTOMATING BUSINESS PROCESSES.”
• This application is related to U.S. patent application Ser. No. 09/___,___, entitled “DESIGNING BUSINESS PROCESSES USING PARAMETRIC ROLES,” Attorney's Docket 067833.0130, filed concurrently with the present application.
• This application is related to U.S. patent application Ser. No. 09/___,___, entitled “DESIGNING BUSINESS PROCESSES USING DISTRIBUTED PROCESS FLOWS,” Attorney's Docket 067833.0131, filed concurrently with the present application.
• This application is related to U.S. patent application Ser. No. 09/___,___, entitled “EXECUTING BUSINESS PROCESSES USING PERSISTENT VARIABLES,” Attorney's Docket 067833.0135, filed concurrently with the present application.
TECHNICAL FIELD OF THE INVENTION
• This invention relates generally to the field of business process automation and more specifically to publishing and deploying business processes.
BACKGROUND OF THE INVENTION
• Organizations typically automate their business processes to manage their operations. A business process includes a series of activities that are undertaken to perform the operations of an organization. For example, a business process may describe activities for processing a sales order, such as the steps of receiving a sales order, checking the payment history, checking the inventory, and so on. An organization may automate a business process by having a computer perform some activities such as receiving a sales order. A business process may also be automated by having a computer remind human participants of activities that need to be performed. For example, a computer may send an email message notifying an account manager to check the payment history of a client.
• Automating business processes, however, has posed challenges. Designing automated business processes involves the use of software programs, which business process designers may find difficult to use. Moreover, testing automated business processes requires performing trial runs of a business process, which may be difficult to do without disrupting the actual users of the business process. Consequently, automating business processes has posed challenges.
SUMMARY OF THE INVENTION
• In accordance with the present invention, disadvantages and problems associated with previous techniques for business process design may be reduced or eliminated.
• According to one embodiment of the present invention, publishing a business process includes accessing a business process that includes activities, where each activity is associated with an abstract role. Organizational roles are accessed. Each abstract role is matched with an organizational role. The business process is published to a data repository by creating a plurality of object classes representing the business process having the matched organizational roles.
• Certain embodiments of the invention may provide numerous technical advantages. A technical advantage of one embodiment is that business processes may include activities with compensation tasks. Compensation tasks are executed when a task of an activity fails to execute, thus allowing for the performance of the activity to continue uninterrupted to completion. Compensation tasks may be used for automated business processes to maintain business process consistency.
• Another technical advantage of one embodiment is that an activity may be associated with an abstract role in order to specify users representing people responsible for performing the activity. The association may provide for abstract business process modeling, which may allow for the creation of business process templates creation that may be used for different organizations.
• Another technical advantage of one embodiment is that the processes of publishing and deploying business processes are separated. By separating the publication and deployment processes, a business process may be published and tested, without deploying the business process to users. Another technical advantage of one embodiment is that persistent variables are used. Persistent variables allow a value related to an instance of a business process to be efficiently carried from one activity of the business process to another activity of the same business process or of another business process.
• Certain embodiments of the invention may include none, some, or all of the above technical advantages. One or more other technical advantages may be readily apparent to one skilled in the art from the figures, descriptions, and claims included herein.
BRIEF DESCRIPTION OF THE DRAWINGS
• For a more complete understanding of the present invention and for further features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:
• FIG. 1A is a block diagram of one embodiment of a system for automating a business process in accordance with the present invention;
• FIG. 1B is a block diagram of one embodiment of a data repository that may be used with the system ofFIG. 1A;
• FIG. 2 illustrates one embodiment of designer screen that may be used for automating business process modeling;
• FIG. 3 illustrates one embodiment of task table that may be used for recording tasks and compensation tasks for a business process activity;
• FIG. 4 illustrates one embodiment of an activity properties screen that may be used to define tasks and compensation tasks;
• FIG. 5 is a flowchart illustrating one embodiment of a method for defining, implementing, and executing tasks and compensation tasks;
• FIG. 6 illustrates one embodiment of an organizational roles screen that may be used to configure organizational roles that can have values;
• FIG. 7 illustrates one embodiment of assign organizational roles screen that may be used to assign organizational roles to users;
• FIG. 8 illustrates one embodiment of a match roles screen that may be used to match abstract roles with organizational roles when an abstract business process model is published to an organization;
• FIG. 9 is a flowchart illustrating one embodiment of a method for defining and implementing organizational roles;
• FIG. 10 illustrates one embodiment of a publish screen that may be used to publish and deploy a business process;
• FIG. 11 is a flowchart illustrating one embodiment of a method for publishing a business process;
• FIG. 12 is a flowchart illustrating one embodiment a method for implementing an instance variable at runtime or execution time;
• FIG. 13 is a flowchart illustrating one embodiment a method for implementing an argument variable when communicating to business processes;
• FIGS. 14 through 18 illustrate distributed process flow; and
• FIG. 19 illustrates polymorphic sub-processes.
DETAILED DESCRIPTION OF THE DRAWINGS
• FIG. 1A is a block diagram of one embodiment of asystem100 for automating a business process. A business process includes a series of activities that are undertaken to perform the operations of an organization. For example, a business process may describe activities for processing a sales order, such as the steps of receiving a sales order, checking the payment history, checking the inventory, and so on.System100 allows an organization to automate business processes.
• Referring toFIG. 1A, auser group110 may accesssystem100 through acommunication network114. An organization may usesystem100 to implement business processes to solve problems.User group110 comprises a data set of user identifiers, which may represent, for example, people who may accesssystem100 using computing modules such as personal computers. For example,user group110 may include adesigner122, which represents a person who usessystem100 to design a business process model.
• User group110 also includes users124, which represent people who may be responsible for performing activities of a business process. For example, a user124 may be responsible for receiving a sales order and verifying its completeness.System100 allowsdesigner122 to design a business process model. In turn,system100 notifies users124 of the activities that need to be performed.
• Users124 may be logically organized into user sets123, where users124 of a user set123 represent people who are responsible for the execution of specific activities. The logical grouping of users may be defined and stored insystem100. A user124 may be a member of any suitable number of user sets123. For example,user124cis a member of user sets123aand123b. User sets125 may be associated with, for example, organizational roles defined within an organization, such as a salesperson role.
• Communication network114 may include wired telecommunications, satellite, microwave, or other suitable wired or wireless networks, or a combination of the preceding.
• System100 includes aninterface module116,modules112, and adata repository118.Interface module116 may include awebsite126, aninterface128 deployed inwebsite126, and asecurity module129.Website126 allows for communication of information betweenuser group110 andsystem100.Interface128 may comprise a hypertext markup language (HTML) interface that receives instructions through a web server deployed inwebsite126 in order to perform operations included in instructions from users124.Security module129 may provide, for example, password security, resource access security, and/or system security.Security module129 may be used for authentication procedures and may be adapted to the security policy and infrastructure of an organization.
• System100 provides advantages in automating business processes.System100 generates business processes that include compensation tasks. A compensation task is executed when an associated task of a business process activity fails to execute, allowing the business process to achieve a steady and consistent state before its execution is retried. The business process instance may proceed to the next business process activity. Additionally,system100 allows for specification of people who are responsible for performing the activities of a business process through user sets123 defined insystem100, thus allowing an organization to readily automate the business process.
• Moreover,system100 separates the processes of publishing and deploying business processes. By separating the publication and deployment processes, a business process may be published and tested, without being deployed to users124 of the production environment. Furthermore,system100 provides persistent variables, which allow a value to be transferred from one activity to another activity of the same business process or of a different business process using process arguments.
• Modules112 include acatalog manager130, aprocess designer132, anorganizational settings module134, anexecution console136, and execution engines140 coupled as shown inFIG. 1A. In general,catalog manager130 may be used to define and specify the components or programs that can be called from a business process.Process designer132 may be used to model business processes to be deployed in an organization.Organizational settings module134 may be used as a front-end module to define business process participants and how they are going to be organized.
• Execution console136 may be used to manage the execution engine in which business processes are deployed, and may be accessed by users124 ofuser group110. Execution engines140 may be used to deploy business processes, execute tasks requested by users124, and perform automated business process activities.Modules112 may store and retrieve data using adata repository118 that includes anorganizational data repository150 and atransactional database170.
• According to one embodiment,catalog manager130 defines, describes, and organizes components. A component may comprise a modular software routine that has been compiled, and may be used with other components or programs.Catalog manager130 stores components indata repository118 and supplies components to processdesigner132 and execution engines140.
• Process designer132 is used to design business processes, which are stored indata repository118 once the business processes are published. While the business process is being designed usingProcess Designer132, the business process model definition may be stored in a local computer. Business processes are described in more detail in connection withFIG. 2.Process designer132 may also be used to publish business processes todata repository118 as well as to deploy business processes to execution engine140.
• According to one embodiment, business processes are designed on a computer by manipulating graphical icons on a computer screen. An example of a computer screen that may be used to design a business process is described in connection withFIG. 2.
• FIG. 2 illustrates one embodiment of adesigner screen200 for automating abusiness process210 on a computer.Business process210 includes a sequence ofactivities212 coupled by transitions214. For example,business process210 may include a sequence ofactivities212 for processing a sales order. Eachactivity212 comprises a series of tasks that are executed to completeactivity212. For example, anactivity212 that notifies a client of an incomplete sales order may include the task of “sending an email message to the client.” Tasks may execute components catalogued usingcatalog manager130 and made available through publishing and deployment.
• To designbusiness process210,activities212 are placed in adesigner window202.Activities212 may have a specific semantic, which may be designated by a particular color or shape. Custom colors and shapes may be used in response to user preference. For example,activity212amay be an activity that is used to begin a business process, and may be designated by a triangular shape pointing in the right-hand direction.Activity212fmay be an activity that is used to end a business process, and may be designated by a triangular shape pointing in the left-hand direction.
• Transitions214 are used to indicate a next activity that is to be initiated after executing a previous activity. For example, transition214aindicates thatactivity212bis to be initiated after the execution ofactivity212a. Transitions214 may indicate multiple next activities that are to be initiated after the execution of a previous activity. For example, transitions214band214cindicate thatactivities212cand212d, respectively, are to be initiated after the execution ofactivity212b.
• Depending upon howbusiness process210 is defined, either one or bothactivities212cand212dmay be initiated afteractivity212b. For example,business process210 may be defined such that depending upon a decision made atactivity212b, eitheractivity212coractivity212dis initiated after the execution ofactivity212b. Additionally, transitions214 may direct multiple activities to a single next activity. For example, transitions214dand214edirect activities212cand212d, respectively, toactivity212e.
• Business process210 also includes abstract roles216 that are used at design time to represent in the abstract user sets123 that represent people of an organization who are responsible for performing anactivity212. Abstract role216 may be matched to an organizational role. An abstract role represents in the abstract a set of users responsible for performing the activity, and the organizational role may take on values that correspond to actual users124 of an organization. For example, an abstract role represents a salesperson in the abstract, and the organizational role describes actual salespeople of an organization. At design time, abstract roles are used instead of organizational roles, such that a single business process may be used for multiple organizations, incorporating the concept of template models.
• An organizational role may be parametric, that is, the organizational role may be assigned a value that corresponds to user set123, and may take on multiple values that correspond to different user sets123. Users124 of user set123 represent people responsible for performingactivity212. For example, users124 of one user set123 may represent salespeople from one state, and users of another user set123 may represent salespeople from another state. An organizational role may be used to create groups of users that can be instantiated with, for example, salespeople from different states. An advantage of defining parametric roles is that the assignment of a user set123 may be determined dynamically based on business process rules.
• Abstract roles216 are specified foractivities212 by placingactivities212 in the appropriate abstract role column. For example,abstract role216ais specified foractivity212a, andabstract role216bis specified foractivities212band212e. To summarize,business process210 may includeactivities212 coupled by transitions214 and associated with abstract roles that may be associated with real organizational roles stored indata repository118.
• Referring back toFIG. 1A,organizational settings module134 defines the settings for an organization. Organizational settings may describe user sets123, organizational roles and associated values if the organizational roles are parametric, and organizational units of the organization.
• Execution engines140 manage the execution of instances of business processes210. An example of an instance of a business process may be processing a specific sales order using a business process for processing sales orders. Execution engine140 is used to execute an instance ofbusiness process210 that has been deployed on it. Execution engine140 retrieves and collectsbusiness process210 definitions fromorganizational data repository150. Execution engine140 manages the execution of a particular task of a specific business process instance requested by a user124 if the activity is interactive. Execution engine140 automatically executes the task if the activity is an automated one.
• The state of the instance is maintained intransactional database170 if the task is completed successfully. Each execution engine140 may be associated with its owntransactional database170 that may comprise, for example, a relational database management system (RDBMS). “Each” as used in this document means either each member of a set or each member of a subset of a set.
• Execution console136 defines and manages execution engines140. For example,execution console136 defines port settings for execution engines140 and database settings fortransactional databases170 associated with execution engines140.
• FIG. 1B is a block diagram of one embodiment ofdata repository118 ofsystem100 ofFIG. 1A. Data repository includesorganizational data repository150 andtransactional database170.Organizational data repository150 includes information that is typically maintained through multiple executions of instances of business processes, and may be received fromorganizational settings134 andexecution console136.Organizational data repository150 may comprise, for example, a lightweight directory access protocol (LDAP) database.
• Organizational data repository150 includesbusiness process definitions152 andorganizational data154.Business process definitions152 include activities, transitions between the activities, and abstract roles associated with the activities.Business process definitions152 may include a task table159 that records the tasks of an activity and their associated compensation tasks. A compensation task is executed when its associated task fails to execute. The compensation task undoes things done by the associated task to a particular business process activity, resulting in a consistent state in case a task fails. Task table159 is described in more detail in connection withFIG. 3.
• Organizational data154 includes information about the organization.Organizational roles160 include information about organizational roles and associated users124.Organizational roles160 are matched with abstract roles216 in order to specify users124 representing people who are responsible for performing the activities of business processesdefinitions152.Matchings164 record the association between abstract roles and corresponding organizational roles when publishing a particular businessprocess using system100.
• Transactional database170 includes persistent variables that record information that is typically maintained for an instance of a business process. For example, a value describing the requested quantity of goods for a specific sales order is typically maintained for the instance that processes the specific sales order. The value is generally not needed for instances that process other sales orders.
• Persistent variables includeinstance variables172 andargument variables174.Instance variables172 record values that may be passed from one activity of a business process to another activity of the same business process.Instance variables172 may maintain the state of the instance within the context of a business process. For example, an instance variable may maintain the activity where an instance is at a given moment in time during the lifetime of the instance in a business process.Argument variables174 record values that may be passed from one business process to another business process. Methods for implementing and using persistent variables are described in more detail in connection withFIGS. 12 and 13.
• System100 provides advantages in automating business processes210. Business processes210 may includeactivities212 with tasks associated with compensation tasks. Compensation tasks are executed when an associated task ofactivity212 fails to execute, thus allowing for a consistent state. Compensation tasks are described in more detail in connection withFIGS. 3,4, and5. Additionally,activities212 may also be associated with abstract roles that are used to specify users124 representing people who are responsible for performing theactivity212, thus allowing an organization to readily automate business processes210. Organizational roles are described in more detail in connection withFIGS. 7,8, and9.
• Moreover,system100 separates the processes of publishing and deploying business processes210.Business process210 is published by matching abstract roles with organizational roles to specify users124 representing people responsible for performing the activities of thebusiness process210. After publishing,business process210 may be tested in a testing environment. The testedbusiness process210 is then deployed to makebusiness process210 available to users124 of a production environment. By separating the publication and deployment processes,business process210 may be published and tested, without deployingbusiness process210 to users124 of the production environment, thus reducing risk of problems in the production environment. Publication and deployment ofbusiness processes210 are described in more detail in connection withFIGS. 10 and 11.
• Furthermore,system100 provides persistent variables, which allow a value related to an instance to be carried from one activity to another activity within the same business process or between different business processes. Persistent variables are described in more detail in connection withFIGS. 12 and 13.
Compensation Tasks
• FIG. 3 illustrates one embodiment of a task table300 that recordstasks310 andcompensation tasks312.Activity212 includes a sequence oftasks310 that are performed in order to completeactivity212.Activity212 may describe, for example, notifying a client of an incomplete sales order.Tasks310 may be written in any suitable computer language and may invoke components implemented in a different computer programming language such as C, C++, Fortran, Cobol, or Basic.
• Atask310 may be associated with acompensation task312 that is specified to be executed intask310.Compensation task312 is only executed if its associated task fails. For example,Task1, which may represent “send email message to the client and to the financial department” is associated withcompensation Task3, which may represent “send a disregarding email message to the client if the email message could not be sent to the financial department”.Task3 is performed ifTask1 fails. Atask310 is not required to have acompensation task312. For example,Task2, which may be “send a fax to the client,” has no associatedcompensation task312. Recordingtasks310 and associatedcompensation tasks312 in task table300 provides for efficient and organized storage oftasks310 andcompensation tasks312.
• FIG. 4 illustrates one embodiment of an activity properties screen320 or task definition screen, that may be used to definetasks310 andcompensation tasks312 ofactivity212. Activity properties screen320 includes anactivity tasks section322 and a set ofavailable tasks section324.
• Activity tasks section322 includeswindows326 and330 andboxes328 and332 that may be used to definetasks310 andcompensation tasks312 ofactivity212. To define atask310, the name oftask310 may be inserted intask name window326, and a requiredbox328 may be selected in order to indicate thattask310 is mandatory to complete an instance ofactivity212. A mandatory task may comprise a task that must be completed in order to route an instance from one activity to another activity. In one embodiment, mandatory tasks must be completed in order to route an instance from one activity to a next activity to continue execution ofactivity212. In the illustrated example,Task1, “send an email message to the client and to the financial department” must be completed in order to continue execution ofactivity212.
• Compensation task312 may be defined by inserting the name ofcompensation task312 into compensationtask name window330, and a repeatable332 box may be selected in order to indicate thattask310 may be repeated a number of times. An addbutton334a, anedit button334b, and a remove button334cmay be used to add, edit, or removetasks310 fromactivity212. When a task is added, the new task appears intask name window326.
• Tasks310 andcompensation tasks312 foractivity212 may be selected from set oftasks section324. Set oftasks section324 includes aname window334 and adescription window336 that lists the names and descriptions, respectively, of available tasks that may be selected foractivity212. Activity properties screen320 allowsdesigner122 usingProcess Designer132 to readily specifytasks310 and associatedcompensation tasks312 ofactivity212, thus providing for efficient design of business processes210.
• FIG. 5 is a flowchart illustrating one embodiment of a method for defining and implementingtasks310 andcompensation tasks312 ofactivity212. In the illustrated example,Task1, which is “send an email message to the client and to the financial department” is associated withcompensation Task3, which is “send a disregarding email message to the client if the email message could not be sent to the financial department”.Task3 is performed ifTask1 fails, that is, if the email message cannot be sent to the financial department, then a disregarding email message is sent to the client.
• The method begins atstep350, whereprocess designer132 displays activity properties screen320, which may be used to generate tasks foractivity212. Activity properties screen320 may be displayed in response to a user request throughprocess designer132. A user may, for example, click onactivity212 ofdesigner screen200 ofFIG. 2 to request activity properties screen320.
• Activity properties screen320 may be used to specifytasks310 and associatedcompensation tasks312 ofactivity212. In the illustrated example,Task1 is “send an email message to the client and to the financial department” andTask3 is “send disregarding email message to the client if the email message could not be sent to the financial department”. Atstep352,tasks310 and associatedcompensation tasks312 are defined.Tasks310 and associatedcompensation tasks312 are stored in task table159 oforganizational data repository150 atstep354.
• Atstep356, an instance ofactivity212 is requested to initiate execution of atask310. Ifactivity212 is interactive, then the request is received from user124. Ifactivity212 is automatic, then execution engine140 initiates the execution oftask310. Atask310, for example,Task1, ofactivity212 is initiated by execution engine140 atstep358, that is, an email message is sent to the client and to the financial department.
• Execution engine140 may determine thatTask1 has failed atstep360. Execution engine140 may, for example, receive a notification that a program responsible for executingTask1, such as an email software program, cannot be located. Execution engine140 determinescompensation task312 associated withtask310 from task table159. In the illustrated example, task table159 ofFIG. 3 specifies thatTask3 is thecompensation task312 associated withTask1.
• Atstep364, execution engine140 initiatescompensation task312 to compensate for failedtask310. In the illustrated example,Task3 may be initiated by sending a disregarding email message to the client. After initiatingcompensation task312, the method terminates. Thus, the method provides for efficient specification ofcompensation tasks312 that are executed in the event an associatedtask310 fails to execute.
Parametric Roles
• FIG. 6 illustrates one embodiment of an organizational roles screen400 that may be used to define organizational roles and associated values for an organization. The organizational roles and associated values may be stored inorganizational data repository150. Organizational roles are matched with abstract roles ofactivity212 when a business process model is published into an organization. An organizational role may group users124 with the same responsibility such that users124 associated with an organizational role may perform the same operations or functions. For example, multiple users124 may have the ability to perform thesame activity212.
• An organizational role may be parametric, that is, may take on values that may be associated with categories such as subsets of the group with which the organizational role is associated. For example, an organizational role associated with a sales role may take on values associated with sales team categories within the sales role.
• Users124 may be associated with organizational units in order to designate other groupings of users124, for example, groupings by department or location. Organizational units may be associated with divisions or departments within an organization context. Information about the organizational units may be stored inorganizational data repository150. For example, an organizational unit may be associated with a particular department such as a sales department or a particular office location such as a Dallas office location.
• Organizational units may be used to group users124 that may access published and deployed business processes. For example, an organization develops a business process for processing a sales order that deals with operations in a sales department and no other department. The business process may be published and deployed to an organizational unit associated with the sales department such that only users124 of this particular organizational unit, and no other users124, may access the business process.
• A value may also be associated with a time period. For example, an organization may have one value for telephone operators who work during a daytime period, and another value for telephone operators who work during a nighttime period. An instance ofactivity212 that occurs during a particular time period may be assigned the value corresponding to the time period. For example, an instance that occurs during a daytime period may be assigned the value for telephone operators who work during a daytime period. An organizational role that has no specified value is assigned a default value.
• An advantage of the parametric roles may be that only one activity may be needed for multiple parametric values, thus avoiding the need to specify multiple activities for multiple values. Another advantage may be that a user set123 associated with an instance may be determined dynamically based on business process rules.
• Organizational roles screen400 includes arole name window410 and adescription window412, where a name and a description, respectively, of an organizational role may be inserted. In the illustrated example, an organizational role, Sales, is described as an organizational role for sales teams. Abrowse button414 may be selected in order to view available organizational roles.
• Value windows416 may be used to define values that the organizational role may have if the organizational role is parametric. In the illustrated example, Team A, Team B, and Team C, are the defined values that the Sales may have. Add and remove buttons418 may be used to add and remove, respectively, values. An assignorganizational role button420 may be used to display assign organizational roles screen that may be used to assign roles to users124, which is described in more detail in connection withFIG. 7.
• FIG. 7 illustrates one embodiment of an assign organizational roles screen430 that may be used to assign organizational roles and values to users124. The organizational roles and values may be stored inorganizational data repository150. Organizational roles are assigned to users124 in order to create user sets123 corresponding to the organizational roles.
• A user I.D.window432, aname window434, and anemail address window435 may be used to specify user124 by inserting the user identification, name, and email address, respectively, of user124. Abrowse button436 may be used to view a list of available users124. Anorganizational unit button438 may be used to select anorganizational unit162 for user124 referenced in user I.D.window432. The information may be stored inorganizational data repository150.
• Anorganizational roles section440 may be used to define organizational roles assigned to user124.Role name windows442 andvalue windows446 may be used to specify organizational roles and values for parametric organizational roles, respectively, assigned to user124. In the illustrated example, a Sales role having Team A value, and a Training role are specified for JDOE.
• Permission windows444 are used to specify the actions a user may perform in a specified role. Possible permissions may include: execute task, abort instance, suspend instance, and route instance. The permission may be assigned to a particular user124, which may provide for different users124 associated with the same organizational role having different permissions.
• Add and removebuttons448 may be used to add or remove, respectively, organizational roles. Organizational roles screen400 and assign organizational roles screen430 thus allow for efficient specification of organizational roles, values, and user sets123. According to one embodiment,organizational settings module134 may be used to define and configure users124,organizational roles160, andorganizational units162.
• FIG. 8 illustrates one embodiment of a match roles screen450 that may be used to match abstract roles with organizational roles when a business process is published into an organization. Match roles screen450 includesabstract role windows452 andorganizational roles windows454 that may be used to specify the abstract roles and organizational roles to be matched. In the illustrated example,Abstract Role1 is matched with a Sales organizational role, andAbstract Role2 is matched with a Training organizational role.
• Parametric boxes456 may be used to specify whether a role is parametric. Software based on the abstract role definition may be used to determine whether a role is parametric. If an organizational role is parametric,value windows458 may be used to specify a value for the organizational role. In the illustrated example, a Team A value is specified for Sales, and nothing is specified for Training.
• FIG. 9 is a flowchart illustrating one embodiment of a method for defining and implementing organizational roles. In the illustrated example, assign organizational roles screen430 is used to assign Sales and Training roles to user124 JDOE. Match roles screen450 is used to match abstract roles ofbusiness process210 with organizational roles defined inorganization data repository150. After role matching has been performed, user124 JDOE may have access toactivities212a,212b, and212ebecause user124 JDOE has been assigned the Sales and Training roles. As a result, user124 JDOE is allowed to participate in the execution ofactivities212a,212band212e.
• The method begins atstep462, where anactivity212 is associated with an abstract role. An abstract role is created usingprocess designer132. Once the abstract role has been created,activity212 can be located within the abstract role location. In this case,activity212 belongs to a specific domain delimited by the abstract role.Activity212 may be defined and abstract role may be specified usingdesigner screen200 ofFIG. 2.Activity212 and the associated abstract role are stored withbusiness process210 inorganization data repository150.
• Organizational roles are added atstep464 usingorganizational settings module134. Organizational roles screen400 may be used to generate a request to define organizational roles. Values may be specified for a parametric organizational role. Atstep466, users124 are assigned to organizational roles. The assignment specifies the activities for which users124 may participate in the execution. In the illustrated example, Sales and Training are specified for user124 JDOE. Values may be specified for organizational roles that are parametric. In the illustrated example, a Team A is specified for Sales, and no value is specified for Training since Training is not parametric. Atstep468,organizational settings module134 stores the organizational notes and corresponding users124 inorganization data repository118.
• Business process210 may be published atsteps472 and474 usingprocess designer132 orexecution console136. Match roles screen450 to generate a request to match abstract roles with organizational roles is displayed. A user124 such as an administrator may use match roles screen450 to generate a request matching the abstract role and the organizational role. The request is received atstep472. The abstract role and the organizational role are matched and stored atstep474. In the illustrated example,Abstract Role1 is matched with Sales, andAbstract Role2 is matched with Training. The matching is stored inorganization data repository150.
• Atstep476, execution engine140 receives a request from user124 to determineactivities212 that user124 has access or authorization to process. User124 is validated and is connected to execution engine140. Execution Engine140 determines the organizational role or roles associated with user124 atstep477.
• Atstep478, execution engine140 identifies activities that user124 is allowed to access. If the organizational role is not parametric, user124 may access activities associated with the organizational role assigned to user124. If the organizational role is parametric, the user124 may access instances associated with values assigned to user124. User124 is granted access to the allowed activities atstep480. After granting access, the method terminates.
• Organizational roles screen400, assign organizational roles screen430, and matchrole screen450 allow for easy specification and matching of abstract roles and organizational roles. Thus, the method provides for efficient definition of users124 responsible for performingactivities212 ofbusiness process210.
Publication and Deployment
• FIG. 10 illustrates one embodiment of a publishscreen500 that may be used to publishbusiness process210.Process designer132 andexecution console136 publishbusiness process210 toorganization data repository150 by matching abstract roles with organizational roles, and then storing the matched abstract roles and organizational roles inorganization data repository150. Metadata and the structure of the business process model may also be stored inorganization data repository150. Metadata describes a graphical representation of the business process model.
• After publication,business process210 may be deployed into a testing environment before deployingbusiness process210 to users124 of a production environment.Process designer132 andexecution console136 displays publishscreen500 in order to match the abstract roles with the organizational roles.
• Publishscreen500 includes a “publish to”section510, aprocess information section512, and acommands section514. “Publish to”section510 is used to specify the organization andorganizational unit162 for whichbusiness process210 is to be published. Publish tosection510 includes anorganization window516 and anorganizational unit window518, where names of the organization andorganizational unit162, respectively, may be placed. Users124 oforganizational unit162 specified in “publish to”section510, for example, a Sales organizational unit, may be granted access tobusiness process210 after deployment ofbusiness process210 to a production environment.
• Process information section512 includes aname window520 that displays a name ofbusiness process210 to be published, for example,Process1. Avariation window522 is used to show the variation of the business process to be published. The variation may describe, for example, a business process published to a specificorganizational unit162. Variations may be used if variations of the same business process are to be used in the same organization. For example a business process may be implemented one way inRegion1 and may be implemented another way inRegion2. Conceptually, the business processes do the same thing, but are implemented differently.
• Version window524 displays the version of the variation ofbusiness process210 to be published. The version number may track the number oftimes business process210 has been published. For example, a version number “1.3” may indicate that a first version of the business process has been published three times. A newmajor version button526 may be selected in order to adjust the version number to show that the business process to be published is a new major version. For example, version number “2.0” may be used to indicate a new major version over version number “1.0”.
• Afile window528 is used to specify business process model location, for example, a computer associated withdesigner122. Amatch roles button530 may be used to display match roles screen450 that may be used to match abstract roles with organizational roles in a manner substantially similar to the method described in connection withFIG. 9. A deploy process intest server box532 may be selected in order to deploybusiness process210 to a test environment automatically after publication.
• Commands section514 may be used to specify additional commands, for example, a JAVA compiler program used to generate business process metadata when publishingbusiness process210. Abrowse button534 may be selected to list available commands that may be inserted intocommands section514. Astatus window536 shows the status of the publication process. Okay and cancelbuttons538 may be used to submit or cancel, respectively, a request to publishbusiness process210.
• FIG. 11 is a flowchart illustrating one embodiment of a method for publishingbusiness process210. In the illustrated example, publishscreen500 is used to publishProcess1 destined for aSales organization unit162 in order to testProcess1.Process1 is deployed to allow users of the Salesorganizational unit162 access toProcess1.
• The method begins atstep560, whereprocess designer132 displays publishscreen500. Publishscreen500 is used to generate a request to publishbusiness process210 toorganization data repository150. In the illustrated example,Process1 is published for a Salesorganizational unit162. Publishscreen500 is also used to access match roles screen450 to generate a request to match abstract roles and organizational roles. In response to the request,process designer132 matches abstract roles and organizational roles atstep562.
• Atstep564,process designer132 initiates publication generating a suitable object-based code such as Java code for the tasks ofactivities212 ofbusiness process210. The code is then compiled using a suitable compiler such as a Java compiler. The code may also be packaged and compressed by using a suitable compression method such as zip compression. Atstep566,process designer152 completes publication by storing the code and the material abstract roles and organizational notes inorganization data repository150.
• Atstep568, the method determines whetherbusiness process210 is to be deployed to a testing environment.Designer122 of the organization may inspect and test publishedbusiness process210 in a test environment to determine whether it is ready for deployment. Ifbusiness process210 is not ready for deployment atstep568, the method terminates.
• Ifbusiness process210 is ready for deployment atstep568, the method proceeds directly to step574. At step574,business process210 is deployed toorganizational unit162 using execution engine140 specified atstep560. Users oforganizational unit162 may be granted access tobusiness process210 after deployment. After deployingbusiness process210, the method terminates. To summarize, the method provides for publication ofbusiness process210 that allows for inspection and testing ofbusiness process210 without deployment ofbusiness process210 to a production environment.
Persistent Variables
• FIG. 12 is a flowchart illustrating one embodiment of a method for implementing an instance variable, a type of persistent variable. An instance variable allows for a value associated with an instance ofbusiness process210 to be transferred from oneactivity212 to anotheractivity212 ofbusiness process210.Business process210 may include, for example,activities212 for processing a sales order, and the instance may describe the processing of a specific sales order. The instance is associated with an instance variable, which may describe, for example, a requested quantity of goods for that particular sales order.
• The method begins atstep610, where an instance ofbusiness process210 is initiated. Afirst activity212aofbusiness process210 is executed atstep612. Atstep614, a value corresponding to the instance variable is received. The value may describe a quantity of goods. Execution engine140 records the value and the instance variable in objects atstep616. The objects may comprise, for example, a Java object. The objects are serialized atstep618 so that the objects can be persisted in a data repository. A serialization mechanism may be used for complex structures. Atstep620, the objects are stored intransactional data repository118.
• Atstep622, asecond activity212bofbusiness process210 is executed.Activity212bmay require the value for the instance variable that was received during execution offirst activity212a. Atstep624, the objects that record the value are retrieved fromtransactional data170 for use bysecond activity212b. To determine the value previously set inactivity212a, the value retrieved fromtransactional database170 may be deserialized to be read by the task in second activity. After retrieving the objects, the method terminates.
• FIG. 13 is a flowchart illustrating one embodiment of a method for implementing an argument variable, another type of persistent variable. An argument variable allows for a value to be transferred from one business process210ato another business process210b. For example, a first business process210amay describe processing sales orders, and an instance may describe processing a specific sales order. The instance is associated with an argument variable that describes, for example, a requested quantity of goods for the particular sales order. A second business process210bmay describe determining the inventory of a type of goods, and may require information about quantities of goods requested by sales orders. An argument variable allows for information about requested quantities of goods to be transferred from first business process210ato second business process210b.
• The method begins atstep650, where an instance of first business process210ais initiated by execution engine140 with a value for a process instance variable as described inFIG. 12. First business process210a, includes an activity that connects first business process210awith second business process210b. An instance variable of first business process210ais associated with an argument variable used to send a value to second business process210b. Atstep652, a value corresponding to the argument variable is received. The value may describe a quantity of goods. The value for the corresponding argument variable is recorded in objects. The objects may comprise, for example, a Java object. The objects are serialized atstep656 for recording the objects in a data repository. Atstep658, the serialized objects are stored intransaction database170 ofdata repository118.
• Atstep660, a process instance variable of second business process210bis initiated with a default value. Atstep662, the argument variable of first business process210ais mapped to the instance variable of second business process210band persisted intransactional database170. Atstep664, the objects that record the value for process instance variable are retrieved fromtransactional data170 for use by the instance of second business process210b. After the objects are retrieved, the method terminates.
• Embodiments of the present invention provide advantages for automating business processes210. Business processes210 may includeactivities212 withcompensation tasks312.Compensation tasks312 are executed when an associatedtask310 ofactivity212 fails to execute. Additionally, anactivity212 may be associated with an abstract role to efficiently specify users124 representing people who are responsible for performing theactivity212.
• Moreover, the processes of publishing and deployingbusiness processes210 are separated. By separating the publication and deployment processes,business process210 may be published and tested, without deployment ofbusiness process210 toorganizational unit162. Furthermore,system100 provides persistent variables, which allow a value related to an instance to be carried from one activity to another activity. Consequently, embodiments of the present invention provide effective and efficient systems and methods for automating business processes210.
Distributed Process Flow
• FIGS. 14 through 18 illustrate embodiments of distributed process flow. Distributed process flow provides for the definition of distributed processes, which may improve process design and implementation. Distributed process flow may be applied to any suitable software program.
• According to one embodiment, distributed process flow is applied to abusiness designer700. According to the illustrated example,business designer700 offers the following distributed features: asynchronous process creation, synchronous process creation, process-to-process notification, external notification to processes, and process interruption. Distributed process flow may be applied to any procedure, for example, process modularization, logical distribution of implementable processes, task parallelization, or notification between processes.
Asynchronous Process Creation
• FIG. 14 illustrates an example of asynchronous process creation, which may be called non-blocking process creation. Asynchronous process creation allows for a first business process to create an instance in a second business process represented by an activity of the first business process. According to one embodiment, instance creation is requested by aparent business process710, and the instance is created in achild business process712.
• An instance ofparent business process710 is not required to wait for an instance inchild business process712 and may continue flowing throughparent business process710. Both instances may run concurrently inbusiness processes710 and712. An asynchronous instance creation may occur in thesame business process710, which involves callingbusiness process710 recursively.
• In the illustrated example, once an order is received and processed in aFather parent process710, the order is sent to PostOrder child process712 for further processing. PostOrder child process712 is represented by a process creation activity.Father parent process710 is not required to wait until order processing in PostOrder child process712 is completed.
• Eachbusiness process710 and712 may have incoming parameters, known as incoming arguments. When an instance is created asynchronously inchild business process712, parameters are passed tochild business process712.
Synchronous Process Creation
• FIG. 15 illustrates an example of synchronous process creation, which may be called blocking process creation. Synchronous process creation is similar to asynchronous process creation, however, an instance in aparent business process714 waits until an instance in achild business process716 is complete. Once the instance ofchild business process716 is complete, the instance inparent business process714 continues to flow throughparent business process714. When an instance is created synchronously inchild business process714, arguments are passed tochild business process714.
• In the illustrated example,Father parent process714 waits for a response fromDelivery child process716 to confirm successful delivery of goods stated in the order.
Process-to-Process Notification and External Notification
• FIG. 16 illustrates an example of process-to-process notification and external notification. Process-to-process notification and external notification allow for communication and synchronization between business processes.
• Process-to-process notification is based on process notification and notification wait activities. The process notification activity is used to send a notification to an instance at a notification wait activity of a second business process. If the instance is not at the notification wait activity, the notification is stored at the execution engine140. The instance is notified when it reaches the notification wait activity. If the notification wait activity has not received the notification, the instance waits until the notification arrives and is notified by the execution engine140, after which the instance may continue to flow through the business process.
• Three types of relations between business processes: child-parent, parent-child, process-external event. A child-parent relation exists when a parent business process creates an instance in a child business process, and the child business process sends a notification to the parent business process, which is managed bybusiness designer700. A parent-child relation exists when a parent business process creates an instance in a child business process and the parent business process sends a notification to the child business process, which is managed bybusiness designer700.
• A process-external event relation exists when an external source sends an external notification to an instance in a notification wait activity of a business process. The external source may comprising a program written in a different programming language or a process not related to the business process by a parent-child relationship. The external notification uniquely identifies the instance to which it is sending the notification. Parameters are used when creating instances in a process and are passed when a notification is sent to an instance in another business process.
• In the illustrated example business process718, an order atDelivery720 to be delivered is sent asynchronously, after which processing atReview Order722 may occur. Business process718 waits until delivery confirmation is received.
• FIG. 17 illustrates an example of process-to-process notification and external notification. In the illustrated example, afirst business process724 notifies a second business process.First business process724 sends a notification to the second business process waiting for the delivery confirmation.
Process Interruption
• FIG. 18 illustrates an example of process interruption. Process interruption is form of process-to-process communication. Process interruption allows a first business process to interrupt a second business process in order to process an interruption or urgent event over a particular instance. This notification is similar to the notification wait activity, but in this case the instance is not required to be at the notification wait activity. Once the notification is sent, the instance is taken automatically to the notification wait activity, regardless of where the instance is in the process.
• In the illustrated example, an instance inbusiness process730 flows to aCredit Check activity730. Under normal conditions, the instance is processed without error, however, a warning may be issued to indicate an abnormality with a particular instance.Business process730 receives an external notification, and the instance is automatically forwarded to aCredit Warning activity734 and continues to flow through aProcess Warning activity736.
Polymorphic Sub-Process
• FIG. 19 illustrates an example of polymorphic sub-processes. A polymorphic sub-process creates instances in different child business processes sharing the same interface, depending on variables embedded in a parent business process. According to one embodiment, a parent and child business process use the same interface to communicate between the business processes. An interface may be defined by the input and output arguments of a business process and a notification wait activity. The instance may be routed to the correct child business process according to predefined variables. The variables may include, for example, organizational unit, organization, and country.
• In the illustrated example,child business Process1740a,Process2740b, andProcess3740cofparent business process744 share acommon interface746.Common interface746 allows aparent business process744 to create an instance in any of the child business processes740.
• Certain embodiments of the invention may provide numerous technical advantages. A technical advantage of one embodiment is that business processes may include activities with compensation tasks. Compensation tasks are executed when a task of an activity fails to execute, thus allowing for the performance of the activity to continue uninterrupted to completion. Compensation tasks may be used for automated business processes to maintain business process consistency.
• Another technical advantage of one embodiment is that an activity may be associated with an abstract role in order to specify users representing people responsible for performing the activity. The association may provide for abstract business process modeling, which may allow for the creation of business process templates creation that may be used for different organizations.
• Another technical advantage of one embodiment is that the processes of publishing and deploying business processes are separated. By separating the publication and deployment processes, a business process may be published and tested, without deploying the business process to users. Another technical advantage of one embodiment is that persistent variables are used. Persistent variables allow a value related to an instance of a business process to be efficiently carried from one activity of the business process to another activity of the same business process or of another business process.
• Although an embodiment of the invention and its advantages are described in detail, a person skilled in the art could make various alterations, additions, and omissions without departing from the spirit and scope of the present invention as defined by the appended claims.

Claims (26)

1. A method for separating the publishing and deployment of a business process, said method comprising:

accessing a business process comprising a plurality of activities, each activity associated with an abstract role and including a sequence of one or more tasks;

accessing a plurality of organizational roles;

matching each abstract role with an organizational role;

publishing the business process to a data repository wherein publishing the business process includes creating a plurality of object classes representing the business process having the matched organizational roles, compiling the object classes and storing the compiled object classes in the data repository;

inspecting and testing the published business process in the data repository, without deploying the business process to an execution engine;

determining whether the business process is ready for deployment in a production environment with actual users;

deploying the business process to the execution engine upon determining that the business process is ready for deployments;

executing a task of at least one activity of the business process;

determining by the execution engine, that the task of the business process has failed; and

executing a compensation task that is associated with said task if the task has failed such that execution of the compensation task attains a steady and consistent state in the business process.

2-3. (canceled)

4. The method ofclaim 1, wherein the object classes comprise a Java class.

5. The method ofclaim 1, wherein deploying the business process further includes:

specifying an organizational unit associated with the business process, the organizational unit associated with a set of users;

deploying the business process; and

providing the set of users access to the business process.

6. The method ofclaim 1, wherein deploying the business process further includes:

specifying an execution engine associated with the business process; and

deploying the business process by notifying the execution engine of the business process.

7. The method ofclaim 1, wherein deploying the business process further includes:

specifying an execution engine associated with the business process;

deploying the business process;

transmitting an instance of the business process to the execution engine; and

executing the instance using the execution engine.

8. (canceled)

9. A system for publishing a business process, comprising:

a first data repository operable to:

store a business process comprising a plurality of activities, each activity associated with an abstract role and including one or more tasks; and

store a plurality of organizational roles;

an organizational settings module coupled to the first data repository and operable to match each abstract role with an organizational role; and

a process designer coupled to the first data repository and operable to publish the business process to a second data repository by creating a plurality of object classes representing the business process having the matched organizational roles, compiling the object classes and storing the compiled object classes in the data repository;

a publish screen used for publishing the business process; and

an execution engine for executing an instance of the business process once the published business process has been inspected and tested wherein the execution engine determines that a task of the instance of the business process has failed and executes a compensation task associated with said task in order to attain a steady and consistent state within the business process.

10-11. (canceled)

12. The system ofclaim 9, wherein the object classes comprise a Java class.

13. The system ofclaim 9, wherein:

the organizational settings module is operable to define an organizational unit associated with the business process, the organizational unit associated with a set of users, the set of users granted access to the business process if deployed.

14. The system ofclaim 9, wherein the process designer is operable to:

specify an execution engine associated with the business process; and

deploy the business process by notifying the execution engine of the business process.

15. (canceled)

16. The system ofclaim 9, wherein the organizational settings module is operable to:

display a screen for generating a request;

receive the request describing the abstract roles and the organizational roles; and

match each abstract role with an organizational role in response to the request.

17. Software for publishing a business process, the software embodied in a medium and when executed is operable to:

retrieve a business process comprising a plurality of activities, each activity associated with an abstract role and including one or more tasks;

retrieve a plurality of organizational roles;

match each abstract role with an organizational role;

publishing the business process to a data repository wherein publishing the business process includes creating a plurality of object classes representing the business process having the matched organizational roles, compiling the object classes and storing the compiled object classes in the data repository;

inspect and test the published business process in the data repository, without deploying the business process to an execution engine;

determine whether the business process is ready for deployment in a production environment with actual users;

deploy the business process to the execution engine upon determining that the business process is ready for deployments

executing a task of at least one activity of the business process;

determining by the execution engine that the task of the business process has failed; and

executing a compensation task that is associated with said task if the task has failed such that execution of the compensation task attains a steady and consistent state in the business process.

18-19. (canceled)

20. The software ofclaim 17, wherein the object classes comprise a Java class.

21. The software ofclaim 17, operable to:

define an organizational unit associated with the business process, the organizational unit associated with a set of users;

deploy the business process; and

provide the set of users access to the business process.

22. The software ofclaim 17, operable to:

define an execution engine associated with the business process; and

deploy the business process by notifying the execution engine of the business process.

23. The software ofclaim 17, operable to:

define an execution engine associated with the business process;

deploy the business process;

transmit an instance of the business process to the execution engine; and

execute the instance using the execution engine.

24. (canceled)

25. A system for publishing a business process, the system comprising:

a first data repository operable to:

store a business process comprising a plurality of activities, each activity associated with an abstract role; and

store a plurality of organizational roles;

an organizational settings module coupled to the first data repository and operable to:

match each abstract role with an organizational role; and

define an organizational unit associated with the business process, the organizational unit associated with a set of users;

a process designer coupled to the first data repository and operable to:

generate a publish screen used to publish the business process;

publish the business process to a second data repository such that the published business process is tested before deploying it to an execution engine, wherein publishing the business process includes performing the following:

creating a plurality of Java classes representing the business process having the matched organizational roles;

compiling the Java classes; and

storing the Java classes in the second data repository;

deploy the business process by performing the following:

defining an execution engine associated with the business process;

notifying the execution engine of the business process; and

providing the set of users access to the business process, the execution engine coupled to the process designer and operable to execute an instance of the business process according to the Java classes wherein the execution engine determines that a task of the instance of the business process has failed and executes a compensation task associated with said task in order to attain a steady and consistent state within the business process.

26. The method ofclaim 1, wherein publishing the business process further includes:

generating business process metadata and storing the business process metadata in the repository.

27. The method ofclaim 1, wherein generating a publish screen further includes:

generating a variation window used to show the variation of the published business process per specific organizational unit.

28. The method ofclaim 1, wherein generating a publish screen further includes:

generating a version window that tracks the number of times the business process has been published to the data repository.

29. (canceled)

Images