Form management apparatus and form management method

Abstract

It is possible to comprehensively manage rules relating to handling of data at each base.SOLUTION: The form management unit 402 determines a relationship of each item value of the form information 111 for each item of the form information 111. In addition, in a case where a change of the item value of the target item which is the item of the target form information which is any one of the plurality of pieces of form information is requested, the form management unit 402 changes the item value of the target item which is the item of the target form information in accordance with the request, and further changes the item value of the cooperation item which is the item of the other form information 111 corresponding to the target item on the basis of the item value of the target item and the above-described relationship.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a form management device and a form management method. [Background technology]

[0002] In recent years, data transfers between computers located at multiple locations are becoming common. The data being transferred may include sensitive data such as personal information, and such data must be managed appropriately in accordance with rules established by national laws and regulations. Furthermore, the locations where computers are located are often not limited to a single country, but span multiple countries. For this reason, at each location, a handling document is created that outlines the rules for handling data at that location, based on the laws and regulations of the country where the location is located, and data is managed based on this handling document.

[0003] However, because the handling documents are managed independently at each location, there is a problem in that appropriate coordination cannot be achieved regarding the transfer of data.

[0004] For example, if a change in law occurs in one of the countries where a data transfer base is located, the bases in other countries may also need to change their transaction forms in accordance with the change in law. This requires each base to check whether the transaction forms in other countries have been changed, and then determine whether to change its own transaction forms in response to the change, which, in some cases, requires the complicated process of changing its own transaction forms.

[0005] In response to this, Patent Document 1 discloses a technology that includes multiple slave station devices that monitor each piece of equipment in a plant and a master station device that manages each of the slave station devices, and when setting information is changed in a slave station device, the setting information is sent to the master station device, and the setting information is also updated in the master station device. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2012-135138 Summary of the Invention [Problem to be solved by the invention]

[0007] However, the technology described in Patent Document 1 only reflects changes to setting information in one device to other devices when the changes are made. For this reason, it is difficult to apply the technology described in Patent Document 1 to cases where it is necessary to determine whether a transaction form needs to be changed based on the relationship between transaction forms at each location, such as when a transaction form needs to be changed due to a change in law, or to make changes to another transaction form that differ from the changes made to the original transaction form based on that relationship.

[0008] An object of the present disclosure is to provide a document management device and a document management method that can reduce the effort required to manage document information that indicates rules regarding data handling at each location where data is transferred. [Means for solving the problem]

[0009] A document management device according to one aspect of the present disclosure is a document management device that manages multiple document information indicating data handling rules in each of multiple computers that transfer data between each other, and has a management unit that determines the relationship between the item values ​​of each of the multiple document information for each item of the document information, and when a request is made to change the item value of an item of target document information that is one of the multiple document information, changes the item value of the target item that is an item of the target document information in accordance with the request, and also changes the item value of linked items that are items of other document information that correspond to the target item based on the item value of the target item and the relationship. [Effects of the Invention]

[0010] According to the present invention, it becomes possible to comprehensively manage rules regarding the handling of data at each base. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of a computer system according to an embodiment of the present disclosure. [Figure 2] FIG. 10 is a diagram illustrating an example of common form item information. [Figure 3] FIG. 10 is a diagram illustrating an example of additional form item information. [Figure 4] FIG. 10 is a diagram showing an example of document item value definition information for each country. [Figure 5] FIG. 10 is a diagram illustrating an example of base information. [Figure 6] FIG. 10 is a diagram illustrating an example of each base location form information. [Figure 7] FIG. 10 is a diagram illustrating an example of base pair management information. [Figure 8] FIG. 10 is a diagram showing an example of term conversion information. [Figure 9] 10 is a flowchart illustrating an example of an initial registration process. [Figure 10] FIG. 10 is a diagram showing an example of a personal information handling screen. [Figure 11] 10 is a flowchart illustrating an example of a relationship determination process. [Figure 12] FIG. 10 is a diagram illustrating an example of a policy display screen. [Figure 13] 10 is a flowchart illustrating an example of an item relationship re-determination process. [Figure 14] 10 is a flowchart illustrating an example of a form correction process. [Figure 15] 10 is a flowchart illustrating another example of the form correction process. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the following description, "ID" and "name" are used as identification information for each element, but these can be replaced with identification information.

[0013] Fig. 1 is a diagram illustrating an example of a computer system according to an embodiment of the present disclosure. The computer system illustrated in Fig. 1 includes a plurality of country-based computers 1, a management computer 3, and a form management server 4. In the example of Fig. 1, the country-based computers 1 and the form management server 4 are connected to each other via a network 2 so that they can communicate with each other, while the management computer 3 and the form management server 4 are connected to each other without using the network 2.

[0014] The country base computers 1 are computers located at each of a plurality of geographically separated bases. In this embodiment, the country base computers 1 are located in different countries. There may be three or more country base computers 1.

[0015] The local computer 1 has a memory 11, a CPU 12, and an I / F 13. The memory 11 stores a program that defines the operation of the CPU 12 and various pieces of information used and generated by the program. The CPU 12 is a processor that realizes various functional units by reading and executing the program stored in the memory 11. The I / F 13 exchanges data with users and external devices.

[0016] The national base computer 1 has, as its functional units, a linking unit 101 and a form editing unit 102. The linking unit 101 sends and receives information to and from external devices. The form editing unit 102 edits form information 111 stored in the memory 11. The form information 111 is information that includes one or more items related to handling rules, which are rules regarding the handling of data in the national base computer 1 that has the form information 111. The handling rules are determined by the laws and regulations of the country in which the national base computer 1 is established.

[0017] The management computer 3 is a computer for managing the form management server 4, and is used by the administrator of the form management server 4. The management computer 3 has a memory 31, a CPU 32, and an I / F 33. The memory 31 records a program that defines the operation of the CPU 32 and various information used and generated by the program. The CPU 32 is a processor that realizes various functional units by reading and executing the program recorded in the memory 31. The I / F 33 exchanges data with users and external devices.

[0018] The management computer 3 has, as a functional unit, a linking unit 301. The linking unit 301 performs input / output with the administrator and transmits / receives information to / from external devices.

[0019] The form management server 4 is a form management device for managing the form information 111 of the base computers 1 in each country, and includes a memory 41, a CPU 42, an I / F 43, and a storage device 44. The memory 41 records a program that defines the operation of the CPU 42 and various information used and generated by the program. The CPU 42 is a processor that realizes various functional units by reading and executing the program recorded in the memory 41. The I / F 43 exchanges data with users and external devices. The storage device 44 is a device that non-temporarily stores information, and at least a portion of the programs and information stored in the memory 41 in FIG. 1 may be stored in the storage device 44.

[0020] The form management server 4 has, as functional units, a linking unit 401, a form management unit 402, a base pair management unit 403, an equivalence determination unit 404, and a term conversion unit 405. The memory 41 stores common form item information 411, additional form item information 412, form item value definition information for each country 413, base information 414, each base form information 415, base pair management information 416, and term conversion information 417.

[0021] In the example of FIG. 1, for convenience, the functional units of each device are described in a memory that stores a program for realizing the functional unit.

[0022] 2 is a diagram showing an example of the common form item information 411. The common form item information 411 is information indicating common form items that are items common to the form information 111 of each of the multiple national base computers 1, and includes fields 411A to 411E.

[0023] Field 411A stores an item ID that identifies a common form item. Field 411B stores the item name of the common form item. Field 411C stores the entry method for inputting (entering) the item value of the common form item. Entry methods include, for example, "selection," in which an item value is selected from predetermined candidates, and "free description," in which the user arbitrarily enters an item value. Field 411D stores the format of the item value of the common form item. Formats include, for example, "character string" and "numeric value." Field 411E stores a mandatory flag that indicates whether the common form item is mandatory as an item in the form information 111. In this embodiment, the mandatory flag indicates "◯" if the item is mandatory, and indicates "×" if it is not mandatory.

[0024] 3 is a diagram showing an example of the added form item information 412. The added form item information 412 is information indicating added form items that are items added in the base computer 1 in each country in the form information 111, and includes fields 421A to 421F.

[0025] Field 412A stores an item ID that identifies the added form item. Field 412B stores the name of the base country where the base computer 1 that added the added form item is located. Field 412C stores the item name of the added form item. Field 412D stores the entry method for entering a value into the added form item. Field 412E stores the value format of the added form item. Field 412F stores a mandatory flag that indicates whether the added form item is mandatory as an item of form information in the base country.

[0026] 4 is a diagram showing an example of the national form item value definition information 413. The national form item value definition information 413 is definition information that indicates, for each country, information that can be input as item values ​​for form information items (common form items and additional form items), and includes fields 413A to 413D.

[0027] Field 413A stores a definition ID that identifies definition information that can be input as an item value for a form information item. Field 413B stores the name of the base country to which the definition information applies. Field 413C stores an item ID that identifies the item in form information 111 to which the definition information applies. Field 413D stores definition information.

[0028] 5 is a diagram showing an example of the base information 414. The base information 414 is information relating to the base computer 1 in each country, and includes fields 414A to 414E.

[0029] Field 414A stores a base ID that identifies the base where each country base computer 1 is located. Field 414B stores a base name, which is the name of the base. Field 414C stores the country name of the base country where the base is located. Field 414D stores a server name, which is the name of each country base computer 1. Field 414E stores an address that indicates the location of each country base computer 1 on the network. The address may be an IP (Internet Protocol) address or a URL (Uniform Resource Locator).

[0030] 6 is a diagram showing an example of each base site form information 415. Each base site form information 415 is information including the form information 111 of the base computer 1 in each country, and includes fields 415A to 415G.

[0031] Field 415A stores a base ID that identifies the base where the base computer 1 is located in each country. Field 415B stores a business ID that identifies the business performed at the base. Field 415C stores a business name, which is the name of the business performed at the base. Field 415D stores an item ID that identifies an item of the form information applied to the data used in the business. Field 415E stores the item value of the item. Field 415F stores a linkage flag that indicates whether or not linkage is performed, so that changes to the item value of the item at the base are reflected in the form information at other bases. In this embodiment, the linkage flag indicates "on" if linkage is performed and "off" if linkage is not performed. Field 415G stores a constraint flag that indicates whether or not a constraint is present for the item at the base to which the linkage is performed. In this embodiment, the constraint flag indicates "enabled" if a constraint is present and "-" if no constraint is present. Constraints are stipulated, for example, by the laws and regulations of the base country and indicate, for example, information that is permitted as an item value or information that is not permitted as an item value.

[0032] 7 is a diagram showing an example of the base pair management information 416. The base pair management information 416 is information for managing a plurality of (two in this embodiment) bases (base computers 1 in each country) that transfer data to each other, and includes fields 416A to 416H.

[0033] Field 416A stores a pair ID that identifies the base pair, which is the two bases (base computers 1 in each country) between which data is transferred. Field 416B stores a base ID that identifies the base from which data is being transferred. Field 416C stores a business ID that identifies the business performed at the base from which data is being transferred. Field 416D stores a destination base ID that identifies the base to which data is being transferred. Field 416E stores a destination business ID that identifies the business performed at the base to which data is being transferred. Field 416F stores an item ID that identifies an item of report information related to the data to be transferred. Field 416G stores relationship information that indicates the relationship between the item value of the item with the item ID at the source base and the item value of the item with the item ID at the destination base. Field 416H stores a reflection policy for reflecting the item value of the item with the item ID in the report information of another base.

[0034] 8 is a diagram showing an example of the term conversion information 417. The term conversion information 417 is information for converting different terms at each location, and includes fields 417A to 417C.

[0035] Field 417A stores a term ID that identifies a term. Field 417B stores the term. Field 417C stores translations corresponding to the term in each country. In the example of Figure 8, the term is Japanese and the translations are English, French, and Chinese, but the term may be in another language such as English, and the translations are not limited to these examples.

[0036] FIG. 9 is a flowchart for explaining an example of the initial registration process for registering each base form information 415.

[0037] In the initial registration process, the form management unit 402 of the form management server 4 first transmits the common form item information 411 to each of the base computers 1 in each country (step S101).

[0038] When the collaboration unit 101 of each country base computer 1 receives the common form item information 411, the form editing unit 102 displays the common form item information 411 and instructs the administrator of the country base computer to create form information. The administrator inputs the item values ​​of the common items indicated in the common form item information 411, and additional items and their item values ​​as necessary, into the country base computer 1. The form editing unit 102 creates form information 111 based on the input contents and sends it to the form management server 4. The collaboration unit 401 of the form management server 4 receives the form information 111 from each country base computer 1 (step S102).

[0039] The report management unit 402 checks whether there is any item-added report information in which items other than the common items included in the common report item information 411 have been added among the multiple report information 111 received from the respective country base computers 1 (step S103).

[0040] If the item addition form information exists (step S103: Yes), the form management unit 402 checks whether there are multiple pieces of item addition form information (step S104). If the item addition form information does not exist (step S103: No), step S104 and the following steps S105 to S108 are skipped.

[0041] If there is a plurality of pieces of item-added form information (step S104: Yes), the equivalence determination unit 404 determines the equivalence between the added form items added to each of the plurality of pieces of item-added form information (step S105). For example, the equivalence determination unit 404 determines that the added form items are equivalent if the item names of the added form items are expressed by the same term using the term conversion information 417. Alternatively, the equivalence determination unit 404 may determine that the added items are equivalent if the item names are expressed by the same term and have the same format. Note that if there is not a plurality of pieces of item-added form information, the processes of step S105 and the following steps S106 to S107 are skipped.

[0042] Then, the form management unit 402 determines whether or not there are additional form items that are determined to be equivalent in the form information 111 of all the base computers 1 in each country (step S106).

[0043] If there are additional form items that are determined to be equivalent in all of the form information 111 (step S106: Yes), the form management unit 402 adds the additional form items that are determined to be equivalent to the common form item information 411 (step S107). If there are no additional form items that are determined to be equivalent in all of the form information 111 (step S106: No), the processing of step S107 is skipped.

[0044] The form management unit 402 adds the additional form item to the additional form item information 412 (step S108). However, if the additional form item is determined to be equivalent in all of the form information 111 in step S106, it is not added to the additional form item information 412.

[0045] The form management unit 402 generates each site form information 415 based on the form information 111 from each site computer 1 in each country (step S109), and the process ends.

[0046] In the initial registration process, the form management unit 402 may notify information that can be entered as the item value of each item in the form information 111 by sending national form item value definition information 413 in addition to the common form item information 411. The form management unit 402 may also check whether the item value of each item in the form information 111 is included in the definition information indicated in the national form item value definition information 413, and if not included in the definition information, may request the national base computer 1 corresponding to that form information 111 to correct the form information 111.

[0047] 10 is a diagram showing an example of a personal information handling screen for setting up the linkage of the form information 111. The personal information handling screen is displayed, for example, on the base computer 1 in each country.

[0048] The personal information handling screen 500 shown in FIG. 10 includes a base pair information input area 501 and a relationship determination button 502.

[0049] The base pair information input area 501 is an interface for inputting information about the base pair. In the example of FIG. 10, the information about the base pair includes a management ID, the name of the business performed at the base from which the data is being transferred, the department in charge of performing the business, the base country of the base from which the data is being transferred, whether or not there has been a transfer, and the base country of the base to which the data is being transferred. The relationship determination button 502 is a button for requesting the execution of a relationship determination process that determines the relationship between an item in the form information 111 of the base country from which the data is being transferred and an item in the form information 111 of the base country to which the data is being transferred. When the relationship determination button 502 is pressed, the collaboration unit 101 sends a relationship determination request to the form management server 4, requesting the execution of the relationship determination process.

[0050] FIG. 11 is a flowchart illustrating an example of the relationship determination process.

[0051] In the relationship determination process, the base pair management unit 403 receives a relationship determination request from the base computer 1 of each country that is the data transfer source via the collaboration unit 101 (step S201). The relationship determination request includes transfer destination information that specifies the base computer 1 of each country that is the transfer destination to which the data is to be transferred.

[0052] The base pair management unit 403 adds information about both bases that make up the relocation pair to the base pair management information 416 based on the relocation destination information in the relationship determination request (step S202).

[0053] Based on each base report information 415, the base pair management unit 403 identifies any of the items in the report information 111 of the source base that have a linkage flag set to "on", and determines the relationship between the item value of the identified target item and the item value of the linkage item, which is an item in the report information 111 of the linked base (step S203).

[0054] The base pair management unit 403 determines whether the relationship is "match," "inclusion," "partial match," or "unrelated" (step S204). The relationship between the target item and the linked item is indicated as "match" if the item value of the target item matches the item value of the linked item, "inclusion" if the item value of the target item and the item value of the linked item are in an inclusive relationship, and "partial match" if the item value of the target item and the item value of the linked item partially match. Furthermore, the base pair management unit 403 determines the relationship between the target item and the linked item to be "unrelated" if the relationship is other than "match," "inclusion," or "partial match."

[0055] For example, if the item value of the target item is "personal information" and the item value of the linked item is "sensitive personal information," the relationship between them is "inclusion." Also, if the item value of the target item is "anonymously processed information" and the item value of the linked item is "pseudonymously processed information," the relationship between them is "partial match."

[0056] If the relationship is "matched", the base pair management unit 403 sets the reflection policy of the form information 111 of the base computer 1 of each country of the transfer destination to "automatic" which automatically corrects (step S205).

[0057] If the relationship is "inclusive", the base pair management unit 403 sets the reflection policy of the form information 111 of the base computer 1 of each country to "partial automatic", which automatically corrects part of the information (step S206).

[0058] Furthermore, if the relationship is "partial match," the base pair management unit 403 sets the reflection policy of the report information 111 of the destination country base computer 1 to "response request," which proposes corrections to the user of the destination country base computer 1 (step S207).

[0059] Also, if the relationship is "unrelated," the base pair management unit 403 sets the reflection policy of the report information 111 of the destination country base computer 1 to "not implemented," which does not make any corrections and maintains the current item values ​​(step S208).

[0060] When any of steps S204 to S208 is completed, the base pair management unit 403 determines whether or not the reflection policy has been set for all items whose collaboration flags are "on" (step S209).

[0061] If a reflection policy has not been set (step S209: No), the base pair management unit 403 returns to the processing of step S203. On the other hand, if a reflection policy has been set (step S209: Yes), the base pair management unit 403 transmits reflection policy information indicating the reflection policy of each target item to the base computer 1 in each country that is part of the base pair (step S210).

[0062] When the collaboration unit 101 of each country base computer 1 receives the reflection policy information, the base pair management unit 403 displays the reflection policy information and instructs the administrator of each country base computer 1 to judge the validity of the reflection policy. The administrator inputs the validity judgment result to the country base computer. If the reflection policy is not valid, the judgment result includes a request to change the reflection policy. The form editing unit 102 creates the input judgment result and sends it to the form management server 4. The collaboration unit 401 of the form management server 4 receives the judgment result from each country base computer 1 and checks whether the judgment result includes a change request (step S211).

[0063] If a change request is not included (step S211: No), the base pair management unit 403 reflects the reflection policy set for each target item in the processing of steps S205 to S208 in the base pair management information 416 (step S212), and terminates the processing. On the other hand, if a change request is included (step S211: Yes), the base pair management unit 403 reflects a change reflection policy obtained by changing the reflection policy set for each target item in the processing of steps S205 to S208 in accordance with the change request in the base pair management information 416 (step S213), and terminates the processing.

[0064] 12 is a diagram showing an example of a policy display screen that displays the reflection policy information. The policy display screen is displayed, for example, on the base computer 1 in each country.

[0065] The policy display screen 600 shown in FIG. 12 includes a basic information display section 601 and a detailed information display section 602 .

[0066] The basic information display section 601 is a section that displays basic information such as the management ID, the business name of the business, the base country of the relocation destination, etc. The detailed information display section 602 is a section that displays detailed information about each item in the form information 111. The detailed information indicates the entry content, which is the item value, whether or not there is a link, the relationship with the linked item, the reflection policy for the linked item, the linked item, and the type of value.

[0067] FIG. 13 is a flowchart for explaining an example of the item relationship re-determination process that is performed when updating the definition information of the items in the form information 111.

[0068] In the item relationship re-determination process, the form management unit 402 receives an update request to update the definition information of item values ​​from the base computer 1 in each country via the collaboration unit 401 (step S301). The update request includes information specifying the item whose definition information is to be updated and the update content of the definition information. The update content indicates, for example, the type of item value to be added to or deleted from the definition information.

[0069] Based on the base pair management information 416, the report management unit 402 determines whether there is a destination computer, which is a national base computer 1 (a national base computer 1 that is part of the base pair of the sender of the update request) to which the data of the requesting computer, which is the national base computer 1 that sent the update request, is to be transferred (step S302).

[0070] If a transfer destination computer exists (step S302: Yes), the form management unit 402 determines whether or not there is a linked item that is linked to the item requested to be updated in the update request, based on each base form information 415 (step S303).If a transfer destination computer does not exist (step S302: No), the form management unit 402 updates the national form item value definition information 413 in accordance with the update request (step S307), and ends the process.

[0071] If a linked item exists (step S303: Yes), the form management unit 402 determines whether the type of item value after the update is outside the item value definition information that can be input as the item value of the item, based on the national form item value definition information 413 (step S304).If a linked item does not exist (step S303: No), the form management unit 402 updates the national form item value definition information 413 in accordance with the update request (step S307) and ends the process.

[0072] If the item value does not conform to the definition information (step S304: Yes), the report management unit 402 sends warning information to the requesting computer indicating that the item value update violates the definition information, requests that the item value type be corrected (step S305), and terminates the processing.

[0073] If the item does not fall outside the item value definition information (step S304: No), the form management unit 402 reassess the relationship between the item to be updated and the linked item, and changes the reflection policy of the linked item (step S306).Then, the form management unit 402 updates the national form item value definition information 413 in accordance with the update request (step S307), and ends the process.The process of reassessing the relationship and changing the reflection policy in step S306 is the same as the process in steps 203 to S213 in FIG.

[0074] FIG. 14 is a flowchart illustrating an example of a form correction process that is performed when an item value is changed.

[0075] In the form correction process, the form management unit 402 receives a correction request to correct an item value from the local base computer 1 via the collaboration unit 401 (step S401). The correction request includes information specifying the item to be corrected, which is the item whose item value is to be corrected, and information indicating the item value after correction.

[0076] Based on each base report information 415 and base pair management information 416, the report management unit 402 determines whether there is a linked item that is linked to the item to be modified and whether the reflection policy of that linked item is "automatic" (step S402).

[0077] If a linked item exists and the reflection policy is "automatic" (step S402: Yes), the form management unit 402 checks the constraint flag of the linked item based on each site form information 415 to check whether a constraint condition exists for the linked item (step S403). Note that if a linked item exists and the reflection policy is not "automatic" (step S402: No), the process proceeds to the process in FIG. 15.

[0078] If a constraint condition exists (step S403: Yes), the form management unit 402 determines whether the modification in the linked item in response to the modification request (modification equivalent to the target item) satisfies the constraint condition (step S404).

[0079] If there are no constraints (step S403: No), or if the constraints are met (step S404: Yes), the report management unit 402 corrects both the item to be corrected in the report information 111 and the item values ​​of its associated items to the item values ​​corrected by the correction request (step S405), and terminates the processing.

[0080] If the constraints are not met (step S404: No), the report management unit 402 sends violation reason information indicating that the modification request violates the constraints to the country base computer 1 that sent the modification request (step S406), and terminates the processing.

[0081] FIG. 15 is a flowchart for explaining another example of the form correction process that is performed when an item value is changed.

[0082] In the processing of Figure 14, if a linked item exists and the reflection policy is not "automatic" (step S402: No), the report management unit 402 determines, based on each base report information 415 and base pair management information 416, whether a linked item exists that is linked to the item to be modified and whether the reflection policy of that linked item is "partially automatic" (step S501).

[0083] If a linked item exists and the reflection policy is "partially automatic" (step S501: Yes), the report management unit 402 determines whether the item value after correction due to the correction request and the item value before correction are in an inclusive relationship (step S502).

[0084] If there is an inclusion relationship (step S502: Yes), the report management unit 402 determines, based on each base report information 415, whether the corrected item value is a narrower correction that is included in the item value before correction (step S503).

[0085] If the correction is to narrow the range (step S503: Yes), the form management unit 402 corrects the item values ​​of the linked items that are linked to the item to be corrected to the corrected item values ​​in the correction request (step S504) based on the each-site form information 415 and the site pair management information 416. Then, the form management unit 402 corrects the form information 111 in accordance with the correction request (step S505) and ends the process.

[0086] If the correction is not to narrow the range (step S503: No), the form management unit 402 sends a response request to the cooperating country base computer 1 to request that the form information 111 be corrected. Thereafter, the form management unit 402 receives a correction instruction in response to the response request from the cooperating country base computer 1, and corrects the item value of the linked item in accordance with the correction instruction (step S506). Thereafter, the form management unit 402 executes the process of step S505.

[0087] Furthermore, if a linked item exists and the reflection policy is not "partially automatic" (step S501: No), the report management unit 402 determines, based on each base report information 415 and base pair management information 416, whether a linked item exists that is linked to the item to be corrected and whether the reflection policy of that linked item is "response request" (step S507).

[0088] If a linked item exists and the reflection policy is "response request" (step S501: Yes), the form management unit 402 executes the process of step S506. If a linked item exists and the reflection policy is "response request" (step S501: No), the form management unit 402 determines that there is no linked item or that even if there is a linked item, the correction policy is "not implemented", so that there is no need to correct the linked item, and executes the process of step S505.

[0089] As described above, in this embodiment, the form management unit 402 determines the relationship between the item values ​​of each item in the form information 111 for each item in the form information 111. Furthermore, when a request is made to change the item value of an item in target form information, which is one of a plurality of pieces of form information, the form management unit 402 changes the item value of the target item, which is an item in the target form information, in accordance with the request, and further changes the item value of the linked item, which is an item in other form information 111 that corresponds to the target item, based on the item value of the target item and the above-mentioned relationship. In this case, it is possible to modify the item values ​​based on the relationship between the item to be modified and the linked items that are linked to it, making it possible to comprehensively manage rules regarding data handling at each location.

[0090] Furthermore, in this embodiment, if the relationship is "match," the form management unit 402 makes a change to the field value of the linked field equivalent to the field value of the target field; if the relationship is "unrelated," the current field value of the linked field is maintained; if the relationship is "included," if the field value of the target field after the change is included in the field value before the change, the form management unit 402 makes a change to the field value of the linked field equivalent to the field value of the target field; and if the relationship indicates "partial match," it proposes a change to the field value of the linked field to the computer corresponding to the form information of the linked field. In this case, it is possible to modify the field value of the linked field appropriately according to the relationship.

[0091] In this embodiment, when the form management unit 402 receives a correction request for correcting the form item value definition information for each country 413, it re-evaluates the relationships between items in response to the correction request. In this case, it becomes possible to appropriately set the relationships between items.

[0092] The above-described embodiments of the present disclosure are merely illustrative examples of the present disclosure, and are not intended to limit the scope of the present disclosure to these embodiments alone. Those skilled in the art may implement the present disclosure in various other forms without departing from the scope of the present disclosure. [Explanation of symbols]

[0093] 1: Country-based base computer 2: Network 3: Management computer 4: Report management server 11: Memory 12: CPU 13: I / F 31: Memory 32: CPU 33: I / F 41: Memory 42: CPU 43: I / F 44: Storage device 101: Collaboration unit 102: Report editing unit 111: Report information 301: Collaboration unit 401: Collaboration unit 402: Report management unit 403: Base pair management unit 404: Equivalence determination unit 405: Term conversion unit

Claims

1. A document management device that manages a plurality of document information items each including one or more items related to a data handling rule in each of a plurality of computers involved in data transfer, comprising: A document management device having a management unit that determines the relationship between the item values ​​of each of the multiple document information items for each item of the document information, and when a request is made to change the item value of an item of target document information that is one of the multiple document information items, changes the item value of the target item that is an item of the target document information in accordance with the request, and changes the item value of linked items that are items of other document information that correspond to the target item based on the item value of the target item and the relationship.

2. The document management device according to claim 1 , wherein the management unit, when the relationship indicates a match, makes a change to the item value of the linked item equivalent to the item value of the target item.

3. The document management device according to claim 1 , wherein the management unit maintains the current item value of the linked item when the relationship indicates that the items are unrelated to each other.

4. The document management device of claim 1, wherein, when the relationship indicates an inclusion relationship, if the item value of the target item after the change is included in the item value before the change, the management unit makes a change to the item value of the linked item equivalent to the item value of the target item, and if the item value of the target item after the change is not included in the item value before the change, it sends information suggesting a change to the item value of the linked item to the computer corresponding to the other document information.

5. The document management device according to claim 1 , wherein the management unit transmits information proposing a modification of the target item to the computer corresponding to the other document information when the relationship indicates a partial match.

6. The document management device of claim 1, wherein the management unit, when a constraint condition exists for the target item, determines whether the item value of the target item after the change satisfies the constraint condition, and if the constraint condition is satisfied, changes the item value of the linked item based on the relationship, and if the constraint condition is not satisfied, sends information suggesting a modification to the change of the target item to the computer corresponding to the target document information.

7. The document management device of claim 1, wherein the management unit manages definition information, which is information that can be set as an item value for each item of the document information, and when a correction request is received requesting correction of the definition information, the management unit re-evaluates the relationship in accordance with the correction request.

8. 2. The document management device according to claim 1, wherein the plurality of computers are provided in different countries.

9. 1. A form management method by a form management device that manages a plurality of form information items including one or more items related to a data handling rule in each of a plurality of computers involved in data transfer, comprising: determining a relationship between the item values ​​of each of the plurality of pieces of form information for each item of the form information; A document management method in which, when a request is made to change the item value of an item of target document information, which is one of the plurality of document information, the item value of the target item, which is an item of the target document information, is changed in accordance with the request, and the item value of a linked item, which is an item of other document information corresponding to the target item, is changed based on the item value of the target item and the relationship.

Images