Information processing device, information processing system, system, information processing method, method and program

Abstract

The second information processing device is provided with a screen that requests electronic data from it. [Solution] The information processing device is an information processing device that can communicate via a network with a second information processing device that processes electronic data transmitted from a user terminal, and comprises a transmission unit that transmits electronic data to the second information processing device, an identification information acquisition unit that acquires identification information of the electronic data in the second information processing device from the second information processing device, and a screen information provision unit that provides the user terminal with a screen requesting the second information processing device to transmit electronic data having the identification information.

Description

Technical Field

[0001] This invention relates to an information processing apparatus, an information processing system, an information processing method, and a program.

Background Art

[0002] Document management systems are used to electronically manage electronic data such as documents generated in business. Also, electronic contract systems are used to electronically conclude contracts using electronic data. An information processing apparatus such as a document management system and a second information processing apparatus such as an electronic contract system are linked, and the information processing apparatus manages the electronic data used by the second information processing apparatus for contract conclusion.

[0003] Patent Document 1 discloses a document processing apparatus that can switch document processing operations based on metadata added to electronic document data.

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, there is a problem that a screen for requesting electronic data from the second information processing apparatus is not provided to the information processing apparatus. For example, conventionally, when a user wants to display electronic data stored in the second information processing apparatus, the user has to log in to the second information processing apparatus and find the target electronic data.

[0005] An embodiment of this invention aims to provide a screen for requesting electronic data from the second information processing apparatus to the information processing apparatus in view of the above technical problems.

Means for Solving the Problems

[0006] To solve the above problems, an information processing device, which is one embodiment of the present invention, is an information processing device that can communicate via a network with a second information processing device that processes electronic data transmitted from a user terminal, and comprises a transmission unit that transmits electronic data to the second information processing device, an identification information acquisition unit that acquires identification information of the electronic data in the second information processing device from the second information processing device, and a screen information provision unit that provides the user terminal with a screen requesting the second information processing device to transmit electronic data having the identification information. [Effects of the Invention]

[0007] According to one embodiment of this invention, a screen requesting electronic data from a second information processing device can be provided to the information processing device. [Brief explanation of the drawing]

[0008] [Figure 1] This figure illustrates the overall configuration of an information processing system in one embodiment. [Figure 2] This figure illustrates the hardware configuration of an information processing device in one embodiment. [Figure 3] This figure illustrates the hardware configuration of an image forming apparatus in one embodiment. [Figure 4] This diagram illustrates the functional configuration of the document management server in the first embodiment. [Figure 5] This diagram illustrates the functional configuration of the electronic contract server in the first embodiment. [Figure 6] This figure illustrates the functional configuration of a user terminal in the first embodiment. [Figure 7] This figure illustrates the functional configuration of a customer terminal in the first embodiment. [Figure 8] This diagram illustrates the processing procedure of an information processing system in the prior art. [Figure 9] This diagram illustrates the processing procedure of an information processing system in the prior art. [Figure 10] This figure shows an example of a workflow setting screen in one embodiment. [Figure 11] This figure shows an example of workflow information in one embodiment. [Figure 12] This figure shows another example of workflow information in one embodiment. [Figure 13] This figure shows a specific example of workflow information in one embodiment. [Figure 14] This figure shows an example of a document registration screen in one embodiment. [Figure 15] This figure shows an example of a metadata setting screen in conventional technology. [Figure 16] This figure shows an example of a metadata table in conventional technology. [Figure 17] This figure shows a concrete example of a metadata table in conventional technology. Figure 17(A) shows a concrete example of metadata generated when a document is stored. Figure 17(B) shows a concrete example of metadata updated when metadata is set. [Figure 18] This figure shows an example of a task processing screen in one embodiment. [Figure 19] This figure shows an example of a contract selection screen in one embodiment. [Figure 20] This figure shows an example of a contract settings screen in one embodiment. [Figure 21] This figure shows an example of a contract signing screen in one embodiment. [Figure 22] This figure shows an example of a contract confirmation screen in one embodiment. [Figure 23] This figure illustrates the processing procedure of the information processing system in the first embodiment. [Figure 24] This figure shows an example of workflow information in the first embodiment. [Figure 25]It is a diagram showing a specific example of a metadata table in the first embodiment. FIG. 26(A) is a diagram showing a specific example of metadata generated when a document is stored. FIG. 26(B) is a diagram showing a specific example of metadata updated when metadata is set. FIG. 26(C) is a diagram showing a specific example of metadata updated when a connection destination identifier is acquired. [Figure 26] It is a diagram showing an example of a metadata setting screen in the first embodiment. [Figure 27] It is a diagram exemplifying the processing procedure of an information processing system in the second embodiment. [Figure 28] It is a diagram exemplifying the processing procedure of an information processing system in the second embodiment. [Figure 29] It is a diagram showing an example of workflow information in the second embodiment. [Figure 30] It is a diagram showing a specific example of a metadata table in the second embodiment. FIG. 30(A) is a diagram showing a specific example of metadata updated when a connection destination identifier before contract conclusion is acquired. FIG. 30(B) is a diagram showing a specific example of metadata updated when a connection destination identifier after contract conclusion is acquired. [Figure 31] It is a diagram showing an example of a metadata setting screen in the second embodiment. [Embodiments for Carrying Out the Invention]

[0009] Hereinafter, embodiments of this invention will be described in detail with reference to the drawings. In the drawings, components having the same function are denoted by the same reference numerals, and redundant description is omitted.

[0010] [Background] A document management system is an information processing system for electronically storing, managing, and utilizing documents generated in the business of enterprises and the like. Also, an electronic contract system is an information processing system for electronically concluding contracts in enterprises and the like.

[0011] Document management systems alone may not be able to fully cover business workflows. For example, in traditional contract processing, documents processed in the document management system were printed on paper for contract processing. In this case, the paper documents that had undergone contract processing, such as signing or stamping, had to be scanned and stored again in the document management system.

[0012] Paper-based contract processing incurs printing and storage costs and is inefficient for searching, so document management systems and electronic contract systems are often used in conjunction. However, simply using document management systems and electronic contract systems together presents a challenge: since the two systems operate independently, user operation becomes cumbersome.

[0013] For example, if a user wants to access a document stored in an electronic contract system, they need to log in to the system and find the desired document among the many stored documents.

[0014] One embodiment of this invention stores documents managed by a document management server in association with identification information used to identify those documents in an electronic contract system, and outputs screen information representing a screen that displays the identification information in association with information about the documents. As a result, users can directly view documents stored in the electronic contract system from the screen output by the document management server. In other words, it eliminates the need to log in to the electronic contract system and search for the desired document in order to view the documents stored in the electronic contract system.

[0015] [First Embodiment] In the first embodiment of this invention, the metadata stored by the document management system in association with a document includes identification information that identifies the document in an electronic contract system. The document management system outputs screen information to the user terminal that represents a screen displaying information about the document in association with the identification information.

[0016] In this embodiment, the document is electronic data representing the content of a document or the like. The electronic data is not limited to documents, but may be any electronic data representing any information, such as text, images, or videos.

[0017] In this embodiment, the identification information is information that allows direct access to the document stored in the electronic contract system. For example, the identification information is a destination identifier that identifies the destination of the document in the electronic contract system. The destination identifier is, for example, a URL (Uniform Resource Locator) that identifies the location of the document in electronic space, or an access key that is entered to display a specific document.

[0018] <Overall configuration of Information Processing System 1> First, the configuration of the information processing system 1 in this embodiment will be described with reference to Figure 1. Figure 1 is a diagram showing an example of the overall configuration of the information processing system 1 in this embodiment.

[0019] As shown in Figure 1, the information processing system 1 includes a document management server 10, an electronic contract server 20, a staff terminal 30-1, a reviewer terminal 30-2, an approver terminal 30-3, and a business partner terminal 40. The staff terminal 30-1, reviewer terminal 30-2, and approver terminal 30-3 are distinguished by the type of user they are used for, but they have the same functions. Hereinafter, the staff terminal 30-1, reviewer terminal 30-2, and approver terminal 30-3 will be collectively referred to as the user terminal 30.

[0020] The document management server 10, the electronic contract server 20, the user terminal 30, and the trading partner terminal 40 are each connected to the communication network 100. The communication network 100 is configured so that each connected device can communicate with each other. The communication network 100 is constructed using wired communication networks such as the Internet, LAN (Local Area Network), or WAN (Wide Area Network). The communication network 100 may also include wireless communication networks such as wireless LAN or short-range wireless communication, or mobile communication networks such as WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution), or 5G (5th Generation).

[0021] The document management server 10 electronically manages documents generated in the course of business operations. The document management server 10 stores metadata associated with documents, enabling efficient document retrieval. Furthermore, the document management server 10 has functions to execute workflows for business operations, enabling, for example, the efficient implementation of document circulation flows.

[0022] The document management server 10 may be implemented by a single information processing device, or it may be a system implemented by multiple information processing devices.

[0023] The electronic contract server 20 performs the processing necessary to conclude a contract electronically. The electronic contract server 20 sends the contract to the business partner, and if the business partner agrees, it performs processing such as adding an electronic signature or seal to the contract.

[0024] The electronic contract server 20 may be implemented by a single information processing device, or it may be a system implemented by multiple information processing devices.

[0025] The user terminal 30 is an electronic device used by the user. The user can use the user terminal 30 to perform operations on both the document management server 10 and the electronic contract server 20.

[0026] In this embodiment, the users include a person responsible for drafting the contract, a reviewer who examines the contents of the contract, and an approver who approves the contents of the contract. The person responsible terminal 30-1 is a user terminal 30 used by the person responsible. The reviewer terminal 30-2 is a user terminal 30 used by the reviewer. The approver terminal 30-3 is a user terminal 30 used by the approver.

[0027] The trading partner terminal 40 is an electronic device used by the trading partner's users. The trading partner's users can use the trading partner terminal 40 to perform operations on the electronic contract server 20.

[0028] An example of the document management server 10, electronic contract server 20, user terminal 30, and trading partner terminal 40 is an information processing device. Another example of the document management server 10, electronic contract server 20, user terminal 30, and trading partner terminal 40 is an image forming device (printer, fax machine, MFP (Multifunction Peripheral / Product / Printer: digital multifunction device), scanner). Note that the document management server 10, electronic contract server 20, user terminal 30, and trading partner terminal 40 are not limited to information processing devices or image forming devices, as long as they are devices equipped with communication functions.

[0029] The document management server 10, electronic contract server 20, user terminal 30, and trading partner terminal 40 may be, for example, output devices such as PJ (Projector), IWB (Interactive White Board: a whiteboard with electronic blackboard functionality that enables mutual communication), digital signage, HUD (Head Up Display) devices, industrial machinery, imaging devices, sound collection devices, medical equipment, networked home appliances, automobiles (Connected Car), notebook PC (Personal Computer), mobile phones, smartphones, tablet devices, game consoles, PDA (Personal Digital Assistant), digital cameras, wearable PCs, or desktop PCs.

[0030] <Hardware configuration of each device included in Information Processing System 1> Next, the hardware configuration of each device included in the information processing system 1 in this embodiment will be described with reference to Figures 2 and 3.

[0031] Hardware configuration of information processing equipment Figure 2 shows an example of a hardware configuration when the document management server 10, electronic contract server 20, user terminal 30, and trading partner terminal 40 are implemented by an information processing device. As shown in Figure 2, the information processing device includes a CPU 501, ROM 502, RAM 503, HD 504, HDD (Hard Disk Drive) controller 505, display 506, external device connection I / F (Interface) 508, network I / F 509, bus line 510, keyboard 511, pointing device 512, DVD-RW (Digital Versatile Disk Rewritable) drive 514, and media I / F 516.

[0032] Of these, the CPU 501 controls the operation of the entire information processing unit. The ROM 502 stores programs used to drive the CPU 501, such as IPL. The RAM 503 is used as the work area for the CPU 501. The HD 504 stores various data such as programs. The HDD controller 505 controls the reading or writing of various data to the HD 504 according to the control of the CPU 501. The display 506 displays various information such as cursors, menus, windows, characters, or images. The external device connection I / F 508 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memory and printers. The network I / F 509 is an interface for data communication using the communication network 100. The bus line 510 is an address bus, data bus, etc., for electrically connecting each component such as the CPU 501 shown in Figure 2.

[0033] The keyboard 511 is a type of input means equipped with multiple keys for inputting characters, numbers, and various instructions. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting processing targets, and moving the cursor. The DVD-RW drive 514 controls the reading or writing of various data to the DVD-RW 513, which is an example of a removable recording medium. Note that it is not limited to DVD-RW, but may also be DVD-R, etc. The media interface 516 controls the reading or writing (storage) of data to the recording medium 515, such as flash memory.

[0034] Hardware configuration of the image forming apparatus Figure 3 shows an example of a hardware configuration when the document management server 10, electronic contract server 20, user terminal 30, and trading partner terminal 40 are implemented in an image forming apparatus. As shown in Figure 3, the image forming apparatus includes a controller 910, a short-range communication circuit 920, an engine control unit 930, an operation panel 940, and a network interface 950.

[0035] Of these, the controller 910 includes the main components of the computer: the CPU 901, system memory (MEM-P) 902, northbridge (NB) 903, southbridge (SB) 904, ASIC (Application Specific Integrated Circuit) 906, local memory (MEM-C) 907, HDD controller 908, and HD 909, with the NB 903 and ASIC 906 connected by an AGP (Accelerated Graphics Port) bus 921.

[0036] Of these, the CPU901 is a control unit that performs overall control of the image forming apparatus. The NB903 is a bridge that connects the CPU901 to the MEM-P902, SB904, and AGP bus 921, and includes a memory controller that controls reading and writing to the MEM-P902, as well as a PCI (Peripheral Component Interconnect) master and an AGP target.

[0037] MEM-P902 consists of ROM902a, which is a memory for storing programs and data that realize the various functions of the controller 910, and RAM902b, which is used for program and data deployment and drawing during memory printing. The programs stored in RAM902b may be configured to be provided as installable or executable files recorded on a computer-readable recording medium such as a CD-ROM, CD-R, or DVD.

[0038] SB904 is a bridge for connecting NB903 to PCI devices and peripherals. ASIC906 is an integrated circuit (IC) for image processing applications that has hardware elements for image processing, and acts as a bridge connecting the AGP bus 921, PCI bus 922, HDD908, and MEM-C907, respectively. This ASIC906 consists of a PCI target and AGP master, an arbiter (ARB) that forms the core of the ASIC906, a memory controller that controls the MEM-C907, multiple DMACs (Direct Memory Access Controllers) that perform image data rotation using hardware logic, and a PCI unit that performs data transfer via PCI bus 922 between the scanner unit 931 and the printer unit 932. Note that the ASIC906 may also be connected to a USB (Universal Serial Bus) interface or an IEEE1394 (Institute of Electrical and Electronics Engineers 1394) interface.

[0039] MEM-C907 is local memory used as a copy image buffer and code buffer. HD909 is storage for storing image data, font data used during printing, and forms. HD909 controls data reading or writing to it according to the control of CPU901. The AGP bus 921 is a bus interface for graphics accelerator cards proposed to speed up graphics processing, and by directly accessing MEM-P902 with high throughput, the graphics accelerator card can be made faster.

[0040] Furthermore, the short-range communication circuit 920 is equipped with a short-range communication circuit 920a. The short-range communication circuit 920 is a communication circuit such as NFC or Bluetooth.

[0041] Furthermore, the engine control unit 930 is composed of a scanner unit 931 and a printer unit 932. The operation panel 940 includes a panel display unit 940a, such as a touch panel, which displays current settings and selection screens and accepts input from the operator, and an operation panel 940b, which consists of a numeric keypad that accepts setting values ​​for image formation conditions such as density settings and a start key that accepts copy start instructions. The controller 910 controls the entire image forming apparatus, for example, controlling drawing, communication, and input from the operation panel 940. The scanner unit 931 or the printer unit 932 includes an image processing section, such as error diffusion and gamma conversion.

[0042] The image forming apparatus allows the user to sequentially switch between document box function, copy function, printer function, and facsimile function using the application switching key on the control panel 940. When the document box function is selected, the apparatus switches to document box mode; when the copy function is selected, it switches to copy mode; when the printer function is selected, it switches to printer mode; and when the facsimile mode is selected, it switches to facsimile mode.

[0043] Furthermore, the network interface 950 is an interface for data communication using the communication network 100. The short-range communication circuit 920 and the network interface 950 are electrically connected to the ASIC 906 via the PCI bus 922.

[0044] <Functional configuration of each device included in Information Processing System 1> Next, an example of the functional configuration of the information processing system 1 in this embodiment will be described with reference to Figures 4 to 7.

[0045] ≪Functional Configuration of Document Management Server 10≫ Figure 4 is a block diagram illustrating the functional configuration of the document management server 10 in this embodiment. As shown in Figure 4, the document management server 10 in this embodiment includes a screen information provision unit 11, a document management unit 12, a workflow control unit 13, a screen information storage unit 101, a document storage unit 102, a metadata storage unit 103, and a workflow information storage unit 104. The document management unit 12 includes a document receiving unit 121, a metadata setting unit 122, and a document transmission unit 123. The workflow control unit 13 includes a workflow setting unit 131, a workflow acquisition unit 132, a workflow execution unit 133, and an identification information acquisition unit 134.

[0046] The screen information provision unit 11, document management unit 12, and workflow control unit 13 of the document management server 10 are realized, for example, by a process in which a program deployed from the HD 504 shown in Figure 2 onto the RAM 503 is executed by the CPU 501.

[0047] The screen information storage unit 101, document storage unit 102, metadata storage unit 103, and workflow information storage unit 104 of the document management server 10 are implemented, for example, using the HD504 shown in Figure 2. Reading or writing data stored in the HD504 is performed, for example, via the HDD controller 505.

[0048] The screen information provision unit 11 provides screen information stored in the screen information storage unit 101 to the browser 31 of the user terminal 30 in response to a request from the browser 31. The screen information stored in the screen information storage unit 101 is information representing a screen for performing operations on the document management server 10.

[0049] The document management unit 12 stores documents and metadata received from the user terminal 30 and performs processing on the documents and metadata according to the workflow executed by the workflow control unit 13.

[0050] The document receiving unit 121 receives documents from the user terminal 30. The document receiving unit 121 also stores the documents received from the user terminal 30 in the document storage unit 102.

[0051] The metadata setting unit 122 receives metadata from the user terminal 30. The metadata setting unit 122 also associates the metadata received from the user terminal 30 with the document stored in the document storage unit 102 and stores it in the metadata storage unit 103.

[0052] Metadata contains one or more attribute pieces of information that represent the content of a document. Because metadata is managed separately from the document itself, editing metadata, such as adding or deleting items or changing metadata values, does not affect the document itself.

[0053] The document transmission unit 123 transmits the contract documents stored in the document storage unit 102 to the electronic contract server 20 in response to a request from the workflow control unit 13. The document transmission unit 123 also transmits the destination information of the documents transmitted to the electronic contract server 20.

[0054] The workflow control unit 13 sets up, retrieves, and executes a workflow that describes the processing content for the document.

[0055] The workflow setting unit 131 receives workflow information from the user terminal 30. The workflow setting unit 131 also stores the workflow information received from the user terminal 30 in the workflow information storage unit 104.

[0056] The workflow acquisition unit 132 acquires the workflow information stored in the workflow information storage unit 104.

[0057] The workflow execution unit 133 executes the workflow according to the workflow information acquired by the workflow acquisition unit 132. The workflow execution unit 133 identifies the next task to be performed on the document and assigns that task to the user who should handle it. The workflow execution unit 133 also performs processing on the document in response to user operations. Processing on the document includes processing performed in cooperation with external systems.

[0058] The identification information acquisition unit 134 acquires identification information from the electronic contract server 20 to identify documents related to contracts stored in the electronic contract server 20. In this embodiment, the identification information acquisition unit 134 receives the identification information transmitted by the electronic contract server 20. The identification information acquisition unit 134 updates the metadata stored in the metadata storage unit 103 to include the identification information received from the electronic contract server 20.

[0059] The screen information storage unit 101 stores the screen information that the screen information provision unit 11 provides to the browser 31. Each piece of screen information stored by the screen information storage unit 101 is, for example, screen information written in HTML (HyperText Markup Language), and may also include applications written in JavaScript (registered trademark).

[0060] The document storage unit 102 stores documents managed by the document management unit 12. The documents stored in the document storage unit 102 are the electronic files themselves that represent the content of the documents. The documents are stored in the document storage unit 102 in a file format corresponding to the file system of the document storage unit 102.

[0061] The metadata storage unit 103 stores metadata associated with documents managed by the document management unit 12. The metadata is stored in the metadata table stored by the metadata storage unit 103.

[0062] The workflow information storage unit 104 stores workflow information related to the workflow executed by the workflow control unit 13. The workflow information may be written in an electronic file in text format or stored in a database table.

[0063] ≪Functional Configuration of Electronic Contract Server 20≫ Figure 5 is a block diagram illustrating the functional configuration of the electronic contract server 20 in this embodiment. As shown in Figure 5, the electronic contract server 20 in this embodiment includes a screen information provision unit 21, a contract management unit 22, a screen information storage unit 201, a contract storage unit 202, a destination information storage unit 203, and a setting information storage unit 204. The contract management unit 22 includes a contract receiving unit 221, a contract setting unit 222, a contract transmission unit 223, and an identification information transmission unit 224.

[0064] The screen information provision unit 21 and the contract management unit 22 of the electronic contract server 20 are realized, for example, by a process in which a program deployed from the HD 504 shown in Figure 2 onto the RAM 503 is executed by the CPU 501.

[0065] The screen information storage unit 201, contract storage unit 202, destination information storage unit 203, and setting information storage unit 204 of the electronic contract server 20 are implemented, for example, using the HD504 shown in Figure 2. Reading or writing data stored in the HD504 is performed, for example, via the HDD controller 505.

[0066] The screen information provision unit 21 provides screen information stored in the screen information storage unit 201 to the browser 31 on the user terminal 30 or the browser 41 on the trading partner terminal 40 in response to a request from the browser 31 on the user terminal 30 or the browser 41 on the trading partner terminal 40. The screen information stored in the screen information storage unit 201 is information representing a screen for performing operations on the electronic contract server 20.

[0067] The contract management unit 22 stores contract-related documents received from the document management server 10 and processes the contracts in response to requests from user terminals 30 or business partner terminals 40.

[0068] The contract receiving unit 221 receives contract-related documents from the document management server 10. The contract receiving unit 221 also stores the contract-related documents received from the document management server 10 in the contract storage unit 202. Furthermore, the contract receiving unit 221 stores the destination information received from the document management server 10 in the destination information storage unit 203.

[0069] The contract setting unit 222 processes documents related to contracts stored in the contract storage unit 202. The processing performed by the contract setting unit 222 includes processing to set various settings for the contracts.

[0070] The contract transmission unit 223 transmits the contract-related documents stored in the contract storage unit 202 to the customer terminal 40.

[0071] The identification information transmission unit 224 transmits identification information to the document management server 10 that identifies the documents related to the contracts stored in the contract storage unit 202.

[0072] The screen information storage unit 201 stores the screen information that the screen information provision unit 21 provides to the browser 31 or browser 41.

[0073] The contract storage unit 202 stores documents related to contracts managed by the contract management unit 22. The contract documents stored in the contract storage unit 202 are electronic files that represent the content of the contract documents. The contract documents are stored in the contract storage unit 202 in a file format corresponding to the file system of the contract storage unit 202.

[0074] The destination information storage unit 203 stores destination information that indicates the recipient to whom documents related to contracts managed by the contract management unit 22 are sent. The destination information is stored in the destination information table stored in the destination information storage unit 203.

[0075] The configuration information storage unit 204 stores configuration information that represents the content of the configuration process performed by the contract configuration unit 222. The configuration information is stored in the configuration information table stored by the configuration information storage unit 204.

[0076] ≪Functional Configuration of User Terminal 30≫ Figure 6 is a block diagram illustrating the functional configuration of the user terminal 30 in this embodiment. As shown in Figure 6, the user terminal 30 in this embodiment includes a browser 31. The browser 31 includes a workflow registration unit 311, a document registration unit 312, a document processing unit 313, and a contract processing unit 314.

[0077] The browser 31 on the user terminal 30 is implemented, for example, by a process in which a program loaded onto RAM 503 from HD 504, as shown in Figure 2, is executed by CPU 501.

[0078] Browser 31 requests screen information from the screen information provision unit 11 of the document management server 10, and displays a screen for performing operations on the document management server 10 based on the screen information received from the screen information provision unit 11. Browser 31 also requests screen information from the screen information provision unit 21 of the electronic contract server 20, and displays a screen for performing operations on the electronic contract server 20 based on the screen information received from the screen information provision unit 21.

[0079] The browser 31 executes the screen information received from the screen information provision unit 11, thereby realizing the workflow registration unit 311, the document registration unit 312, and the document processing unit 313. Furthermore, the browser 31 executes the screen information received from the screen information provision unit 21, thereby realizing the contract processing unit 314.

[0080] Furthermore, the workflow registration unit 311 is not limited to a configuration in which the browser 31 executes screen information received from the screen information provision unit 11, but may also be implemented as a dedicated application installed on the user terminal 30.

[0081] The workflow registration unit 311 sends a request to the document management server 10 to configure workflow information in response to user operations on the workflow settings screen. The workflow settings screen is a screen for inputting workflow information to be registered with the document management server 10. Details of the workflow settings screen will be described later.

[0082] The document registration unit 312 sends a document registration request to the document management server 10 in response to user operations on the document registration screen. The document registration screen is a screen for inputting documents to be registered with the document management server 10. Details of the document registration screen will be described later.

[0083] Furthermore, the document registration unit 312 sends a request to the document management server 10 to set metadata for a document in response to user operations on the metadata setting screen. The metadata setting screen is a screen for inputting metadata to be set for a document. Details of the metadata setting screen will be described later.

[0084] The document processing unit 313 sends a task processing request for a document to the document management server 10 in response to user operations on the task processing screen. The task processing screen is a screen for processing tasks for a document. Details of the task processing screen will be described later.

[0085] The contract processing unit 314 selects documents related to the contract in response to user operations on the contract selection screen. The contract processing unit 314 also adds, modifies, or deletes document settings related to the contract in response to user operations on the contract settings screen. Furthermore, the contract processing unit 314 displays the contents of the documents related to the contract on the contract confirmation screen. Details of the contract selection screen, contract settings screen, and contract confirmation screen will be described later.

[0086] ≪Functional Configuration of 40 Client Terminals≫ Figure 7 is a block diagram illustrating the functional configuration of the trading partner terminal 40 in this embodiment. As shown in Figure 7, the trading partner terminal 40 in this embodiment includes a browser 41. The browser 41 includes a contract signing unit 411.

[0087] The browser 41 on the trading partner terminal 40 is implemented, for example, by a process in which a program deployed from the HD 504 shown in Figure 2 onto the RAM 503 is executed by the CPU 501.

[0088] The browser 41 requests screen information from the screen information provision unit 21 of the electronic contract server 20, and displays a screen for performing operations on the electronic contract server 20 based on the screen information received from the screen information provision unit 21.

[0089] The browser 41 executes the screen information received from the screen information provision unit 21, thereby realizing the contract conclusion unit 411.

[0090] The contract signing unit 411 sends an agreement request for contract signing to the electronic contract server 20 in response to the customer's actions on the contract signing screen. Details of the contract signing screen will be described later.

[0091] <Processing procedure of conventional technology> First, an example of the processing procedure of the information processing method executed by the information processing system 1 in the prior art will be explained with reference to Figures 8 and 9. Figures 8 and 9 are sequence diagrams showing the processing procedure of the information processing method in the prior art, indicating that the processing procedure shown in Figure 8 is followed by the processing procedure shown in Figure 9.

[0092] In step S3001, the browser 31 on the user terminal 30 requests the workflow setting screen from the screen information provider 11 in response to the user's operation. The screen information provider 11 returns screen information representing the workflow setting screen stored in the screen information storage unit 101 to the browser 31. Based on the screen information received from the screen information provider 11, the browser 31 displays the workflow setting screen. This activates the workflow registration unit 311.

[0093] Furthermore, if the workflow registration unit 311 is implemented as a dedicated application installed on the user terminal 30, in step S3001, the workflow registration unit 311 is activated in response to user operations on the user terminal 30.

[0094] Here, we will explain the details of the workflow settings screen with reference to Figure 10. Figure 10 is a diagram showing an example of the workflow settings screen 1000.

[0095] As shown in Figure 10, the workflow setting screen 1000 includes a start trigger input field 1001, a first reviewer input field 1002, a second reviewer input field 1003, an approver input field 1004, an external link input field 1005, and a confirmation button 1006.

[0096] The Start Trigger input field 1001 accepts input of information representing the start trigger, which indicates what triggers the start of the workflow. The First Reviewer input field 1002 accepts input of information representing the first reviewer to perform the review in the workflow. The Second Reviewer input field 1003 accepts input of information representing the second reviewer to perform the review in the workflow. The Approver input field 1004 accepts input of information representing the approver to perform the approval in the workflow. The External Integration input field 1005 accepts input of information representing the external system if the workflow is integrated with an external system.

[0097] When the user presses the confirmation button 1006, the workflow registration unit 311 sends a request to the screen information provision unit 11 to set workflow information representing the contents entered in the start trigger input field 1001, the first examiner input field 1002, the second examiner input field 1003, the approver input field 1004, and the external link input field 1005.

[0098] The input fields on the workflow settings screen 1000 can be added, modified, and deleted by the user as needed, depending on the content of the workflow they wish to configure. The number of flows included in the workflow can also be set by the user.

[0099] The configuration of the workflow settings screen is not limited to the workflow settings screen 1000 shown in Figure 10. For example, an intuitive display format such as a flowchart may be adopted.

[0100] Let's return to Figure 8 for explanation. In step S1101, the screen information provision unit 11 receives a request to set workflow information from the workflow registration unit 311. Then, in response to the request to set workflow information, the screen information provision unit 11 sends a request to save workflow information to the workflow control unit 13.

[0101] In step S1301, the workflow setting unit 131 of the workflow control unit 13 receives a request to save workflow information from the screen information provision unit 11. Then, in response to the request to save workflow information, the workflow setting unit 131 stores the workflow information in the workflow information storage unit 104.

[0102] Here, the details of the workflow information stored in the workflow information storage unit 104 will be explained with reference to Figure 11. Figure 11 is a diagram showing an example of workflow information 1040 in this embodiment.

[0103] As shown in Figure 11, the workflow information 1040 in this embodiment has a number, a start trigger, flow 1, flow 2, flow 3, and flow 4 as data items.

[0104] The number is an identifier that identifies the workflow information. The start trigger is information that indicates what triggers the start of that workflow. The start trigger may be triggered by a specific operation, as in the workflow information with number 1, or by the elapsed time interval, as in the workflow information with number 2.

[0105] Flow 1 represents the first flow to be executed in that workflow. Flow 2 represents the second flow to be executed in that workflow. Flow 3 represents the third flow to be executed in that workflow. Flow 4 represents the fourth flow to be executed in that workflow.

[0106] Figure 12 shows another example of workflow information. Workflow information 1040-1 shown in Figure 12 is workflow information in which only the content of the flows included in the workflow is set. Workflow information 1040-2 shown in Figure 12 is workflow information in which the assignment destinations of each flow set in workflow information 1040-1 are set afterwards.

[0107] As shown in Figure 11, the processing content and assignment destination for each flow may be set simultaneously, or the assignment destination may be set later for the already configured processing content, as shown in Figure 12.

[0108] Figure 13 shows a concrete example of workflow information for implementing the processing procedures shown in Figures 8 and 9. As shown in Figure 13, workflow information 1041 represents a workflow that starts when "document saving and metadata (including destination) setting" is performed, then sequentially executes "reviewer's review process" and "approver's approval process," and finally ends with "document upload to the electronic contract system and destination information setting."

[0109] Let's return to Figure 8 for explanation. In step S1302, the workflow acquisition unit 132 of the workflow control unit 13 acquires the workflow information stored in the workflow information storage unit 104.

[0110] In step S3002, the browser 31 on the user terminal 30-1 requests the screen information provider 11 to display the document registration screen in response to the user's operation. The screen information provider 11 returns screen information representing the document registration screen, which is stored in the screen information storage unit 101, to the browser 31. Based on the screen information received from the screen information provider 11, the browser 31 displays the document registration screen. This activates the document registration unit 312.

[0111] Here, we will explain the details of the document registration screen with reference to Figure 14. Figure 14 is a diagram showing an example of the document registration screen 2000.

[0112] As shown in Figure 14, the document registration screen 2000 includes a file input field 2001, a browse button 2002, and a save button 2003. The file input field 2001 accepts input of information representing the location of the electronic file corresponding to the document to be registered. The information representing the location of the electronic file may be an absolute path, a relative path, or information indicating a file on another device described in URI (Uniform Resource Identifier) ​​format.

[0113] When the user clicks the Browse button 2002, a file selection dialog box appears. The user can then select a file using the file selection dialog box, thereby entering data into the file input field 2001.

[0114] When the user presses the save button 2003, the document registration unit 312 sends a registration request for the document identified by the contents entered in the file input field 2001 to the screen information provision unit 11.

[0115] Let's return to Figure 8 for explanation. In step S1102, the screen information provision unit 11 receives a document registration request from the document registration unit 312. Then, in response to the document registration request, the screen information provision unit 11 sends a document saving request to the document management unit 12.

[0116] In step S1201, the document receiving unit 121 of the document management unit 12 receives a document save request from the screen information providing unit 11. The document receiving unit 121 then stores the document in the document storage unit 102 in response to the document save request. At this time, the document storage unit 102 generates a document ID to identify the document.

[0117] In step S1202, the document receiving unit 121 sends a document save notification to the workflow control unit 13, informing it that the document has been saved. The document save notification includes the document ID.

[0118] In step S3003, the document registration unit 312 selects one document from the documents stored in the document storage unit 102 in response to the operator's operation, and requests the screen information provision unit 11 to display a metadata setting screen for setting metadata for that document. The screen information provision unit 11 returns screen information representing the metadata setting screen stored in the screen information storage unit 101 to the browser 31. The browser 31 displays the metadata setting screen based on the screen information received from the screen information provision unit 11.

[0119] Here, we will explain the details of the metadata settings screen with reference to Figure 15. Figure 15 is a diagram showing an example of the metadata settings screen 2100 in the conventional technology.

[0120] As shown in Figure 15, the metadata setting screen 2100 includes a document type input field 2101, a recipient input field 2102, a signing party input field 2103, a signing date input field 2104, an expiration date input field 2105, and a confirmation button 2106.

[0121] The Document Type input field 2101 accepts input of attribute information representing the document type. The Recipient input field 2102 accepts input of attribute information representing the recipient to whom the document should be sent. The Contracting Party input field 2103 accepts input of attribute information representing the contracting party. The Contract Signing Date input field 2104 accepts input of attribute information representing the contract signing date. The Expiration Date input field 2105 accepts input of attribute information representing the contract's expiration date.

[0122] When the user presses the confirmation button 2106, the document registration unit 312 sends a request to the screen information provision unit 11 to set metadata representing the contents entered in the document type input field 2101, the recipient input field 2102, the signing party input field 2103, the signing date input field 2104, and the expiration date input field 2105.

[0123] The input fields on the metadata settings screen 2100 can be added, modified, and deleted by the user as needed, depending on the metadata content they wish to set. Input fields corresponding to items not to be included in the metadata may also be left blank.

[0124] Let's return to Figure 8 for explanation. In step S1103, the screen information provision unit 11 receives a metadata setting request from the document registration unit 312. Then, in response to the metadata setting request, the screen information provision unit 11 sends a metadata save request to the document management unit 12. The metadata save request includes the document ID.

[0125] In step S1203, the metadata setting unit 122 of the document management unit 12 receives a request to save metadata from the screen information provision unit 11. Then, in response to the request to save metadata, the metadata setting unit 122 stores the metadata in the metadata storage unit 103.

[0126] Here, the details of the metadata table stored in the metadata storage unit 103 will be explained with reference to Figure 16. Figure 16 is a diagram showing an example of the metadata table 1030 in the prior art.

[0127] As shown in Figure 16, the metadata table 1030 has data items such as document ID, document type, recipient, signatory, signatory date, and expiration date.

[0128] The document ID is identification information that identifies a document on the document management server 10. In other words, metadata is associated with a document by its document ID.

[0129] The document type is set to the content entered in the document type input field 2101. The recipient is set to the content entered in the recipient input field 2102. The signing party is set to the content entered in the signing party input field 2103. The signing date is set to the content entered in the signing date input field 2104. The expiration date is set to the content entered in the expiration date input field 2105.

[0130] The fields in metadata table 1030 can be added and deleted by the user as needed, depending on the document type, etc. Some fields may not have a value set depending on the document type. For example, in the metadata shown in Figure 16, the document with document ID "333" does not have a value set for the expiration date.

[0131] Figure 17 shows a specific example of a metadata table 1030 in the prior art. Figure 17(A) is an example of metadata generated when the document receiving unit 121 stores a document in the document storage unit 102. As shown in Figure 17(A), at this time, only the document ID is stored.

[0132] Figure 17(B) shows an example of updated metadata when the metadata setting unit 122 stores the metadata in the metadata storage unit 103. As shown in Figure 17(B), at this time, the metadata entered in the metadata setting screen 2100 is stored in association with the document ID.

[0133] Let's return to Figure 8 for explanation. In step S1204, the metadata setting unit 122 sends a metadata saving notification to the workflow control unit 13, informing it that the saving of metadata is complete. The metadata saving notification includes the document ID.

[0134] In step S1303, the workflow execution unit 133 of the workflow control unit 13 sends a review task to the reviewer terminal 30-2 requesting the reviewer to review the document, in accordance with the workflow information acquired by the workflow acquisition unit 132. The review task includes the document ID.

[0135] In step S3004, the browser 31 on the examiner terminal 30-2 receives the examination task. The browser 31 requests the screen information provision unit 11 to display the task processing screen. The screen information provision unit 11 returns screen information representing the task processing screen, which is stored in the screen information storage unit 101, to the browser 31. Based on the screen information received from the screen information provision unit 11, the browser 31 displays the task processing screen. This starts the document processing unit 313.

[0136] Here, we will explain the details of the task processing screen with reference to Figure 18. Figure 18 is a diagram showing an example of the task processing screen 3000.

[0137] As shown in Figure 18, the task processing screen 3000 includes a task list display area 3001, a document preview area 3002, an approval button 3003, and a rejection button 3004.

[0138] The task list display area 3001 shows a list of tasks assigned to the reviewer. The task list includes, for example, the task name and the date the task was received. The document preview area 3002 displays a preview of the document that is the target of the task selected in the task list display area 3001.

[0139] The reviewer examines the document content on the task processing screen 3000. Once the review is complete, the reviewer presses the review button 3003. If the reviewer cannot complete the review, for example, if any deficiencies are found, the reviewer presses the reject button 3004.

[0140] The buttons on the task processing screen 3000 change depending on the workflow content and task type. The task processing screen 3000 shown in Figure 18 is an example of the task processing screen when a review task is selected. For example, if an approval task is selected, an approval button will be displayed instead of a review button.

[0141] When the examiner presses the review button 3003, the document processing unit 313 sends a request to the screen information provision unit 11 to complete the review of that document. When the examiner presses the reject button, the review task is rejected, and the document is returned to the person in charge. From here on, the explanation will continue assuming that the examiner has pressed the review button 3003.

[0142] Let's return to Figure 8 for explanation. In step S1104, the screen information provision unit 11 receives a document review completion request from the examiner terminal 30-2. Then, in response to the document review completion request, the screen information provision unit 11 sends a review completion notification to the workflow control unit 13. The review completion notification includes the document ID.

[0143] In step S1304, the workflow execution unit 133 of the workflow control unit 13 sends an approval task to the approver terminal 30-3, requesting the approver to approve the document, in accordance with the workflow information acquired by the workflow acquisition unit 132. The approval task includes the document ID.

[0144] In step S3005, the browser 31 on the approver terminal 30-3 receives the approval task. The document processing unit 313 displays the task processing screen 3000 related to the approver. The approver reviews the contents of the document on the task processing screen 3000, and once the review is complete, presses the approve button.

[0145] When the approver presses the approve button, the document processing unit 313 sends an approval request for that document to the screen information provision unit 11.

[0146] In step S1105, the screen information provision unit 11 receives a document approval request from the approver terminal 30-3. The screen information provision unit 11 then sends an approval completion notification to the workflow control unit 13 in response to the document approval request. The approval completion notification includes the document ID.

[0147] In step S1305, the workflow execution unit 133 of the workflow control unit 13 receives an approval completion notification from the screen information provision unit 11. The workflow execution unit 133 then sends a document transmission request to the document management unit 12, which is identified by the document ID included in the approval completion notification. The document transmission request includes the document ID.

[0148] In step S1205, the document transmission unit 123 of the document management unit 12 receives a document transmission request from the workflow execution unit 133. The document transmission unit 123 then retrieves the document identified by the document ID included in the document transmission request from the document storage unit 102.

[0149] In step S1206, the document transmission unit 123 transmits the document acquired in step S1205 to the electronic contract server 20.

[0150] In step S2201, the contract receiving unit 221 of the electronic contract server 20 receives a document related to the contract from the document transmission unit 123. The contract receiving unit 221 then stores the document related to the contract in the contract storage unit 202.

[0151] In step S1306, the workflow execution unit 133 of the workflow control unit 13 retrieves metadata associated with the document identified by the document ID from the metadata storage unit 103, according to the workflow information acquired by the workflow acquisition unit 132. Then, the workflow execution unit 133 sends a destination setting request, including the destination included in the metadata, to the electronic contract server 20.

[0152] In step S2202, the contract receiving unit 221 of the electronic contract server 20 determines the destination included in the destination setting request received from the workflow execution unit 133 as the destination for the contract-related document stored in the contract storage unit 202. The contract receiving unit 221 then stores the destination information representing the destination of the contract-related document in the destination information storage unit 203.

[0153] In this embodiment, an email address is used as the destination, but the destination is not limited to an email address. For example, a destination may be set to a telephone number, fax number, or account on various SNS (Social Networking System) services, or any other means of communication that can be transmitted electronically.

[0154] Let's move on to Figure 9 for explanation. In step S3006, the browser 31 on the employee terminal 30-1 requests authentication from the electronic contract server 20. The authentication request includes authentication information about the employee. An example of authentication information is the user ID that identifies the user and the password entered by that user.

[0155] In step S2101, the screen information providing unit 21 receives an authentication request from the browser 31. Based on the authentication information included in the authentication request, the screen information providing unit 21 authenticates the person in charge.

[0156] In step S2102, the screen information provision unit 21 returns screen information to the browser 31, representing the screen to be displayed after authentication, based on the authentication result of the person in charge. If authentication is successful, the screen displayed after authentication is the contract selection screen. If authentication fails, the screen displayed after authentication is the error display screen. From here on, the explanation will continue assuming that the screen information provision unit 21 has successfully authenticated the person in charge.

[0157] In step S3007, the browser 31 on the employee terminal 30-1 displays the contract selection screen based on the screen information received from the screen information provision unit 21. This activates the contract processing unit 314.

[0158] Here, we will explain the details of the contract selection screen with reference to Figure 19. Figure 19 is a diagram showing an example of the contract selection screen 4000 in this embodiment.

[0159] As shown in Figure 19, the contract selection screen 4000 includes a contract list display area 4010 and a status selection area 4020. The contract list display area 4010 includes contract display areas 4011-1 to 4011-6 that display information for each contract. The status selection area 4020 includes status selection buttons 4021-1 to 4021-6 that correspond to each pre-set status.

[0160] In the status selection field 4020, when the person in charge presses any of the status selection buttons 4021, the contract display field 4011 corresponding to the contract in the status corresponding to that status selection button 4021 is displayed in the contract list display field 4010. In the example in Figure 18, six contract display fields 4011 are displayed, but the number of contract display fields 4011 displayed in the contract list display field 4010 varies depending on the number of contracts in the selected status.

[0161] In this embodiment, the contract selection screen 4000 is initially displayed with the status selection button 4021-4 corresponding to the "Concluded" status pressed. That is, the contract list display field 4010 displays a list of contracts for which the conclusion of the contract has been completed. However, the initial display status may be arbitrarily determined.

[0162] When the person in charge selects any of the contract display fields 4011 in the contract list display field 4010, the contract processing unit 314 sends a request to the screen information provision unit 21 to retrieve the document related to the selected contract display field 4011. The document retrieval request includes the document ID.

[0163] Let's return to Figure 9 for explanation. In step S2103, when the screen information provision unit 21 receives a document acquisition request from the contract processing unit 314, it forwards the acquisition request to the contract management unit 22.

[0164] In step S2203, the contract transmission unit 223 of the contract management unit 22 receives a document acquisition request from the screen information provision unit 21. The contract transmission unit 223 acquires the document identified by the document ID from the document storage unit 102. Then, the contract transmission unit 223 transmits the document acquired from the document storage unit 102 to the employee terminal 30-1.

[0165] In step S3008, the contract processing unit 314 on the user terminal 30-1 receives a document from the contract transmission unit 223. The browser 31 on the user terminal 30-1 requests the screen information provision unit 21 to display the contract settings screen. The screen information provision unit 21 returns screen information representing the contract settings screen, which is stored in the screen information storage unit 201, to the browser 31. Based on the screen information received from the screen information provision unit 21, the browser 31 displays the contract settings screen.

[0166] Here, we will explain the details of the contract settings screen with reference to Figure 20. Figure 20 is a diagram showing an example of the contract settings screen 4100 in this embodiment.

[0167] As shown in Figure 20, the contract setting screen 4100 includes a recipient display field 4101, an input item selection field 4102, a file preview field 4103, and a send button 4104.

[0168] The recipient display field 4101 displays the sender and recipient of the document related to the contract being configured. The sender is pre-configured information. The recipient is the recipient information set in the contract. The input item selection field 4102 displays the input items that can be set in the contract. The file preview field 4103 displays a preview of the contents of the document related to the contract being configured.

[0169] After the user selects the input item they want to set from the input item selection field 4102, they can click the desired position in the file preview field 4103 to display the contents of the contract document with that input item set at that position in the file preview field 4103.

[0170] When the user presses the send button 4104, the contract processing unit 314 sends a contract setting request to the screen information provision unit 21, which represents the type and position of each input item set in the file preview area 4103. The contract setting request includes the document ID and setting information representing the type and position of each input item.

[0171] Let's return to Figure 9 for explanation. In step S2104, when the screen information provision unit 21 receives a contract setting request from the contract processing unit 314, it forwards the setting request to the contract management unit 22.

[0172] In step S2204, the contract setting unit 222 of the contract management unit 22 receives a contract setting request from the screen information provision unit 21. The contract setting unit 222 stores the setting information included in the contract setting request in the setting information storage unit 204.

[0173] In step S3009, the browser 31 on the operator's terminal 30-1 sends a request to the screen information provision unit 21 to send a request for contract signing in response to the operator's actions. The request to send a request for contract signing includes a document ID that identifies the document related to the contract.

[0174] In step S2105, when the screen information provision unit 21 receives a request from the browser 31 to send a request to conclude a contract, it forwards the request to the contract management unit 22.

[0175] In step S2205, the contract transmission unit 223 of the contract management unit 22 receives a request to send a contract signing request from the screen information provision unit 21. The contract transmission unit 223 generates a document destination identifier identified by the document ID included in the request to send a contract signing request. The contract transmission unit 223 then sends the contract signing request, including the document destination identifier, to the trading partner terminal 40.

[0176] The request to conclude the contract is sent via a communication method corresponding to the recipient information set in the document containing the contract to be sent. In this embodiment, the request to conclude the contract is sent via email containing the destination identifier of the document. However, the communication method is not limited to email, and various electronically transmitted communication methods such as various social networking services, short messages, and faxes can be used.

[0177] In step S4001, the trading partner terminal 40 receives a request to conclude a contract from the electronic contract server 20. The browser 41 on the trading partner terminal 40, in response to the trading partner user's operation, uses the connection identifier included in the contract conclusion request to request the contract conclusion screen from the screen information provider unit 21. The screen information provider unit 21 generates screen information representing the contract conclusion screen using the connection identifier and sends it back to the browser 41. Based on the screen information received from the screen information provider unit 21, the browser 41 displays the contract conclusion screen. This activates the contract conclusion unit 411.

[0178] Here, the details of the contract signing screen will be explained with reference to Figure 21. Figure 21 is a diagram showing an example of the contract signing screen 4200 in this embodiment.

[0179] As shown in Figure 21, the contract signing screen 4200 includes a recipient display field 4201, an item input field 4202, a file preview field 4203, and an agreement button 4204.

[0180] The recipient display field 4201 displays the sender and recipient of the document related to the contract that is the subject of the request for conclusion. The item input field 4202 accepts input content for the input fields set in the document related to the contract. The file preview field 4203 displays a preview of the contents of the document related to the contract that has been set with the input content from the item input field 4202.

[0181] When a user enters content into the item input field 4202 and then presses the agree button 4204, the contract signing unit 411 sends a request to the screen information provision unit 21 to sign a contract representing the content entered in the item input field 4202. The request to sign the contract includes a document ID and agreement information representing the content entered for each input item.

[0182] Let's return to Figure 9 for explanation. In step S2106, when the screen information provision unit 21 receives a request to conclude a contract from the contract conclusion unit 411, it forwards the conclusion request to the contract management unit 22.

[0183] In step S2206, the contract setting unit 222 of the contract management unit 22 receives a contract signing request from the screen information provision unit 21. The contract setting unit 222 stores the agreement information included in the contract signing request in the setting information storage unit 204.

[0184] In step S2207, the contract setting unit 222 sends a contract signing notification to the person in charge terminal 30-1, including the document destination identifier identified by the document ID included in the contract signing request. In this embodiment, the contract signing notification is sent by email containing the document destination identifier. However, the means of communication is not limited to email, and various electronically transmittable means of communication can be used.

[0185] In step S3010, the user terminal 30-1 receives a contract signing notification from the electronic contract server 20. The browser 31 on the user terminal 30-1 requests the screen information provider 21 to display the contract confirmation screen using the connection destination identifier included in the contract signing notification, in response to the user's operation. The screen information provider 21 generates screen information representing the contract confirmation screen using the connection destination identifier and sends it back to the browser 31. Based on the screen information received from the screen information provider 21, the browser 31 displays the contract confirmation screen.

[0186] Here, the details of the contract confirmation screen will be explained with reference to Figure 22. Figure 22 is a diagram showing an example of the contract confirmation screen 4300 in this embodiment.

[0187] As shown in Figure 22, the contract confirmation screen 4300 includes a contract details display field 4310 and a status selection field 4320. The contract details display field 4310 includes a status display field 4311, a contract name display field 4312, a recipient display field 4313, and a contract preview field 4314.

[0188] The status display field 4311 shows the status of the contract being reviewed. The contract name display field 4312 shows the name of the contract being reviewed. The recipient display field 4313 shows the recipient of the contract being reviewed and the status of each recipient. The contract preview field 4314 shows the contents of the document related to the contract after it has been signed.

[0189] The status selection field 4320 is the same as the status selection field 4020 provided in the contract selection screen 4000 shown in Figure 19. That is, when the person in charge presses one of the status selection buttons 4321 in the status selection field 4320, a list of contracts related to the contract in the status corresponding to that status selection button 4321 is displayed. Then, when the person in charge selects any of the contracts, the information of the selected contract is displayed in the contract details display field 4310.

[0190] <Processing procedure of the information processing method in the first embodiment> Next, an example of the processing procedure of the information processing method executed by the information processing system 1 in this embodiment will be described with reference to Figure 23. Figure 23 is a sequence diagram showing the processing procedure of the information processing method in this embodiment.

[0191] Figure 24 shows a specific example of workflow information for implementing the processing procedure shown in Figure 23. As shown in Figure 24, the workflow information 1042 in this embodiment represents a workflow that starts when "document saving and metadata (including destination) setting" is performed, and then sequentially performs "reviewer's review process", "approver's approval process", "document upload to the electronic contract system and destination information setting", and "acquisition of processing results from the electronic contract system", before ending with "person in charge's document processing".

[0192] Let's return to Figure 23 for explanation. The process from step S3001 to step S2202 is the same as the processing procedure of the information processing system 1 in the prior art shown in Figure 8.

[0193] In step S2211, the identification information transmission unit 224 of the contract management unit 22 generates a connection destination identifier for the document related to the contract stored in the contract storage unit 202 in step S2201. The identification information transmission unit 224 then transmits the connection destination identifier for the document related to the contract to the document management server 10.

[0194] At step S2211, the request to conclude the contract has not yet been sent to the business partner. Therefore, the connection identifier generated by the identification information transmission unit 224 will identify the document related to the contract before it has been concluded. Hereinafter, the connection identifier generated in step S2211 will also be referred to as the "pre-contract conclusion connection identifier".

[0195] In step S1311, the identification information acquisition unit 134 of the document management server 10 receives the pre-contract connection destination identifier from the electronic contract server 20. The workflow execution unit 133 then sends a request to save the identification information to the document management unit 12. The request to save the identification information includes the document ID and the pre-contract connection destination identifier.

[0196] In step S1211, the metadata setting unit 122 of the document management unit 12 receives a request to save identification information from the workflow execution unit 133. The metadata setting unit 122 then updates the metadata stored in the metadata storage unit 103 so that the metadata associated with the document ID included in the request to save identification information includes the pre-contract connection destination identifier.

[0197] Here, the details of the metadata table in this embodiment will be explained with reference to Figure 25. Figure 25 is a diagram showing a specific example of the metadata table 1031 in this embodiment.

[0198] As shown in Figure 25, the metadata table 1031 in this embodiment has data items such as document ID, document type, destination, signing party, signing date, and expiration date, similar to the metadata table 1030 shown in Figure 16, and further includes the URL of the pre-contract document.

[0199] The URL of the pre-contract document is the pre-contract connection identifier included in the request to save the identification information. In other words, metadata table 1031 in this embodiment differs from metadata table 1030 shown in Figure 16 in that the pre-contract connection identifier has been added.

[0200] Figure 25(A) shows an example of metadata generated when the document receiving unit 121 stores a document in the document storage unit 102. As shown in Figure 25(A), at this time, only the document ID is stored.

[0201] Figure 25(B) shows an example of updated metadata when the metadata setting unit 122 stores the metadata in the metadata storage unit 103. As shown in Figure 25(B), at this time, the metadata entered in the metadata setting screen 2100 is stored in association with the document ID.

[0202] Figure 25(C) shows an example of metadata after the metadata setting unit 122 has updated the metadata to include the pre-contract connection destination identifier. As shown in Figure 25(C), at this time, the pre-contract connection destination identifier received from the identification information transmission unit 224 is stored in association with the document ID.

[0203] Let's return to Figure 23 for explanation. In step S1212, the metadata setting unit 122 sends a metadata saving notification to the workflow control unit 13, informing it that the saving of metadata is complete. The metadata saving notification includes the document ID.

[0204] In step S1312, the workflow execution unit 133 of the workflow control unit 13 sends a configuration task to the person in charge terminal 30-1, requesting the person in charge to configure the contract, according to the workflow information acquired by the workflow acquisition unit 132. The configuration task includes a document ID.

[0205] In step S3011, the contract processing unit 314 on the user terminal 30-1 receives a configuration task from the workflow execution unit 133. The browser 31 on the user terminal 30-1 requests the screen information provision unit 11 to display the metadata configuration screen for the document identified by the document ID included in the configuration task, in response to the user's operation. The screen information provision unit 11 returns screen information representing the metadata configuration screen stored in the screen information storage unit 101 to the browser 31. The browser 31 displays the metadata configuration screen based on the screen information received from the screen information provision unit 11.

[0206] Here, the details of the metadata setting screen in this embodiment will be explained with reference to Figure 26. Figure 26 is a diagram showing an example of the metadata setting screen 2110 in this embodiment.

[0207] As shown in Figure 26, the metadata setting screen 2110 in this embodiment, similar to the metadata setting screen 2100 shown in Figure 15, includes a document type input field 2101, a recipient input field 2102, a signing party input field 2103, a signing date input field 2104, an expiration date input field 2105, and a confirmation button 2106, and further includes a pre-contract document display field 2111.

[0208] The pre-contract document display field 2111 displays the pre-contract connection identifier set in the URL of the pre-contract document in the metadata table 1031. In other words, the metadata setting screen 2110 in this embodiment differs from the metadata setting screen 2100 shown in Figure 15 in that the pre-contract connection identifier has been added.

[0209] The browser 31 on the user terminal 30-1 requests the contract setting screen from the screen information provision unit 21 using the pre-contract connection destination identifier, in response to the user's operation on the metadata setting screen 2110. The screen information provision unit 21 generates screen information representing the contract setting screen using the pre-contract connection destination identifier and sends it back to the browser 31. The browser 31 displays the contract setting screen based on the screen information received from the screen information provision unit 21.

[0210] The operation to display the contract settings screen from the metadata settings screen 2110 is, for example, clicking the URL of the pre-contract signing document on the metadata settings screen 2110.

[0211] In this embodiment, the contract setting screen can directly display documents related to the contract to be set by using a pre-contract connection identifier. In the processing procedure of the information processing system 1 in the prior art, it was necessary to select the contract to be set on the contract selection screen in order to display the contract setting screen (see steps S3007 to S3008).

[0212] Subsequently, the processing from step S2104 to step S3010 is performed in the same manner as the processing procedure of the information processing system 1 in the conventional technology shown in Figure 9.

[0213] <Effects of the First Embodiment> In this embodiment, the information processing system 1 stores documents managed by the document management server 10 in association with connection identifiers used to identify those documents in the electronic contract server 20, and outputs screen information to the user terminal 30 that displays the connection identifiers in association with information about the documents.

[0214] This allows users to directly view documents stored in the electronic contract server 20 based on the connection identifier displayed on the screen output by the document management server 10. Therefore, users can avoid the hassle of logging into the electronic contract server 20 each time to check the contents of documents stored in the electronic contract server 20 and finding the desired document among many documents.

[0215] [Second Embodiment] In the first embodiment, when the electronic contract server 20 received a document from the document management server 10, it sent a connection identifier to the document management server 10 that identifies the document relating to the contract before its conclusion. The document management server 10 stored the connection identifier received from the electronic contract server 20 in the metadata associated with the document.

[0216] In the second embodiment, the document management server 10 obtains a connection identifier from the electronic contract server 20 at predetermined time intervals to identify documents related to contracts. The document management server 10 stores the connection identifiers corresponding to each state of the contract (e.g., before contract signing and after contract signing) in the metadata associated with the document.

[0217] <Processing procedure of the information processing method in the second embodiment> First, an example of the processing procedure of the information processing method executed by the information processing system 1 in this embodiment will be described with reference to Figures 27 and 28. Figures 27 and 28 are sequence diagrams showing the processing procedure of the information processing method in this embodiment, indicating that the processing procedure shown in Figure 27 is followed by the processing procedure shown in Figure 28.

[0218] Figure 29 is a concrete example of workflow information for realizing the processing procedures shown in Figures 27 and 28. As shown in Figure 29, the workflow information 1043 in this embodiment represents a workflow that starts when "document saving and metadata (including destination) setting" is performed, and then sequentially performs "reviewer's review process", "approver's approval process", "uploading the document to the electronic contract system and setting destination information", "obtaining processing results from the electronic contract system", "person in charge's document processing", "obtaining document information from the electronic contract system (periodically executed)", and "notifying the approver of contract completion", before ending with "approver confirms the document after contract signing".

[0219] Let's return to Figure 27 for explanation. The process from step S3001 to step S2202 is the same as the processing procedure of the information processing system 1 in the first embodiment shown in Figure 23.

[0220] In step S1321, the workflow execution unit 133 of the workflow control unit 13 starts the workflow when a predetermined time interval has elapsed, in accordance with the workflow information acquired by the workflow acquisition unit 132.

[0221] In step S1322, the identification information acquisition unit 134 of the workflow control unit 13 sends a request to the electronic contract server 20 to acquire a connection destination identifier.

[0222] In step S2221, the identification information transmission unit 224 of the contract management unit 22 receives a request from the identification information acquisition unit 134 to acquire a connection destination identifier. For documents relating to contracts that have not yet been concluded and have not yet sent a connection destination identifier, the identification information transmission unit 224 generates a connection destination identifier and sends it back to the identification information transmission unit 224.

[0223] The connection destination identifier generated by the identification information transmission unit 224 in step S2221 is a pre-contract connection destination identifier that identifies documents related to the contract before the contract is concluded.

[0224] Furthermore, the pre-contract connection identifier transmitted by the identification information transmission unit 224 in step S2221 is the pre-contract connection identifier for the contract document newly received from the document management server 10 since the last execution of step S2221. Therefore, the identification information transmission unit 224 may transmit multiple pre-contract connection identifiers, or it may not transmit any pre-contract connection identifiers.

[0225] The processing from step S1311 to step S2204 is the same as the processing procedure of the information processing system 1 in the first embodiment shown in Figure 23.

[0226] Let's move on to Figure 28 for further explanation. The process from step S3009 to step S2206 is the same as the processing procedure of the information processing system 1 in the prior art shown in Figure 9.

[0227] In step S1323, the identification information acquisition unit 134 of the workflow control unit 13 sends a request to the electronic contract server 20 to acquire a connection destination identifier.

[0228] In step S2222, the identification information transmission unit 224 of the contract management unit 22 receives a request from the identification information acquisition unit 134 to acquire a connection destination identifier. For contract documents after the contract has been concluded that have not yet transmitted a connection destination identifier, the identification information transmission unit 224 generates a connection destination identifier and sends it back to the identification information transmission unit 224.

[0229] The connection destination identifier generated by the identification information transmission unit 224 in step S2222 is a connection destination identifier that identifies documents related to the contract after the contract has been concluded. Hereinafter, the connection destination identifier generated in step S2222 will also be referred to as the "post-contract conclusion connection destination identifier".

[0230] Furthermore, the post-contract connection identifier transmitted by the identification information transmission unit 224 in step S2222 is the post-contract connection identifier for the contract document for which agreement information has been newly received from the trading partner terminal 40 since the last execution of step S2222. Therefore, the identification information transmission unit 224 may transmit multiple post-contract connection identifiers, or it may not transmit any post-contract connection identifiers.

[0231] In step S1323, the identification information acquisition unit 134 of the document management server 10 receives the post-contract connection destination identifier from the electronic contract server 20. The workflow execution unit 133 then sends a request to save the identification information to the document management unit 12. The request to save the identification information includes the document ID and the post-contract connection destination identifier.

[0232] In step S1221, the metadata setting unit 122 of the document management unit 12 receives a request to save identification information from the workflow execution unit 133. The metadata setting unit 122 then updates the metadata stored in the metadata storage unit 103 so that the metadata associated with the document ID included in the request to save identification information includes the post-contract connection destination identifier.

[0233] Here, the details of the metadata table in this embodiment will be explained with reference to Figure 30. Figure 30 is a diagram showing a specific example of the metadata table 1032 in this embodiment.

[0234] As shown in Figure 30, the metadata table 1032 in this embodiment has data items similar to the metadata table 1031 shown in Figure 25, such as document ID, document type, recipient, signing party, signing date, expiration date, and URL of the pre-contract document, and further includes the URL of the post-contract document.

[0235] The URL of the post-contract document is the post-contract connection destination identifier included in the request to save the identification information. In other words, the metadata table 1032 in this embodiment differs from the metadata table 1031 shown in Figure 25 in that the post-contract connection destination identifier has been added.

[0236] Figure 30(A) shows an example of metadata after the metadata setting unit 122 has updated the metadata to include the pre-contract connection destination identifier. As shown in Figure 30(A), at this time, the pre-contract connection destination identifier received from the identification information transmission unit 224 is stored in association with the document ID.

[0237] Figure 30(B) shows an example of metadata after the metadata setting unit 122 has updated the metadata to include the post-contract connection identifier. As shown in Figure 30(B), at this time, the post-contract connection identifier received from the identification information transmission unit 224 is stored in association with the document ID.

[0238] Let's return to Figure 28 for explanation. In step S1324, the workflow execution unit 133 of the workflow control unit 13 sends a confirmation task to the approver terminal 30-3, requesting the approver to review the contract after its conclusion, in accordance with the workflow information acquired by the workflow acquisition unit 132. The confirmation task includes a document ID.

[0239] In step S3021, the contract processing unit 314 of the approver terminal 30-3 receives a confirmation task from the workflow execution unit 133. The browser 31 of the approver terminal 30-3 requests the screen information provision unit 11 to display the metadata setting screen for the document identified by the document ID included in the confirmation task, in response to the approver's operation. The screen information provision unit 11 returns screen information representing the metadata setting screen stored in the screen information storage unit 101 to the browser 31. The browser 31 displays the metadata setting screen based on the screen information received from the screen information provision unit 11.

[0240] Here, the details of the metadata setting screen in this embodiment will be explained with reference to Figure 31. Figure 31 is a diagram showing an example of the metadata setting screen 2120 in this embodiment.

[0241] As shown in Figure 31, the metadata setting screen 2120 in this embodiment, similar to the metadata setting screen 2110 shown in Figure 26, includes a document type input field 2101, a recipient input field 2102, a signing party input field 2103, a signing date input field 2104, an expiration date input field 2105, a confirmation button 2106, and a pre-contract document display field 2111, and further includes a post-contract document display field 2121.

[0242] The post-contract document display field 2121 displays the post-contract connection identifier set in the URL of the post-contract document in the metadata table 1032. In other words, the metadata setting screen 2120 in this embodiment differs from the metadata setting screen 2110 shown in Figure 26 in that the post-contract connection identifier has been added.

[0243] The browser 31 on the approver terminal 30-3 requests the contract confirmation screen from the screen information provision unit 21 using the post-contract connection identifier, in response to the approver's operation on the metadata setting screen 2120. The screen information provision unit 21 generates screen information representing the contract confirmation screen using the post-contract connection identifier and sends it back to the browser 31. The browser 31 displays the contract confirmation screen based on the screen information received from the screen information provision unit 21.

[0244] The operation to display the contract confirmation screen from the metadata settings screen 2120 is, for example, clicking on the URL of the pre-contract signing document or the URL of the post-contract signing document on the metadata settings screen 2120.

[0245] In this embodiment, the metadata setting screen simultaneously displays the pre-contract connection identifier and the post-contract connection identifier. This allows the contents of the contract documents before and after contract signing to be displayed directly from the same screen. For example, if a user wants to compare and review the pre-contract documents and the post-contract documents, the amount of effort required is significantly reduced compared to conventional methods, making it highly convenient.

[0246] <Effects of the second embodiment> In this embodiment, the information processing system 1 obtains a connection identifier from the electronic contract server 20 at predetermined time intervals to identify documents related to contracts. This allows the document management server 10 to store connection identifiers related to contracts before they are concluded and connection identifiers related to contracts after they are concluded in association with each other.

[0247] Since the electronic contract server 20 sends a notification that the contract has been concluded only to the employee's terminal 30-1, it was previously difficult for anyone other than the employee to recognize that the contract had been concluded. According to the information processing system 1 in this embodiment, since the document with the connection destination identifier set after the contract has been concluded indicates that the contract has been concluded, it becomes possible for anyone other than the employee to recognize that the contract has been concluded.

[0248] Furthermore, because the connection identifier before and after the contract is linked, users can easily compare documents related to the contract before and after the contract is signed.

[0249] [supplement] In each of the above embodiments, the document management server 10 is an example of an information processing device. The electronic contract server 20 is an example of a second information processing device. A document is an example of electronic data. The document transmission unit 123 is an example of a transmission unit. The identification information transmission unit 224 is an example of a generation unit. The browser 31 is an example of a screen display unit. Step S1206, performed by the document transmission unit 123, is an example of a transmission procedure. Step S1311, performed by the identification information acquisition unit 134, is an example of an acquisition procedure. Step S3011, performed by the screen information provision unit 11, is an example of a provision procedure.

[0250] Each of the functions of the embodiments described above can be realized by one or more processing circuits. Hereinafter, "processing circuit" as used herein includes processors programmed to execute each function by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), and conventional circuit modules designed to execute each of the functions described above.

[0251] The apparatus described in the examples represents only one of several computing environments for carrying out the embodiments disclosed herein. In one embodiment, the document management server 10 and the electronic contract server 20 include multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other via any type of communication link, including networks and shared memory, and to perform the processes disclosed herein.

[0252] Although embodiments of the present invention have been described in detail above, the present invention is not limited to these embodiments, and various modifications or changes are possible within the scope of the gist of the present invention as described in the claims. [Explanation of symbols]

[0253] 1. Information Processing System 10. Document Management Server 11 Screen information provision department 12 Document Management Department 101 Screen information storage section 102 Document Storage Unit 103 Metadata storage unit 104 Workflow Information Storage Unit 121 Document Receiving Unit 122 Metadata setting section 123 Document Transmission Section 13 Workflow Control Unit 131 Workflow Settings Section 132 Workflow Acquisition Section 133 Workflow Execution Unit 134 Identification Information Acquisition Unit 20 Electronic contract server 21 Screen information provision department 22 Contract Management Department 201 Screen information storage section 202 Contract storage section 203 Destination Information Storage Unit 204 Configuration Information Storage Unit 221 Contract Receiving Department 222 Contract Formulation Department 223 Contract Transmission Department 224 Identification Information Transmission Unit 30 User terminals 31 Browsers 311 Workflow Registration Section 312 Document Registration Department 313 Document Processing Unit 314 Contract Processing Department 40. Customer terminals 41 Browsers 411 Contracts Department [Prior art documents] [Patent Documents]

[0254]

Patent Document 1

Claims

1. An information processing device that can communicate with a second information processing device via a network, A receiving unit that receives electronic data transmitted from a user terminal, A storage unit generates first identification information for identifying the received electronic data, and stores the generated first identification information in association with the metadata of the electronic data. A transmitting unit transmits the electronic data to a second information processing device after the first identification information has been stored in the storage unit. An identification information acquisition unit acquires from the second information processing device a second identification information generated in the second information processing device for identifying the electronic data transmitted by the transmission unit, the second information processing device having identified the electronic data. Equipped with, The storage unit further stores the second identification information acquired by the identification information acquisition unit from the second information processing device in association with the first identification information stored by the transmission unit before transmitting the electronic data to the second information processing device. The information processing device further comprises a screen information providing unit that provides screen information for displaying a screen including the metadata to the user terminal, When an operation is performed on the screen displayed on the user terminal, the electronic data is displayed on the user terminal, and the displayed electronic data is electronic data acquired from the second information processing device using the second identification information. Information processing device.

2. An information processing apparatus according to claim 1, The aforementioned screen is the metadata settings screen, The metadata of the electronic data is input via the metadata setting screen and stored in the storage unit in association with the first identification information of the electronic data. Information processing device.

3. The second identification information is a URL that identifies the location of the electronic data in the electronic space of the second information processing device. The information processing apparatus according to claim 1.

4. The electronic data is a document relating to a contract. The information processing apparatus according to claim 1.

5. An information processing system comprising a user terminal and an information processing device that can communicate with the user terminal and a second information processing device via a network, The aforementioned information processing device is The electronic data transmitted from the user terminal is received by the receiving unit, A storage unit generates first identification information for identifying the received electronic data, and stores the generated first identification information in association with the metadata of the electronic data. A transmitting unit transmits the electronic data to a second information processing device after the first identification information has been stored in the storage unit. An identification information acquisition unit acquires from the second information processing device a second identification information generated in the second information processing device for identifying the electronic data transmitted by the transmission unit, the second information processing device having identified the electronic data. Equipped with, The storage unit further stores the second identification information acquired by the identification information acquisition unit from the second information processing device in association with the first identification information stored by the transmission unit before transmitting the electronic data to the second information processing device. The information processing device further comprises a screen information providing unit that provides screen information for displaying a screen including the metadata to the user terminal, The aforementioned user terminal is A document registration unit transmits the electronic data to the information processing device, A screen display unit that displays the screen based on the screen information provided by the information processing device, Equipped with, The screen display unit further displays the electronic data in response to an operation on the screen, and the displayed electronic data is electronic data acquired from the second information processing device using the second identification information. Information processing system.

6. The screen information provided from the information processing device to the user terminal includes the second identification information used to identify the electronic data in the second information processing device, The screen display unit, in response to an operation on the screen, uses the second identification information to acquire the electronic data from the second information processing device and displays the acquired electronic data. The information processing system according to claim 5.

7. A system comprising a user terminal, an information processing device, and a second information processing device, The aforementioned information processing device is A first receiving unit that receives electronic data transmitted from a user terminal, A first storage unit generates first identification information for identifying the received electronic data, and stores the generated first identification information in association with the metadata of the electronic data. A first transmission unit transmits the electronic data to the second information processing device after the first identification information has been stored in the first storage unit, An identification information acquisition unit acquires from the second information processing device second identification information, which is generated in the second information processing device for the electronic data transmitted by the first transmission unit and used to identify the electronic data in the second information processing device, Equipped with, The aforementioned second information processing device is A second receiving unit that receives the electronic data transmitted from the information processing device, A second storage unit that stores the received electronic data, A second transmission unit generates the second identification information from the received electronic data and transmits the generated second identification information to the information processing device, Equipped with, The first storage unit further stores the second identification information acquired by the identification information acquisition unit from the second information processing device in association with the first identification information stored by the first transmission unit before transmitting the electronic data to the second information processing device. The information processing device further comprises a screen information providing unit that provides screen information for displaying a screen including the metadata to the user terminal, The aforementioned user terminal is A document registration unit transmits the electronic data to the information processing device, A screen display unit that displays the screen based on the screen information provided by the information processing device, Equipped with, The screen display unit further displays the electronic data in response to an operation on the screen, and the displayed electronic data is electronic data acquired from the second information processing device using the second identification information. system.

8. An information processing device that can communicate with a second information processing device via a network, The receiving procedure for receiving electronic data transmitted from a user terminal, A storage procedure comprising: generating a first identification information for identifying the received electronic data; associating the generated first identification information with the metadata of the electronic data and storing it in a storage unit; A transmission procedure comprising: transmitting the electronic data to the second information processing device after the first identification information has been stored in the storage unit; An identification information acquisition procedure, which involves acquiring from the second information processing device a second identification information generated in the second information processing device for the electronic data transmitted by the transmission procedure, for use in the second information processing device to identify the electronic data, Execute, The storage procedure further stores the second identification information obtained by the identification information acquisition procedure from the second information processing device in association with the first identification information stored by the transmission procedure before transmitting the electronic data to the second information processing device. The information processing device further performs a screen information provision procedure to provide the user terminal with screen information for displaying the screen containing the metadata, When an operation is performed on the screen displayed on the user terminal, the electronic data is displayed on the user terminal, and the displayed electronic data is electronic data acquired from the second information processing device using the second identification information. Information processing methods.

9. An information processing method performed by an information processing system, comprising a user terminal and an information processing device that can communicate with the user terminal and a second information processing device via a network, The aforementioned information processing device A receiving procedure for receiving electronic data transmitted from the user terminal, A storage procedure comprising: generating a first identification information for identifying the received electronic data; associating the generated first identification information with the metadata of the electronic data and storing it in a storage unit; A transmission procedure comprising: transmitting the electronic data to the second information processing device after the first identification information has been stored in the storage unit; An identification information acquisition procedure, which involves acquiring from the second information processing device a second identification information generated in the second information processing device for the electronic data transmitted by the transmission procedure, for use in the second information processing device to identify the electronic data, Execute, The storage procedure further stores the second identification information obtained by the identification information acquisition procedure from the second information processing device in association with the first identification information stored by the transmission procedure before transmitting the electronic data to the second information processing device. The information processing device further performs a screen information provision procedure to provide the user terminal with screen information for displaying the screen containing the metadata, The aforementioned user terminal A document registration procedure for transmitting the electronic data to the information processing device, A first screen display procedure, which involves displaying the screen based on the screen information provided by the information processing device, A second screen display procedure, in which the electronic data is displayed in response to an operation on the screen displayed in the first screen display procedure, Execute, The electronic data displayed in the second screen display procedure is electronic data acquired from the second information processing device using the second identification information. Information processing methods.

10. A method to be performed by a system including a user terminal, an information processing device, and a second information processing device, The aforementioned information processing device A first receiving procedure for receiving electronic data transmitted from a user terminal, A first storage procedure involves generating a first identification information for identifying the received electronic data, and storing the generated first identification information and the metadata of the electronic data in a storage unit in association with each other. A first transmission procedure, in which the first identification information is stored in the storage unit, and the electronic data is transmitted to the second information processing device, An identification information acquisition procedure, which involves acquiring from the second information processing device a second identification information generated in the second information processing device for identifying the electronic data transmitted by the first transmission procedure, Execute, The second information processing device described above, A second receiving procedure for receiving the electronic data transmitted from the information processing device, A second storage procedure for storing the received electronic data, A second transmission procedure comprising generating the second identification information from the received electronic data and transmitting the generated second identification information to the information processing device, Execute, The first storage procedure further stores the second identification information acquired by the identification information acquisition procedure from the second information processing device in association with the first identification information stored before the first transmission procedure transmitted the electronic data to the second information processing device. The information processing device further performs a screen information provision procedure to provide the user terminal with screen information for displaying the screen containing the metadata, The aforementioned user terminal A document registration procedure for transmitting the electronic data to the information processing device, A first screen display procedure, which involves displaying the screen based on the screen information provided by the information processing device, A second screen display procedure, in which the electronic data is displayed in response to an operation on the screen displayed in the first screen display procedure, Execute, The electronic data displayed in the second screen display procedure is electronic data acquired from the second information processing device using the second identification information. method.

11. An information processing device that can communicate with a second information processing device via a network, The receiving procedure for receiving electronic data transmitted from a user terminal, A storage procedure comprising: generating a first identification information for identifying the received electronic data; associating the generated first identification information with the metadata of the electronic data and storing it in a storage unit; A transmission procedure comprising: transmitting the electronic data to the second information processing device after the first identification information has been stored in the storage unit; An identification information acquisition procedure, which involves acquiring from the second information processing device a second identification information generated in the second information processing device for the electronic data transmitted by the transmission procedure, for use in the second information processing device to identify the electronic data, Make it run, The storage procedure further stores the second identification information obtained by the identification information acquisition procedure from the second information processing device in association with the first identification information stored by the transmission procedure before transmitting the electronic data to the second information processing device. The information processing device is further instructed to perform a screen information provision procedure, which involves providing the user terminal with screen information for displaying a screen containing the metadata. When an operation is performed on the screen displayed on the user terminal, the electronic data is displayed on the user terminal, and the displayed electronic data is electronic data acquired from the second information processing device using the second identification information. program.

Images