JP4307122B2 - Workflow processing method and program - Google Patents

Description

[0001]
[Technical field to which the invention belongs]
The present invention relates to a workflow processing technique.
[0002]
[Prior art]
In the past, much effort has been required to develop a workflow processing system. The fields on the slip screen that displays the slips handled in the workflow are input fields, display fields, or non-display fields, even if they are the same fields in the same slip, depending on the workflow progress status (current location) of the slip itself. In addition, the input field check logic (format check, master check, unique business logic, etc.) and display field display logic (master reference, calculation logic, format conversion logic, etc.) also change.
[0003]
In addition, workflow programming on the slip screen also applies to the workflow progress and defined workflow, depending on the workflow progress status (current location), such as application, approval / disapproval, remand, recovery, etc. It is necessary to determine whether the button (such as a button provided on the slip screen such as application or approval) is valid, and to proceed with the workflow by executing the workflow function selected by the user's operation.
[0004]
In this way, the slip screen corresponding to the workflow progress status (current location) has a considerable number of variations consisting of combinations with the respective slip forms with respect to variations of the workflow progress status (current location) in each workflow definition. Become.
[0005]
In this situation, in order to appropriately coordinate the programming of the slip field and the workflow programming on the slip screen for each slip style (slip type), the development sharing is the slip screen with workflow for each slip style (slip type). It becomes. The program developer had to understand all of the following matters when developing the slip screen with workflow. (1) Screen design, (2) Workflow control, (3) Slip field logic, (4) Coordination of (1) to (3) (Workflow status (current location) in a certain slip style and workflow definition in which it is used Therefore, for example, (1a) design of slip screen at the time of drafting, (2a) determination of available workflow function (application, etc.) and workflow execution, (3a) each input / output field of the slip Each program developer must perform programming to link the logic of (4a), (1a) to (3a). In this case, there is a problem that even if N people develop, the development period cannot be shortened.
[0006]
Further, for example, Japanese Patent Laid-Open No. 2001-134681 discloses the following technique. That is, an action that can be executed is defined for each worker on the workflow for processing the electronic form. When each worker operates the electronic form, an object such as a button corresponding to the action designated by the worker is displayed on the form image on the operation screen. By manipulating the object, the action is executed. Information about which node on the workflow is currently being processed, what action is defined as valid for that node, and what the status of the transitioned form will be Is set as current form information every time an electronic form moves between nodes by the server program. The client service program will display accordingly accordingly. In this technique, a method for generating a button is described, but a device for improving development efficiency is not disclosed in relation to an electronic form.
[0007]
[Patent Document 1]
JP 2001-134681 A
[0008]
[Problems to be solved by the invention]
As described above, in the conventional workflow processing system, it is necessary to develop as many voucher screens with workflows as the number of voucher formats, so the development burden is large, and it takes time for the program developer to understand the system. The development period and maintenance time could not be shortened due to the sequential development by each person, and there were many problems such as the need for a complete review even when part of the system was changed. This is a major cause of the above-mentioned problems because it has been necessary to adopt a development method in which workflow slip forwarding control and slip screen programming are mixed.
[0009]
Accordingly, an object of the present invention is to provide a technique for enabling the development and maintenance efficiency of a workflow processing system to be improved.
[0010]
[Means for Solving the Problems]
A workflow processing method according to the present invention includes, based on data received from a user terminal, a position specifying step for specifying a position that is either a state or a state transition between the states in a workflow process for a specific slip; , Slip form data acquisition step that acquires the form data related to the position and stores it in the storage device, and the state that can be instructed by the user in relation to the specified position based on the workflow definition A transition data acquisition step for acquiring transition data and storing it in the storage device, and generating at least electronic form display data from the slip form data, and generating button display data from the state transition data, and outputting them Display data generation step. Furthermore, it is possible to minimize correction even during maintenance.
[0011]
In this way, the electronic form display data from the form data of the slip related to the specified position, the button display data from the state transition data that can be instructed by the user based on the workflow definition. Since it is generated, the development work related to the form data of the slip can be separated from the development work related to the workflow. Therefore, the parallelism of development is improved and the burden on each program developer can be reduced.
[0012]
Further, in the present invention, when the specified position is a state transition, the display further includes a program start step for starting a program specified by at least the state transition and a slip related to the state transition. In the data generation step, electronic form display data can be generated by further using data from the program. As described above, since the slip and the program to be executed in relation to the state transition are also started in accordance with the state transition, it can be developed separately from the electronic form display data. Therefore, the development efficiency is improved.
[0013]
Further, in the present invention, when a predetermined state transition is specified in the position specifying step described above, the data input to the electronic form related to the state before the transition of the specific state transition and the transition of the specific state transition The method may further include a step of registering data relating to the previous state as workflow execution control information. Furthermore, a return value from the program started above may be registered. The workflow forwarding control is performed by the workflow definition information and the workflow execution control information, and is processed independently from the form data of the slip.
[0014]
Further, when the position specifying step described above receives the identification data of a specific workflow process from the user's terminal, the step of specifying the corresponding workflow execution control information based on the identification data of the specific workflow process The step of specifying the current state by the workflow execution control information to be performed may be included. For example, this is processing when a user having specific authority approves an application.
[0015]
The above-described method can be implemented by a program and a computer, and the program is stored in a storage medium or storage device such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, or a hard disk. Moreover, it may be distributed as a digital signal via a network or the like. The intermediate processing result is temporarily stored in the memory.
[0016]
DETAILED DESCRIPTION OF THE INVENTION
FIG. 1 shows a system outline diagram according to an embodiment of the present invention. For example, the network 1 which is a LAN (Local Area Network) has one or a plurality of user terminals 3 having a Web (Web) browser function, for example, with a personal computer, a well-known Web server function 51, and in the present embodiment. A workflow processing system 5 that performs main processing is connected. The network 1 may be connected to a developer terminal 7 that is operated by a developer or a person in charge of maintenance and is a personal computer, for example.
[0017]
In response to a request from the user terminal 3, the workflow processing system 5 generates Web page data (such as an HTML (Hyper Text Markup Language) file and an embedded image file) and transmits the generated data to the user terminal 3. From the web server function 51 that receives input data and the like and outputs it to the slip container 53, the slip container 53 that exchanges data with the web server function 51 and performs the main processing in the present embodiment, and the slip container 53 A definition information DB 55 storing definition information to be referred to, a plurality of action components 57 that are programs executed by the slip container 53 and that perform predetermined processing, and various types of master files that have been conventionally used and actions Background system for exchanging data with component 57 And arm 59, and a workflow execution control information storage unit 58 for storing the workflow execution control information is control information in the execution individual workflow process.
[0018]
The slip container 53 includes an electronic form control unit 531, a workflow control unit 532, an event control unit 533, and a workflow data processing unit 534. Detailed processing of the slip container 53 will be described below. The background system 59 includes an affiliate master file 591, an employee master file 593, various business master files 595, and the like. The background system 59 is not different from the conventional system and will not be described in further detail.
[0019]
The action component 57 is a program, and is composed of, for example, EJB (Enterprise Java Beans: Java is a trademark of Sun Microsystems).
[0020]
As shown in FIG. 2, the developer terminal 7 includes an electronic form designer 71 and an associated property setting unit 73. The developer operates the developer terminal 7 to design the screen of the electronic slip by the electronic form designer 71 according to the provided GUI (Graphical User Interface). The attribute information such as the field name and type of the electronic slip is set for each field by the property setting unit 73. Also, the property setting unit 73 sets attribute information about the entire electronic slip. Along with the screen design data (form data) generated by the electronic form designer 71, the electronic form definition 551 set by the property setting unit 73 for each field and the entire electronic slip is registered in the definition information DB 55, and the slip container 53 Referenced by. An example of the electronic form definition 551 is shown in FIG. The table shown in FIG. 3 includes a slip name column 301, a field name column 302, and a type column 303, and attribute information such as a type is registered for each field provided in the electronic slip. Yes.
[0021]
In addition, the property setting unit 73 also defines what kind of event (state transition) the action component 57 is activated for performing processing for the background system 59 for the electronic slip. In FIG. 2, an event / action tab is selected to define an action component 57 to be activated for a specific field (for example, the number of remaining days). However, the action component 57 to be activated is defined for the entire slip. In the example of FIG. 2, an event is specified in the event input unit 731, an action component is specified in the action component input unit 732, a parameter item name is specified in the parameter item name specifying unit 733, and a parameter is specified in the parameter input unit 734. To do. Note that the event input unit 731 indicates options from the event definition 601 in a combo box format. An example of the event definition 601 is shown in FIG. The table shown in FIG. 4 includes an event name column 311 and a description column 312, and is a list of events that appear in the workflow processing system 5. In the present embodiment, an event definition 601 as shown in FIG. 4 is prepared in advance and is referred to in development work. In the event input unit 731, a combo box is configured by the data in the event name column 311 in FIG. 4.
[0022]
In addition, the action component input unit 732 indicates options from the business logic component definition 602 in a combo box format. An example of the business logic component definition 602 is shown in FIG. The table shown in FIG. 5 has an action part name column 321, a parameter number column 323, and a parameter item name column 324 corresponding to the parameter number, and a column 322 of input information to the component. For each action component, the number of parameters and the parameter item name to which data is to be input are defined. In the present embodiment, a business logic component definition 602 as shown in FIG. 5 is prepared in advance and is referred to in development work. The action component 57 is created according to the business logic component definition 602, and implements a function described in the action component name. In the action component input unit 732, a combo box is configured by the data of the action component name 321 in FIG. When a specific action component 57 is selected in the action component input unit 732, the number of columns for the specific action component 57 is determined from the value of the parameter number column 323 in FIG. item Name The display of the specifying unit 733 (FIG. 2) is expanded in the column direction. The parameter number in the property setting section 73 is 1 for “acquisition of remaining days of annual leave” but 1 for “annual leave application period / number of days check”. Name The display of the specifying unit 733 is automatically expanded into two columns.
[0023]
Further, the parameter item name specifying unit 733 is automatically specified from the business logic component definition 602 based on the action component name selected by the action component input unit 732. For example, since there is only one parameter for “acquisition of remaining days of annual leave”, “target year” is automatically specified. Since the “annual leave application period / number of days check” has two parameters, “target year” and “application period” are specified across two columns in the property setting section 73.
[0024]
The parameter input unit 734 is presented in a combo box format with field name data and system variables (such as% current year) included in the electronic form definition 551 specified in FIG. 3 as options.
[0025]
Thus, according to the screen displayed by the property setting unit 73, the event, action component, parameter item, and parameter are identified and registered as the item logic instruction definition 552. An example of the item logic instruction definition 552 is shown in FIG. The table shown in FIG. 6 includes a slip name column 331, an event name column 332, a field name column 333, an action component column 334, and a parameter information column 335 including parameter item names and parameters. An action component is specified for each combination of slip and event. In some cases, no value is registered in the column of the field name 333. In this case, an action component is defined as the entire slip.
[0026]
As described above, if there is an event definition 601 and a business logic component definition 602 related to a workflow, it is possible to proceed with the development of an electronic voucher without workflow data. Therefore, development efficiency can be improved. In the maintenance, the screen design can be changed without affecting the workflow.
[0027]
Further, as shown in FIG. 7, the developer terminal 7 also includes a workflow process setting unit 75, and the developer operates the developer terminal 7 to design a workflow by the workflow process setting unit 75. In accordance with the provided GUI. For example, a terminal 401 and an activity 403 are represented by using a terminal 401 for start and end, an activity 403 representing a state in the workflow, and an event 402 representing a state transition between the terminal 401 and the activity 403 or between activities. By connecting at event 402, the workflow is defined. Since the event 402 is defined in the event definition 601 (FIG. 4), when specifying an event name (for example, “draft”), for example, an option according to the event definition 601 by right-clicking. Is presented and can be selected. The developer defines all workflows handled in the workflow processing system 5 by the workflow process setting unit 75 and registers them in the definition information DB 55 as workflow process definitions 553. FIG. 8 shows an example of the data of the workflow process definition 553. The table shown in FIG. 8 includes a workflow process name column 341, an activity name column 342, an event name column 343, and a transition destination activity name column 344. For each workflow process, the source activity From which event to which transition destination activity is specified. Since there may be a transition from one activity to many activities, a plurality of records for the same activity may be registered even in one workflow process.
[0028]
When defining a workflow in this way, the event definition 601 is referred to, but other data need not be used. Therefore, development efficiency can be improved. Even in maintenance, a small workflow change does not affect the electronic form definition 551.
[0029]
A slip definition 554 is further registered in the definition information DB 55. An example of the slip definition 554 is shown in FIG. The table shown in FIG. 9 includes a business category name column 351, a slip name column 352, a form name column 353, a workflow process name column 354, an activity name column 355, and an event column 356. including. For example, when an activity name in a specific workflow process is identified or an event name in a specific workflow process is specified, the form data of the electronic slip to be used can be specified.
[0030]
In this way, in the definition information DB 55, the electronic form definition 551, the item logic instruction definition 552, the workflow process definition 553, and the slip definition 554 are registered, and the slip container 53 stores these definition information and action components. 57 and workflow execution control information stored in the workflow execution control information storage unit 58 are used for processing.
[0031]
Hereinafter, the processing flow of the workflow processing system 5 will be described with reference to FIGS. 10 to 18. It is assumed that the user is logged in to the workflow processing system 5 with his / her user ID or the user ID is specified by another method before the processing of FIG. First, the processing flow of application processing will be described. The user operates the user terminal 3 to access a menu page for workflow processing (step S1). The web server function 51 of the workflow processing system 5 transmits the data of the menu page to the user terminal 3 in response to the access from the user terminal 3 (Step S3). The user terminal 3 receives the menu page data from the workflow processing system 5 and displays it on the display device (step S5). It is assumed that the user selects and clicks “annual leave application” in the “work” category, for example, from various slips for various tasks included in the menu page. The user terminal 3 accepts a selection input of “annual leave application” by the user (step S7), and transmits selection data of the “annual leave application” to the workflow processing system 5 (step S9). The web server function 51 of the workflow processing system 5 receives the selection data of “annual leave application” from the user terminal 3 and temporarily stores it in the storage device (step S11), and executes the draft event processing (step S13). . The draft event process will be described with reference to FIG.
[0032]
When the Web server function 51 of the workflow processing system 5 receives the selection data of “annual leave application” as described above, the Web server function 51 notifies the event control unit 533 as a draft event of “annual leave application” (FIG. 11: Step S31). The event control unit 533 receives the “annual leave application” draft event from the Web server function 51, temporarily stores it in the storage device, and notifies the electronic form control unit 531 and the workflow control unit 532 (step S33). .
[0033]
The electronic form control unit 531 receives the “annual leave application” draft event from the event control unit 533, and temporarily stores it in the storage device (step S35). Then, with reference to the slip definition 554 (FIG. 9), the form name corresponding to “annual leave application” is specified, and the corresponding form data is extracted from the electronic form definition 551 by the form name (step S37). . Also, referring to the item logic instruction definition 552 in accordance with the “annual leave application” draft event, the action component 57 related to the draft event is specified, and the action component 57 is activated (step S39). If a parameter is defined in the item logic instruction definition 552, the parameter data is output to the action component 57. Each action component 57 performs a prescribed process, for example, G This is performed for the land system 59. For example, processing such as reading data on the remaining days of vacation registered in the employee master file 593 is performed.
[0034]
Then, the electronic form control unit 531 receives a return value from the action component 57 (step S41), and uses the return value from the action component 57 and the form data read from the electronic form definition 551 to use the electronic form unit. Is generated and temporarily stored in the storage device (step S43). For example, data for a screen as shown in FIG. In the example of FIG. 12A, the start input field 361 of the annual vacation acquisition period, the end input field 362 of the annual vacation acquisition period, and the remaining days display in which the return value from the action component 57 is embedded. A column 363 and a vacation reason selection combo box 364 are provided. Data of such an electronic form part is generated. The electronic form control unit 531 outputs the data of the electronic form unit to the web server function 51 (step S45).
[0035]
The workflow control unit 532 receives the “annual leave application” draft event from the event control unit 533, and temporarily stores it in the storage device (step S47). Then, referring to the workflow process definition 553 (FIG. 8), the transition destination activity of the “annual leave request” event is specified, and the data of the next event having the transition destination activity as the transition source is extracted (see FIG. 8). Step S49). In the example of FIG. 8, an “application” event is extracted. Then, the data of the workflow part is generated based on the data of the next event and temporarily stored in the storage device (step S51). For example, data for a screen as shown in FIG. In the example of FIG. 12B, since an “application” event is extracted, an application button 365 is provided. The application button 365 is a button for generating an application event of “annual leave application”. Data of such a workflow part is generated. The workflow control unit 532 outputs the data of the workflow unit to the web server function 51 (step S53).
[0036]
The Web server function 51 receives the electronic form part data from the electronic form control part 531, receives the workflow part data from the workflow control part 532, and temporarily stores it in the storage device (step S 55). And it returns to the process of FIG. The Web server function 51 generates application form data using the data of the electronic form part and the data of the workflow part, and transmits it to the user terminal 3 (step S15). The user terminal 3 receives the application form data from the workflow processing system 5 and displays it on the display device (step S17). For example, a screen as shown in FIG. 12C is displayed. That is, an electronic form unit 366 is provided in the upper stage, and a workflow unit 367 is provided in the lower stage. It is also possible to reverse the layout of the upper and lower stages. In addition, the button of the workflow unit 367 may not be a button but another clickable button such as a link.
[0037]
In the case of the screen as shown in FIG. 12, the user inputs a vacation start time and a vacation end time in the electronic form section 366, selects a vacation reason, and clicks an application button. The user terminal 3 receives input data and an application instruction for “annual leave application” by the user (step S19), and transmits the input data and data representing the application instruction to the workflow processing system 5 (step S21). The web server function 51 of the workflow processing system 5 receives the input data of “annual leave application” and the data indicating the application instruction from the user terminal 3, and temporarily stores them in the storage device (step S23). Then, application event processing is performed (step S25).
[0038]
The application event process will be described with reference to FIG. The web server function 51 of the workflow processing system 5 notifies the event control unit 533 of the input data of “annual leave application” and the data indicating the application instruction to the event control unit 533 as the input data and application event occurrence (FIG. 13: step S61). . The event control unit 533 receives the input data of “annual leave application” and the notification of occurrence of the application event from the Web server function 51, and notifies the electronic form control unit 531 and the workflow control unit 532 (step S63).
[0039]
When the electronic form control unit 531 receives the input data of “annual leave application” and the notification of occurrence of the application event from the event control unit 533 (step S65), the electronic form control unit 531 refers to the item logic instruction definition 552 and relates to the application event. The action component 57 is activated (step S67). At least a part of the input data of “annual leave application” is passed to the action component 57 as a parameter. The activated action component 57 performs a predetermined process such as checking whether there is a problem in the acquisition start period and the acquisition end period. Although not shown in the figure, the user ID of the forwarding supervisor (approver) is specified by the applicant at the time of application, and is handled as input data for “annual leave application”, for example. Further, the supervisor's e-mail address may be extracted to notify that the application has been submitted for the approval process. Then, the action component 57 outputs a return value to the electronic form control unit 531 based on the processing result. The electronic form control unit 531 receives the return value from the action component 57 (step S69). For example, if there is no problem with the input data of “annual leave application”, the input data, the return value from the action component 57, and the like are output to the workflow control unit 532 (step S71). Note that predetermined processing may be performed on input data of “annual leave application”.
[0040]
When the workflow control unit 532 receives the notification of occurrence of the application event from the event control unit 533 (step S77), the workflow control definition 553 is referred to according to the application event, and the transition source activity name and the transition destination activity name are specified (step S79). ). Then, input data of “annual leave application” or the like is received from the electronic form control unit 531 (step S81), and is output to the workflow data processing unit 534 as registration data together with the data specified from the workflow process definition 553 (step S81). S83). The workflow data processing unit 534 receives the registration data from the workflow control unit 532 (step S85) and registers it in the workflow execution control information storage unit 58.
[0041]
An example of the workflow execution control information is shown in FIG. The table shown in FIG. 14A is a workflow history column including a workflow process ID column 371 for specifying a workflow process for processing one specific slip, and an activity name column and an event name column. 372, a current activity column 373 for indicating the current state of each workflow process, a slip name column 374, a slip content column 375, and a user ID column 376 of the associated user. As shown in the example of FIG. 14A, in the present embodiment, as the workflow execution control information, a plurality of records are registered for the same workflow process ID, and the latest state is indicated by the flag in the column 373 of the current location activity. The record to represent is specified. That is, the flag in the current location activity column 373 of records other than the latest record is OFF.
[0042]
At the application event, since registration is not performed in the workflow process definition 553 in the draft event, a workflow process ID is issued and registered in the workflow process ID column 371. Then, in the workflow history column 372, “application” is registered as the transition source activity name and “application” as the occurrence event name. Further, “annual leave application” is registered in the slip name column 374, and slip data of “annual leave application” is registered in the slip content column 375. Further, the user ID of the applicant is registered in the user ID column 376. As described above, since no registration is performed in the workflow process definition 553 at the time of the draft event, another record is registered. The record includes the transition destination activity (approval 1), the ON flag of the current location activity (circled in FIG. 14 (a)), the slip name (annual leave application), and the user ID (supervisor's user ID). And are included. Other data is registered when the next event occurs. When the processing is executed so far, the workflow execution control information is in the state shown in FIG.
[0043]
When the process ends, the workflow data processing unit 534 notifies the workflow control unit 532 of a process end notification (step S87). Upon receiving the processing end notification from the workflow data processing unit 534, the workflow control unit 532 further notifies the Web server function 51 (step S89). In addition, when an application event occurs, Raka Since the button for generating the event is not presented, the workflow part data is not generated. However, data of a workflow part that does not include a button may be generated and output to the web server function 51.
[0044]
On the other hand, if there is no problem in the return value of the action component 57, the electronic form control unit 531 may be an electronic form unit such as “application has been completed” or “*** has been completed”. Generate data for Note that an electronic form definition 551 used when an application event occurs may be defined, and the electronic form definition 551 may be specified with reference to the slip definition 554. Then, the electronic form control unit 531 outputs the generated electronic form unit data to the Web server function 51 (step S75). Then, the Web server function 51 receives the data of the electronic form unit from the electronic form control unit 531 (Step S91). The web server function 51 also receives a process end notification from the workflow control unit 532.
[0045]
If the return value from the action component 57 is a value indicating that the application is not appropriate, the processing of the electronic form control unit 531 is interrupted, and the processing proceeds to step S15 (FIG. 10). If the return value from the action component 57 is a value indicating that the application is not appropriate, the electronic form control unit 531 proceeds to step S15 (FIG. 10) with respect to the workflow control unit 532 in step S71. Outputs data indicating that If it does so, the process of the workflow control part 532 will be interrupted and a process will transfer to step S15 (FIG. 10). Then, the web server function 51 transmits the held application form data to the user terminal 3.
[0046]
Returning to the processing of FIG. 10, the Web server function 5 1 generates the data of the application acceptance notification page using the received data of the electronic form part (data of the workflow part without buttons in some cases) and transmits it to the user terminal 3 (step S27). The user terminal 3 receives the application acceptance notification page data from the workflow processing system 5 and displays it on the display device (step S29).
[0047]
In this way, the user can make an “annual leave application”. However, not only the annual leave application but also other application processes are performed in the same process. As described above, the electronic form definition 551, the item logic instruction definition 552, the action component 57, and the workflow process definition 553 are developed separately, but the slip container 53 organically links them for processing. In order to carry out, the user can perform processing such as application without feeling any problems. In the slip container 53, the processing related to the workflow process definition 553 and the processing related to the electronic form definition 551 and the item logic instruction definition 552 are almost separated. Processing according to the workflow process definition 553 is performed.
[0048]
Next, the processing flow of the approval process will be described with reference to FIGS. In this case as well, it is assumed that the workflow processing system 5 has already grasped the user ID by login or the like. For example, a user with approval authority operates the user terminal 3 to access an approval page for performing approval processing (step S101). When receiving the access to the approval page from the user terminal 3 (Step S103), the Web server function 51 of the workflow processing system 5 issues an inquiry request for approval including the login ID to the workflow control unit 532 of the slip container 53. Output.
[0049]
When the workflow control unit 532 receives an inquiry request for approval including a login ID, the workflow control unit 532 outputs the request to the workflow data processing unit 534. The workflow data processing unit 534 searches the workflow execution control information storage unit 58 using the login ID as a search key, and is a record in which the ON flag is set in the column 373 of the current location activity, and the login ID is registered as the user ID. Identify records that are current and the current activity is “approved”. Then, the workflow process data for the specified record is read (step S105). The read workflow process data includes, for example, a workflow process ID, a slip name, and a user ID of the user who has applied. In some cases, the user name corresponding to the user ID may be extracted from another database. The workflow process data is output to the workflow control unit 532. Work flow System The control unit 532 outputs the workflow process data to the Web server function 51. Then, when the web server function 51 receives the workflow process data from the workflow control unit 532, the web server function 51 generates data of an approval target selection menu page including data such as the workflow process ID and the slip name, and transmits the data to the user terminal 3 (step). S107). The user terminal 3 receives the data of the approval target selection menu page from the workflow processing system 5 and displays it on the display device (step S109).
[0050]
The user looks at the contents of the approval target selection menu and determines which slip (workflow process) is to be processed. Then, any one slip (workflow process) is selected, and a button corresponding to the slip is clicked. The user terminal 3 receives an approval target selection input from the user (step S111), and transmits approval target selection data (workflow process ID) to the workflow processing system 5 (step S113). The web server function 51 of the workflow processing system 5 receives the approval target selection data (workflow process ID) from the user terminal 3 and temporarily stores it in the storage device (step S115). Then, an approval activity start process is performed (step S117).
[0051]
The approval activity start process will be described with reference to FIG. The Web server function 51 outputs the received approval target workflow process ID to the event control unit 533 (step S141). When receiving the approval target workflow process ID from the Web server function 51, the event control unit 533 notifies the electronic form control unit 531 and the workflow control unit 532 of the approval target workflow process ID (step S143). The electronic form control unit 531 receives the approval target workflow process ID from the event control unit 533 (step S145). The workflow control unit 532 receives the approval target workflow process ID from the event control unit 533 (step S147), and outputs it to the workflow data processing unit 534 (step S148). Upon receiving the approval target workflow process ID from the workflow control unit 532 (step S149), the workflow data processing unit 534 searches the workflow execution control information storage unit 58 with the approval target workflow process ID, extracts related data, and extracts the workflow. It outputs to the control part 532 (step S151). The related data is, for example, a current activity name, a workflow process name, the contents of a slip registered by a previous event, and the like.
[0052]
Upon receiving the related data of the workflow execution control information corresponding to the approval target workflow process ID from the workflow data processing unit 534, the workflow control unit 532 further outputs the data to the electronic form control unit 531 (step S153). The electronic form control unit 531 receives the related data of the workflow execution control information corresponding to the approval target workflow process ID (step S155). Then, the slip definition 554 is referred to based on the workflow process name and the current activity name included in the received data, and the corresponding electronic form definition 551 is specified (step S157). Using the electronic form definition 551 and the data received from the workflow control unit 532 (for example, the contents of the previous slip), the electronic form unit data is generated and temporarily stored in the storage device (step S159). Finally, the electronic form control unit 531 outputs the data of the electronic form unit to the web server function 51 (step S161).
[0053]
The workflow control unit 532 refers to the workflow process definition 553 based on the workflow name and the current activity name included in the related data of the workflow execution control information corresponding to the approval target workflow process ID, and can generate an event (next event) that can occur from the current activity. ) Information is specified (step S163). Then, data of the workflow unit is generated using the information of the next event, and is temporarily stored in the storage device (step S165). Then, the generated workflow section data is output to the Web server function 51 (step S167).
[0054]
The Web server function 51 receives data of the electronic form unit from the electronic form control unit 531 and data of the workflow unit from the workflow control unit 532 (step S169). For example, data for displaying a “Approve” button and a “Deny” button is generated.
[0055]
Returning to the processing of FIG. 15, the Web server function 51 generates approval instruction page data using the received data of the electronic form part and the data of the workflow part, and transmits it to the user terminal 3 (step S119). The user terminal 3 receives the approval instruction page data from the workflow processing system 5 and displays it on the display device (step S121).
[0056]
The user refers to the approval instruction page and determines whether to approve. If you decide to approve, enter the reason for approval and then click the “Approve” button. If you decide not to approve, enter the reason for rejection and click the “Decline” button. To do. In some cases, the reason is not entered. In some cases, another data must be input. The user terminal 3 receives input data and instruction input by the user (step S123), and transmits the input data and instruction input to the workflow processing system 5 (step S125).
[0057]
The web server function 51 of the workflow processing system 5 receives input data and instruction input data on the approval instruction page from the user terminal 3, and temporarily stores them in the storage device (step S127). Then, an instruction input event process is performed (step S129). This instruction input event process will be described with reference to FIG.
[0058]
The web server function 51 of the workflow processing system 5 converts the input data and the instruction input data on the approval instruction page into the input data and the instruction input event occurrence (for example, “pass” event or “decision” event (in some cases, “return”). "Event))" is notified to the event control unit 533 (FIG. 17: step S171). The event control unit 533 receives the input data of the approval instruction page and the notification of the occurrence of the instruction input event from the web server function 51, and notifies the electronic form control unit 531 and the workflow control unit 532 (step S173).
[0059]
When the electronic form control unit 531 receives the input data on the approval instruction page and the notification of the occurrence of the instruction input event from the event control unit 533 (step S175), the electronic form control unit 531 refers to the item logic instruction definition 552 and performs an action related to the instruction input event. The component 57 is activated (step S177). In some cases, at least part of the input data on the approval instruction page is passed to the action component 57 as a parameter. The activated action component 57 performs a predetermined process such as reconfirming the authorization authority. In addition, there may be a process of reading the user ID of a higher-level approver from the affiliation master file 591 of the background system 59. Further, the e-mail address of a higher-level approver may be extracted and notified. Then, the action component 57 outputs a return value to the electronic form control unit 531 based on the processing result. The electronic form control unit 531 receives the return value from the action component 57 (step S179). For example, if there is no problem with the instruction input event, the input data on the approval instruction page, the return value from the action component 57, and the like are output to the workflow control unit 532 (step S181). Note that a predetermined process may be performed on the input data on the approval instruction page.
[0060]
When the workflow control unit 532 receives a notification of the occurrence of the instruction input event from the event control unit 533 (step S185), the workflow control unit 532 refers to the workflow process definition 553 according to the instruction input event and specifies the transition source activity name and the transition destination activity name ( Step S187). Then, the input data on the approval instruction page is received from the electronic form control unit 531 (step S189), and is output to the workflow data processing unit 534 as registration data together with the data specified from the workflow process definition 553 (step S191). The workflow data processing unit 534 receives registration data from the workflow control unit 532 (step S193) and registers it in the workflow execution control information storage unit 58.
[0061]
Registration in the workflow execution control information storage unit 58 will be described with reference to FIGS. 14 (a) and 14 (b). In the current activity column 373 (FIG. 14A), the ON flag is set in the row where the workflow process ID is 00001 and the activity name is “approval 1”. If the event name is “approved” after confirming the transition source activity name “approved”, “approved” is registered in the event name column, and the input data on the approval instruction page is set as approval 1 slip data in the slip content column 375. sign up. The same is true for the “no” event. Further, in order to register the transition destination activity, a new line is generated, “00001” is set in the workflow process ID column 371, “approval 2” is set in the activity name column in the workflow history column 372, and the current location activity is registered. The ON flag is registered in the column 373, “annual leave application” is registered in the column 374 of the slip name, and the user ID of the higher approver is registered in the column 376 of the user ID. At this time, the ON flag of the current location activity in the row of the event name “approved” with the activity name “approval 1” is reset. When the processing is executed so far, the workflow execution control information is in the state shown in FIG. In the case of a “denied” event, the transition destination activity is “application”, and the user ID of the applicant is registered in the user ID column 376. For example, FIG. 14C shows a state in which “approval 2” is “no”. In FIG. 14C, in the row of the activity name “approval 2”, “decision” is registered in the event name column, and the input data on the approval instruction page is registered as approval 2 slip data in the slip content column 375. For example, data such as the reason for rejection is included. Then, the ON flag of the current location activity in the row of the activity name “approval 2” is reset, and a row of activity name “application” is newly added. In the row of the activity name “application”, “annual leave application” is registered in the slip name column 374, and the user ID of the applicant is registered in the user ID column 376. Then, an ON flag is set in the current location activity column of the row.
[0062]
When the process is completed, the workflow data processing unit 534 notifies the workflow control unit 532 of a process end notification (step S195). Upon receiving the process end notification from the workflow data processing unit 534, the workflow control unit 532 notifies the Web server function 51 (step S197). What happens to the approver at the time of the “Approval” event? Raka Since the button for generating the event is not presented, the workflow part data is not generated. However, data of a workflow part that does not include a button may be generated and output to the web server function 51.
[0063]
On the other hand, if there is no problem in the return value by the action component 57, the electronic form control unit 531 has been “passed” for example, ““ Approved ”has been registered” or “***”. The data of the electronic form part is generated. Note that the electronic form definition 551 used when the approval event occurs may be defined, and the electronic form definition 551 may be specified with reference to the slip definition 554. Then, the electronic form control unit 531 outputs the generated electronic form unit data to the Web server function 51 (step S183). Then, the web server function 51 receives data of the electronic form unit from the electronic form control unit 531 (step S199). The web server function 51 receives a process end notification from the workflow control unit 532.
[0064]
If the return value from the action component 57 is a value indicating that a problem has occurred or that a problem has been detected, the process of the electronic form control unit 531 is interrupted, and the process proceeds to step S119 (FIG. 15). Transition. If the return value from the action component 57 is a value indicating that it is not appropriate, the electronic form control unit 531 sends data indicating that the process proceeds to step S119 (FIG. 15) to the workflow control unit 532 in step S181. Output. If it does so, the process of the workflow control part 532 will be interrupted and a process will transfer to step S119.
[0065]
Returning to the processing of FIG. 15, the Web server function 5 1 generates the data of the instruction completion notification page using the received data of the electronic form part (data of the workflow part without buttons in some cases) and transmits it to the user terminal 3 (step S131). The user terminal 3 receives the instruction completion notification page data from the workflow processing system 5 and displays it on the display device (step S133).
[0066]
In this way, a user who is an approver can perform an approval process. However, not only the annual leave application but also other application processes are performed in the same process. Furthermore, in addition to “Approve” and “Negative”, a “Return” button is provided in the workflow section when the determination “Return” can be made. Also in that case, the processing of FIG. 17 is basically performed. However, the action component 57 for notifying the previous approver (and / or the applicant) of the return is activated, the return is registered in the workflow execution control information, and the current location activity is also “approved * (* is 1). Represents the number of the previous approval activity) ”. At this time, the history is registered by further adding records. After the return, the same is true in that it starts from the “Approve *” activity.
[0067]
FIG. 18 outlines typical workflow examples and screen transitions. As shown in the upper part of FIG. 18, a transition is made from the start to the application activity by the draft event, a transition from the application activity to the approval 1 activity by the application event, a transition from the approval 1 activity to the approval 2 activity by the approval event, and an approval 2 activity. From the final approval activity to the final approval activity, and the final approval activity ends with the approval event. In addition, a transition is made from an approval 1 activity, an approval 2 activity, or a final approval activity to an application activity due to a rejection event. Transition from the approval 2 activity to the approval 1 activity by the return event, and from the final approval activity to the approval 2 activity by the return event. In the application activity in such a workflow, as shown in the lower part of FIG. 18, the electronic form part includes an electronic form for application, and the workflow part includes a Web page including an “apply” button that is an event that can occur. . In the approval 1 activity, the electronic form part includes an electronic form of approval 1, and the workflow part includes a Web page including “approved” and “denied” buttons that are events that can occur. In the approval 2 activity, an electronic form of approval 2 is configured in the electronic form section, and a web page including “pass”, “decline”, and “return” buttons that are events that can occur in the workflow section is configured. In the final approval activity, the electronic form section includes a final approval electronic form, and the workflow section includes a Web page including “pass”, “denial”, and “send back” buttons that can be generated events. As described above, the electronic form unit is generated by the electronic form control unit 531 and the workflow unit is generated by the workflow control unit 532, and the electronic form control unit 531 and the workflow control unit 532 exchange data. Basically, the electronic form definition 551, the item logic instruction definition 552, and the workflow process definition 553, which are separately developed, are used separately, and an appropriate screen display is performed according to the workflow process definition 553. Can do.
[0068]
Although the embodiment of the present invention has been described above, the present invention is not limited to this. For example, the definition data format registered in the definition information DB 55 is not limited to the format described above, but may be registered in other formats including similar data or additional data. Also, the functional block division in the workflow processing system 5 is an example, and the program module may not be created as illustrated. In particular, the workflow control unit 532 and the workflow data processing unit 534 may be created as one module.
[0069]
In addition, although the configuration in which the return value from the action component 57 is notified from the electronic form control unit 531 to the workflow control unit 532 is shown, it may be notified directly from the action component 57 to the workflow control unit 532. In that case, if the input data or the like is notified from the event control unit 533, communication between the workflow control unit 532 and the electronic form control unit 531 can be reduced.
[0070]
Furthermore, although the configuration in which the workflow execution control information storage unit 58 is referred to via the workflow control unit 532 and the workflow data processing unit 534 is shown, the electronic form control unit 531 requests the workflow data processing unit 534 directly. It is also possible to adopt such a configuration.
[0071]
(Appendix 1)
A position identifying step for identifying a position that is either a state or a state transition between the states in a workflow process for a specific slip based on data received from a user terminal;
Obtaining slip form data related to the position, and storing the slip form data in a storage device;
A state transition data acquisition step of acquiring state transition data that can be instructed by the user in relation to the specified position based on a workflow definition, and storing the data in a storage device;
A display data generation step for generating and outputting data for electronic form display from at least the form data of the slip, and data for button display from the state transition data; and
And a workflow processing method executed by a computer.
[0072]
(Appendix 2)
A program start step for starting a program specified by at least the state transition and a slip related to the state transition when the specified position is a state transition
Further including
In the display data generation step, the electronic form display data is generated by further using data from the program.
The workflow processing method according to supplementary note 1, wherein:
[0073]
(Appendix 3)
A step of determining execution of the state transition data acquisition step based on data from the program;
The workflow processing method according to appendix 2, further comprising:
[0074]
(Appendix 4)
The slip form data acquisition step includes:
Searching the slip definition information stored in the slip definition information storage unit based on the identified position and identifying the corresponding slip;
Searching the electronic form definition information stored in the electronic form definition information storage unit based on the specified slip and identifying the corresponding form data;
The workflow processing method according to any one of supplementary notes 1 to 3, including:
[0075]
(Appendix 5)
The program starting step includes
The item logic instruction definition information stored in the item logic instruction definition information storage unit is searched based on the state transition as the position and the slip related to the state transition, and the program to be started and the parameters to be output to the program Step to extract data
The workflow processing method according to appendix 2, including:
[0076]
(Appendix 6)
When the predetermined state transition is specified in the position specifying step, the data input to the electronic form related to the state before the transition of the specific state transition and the data related to the transition destination state of the specific state transition, Registering as workflow execution control information;
The workflow processing method according to any one of appendices 1 to 5, further including:
[0077]
(Appendix 7)
The position specifying step includes
When receiving identification data of a specific workflow process from the user terminal, identifying corresponding workflow execution control information based on the identification data of the specific workflow process;
Identifying the current state from the corresponding workflow execution control information;
The workflow processing method according to appendix 6, including:
[0078]
(Appendix 8)
Item 5. The item logic instruction definition information defines a program to be started in correspondence with a slip field related to the state transition and parameter data to be output to the program. Workflow processing method.
[0079]
(Appendix 9)
A position identifying step for identifying a position that is either a state or a state transition between the states in a workflow process for a specific slip based on data received from a user terminal;
Obtaining slip form data related to the position, and storing the slip form data in a storage device;
A state transition data acquisition step of acquiring state transition data that can be instructed by the user in relation to the specified position based on a workflow definition, and storing the data in a storage device;
A display data generation step for generating and outputting data for electronic form display from at least the form data of the slip, and data for button display from the state transition data; and
A program that causes a computer to execute.
[0080]
(Appendix 10)
Based on data received from the user's terminal, a position specifying means for specifying a position that is either a state or a state transition between the states in a workflow process for a specific slip;
Slip form data acquisition means for acquiring slip form data related to the position and storing it in a storage device;
State transition data acquisition means for acquiring state transition data that can be instructed by the user in relation to the specified position based on a workflow definition, and storing the data in a storage device;
Display data generation means for generating and outputting data for electronic form display from at least form data of the slip, and data for button display from the data of the state transition;
A workflow processing apparatus.
[0081]
【The invention's effect】
As described above, the development and maintenance efficiency of the workflow processing system can be improved.
[Brief description of the drawings]
FIG. 1 is a diagram showing functional blocks in an embodiment of the present invention.
FIG. 2 is a diagram for explaining processing in an electronic form designer and a property setting unit.
FIG. 3 is a diagram illustrating an example of an electronic form definition.
FIG. 4 is a diagram illustrating an example of an event definition.
FIG. 5 is a diagram illustrating an example of a business logic component definition.
FIG. 6 is a diagram illustrating an example of an item logic instruction definition.
FIG. 7 is a diagram for explaining processing in a workflow process setting unit.
FIG. 8 is a diagram illustrating an example of a workflow process definition.
FIG. 9 is a diagram illustrating an example of a slip definition.
FIG. 10 is a diagram showing a processing flow at the time of application.
FIG. 11 is a diagram showing a processing flow of draft event processing.
12A is a diagram illustrating an example of an electronic form unit, FIG. 12B is a diagram illustrating an example of a workflow unit, and FIG. 12C is a diagram illustrating an example of a screen display;
FIG. 13 is a diagram showing a processing flow of application event processing;
FIG. 14 is a diagram illustrating an example of workflow execution control information.
FIG. 15 is a diagram showing a processing flow at the time of approval.
FIG. 16 is a diagram showing a process flow of an approval activity start process.
FIG. 17 is a diagram illustrating a processing flow of instruction input event processing;
FIG. 18 is a diagram illustrating a relationship between a workflow and screen transition.
[Explanation of symbols]
1 LAN 3 User terminal 5 Workflow processing system
7 Developer terminal
51 Web server function 53 Voucher container
55 Definition information DB 57 Action parts
58 Workflow execution control information storage
59 Background system
531 Electronic Form Control Unit
532 Workflow control unit
533 event control unit
534 Workflow data processing unit
591 Affiliation master file
593 Employee Master File
595 Various business master files

Claims (4)

Electronic form definition including form data of each slip, slip definition including slip name and state related to the slip, state transition and workflow process identification data, and state transition that can occur in the state and the state A definition information database that stores a workflow process definition including a transition destination state by a transition, a workflow execution control information storage unit that stores workflow execution control information including data indicating a current state in the workflow process, and a storage device A workflow processing method executed by an accessible computer,
When the identification data of a specific workflow process is received from a user terminal, the workflow execution control information storage unit is searched based on the identification data of the specific workflow process, and the workflow corresponding to the specific workflow process When the current state included in the execution control information is specified as a position, or when a predetermined instruction related to a specific slip is received from the user terminal, a state transition corresponding to the predetermined instruction is set as the position. A position identification step to identify;
The slip definition is searched based on the received identification data of the specific workflow process or the slip name of the specific slip related to the received predetermined instruction and the position specified in the position specifying step. identify the documents associated with the position, and acquires the form data of the specified document from the electronic form definition, a slip form data obtaining step of storing in the storage device,
When the position specified in the position specifying step indicates a state, state transition data that can occur in the state is acquired from the workflow process definition and stored in the storage device, or the position When the position specified in the specifying step indicates a state transition, the transition destination state corresponding to the state transition is specified from the workflow process definition, and can occur in the specified transition destination state A state transition data acquisition step of acquiring state transition data from the workflow process definition and storing it in the storage device;
Stored in at least said storage device generates data for electronic form displayed from the form data of the document, stored in said storage device, generates data for button display from the state transition data output Display data generation step to be performed;
Including workflow processing methods. The definition information database further stores an item logic instruction definition including a slip name, state transition, and identification data of a program to be activated;
When the position specified in the position specifying step indicates a state transition, the item logic instruction definition is searched based on at least the state transition and a slip name of a slip related to the state transition, and the state transition A program starting step of specifying the program corresponding to the slip name of the slip related to the state transition and starting the program;
The workflow processing method according to claim 1, wherein, in the display data generation step, the data for displaying the electronic form is generated by further using data from the program. If the position identified in said position identifying step indicates a state transition, the data relating to the destination state of the electronic form to the input data and the state transitions associated with the state before transition of the state transition , the step of registering the workflow execution control information storage unit as the workflow execution control information
The workflow processing method according to claim 1 or 2 , further comprising: Electronic form definition including form data of each slip, slip definition including slip name and state related to the slip, state transition and workflow process identification data, and state transition that can occur in the state and the state A definition information database that stores a workflow process definition including a transition destination state by a transition, a workflow execution control information storage unit that stores workflow execution control information including data indicating a current state in the workflow process, and a storage device On an accessible computer,
When the identification data of a specific workflow process is received from a user terminal, the workflow execution control information storage unit is searched based on the identification data of the specific workflow process, and the workflow corresponding to the specific workflow process When the current state included in the execution control information is specified as a position, or when a predetermined instruction related to a specific slip is received from the user terminal, a state transition corresponding to the predetermined instruction is set as the position. A position identification step to identify;
The slip definition is searched based on the received identification data of the specific workflow process or the slip name of the specific slip related to the received predetermined instruction and the position specified in the position specifying step. identify the documents associated with the position, and acquires the form data of the specified document from the electronic form definition, a slip form data obtaining step of storing in the storage device,
When the position specified in the position specifying step indicates a state, state transition data that can occur in the state is acquired from the workflow process definition and stored in the storage device, or the position When the position specified in the specifying step indicates a state transition, the transition destination state corresponding to the state transition is specified from the workflow process definition, and can occur in the specified transition destination state A state transition data acquisition step of acquiring state transition data from the workflow process definition and storing it in the storage device;
Stored in at least said storage device generates data for electronic form displayed from the form data of the document, stored in said storage device, generates data for button display from the state transition data output Display data generation step to be performed;
It is allowed to run the program.

Images