JP2011034421A - Information processing apparatus, information processing system, information processing method, program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To set the authority to refer to a process history about an operation, so that the process history that is unnecessary for security is not displayed when an entrusting user refers to the process history. <P>SOLUTION: An operation that an entrusting user can entrust is extracted from an operation data table defining each operation. The designation of an entrusted user entrusted with the operation extracted is received. The designation of operation authority for entrusting the extracted operation to the entrusted user and reference authority after the processing of the operation is accepted and the authorities are associated and stored in an entrustment setting table. The history processed is stored in a process history table. Control for displaying the history of the process related to the operation is performed. Using information for identifying a requesting user and the reference authority stored in the entrustment setting table, a history that the requesting user can refer to is extracted from the process history table and displayed. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a workflow control apparatus and a control method thereof connected via a network, a workflow control system configured by connecting a client terminal, a workflow control server, and a client terminal to each other via a network, and a program In particular, the present invention relates to a system characterized by flexible settings relating to the workflow processing history browsing authority.

  In a general workflow system, a user may keep a history of processing electronic slips. Patent Document 1 also holds such a history.

  Further, in Patent Document 1, by setting the history reference authority for each user, it is possible to refer to other than the processing history of the electronic slip processed by the user.

JP 2001-22827 A

  However, Patent Document 1 is characterized in that the system administrator sets the reference authority for each user, and the user cannot set the reference authority for the user.

  Therefore, in particular, the delegation source user does not correspond to setting the authority to refer to the history processed by the delegation source to the delegation destination user at the time of delegation.

  In addition, although the processing history can be set for each user, the processing history cannot be set in finer units, so that the flexibility is not sufficient and a security problem remains.

  For example, the following six security problems can be considered.

Problem 1 “Case where you do not want to show the history of the delegation source”
(1) Mr. A delegates to Mr. B. (2) Mr. A applied for a large number of customer registration slips. (3) Mr. B applied for a large amount of customer registration slips as Mr. A. (4) Since Mr. B can see all of the processing history of Mr. A, he can see the customer registration slip processed by Mr. A, and even customer information irrelevant to Mr. B can be seen.

Problem 2 “Case where you do not want to share processing history between delegates”
(1) Mr. A delegates to Mr. B and Mr. C. (2) Mr. B applied for a contract slip as Mr. A. (3) Since Mr. C can see all the processing histories that Mr. B applied as Mr. A, he can see the processing history of the slip that Mr. B who has nothing to do with Mr. A applied.

Problem 3 “Case where you do not want to show the processing history for each application / approval”
(1) Mr. A applied for a book purchase slip. (2) Mr. A approves the contract slip. (3) Mr. A is entrusted with Mr. B. (4) Mr. A does not want to show the processing history of the important contract amount of the contract slip, but wants to show the processing history of the book purchase slip.

Problem 4 “Case where you do not want to show the processing history for each job”
(1) Mr. A delegates to Mr. B. (2) Mr. A approves the contract slip. (3) Mr. A approves the personnel evaluation slip. (4) Mr. A applied for a transportation fee slip. (5) Since Mr. B can see all processing histories, he can also see important processing histories such as contracts and personnel evaluations.

Problem 5 “Case where you do not want to see the processing history processed before delegation”
(1) Mr. A approves the contract slip (referred to as slip 1). A delegates to B. (3) Mr. A approves the contract slip (referred to as slip 2). (4) Mr. A wants to show only slip 2 after delegation to B, but also shows slip 1.

Problem 6 “Case where you can select whether or not you can see the work history so far after delegation”
(1) Mr. A delegates to Mr. B. (2) Mr. B processes the slip as Mr. A. (3) Mr. A cancels Mr. B's delegation. (4) Mr. B wants to see the history of the voucher processed as Mr. A, but cannot see it because the delegation has been released (the problem is that security is too high)
Therefore, the present invention enables the delegation source user to refer to the processing history by allowing the delegation source user to set the authority to refer to the processing history related to the business when delegating the business to the delegation destination user at the time of delegation. An object of the present invention is to prevent display of a processing history unnecessary for security.

  The present invention is an information processing apparatus capable of delegating the operation authority of a delegation source user to a delegation destination user in a workflow procedure, and according to the request of the delegation source user, the tasks that can be delegated are Extraction means for extracting from the business data table to be defined, delegation destination user reception means for accepting designation of a delegation destination user for delegating the work extracted by the extraction means in accordance with the request of the delegation source user, and the delegation source According to the user's request, the authority accepting means for accepting the designation of the operation authority to be delegated to the delegation destination user and the reference authority after the work is processed on the work extracted by the extracting means, and the delegation source A user, a delegation-destination user received by the delegation-destination user reception unit, and a reception by the authority reception unit A first storage means for storing the operation authority and the reference authority to be delegated to the assigned user and the authority to be stored in the delegation setting table; Storage means, and history display means for performing control to display a history of processing related to the job in accordance with a user's request, the history display means to the request setting user information, and to the delegation setting table The history that can be referred to by the requesting user is extracted from the processing history table and displayed using the stored reference authority.

  According to the present invention, when a delegation source user delegates a task to a delegation destination user at the time of delegation, the delegation source user can refer to the processing history by enabling the setting of the processing history reference authority for the task. It is possible to prevent display of a processing history unnecessary for security.

System configuration diagram showing the configuration of the workflow system Diagram showing hardware configuration of various terminals Example of delegation setting screen Flow chart until delegation setting screen is displayed Example of processing history search screen on client terminal Flow chart until processing history search screen is displayed Flowchart from the start of search on the processing history search screen to the display of search results Delegation setting table example Process history browsing screen target user selection list acquisition flowchart Detailed processing flowchart of delegation screen acquisition processing Example of business data table Example of processing history search screen on client terminal Process history table example

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a system configuration diagram showing a configuration of a workflow system (information processing system) according to the present invention.

  In FIG. 1, in the workflow system, at least one workflow server 101 and a workflow client 102 are connected via a network.

  The user makes a workflow progress request or the like from the workflow client 102 to the workflow server 101 using, for example, a web browser or client software.

  The workflow server 101 performs processing and management according to the request, and transmits a result to the workflow client 102 if necessary.

  The communication between the workflow server 101 and the workflow client 102 may be a normal HTTP request or a web service request using SOAP or the like. Further, the workflow server 101 is connected to the DB server 103 via the network, and the processing history data 104 is held in the DB server 103.

  FIG. 2 is a diagram showing a hardware configuration of various terminals according to the embodiment of the present invention.

  In FIG. 2, the CPU 201 comprehensively controls each device connected to the system bus 204.

  The ROM 203 or the external memory 211 stores an operating system (OS) that is a control program of the CPU 201 and programs for realizing various functions described later of each server or each client.

  The RAM 202 functions as a main memory, work area, temporary save area, and the like for the CPU 201.

  The input controller 205 controls input from the input unit 209. Examples of the input unit 209 include a pointing device such as a keyboard and a mouse in a terminal such as a server or a client. Moreover, in a printing apparatus etc., a touch panel, a button, a switch, etc. are mentioned.

  The output controller 206 controls the display of the output unit 210. Examples of the output unit 210 include a CRT and a liquid crystal.

  The external memory controller 207 controls access to the external memory 211 that stores a boot program, various applications, font data, user files, edit files, printer drivers, and the like. In addition, various tables and parameters for realizing various functions of each server or each client are stored. Examples of the external memory 211 include a hard disk (HD), a floppy (registered trademark) disk (FD), a compact flash (registered trademark) connected to a PCMCIA card slot via an adapter, and smart media.

  The communication I / F controller 208 executes communication control processing with an external device via the network 214.

  A program 212 for realizing the present invention is recorded in the external memory 211 and is executed by the CPU 201 by being loaded into the RAM 202 as necessary.

  FIG. 3 is an example of a delegation setting screen in the client terminal.

  This screen is for opening the delegation setting screen (305) after the client terminal is logged in with “SHIMIZU” (300) as the login user and the delegation setting (303) of the menu screen (319) is selected.

  In this example, the login user “SHIMIZU” (300) delegates to the user with the department name “system department 1 copy” (314) and the nominated “Yamada” (315).

  Next, the task (306) is a list of tasks that can be delegated by the login user “SHIMIZU” (300). It shows that business A to business E can be delegated.

  The application authority (307) makes it possible to delegate the processing history browsing authority only to the application history. By checking this application authority (307), the history of application processing by “SHIMIZU” (300) of the delegation source and “YAMADA” (315) of the delegation destination user were replaced with SHIMIZU (300), and the application processing was performed. Make history viewable.

  The approval authority (308) makes it possible to delegate the processing history browsing authority only to the approval history. By checking this approval authority (308), the history of approval processing by “SHIMIZU” (300) of the delegation source and “YAMADA” (315) of the delegation destination user are replaced with SHIMIZU (300) for approval processing. Make history viewable.

  The delegation source (309) can select whether to delegate the processing history browsing authority of the delegation source. For example, if the application authority (307) and approval authority (308) are checked, the operation authority of the delegation source is delegated to the delegation destination, but if the delegation source (309) is unchecked, the processing history browsing authority Therefore, the delegation destination cannot refer to the history processed by the delegation source. The history processed by the delegation destination as the delegation source user can be viewed.

  Before delegation (310), it is possible to select whether or not to delegate processing history browsing authority processed before delegation. By checking before delegation (310), the delegation destination cannot refer to the delegation source processing history processed before delegation. It is possible to refer to the processing history of the delegation source processed after delegation, or the processing history of the delegation destination processed after delegation replaced with the delegation source.

  After delegation (311), it is possible to select whether or not the history processed after delegation becomes a delegation source after delegation can be viewed. If the check after delegation (311) is unchecked, the history processed at the time of delegation cannot be referred to after delegation.

  When there are a plurality of delegation destinations, between the delegation destinations (316), it is possible to select whether or not the processing history between the delegation destinations can be referred to. For example, when “Shimizu” (300) delegates to “Yamada” (315), it is assumed that a check is made between the delegates (316). In addition, when “Shimizu” (300) delegates to “Yamamoto”, it is assumed that a check is not made between the delegates (316). In this case, although “Yamamoto” (315) can refer to the processing history processed by “Yamamoto” as the delegated user “Shimizu” (300), Yamada (315) can refer to the delegated user “Shimizu” (300). 300), “Yamamoto” cannot refer to the processing history processed instead.

  Note that when the application process (307) and the approval process (308) are not checked, since the delegation itself is not performed, checks other than the application process (307) and the approval process (308) are disabled.

  Further, improvement of security by performing flexible setting of reference authority, which is the core of the present invention, includes application authority (307), approval authority (308), delegation source (309), and before delegation (310). After delegation (311), it is realized by combining each selection between delegation destinations (316).

  Here are some examples:

Example 1: Case of delegating the entire processing history If you want to delegate all processing history browsing authority of the delegation source to the delegation destination, application authority (307), approval authority (308), delegation source (309), before delegation This is realized by selecting (310).

Example 2: Case of delegating to each boss and subordinate Application authority (307), approval authority (308), delegation source (309), before delegation (310) Select and delegate between the delegates (316). Further, the subordinate (B) selects the application authority (307) and the approval authority (308) and delegates them.

  In this way, the supervisor A can see all the processing history of the delegation source, and further can see the processing history processed by the subordinate B replacing the delegation source. Also, subordinate B cannot see the processing history processed by the delegation source, nor can he see the processing history processed by superior A as the delegation source.

Example 3: A case in which a specific task is shared by multiple people. The delegation source belongs to the management department and can approve various tasks, but consider the case where only the personal computer take-out approval task is delegated. The feature of this work is that the work efficiency is improved by sharing the processing history.

  First, the delegation source selects approval authority (307), delegation source (309), and delegation destination (316) of the personal computer take-out approval work, and delegates to a plurality of persons. By doing so, only the approval process of the target business can be performed, and the processing history can be shared between the delegation destinations, so that work efficiency is improved. Also, since the pre-delegation (310) is not selected, the history processed by the delegation source before delegation is not shared, and security is high.

  When the delegation source (309) is not checked, the processing history browsing authority of the delegation source is not delegated, so that the state before delegation (310) is not selectable.

  When the decision (312) is pressed, the delegation setting registration request (411) of FIG. 4 is passed to the server, and the delegation setting registration process (412) is performed by the server, the delegation is decided, and the delegation screen (413) Is displayed in the delegation set list (313).

  In this example, it can be seen that “Shimizu” (300) has already delegated to “Sato” (317) and “Yamamoto” (318).

  When the delegation release (318) button is pressed, delegation to the target user is released.

  Specifically, in the delegation setting table shown in FIG. 8, the “cancellation flag” for which delegation is designated is changed from “0” to “1”.

  FIG. 8 is an example of a delegation setting table.

  The records in this table are created by the delegation setting registration process (412) of FIG.

  The delegation source ID (800) is an item for storing an ID that uniquely represents the delegation source user. In the example, it can be seen that User_001 and User_005 are delegating.

  The delegation destination ID (801) is an item for storing an ID that uniquely represents the delegation destination. In the example, it can be seen that User_002 is delegated from User_001 and User_005, and User_003 is delegated from User_001.

  The delegation task ID (802) is an item for storing an ID that uniquely represents a task that the delegation source delegates to the delegation destination. In the example, User_001 delegates Gyomu_A to User_002, User_001 to Gyomu_B to User_002, User_001 to Gyomu_B to User_003, and User_005 to Gyoum_C to User_002.

  The application flag (803) is an item indicating that the processing history browsing authority is delegated only for the application history, and 1 indicates that only the application history is delegated, and 0 indicates that the application history is not delegated.

  The approval flag (804) is an item indicating that the processing history browsing authority is delegated only for the approval history, and 1 indicates that only the approval history is delegated, and 0 indicates that the authorization is not delegated.

  The delegation source flag (805) is an item indicating whether to delegate the processing history browsing authority of the delegation source, where 1 represents delegation and 0 represents no delegation.

  The pre-delegation flag (806) is an item indicating whether to delegate the processing history browsing authority processed before delegation. 1 represents delegation and 0 represents no delegation.

  The post-delegation flag (807) is an item indicating whether or not the history processed after delegation becomes a delegation source after delegation can be viewed. 1 indicates that browsing is possible, and 0 indicates that browsing is impossible.

  The inter-delegation destination flag (808) is an item indicating whether or not the processing history between delegation destinations can be referred to when there are a plurality of delegation destinations. 1 indicates that reference is possible, and 0 indicates that reference is not possible.

  The release flag (809) is an item indicating whether delegation is released. 1 indicates that the delegation has been released, and 0 indicates that the delegation has not been released. 3 is set to 0 when the record is created by pressing the decision (312) button in FIG. 3, and updated when the delegation is canceled (318).

  The date of delegation (810) is an item indicating the date of delegation. In more detail, it is possible to describe not only the date of delegation but also the time.

  FIG. 4 is a flowchart until the delegation setting screen is displayed.

  Upon receiving the login screen request (402) from the client terminal (400), the server (401) performs login screen acquisition processing and returns the login screen (404).

  The client terminal makes a login authentication request (405) on the login screen (404).

  The server (401) performs login processing and menu screen acquisition processing (406), and returns the menu screen (407).

  A delegation screen request (408) is made from the menu screen (407) from the client terminal (400), a delegation screen acquisition process (409) is performed by the server (401), and a delegation screen (410) is obtained. The delegation screen is the screen of FIG.

  Next, a detailed processing flow of the delegation screen acquisition process (409) will be described with reference to FIGS.

  This process is a process in the server, and starts when a delegation screen request (408) is received from the client terminal.

  In step 1000, a business that can be referred to by the login user is extracted from the business data table.

  An example of the business data table is shown in FIG. For each business name (1100), an organization that can refer to the business is defined as a referable organization (1101). In this example, the organization that can refer to the job A is “1st system department”. Note that users belonging to each organization are stored in an organization database (not shown).

  Therefore, in step 1000, first, after identifying the organization to which the login user belongs, the work that can be referred to by the organization is extracted.

  In step 1001, a check box for designating operation authority to be delegated for each extracted task is generated. Here, a check box between the application authority (307) and the delegation destination (316) is generated for each business.

  In step 1002, the record delegated by the login user is extracted from the delegation setting table. Specifically, in FIG. 8, a record whose delegation source ID matches the ID of the login user is extracted.

  In step 1003, the delegated user is specified using the extracted record. Using the delegation destination ID of the record extracted in step 1002, the delegation destination user is specified from the user management database.

  In step 1004, a delegation set list (313) is created.

  Finally, delegation setting screen data to be displayed on the client terminal is generated and transmitted to the client terminal.

  FIG. 5 is an example of a process history search screen on the client terminal.

  In this screen, after the client terminal is logged in as “Yamada” (500) as a login user and the processing history browsing (504) on the menu screen (514) is selected, the processing history browsing screen (505) after pressing is opened. Is.

  The user operating the client terminal selects which user's processing history is searched from the target user selection (506).

  When (person) is selected, a history processed by the person or a history processed by the delegation destination delegated by the principal as a delegation source is set as a search target.

  A user other than (person) who is not displayed as (past) represents a currently delegated user, and a history processed by the delegation source or a history processed by himself / herself as a delegation source is set as a search target.

  In addition, a user whose user name is displayed as (past) is a user who has been delegated in the past (currently a user who has been delegated) and is checked after delegation (311) in FIG. 3 at the time of delegation The history that is displayed and delegated to the delegation source and processed during the delegated period is the search target.

  The search condition (507) can specify a search condition for the processing history of the user selected by the target user selection (506). In the example, it is possible to narrow down by business name and item ID.

  By pressing the search (508) button, the user can search the processing history with the conditions specified by the target user selection (506) and the search conditions (507).

  The search result (509) displays the result of the processing history searched in the search (508).

  In this example, a business name (510), a case ID (511), a case status (512), a delegate name (513) (indicating the name of the person who has been delegated), and a processor (516). it's shown. In addition, by pressing the open (516) button of each business column, it is possible to open the detailed screen of the project with the target business name (510) and the target project ID (511).

  Further, this example shows an example in which the login user (500) “Yamada” selects “Shimizu” in the target user selection.

  As a premise, the delegation source “Shimizu” has delegation settings for “Yamada” and “Sato” as delegation destinations in the operations A to C, and the inter-delegation destination (316) is designated. Shall. Business A is processed by “Yamada” instead of “Shimizu”, Business B is processed by “Sato” instead of “Shimizu”, and Business C is processed by “Shimizu” as “Shimizu” Shall.

  Accordingly, when the search result (509) is browsed, it is understood that the business A has been entrusted with “Yamada”, and “Yamada” has performed processing instead of the delegation source. In addition, it can be seen that in the business B, “Sato”, who has been delegated together with “Yamada”, has performed processing instead of the delegation source. Further, it can be seen that the business C has been processed with “SHIMIZU” as “SHIMIZU”, which is the delegation source, in which the delegating company name (513) is blank.

  Next, another example is shown in FIG.

  In this example, in the target user selection 506, a user whose user name is displayed in the past is selected. For example, this is a display example in the case where “Yamada” has browsed a task delegated by “Kato” in the past.

  The search result (509) displays the business A in which the commissioned company name (513) “Yamada” and the processor (515) “Yamada” are displayed. This displays only what “Yamada” commissioned by “Kato” in the past has processed instead of “Kato”. In other words, what "Kato" delegates to another person and that person processes instead of "Kato", and what "Kato" processes as "Kato" are not displayed.

  FIG. 6 is a flowchart until the processing history search screen is displayed.

  Upon receiving the login screen request (602) from the client terminal (600), the server (601) performs login screen acquisition processing and returns the login screen (604).

  The client terminal makes a login authentication request (605) on the login screen (604).

  The server (601) performs login processing and menu screen acquisition processing (606), and returns the menu screen (607).

  A processing history browsing screen request (608) is made from the menu screen (607) from the client terminal (600).

  The server (601) performs processing history browsing screen acquisition processing (609) to acquire the processing history browsing screen (610). The processing history browsing screen is the screen shown in FIG.

  Next, in the processing history browsing screen acquisition processing (609), the flow of processing for specifying the user to be displayed in the target user selection (506) will be described with reference to FIG.

  FIG. 9 is an example of a target user selection list acquisition flow on the processing history browsing screen.

  This is performed in the server as a part of the processing history browsing screen acquisition processing (609) of FIG.

  First, in step 900, (person) is unconditionally added to the target user selection list. This is necessary for the person to see his / her processing history.

  Next, in step 901, a target user delegation list is acquired. Specifically, the user ID of the principal is the delegation destination ID (801), the delegation setting table of FIG. 8 is searched, and the hit record is acquired as the delegation list.

  In step 902, the obtained delegation list is looped. Get the delegation list one by one in the loop.

  First, in step 903, the release flag of the acquired delegation list record is determined. If it is 0 (not released), the process proceeds to step 907. If it is 1 (released), the process proceeds to step 905.

  In step 907, it is determined whether or not there is a delegation source ID of the target record in the target user selection list. If yes, go to step 904; if not, return to the loop and get the next record. This process is a process for preventing duplicate acquisition of the already acquired user delegation source ID.

  In step 904, the delegation source ID is added to the target user selection list.

  In step 905, it is determined whether the post-delegation flag (807) is set. If it is set, the process proceeds to step 908. If it is set, the process returns to the loop to acquire the next record.

  In step 908, it is determined whether there is no delegation source ID in the target user selection list. If yes, go to Step 906; if not, return to the loop and get the next record. This process is a process for preventing duplicate acquisition of the already acquired user delegation source ID.

  In step 906, the delegation source ID is added to the target user selection list.

  After the loop ends, in step 909, the target user return list is returned and the process is terminated.

  The server uses the target user list to generate processing history browsing screen data that can be displayed on the client terminal.

  FIG. 7 is an example of a flowchart from the start of the search on the processing history search screen until the search result is displayed.

  Specifically, when the client terminal requests the server from the client terminal when the search (508) button in FIG. 5 is pressed, screen data for displaying the search result (509) on the client terminal is displayed. It is a flowchart which shows the flow of the process in the server until it produces | generates.

  In step 700, the processing history of the user selected in the target user selection (506) is searched. Specifically, the user ID (1301) in the processing history table shown in FIG. 13 is searched with the selected target user ID. The matched processing history list is temporarily stored in a memory or the like, and the final processing history list is narrowed down by the following processing.

  FIG. 13 shows an example of the processing history table.

  In the processing date (1300), the processing date when the matter is processed is recorded. In more detail, time may be recorded.

  In the user ID (1301), the user ID that processed the matter is recorded. In the example of the figure, it can be seen that “User_002”, “User_003”, and “User_005” have been processed.

  In the delegation destination ID (1302), when the designated delegation destination user processes a matter instead of the delegation source user, the delegation destination user ID is recorded. In the example of the figure, it is understood that “User — 002” and “User — 003” have been processed as delegation destination users. The blank is a case where the delegation source user himself / herself does not process the delegation destination user as a delegation destination user.

  In the business ID (1303), an ID for identifying the business is recorded.

  In the case ID (1304), an ID for specifying the case is recorded.

  In the case status (1305), contents indicating the status of the case are recorded.

  In other items (1306), various contents are recorded as necessary.

  In step 701, it is determined whether a search condition (507) is input. If it is input, the process proceeds to step 702. If it is not input, the process proceeds to step 703.

  In step 702, a record that does not match the search condition is excluded from the searched processing history list, and the process advances to step S703.

  In step 703, it is determined whether or not the user selected in the target user selection (506) is (person). If it is the principal, the process proceeds to step 713. If not, the process proceeds to step 704.

  In step 704, it is determined whether (past) is set for the user selected in the target user selection (506). If it is past delegation, the process proceeds to step 705. If it is not past delegation, the process proceeds to step 706.

  In step 705, if the user is set to (past), the history other than the history processed by the user is excluded from the search result (705). By removing, it is possible to acquire only the history processed by itself from the processing history delegated in the past. Specifically, only those that match the ID of the login user are left in the delegation destination ID (1302). After the processing, the process proceeds to step 713.

  In step 706, the delegation list is obtained from the delegation setting table (FIG. 8) and temporarily stored in the memory.

  Specifically, the user ID of the user selected in the target user selection (506) is set as the delegation source ID (800) in FIG. 8, and the user ID of the user is set as the delegation destination ID (801), and the delegation setting table is read and delegation is performed. Get a list.

  By steps 707 to S712, the processing is repeated for the number of records in the processing history list stored in the memory.

  In step 708, it is determined with reference to the delegation setting table whether or not the delegation can be viewed. If yes, go to step 710; if no, go to step 709. Specifically, it is determined whether the pre-delegation flag (806) in the delegation list record is “0” or “1”. “0” is Yes, and “1” is No.

  In step 709, the history processed by the delegation source before delegation is removed from the search result (700) (= processing history list). Specifically, a record in which the business ID (1303) in the processing history list matches the delegation business ID (802) and the processing date (1300) is older than the delegation date (810) is deleted.

  In step 710, it is determined with reference to the delegation setting table whether or not browsing is possible between delegation destinations. If yes, then go to step 712, if no, go to step 711. Specifically, it is determined whether the delegation destination flag (808) in the delegation list record is “0” or “1”. “0” is Yes, and “1” is No.

  In step 711, the history processed by the delegation destination other than itself is removed from the search result (700) (= processing history list). Specifically, a record whose delegation destination ID in the processing history list does not match the login user ID is deleted.

  Finally, in step 713, screen data for displaying on the client terminal the processing history list finally narrowed down to the search result (509) is generated.

  In the above example, all the processing history of the target user is acquired once and narrowed down by condition. However, the order of narrowing down is changed in consideration of performance depending on the job, or the conditions narrowed down at once are circulated from the circulation history (104). Needless to say, there are various patterns that can be acquired.

  Although not described in this flowchart, by determining whether or not the delegation source (309) is checked, the delegation destination user can leave or delete the processing list processed by the delegation source user. You can also Similarly, by determining whether or not the check is made after delegation (311), the delegation destination user can leave or delete the list processed by the delegation source user after delegation.

  As described above, according to the present invention, when a delegation source user delegates a task to a delegation destination user at the time of delegation, the delegation source user can set the processing history reference authority for the task so that the delegation source user can set the process history. When referring to, it is possible not to display a processing history unnecessary for security.

  It should be noted that the configuration and contents of the various data described above are not limited to this, and it goes without saying that the various data and configurations are configured according to the application and purpose.

  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.

101 Workflow server 102 Workflow client 103 DB server 104 Circulation history

Claims (10)

An information processing apparatus that can delegate the operation authority of the delegation source user to the delegation destination user in the workflow procedure,
In accordance with the request of the delegating source user, an extracting means for extracting the business that can be delegated from the business data table in which each business is defined,
Delegation destination user reception means for accepting designation of a delegation destination user for delegating the work extracted by the extraction means according to the request of the delegation source user;
In accordance with the request of the delegation source user, the authority accepting unit that accepts the designation of the operation authority to be delegated to the delegation destination user and the reference authority after the task is processed, according to the task extracted by the extraction unit;
The delegation source user, the delegation destination user received by the delegation destination user reception unit, and the operation authority and the reference authority delegated to the delegation destination user received by the authority reception unit are stored in association in the delegation setting table First storage means to
Second storage means for storing a history of processing of the business in a processing history table;
According to a user's request, it has a history display means for performing control to display a history of processing related to the work,
The history display means uses the information for identifying the requesting user and the reference authority stored in the delegation setting table to extract and display the history that can be referred to by the requesting user from the processing history table. An information processing apparatus characterized by: The authority accepting unit can set the processing history before delegation of the delegation source user to be referable to the delegation destination user,
The information processing apparatus according to claim 1, wherein the history display unit displays a history before delegation of a delegation source user who has delegated the task to the request source user. The authority accepting unit can set the processing history after delegation of the delegation source user so that the delegation destination user can refer to the history.
The information processing apparatus according to claim 1, wherein the history display unit displays a history after delegation of a delegation source user who delegated the task to the request source user. The authority accepting means can set the processing history of a plurality of delegation destination users so that the delegation destination users can refer to each other,
The information processing apparatus according to claim 1, wherein the history display unit displays a history of a delegation destination user different from the user to the request source user. The authority accepting unit can be set so that delegation of a delegation destination user can be canceled,
5. The information processing apparatus according to claim 1, wherein the history display unit does not display, to the request source user, a history regarding a task for which the user has been delegated. 6.   The information processing apparatus according to any one of claims 1 to 5, wherein the operation authority to be delegated to the delegation destination user accepted by the authority accepting unit includes an authorization authority and an application authority. . An information processing system in which a client terminal and an information processing apparatus capable of delegating the operation authority of a delegation source user to a delegation destination user in a workflow procedure are communicated via a network,
In accordance with the request of the delegating source user, an extracting means for extracting the business that can be delegated from the business data table in which each business is defined,
Delegation destination user reception means for accepting designation of a delegation destination user for delegating the work extracted by the extraction means according to the request of the delegation source user;
In accordance with the request of the delegation source user, the authority accepting unit that accepts the designation of the operation authority to be delegated to the delegation destination user and the reference authority after the task is processed, according to the task extracted by the extraction unit;
The delegation source user, the delegation destination user received by the delegation destination user accepting unit, and the operation authority and the reference authority delegated to the delegation destination user accepted by the authority accepting unit are stored in the delegation setting table in association with each other First storage means to
Second storage means for storing a history of processing of the business in a processing history table;
According to a user's request, it has a history display means for performing control to display a history of processing related to the work,
The history display means uses the information for identifying the requesting user and the reference authority stored in the delegation setting table to extract and display the history that can be referred to by the requesting user from the processing history table. An information processing system characterized by An information processing method in an information processing apparatus that includes a first recording unit and a second recording unit, and is capable of delegating an operation authority of a delegation source user to a delegation destination user in a workflow procedure,
In accordance with the request of the delegation source user, an extraction step for extracting the business that can be delegated from the business data table in which each business is defined,
In accordance with the request of the delegation source user, a delegation destination user reception step for accepting designation of a delegation destination user for delegating the work extracted by the extraction step;
According to the request of the delegation source user, the authority reception step for accepting designation of the operation authority to be delegated to the delegation destination user and the reference authority after the transaction is processed, according to the work extracted by the extraction step;
The first storage means includes the delegation source user, the delegation destination user received in the delegation destination user reception step, and the operation authority and reference authority delegated to the delegation destination user received in the authority reception step. A first storage step for storing in the delegation setting table in association with each other;
A second storage step in which the second storage means stores a history of processing of the work in a processing history table;
A history display step for performing control to display a history of processing related to the job according to a user request,
The history display step uses the information for identifying the requesting user and the reference authority stored in the delegation setting table to extract and display the history that can be referred to by the requesting user from the processing history table. An information processing method characterized by: A program that can be executed in an information processing apparatus that can delegate the operation authority of the delegation source user to the delegation destination user in the workflow procedure,
Extraction means for extracting the tasks that can be delegated according to the request of the delegating user from the business data table in which each business is defined,
Delegation destination user reception means for accepting designation of a delegation destination user for delegating the work extracted by the extraction means according to the request of the delegation source user;
Authority accepting means for accepting designation of the operation authority to be delegated to the delegation destination user and the reference authority after the work is processed, according to the request of the delegation source user, the work extracted by the extraction means;
The delegation source user, the delegation destination user received by the delegation destination user reception unit, and the operation authority and the reference authority delegated to the delegation destination user received by the authority reception unit are stored in association in the delegation setting table A first storage means,
Second storage means for storing a history of processing of the business in a processing history table;
In accordance with a user request, the information processing apparatus functions as a history display unit that performs control to display a history of processing related to the job,
The history display means uses the information for identifying the requesting user and the reference authority stored in the delegation setting table to extract and display the history that can be referred to by the requesting user from the processing history table. The program characterized by doing.   A recording medium storing the program according to claim 9 in a computer-readable manner.

Images