JP2000251002A - Item processing method of workflow system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable an applicant to speedily and accurately perform an operation process by dividing the event of document creation into two successive parts and informing a document creator which created a document before the event of document creation after the event. SOLUTION: An operation monitor and notification program 111 compares the system date of a server 101 with the event schedule date of event management information 129 inputted by the document creator and informs the document creator of an operation process after the event as to an item whose dates both match each other. An electronic document selecting program 113 generates a list of documents to be created from event document correspondence information 123 on the basis of selected event information sent from a client 103 and transmits it to the client 103 of the applicant. A workflow program 115 controls item transition to a person in charge of operation according to previously defined business process definition information 125 and according to the notification of the input of the item to business processes corresponding to respective documents and the end of operation.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a workflow system for sequentially circulating electronic forms to a worker in accordance with a predefined work flow, and in particular, creates a plurality of different electronic forms at the same event, and To circulate as a separate matter, how to associate the matter with the event and give the work instructions hierarchically to the person in charge of the work after the applicant, and the work after the event to the person who made the bill before the event The present invention relates to a method for automatically performing processing notification.

[0002]

2. Description of the Related Art Nikkei Computer No. 425 (199
7.9.1) As described on pages 204 to 217, the workflow system sequentially transfers an electronic form including a plurality of information items to a worker who performs the next work in accordance with a predetermined transfer order and performs a series of operations. Is a system that performs A set of defined work is called a business process, and each work is called a node. The unit of work passed between the nodes is called a case, and the workflow system manages each case by attaching a case ID, which is a unique identifier. Creating a matter at the first node and starting a business process is called input, and passing a matter to the next node according to the business process is called transition.

In recent years, with the spread of workflows, there are many cases where business forms are digitized and circulated by a workflow system. However, there are a very large number of business forms, and the originator prepares which form when and when. Very difficult to understand. In particular, in the case of indirect operations in a company, there are several hundred types of forms, and the forms to be created differ depending on the status of the originator, and which form should be created when an event such as marriage or moving occurs I do not understand.

Conventionally, in order to solve the above-mentioned problem, information of a form to be created for each event is defined in advance, and an initiator is provided with an interface for selecting an event. When the drafter selects an event, a form list to be created is displayed based on the predefined event and created form information. The applicant selects an electronic form to be created from the list, inputs necessary data to the displayed electronic form, and repeats the process of inputting the input electronic form to a corresponding business process of the workflow.

[0005] By providing a form selection interface based on the above-mentioned events, it is possible to reduce the generation of wrong forms by each event and the inquiries to the related departments in each event.

[0006]

In the above-described conventional technique, when an event occurs, a plurality of forms are generated, and each of the generated forms is input to a corresponding business process as one matter, and circulation is performed. Is going. However, since forms submitted by the same applicant in the same event flow through the business process as independent issues, work instructions from the applicant onward are given to each person in charge as separate issues. As a result, there arises a problem that the work efficiency is reduced.

For example, when Hitachi Taro creates a marriage report, address change report, commuting route change report, etc. upon marriage and circulates each form to the business processing process of the general affairs section, the person in charge of the general affairs section has three forms. Is notified as a separate and independent matter. However, since it is necessary to refer to each other between forms created in the same event, the general affairs section staff searches for the case (form) that Hitachi Taro applied for by marriage from many cases that arrived at him. Processing must be performed. Therefore, in addition to the original business processing of the general affairs section staff, a task of searching for a related matter from a huge number of cases delivered to the user is generated, thereby increasing the work load.

[0008] The work of searching for a related matter in consideration of the relevance between cases as described above occurs in all of the workers in charge after the person who created the form, and the work load in the overall business processing increases. Also, since the form to be created differs depending on the status of the originator even in the same event, it is not clear whether all the forms transferred to the worker or some of the forms remain in the processing node of the previous worker. The problem that disappears occurs.

Further, in the prior art, a means for a drafter to select an event by his / her own judgment and to automatically narrow down and display a created form is provided. In many cases, business forms are created before and after an event, and according to the above-described method, all forms before and after an event must be made by human judgment. For example, as an example of the above-mentioned marriage, a company housing application form, a notice of address change, a notice of a change in commuting route, etc. are created before marriage, and a notice of marriage, a report of occurrence of dependents, etc. are created after marriage. It is necessary for the applicant to submit the application documents at his own discretion even after the event of marriage, but in practice it often happens that the applicant forgets to submit the application after the event or is late for the application. Business processing cannot be performed.

[0010] An object of the present invention is to divide a form creation event into preceding and following timings, and notify the initiator who drafted the form before the event after the event has occurred, thereby notifying the applicant of the creation of the form quickly and quickly. An object of the present invention is to provide a system capable of performing business operations accurately.

Another object of the present invention is to provide a system in which, when a plurality of forms are created at the same event and at the same timing and circulated by a workflow system, the work performed by the person who creates the form based on the relationship between the plurality of forms by the event. It is an object of the present invention to provide a system in which a work instruction is given to a person in charge, thereby reducing the work load of the person in charge and improving the work efficiency.

[0012]

SUMMARY OF THE INVENTION The present invention provides an interface that allows a person who creates an electronic form to select a form based on timing before and after each event. When the drafter selects and raises the timing before the event, it acquires and stores the scheduled event occurrence date and applicant information. The system compares the stored scheduled event date to the current time at regular intervals,
When the scheduled date of the event is reached, notify the applicant of the work so that the business process after the event can be performed.

When a drafter creates a form by selecting an event, an electronic form information created for each event to be raised and applicant information, and business process information and case information in each electronic form are transmitted from a workflow system. By acquiring, storing, and managing, the related information between the created forms for each event is held and managed. When a worker in charge after the drafter accesses the workflow, the matter in which a plurality of electronic forms are created is extracted from the matter delivered to the worker.

Based on the events stored at the time of drafting, the electronic form creation information for each drafting person, and the workflow system management information for each electronic form, the extracted information is sent to the worker in charge of the event information for each event. Display and give work instructions. When the worker selects a work instruction for each event,
For the case in which all the forms to be processed in the selected case have arrived, a work instruction for the case for each electronic form is displayed based on the created form information for each event.

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a configuration diagram of a system showing an outline of a workflow system according to an embodiment.

The present system includes a workflow server 10
1. It is composed of a client 103 used by an operator and a network 109 connecting these devices.

The work management server 101 is a computer such as a server dedicated machine or a personal computer. The work management server 101 stores a work monitoring / notification program 111, an electronic form selection program 113, a workflow program 115, and a communication control program 117. Be executed.

The work monitoring / notification program 111 compares the system date of the server 101 with the scheduled event date of the event management information 129 input by the drafting party, and sends a message to the drafting party for an item whose two dates match. Notification of business process after event.

The electronic form selection program 113 creates a list of forms to be created from the event form correspondence information 123 based on the selected event information transmitted from the client 103 and transmits the list to the client 103 of the applicant. Further, it receives the created form information selected from the client 103 and stores the corresponding electronic form file 109 and electronic form data storage table 121 in the client 103.
Send to

The workflow program 115 controls the transition of a case to the next worker based on the business process definition information defined in advance and the input of the case to the business process corresponding to each form and the notification of the end of the work.

The communication control program 117 controls data communication between the workflow server and the client.

An electronic form file 119, an electronic form data storage table 121, and an event form correspondence information 1 are stored in a storage device connected to the processing device of the work management server 101.
23, business process definition information 125, workflow management information 127, event management information 129, and event-based draft management information 131.

The electronic form file 119 is a file in which a form including a plurality of items required for business is defined and registered in advance.

The electronic form data storage table 121 is a database file for storing data input to the electronic form file 119.

The event form correspondence information 123 stores a form name to be created for each event that indicates an event that can be a trigger for making a form.

The business process definition information 125 stores the order of each work in a series of work defined as a business process, an operator, work contents, and the like.

The workflow management information 127 includes a business process name to be executed based on the business process definition information registered in the business process definition information 125,
Information on the current status of a case in a workflow such as a business process ID, a node name for processing the current case, and a worker of the processing node is stored.

The event management information 129 stores event information, such as an event name, an applicant name, an application date, and a scheduled event date, in order to manage an event for which a request has been made.

The event-based form management information 131 includes information such as a business process ID, a business process name, a case ID, and a created form name for managing management information for a form created for each event and a workflow of each form. Is stored.

The client 103 is a computer such as a personal computer, and includes a processing device, a display device 105 for displaying a processing result to the applicant, and an input device 10 for the applicant to input data.
7. The processing device of the client 103 includes:
It comprises a communication control program 133, a workflow client program 135, an event guidance drafting program 137, and an inbox display program 139.

The communication control program 133 controls communication of data between the workflow server and the client.

Workflow client program 13
Reference numeral 5 denotes a client that obtains information on a case from the server 101 and passes it to the inbox display program 139 or passes user information for performing a business process to the work management program 115 of the server 101, notification of the end of the business process, and delivery of the business process result. This is a program for controlling data exchange between the server 103 and the server 101.

The inbox display program 139 uses the workflow management information 1 based on the logged-in user ID.
27. Control is performed to acquire the case reached to the user concerned and display the case in charge of the worker.

FIG. 2 is a data configuration diagram of the workflow management information 127.

The workflow management information 127 is a table for managing the current processing status of an item in a predefined business process of the workflow system.
It comprises a PID 200, a BP name 210, a case ID 220, a processing node name 230, a person in charge 240, and a multiple form flag 250.

The BPID 200 is an identifier automatically assigned by the workflow program 115 of the workflow server 101 to uniquely identify a business process.

The BP name 210 is the name of a business process defined in advance.

The case ID 220 is used by the workflow server 10 to uniquely identify a case in each business process.
An identifier automatically assigned by one workflow program 115, and is uniquely assigned to each business process.

The processing node name 230 is the name of the processing node that should be currently processed on the business process in each case.

The person in charge 240 is the name of the person in charge who is to process each case at present, and the workflow program 115 determines and registers the person in charge based on the business process definition information 125 defined in advance.

The multiple form flag 250 is a flag indicating that a plurality of forms have been created from one event and each form has been input to the workflow as a separate matter. The case indicates that the form is managed by the workflow system as a plurality of matters.

FIG. 3 is a data configuration diagram of the event management information 129.

The event management information 129 is a table for storing information related to the raised event, and includes an event name 300, an applicant name 310, an application date 320, an application ID
330, scheduled event date 340, form synchronization flag 350
Consists of

The event name 300 is the name of the event selected by the drafter for drafting.

The applicant name 310 is the name of a drafter who has selected an event and made a draft.

The application date 320 is the date on which the drafter creates a form based on an event and submits it to the workflow system.

The application ID 330 is an identifier for uniquely identifying the event that created the form by the drafter, and is automatically given by the electronic form selection program 113.

The scheduled event date 340 is a scheduled date on which an event serving as a trigger for drafting will occur, and is input and stored only when the drafter selects the timing before the event.

The form synchronization flag 350 is a flag indicating whether the form to be processed by the worker has arrived at the work node in charge among a plurality of forms created by the same event. "1" indicates that the report has arrived
In the case of, it means that all the forms to be processed have not yet arrived.

FIG. 4 is a data configuration diagram of the event-based slip management information 131.

The event-based form management information 131 is a table for storing a form name and workflow information for each form created for each event in which the form is generated.
It is composed of a BPID 410, a BP name 420, a case ID 430, and a created form name 440.

The application ID 400 is an identifier for uniquely identifying an event for which a drafter has created a form, and is a key representing the association between the event of the event management information 129 and the form created for each event.

The BPID 410 is an identifier for identifying a business process in which the corresponding form is circulated.

The BP name 420 is the name of the business process in which the corresponding form is circulated.

The case ID 430 is an identifier for uniquely identifying the corresponding form on the business process in which the form is circulated.

The created form name 440 is the name of a form created for each event.

FIG. 5 shows the display device 105 by the event guidance drafting program 137 of the client 103.
Is an example of an event menu screen displayed by the drafter, in which the drafter selects a draft event in order to narrow down the created forms.

The event name 510 is an event that is a trigger for a draft.

The timing 520 indicates the timing in each event, and the timing is selected by pressing the "before" and "after" buttons. When the “end” button 530 is pressed for the selected event and timing, the information is transmitted to the server.

FIG. 6 is an example of an expected event date input screen displayed when “Previous” is selected as the event timing on the event menu screen 500.

The scheduled date 610 is the date of the event (year, month,
This is an input area for inputting the date.

The drafter inputs the scheduled date, and presses an “OK” button 620, so that the event scheduled date server 101
And stores it in the event management information 129. If the drafter presses the "cancel" button 630, the screen returns to the event menu screen 500 without storing the input information.

FIG. 7 shows a created form in which, after selecting an event or inputting a scheduled event date, a form list corresponding to the event narrowed down by the electronic form selection program 113 of the server 101 is displayed on the display device 105 of the client 103. This is an example of a list screen, and a drafter creates a form by selecting a form displayed in the form list.

The event 710 is a display area for displaying the event name selected by the drafter.

The form name 720 is a cover area indicating the form name extracted according to the selected event and timing.

The creation presence / absence 730 is an area for displaying information indicating whether or not the displayed form has been generated.

The drafter is the form name 7 created from the form list.
When the user selects “20” and presses a “Create” button 740, the selected form name is transmitted to the server 101. The electronic form selection program 113 of the server 101 sends the electronic form file 119 corresponding to the received form name and the electronic form data storage table 121 to the client 103.

When the drafter presses the "apply" button 750,
A form in which the creation status 740 is set to “completed” is subjected to input processing into a business process defined in advance for each form. If the drafter presses a "cancel" button 760, the processing so far is invalidated and the screen returns to the event menu screen 800.

FIG. 8 is an example of a screen for displaying the cases reached to each worker when the worker after the drafter starts the inbox display program 139 and accesses the workflow. Starts an electronic form or business application from the matter list displayed in the inbox and performs work.

The case name 810 is the title of the case to indicate the outline of the case to be processed by the worker, and displays the event name in the case of the case generated by the event.

The applicant 820 is the name of the user who has submitted the business processing matter, and is the drafter of the form.

The application date 830 is the date when the form was created by the drafter and entered into the workflow system.

The lower work 840 is a flag indicating that a plurality of forms are created in one event and a plurality of cases are processed, and is displayed based on the plurality of forms flag 250 of the workflow management information 127.

The worker is in the lower work column 840 with “Yes”.
Is selected and the "Lower display" button 850 is displayed.
By pressing, the lower-level work display screen 900 is displayed only for the case for which the lower-order form has reached all the processing nodes of the worker.

After the worker selects a matter and ends the matter processing, selects the completed matter and presses a “transition” button 860 to move the selected matter to the next worker defined in advance. Transition to.

After the worker in charge selects a case and completes the case processing, selects the completed case and presses a “return” button 860 to shift the selected case to the previous work processor.

When the worker presses an “end” button 880, the work is completed and the inbox screen 800 is closed.

FIG. 9 is an example of a lower-level work list screen displayed when a “Yes” item is selected in the lower-level work field 840 of the inbox screen 800 and the “Lower-level display” button 851 is pressed. It is a screen for displaying a list of forms to be processed every time.

The case name 910 is the name of the event that generated the case to be processed.

The applicant 920 is the name of a user who has issued a plurality of forms displayed in a list by an event and has entered each form into the workflow.

The form name 930 is the name of the form to be processed by the worker for each event.

The processing presence / absence 940 is a flag indicating that the form has been opened and the form has been processed.

When the worker in charge selects the form name 930 and presses the “open” button 950, the selected form is displayed on the display device 105 of the client 103.

When the worker finishes the work and presses the “end” button 960, the lower work list screen 900 is closed and the screen of the inbox 800 is displayed.

FIG. 10 shows a case where a “Yes” item is selected in the lower work field 840 of the inbox screen 800 and the “Lower display” button 850 is pressed. It is an example of a non-arrival form notification screen displayed when all the electronic forms to be processed have not reached the processing node.

The message 1010 is the content of a notification notifying that there is a non-arrival form.

When the operator touches the “end” button 1020 after reading the message, the non-arrival form notification message screen 1000 is closed and the inbox screen 800 is displayed.

FIG. 11 shows the event guidance program 1.
37 is a flowchart showing the flow of a form drafting process performed by a form 37.

When the drafter activates the event guidance drafting program 137 of the client 103 and performs a login process, an event menu screen 500 is displayed on the display device 105 of the client (step 1100).
The drafter selects a corresponding event and a button of the timing from the displayed event menu screen 500.

If the timing of the selected event is “before” the event (step 1105), an event scheduled date input screen 600 is displayed. After inputting the scheduled date (year, month, day) on the displayed scheduled event date input screen 600, the user presses an “OK” button 620 (step 111).
0), the event guidance drafting program 137 sends the logged-in user name, the input event name, the scheduled event date, and the application date to the server 101 (step 1).
115).

If the timing of the selected event is “after” the event (step 1105), the event guidance drafting program 137 transmits the logged-in user name, the input event name, and the application date to the server 101 (step 1105). Step 1115).

When the electronic form selection program 113 of the workflow server 101 receives the data transmitted from the client 103, it assigns an application ID and stores it in the event management information 129 (step 1120).
At the same time, event form correspondence information 1 based on the event name
23, the form name to be created is acquired and transmitted to the client 103 together with the application ID (step 1125).

The event guidance drafting program 137 of the client 103 displays the created form list screen 700 on the display device 105 of the client based on the form name transmitted from the server 101 (step 1130).

When the drafter selects the form name 720 to be created from the created form list screen 700 and presses the "Create" button 740, the event guidance drafting program 137 sends the selected form name to the server 101 (step). 113
5).

The server 101 receives the form name transmitted from the client 103, retrieves the corresponding electronic form file 119 and electronic form data storage table 121 from the storage device, and transmits them to the client 103 (step 1140).

The client 103 sends the electronic form file 119 and the electronic form data storage table 1 from the server 101.
21 is received and the electronic form is displayed on the display device 105 (step 1145).

The drafter inputs necessary data into the displayed electronic form, and performs input termination processing (step 115).
0), the input form data is stored in the electronic form storage table, and then the created form list screen 700 is displayed, and the presence / absence 730 is updated to “done” (step 1155).

FIG. 12 shows the event guidance program 1.
37 is a flowchart showing the flow of inputting a created form to the workflow system after the form has been created by 37.

When all the forms displayed in the created form list 700 have been completed, the applicant presses the “apply” button 750 on the created form list 700 (step 1200).

The workflow client program 135 of the client 103 acquires the business process name to be entered from each electronic form file, and stores the electronic form data storage table, the business process name, and the application ID in the server 10.
1 (step 1205).

Workflow program 1 of server 101
Reference numeral 15 inputs the electronic form data storage table to the corresponding business process defined in the business process definition information 125 based on the business process name for each form transmitted from the client 103, and generates a case. After the case is generated, information such as the ID of the generated case and the corresponding business process ID, business process name, next work node, person in charge is acquired (step 1210).
7 (step 1215), and at the same time, the value of the plural form flag 250 of the work management information 127 is changed from 0 to 1.
Is updated (step 1220).

Also, the application ID, form name, business process ID, business process name, and case ID obtained in step 1210 transmitted from the client are stored in the event-based form management information 131 (step 122).
5).

The above steps 1210 to 12
Steps 25 through 25 are performed for a plurality of all forms received from the client 103 (step 1230).

The work management information 127 for all forms
When the registration in the event-based invoice management information 131 is completed, a message indicating that the processing has been completed is transmitted to the client 103 (step 1235).

The client 103 receives the processing completion message from the server, closes the created form list screen 700, and displays the event menu screen 500 (step 1240).

FIG. 13 is a flow chart showing a flow in which a person in charge of work after the drafter opens a case reached by himself using the inbox display program 139 and performs work.

The person in charge of the work after the drafter is the client 1
When the inbox display program 139 is activated and the login process is performed (step 1300), the user information acquired by the login is transmitted to the server 101 (step 1305).

The server 101 receives the user information transmitted from the client 103, and searches for the person in charge 240 in the workflow management information 127 (step 1).
310). As a result of the search, if there is a case that matches the transmitted user name (step 1315), it is determined whether the value of the multiple form flag 250 of the matching record is “1” or “0” (step 1355).

If the result of the determination is “1”, the business process ID 200, business process name 210, and matter ID 220 of the corresponding record are obtained (step 136).
0).

Using the acquired business process ID 200 and case ID 220 as keys,
1 is searched, and the business process ID 200 and the case I
The application ID 400 of the case where D220 matches is acquired (step 1365).

Based on the obtained application ID, the related form is synchronized (step 1370).

After the related form synchronization processing is completed, the acquired application ID 400 is used as a key and the event management information 129 is set.
Is retrieved (step 1375), and the event name, applicant name, and application date of the record having the same application ID are obtained (step 1380).

As a result of the determination in step 1355, if the value of the plural form flag 250 of the work management information 127 is “0”, a record in which the user 240 transmitted from the client 103 matches the person 240 in charge of the work management information 127. Information corresponding to the matter is obtained from (Step 138)
5).

User I sent from client
The search of the workflow management information 127 using D as a key is performed up to the last record of the work management information 127. When the search of all records is completed (step 1315), the case information and the application ID acquired by the search are transmitted to the client 103 (step 1315). Step 1320).

The client 103 acquires the case information from the server 101 and displays the inbox screen 8 on the display device 105.
00 is displayed (step 1325).

The worker selects a case to be processed from the cases displayed on the inbox screen 800. If the selected matter is “present” in the display field of the lower-level work 840, when the worker presses the “lower-level work” button 850, the acquired application ID is transmitted to the server 101 (step 133).
0).

The server 101 receives the application ID transmitted from the client 103 and receives the received application ID.
Is used as a key, and the application ID of the event-based draft management information 131
400 are searched (step 1335).

[0119] Event-based invoicing management information 1 by application ID
As a result of the inspection at 31, it is determined whether the form synchronization flag 350 of the record with the matching application ID is “1” or “0” (step 1340).

If the result of the determination is "0", the business process ID 410, business process name 420, and creation form name 440 of the record with the matching application ID are obtained and transmitted to the client 103 (step 1345).

The client 103 sends the business process ID, business process name,
The work form name is received, and a lower-level work display screen 900 is displayed on the display device 105 of the client 103 (step 1350).

If the form synchronization flag is "1" as a result of the determination in step 1340, a non-arrival form notification message 1000 notifying that all forms to be processed have not arrived.
Is transmitted to the client 103 and displayed (step 1).
390).

When the worker presses the “end” button 1100 on the non-arrival form notification message screen 1000, an inbox screen 800 is displayed.

FIG. 14 is a flowchart showing a flow for confirming whether all the forms to be processed by the worker have arrived at the processing node of the worker in the plurality of forms generated in the same event. FIG. 14 is a flowchart illustrating in detail the “related form synchronization process” (step 1370) in the flowchart of FIG.

Step 1360 in the flowchart of FIG.
Based on the application ID acquired from, a search is made of the event management information 131 for each event, and a form having the same application ID is searched (step 1400).

As a result of the search, when there is a form having the same application ID (step 1405), the business process ID 410, business process name 420, and matter ID 430 of the record having the same application ID are obtained (step 141).
0).

Obtained business process ID and case ID
Is used as a key, the workflow management information 127 is searched, and the processing node name 230 of the record in which the business process ID and the case ID match is obtained (step 1415).

At the same time, the business process definition information 125
To obtain business process definition information having the same business process ID and business process name (step 1420), and determine whether there is a work node in which the user who has logged in is defined as a worker in the business process. Is performed (step 1425).

As a result of the judgment, if there is a work node in which the login user is defined (step 1430), the process node obtained in step 1415 is compared with the work node obtained from the business process definition information, and the workflow management information 127 It is determined whether the processing node 230 is a node before the work node (step 1435).

If the result of determination is that the processing node is earlier than the work node on the business process (step 1440),
The form synchronization flag 360 of the event management information 129 is updated to “1”, and the next record search of the event-based form management information 131 is performed using the application ID as a key (step 1).
450).

As a result, the event management information 1 is set for the case in which all the reports have not reached the processing node of the worker.
A flag can be set in the 29 form synchronization flag 350.

FIG. 15 is a flowchart showing the flow of issuing a post-event notice based on the input scheduled event date.

The work monitoring / notification program 111 of the server 101 is started by a timer at a fixed time, such as 0:00 every day, and acquires the system time of the server 101 (step 1500).

The work monitoring / notification program 111 searches the event management information 129 for the scheduled event date 340, and compares the date acquired from the system with the scheduled event date 340 (step 1505). As a result of the search of the event management information 129, if the event date matches the date acquired from the system (step 1510), the applicant name and the event name of the matching record of the event management information 129 are acquired (step 1515).

Based on the acquired event name, a notification message such as "Please do the procedure after marriage" is created (step 1520), and the created notification message is sent to the applicant obtained in step 1515. (Step 1525).

[0136]

As described above, according to the present invention, an interface for issuing an event at a timing before and after the event is provided, and a post-event business process is performed for the person who created the event on the input scheduled event date. By providing a mechanism for notifying such a task, a drafter can prevent forgetting work after an event or delay of drafting work in advance, and can perform the work quickly and accurately.

Further, when a plurality of forms are created by the same event and each created form is circulated as one matter by the workflow system, the related information between the plurality of forms created by the same event and by the same originator is used. By providing a mechanism to perform hierarchical work instructions based on the information related to each matter (form) to the person in charge after the issuer, and by synchronizing the related forms, the worker Can reduce the load of searching for a related matter from many cases that have arrived, and can improve the efficiency of business processing.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram illustrating a workflow system according to an embodiment.

FIG. 2 is a data configuration diagram of workflow management information 127 according to the embodiment.

FIG. 3 is a data configuration diagram of event management information 129 according to the embodiment.

FIG. 4 is a data configuration diagram of event-based invoice management information 131 according to the embodiment;

FIG. 5 is an event menu screen for the drafter to select an event to narrow down a created form.

FIG. 6 is an event scheduled date input screen for inputting an event scheduled date when a draft is issued at a timing before an event.

FIG. 7 is a creation form list screen that displays a form to be created by an event in order to create a form after a drafter selects an event.

FIG. 8 is an inbox screen for a worker to notify a matter to be processed.

FIG. 9 is a lower-level work display screen for displaying a plurality of lower-level cases for each case when a plurality of forms exist in the case delivered to the worker in charge.

FIG. 10 is a non-arrival form notification screen for notifying that all the forms to be processed by the business clerk have not been received as lower-level cases when a plurality of forms exist in the case delivered to the worker.

FIG. 11 is a flowchart illustrating a flow of processing in which a drafter starts an event guidance program to create a form.

FIG. 12 is a flowchart showing a flow of a process in which a drafting person creates all forms by an event guidance program and then inputs the created forms to a workflow system.

FIG. 13 is a flowchart showing a flow of a process in which a worker in charge after the drafter opens a case that has arrived by the inbox display program and performs work.

FIG. 14 is a flowchart showing a processing flow for confirming whether all of the forms to be processed by the worker have arrived at the processing node of the worker in the plurality of forms generated by the same event.

FIG. 15 is a flowchart showing the flow of a process for issuing a post-event notice based on an input scheduled event date.

[Explanation of symbols]

101: Workflow server, 103: Client,
105 client display device, 107 client input device, 109 network, 111 work monitoring / notification program, 113 electronic form selection program, 115 workflow system, 117 communication control program, 119 electronic form file, 121: electronic form data storage table, 123: event form correspondence information, 125: business process definition information, 127: workflow management information, 129: event management information, 131
... Event management information for each event 133 Communication control program 135 Workflow client program 1
37: Event guidance drafting program, 139: Inbox display program

 ──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Tomokazu Igata 890 Kashimada, Saiwai-ku, Kawasaki-shi, Kanagawa Prefecture Inside the Hitachi, Ltd.System Development Division (72) Yoshihide Omura 890 Kashimada, Sai-ku, Kawasaki-shi, Kanagawa 5B089 GB03 JA16 KA13 KB11 KC11 KC30 KC53

Claims (5)

[Claims] 1. A workflow system for executing a job by sequentially circulating an electronic form including a plurality of information items to a next worker in accordance with a predefined business flow (hereinafter, referred to as a business process). When a plurality of electronic forms are created and circulated to a workflow system, the same event, the same creation timing, and business processing can be used as a trigger (hereinafter referred to as an event) for a drafter to create an electronic form. A case processing method in a workflow system, characterized by associating a plurality of forms based on the above relationship so that a worker can refer to and process related forms as one business processing unit. 2. A system according to claim 1, wherein an event for issuing an electronic form, electronic form information created for each applicant, and case information for each electronic form managed by a workflow system are stored and managed. A method of processing a case in a workflow system, wherein a plurality of electronic forms generated by the same applicant at the same event are related in business and managed. 3. In the system according to claim 1, when a plurality of electronic forms are created at the same event and at the same timing when a work instruction is given to a worker, related information between the events and the forms is provided. A case processing method in a workflow system, comprising: synchronizing a plurality of reports assigned to a worker who performs login and processing based on each event. 4. In the system of invoice 1, when a plurality of electronic forms are created in one event when a work instruction is given to a worker, the electronic form information created for each event and Based on the case information on the workflow system in the electronic form, the work instruction is given to the worker in charge of the information for each event, and then the work instruction for the case for each electronic form to be processed for each event is given. A case processing method in a workflow system, in which a work instruction is given in a hierarchical manner. 5. The system according to claim 1, wherein an electronic form invoicing person stores the scheduled event occurrence date and the applicant information in the invoicing before the event by an interface capable of selecting a form according to timing before and after each event, A case processing method in a workflow system, which automatically notifies a drafter of a business process on a scheduled event date by comparing a stored scheduled event date with a current time at regular intervals.