JP2012141958A - Information processor, information processing method, information processing system, program, and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a work flow system capable of allowing a user who approves a succeeding activity to urge a user who approves a preceding activity in the flow of work flow processing.SOLUTION: An information processor includes: first case extraction means for extracting cases including an activity to be scheduled to be processed by a first user, in response to a request from the first user; first selection reception means for receiving the selection of a case to urge a second user who processes the succeeding activity of the activity to be processed by the first user among the cases extracted by the first case extraction means; and first urging means for urging the second user, who has to process the activity of the case before the activity to be processed by the first user, to process the activity of the case concerning the case whose selection is received by the first selection reception means.

Description

  The present invention relates to a technique that makes it possible to reduce time spent for completion of a process in a workflow system.

  In the workflow system, a new process is created by creating a new application.

  In this process, a workflow process flows by receiving approval from an approver on a route designed in advance, and finally the process ends.

  Here, conventionally, there has been a problem that the flow of workflow processing is stagnated due to a state in which the approver on the route waits for approval.

  On the other hand, for example, Patent Document 1 discloses a technique for automatically or manually skipping a stagnation in a workflow at the time of execution of the workflow, and a person in charge who is skipped in the middle of the workflow eventually has its process. Techniques that can participate in are disclosed.

JP 2002-254214 A

  However, as in the technique described in Patent Document 1, in the method of skipping and finally participating in the process, the order in which the user participates in the process changes, so that the intended decision-making procedure is not performed. Problems will arise. Therefore, there is a need for a method that shortens the time spent completing a process without changing the order in which the user participates in the process.

  By the way, in the case of staying waiting for processing, the approver often forgets the operation itself. Therefore, if a stagnating activity can be urged from the approver behind the workflow processing flow to the approver of the stagnant activity, for example, without changing the order in which the user participates in the process, It is possible to reduce the time spent for completing the process. On the other hand, if the applicant or approver can prompt the approver behind him to advance this process quickly, the process can be completed without changing the order in which the user participates in the process. It is possible to reduce the time spent on the process.

  Accordingly, the present invention solves the above-described problem, and provides a workflow system that can prompt a user who approves a previous activity from a user who approves a subsequent activity in the workflow processing flow. The purpose is to do.

  The present invention is an information processing apparatus that performs workflow processing for an applied item, and includes an item that includes an activity that the first user is scheduled to process in response to a request from the first user A first case extracting means for extracting a message and a second user who processes an activity before the activity processed by the first user from the cases extracted by the first case extracting means. A first selection receiving unit that receives a selection of a case to be processed, and a case that has been selected by the first selection receiving unit, and processes the activity of the case before the activity that the first user processes And a first prompting means for prompting the second user to process the activity of the matter. And features.

  According to the present invention, it is possible to provide a workflow system capable of prompting a user who approves a previous activity from a user who approves a back activity in the workflow processing flow.

Diagram showing schematic configuration of workflow system Block diagram showing an example of a hardware configuration of a computer Diagram showing the relationship between activities and transitions Diagram showing an example of activity and transition when there is a branch The figure which shows an example of the table which comprises organization information Specific examples of organization information Figure showing the relationship between definition information and job information Data table showing an example of definition information Diagram showing examples of work items Data table showing an example of job information Flow of processing in the workflow system when applying Flowchart for acquiring work that can be applied in the workflow server Example of displaying the work that can be applied and acquired by the workflow server on the display device of the workflow operation terminal Example of a screen for selecting a role Application screen example Process flow in workflow system when re-applying, approving, sending back, or rejecting Flowchart for obtaining a processing wait list in the workflow server Sample screen for waiting for processing Example of Item details screen Flow of processing in the workflow system when reminding from before Process flow in workflow system when reminding from behind Flow chart showing the flow of delivery processing in the workflow system Flowchart showing the flow of processing for obtaining the next user execution activity in the workflow server Detailed process flow for creating a work item to be processed Process flow for seeking the person concerned Process flow for requesting persons in department & role Process flow for creating a scheduled work item Process flow for sending approval request email Flow of reminder process Screen to select the user to be prompted A diagram showing specific examples of various project lists An example of a screen that prompts you for the selected project Process flow in other workflow systems Example of matter selection screen

  Hereinafter, details of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram showing a schematic configuration of a workflow system to which this embodiment is applied.

  A workflow system according to the embodiment includes a workflow and slip design computer terminal (workflow and slip design terminal) 400, and a workflow operation computer terminal (workflow operation terminal) provided corresponding to a processor (person in charge) who performs a task. A terminal) 300, various tables for executing a workflow, and a workflow server (information processing apparatus) 200 for storing various programs.

  The workflow and slip design terminal 400, the workflow operation terminal 300, and the workflow server 200 are each connected to a network 500 and operated.

  The workflow and slip design terminal 400 includes a slip designer program 401 and a system management program 402, and creates a slip definition used in the workflow system and various definition information used in the workflow system. For example, the workflow and slip design terminal 400 can register a department table, a business table, and the like in the workflow server 200. In order to perform these operations, the workflow and slip design terminal 400 can connect to the workflow server 200 by inputting its own identification information.

  The workflow operation terminal 300 uses the Web browser 301 executed on the workflow operation terminal 300 to transmit access information regarding the slip to the workflow server 200 by HTTP, and receives the result. At this time, the generated display / calculation processing is executed by using a Java (registered trademark) applet 302 or the like. The workflow operation terminal 300 is arranged for a person in charge (for example, a drafter, a section manager, a department manager, etc.) who performs a predetermined job specified in advance.

  The workflow server 200 includes an RDBMS (Relational DataBase Management System) 205 that stores information related to the workflow system (organization information in FIG. 5 described later), various slip information (definition information and job information in FIG. 7 described later), a workflow operation terminal. An HTTP server 201 for receiving a request from 300 and executing the request, a servlet engine 202, a workflow program 203, and an SMTP server 204 for realizing a workflow notification function.

  Hereinafter, a hardware configuration of a computer applicable to the workflow server 200, the workflow operation terminal 300, the workflow and slip design terminal 400 illustrated in FIG. 1 will be described with reference to FIG.

  FIG. 2 is a block diagram showing an example of a hardware configuration of a computer applicable to the workflow server 200, the workflow operation terminal 300, the workflow and slip design terminal 400 shown in FIG.

  In FIG. 2, reference numeral 101 denotes a CPU, which is stored in a ROM 103 or a hard disk (HD) 104 (any other storage device such as a flexible disk, CD-ROM, DVD-ROM, etc.) 104. The entire computer is controlled by loading the program onto the RAM 102 and executing it. The RAM 102 is used as a work area for the CPU 101.

  A communication interface 108 enables connection to the communication network 500. An input device 106 corresponds to a pointing device such as a keyboard or a mouse. Reference numeral 107 denotes a display device, which includes a CRT, an LCD, and the like.

  Note that the RDBMS 205 of the workflow server 200 illustrated in FIG. 1 is built in the HD 104 of the workflow server 200. Further, the HTTP server 201, the servlet engine 202, the workflow program 203, and the SMTP server 204 of the workflow server 200 are realized by the CPU 101 of the workflow server 200 loading and executing a program stored in the HD 104 on the RAM 102. The

  Further, the Web browser 301 of the workflow operation terminal 300 shown in FIG. 1 is realized by the CPU 101 of the workflow operation terminal 300 loading and executing a program stored in the HD 104 on the RAM 102.

  Further, the Java (registered trademark) applet 302 of the workflow operation terminal 300 shown in FIG. 1 is executed by the CPU 101 of the workflow operation terminal 300 executing the program downloaded from the workflow server 200 on the Web browser 301. Realized.

  In addition, the slip designer program 401 and the system management program 402 of the workflow and slip design terminal 400 shown in FIG. 1 are loaded into the RAM 102 by the CPU 101 of the workflow and slip design terminal 400 by loading a program stored in the HD 104. It is realized by executing.

  FIG. 3 is a diagram illustrating the relationship between activities and transitions.

  An activity refers to a process that constitutes a workflow. A transition defines the order of processing between activities.

  In the example of FIG. 3, there are an application activity 301, user execution activities 302 to 304, and an end activity 305 as activities. The order of each activity is defined by transitions 306 to 309.

  FIG. 4 is a diagram illustrating an example of an activity and a transition when there is a branch.

  The order of the application activity 401 and the conditional branch activity 402 is defined by a transition.

  In this example, as conditional expressions for conditional branching, the branch is made when the application amount is less than 300,000 yen and when the application amount is 300,000 yen or more.

  When the application amount is less than 300,000 yen, the transition is continued to the user execution activity 403, and further the order is followed to the user execution activity 404. On the other hand, when the application amount is 300,000 yen or more, the transition continues to the user execution activity 405 and the order is further traced to the user execution activity 406.

  Then, the user execution activity 404 and the user execution activity 406 merge at a merge activity 407.

  Thereafter, the process ends in the order of the user execution activity 408 and the end activity 409.

  In the workflow system in the present embodiment, conditional branching is determined at the time of new application.

  FIG. 5 is a diagram illustrating an example of a table constituting organization information.

  The organization information includes a department table 501, a roll table 502, a user table 503, and a position table 504.

  The department 501 includes (department ID, department name, level number, parent department ID). The role 502 includes (role ID, role name). The user 503 includes (user ID, name, email address, password). The position 504 includes (user ID, role ID, department ID). A position refers to a group of roles and departments to which a user belongs.

  FIG. 6 shows a specific example of organization information.

  A specific example of each table of organization information and an example of charting it as an organization chart are shown.

  In this example, as shown in the department table 601, there are organizations of “Kannon Co., Ltd.”, “Sales Department”, “Management Department”, “Sales Section 1”, and “Sales Section 2”. In addition, as shown in the user table 603, there are users named “Kannon Taro”, “Kannon Hanako”, “Kannon Kintaro”, and “Kannon Jiro”. “Accounting charge” (from the roll table 602 and the position table 604).

  FIG. 7 is a diagram illustrating the relationship between definition information and job information.

  The definition information 71 is information that defines the work in the workflow, and is defined in advance by the designer. Note that “1” and “*” in the figure indicate a one-to-many relationship.

A process 712, a form 713, a unit 714, and a schema 715 are associated with the business 711. An activity 716 and a transition 717 are associated with the process 712. Further, the job information 72 is associated with the item 721.
The job information 72 is definition information related to a job drafted in the workflow. A work item 722, input contents 723, and a reminder 724 are associated with the case 721.

  Note that the definition information 71 is conventional. Further, in the job information 72, the case 721, the work item 722, and the input content 723 are conventional, but the reminder 724 is a definition newly added to implement the present invention.

  FIG. 8 is a data table showing an example of definition information.

  This definition information is based on the example of the organization information in FIG.

  In the business 81, a business ID and a business name are defined. In this example, “GID001” is defined as the business ID and “purchase application” is defined as the business name.

  In the process 82, a business ID, a process ID, and an application possible department ID are defined. In this example, a business ID “GID001”, a process ID “PID001”, and an application possible department ID “B001” are defined.

  In activity 83, process ID, activity ID, person in charge ID, role ID in charge, department ID in charge, attribute, return destination, and form ID are defined. Here, a plurality of records are defined.

  The department in charge of the activity can be designated as “same as the applicant's department”. In this case, the same operation is performed as when the applicant's department is designated as the department in charge.

  Finally, the activity for the business name “purchase application form” is shown in FIG.

  FIG. 9 is a diagram illustrating an example of a work item.

  This figure is based on the examples of FIGS.

  In this example, the change of the work item after Kanonon Hanako approved from the initial state of FIG. 8 is shown.

  Approval by Kanon Hanako shows that the status of Kantaro Kintaro, who had been “planned”, has changed to “waiting for processing”.

  FIG. 10 is a data table showing an example of job information.

  This job information is based on the example of organization information in FIG. 6 and the example of definition information in FIG.

  When a new case is drafted, a process ID, a case ID, an application department ID, and an application role ID are registered in the case 101.

  In the work item 102, a case ID, an activity ID, a person in charge ID, and a state are registered. In this example, the case ID “0000001” indicates that the activity ID “act000” has been processed, and the activity ID “act001” is waiting for processing.

  Next, the reminder 103 will be described. This is a data table newly provided to realize the embodiment of the present invention. By using the reminder function for the proposed matter, the matter ID, reminder ID, reminder execution (activity ID), reminder start (activity ID), reminder end (activity ID), and attributes are registered in the reminder 103. The The record of the case ID “0000001” shows an example that the applicant urged at the time of application, and the record of the case ID “0000002” shows an example that the accounting person urged at the time of sending back.

  In addition, an activity corresponding to the business name “purchase application form” is shown in FIG. A work item and a reminder are shown in 105.

  In the example of prompting from 105, an example is shown in which the applicant “Taro Kannon” prompts from “act001” to “act004” for the case “0000001” from before. When the applicant prompts, the applicant will be prompted to the last approver of the case in order to promptly end the case itself.

  Further, in the example of prompting from the back of 105, an example is shown in which “Jinro Kannon”, who is in charge of accounting, prompts from “act002” to “act003” from behind for the case “0000002”. If a user in the back activity wants to prompt a user in the activity before him, the user in the activity behind him / her in order to prompt the end of his / her processing in his / her activity. Does not prompt. For example, before the user of the back activity takes a long vacation, it is possible to end the processing before the break by prompting the user of the previous activity for the matter that the user is planning to process Become.

  In this example, “Kannon Jiro”, who is the last processor, is a reminder from the back. For example, when “Kannon Kintaro” prompts “Kannon Taro”, The following “Kannon Hanako” is urged, but “Kannon Jiro” is not urged. This is because “Kannon Kintaro” does not prompt “Kannon Jiro” who is the user behind. If “Kannon Kintaro” wants to urge “Kannon Jiro”, it can be realized by urging from the front.

  Next, the flow of processing in the workflow system when applying for application will be described with reference to FIG.

  In this flowchart, the user operates the workflow operation terminal, and the workflow server performs processing according to the operation.

  First, the workflow operation terminal displays a login screen to the workflow server on the display device in response to a user operation (1101). Then, the input authentication information is transmitted to the workflow server.

  In step 1102, the workflow server performs authentication to identify a user, and acquires a business that can be applied by the user.

  FIG. 12 shows a flowchart for acquiring a business that can be applied in the workflow server.

  In 1201, the workflow server acquires the applicant's position. Based on the login user ID (input information), the position information (504 in FIG. 5) is referred to. Here, the position means a group of roles and roles to which the user belongs. For example, in the case of “Taro Kannon” in FIG. 6, the position is sales section 1 / general from the organization information, and in the case of “Kannon Hanako”, the positions are sales section 1 / section manager and sales section 2 / section manager .

  In 1202, the workflow server acquires a business that can be applied. For each job, check whether it is possible to apply at the drafter's position and create a list of jobs that can be applied. For every business, with reference to the process definition of FIG. 7, if the applicant belongs to the department specified by the department ID that can be applied in the process definition 712 or its lower department, it is determined that the application can be applied. For example, when the department ID that can be applied for the process definition is the sales department of FIG.

  FIG. 13 shows an example in which the work that can be applied for acquired by the workflow server is displayed on the display device of the workflow operation terminal. The user can select a job application by pressing the “draft” button.

  The input information is a login user ID.

  In step 1103, the workflow operation terminal accepts selection of application work by the user. Then, the selected application work is notified to the workflow server.

  In 1104, the workflow server obtains the role at the time of drafting.

  The processing flow here is the same as the flowchart for acquiring the business that can be applied in the workflow server shown in FIG. 12, except that the input information is the login user ID and the business ID. Processing is different. Specifically, in 1202, the workflow server creates a list of positions that can be applied. The application belongs to the department specified by the department ID that can be applied in the process definition (712) or its lower department by referring to the process definition in FIG. 7 with the business specified by the user (the business ID of the input information). In this case, it is determined that the position can be applied. For example, if the logged-in user's position is Sales 1 Section / Manager and Sales 2 Section / Manager in FIG. 6 and the department ID that can be applied for the process definition is Sales 1 Section in FIG.・ Judge as section manager.

  In 1105, the workflow server determines whether there are a plurality of drafting roles. If yes, go to 1106; if no, go to 1108.

  In 1106, the workflow operation terminal displays the role selection screen acquired from the workflow server.

  In 1107, the workflow operation terminal accepts a role selection from the user. Then, the selected role is notified to the workflow server. FIG. 14 shows an example of a screen for selecting a role. This example shows a screen in which “Nanako Kanagawa” serves as both a general manager and a section manager, and selects which one to draft.

  In 1108, the workflow operation terminal displays the application screen acquired from the workflow server. FIG. 15 shows an example of the application screen. The user inputs necessary items on this screen.

  In 1109, the workflow operation terminal accepts input of application contents / prompting presence / absence. Then, various contents input to the workflow server are notified.

  In 1110, the workflow server performs a delivery process (new application).

  The delivery process will be described later.

  As described above, for example, as shown in FIG. 8, a new case is started.

  Next, the flow of processing in the workflow system when re-application, approval, return, and rejection will be described with reference to FIG.

  In this flowchart, the user operates the workflow operation terminal, and the workflow server performs processing according to the operation.

  First, the workflow operation terminal displays a login screen for the workflow server on the display device in response to a user operation (1601). Then, the input authentication information is transmitted to the workflow server.

  In 1602, the workflow server transmits the process waiting list to the workflow operation terminal, and the workflow operation terminal displays the process waiting list.

  FIG. 17 shows a flowchart for acquiring a processing waiting list in the workflow server. Note that the processing waiting list is a list for confirming a matter to be processed by the login user.

  The input information here is a login user ID.

  In 1701, the workflow server creates a list of matters waiting for processing.

A list of work items that meet all of the following conditions is created from all work items (722).
(1) Work item status is “Waiting for processing” (2) The person ID of the work item is the same as the login user ID (input information) For example, in FIG. 10, Hanako Kanon (section manager) opens the processing waiting list If the work item 102 is found to meet the above conditions, the following applies.
-Case ID “0000001”, activity ID “act001”, person in charge ID “U001”, status “waiting for processing”
From 1702 to 1707, the number of cases waiting for processing is repeated.

Moreover, it repeats by the number of reminders from 1703 to 1706. Here, referring to the prompt information (724 in FIG. 7) based on the work item case ID, the prompt is repeated. For example, in FIG. 10, when Hanako Kannon (section chief) opens the list of processing waiting, the following corresponds to the prompt.
Project ID “0000001”, reminder ID “U000”, reminder execution (activity ID) “act000”, reminder start (activity ID) “act001”, prompting end (activity ID) “act004”, attribute “from before”
In 1704, the workflow server determines whether there is a prompt for the item. If yes, go to 1705; if no, go to 1706. If the reminder meets the following conditions, the work item is regarded as reminder. If the activity of the work item (722, 716 in FIG. 7) is between the start of the reminder (724 in FIG. 7) and the end of the reminder, it is determined that there is a reminder (prompt start ≦ delivery destination ≦ prompt end). For example, in FIG. 10, when Kanon Hanako (section manager) opens a list of waiting for processing, the prompt is considered to be a prompt because it meets the above conditions.

  FIG. 18 shows an example of a screen for processing waiting list. Here, the state about the prompt is displayed in 1801. In this example, the case ID “S000000007” indicates “prompted”, the case ID “S000000006”, and the case ID “S000000002” indicate that there is no normal process-waiting case.

  Here, “prompted” indicates that the item is urged to process the item. In the present embodiment, the reminder itself is notified by e-mail or the like, so that the user knows the existence of the prompting matter by the notice. On this screen, it is possible to distinguish from the list which item is being urged.

  In 1603, the workflow operation terminal transmits the matter to be processed selected by the user to the workflow server.

  In 1604, the workflow server transmits the matter detail screen to the workflow operation terminal, and the workflow operation terminal displays the matter detail screen.

  FIG. 19 shows an example of a case detail screen.

  In 1605, the workflow operation terminal accepts input of application content editing / prompting presence / absence by user operation, and notifies the workflow server of the content.

  In 1606, the workflow server performs delivery processing (re-application, approval, return, rejection). The delivery process will be described later.

  As described above, re-application, approval, return, and rejection are made.

  Next, the flow of processing in the workflow system when prompting from the front will be described with reference to FIG.

  In this flowchart, the user operates the workflow operation terminal, and the workflow server performs processing according to the operation.

  First, the workflow operation terminal displays a login screen for the workflow server on the display device in response to a user operation (2001). Then, the input authentication information is transmitted to the workflow server.

  In 2002, the workflow server transmits the matter progress screen to the workflow operation terminal, and the workflow operation terminal displays the matter progress screen. The case progress list is a list for confirming processed cases processed by the login user (3101 in FIG. 31).

  Note that the flow of processing for acquiring a list of waiting for processing to be displayed on the case progress screen is handled by replacing “waiting for processing” with “processed” in the flowchart for acquiring the waiting list for processing shown in FIG.

Similarly, the input information is a login user ID. The workflow server creates a list of work items that meet all of the following conditions from all work items (722 in FIG. 7).
(1) The work item status is “processed” (2) The person ID of the work item is the same as the login user ID (input information) For example, in FIG. 10, Taro Kannon (applicant) When opened, if the work item (102 in FIG. 10) that satisfies the above conditions is found, the following applies.
-Case ID “0000001”, activity ID “act000”, person in charge ID “U000”, status “processed”
-Project ID “0000002”, activity ID “act000”, person in charge ID “U000”, status “processed”

Further, based on the work item item ID, the prompting information (724 in FIG. 7) is referred to, and the prompting is repeated. For example, in FIG. 10, when Taro Kannon (applicant) opens the project progress list, the following applies to the prompt.
(Prompt for case 0000001)
Project ID “0000001”, reminder ID “U000”, reminder execution (activity ID) “act000”, reminder start (activity ID) “act001”, prompting end (activity ID) “act004”, attribute “from before”
(Prompt for Project 0000002)
Item ID “0000002”, reminder ID “U003”, reminder execution (activity ID) “act003”, reminder start (activity ID) “act002”, prompt end (activity ID) “act003”, attribute “from behind”

If the reminder meets one of the following conditions, the work item is considered to be reminded. (1) Reminder executor ID is equal to login user ID (2) It is determined that there is a reminder if the activity ID of the work item is between the reminder start and the reminder end (recommendation start ≦ activity processed by the logged-in user) ≦ reminder end)
For example, when Taro Kannon (applicant) opens the case progress list in FIG. 10, since the prompt for the case 0000001 is a prompter ID = login user, it is determined that there is a prompt because the condition is met. Moreover, since the prompt about the matter 0000002 does not correspond to conditions, it determines with there being no prompt.

  In 2003, the workflow operation terminal accepts selection of a matter to be prompted by the user and notifies the workflow server.

  In 2004, the workflow server performs a reminder process (from the front). The prompting process will be described later.

  With the above, it is possible to prompt from before.

  FIG. 21 illustrates the flow of processing in the workflow system when prompting from behind.

  In this flowchart, the user operates the workflow operation terminal, and the workflow server performs processing according to the operation.

  First, the workflow operation terminal displays a login screen for the workflow server on the display device in response to a user operation (2101). Then, the input authentication information is transmitted to the workflow server.

  In 2102, the workflow server transmits the scheduled item list to the workflow operation terminal, and the workflow operation terminal displays the scheduled item list. The scheduled item list is a list for the login user to confirm items to be processed in the future (3102 in FIG. 31). For example, when there is a situation such as a business trip in the near future, the user can prompt the authorized user before him to process the matter before the business trip.

  Note that the flow of processing for acquiring the scheduled item list to be displayed in the scheduled item list is handled by replacing “processing waiting” with “processed” in the flowchart for acquiring the processing waiting list shown in FIG.

Similarly, the input information is a login user ID.
A list of work items that meet all of the following conditions is created from all work items (722 in FIG. 7).
(1) The work item status is “scheduled” (2) The person in charge of the work item is the same as the login user ID (input information) For example, in FIG. 10, Jiro Kannon (in charge of accounting) opens the list of scheduled cases In this case, when a work item (102 in FIG. 10) that satisfies the above conditions is obtained, the following applies.
-Case ID “0000001”, activity ID “act003”, person in charge ID “U003”, status “planned”
-Project ID “0000002”, activity ID “act003”, person in charge ID “U003”, status “planned”

Based on the item ID of the work item, the prompt information (724 in FIG. 7) is referred to, and the prompt is repeated. For example, in FIG. 10, when Jinro Kannon (accounting officer) opens the case progress list, the following applies to the prompt.
(Prompt for case 0000001)
Project ID “0000001”, reminder ID “U000”, reminder execution (activity ID) “act000”, reminder start (activity ID) “act001”, prompting end (activity ID) “act004”, attribute “from before”
(Prompt for Project 0000002)
Item ID “0000002”, reminder ID “U003”, reminder execution (activity ID) “act003”, reminder start (activity ID) “act002”, prompt end (activity ID) “act003”, attribute “from behind”

If the reminder meets one of the following conditions, the work item is considered to be reminded. (1) The reminder executor ID is equal to the login user ID (2) The activity corresponding to the work item (722 in FIG. 7) whose state is “waiting for processing” is the start and end of the reminder (724 in FIG. 7) If it is between, it will be determined that there is a reminder (prompt start ≤ current processing waiting activity ≤ reminder end)
For example, in FIG. 10, when Jinro Kannon (accounter) opens the case progress list, the reminder ID (U000) for the case 0000001 does not match the login user ID (U003). The work item whose condition is “waiting for processing” is the case ID “0000001”, the activity ID “act001”, the person in charge ID “U001”, and the state “waiting for processing”.
The activity ID (act001) falls between the prompting start (act001) and the prompting end (act004), so it is determined that there is a prompting.

  Further, the prompt for the matter 0000002 is determined to be prompted because the prompter ID (U003) matches the login user ID (U003).

  In 2103, the workflow operation terminal accepts selection of a matter to be urged by the user and notifies the workflow server.

  Here, when the user selects a “scheduled” case, an approved user who is currently waiting for processing is identified and displayed on the screen (FIG. 32). The person in charge who is “waiting for processing” in the state of the corresponding item ID and the work item 102 shown in FIG. 10 is specified as the target. Then, when the user gives a prompt instruction, the instruction is transmitted to the workflow server. When a prompting instruction is given, a prompting process is executed. Details of the process will be described later.

  In addition, if there is a “scheduled” matter that meets the predetermined conditions without the user selecting a matter, or all “scheduled” matter will be promptly processed without user intervention. It can also take a form.

  Furthermore, it is possible to select whether the selected item is a prompt from the “selected user” or “the approver next to the approver of the approving activity”. FIG. 30 is a screen for selecting a user to be prompted. By checking the box 3001, it is possible to select a prompt from “the next approver of the approver of the approving activity”. As a result, in the activity shown in FIG. 8, even if the “accounter” urges the “section manager”, the “section manager” is notified as if the “manager” had been urged. . Usually, in the workflow process flow, even if the approver immediately after me is known, it is often not known the approver of the distant destination, such as next, so it is prompted by the approver immediately after. Effective reminder can be realized by making it look like. If the check box is checked, it is necessary to replace the ID of the reminder in a later process. Therefore, here, the information is temporarily stored in the memory as replacement information.

  In 2104, the workflow server performs a reminder process (from the back). The prompting process will be described later.

  As described above, it is possible to prompt from behind.

  Next, the flow of processing in another workflow system will be described with reference to FIG.

  In this flowchart, the user operates the workflow operation terminal, and the workflow server performs processing according to the operation.

  First, the workflow operation terminal displays a login screen for the workflow server on the display device in response to a user operation (3301). Then, the input authentication information is transmitted to the workflow server.

  In 3302, the workflow server transmits the matter selection screen to the workflow operation terminal, and the workflow operation terminal displays the matter selection screen.

  An example of the item selection screen is shown in FIG. From this item selection screen, the user can display a list of cases waiting for processing (3401), a case where a list of matters waiting to be processed with a prompt (3402), and a case where a list of matters to be processed are displayed ( 3403) "can be selected.

  “When displaying a list of waiting items for processing” is a normal screen that allows a user to check a list of items waiting for processing by the login user.

  The “displaying a list of cases waiting for processing with a prompt” is a screen on which a list of cases that are waiting for processing by the login user and that have a prompt for the case can be confirmed. This is an effective screen when preferentially processing items with reminders.

  “When displaying a list of matters to be processed” is a screen on which a login user can check a list of matters that will be processed in the future. This is an effective screen when, for example, a project to be urged is extracted.

  In 3303, the workflow operation terminal determines the type of screen selected by the workflow server in response to the user operation, and transmits the determination result to the workflow server.

  In 3304, the workflow server performs a process of displaying a list of waiting items to be processed, and transmits the list screen information to the workflow operation terminal. The workflow operation terminal displays a list on the screen using the list screen information.

  Note that the flow of processing for acquiring a list of waiting items to be displayed in the list of waiting items for processing can be realized by the processing of 1701 to 1702 in the flowchart for acquiring the list of waiting for processing shown in FIG.

  In 3305, the workflow server performs a process of displaying a list of cases waiting for processing with prompting, and transmits the list screen information to the workflow operation terminal. In the workflow operation terminal, the list is displayed on the screen using the list screen information (3103 in FIG. 31).

  Note that the flow of processing for acquiring the list of processing waiting for processing items to be displayed in the processing waiting for processing list with prompting can be realized by the processing of the flowchart for acquiring the processing waiting list shown in FIG.

  In 3306, the workflow server performs a process of displaying the scheduled item list, and transmits the list screen information to the workflow operation terminal. In the workflow operation terminal, the list is displayed on the screen using the list screen information (3102 in FIG. 31).

  Note that the flow of processing for acquiring the scheduled item list to be displayed in the scheduled item list is handled by replacing “waiting for processing” with “scheduled” in the flowchart for acquiring the processing waiting list shown in FIG.

  In 3307, the workflow operation terminal accepts a selection of a matter from the user from the displayed list screen.

  In 3308, the workflow operation terminal determines whether the “prompt” operation has been performed on the selected item. If yes, go to 3310; if no, go to 3309. Specifically, the determination is made based on whether the item “prompted” is selected from the menu or the like on the list screen. At that time, it accepts designation of the user who performs the prompting and designates it to the workflow server. In addition, since the extraction method of the user who performs a prompt is as having mentioned above, description is abbreviate | omitted. There are two reminders, “from the front” and “from the back”, and the type is also notified to the workflow server.

  In 3309, the workflow server performs a delivery process in response to an instruction given from the workflow operation terminal. This delivery process is the same as the conventional delivery process.

  In 3310, the workflow server performs a reminder process. Since the prompting process (from the front to the back) is as described above, the description is omitted.

  The flow of processing in other workflow systems has been described above.

  Next, the flow of delivery processing in the workflow system will be described.

  FIG. 22 is a flowchart showing the flow of delivery processing in the workflow system. This process is performed in the workflow server.

  Here, as input information, login user ID, application department ID, application role ID, business ID, process ID, work item ID, input contents, presence / absence of prompt (“Yes”, “No”), processing classification (“New Application” ”,“ Reapply ”,“ approval ”,“ send back ”,“ denial ”).

  In 2201, the workflow server determines a processing category. If it is a new application, the process proceeds to 2204. In other cases, the process proceeds to 2202. For example, if the approver presses the approval button on the case details screen (FIG. 19), the processing classification becomes approval. Similarly, if the return button is pressed, the return is made, and if the reject button is pressed, the result is rejected. The new application and the re-application have different caller flows (1110 in FIG. 11 and 1606 in FIG. 16).

  In 2202, the workflow server deletes the “waiting for processing” work item. Delete “waiting for processing” work items corresponding to activities that have been re-applied, approved, returned, or rejected. For example, the case 0000001 in FIG. 10 is in a state of waiting for Hanako Kanon's processing. In this state, when Kanon Kanoko approves, the approved activity is act001, and the corresponding work item “waiting for processing” is deleted.

  In 2203, the workflow server updates the input content. Update the input contents with the contents input by the end user.

In 2204, the workflow server creates a new matter. (Matter ID: new issue number, business ID: “business ID” of input information, application department ID: “application department ID” of input information, application role ID: “application role ID” of input information)
In 2205, the workflow server newly creates the input content with the content input by the end user.

In 2206, the workflow server creates a “processed” work item (= creates a “processed” work item corresponding to the processed activity).
For example, the case 0000001 in FIG. 10 is waiting for the processing of Hanako Kannon. In this state, when Kanon Kanoko approves, the approved activity is act001, and the corresponding work item “processed” is created.

  For example, when Taro Kannon makes a new application, the applied activity is act 000, and the corresponding work item “processed” is created.

  In 2207, the workflow server determines the processing category. If not, the process proceeds to 2222; otherwise, the process proceeds to 2208.

  In 2208, the workflow server determines the processing category. In the case of return, the process proceeds to 2210, and in other cases, the process proceeds to 2209.

  In 2209, the workflow server obtains a delivery destination activity.

  For example, when Taro Kannon applied for in FIG. 8, the activity that has been processed is act 000, and the activity of the delivery destination is act 001. Further, when Kanon Hanako (section manager) approves, the processed activity is act001, and the delivery destination activity is act002. Further, when Kannon Kintaro (director) approves, the processed activity is act002 and the delivery destination activity is act003. Further, when approved by Jiro Kannon (accounting officer), the activity that has been processed is act003, and the activity of the delivery destination is act004.

  Details of the processing here are shown in FIG.

  FIG. 23 is a flowchart showing a flow of processing for obtaining the next user execution activity in the workflow server.

  A case ID and an input activity ID are input as input information.

  In 2301, the workflow server determines an attribute of the target activity. In the case of a branch condition, the process proceeds to 2303. In other cases, the process proceeds to 2302.

  In 2302, the workflow server obtains the next activity. For example, in 104 of FIG. 10, act 003 is next to act 004.

  In 2303, the workflow server obtains the next activity. An event that satisfies the conditions of all the transitions extending from the conditional branch is found, and the activity that leads to the transition is set as the next activity. For example, in FIG. 4, next to 402 is 403 or 405 depending on the condition.

  In 2304, the workflow server determines the attribute of the next activity. In the case of end, the process proceeds to 2307, in the case of user execution, the process proceeds to 2406, and in other cases, the process proceeds to 2305.

  In 2305, the workflow server returns to 2301 in order to repeatedly perform the next activity.

  In 2306, the workflow server returns the next activity.

  In 2307, the workflow server returns an end activity.

On the other hand, in 2210, the workflow server deletes the reminder that is no longer needed. Delete the reminder that meets all of the following conditions, and send an email notification to the reminder.
(1) “From the front” reminder (2) Returned before (application side) from the start of reminder (send-back activity <reminder start activity)
In 2211, the workflow server determines whether the attribute of the delivery destination activity is “end”. If yes, go to 2212; if no, go to 2219.
For example, if the processing category is “new application”, “re-application”, or “approval”. In 2212, a delivery destination is obtained. In the case of “send back”, the return destination (716 in FIG. 7) of the processed activity is the delivery destination.

  In 2212, the workflow server creates a work queue item. A detailed flow of this process will be described with reference to FIG.

  Here, the input information is a case ID and a delivery destination activity ID.

  In 2401, the workflow server obtains a corresponding person. In 2402 to 2404, the process is repeated for the number of corresponding persons, and a work item is created in 2403 (work item ID: new issue number, activity ID: delivery destination activity ID, person in charge ID: corresponding person's ID). ID, state: “waiting for processing”).

  A detailed processing flow in 2401 will be described with reference to FIG.

  Here, the input information is a case ID and an activity ID.

  In 2501, the workflow server determines whether the user is designated (the user designation means that the person in charge ID of the activity (716 in FIG. 7) is designated). If yes, go to 2505; if no, go to 2502.

  In 2502, the workflow server determines whether only the role is designated (designating only the role is to designate “same as the application department” in the department ID in charge of the activity (716 in FIG. 7). ). If yes, go to 2503; if no, go to 2504. For example, in FIG. 8, only the role is specified for the activity act002.

  In 2503, the workflow server obtains a corresponding person of the department & role. The application department ID (721 in FIG. 7) of the case (input information) is designated for the department, and the role in charge of the activity is designated for the role. Finally, the relevant person is returned and the process is terminated.

In 2504, the workflow server obtains a person corresponding to the department & role.
The department in charge of the activity is designated as the department, and the role in charge of the activity is designated as the role. Finally, the relevant person is returned and the process is terminated.

  The detailed processing flow of this processing will be described with reference to FIG.

  Here, the input information is a department ID and a role ID.

  In 2601, the workflow server determines whether there is a corresponding person. If yes, go to 2602; if no, go to 2603.

For example, in FIG. 6, when it is determined whether there is a user corresponding to the sales department 1 (C001) and the section manager (R001), the position (604 in FIG. 6) is referred to, and the department is the sales department 1 (C001). The records in which the role corresponds to the section manager (R001) are as follows.
User ID “U001”, role ID “R001”, department ID “C001”
Based on this information, the person concerned becomes U001 Kannon Hanako.

  In 2602, the workflow server returns the corresponding person and ends the process.

  In 2603, the workflow server repeats in the upper department and returns to 2601. Find the parent department of a department. It is obtained with reference to the parent department of the department (501 in FIG. 5). For example, in FIG. 6, the parent department of the sales department 1 (C001) becomes the sales department (B001) from 601 in FIG. If there is no parent department (= highest department), it is excluded here because it is abnormal.

  In 2505, the workflow server returns the user ID and ends the process. In the case where a user is specified, the corresponding person is the specified user itself.

  Next, in 2213, the workflow server creates a scheduled work item. The detailed processing flow of this processing will be described with reference to FIG.

  Here, the input information is a case ID and an activity ID (application or user execution activity).

  In 2701, the workflow server determines what the attribute of the activity (input information) is. In the case of “End”, the process ends. In the case of “User execution”, the process proceeds to 2702. In the case of “Conditional branch”, the process proceeds to 2707. In the case of “Join”, the process proceeds to 2709.

  In 2702, the workflow server determines whether it has already been created. If yes, go to 2709; if no, go to 2703. Specifically, it is checked whether or not there is a work item “scheduled” in the target activity.

  In 2703, the workflow server obtains a corresponding person of the target activity. Note that the details of this process are the same as the processes in FIGS.

  Then, in 2704 to 2706, the workflow server repeatedly processes the number of persons, and in 2705, creates a “planned” work item (case ID: matter ID of input information, activity ID: ID of delivery destination activity). Person in charge ID: ID of the corresponding person, state: “plan”).

  In 2707, the workflow server determines a branch condition. Find the condition that is satisfied from all the transition conditions extending from the conditional branch. It should be noted that a case where there is nothing to be established or a case where a plurality is established is excluded because it is an abnormal system.

  At 2708, the workflow server deletes the “scheduled” work item. Delete “scheduled” work items corresponding to all activities up to the corresponding merge after the transition that does not hold the condition. Also, the reminder created from the deleted work item is deleted. Then, an email notification is sent to the creator of the deleted reminder. For example, in the process of FIG. 4, the work items scheduled to be 403 and 404 are deleted in the case where the application is made back after the application with the amount of 100,000 yen and the application is made with 400,000 yen at the time of re-application.

  In 2709, the workflow server repeats the next activity and returns to 2701.

  Next, in 2214, the workflow server determines whether there is a prompt. If yes, go to 2216; if no, go to 2215.

  In 2215, the workflow server transmits an approval request mail. The detailed processing flow will be described with reference to FIG.

  Here, the input information includes “login user ID”, “case ID”, and “delivery destination activity ID”.

  In 2801, the workflow server creates an approval request text. The business name is obtained from the business in the definition information (FIG. 7) based on the case ID. For example, “subject: approval request has been received”, “text: purchase request (0000001) approval request has been received”, and the like. This approval request email is sent to the user who is “waiting for processing” in the work item 102.

  From 2802 to 2807, the workflow server repeats the number of reminders. For example, in the case where the case ID is 0000001 in FIG. 10 is approved by Hanako Kannon (section manager), the prompt is obtained from the prompting table (103 in FIG. 10) based on the case ID (input information). This process is a process for indicating in the approval request mail that there is a prompt for this item.

  In 2803, the workflow server determines whether to give a reminder. If yes, go to 2804; if no, go to 2807. Here, if the delivery destination activity is between the prompt start of the prompt (724 in FIG. 7) and the prompt end, it is determined that there is a prompt (start prompt = delivery destination ≦ prompt end). For example, in the case where the case ID is 000001 in FIG. 10 is approved by Hanako Kannon (section manager), the delivery destination is act002, the start of the prompt is act001, and the end is act004, so it is determined that there is a prompt.

  In 2804, the workflow server determines whether to change the prompter. If yes, go to 2805; if no, go to 2806. Here, if there is presence / absence of the prompter change in the prompt (724 in FIG. 7), it is determined to change.

  In 2805, the workflow server adds a prompt text. Here, the name of the reminder is obtained from the user (503) of the organization information (Fig. 5) based on the reminder ID (text example: prompted by Taro Kannon).

  In 2806, the workflow server adds a prompt text. Here, the next user execution activity is obtained based on the delivery destination activity (FIG. 23), and the corresponding person of the activity is obtained (FIG. 25). Based on the person in question, the name of the reminder is obtained from the user (503) of the organization information (Fig. 5) (text example: prompted by Kintaro Kannon).

  In 2808, the workflow server sends an email. Here, a corresponding person of the delivery destination activity is obtained (FIG. 25), and mail is transmitted to the corresponding person. The text is created in 2801, 2805, 2806.

  E-mail example (Subject: Approval request has arrived. Text: Purchase request (0000001) approval request has arrived. Reminded by Taro Kannon.)

As described above, an example in which the approval request mail is transmitted has been described with reference to FIG. 28, but there is also an embodiment as described below.
(1) An embodiment in which a reminder mail is transmitted separately from the approval request mail. Thereby, the user who is the target of the prompt can be prompted by sending the prompt by an independent mail.
(2) In the case of prompting from the back, an embodiment in which prompting is made to a user waiting for processing, and at the same time prompting a user (planned user) of an activity from the user waiting for processing to the user who made the prompting. As a result, every time you become a user waiting for processing in the workflow flow, you will be prompted for the scheduled user as compared to when you prompt the user. It is possible to squeeze.

  Next, in 2216, the workflow server determines the processing category. In the case of “return”, the process proceeds to 2218. In other cases, the process proceeds to 2217.

In 2217, the workflow server creates a new reminder.
-“Item ID (input information)” as the case ID, “Login user ID (input information)” as the reminder ID, and “Activity corresponding to the work item ID (input information) as the reminder execution (activity ID)” “ID”, “reminder start” (activity ID), “delivery destination activity”, “prompt end” (activity ID) “end activity”, attribute “from before”, and prompter change “none”.

At 2918, the workflow server creates a new reminder.
-“Item ID (input information)” as the case ID, “Login user ID (input information)” as the reminder ID, and “Activity corresponding to the work item ID (input information) as the reminder execution (activity ID)” "ID", as a reminder start (activity ID), as "delivery destination activity", as a reminder end (activity ID) as "activity ID corresponding to work item ID (input information)", as an attribute, from "rear""None" as the presence / absence of the person change.

  Next, in 2219, the workflow server sends an email notification to the applicant. Here, the applicant is notified that the case has been finally approved.

  The applicant obtains from the person in charge ID of the work item (FIG. 7) corresponding to the application activity (FIG. 7), and obtains the mail address from the user of the organization information (FIG. 5) based on the user ID. The business name is obtained from the business in the definition information (FIG. 7) based on the case ID.

  Final approval e-mail example (Subject: Purchase statement was final approved. Main text: Purchase statement (0000001) was final approved.)

  In 2220, the workflow server notifies the reminder of the mail. Here, the reminder is notified that the case has been finally approved.

  The reminder is obtained from the reminder ID of the reminder (FIG. 7), and the e-mail address is obtained from the user of the organization information (FIG. 5).

  E-mail example (Subject: Purchase reimbursement that was urged was finally approved. Text: Purchase reimbursement that was urged (0000001) was finally approved.)

  In 2221, the workflow server deletes the prompt for the matter. Here, all the prompts for the case are deleted. For example, when a case with case ID 0000001 is finally approved, all records with case ID 0000001 are deleted from the reminder table (FIG. 7).

  In 2222, the workflow server sends an email notification to the applicant. Here, the applicant is notified that the case has been rejected.

  The applicant obtains from the person in charge ID of the work item (FIG. 7) corresponding to the application activity (FIG. 7), and obtains the mail address from the user of the organization information (FIG. 5) based on the user ID. The business name is obtained from the business in the definition information (FIG. 7) based on the case ID.

  Example of rejected email (Subject: Purchase Report was rejected. Text: Purchase Report (0000001) was rejected).

  In 2223, the workflow server notifies the reminder of the mail. Here, the reminder is notified that the case has been rejected.

  The reminder is obtained from the reminder ID of the reminder (FIG. 7), and the e-mail address is obtained from the user of the organization information (FIG. 5).

  Example of rejected email (Subject: Purchase reimbursement that was urged was rejected. Text: Purchase reimbursement that was urged (0000001) was rejected).

  In 2224, the workflow server deletes the prompt for the matter. Here, all the prompts for the case are deleted. For example, if the case with the case ID 0000001 is rejected, all records with the case ID 0000001 are deleted from the prompting table (FIG. 7).

  The flow of delivery processing in the workflow system has been described above.

  Next, the flow of the prompting process (2004, 2104, 3110) will be described with reference to FIG.

  FIG. 29 is a flowchart showing a flow of reminding processing in the workflow system.

  Here, the input information includes "login user ID", "case ID", "processing activity ID", "work item ID (work item for which the login user is responsible)", "prompt direction", "prompt performer's". Whether or not there is replacement ”.

  In 2901, the workflow server creates a mail text. If there is no replacement of the reminder (input information), the name of the reminder is obtained from the user (503) of the organization information (FIG. 5) based on the login user ID, and whether or not the reminder is replaced If there is, the name of the prompter obtains the next user execution activity based on the work item awaiting processing (FIG. 23), and finds the person corresponding to the activity (FIG. 25). Then, based on the corresponding person, the name of the prompter is obtained from the user (503) of the organization information (FIG. 5). Email example (Subject: Reminder received. Text: Taro Kannon received a reminder for purchase check-in (0000001).)

  From 2902 to 2907, the workflow server repeats for the number of reminders.

  In 2903, the workflow server determines whether the user is waiting for a process. If yes, go to 2904; if no, go to 2907. Judgment is made depending on whether the activity waiting for processing is between the start and end of the prompt.

  In 2904, the workflow server determines whether to change the prompter. If yes, go to 2906; if no, go to 2905. Here, whether or not to change the prompter is determined to be changed if there is a change in the prompter (see FIG. 7).

  In 2905, the workflow server adds a reminder text. Here, the name of the reminder is obtained from the user (503) of the organization information (Fig. 5) based on the reminder ID (example text: prompted by Taro Kannon).

  In 2906, the workflow server adds a prompt text. Here, the next user execution activity is obtained based on the work item waiting for processing (FIG. 23), and the corresponding person of the activity is obtained (FIG. 25). Based on the person in question, the name of the reminder is obtained from the user (503) of the organization information (Fig. 5) (text example: prompted by Kintaro Kannon).

  In 2908, the workflow server sends an email. Here, the destination is the person in charge of the activity ID (input information) waiting for processing.

  In 2909, the workflow server determines the direction of the reminder. In the case of “from the front”, the process proceeds to 2910.

In 2910, the workflow server creates a reminder. Here, a new reminder is created.
-“Item ID (input information)” as the case ID, “Login user ID (input information)” as the reminder ID, and “Activity corresponding to the work item ID (input information) as the reminder execution (activity ID)” “ID”, “prompt start” (activity ID), “processing waiting activity”, “prompt end” (activity ID) “end activity”, attribute “from before”, prompter change presence / absence “none”.

In 2911, the workflow server creates a reminder. Here, a new reminder list element is created.
-“Item ID (input information)” as the case ID, “Login user ID (input information)” as the reminder ID, and “Activity corresponding to the work item ID (input information) as the reminder execution (activity ID)” “ID”, as a reminder start (activity ID), “activity waiting for processing”, as a reminder end (activity ID), “activity ID corresponding to work item ID (input information)”, as attribute, “from behind”, prompt As the presence / absence of a change of the person, “reminder change / no change (input information)”.

  The flow of the prompting process (2004, 2104) has been described above.

  As described above, according to the present invention, it is possible to provide a workflow system that can prompt the user who approves the previous activity from the user who approves the back activity in the workflow processing flow. Become.

  For example, by prompting the user who approves the previous activity in the process that is set as the user who approves before the user who approves the back activity is absent due to vacation It is possible to finish the approval process of the process before the vacation. Therefore, it is a particularly useful function when trying to quickly end a process that is about to expire.

  Further, it is possible to provide a workflow system that can prompt the approver of the subsequent activity in the workflow processing flow.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

  The program according to the present invention is a program that can be executed by a computer according to the processing method of the flowchart shown in the present invention. The storage medium according to the present invention stores a program that can be executed by a computer. The program in the present invention may be a program for each processing method of each device.

  As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by executing the reading.

  In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program constitutes the present invention.

  As a recording medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk, solid state drive, or the like can be used.

  Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) operating on the computer based on an instruction of the program is actually It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the processing and the processing is included.

  Furthermore, after the program read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention.

  In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

101 CPU7
102 RAM
103 ROM
104 HD
106 Input Device 107 Display Device 108 Communication Interface

Claims (13)

An information processing device that performs workflow processing for an applied item,
A first matter extraction means for extracting a matter including an activity that the first user is scheduled to process;
A first accepting unit for accepting a matter for prompting a second user who processes an activity before the activity processed by the first user from the matter extracted by the first matter extracting unit; ,
For the matter accepted by the first accepting means, the activity of the matter is processed for the second user who should process the matter activity before the activity processed by the first user. An information processing apparatus comprising: a first prompting means for prompting the user. The second user includes each user who should process each activity up to the activity that the first user processes,
The first prompting means prompts a second user who should process each activity up to the activity processed by the first user to process the activity of the matter. The information processing apparatus according to claim 1.   In the case where the first user is urged to the second user, the first urging means urges the user to process the activity next to the activity processed by the second user. The information processing apparatus according to claim 1, wherein the information processing apparatus performs the information processing.   When the processing of the matter is rejected or returned in the flow of the workflow, when the prompting by the first prompting means becomes unnecessary, a second notification means for notifying the first user to that effect The information processing apparatus according to claim 1, further comprising:   The first notification means for notifying that when the activity of the matter has been processed by the last second user to be urged by the first urging means. Item 5. The information processing apparatus according to any one of Items 1 to 4. A second matter extracting means for extracting a matter including an activity to be processed by the first user;
A second accepting unit for accepting a matter that prompts a third user who processes an activity after the activity processed by the first user from the matter extracted by the second matter extracting unit; ,
For the matter accepted by the first accepting means, the activity of the matter is processed for the third user who processes the matter activity after the activity to be processed by the first user. The information processing apparatus according to claim 1, further comprising second prompting means for prompting the user. The first prompting means prompts the second user who should process the activity of the matter before the activity processed by the first user, and the activity processed by the first user Do not prompt the third user who will process the activity of the matter later,
The said 2nd prompting means performs prompting with respect to all the said 3rd users who process the activity of the said matter after the activity which the said 1st user should process. The information processing apparatus described. An information processing device that performs workflow processing for an applied item,
A request accepting means for accepting a matter display request made by the first user;
Depending on the content of the request received by the request receiving means, it is a request to extract a matter including an activity scheduled to be processed by the first user, or an activity to be processed by the first user A determination means for determining whether the request is for extracting a matter including
As a result of the determination by the determination means, when it is determined that the request is for extracting a matter including an activity that the first user is scheduled to process, the first user is scheduled to process. If it is determined that the request includes an activity to be processed by the first user, an item including the activity to be processed by the first user is extracted. An information processing apparatus comprising: a case extracting means for performing   9. The information processing according to claim 1, wherein the first or second prompting means or the first or second notifying means prompts or notifies by e-mail. apparatus. An information processing system in which a client terminal and an information processing apparatus that performs a workflow process for an applied matter can communicate via a network,
A first matter extraction means for extracting a matter including an activity that the first user is scheduled to process;
A first accepting unit for accepting a matter for prompting a second user who processes an activity before the activity processed by the first user from the matter extracted by the first matter extracting unit; ,
For the matter accepted by the first accepting means, the activity of the matter is processed for the second user who should process the matter activity before the activity processed by the first user. An information processing system comprising: a first prompting means for prompting the user. An information processing method in an information processing apparatus that performs workflow processing for an applied matter,
A first matter extraction step to extract matters that include activities that the first user is scheduled to process;
A first accepting step for accepting a matter that prompts a second user who processes an activity before the activity processed by the first user from the matter extracted by the first matter extracting step; ,
For the matter accepted in the first accepting step, the activity of the matter is processed for the second user who should process the matter activity before the activity processed by the first user. An information processing method comprising: a first prompting step for prompting the user. A program that can be executed by an information processing device that performs workflow processing for a filed application,
A first matter extraction means for extracting the matter including the activity that the first user is scheduled to process,
A first accepting means for accepting a matter that prompts a second user to process an activity prior to the activity that the first user processes from the matter extracted by the first matter extracting means;
For the matter accepted by the first accepting means, the activity of the matter is processed for the second user who should process the matter activity before the activity processed by the first user. A program for causing the information processing apparatus to function as first prompting means for prompting the user. A recording medium storing the computer program according to claim 12 in a computer-readable manner.

Images