First system, system, method, data processing method, program

Abstract

To provide an information processing system in which a first system executes processing related to electronic data according to a response from a second system.SOLUTION: According to an aspect of the present invention, there is provided an information-processing system 100 including a first system 10 capable of communicating with a terminal 50 and a second system 30 via a network, wherein the first system includes a communication unit that receives an electronic file from the terminal, a process-executing unit that requests the second system to perform a process on the electronic file received by the communication unit, and a data-managing unit that performs the process on the electronic file in accordance with a response from the second system to a process-change request received from the terminal.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing system, a system, a data processing method, and a program. [Background technology]

[0002] There is known a method for managing electronic data by assigning identification information to the data. There is also known a processing method in which a first system that manages electronic data transmits the electronic data to a second system for processing.

[0003] A technology has been devised for registering an electronic document on a server based on identification information (see, for example, Patent Document 1). Patent Document 1 discloses a system in which an image forming device acquires identification information of scanned document data, determines the appropriateness of the scanned document data based on information corresponding to the identification information, and, if the scanned document data is appropriate, a server registers the electronic document corresponding to the scanned document data as approved. Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology, there is a problem that the first system does not execute processing related to the electronic data in response to a response from the second system. For example, when the first system receives a request from a user to change the processing that the second system performs on the electronic data, the appropriate processing that the first system should perform varies depending on the state of the electronic data in the second system.

[0005] In view of the above-mentioned problems, it is an object of the present invention to provide an information processing system in which a first system executes processing related to electronic data in response to a response from a second system. [Means for solving the problem]

[0006] In view of the above-mentioned problems, the present invention provides an information processing system having a first system capable of communicating with a terminal device and a second system via a network, the information processing system comprising: The first system is characterized by having a communication unit that receives electronic data from the terminal device, a processing execution unit that requests a second system to process the electronic data received by the communication unit, and a data management unit that executes processing related to the electronic data in response to a response from the second system to a processing change request received from the terminal device. [Effects of the Invention]

[0007] An information processing system can be provided in which the first system performs processing on the electronic data in response to a response from the second system. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an outline of a method for managing electronic data performed by a document management system. [Figure 2] FIG. 1 is a system configuration diagram of an example of an information processing system. [Figure 3] FIG. 2 is a diagram illustrating a hardware configuration of an example of a computer. [Figure 4] 1 is a functional block diagram of an example illustrating functions of a document management system, an electronic contract system, and a terminal device, divided into blocks. [Figure 5] FIG. 4 is a diagram illustrating an example of document information stored in a document information storage unit. [Figure 6] FIG. 2 is a diagram illustrating an example of metadata stored in a metadata storage unit. [Figure 7] FIG. 4 is a diagram illustrating an example of workflow information stored in a workflow information storage unit. [Figure 8] 1 is a diagram showing an example of document information stored in a document information storage unit of an electronic contract system. FIG. [Figure 9]FIG. 2 is a diagram showing an example of status information stored in a status information storage unit of the electronic contract system. [Figure 10] 10 is a diagram illustrating an example of status change response information stored in a status change response information storage unit. FIG. [Figure 11A] FIG. 10 is a sequence diagram illustrating an example of a procedure in which a document management system reflects a status change in an electronic contract system. [Figure 11B] FIG. 10 is a sequence diagram illustrating an example of a procedure in which a document management system reflects a status change in an electronic contract system. [Figure 12] FIG. 10 is a diagram showing an example of metadata after the process in step S6. [Figure 13] FIG. 10 is a diagram showing an example of metadata after the process in step S17. [Figure 14] FIG. 10 is a diagram showing an example of metadata after the process in step S20. [Figure 15] 10A and 10B are diagrams illustrating an example of a document registration screen and a metadata setting screen displayed on a terminal device. [Figure 16] FIG. 10 is a diagram showing an example of a search screen displayed by the terminal device. [Figure 17] FIG. 10 is a diagram showing an example of a document display screen displayed by a terminal device. [Figure 18] FIG. 10 is a diagram illustrating an example of a status setting screen displayed on the terminal device. [Figure 19] FIG. 10 is a diagram showing a list of exemplary processes that the document management system performs depending on the withdrawal result. [Figure 20] FIG. 10 is a flowchart illustrating an example of processing performed by the document management system on a document or status in response to a response (withdrawal result) from the electronic contract system. [Figure 21] 10A and 10B are diagrams illustrating exemplary document display screens by status displayed on a terminal device. [Figure 22] FIG. 10 is a flowchart illustrating an example of processing of the electronic contract system in response to a withdrawal request. DETAILED DESCRIPTION OF THE INVENTION

[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An information processing system and a data processing method performed by the information processing system will be described below as an example of an embodiment of the present invention with reference to the drawings.

[0010] <Outline of operation> FIG. 1 is a diagram outlining the method of managing electronic data performed by the document management system 10. The document management system 10 stores and processes various documents. The document management system 10 also executes a series of processes (workflows) on documents, and may request part of the processes from the electronic contract system 30. The electronic contract system 30 handles contract negotiations with business partners and the assignment of electronic signatures. In this system configuration, the document management system 10 of this embodiment manages documents by associating them with each other before processing by the electronic contract system 30 and after processing by the electronic contract system 30. Using this association, a user can request the document management system 10 to cancel processing of a document by the electronic contract system 30, for example. The document management system 10 then executes document-related processing in response to a response from the electronic contract system 30. This overview will be explained below.

[0011] (1) A user operates the terminal device 50 to create a contract as an example of a document, and uploads the contract to the document management system 10 (an example of a first system) from the terminal device 50. The document management system 10 stores the contract and manages it in the document management system 10 with the identification information "001."

[0012] (2) When the predetermined conditions for starting a workflow are met, the document management system 10 executes the workflow. The workflow sends the document to the electronic contract system 30 (an example of a second system) and obtains, as a return value, the identification information "00A" managed on the electronic contract system 30. The document management system 10 generates metadata that associates "001" with "00A."

[0013] (3) A user makes a request to the document management system 10 to cancel the processing of a document managed by, for example, "001" by the electronic contract system 30 (an example of a change in processing).

[0014] (4) Upon receiving a request to withdraw the process, the document management system 10 changes the document status to "Withdrawal Request in Progress." A withdrawal request is a request to withdraw the process by the electronic contract system 30. In other words, a user can request the electronic contract system 30 to change the process by changing the status in the document management system 10. If a change in status is a condition for starting a workflow, the document management system 10 executes the workflow. The workflow refers to the metadata, converts the identification information "001" to "00A," and requests the electronic contract system 30 to withdraw the document "00A."

[0015] (5) The electronic contract system 30 returns a response according to the status of the document identified by "00A" to the document management system 10. The response is determined based on the status of the document in the electronic contract system 30.

[0016] (6) The document management system 10 executes processing on the document identified by "001" according to this response, i.e., the status of the document identified by "00A" in the electronic contract system 30. For example, the document management system 10 deletes the document or changes its status.

[0017] Therefore, by managing the identification information of a document in the document management system 10 in association with the identification information of the electronic contract system 30, the document management system 10 can reflect the processing (change in status) performed by the user on a document in the document management system 10 in the electronic contract system 30. Furthermore, the document management system 10 performs processing related to the document according to the status of the document in the electronic contract system 30 (according to the response from the electronic contract system 30), so it is possible to execute processing without discrepancies with the progress of processing of the document by the electronic contract system 30.

[0018] <Terminology> Electronic data is data used for computer processing and is an "electromagnetic record" stored on an electromagnetic recording medium. In this embodiment, electronic data is described using the term "document." A document is also called a document. However, it does not necessarily have to contain text. A document may be any data that is readable by a computer. Electronic data may also be image data such as video or still images.

[0019] Processing means information processing, and refers to the calculation, classification, collation, or other processing of information expressed by numbers, characters, physical quantities, etc. by a computer. The electronic data does not have to be changed by the second system.

[0020] A workflow refers to a predetermined series of processes that a system performs on data in order, or a series of processes.

[0021] A request to change a process refers to a change to a process that has been requested for some reason, such as interrupting, pausing, or withdrawing the process, or changing the content of the process, etc. In this embodiment, a withdrawal request will be described as an example, but the request is not limited to a withdrawal request.

[0022] The response from the second system is information indicating at least one of how the request from the document management system was processed and the processing that the document management system 10 should perform.

[0023] The state of a document (electronic data) is information associated with the document in the electronic contract system 30. The state may be, for example, the progress of processing, the result of processing (success, failure), etc. In this embodiment, the state is explained using the term status.

[0024] The processing related to electronic data may be any processing related to at least either electronic data or metadata, such as deleting, modifying, or transmitting electronic data, or deleting, modifying, or transmitting metadata.

[0025] <System configuration example> Next, the system configuration of the information processing system 100 will be described with reference to Fig. 2. Fig. 2 is a system configuration diagram of an example of the information processing system 100.

[0026] The information processing system 100 has at least a document management system 10. The information processing system 100 may further have an electronic contract system 30. The document management system 10 and the electronic contract system 30 are communicatively connected via a network. The document management system 10 and the electronic contract system 30 do not need to be connected at all times, but may be connected as needed. In addition, the document management system 10 accepts a connection from a terminal device 50. The document management system 10 and the terminal device 50 do not need to be connected at all times, but may be connected as needed. In addition, the electronic contract system 30 accepts a connection from the terminal device 50. The electronic contract system 30 and the terminal device 50 do not need to be connected at all times, but may be connected as needed.

[0027] The document management system 10 is one or more information processing devices. The document management system 10 provides a service for managing documents. The document management system 10 assigns metadata to documents, enabling efficient document searches using the metadata. The document management system 10 also provides a service for processing documents using a workflow function before or after document management begins. Metadata is data about certain data, and refers to additional data about the data itself that accompanies the data. Details will be provided later.

[0028] The workflow function also allows processing by a second system (illustrated as an electronic contract system 30 in FIG. 2). Conventionally, the document management system 10 did not manage the identification information of documents processed by other systems. In this embodiment, as described in FIG. 1, the information processing system 100 manages the identification information of documents in the information processing system 100 and the electronic contract system 30 in association with each other.

[0029] The document management system 10 may be implemented using cloud computing or a single information processing device. Cloud computing refers to a form in which resources on a network are used without regard to specific hardware resources. The document management system 10 may exist on the Internet or on-premise.

[0030] The electronic contract system 30 is one or more information processing devices. The electronic contract system 30 processes electronic contracts. There is no set definition of an electronic contract system 30, but it is a system that allows contracts to be concluded by adding an electronic signature and timestamp to electronic data (PDF format contracts) over the Internet, instead of stamping a seal on a paper contract. In addition to concluding contracts, the system can also store concluded contracts, search for contracts, and link with other systems. In some cases, the electronic contract system 30 is equipped with a workflow function to allow approvals and requests for approval.

[0031] An example of how a digital signature is created is as follows: Person A, who wants to sign a document, uses a hash function to create a hash value of the document and encrypts the hash value using his private key. Person A attaches his digital signature to the document and saves it. Person B, who wants to know whether the document has been tampered with, decrypts the digital signature using Person A's public key, obtains the document's hash value, and compares the two. If the two match, it is proven that the document was created by the owner of the private key corresponding to the public key, and that it has not been tampered with by anyone other than the owner of the private key. Person B also verifies whether the public key is legitimate by performing certificate verification. Certificate verification involves querying the certificate authority to verify the certificate authority's signature included in the public key.

[0032] The electronic contract system 30 is an example of a second system used in the workflow by the document management system 10. The second system may be any of the following: -Time stamp system: A time stamp is a piece of time-certifying information that can be used by a third party to prove that electronic data existed at a certain point in time and has not been tampered with since then, maintaining its evidential value. While electronic certification guarantees that a document has not been tampered with, it can also guarantee that electronic data existed at a certain point in time. Noise removal system: A noise removal system is a system that removes noise from a document. Noise refers to unnecessary information other than necessary information such as signatures. Digital watermarking system: A digital watermarking system is a system that adds a digital watermark to a document. Digital watermarking is a technology that embeds relevant information in data such as images, videos, and audio in a form that is imperceptible to humans. The embedded information can be detected using specialized software.

[0033] The electronic contract system 30 may be realized by cloud computing or by a single information processing device. The electronic contract system 30 may exist on the Internet or on-premise.

[0034] The terminal device 50 is a general-purpose computer that communicates with the document management system 10 and the electronic contract system 30. A web browser runs on the terminal device 50 and displays various screens based on screen information received from the document management system 10 or the electronic contract system 30. A user can register documents, execute workflows, search for documents, etc. in the document management system 10. In addition, a user can search for and view documents with electronic signatures in the electronic contract system 30.

[0035] The terminal device 50 may be, for example, a PC (Personal Computer), a smartphone, a tablet terminal, a PDA (Personal Digital Assistant), etc., as long as it can run a web browser. Note that the terminal device 50 is not limited to a web browser, and may also run dedicated apps for the document management system 10 and the electronic contract system 30.

[0036] The terminal device 50 may also be an electronic device such as a multifunction peripheral (or MFP (multifunction peripheral / product / printer)) or an electronic whiteboard. For example, the multifunction peripheral can replace the terminal device 50 by transmitting image data (documents) scanned by the multifunction peripheral to the document management system 10. Alternatively, the terminal device 50 may be a video conference terminal, digital signage, projector, or the like. In the case of an electronic whiteboard, the terminal device 50 transmits handwritten data to the document management system 10. In the case of a video conference terminal, the terminal device 50 transmits voice data to the document management system 10. <Hardware configuration> <<Document management system, electronic contract system, terminal device>> The document management system 10, the electronic contract system 30, and the terminal device 50 are realized, for example, by a computer 500 having the hardware configuration shown in Fig. 3. Fig. 3 is a hardware configuration diagram of an example of the computer 500. As shown in Fig. 3, the computer 500 is constructed by a computer and includes a CPU 501, a ROM 502, a RAM 503, an HD 504, an HDD (Hard Disk Drive) controller 505, a display 506, an external device connection I / F (Interface) 508, a network I / F 509, a bus line 510, a keyboard 511, a pointing device 512, a DVD-RW (Digital Versatile Disk Rewritable) drive 514, and a media I / F 516.

[0037] Of these, the CPU 501 controls the overall operation of the computer 500. The ROM 502 stores programs, such as an IPL, used to drive the CPU 501. The RAM 503 is used as a work area for the CPU 501. The HD 504 stores various data, such as programs. The HDD controller 505 controls the reading and writing of various data from and to the HD 504 under the control of the CPU 501. The display 506 displays various information, such as a cursor, menus, windows, characters, or images. The external device connection I / F 508 is an interface for connecting various external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory or the image forming apparatus 20. The network I / F 509 is an interface for data communication using a communication network. The bus line 510 is an address bus, a data bus, or the like, for electrically connecting the components, such as the CPU 501, shown in FIG. 3.

[0038] The keyboard 511 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The optical drive 514 controls reading and writing of various data from an optical storage medium 513, which is an example of a removable storage medium. The optical storage medium is a CD, a DVD, Blu-Ray (registered trademark), etc. The media I / F 516 controls reading and writing (storing) of data from a storage medium 515, such as a flash memory.

[0039] <About the function> Next, the functions of the document management system 10, the electronic contract system 30, and the terminal device 50 will be described with reference to Fig. 4. Fig. 4 is an example of a functional block diagram that explains the functions of the document management system 10, the electronic contract system 30, and the terminal device 50 by dividing them into blocks.

[0040] <<Document Management System>> The document management system 10 includes a communication unit 11, a screen generation unit 12, a data management unit 13, a workflow control unit 14, a process execution unit 15, an HTML information storage unit 21, a document information storage unit 22, a metadata storage unit 23, and a workflow information storage unit 24. These functions of the document management system 10 are realized by a CPU 501 of a computer 500 shown in FIG. 3 executing a program stored in a hard disk 504. The HTML information storage unit 21, the document information storage unit 22, the metadata storage unit 23, and the workflow information storage unit 24 are implemented in the hard disk 504, RAM 503, or the like of the computer 500 shown in FIG. 3. The HTML information storage unit 21, the document information storage unit 22, the metadata storage unit 23, and the workflow information storage unit 24 do not necessarily have to be included in the document management system 10, but may be located on a network.

[0041] The communication unit 11 transmits and receives various types of information to the terminal device 50 or the electronic contract system 30. In this embodiment, the communication unit 11 receives documents from the terminal device 50 and transmits screen information of various screens to the terminal device 50. The communication unit 11 transmits documents and processing requests to the electronic contract system 30, and receives documents and their identification information after processing by the electronic contract system 30. The communication unit 11 also transmits a withdrawal request to the electronic contract system 30 and receives a response from the electronic contract system 30 according to the status of the document.

[0042] The screen generator 12 references the HTML information storage unit 21 to generate screen information for various screens displayed by the terminal device 50. The HTML information storage unit 21 stores screen templates, which are preset with various tags, scripting language formats, and tag styles. The tags define the layout of titles, characters, tables, labels, buttons, and other elements displayed on a web page. The format defines the color, size, and character font of an HTML document using CSS (Cascading Style Sheets). The scripting language format defines the processing content. The screen generator 12 uses these templates to generate screen information for displaying a search screen, document list screen, and other elements, as described below. The screen information is a program written in HTML, XML, a scripting language, CSS, and other languages. The structure of a web page is primarily defined by HTML, the behavior of the web page is defined by the scripting language, and the style of the web page is defined by CSS. A mechanism for dynamically generating web pages in this way, enabling interactive processing between a server and a client, is called a web application. A web app is software or a mechanism that runs on a web browser and operates through the cooperation of a program written in a programming language (such as JavaScript (registered trademark)) that runs on the web browser and a program on the web server side.

[0043] The data management unit 13 manages the document transmitted from the terminal device 50 in association with the metadata. The data management unit 13 stores the document body (file) in the document information storage unit 22, and stores the metadata in the metadata storage unit 23.

[0044] The workflow control unit 14 accepts the registration of a workflow, and also refers to the workflow information storage unit 24 to monitor the start trigger and control the generation of the process execution unit 15. The workflow information will be described later.

[0045] The processing execution unit 15 is a module that executes the workflow. The processing execution unit 15 may also be called the workflow itself. The processing execution unit 15 is an instance that is dynamically generated by the workflow control unit 14. The processing execution unit 15 automatically executes processing according to the processing content of the workflow. The processing execution unit 15 operates independently as an individual module for each document. The processing of the processing execution unit 15 includes task assignment and communication with external systems.

[0046] 5 shows an example of document information stored in the document information storage unit 22. The document information indicates each document itself or the location where the document is stored.

[0047] A document ID is information that uniquely identifies a document. A document ID can be a file name, a file path, or a URL, as long as it is unique. Users can access documents using the document ID.

[0048] The file path represents the document itself or the location where the document is saved.

[0049] 6 shows an example of metadata stored in the metadata storage unit 23. Metadata is data that accompanies each document and is useful for managing the document. Each item of metadata will be explained below. Note that metadata may also be referred to as data of data.

[0050] The document ID is the same as the document ID in the document information storage unit 22, and is identification information that uniquely identifies the document.

[0051] filename is the filename of the document.

[0052] The document ID of the electronic contract system is the identification information of the document in the electronic contract system 30 for the document registered in the document management system 10. This item allows the document management system 10 to easily identify which document is registered in the document management system 10 when it is processed in the electronic contract system 30.

[0053] The document type indicates the type of processing the document is used for. When the electronic contract system 30 processes documents, there are many types of contract-related documents as shown in the figure, but this is only an example.

[0054] The contract start date is the start date of the contract period if the document is related to a contract. The contract end date is the end date of the contract period. The user can change the contract start date and contract end date.

[0055] The status indicates the state of the document, such as valid, rejected, or pending withdrawal. Valid: The contract is being processed in the electronic contract system 30 Rejected: The contract has been rejected in the electronic contract system 30 Withdrawal request in progress: A transitional state in which a user requests the electronic contract system 30 to withdraw a valid document, and the document management system 10 changes the state to rejected (although it may not be possible to reject). In other words, when a user requests the withdrawal of a contract or the like, that state is temporarily set in the metadata.

[0056] These states are merely examples, and other states may exist, and each state may be called by a different name.

[0057] When registering a document, the user can edit the file name, document type, contract start date, contract end date, etc. on the web page. In other words, the user can register metadata. Furthermore, the user can set what attributes to register in the metadata storage unit 23. In other words, the user can register metadata items. This allows the user to register document attributes to be used in searches as metadata. Therefore, the items in the metadata storage unit 23 are not limited to those shown in the figure.

[0058] Furthermore, although metadata is stored for each document, there may be documents for which no metadata exists.

[0059] 7 shows an example of workflow information stored in the workflow information storage unit 24. The workflow information defines the content of a series of processes to be executed by a workflow. Each item of the workflow information will be explained below.

[0060] The workflow ID is the identification information of the workflow. The workflow name can also be used as the identification information as long as it is unique.

[0061] The start trigger is a condition under which the workflow control unit 14 generates the processing execution unit 15 (i.e., the processing execution unit 15 starts the workflow). When an event that satisfies this start trigger occurs, the processing execution unit 15 automatically starts executing the workflow. Therefore, the user does not need to explicitly specify a workflow to start its execution. The start trigger shown in the figure is just one example, and there may also be a workflow whose start trigger is a periodic execution workflow, a workflow whose start trigger is a file name registration workflow, etc.

[0062] Flow 1 and Flow 2 indicate a series of processes that the process execution unit 15 performs in the workflow, in order. Flow 1 indicates the first process, and Flow 2 indicates the second process. In FIG. 7, there are two processes, but the number of processes can be any number and may vary depending on the workflow.

[0063] For example, a workflow with workflow ID=1 indicates that a change to the document is the start trigger, and that Person A's review process and Person B's approval process are carried out. A workflow with workflow ID=2 indicates that a new document is saved as the start trigger, and that a process is carried out to send the document to the electronic contract system 30. A workflow with workflow ID=3 indicates that a change to the metadata "status" to "withdrawal request in progress" is the start trigger, and that a process is carried out to request the electronic contract system 30 to withdraw the document.

[0064] <<Electronic Contract System>> Returning to Figure 4, the explanation will be made. The electronic contract system 30 has a communication unit 31, an electronic signature unit 32, a status information storage unit 38, a document information storage unit 39, and a status change response information storage unit 40. These functions of the electronic contract system 30 are functions or means realized by the CPU 501 of the computer 500 shown in Figure 3 executing a program stored in the HD 504. Furthermore, the status information storage unit 38, the document information storage unit 39, and the status change response information storage unit 40 are constructed in the HD 504, RAM 503, etc. of the computer 500 shown in Figure 3. The status information storage unit 38, the document information storage unit 39, and the status change response information storage unit 40 may be included in the electronic contract system 30, or may be located on a network.

[0065] The communication unit 31 mainly transmits and receives various information to and from the terminal device 50. In this embodiment, the communication unit 31 receives a document from the document management system 10, and transmits the document and its identification information after it has been processed by the electronic contract system 30 to the document management system 10. The communication unit 31 receives a request to cancel processing of a document from the document management system 10, and returns a response according to the status of the document.

[0066] The digital signature unit 32 handles a series of processes related to a contract and assigns a digital signature to a document to certify that the contract has been completed. The digital signature unit 32 manages documents used for a contract, etc. in a document information storage unit 39, and manages the status of each document in a status information storage unit 38. Digital signatures are merely an example, and a second system equivalent to the digital contract system 30 assigns timestamps, removes noise from documents, and creates digital watermarks.

[0067] 8 shows an example of document information stored in the document information storage unit 39 of the electronic contract system 30. The document information indicates each document itself or the location where the document is stored.

[0068] The document ID is identification information that uniquely identifies a document in the electronic contract system 30. The document ID may be a file name or a file path, as long as it is unique. Users can access documents using the document ID. Even for the same document, the document ID in the electronic contract system 30 is often different from the document ID in the document management system 10.

[0069] The file path represents the document itself or the location where the document is saved.

[0070] Figure 9 shows an example of status information stored in the status information storage unit 38 of the electronic contract system 30. The status information indicates the status (state) of each document. For example, the following states exist: These states are merely examples, and other states may exist, and each state may be called by a different name. Draft status: The document has only been uploaded to the electronic contract system 30, and has not yet entered into the agreement process on the electronic contract system 30. Contractor confirmation in progress: Agreement processing has begun on the electronic contract system 30, and the contractor is waiting for agreement (the state from the start to the end of contract processing) Agreed: An agreement has been reached with the contracting party Rejected: The document sent to the electronic contract system 30 has been withdrawn from processing. Figure 10 shows an example of status change response information stored in the status change response information storage unit 40. The status change response information indicates the "result of the withdrawal request" and the "processing after notification of the result within the electronic contract system 30" according to the current status in the electronic contract system 30. This is because, depending on the processing status (progress) of the document in the electronic contract system 30, it may be difficult for the electronic contract system 30 to withdraw processing of the document or change the status.

[0071] As shown in FIG. 10, the digital signature unit 32 returns one of three status patterns, "deleted", "withdrawn", and "cannot be withdrawn", to the document management system 10 in response to a withdrawal request.

[0072] - If the document status in the electronic contract system is in draft The electronic signature unit 32 returns "deleted" to the document management system 10. The drafting period is before the agreement processing performed by the electronic contract system 30. Also, since the contract has been withdrawn, the document is no longer needed. Since there is no need to keep anything that has not been processed on the electronic contract system 30 as history, the status is set to "deleted." The electronic signature unit 32 deletes the document. Note that the electronic contract system 30 may change only the status without deleting the document.

[0073] - When the document status in the electronic contract system is currently being confirmed by the contracting party The electronic signature unit 32 returns "Withdrawn" to the document management system 10. "Withdrawn" means that processing in the electronic contract system 30 has been canceled. For documents for which processing in the electronic contract system 30 has begun, the file itself cannot be deleted even before agreement is reached in order to preserve a history, so "Withdrawn" is returned. The electronic signature unit 32 changes the status to "Rejected." Note that the electronic contract system 30 may respond that the document cannot be withdrawn, rather than responding that it has been withdrawn.

[0074] - When the document status in the electronic contract system is "agreed" The electronic signature unit 32 returns "cannot be withdrawn" to the document management system 10. If an agreement has already been reached based on the document, it cannot be withdrawn, so the electronic contract system 30 returns "cannot be withdrawn." The electronic signature unit 32 does nothing about the status.

[0075] - If the document status in the electronic contract system is rejected The digital signature unit 32 returns "Withdrawn" to the document management system 10. If the processing has already been withdrawn in the electronic contract system 30 (i.e., if a withdrawal request has been made again), "Withdrawn" is returned. The digital signature unit 32 does nothing about the status.

[0076] <<Terminal Device>> The terminal device 50 has a communication unit 51, a display control unit 52, and an operation reception unit 53. Each of these functional units is a function or means realized by the CPU 501 shown in Fig. 3 executing instructions contained in one or more programs installed in the terminal device 50. Note that this program may be a web browser or a dedicated application.

[0077] The communication unit 51 mainly transmits and receives various types of information to and from the document management system 10. In this embodiment, the communication unit 51 receives various types of screen information and the like from the document management system 10, and transmits documents and user input contents to the document management system 10.

[0078] The display control unit 52 interprets screen information of various screens and displays it on the display 506. The operation receiving unit 53 receives various operations on the various screens displayed on the display 506 by the user.

[0079] <Registration processing procedure> Next, the procedure by which the document management system accepts the registration of a document and reflects the status change in the electronic contract system 30 will be described with reference to Fig. 11. Fig. 11 is an example of a sequence diagram showing the procedure by which the document management system 10 reflects the status change in the electronic contract system 30.

[0080] S1: When the document management system 10 is started or when the workflow information in the workflow information storage unit 24 is updated, the workflow control unit 14 acquires the workflow information from the workflow information storage unit 24. This process may be performed by an administrator.

[0081] S2: The user operates the terminal device 50 to create a contract, which is an example of a document. The file format does not matter, and may be a general-purpose format such as PDF or Word (registered trademark), or a format of a specified application. The document creation may be assisted by the document management system 10. In this case, the terminal device 50 executes a web application provided by the document management system 10, and the user can create the desired document by inputting and selecting characters, etc., according to the instructions of the web application.

[0082] S3: Next, the terminal device 50 displays the document registration screen generated by the screen generation unit 12, and the user transmits the contract to the information processing system 100 from this document registration screen. An example of the document registration screen is shown in Figure 15(a). The user inputs an operation to transmit the contract to the information processing system 100 to the terminal device 50 on the document registration screen.

[0083] Furthermore, when the terminal device 50 transmits the contract to the information processing system 100, the screen generation unit 12 generates a metadata setting screen, and the communication unit 11 transmits screen information of the metadata setting screen to the terminal device 50. The communication unit 51 of the terminal device 50 receives the screen information of the metadata setting screen, and the display control unit 52 displays the metadata setting screen. An example of the metadata setting screen is shown in FIG. 15(b). The user sets the desired metadata items and inputs values. The operation reception unit 53 of the terminal device 50 receives the operation, and the communication unit 51 transmits the metadata to the document management system 10. The metadata may be extracted on the document management system 10 side without the terminal device 50 transmitting the metadata (or after transmitting the metadata).

[0084] S4: The communication unit 11 of the document management system 10 receives the contract and the metadata, and the screen generation unit 12 requests the data management unit 13 to store the contract and the metadata.

[0085] S5: The data management unit 13 stores the contract in the document information storage unit 22. The data management unit 13 acquires the stored document ID="001" as a return value.

[0086] S6: The data management unit 13 sets the document ID of the metadata to "001." The data management unit 13 also stores the contract start date, contract end date, and the like in the metadata storage unit 23.

[0087] Fig. 12 shows the metadata after the processing of step S6. Note that the explanation of Fig. 12 mainly focuses on the device in Fig. 6. As shown in Fig. 12, immediately after registering a document, the document ID, document type, contract start date, contract end date, and status (valid) are registered. Note that the status (valid) is the initial value.

[0088] S7: Returning to Fig. 11, the data management unit 13 specifies document ID="001" and notifies the workflow control unit 14 that a document has been newly saved. This is so that the workflow control unit 14 can determine whether the start trigger for the workflow is satisfied.

[0089] S8: The workflow control unit 14 sequentially references the start triggers in the workflow information storage unit 24 and determines whether the start trigger is satisfied. For the sake of explanation, it is assumed that the start trigger is satisfied. Note that if a document or event satisfies the start triggers of multiple workflows, the workflow control unit 14 may generate the processing execution units 15 simultaneously, or may generate the processing execution units 15 sequentially. The following describes the case where the start trigger of workflow ID=2 is satisfied.

[0090] S9: If the start trigger is satisfied, the workflow control unit 14 generates a process execution unit 15 for processing the document with document ID="001". Therefore, the process execution unit 15 and document ID="001" are associated with each other.

[0091] S10: The process execution unit 15 requests the data management unit 13 to acquire the document with document ID="001" in order to execute the first process (flow 1) in the workflow information.

[0092] S11: The data management unit 13 acquires the document with document ID="001" from the document information storage unit 22.

[0093] S12: The data management unit 13 notifies the process execution unit 15 of the document itself or the location where the document is saved.

[0094] S13: The process execution unit 15 performs the process according to the workflow, and transmits the acquired document to the electronic contract system 30 via the communication unit 11.

[0095] S14: The communication unit 31 of the electronic contract system 30 receives the document, and the electronic signature unit 32 stores the document in the document information storage unit 39. The electronic signature unit 32 obtains the document ID="00A" managed on the electronic contract system 30 as a return value.

[0096] S15: The communication unit 31 of the electronic contract system 30 sends the document ID="00A" to the document management system 10.

[0097] S16: The communication unit 11 of the document management system 10 receives the document ID="00A" in the electronic contract system 30, and the processing execution unit 15 specifies the document ID="00A" and requests the data management unit 13 to save "00A" in the metadata.

[0098] S17: The data management unit 13 stores the document ID="00A" in the metadata storage unit 23 in association with the document ID="001".

[0099] Figure 13 shows the metadata after the processing of step S17. Note that the explanation of Figure 13 will mainly focus on the device in Figure 12. As shown in Figure 13, "00A" is set as the identification information in the electronic contract system 30.

[0100] S18: Returning to Fig. 11, the user then operates the terminal device 50 to change the status of the document registered in the document management system 10. For example, if the user notices an error in the document or the contract is no longer necessary, the user can request that the processing of the document be cancelled.

[0101] The terminal device 50 displays the status setting screen generated by the screen generation unit 12, and the user inputs a status change request on this status setting screen. The status setting screen, the search screens used to transition to the status setting screen, and the document list screen are shown in Figs. 16 to 18.

[0102] The operation reception unit 53 of the terminal device 50 receives the operation, and the communication unit 51 transmits the document ID = "001" and the changed status to the document management system 10. In this example, the user changes the status to "requesting withdrawal."

[0103] S19: The communication unit 11 of the document management system 10 receives the status change request, and the screen generation unit 12 passes the status change request to the data management unit 13.

[0104] S20: The data management unit 13 changes the status of the metadata identified by the document ID="001" to "requesting withdrawal."

[0105] Fig. 14 shows the metadata after the processing of step S20. Note that the explanation of Fig. 14 will mainly focus on the device in Fig. 13. As shown in Fig. 14, the status of the metadata has been changed to "requesting withdrawal".

[0106] S21: Returning to Fig. 11, the data management unit 13 designates the document ID="001" and notifies the workflow control unit 14 of a status change (withdrawal request). This is so that the workflow control unit 14 can determine whether the workflow start trigger is satisfied.

[0107] S22: The workflow control unit 14 sequentially references the start triggers in the workflow information storage unit 24 and determines whether the start trigger is satisfied. For the sake of explanation, it is assumed that the start trigger is satisfied. In the following, a case where the start trigger of workflow ID=3 is satisfied will be described.

[0108] S23: If the start trigger is satisfied, the workflow control unit 14 generates a process execution unit 15 for processing the document with document ID="001." Therefore, the process execution unit 15 and document ID="001" are associated with each other.

[0109] S24: In order to execute the first process (flow 1) of the workflow information, the process execution unit 15 requests the metadata of document ID="001" (document ID="00A" in the electronic contract system 30) from the data management unit 13.

[0110] S25: The data management unit 13 acquires the document ID="00A" in the electronic contract system 30 that is associated with the document ID="001".

[0111] S26: The data management unit 13 notifies the process execution unit 15 of the document ID in the electronic contract system 30 = "00A".

[0112] S27: The process execution unit 15 requests the electronic contract system 30 via the communication unit 11 to acquire the status by specifying the document ID="00A".

[0113] S28: The communication unit 31 of the electronic contract system 30 receives the request to obtain the status, and the electronic signature unit 32 obtains the status of the document identified by the document ID="00A" from the status information storage unit 38.

[0114] S29: Furthermore, the process execution unit 15 transmits a status change (withdrawal request) to the electronic contract system 30 via the communication unit 11, specifying the document ID="00A".

[0115] S30: The communication unit 31 of the electronic contract system 30 receives the status change request, and the electronic signature unit 32 sends the withdrawal result (response from the electronic contract system 30) of the document identified by the document ID = "00A".

[0116] The digital signature unit 32 determines whether the withdrawal is rejected or not possible based on the status of the relevant document as shown in Fig. 10, and notifies the document management system 10 of the result. The digital signature unit 32 also performs processing within the electronic contract system 30 as necessary. Details of the processing of step S30 will be explained with reference to Fig. 22.

[0117] S31: The communication unit 31 of the electronic contract system 30 sends a response based on the status of the document (deleted, withdrawn, or not withdrawable) to the document management system 10. Details of the processing of step S31 will be described with reference to FIG.

[0118] <<Screen example>> 15(a) is an example of a document registration screen 250 displayed by the terminal device 50. The document registration screen 250 has a file name field 251, a browse button 252, and a save button 253. The user presses the browse button 252 to select a document saved on the HD 504 or the like. The file name of the selected document is displayed in the file name field 251. When the user presses the save button 253, the terminal device 50 sends the document in the file name field 251 to the document management system 10.

[0119] 15(b) is an example of a metadata setting screen 260 displayed by the terminal device 50. The metadata setting screen 260 has a document type field 261, a contract start date field 262, and a contract end date field 263.

[0120] The document type field 261 is a field where the user inputs the document type as one item of metadata.

[0121] The contract start date field 262 is a field for the user to input the contract start date as one item of metadata. The display control unit 52 may display a calendar, and the operation receiving unit 53 may receive a specific date from the user.

[0122] The contract end date field 263 is a field for the user to input the contract end date as one item of metadata. The display control unit 52 may display a calendar, and the operation receiving unit 53 may receive a specific date or range from the user.

[0123] When the user sets the metadata and presses the confirm button 264, the terminal device 50 transmits the metadata to the document management system 10.

[0124] 16 shows an example of a search screen 210 displayed by the terminal device 50. A user operates the terminal device 50 to connect the terminal device 50 to the information processing system 100. The screen generation unit 12 of the information processing system 100 generates a search screen in response to the user operation, and the communication unit 11 transmits screen information of the search screen to the terminal device 50.

[0125] The search screen 210 has a document type field 211 , a contract start date field 212 , a contract end date field 213 , and a search button 214 .

[0126] The document type field 211 is a field where the user inputs a search key for searching for the document type of the metadata item.

[0127] The contract start date field 212 is a field for the user to input a search key for searching for the contract start date of a metadata item. The display control unit 52 may display a calendar, and the operation receiving unit 53 may receive a specific date or range from the user.

[0128] The contract end date field 213 is a field for the user to input a search key for searching for the contract end date of a metadata item. The display control unit 52 may display a calendar, and the operation receiving unit 53 may receive a specific date or range from the user.

[0129] The search button 214 is a button for the terminal device 50 to send a search request (document list) to the document management system 10.

[0130] 16 is merely an example, and there may be a file name input field and a free keyword input field. There may also be a document ID input field. When the search button 214 is pressed, the screen transitions to the document list screen 220.

[0131] 17 is a diagram showing an example of a document list screen 220 displayed by the terminal device 50. The document list screen 220 has fields for file names 221, document types 222, contract start dates 223, and contract end dates 224 of documents that match the search. In other words, the document list screen 220 displays at least some of the metadata fields in the metadata storage unit 23 for each record (one line) that matches the search. In FIG. 17, all document types are "basic contract," so it is considered that the user entered the search key "basic contract" in the document type field on the search screen 210.

[0132] A status change button 226 is displayed for each document. When the user presses the status change button 226 for the document whose status he or she wants to change, the terminal device 50 displays a status setting screen. The transition from the document list screen 220 to the status setting screen may be performed by the terminal device 50 or by the document management system 10.

[0133] When the user selects one or more documents and presses the open button 225, the terminal device 50 can display the file bodies of the selected documents.

[0134] 18 is an example of a status setting screen 230 displayed by the terminal device 50. The status setting screen 230 has, as an example, a document type field 231, a contract start date field 232, a contract end date field 233, and a status field 234. As with the document list screen 220, the user can set changed values ​​in the document type field 231, the contract start date field 232, and the contract end date field 233.

[0135] The current status is displayed in the status column 234, and the user can select from available statuses (valid, rejected, withdrawal requested) using a pull-down menu. The user changes the status and presses the confirm button 235. This starts the processing from step S18 onwards.

[0136] <Processing on the document management system side> 19 shows a list of processes performed by the document management system 10 in response to the withdrawal result (response from the electronic contract system 30). The withdrawal result in this embodiment is either deleted, withdrawn, or not withdrawable, as described in FIG.

[0137] If the withdrawal result is "deleted", the file in the electronic contract system 30 has been deleted, so the document is also deleted from the document management system 10 for synchronization.

[0138] If the withdrawal result is "Withdrawn," the file is not deleted within the electronic contract system 30; only the status is changed. Therefore, the document management system 10 changes only the metadata without deleting the document. Therefore, in the document management system 10, the status is changed from "Withdrawal Request" to "Rejected."

[0139] If the withdrawal result is "Withdrawal not permitted," the document status is not set to "Rejected" in the electronic contract system 30, and the metadata in the document management system 10 is accordingly changed to "Valid." Therefore, in the document management system 10, the status is changed from "Withdrawal request pending" to "Valid."

[0140] 20 is a flowchart illustrating the process for a document or status that the document management system 10 performs in response to a response (withdrawal result) from the electronic contract system 30. The process in FIG. 20 is the process in step S31 in FIG.

[0141] The data management unit 13 determines whether the response from the electronic contract system 30 is "deleted" (S101).

[0142] If the determination in step S101 is Yes, the data management unit 13 deletes the document identified by the document ID (S102). The data management unit 13 also deletes the metadata when deleting the document.

[0143] If the determination in step S101 is No, the data management unit 13 determines whether the response from the electronic contract system 30 is "withdrawn" (S103).

[0144] If the determination in step S103 is Yes, the data management unit 13 changes the status of the document identified by the document ID to "Rejected" (S104). That is, if the processing by the electronic contract system 30 has started but is not yet finished (contractor confirmation in progress), the data management unit 13 sets the document status to "Rejected," indicating that the processing has been withdrawn.

[0145] If the determination in step S103 is No, the data management unit 13 changes the status of the document identified by the document ID to "valid" (S105).

[0146] In this way, the document management system 10 can change the status of the document depending on the state of the contract in the electronic contract system 30.

[0147] <<Document display example>> If the metadata status in the document management system 10 is "rejected," the document management system 10 displays the document so that the user can determine the status.

[0148] Fig. 21 is a diagram showing a document list screen 240 by status displayed by the terminal device 50. In the explanation of Fig. 21, differences from Fig. 17 will be mainly explained. In Fig. 21, the document list screen 240 has a valid document field 241 and a rejected document field 242. The valid document field 241 displays documents with a status of "valid", and the rejected document field 242 displays documents with a status of "rejected". On the document list screen 240, documents are displayed in a differentiated manner based on the document status.

[0149] In FIG. 21, documents are divided into two categories: valid and rejected. However, if there are documents for which withdrawal requests are being made, these documents are also displayed separately.

[0150] Therefore, the user can understand the status of a document by which column the document is displayed in.

[0151] <Electronic contract system processing of withdrawal requests> The processing of the electronic contract system 30 in response to a withdrawal request will be described with reference to Figure 22. The electronic contract system 30 notifies the document management system 10 of the withdrawal result based on the status change response information in Figure 10, and deletes the document or changes its status.

[0152] 22 is a flowchart illustrating the processing of the electronic contract system 30 in response to a withdrawal request. This processing is executed in step S30 of FIG.

[0153] The electronic signature unit 32 of the electronic contract system 30 determines whether the status of the document for which withdrawal has been requested is in draft or not (S201).

[0154] If the determination in step S201 is Yes, the digital signature unit 32 transmits a withdrawal result, ie, deletion, to the document management system 10 via the communication unit 31 (S202).

[0155] Furthermore, the digital signature unit 32 deletes the document for which the withdrawal request has been made from the document information storage unit 39, and deletes the status from the status information storage unit 38 (S203).

[0156] If the determination in step S201 is No, the electronic signature unit 32 of the electronic contract system 30 determines whether the status of the document for which withdrawal has been requested is currently being confirmed by the contracting party (S204).

[0157] If the determination in step S204 is Yes, the digital signature unit 32 transmits a withdrawal result of rejection to the document management system 10 via the communication unit 31 (S205).

[0158] Furthermore, the digital signature unit 32 changes the status of the document for which withdrawal has been requested in the status information storage unit 38 to "rejected" (S206).

[0159] If the determination in step S204 is No, the electronic signature unit 32 of the electronic contract system 30 determines whether the status of the document for which withdrawal has been requested is "agreed" (S207).

[0160] If the determination in step S207 is Yes, the digital signature unit 32 transmits a withdrawal result indicating that withdrawal is not permitted to the document management system 10 via the communication unit 31 (S208).

[0161] If the determination in step S207 is No, the electronic signature unit 32 of the electronic contract system 30 determines whether the status of the document for which withdrawal has been requested is rejected (S209).

[0162] If the determination in step S209 is Yes, the digital signature unit 32 transmits a withdrawal result, ie, rejection, to the document management system 10 via the communication unit 31 (S210).

[0163] In this way, the electronic contract system 30 can perform processing according to the status of the document for which withdrawal has been requested.

[0164] <Major Effects> As described above, the document management system 10 manages the identification information of documents in the document management system 10 in association with the identification information of documents in the electronic contract system 30, thereby enabling the processing performed by a user on a document in the document management system 10 to be reflected in the electronic contract system 30. The document management system 10 processes documents according to the status of the document in the electronic contract system 30, and therefore can execute processing without discrepancies with the progress of document processing by the electronic contract system 30.

[0165] <Other application examples> The best mode for carrying out the present invention has been described above using examples, but the present invention is not limited to these examples, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention.

[0166] For example, in this embodiment, the document management system 10 and the electronic contract system 30 cooperate with each other and are linked by document IDs during the execution of the workflow, but the document management system 10 does not have to execute the workflow. For example, the user may instruct the document management system 10 and the electronic contract system 30 to perform processing in sequence.

[0167] Furthermore, even if the document management system 10 transmits only one document, multiple documents may be generated by processing the document in the electronic contract system 30. In this case, identification information is assigned to each document generated by the electronic contract system 30.

[0168] Furthermore, when a workflow is executed, there are various workflows, such as a workflow that performs OCR on a document and then saves it to cloud storage, or a workflow that receives an email or fax and then saves it to cloud storage, etc. A workflow can be created by the user setting each process.

[0169] In addition, in this embodiment, the second system includes an electronic contract system 30, a timestamp system, a noise removal system, and an electronic watermark system, but the second system can also be a variety of systems such as cloud storage, OCR, translation, and voice recognition.

[0170] Furthermore, in this embodiment, a change in status in the document management system 10 causes the document management system 10 to accept a processing change request to the electronic contract system 30. However, the document management system 10 may directly accept a processing change request to the electronic contract system 30, request the electronic contract system 30 to change the processing, and execute processing related to the document in the document management system 10 in response to the response from the electronic contract system 30.

[0171] Furthermore, the configuration examples in Figure 4 and the like are divided according to main functions to facilitate understanding of the processing by the document management system 10, the electronic contract system 30, and the terminal device 50. The method of dividing the processing units and their names do not limit the present invention. The processing by the document management system 10, the electronic contract system 30, and the terminal device 50 can be divided into even more processing units depending on the processing content. Furthermore, one processing unit can be divided so that it includes even more processes.

[0172] Additionally, the devices described in the examples are merely illustrative of one of several computing environments for implementing the embodiments disclosed herein. In one embodiment, the document management system 10 includes multiple computing devices, such as a server cluster, configured to communicate with each other via any type of communications link, including a network, shared memory, or the like, and to perform the processes disclosed herein.

[0173] Furthermore, the document management system 10 can be configured to share the processing steps disclosed in this embodiment, for example, the steps shown in Figure 11, in various combinations. The document management system 10 may be integrated into one server device, or may be divided into multiple devices.

[0174] Each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and conventional circuit modules designed to perform each of the above-described functions. [Explanation of symbols]

[0175] 10. Document Management Systems 30 Electronic Contract System 50 Terminal Equipment 100 Information Processing Systems [Prior art documents] [Patent documents]

[0176] [Patent Document 1] Japanese Patent Application Laid-Open No. 2008-259211

Claims

1. A first system that can communicate with terminal devices and a second system via a network, and requests data processing from the second system, A storage unit that stores the data related to the above processing, A processing execution unit transmits the data stored in the storage unit and a first processing request requesting processing of the data to the second system via a communication unit. It has, The communication unit receives second information transmitted from the second system for identifying the data on the second system, The first system further includes a data management unit that stores in the storage unit a first information for identifying the data on the first system, the received second information, and information for identifying the state of the processing, in association with each other. When the communication unit receives a request from the terminal device for a change in the processing of the data identified by the first information, it transmits to the second system the second information stored in the storage unit in association with the first information, and a second processing request that requests a change to the processing requested by the first processing request based on the request received from the terminal device. The data management unit modifies the information that identifies the state of the process, which is stored in the storage unit in association with the first information, based on a request for a change in the process received from the terminal device. A first system characterized by the following:

2. A request relating to a change in the aforementioned process is a request relating to the cancellation of the aforementioned process. The second processing request is a processing request relating to the cancellation of the processing, The data management unit, based on a request for a change in the process received from the terminal device, changes the information identifying the state of the process stored in the storage unit in association with the first information to information identifying the state in which the process has been canceled. The first system according to claim 1.

3. The first system according to claim 1 or 2, wherein the data management unit changes information that identifies the state of the processing stored in the storage unit in association with the second information included in the response to the second processing request from the second system.

4. The first system according to any one of claims 1 to 3, wherein the data management unit, in response to the response from the second system to the second processing request, changes the information that identifies the processing state stored in the storage unit in association with the second information included in the response to information that identifies the same state as the state identified by the information that identifies the state included in the response.

5. The first system according to any one of claims 1 to 4, wherein the first processing request is a processing request requesting the application of an electronic signature.

6. The first system according to any one of claims 1 to 5, wherein the second system is a system for assigning electronic signatures.

7. The first system according to any one of claims 1 to 6, wherein the data is a contract, and the second system is a system for affixing an electronic signature or a timestamp to the contract.

8. The first system according to any one of claims 1 to 7, wherein the first information is identification information that uniquely identifies the data on the first system, and the second information is identification information that uniquely identifies the data on the second system.

9. The communication unit receives the second information as a return value for the first processing request. The first system according to any one of claims 1 to 8.

10. The request relating to the change of the process is a request relating to the cancellation of the process, The second processing request is a processing request relating to the cancellation of the processing, When the data management unit receives a response from the second system to the second processing request indicating that processing by the second system has been completed or that the processing cannot be withdrawn, it changes the information identifying the processing status stored in the storage unit in association with the first information to information indicating that it is valid. The first system according to claim 3.

11. A system comprising a first system and a terminal device, which can communicate with a terminal device and a second system via a network and requests the second system to process data, The first system described above is A storage unit that stores the data related to the above processing, A processing execution unit transmits the data stored in the storage unit and a first processing request requesting processing of the data to the second system via a first communication unit. It has, The first communication unit receives second information transmitted from the second system for identifying the data on the second system, The first system further includes a data management unit that stores in the storage unit a first information for identifying the data on the first system, the received second information, and information for identifying the state of the processing, in association with each other. When the first communication unit receives a request from the terminal device for a change in the processing of the data identified by the first information, it transmits to the second system the second information stored in the storage unit in association with the first information, and a second processing request that requests a change to the processing requested by the first processing request based on the request received from the terminal device. The data management unit modifies the information that identifies the state of the data stored in the storage unit in association with the first information, based on a request for a change in the process received from the terminal device. The terminal device has a second communication unit that transmits a request to the first system for a change in the processing of the data identified by the first information. system.

12. The terminal device further comprises a display control unit that causes a screen for receiving an operation requesting a change in the process to be displayed on the display unit, When the second communication unit receives an operation requesting a change in the process via the screen displayed on the display unit, it transmits the request for the change in the process to the first system. The system according to claim 11.

13. The first system further comprises a screen generation unit that generates screen information for displaying the screen, The first communication unit transmits the generated screen information to the terminal device. The second communication unit receives the screen information transmitted from the first system, The display control unit causes the screen to be displayed on the display unit based on the received screen information. The system according to claim 12.

14. The aforementioned screen information is a web page, The display control unit causes the screen to be displayed on the display unit by executing a web browser program. The system according to claim 13.

15. A data processing method performed by a first system, which is capable of communicating with a terminal device and a second system via a network, and requests data processing from the second system, A step of storing the data related to the above processing in a storage unit, The steps include transmitting the data stored in the storage unit and a first processing request requesting processing of the data to the second system via the communication unit, The steps include receiving second information transmitted from the second system for identifying the data on the second system, A step of storing in the storage unit a first information for identifying the data on the first system, the received second information, and information for identifying the state of the processing, in association with each other. The steps include receiving a request from the terminal device for a change in the processing of the data identified by the first information, A step of transmitting to the second system the second information stored in association with the first information, and a second processing request that requests a change to the processing requested by the first processing request, based on the request received from the terminal device. A step of changing the information that identifies the state of the process stored in the storage unit in association with the first information, based on a request for a change in the process received from the terminal device, A data processing method that includes this.

16. A data processing method performed by a system including a terminal device and a second system, which can communicate with the terminal device and a second system via a network and requests the second system to perform data processing, The first system includes the step of storing the data related to the processing in a storage unit, The first system transmits the data stored in the storage unit and a first processing request requesting processing of the data to the second system via the communication unit, The first system receives second information transmitted from the second system for identifying the data on the second system, The first system stores in the storage unit, in association with first information for identifying the data on the first system, the received second information, and information for identifying the state of the processing. The terminal device transmits a request for a change in the processing relating to the data identified by the first information, The first system receives a request from the terminal device for a change in the processing of the data identified by the first information, The first system transmits to the second system the second information stored in the storage unit in association with the first information, and a second processing request that requests a change to the processing requested by the first processing request, based on the request received from the terminal device. The first system, based on a received request for a change in the process, changes the information that identifies the state of the process, which is stored in the storage unit in association with the first information. A data processing method characterized by the following features.

17. A terminal device and a second system can communicate with the first system via a network, and the first system requests the second system to process data, Means for storing the data related to the above processing in a storage unit, A processing execution unit transmits the data stored in the storage unit and a first processing request requesting processing of the data to the second system via a communication unit. It is a program that makes it function as such. The communication unit receives second information transmitted from the second system for identifying the data on the second system, The program further causes the first system to function as a data management unit that stores in the storage unit a first piece of information for identifying the data on the first system, the received second piece of information, and information for identifying the state of the processing, in association with each other. When the communication unit receives a request from the terminal device for a change in the processing of the data identified by the first information, it transmits to the second system the second information stored in the storage unit in association with the first information, and a second processing request that requests a change to the processing requested by the first processing request based on the request received from the terminal device. The data management unit modifies the information that identifies the state of the process, which is stored in the storage unit in association with the first information, based on a request for a change in the process received from the terminal device. A program characterized by the following features.

Images