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

Abstract

To provide an information processing apparatus for electronically managing electronic data, such as documents generated in the course of business in a company, or the like, an information processing system, an information processing method, and a program.SOLUTION: In an information processing system configured so that a document management server, an electronic contract server, a user terminal, and a client terminal connect to a communication network, the document management server 10 includes a screen information providing unit 11, a document management unit 12, and a workflow control unit 13. The screen information providing unit 11 provides screen information stored in a screen information storage unit 101 to a browser of the user terminal. The document management unit 12 stores a document and metadata received from the user terminal, and executes processing on the document and the metadata in accordance with a workflow executed by the workflow control unit 13. The workflow control unit 13 sets, acquires, and executes a workflow including the description of content of the processing on the document.SELECTED DRAWING: Figure 4

Description

[Technical Field]

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

[0002] Document management systems are used to electronically manage electronic data such as documents generated in business. Electronic contract systems are also used to electronically conclude contracts using electronic data. An information processing device such as a document management system is linked to a second information processing device such as an electronic contract system, and the electronic data used by the second information processing device to conclude the contract is managed by the information processing device.

[0003] Patent Document 1 discloses a document processing device that can switch document processing operations based on metadata added to electronic document data. Summary of the Invention [Problem to be solved by the invention]

[0004] However, there is a problem in that a screen for requesting electronic data from the second information processing device is not provided to the information processing device. For example, in the past, when a user wanted to display electronic data stored in the second information processing device, he or she had to log in to the second information processing device and find the desired electronic data.

[0005] In view of the above technical problems, an embodiment of the present invention has an object to provide an information processing device with a screen for requesting electronic data from a second information processing device. [Means for solving the problem]

[0006] In order to solve the above problem, an information processing device that 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 is equipped with a transmitting unit that transmits the electronic data to the second information processing device, an identification information acquiring 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 providing unit that provides the user terminal with a screen that requests electronic data having the identification information from the second information processing device. [Effects of the Invention]

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

[0008] [Figure 1] 1 is a diagram illustrating an example of the overall configuration of an information processing system according to an embodiment; [Figure 2] FIG. 1 is a diagram illustrating an example of a hardware configuration of an information processing device according to an embodiment. [Figure 3] FIG. 1 is a diagram illustrating an example of a hardware configuration of an image forming apparatus according to an embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of the functional configuration of a document management server according to the first embodiment. [Figure 5] FIG. 2 is a diagram illustrating an example of the functional configuration of an electronic contract server in the first embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of the functional configuration of a user terminal in the first embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of a functional configuration of a customer terminal in the first embodiment. [Figure 8] FIG. 1 is a diagram illustrating a processing procedure of an information processing system according to a conventional technique. [Figure 9] FIG. 1 is a diagram illustrating a processing procedure of an information processing system according to a conventional technique. [Figure 10] FIG. 10 is a diagram illustrating an example of a workflow setting screen according to an embodiment. [Figure 11] FIG. 10 is a diagram illustrating an example of workflow information according to an embodiment. [Figure 12] FIG. 10 is a diagram illustrating another example of workflow information according to an embodiment. [Figure 13] FIG. 10 is a diagram illustrating a specific example of workflow information according to an embodiment. [Figure 14] FIG. 10 is a diagram illustrating an example of a document registration screen according to an embodiment. [Figure 15] FIG. 1 is a diagram showing an example of a metadata setting screen in the prior art. [Figure 16] FIG. 1 is a diagram illustrating an example of a metadata table in the prior art. [Figure 17] 17A and 17B are diagrams showing specific examples of metadata tables in the prior art. Fig. 17A shows a specific example of metadata generated when a document is stored. Fig. 17B shows a specific example of metadata updated when the metadata is set. [Figure 18] FIG. 10 is a diagram illustrating an example of a task processing screen according to an embodiment. [Figure 19] FIG. 10 is a diagram illustrating an example of a contract selection screen according to an embodiment. [Figure 20] FIG. 10 is a diagram illustrating an example of a contract setting screen according to an embodiment. [Figure 21] FIG. 10 is a diagram illustrating an example of a contract signing screen according to an embodiment. [Figure 22] FIG. 10 is a diagram illustrating an example of a contract confirmation screen according to an embodiment. [Figure 23] FIG. 2 is a diagram illustrating a processing procedure of the information processing system in the first embodiment. [Figure 24] FIG. 3 is a diagram illustrating an example of workflow information according to the first embodiment. [Figure 25]Fig. 25 is a diagram showing a specific example of a metadata table in the first embodiment. Fig. 25(A) is a diagram showing a specific example of metadata generated when a document is stored. Fig. 25(B) is a diagram showing a specific example of metadata updated when metadata is set. Fig. 25(C) is a diagram showing a specific example of metadata updated when a connection destination identifier is acquired. [Figure 26] FIG. 2 is a diagram showing an example of a metadata setting screen in the first embodiment. [Figure 27] FIG. 10 is a diagram illustrating a processing procedure of an information processing system according to a second embodiment. [Figure 28] FIG. 10 is a diagram illustrating a processing procedure of an information processing system according to a second embodiment. [Figure 29] FIG. 11 is a diagram illustrating an example of workflow information according to the second embodiment. [Figure 30] 30A and 30B are diagrams showing specific examples of metadata tables in the second embodiment. Fig. 30A is a diagram showing a specific example of metadata updated when a connection destination identifier before contract conclusion is acquired. Fig. 30B is a diagram showing a specific example of metadata updated when a connection destination identifier after contract conclusion is acquired. [Figure 31] FIG. 11 is a diagram showing an example of a metadata setting screen in the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In the drawings, components having the same functions are designated by the same reference numerals, and duplicated explanations will be omitted.

[0010] [background] A document management system is an information processing system for electronically storing, managing, and utilizing documents generated in the course of business at a company, etc. An electronic contract system is an information processing system for electronically concluding contracts at a company, etc.

[0011] Document management systems alone may not be able to cover all business processes. For example, in conventional contract processing, documents processed in a document management system were printed on paper for contract processing. In this case, paper documents that had been signed or stamped had to be scanned and stored again in the document management system.

[0012] Because paper-based contract processing requires printing and storage costs and is inefficient to search, document management systems and electronic contract systems are commonly used in combination. However, simply using a document management system and an electronic contract system in combination creates the problem that the two systems operate independently, making user operations cumbersome.

[0013] For example, when a user wants to refer to a document stored in an electronic contract system, the user must log in to the electronic contract system and find the desired document from among the many documents stored therein.

[0014] In one embodiment of the present invention, a document managed by a document management server is stored in association with identification information that identifies the document in an electronic contract system, and screen information is output representing a screen that displays the identification information in association with information about the document. This allows a user to view a document stored in the electronic contract system directly from the screen output by the document management server. In other words, this eliminates the need to log in to the electronic contract system and search for the desired document in order to view the document stored in the electronic contract system.

[0015] [First embodiment] In a first embodiment of the present invention, metadata stored by a 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 representing a screen that displays information about the document in association with the identification information to a user terminal.

[0016] The document in this embodiment is electronic data representing the contents of a document, etc. The electronic data is not limited to a document, and may be electronic data representing any information, such as text, an image, or a video.

[0017] The identification information in this embodiment is information that allows direct access to a 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 uniform resource locator (URL) that identifies the location of the document in the 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 an information processing system 1 in this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the overall configuration of an information processing system 1 in this embodiment.

[0019] 1, the information processing system 1 includes a document management server 10, an electronic contract server 20, a person in charge terminal 30-1, an examiner terminal 30-2, an approver terminal 30-3, and a trading partner terminal 40. The person in charge terminal 30-1, the examiner terminal 30-2, and the approver terminal 30-3 are distinguished by the type of user who uses them, but they all have the same functions. Hereinafter, the person in charge terminal 30-1, the examiner terminal 30-2, and the approver terminal 30-3 will also be collectively referred to as user terminals 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 a communication network 100. The communication network 100 is configured so that the connected devices can communicate with each other. The communication network 100 is constructed by a wired communication network such as the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network). The communication network 100 may include not only wired communication but also 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. The document management server 10 associates metadata with documents and stores them, enabling efficient document searches. The document management server 10 also has a function for executing workflows for carrying out business, enabling, for example, efficient implementation of document circulation flows.

[0022] The document management server 10 may be realized by one information processing device, or may be a system realized by a plurality of information processing devices.

[0023] The electronic contract server 20 performs processing to electronically conclude a contract. The electronic contract server 20 transmits a contract to the trading partner, and if the trading partner agrees, performs processing to affix an electronic signature or seal to the contract.

[0024] The electronic contract server 20 may be realized by one information processing device, or may be a system realized by a plurality of information processing devices.

[0025] The user terminal 30 is an electronic device used by a 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 in charge of creating a contract, an examiner who examines the contents of the contract, and an approver who approves the contents of the contract. The person in charge terminal 30-1 is a user terminal 30 used by the person in charge. The examiner terminal 30-2 is a user terminal 30 used by the examiner. The approver terminal 30-3 is a user terminal 30 used by the approver.

[0027] The customer terminal 40 is an electronic device used by a customer user. The customer user can use the customer terminal 40 to perform operations on the electronic contract server 20.

[0028] An example of the document management server 10, the electronic contract server 20, the user terminal 30, and the customer terminal 40 is an information processing device. Another example of the document management server 10, the electronic contract server 20, the user terminal 30, and the customer terminal 40 is an image forming device (printer, FAX device, MFP (Multifunction Peripheral / Product / Printer: digital multifunction device), scanner device). Note that the document management server 10, the electronic contract server 20, the user terminal 30, and the customer 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: an electronic white board with a blackboard function that allows intercommunication), digital signage, HUD (Head Up Display) device, industrial machinery, imaging device, sound collection device, medical equipment, network home appliance, automobile (Connected Car), notebook PC (Personal Computer), mobile phone, smartphone, tablet terminal, game console, PDA (Personal Digital Assistant), digital camera, wearable PC or desktop PC, etc.

[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 FIGS.

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

[0032] Of these, the CPU 501 controls the operation of the entire information processing device. The ROM 502 stores programs used to drive the CPU 501, such as an IPL. The RAM 503 is used as a work area for the CPU 501. The HD 504 stores various data, such as programs. The HDD controller 505 controls the reading and writing of various data from and to the HD 504 under the control of the CPU 501. The display 506 displays various information, such as a cursor, menus, windows, characters, or images. The external device connection I / F 508 is an interface for connecting various external devices. In this case, the external devices are, for example, USB (Universal Serial Bus) memories or 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, a data bus, or the like, for electrically connecting the components, such as the CPU 501, shown in FIG. 2.

[0033] The keyboard 511 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The DVD-RW drive 514 controls reading and writing of various data from a DVD-RW 513, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R, etc. The media I / F 516 controls reading and writing (storing) of data from a recording medium 515, such as a flash memory.

[0034] <Hardware configuration of image forming device> 3 is a diagram showing an example of the hardware configuration when the document management server 10, the electronic contract server 20, the user terminal 30, and the customer terminal 40 are realized by an image forming device. As shown in FIG. 3, the image forming device includes a controller 910, a short-range communication circuit 920, an engine control unit 930, an operation panel 940, and a network I / F 950.

[0035] Of these, the controller 910 has a CPU 901, which is the main part of the computer, a system memory (MEM-P) 902, a north bridge (NB) 903, a south bridge (SB) 904, an ASIC (Application Specific Integrated Circuit) 906, a local memory (MEM-C) 907, which is a storage unit, an HDD controller 908, and an HD 909, which is also a storage unit, and is configured such that the NB 903 and the ASIC 906 are connected by an AGP (Accelerated Graphics Port) bus 921.

[0036] Of these, the CPU 901 is a control unit that performs overall control of the image forming apparatus. The NB 903 is a bridge that connects the CPU 901 with the MEM-P 902, the SB 904, and the AGP bus 921, and includes a memory controller that controls reading and writing to the MEM-P 902, a PCI (Peripheral Component Interconnect) master, and an AGP target.

[0037] The MEM-P 902 comprises a ROM 902a, which is memory for storing programs and data that realize the functions of the controller 910, and a RAM 902b, which is used for expanding the programs and data and as a drawing memory during memory printing. The programs stored in the RAM 902b may be provided by being recorded in an installable or executable file format on a computer-readable recording medium such as a CD-ROM, CD-R, or DVD.

[0038] The SB 904 is a bridge for connecting the NB 903 with PCI devices and peripheral devices. The ASIC 906 is an integrated circuit (IC) for image processing applications that has hardware elements for image processing and serves as a bridge connecting the AGP bus 921, PCI bus 922, HDD 908, and MEM-C 907. The ASIC 906 includes a PCI target and AGP master, an arbiter (ARB) that forms the core of the ASIC 906, a memory controller that controls the MEM-C 907, multiple direct memory access controllers (DMACs) that perform image data rotation using hardware logic, and a PCI unit that transfers data between the scanner unit 931 and printer unit 932 via the PCI bus 922. A USB (Universal Serial Bus) interface or an IEEE 1394 (Institute of Electrical and Electronics Engineers) interface may also be connected to the ASIC 906.

[0039] The MEM-C907 is a local memory used as an image buffer for copying and a code buffer. The HD909 is a storage for storing image data, font data used during printing, and forms. The HD909 controls the reading and writing of data from and to the HD909 under the control of the CPU901. The AGP bus 921 is a bus interface for a graphics accelerator card proposed to speed up graphics processing, and direct high-throughput access to the MEM-P902 enables the graphics accelerator card to operate at high speed.

[0040] Further, the short-distance communication circuit 920 includes a short-distance communication circuit 920a. The short-distance communication circuit 920 is a communication circuit such as NFC or Bluetooth.

[0041] Furthermore, the engine control unit 930 is made up of a scanner unit 931 and a printer unit 932. The operation panel 940 is equipped with a panel display unit 940a, such as a touch panel, that displays current setting values ​​and selection screens and receives inputs from the operator, and an operation panel 940b that includes a numeric keypad that receives setting values ​​for image formation conditions such as density setting conditions and a start key that receives a copy start command. The controller 910 controls the entire image forming apparatus, and controls, for example, drawing, communication, and inputs from the operation panel 940. The scanner unit 931 or the printer unit 932 includes an image processing unit that performs error diffusion, gamma conversion, and the like.

[0042] The image forming apparatus can sequentially switch among the document box function, copy function, printer function, and facsimile function using the application switching key on the operation panel 940. When the document box function is selected, the apparatus enters document box mode, when the copy function is selected, the apparatus enters copy mode, when the printer function is selected, the apparatus enters printer mode, and when the facsimile mode is selected, the apparatus enters facsimile mode.

[0043] The network I / F 950 is an interface for performing data communication using the communication network 100. The short-range communication circuit 920 and the network I / F 950 are electrically connected to the ASIC 906 via a 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 FIGS.

[0045] <Functional configuration of document management server 10> 4 is a block diagram illustrating an example of the functional configuration of the document management server 10 in this embodiment. As shown in FIG. 4, the document management server 10 in this embodiment includes a screen information providing 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 sending 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 providing unit 11, document management unit 12, and workflow control unit 13 provided in the document management server 10 are realized, for example, by processing that is executed by the CPU 501 of a program expanded from HD 504 to RAM 503 shown in Figure 2.

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

[0048] In response to a request from the browser 31 included in the user terminal 30, the screen information providing unit 11 provides the browser 31 with screen information stored in the screen information storage unit 101. 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 processes the documents and metadata in accordance with a workflow executed by the workflow control unit 13.

[0050] The document receiving unit 121 receives a document from the user terminal 30. Furthermore, the document receiving unit 121 stores the document received from the user terminal 30 in the document storage unit .

[0051] The metadata setting unit 122 receives metadata from the user terminal 30. Furthermore, the metadata setting unit 122 stores the metadata received from the user terminal 30 in the metadata storage unit 103 in association with the document stored in the document storage unit 102.

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

[0053] In response to a request from the workflow control unit 13, the document sending unit 123 sends the document related to the contract stored in the document storage unit 102 to the electronic contract server 20. In addition, the document sending unit 123 sends the destination information of the document sent to the electronic contract server 20 to the electronic contract server 20.

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

[0055] The workflow setting unit 131 receives workflow information from the user terminal 30. Furthermore, the workflow setting unit 131 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 a workflow in accordance with 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 the task to a user who should process the task. The workflow execution unit 133 also executes processing on the document in response to a user's operation. The processing on the document includes processing performed in cooperation with an external system.

[0058] The identification information acquisition unit 134 acquires, from the electronic contract server 20, identification information that identifies a document related to a contract stored in the electronic contract server 20. The identification information acquisition unit 134 in this embodiment receives identification information sent by the electronic contract server 20. The identification information acquisition unit 134 updates the metadata stored in the metadata storage unit 103 so that the metadata includes the identification information received from the electronic contract server 20.

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

[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 electronic file bodies that represent the contents of the documents. The documents are stored in the document storage unit 102 in a file format that corresponds 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 a metadata table stored in the metadata storage unit 103.

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

[0063] <Functional configuration of the 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 providing 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 providing unit 21 and the contract management unit 22 provided in the electronic contract server 20 are realized, for example, by processing that is executed by the CPU 501 of a program expanded from the HD 504 shown in Figure 2 onto the RAM 503.

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

[0066] In response to a request from the browser 31 of the user terminal 30 or the browser 41 of the business partner terminal 40, the screen information providing unit 21 provides the screen information stored in the screen information storage unit 201 to the browser 31 or the browser 41. 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 documents relating to the contract received from the document management server 10, and processes the contract in response to a request from the user terminal 30 or the business partner terminal 40.

[0068] The contract receiving unit 221 receives a document related to a contract from the document management server 10. The contract receiving unit 221 also stores the document related to the contract received from the document management server 10 in the contract storage unit 202. The contract receiving unit 221 also 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 relating to the contract stored in the contract storage unit 202. The processing performed by the contract setting unit 222 includes processing for making various settings for the contract.

[0070] The contract sending unit 223 sends the document related to the contract stored in the contract storage unit 202 to the business partner terminal 40.

[0071] The identification information transmitting unit 224 transmits, to the document management server 10, identification information for identifying the document related to the contract stored in the contract storage unit 202.

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

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

[0074] The destination information storage unit 203 stores destination information indicating a destination to which a document related to a contract managed by the contract management unit 22 is to be transmitted. The destination information is stored in a destination information table stored in the destination information storage unit 203.

[0075] The setting information storage unit 204 stores setting information that indicates the content of the setting process executed by the contract setting unit 222. The setting information is stored in a setting information table that the setting information storage unit 204 stores.

[0076] <Functional configuration of user terminal 30> Fig. 6 is a block diagram illustrating the functional configuration of the user terminal 30 in this embodiment. As shown in Fig. 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 included in the user terminal 30 is realized by, for example, processing that is executed by the CPU 501 in response to a program loaded from the HD 504 onto the RAM 503 shown in FIG.

[0078] The browser 31 requests screen information from the screen information providing unit 11 included in 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 providing unit 11. The browser 31 also requests screen information from the screen information providing unit 21 included in 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 providing unit 21.

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

[0080] In addition, the workflow registration unit 311 is not limited to a configuration in which it is realized by the browser 31 executing the screen information received from the screen information providing unit 11, but may also be realized as a dedicated application installed on the user terminal 30.

[0081] The workflow registration unit 311 transmits a workflow information setting request to the document management server 10 in response to a user's operation on the workflow setting screen. The workflow setting screen is a screen for inputting workflow information to be registered in the document management server 10. The workflow setting screen will be described in detail later.

[0082] In response to a user's operation on the document registration screen, the document registration unit 312 transmits a document registration request to the document management server 10. The document registration screen is a screen for inputting a document to be registered in the document management server 10. The document registration screen will be described in detail later.

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

[0084] In response to a user's operation on the task processing screen, the document processing unit 313 transmits a processing request for a task for a document to the document management server 10. The task processing screen is a screen for processing a task for a document. The task processing screen will be described in detail later.

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

[0086] <Functional configuration of the customer terminal 40> 7 is a block diagram illustrating the functional configuration of the customer terminal 40 in this embodiment. As shown in FIG. 7, the customer terminal 40 in this embodiment includes a browser 41. The browser 41 includes a contract conclusion unit 411.

[0087] The browser 41 provided in the customer terminal 40 is realized by, for example, processing that is executed by the CPU 501 of a program loaded from the HD 504 onto the RAM 503 shown in FIG.

[0088] The browser 41 requests screen information from the screen information providing unit 21 provided in 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 providing unit 21.

[0089] The browser 41 executes the screen information received from the screen information providing unit 21, whereby a contract conclusion unit 411 is realized.

[0090] In response to the business partner's user's operation on the contract conclusion screen, the contract conclusion unit 411 transmits an agreement request for the contract conclusion request to the electronic contract server 20. Details of the contract conclusion screen will be described later.

[0091] <Procedure of the prior art> First, an example of the processing procedure of an information processing method executed by an information processing system 1 in the conventional technology will be described with reference to Fig. 8 and Fig. 9. Fig. 8 and Fig. 9 are sequence diagrams showing the processing procedure of an information processing method in the conventional technology, and show that the processing procedure shown in Fig. 9 follows the processing procedure shown in Fig. 8.

[0092] In step S3001, in response to a user operation, the browser 31 included in the user terminal 30 requests a workflow setting screen from the screen information providing unit 11. The screen information providing unit 11 returns screen information representing the workflow setting screen stored in the screen information storage unit 101 to the browser 31. The browser 31 displays the workflow setting screen based on the screen information received from the screen information providing unit 11. This starts up the workflow registration unit 311.

[0093] If workflow registration unit 311 is implemented as a dedicated application installed in user terminal 30, workflow registration unit 311 is started in response to a user operation on user terminal 30 in step S3001.

[0094] Details of the workflow setting screen will now be described with reference to Fig. 10. Fig. 10 is a diagram showing an example of a workflow setting screen 1000.

[0095] As shown in FIG. 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 collaboration input field 1005, and a confirm button 1006.

[0096] The start trigger input field 1001 accepts input of information representing a start trigger that indicates the opportunity to start the workflow. The first reviewer input field 1002 accepts input of information representing the reviewer who will perform the first review in the workflow. The second reviewer input field 1003 accepts input of information representing the reviewer who will perform the second review in the workflow. The approver input field 1004 accepts input of information representing the approver who will approve in the workflow. The external linkage input field 1005 accepts input of information representing the external system if the workflow is linked to an external system.

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

[0098] The user can add, change, or delete any of the input fields provided on the workflow setting screen 1000 according to the content of the workflow to be set. The user can set any number of flows included in the workflow.

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

[0100] Returning to Fig. 8, in step S1101, the screen information providing 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 providing unit 11 transmits a request to save the workflow information to the workflow control unit 13.

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

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

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

[0104] The number is identification information that identifies the workflow information. The start trigger is information that indicates the timing for starting the workflow. The start trigger may be the performance of a specific operation, as in the workflow information numbered 1, or the passage of a predetermined time interval, as in the workflow information numbered 2.

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

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

[0107] In this way, the processing content and assignment destination of each flow may be set simultaneously, as in the workflow information shown in Figure 11, or the assignment destination may be set later for the processing content that has already been set, as in the workflow information shown in Figure 12.

[0108] Figure 13 is a specific example of workflow information for realizing the processing procedures shown in Figures 8 and 9. As shown in Figure 13, workflow information 1041 represents a workflow that starts when "saving a document and setting metadata (including destination)" is executed, and that executes "review processing by the reviewer" and "approval processing by the approver" in order, and then ends by executing "uploading a document to the electronic contract system and setting destination information."

[0109] 8, in step S1302, the workflow acquisition unit 132 included in the workflow control unit 13 acquires the workflow information stored in the workflow information storage unit 104.

[0110] In step S3002, the browser 31 included in the person in charge terminal 30-1 requests a document registration screen from the screen information providing unit 11 in response to an operation by the person in charge. The screen information providing unit 11 returns screen information representing the document registration screen stored in the screen information storage unit 101 to the browser 31. The browser 31 displays the document registration screen based on the screen information received from the screen information providing unit 11. This starts up the document registration unit 312.

[0111] Details of the document registration screen will now be described with reference to Fig. 14. Fig. 14 is a diagram showing an example of the document registration screen 2000.

[0112] 14, a 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 indicating the location of an electronic file corresponding to a document to be registered. The information indicating the location of the electronic file may be an absolute path, a relative path, or information indicating a file on another device written in URI (Uniform Resource Identifier) ​​format.

[0113] A file selection dialog box is launched when the user presses the browse button 2002. The user can input data into the file input field 2001 by selecting a file using the file selection dialog box.

[0114] When the user presses the save button 2003 , the document registration unit 312 transmits a registration request for the document specified by the content entered in the file input field 2001 to the screen information providing unit 11 .

[0115] 8, in step S1102, the screen information providing unit 11 receives a document registration request from the document registration unit 312. Then, the screen information providing unit 11 transmits a document storage request to the document management unit 12 in response to the document registration request.

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

[0117] In step S1202, the document receiving unit 121 transmits a document storage notification notifying that the document storage has been completed to the workflow control unit 13. The document storage 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 an operation by the person in charge, and requests a metadata setting screen for setting metadata for that document from the screen information providing unit 11. The screen information providing 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 providing unit 11.

[0119] Here, details of the metadata setting screen will be described with reference to Fig. 15. Fig. 15 is a diagram showing an example of a metadata setting screen 2100 in the prior art.

[0120] As shown in FIG. 15, the metadata setting screen 2100 includes a document type input field 2101, a destination input field 2102, a contract destination input field 2103, a contract date input field 2104, an expiration date input field 2105, and a confirm button 2106.

[0121] The document type input field 2101 accepts input of attribute information that indicates the document type. The destination input field 2102 accepts input of attribute information that indicates the destination to which the document is to be sent. The contract destination input field 2103 accepts input of attribute information that indicates the contract destination. The contract date input field 2104 accepts input of attribute information that indicates the contract conclusion date. The expiration date input field 2105 accepts input of attribute information that indicates the contract expiration date.

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

[0123] The user can add, change, or delete any of the input fields provided on the metadata setting screen 2100 according to the content of the metadata to be set. Also, input fields corresponding to items not to be set in the metadata may be left blank.

[0124] Returning to Fig. 8, in step S1103, the screen information providing unit 11 receives a metadata setting request from the document registration unit 312. Then, in response to the metadata setting request, the screen information providing unit 11 transmits a metadata saving request to the document management unit 12. The metadata saving request includes a document ID.

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

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

[0127] As shown in FIG. 16, the metadata table 1030 has data items such as a document ID, a document type, a destination, a contracting party, a contracting date, and an expiration date.

[0128] The document ID is identification information that identifies a document in the document management server 10. That is, metadata is associated with a document by the document ID.

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

[0130] The items in the metadata table 1030 can be added or deleted as desired by the user depending on the type of document, etc. Some items may not have a value set depending on the type of document. For example, in the metadata example shown in FIG. 16, the document with the document ID "333" has no 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) 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 17(A), at this time, only the document ID is stored.

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

[0133] Returning to Fig. 8, in step S1204, the metadata setting unit 122 transmits a metadata storage notification notifying that storage of the metadata has been completed to the workflow control unit 13. The metadata storage notification includes a document ID.

[0134] In step S1303, the workflow execution unit 133 included in the workflow control unit 13 transmits an examination task for requesting an examiner to examine the document to the examiner terminal 30-2 in accordance with the workflow information acquired by the workflow acquisition unit 132. The examination task includes a document ID.

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

[0136] Details of the task processing screen will now be described with reference to Fig. 18. Fig. 18 is a diagram showing an example of the task processing screen 3000.

[0137] As shown in FIG. 18, the task processing screen 3000 includes a task list display field 3001 , a document preview field 3002 , a review button 3003 , and a reject button 3004 .

[0138] A list of tasks assigned to reviewers is displayed in the task list display field 3001. The task list displays, for example, the task name and the date the task was received. A document preview field 3002 displays a preview of the contents of the document to be processed by the task selected in the task list display field 3001.

[0139] The reviewer reviews the contents of the document on the task processing screen 3000. When the reviewer has completed the review, the reviewer presses the review button 3003. If the reviewer cannot complete the review, for example, if a defect is found, the reviewer presses the reject button 3004.

[0140] The buttons on the task processing screen 3000 vary depending on the content of the workflow and the type of task. The task processing screen 3000 shown in Fig. 18 is an example of a task processing screen when an examination task is selected. For example, when an approval task is selected, an approval button is displayed instead of the examination button.

[0141] When the examiner presses the Examination button 3003, the document processing unit 313 sends an examination completion request for the document to the screen information providing unit 11. When the examiner presses the Reject button, the examination task is rejected and the document is returned to the person in charge. In the following explanation, it is assumed that the examiner presses the Examination button 3003.

[0142] Returning to Fig. 8, in step S1104, the screen information providing unit 11 receives a document examination completion request from the examiner terminal 30-2. Then, in response to the document examination completion request, the screen information providing unit 11 transmits an examination completion notification to the workflow control unit 13. The examination completion notification includes a document ID.

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

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

[0145] When the approver presses the approval button, the document processing unit 313 transmits an approval request for the document to the screen information providing unit 11.

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

[0147] In step S1305, the workflow execution unit 133 included in the workflow control unit 13 receives the approval completion notification from the screen information providing unit 11. Then, the workflow execution unit 133 transmits a request to transmit the document identified by the document ID included in the approval completion notification to the document management unit 12. The document transmission request includes the document ID.

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

[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 included in the electronic contract server 20 receives a document related to the contract from the document sending unit 123. Then, the contract receiving unit 221 stores the document related to the contract in the contract storage unit 202.

[0151] In step S1306, the workflow execution unit 133 included in the workflow control unit 13 acquires metadata associated with the document identified by the document ID from the metadata storage unit 103, in accordance with the workflow information acquired by the workflow acquisition unit 132. Then, the workflow execution unit 133 transmits 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 included in the electronic contract server 20 determines the destination included in the destination setting request received from the workflow execution unit 133 as the destination of the document related to the contract stored in the contract storage unit 202. Then, the contract receiving unit 221 stores destination information indicating the destination of the document related to the contract 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, the destination may be a telephone number, a fax number, or an account on various social networking systems (SNS) or other communication means that can be used for electronic transmission.

[0154] 9 will be explained. In step S3006, the browser 31 provided on the person in charge terminal 30-1 requests authentication from the electronic contract server 20. The authentication request includes authentication information related to the person in charge. An example of the authentication information is a user ID that identifies the user and a password entered by the user.

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

[0156] In step S2102, the screen information providing unit 21 returns screen information representing a screen to be displayed after authentication to the browser 31 based on the authentication result of the person in charge. If the authentication is successful, the screen to be displayed after authentication is a contract selection screen. If the authentication is unsuccessful, the screen to be displayed after authentication is an error display screen. In the following explanation, it is assumed that the screen information providing unit 21 has successfully authenticated the person in charge.

[0157] In step S3007, the browser 31 included in the person in charge terminal 30-1 displays the contract selection screen based on the screen information received from the screen information providing unit 21. This starts up the contract processing unit 314.

[0158] Details of the contract selection screen will now be described with reference to Fig. 19. Fig. 19 is a diagram showing an example of the contract selection screen 4000 in this embodiment.

[0159] 19, the contract selection screen 4000 includes a contract list display field 4010 and a status selection field 4020. The contract list display field 4010 includes contract display fields 4011-1 to 4011-6 that display information about each contract. The status selection field 4020 includes status selection buttons 4021-1 to 4021-6 that correspond to each preset status.

[0160] When the person in charge presses one of the status selection buttons 4021 in the status selection field 4020, 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 of Fig. 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 in a state where the state selection button 4021-4 corresponding to the "concluded" state is pressed. That is, a list of contracts for which the conclusion of the contract has been completed is displayed in the contract list display field 4010. However, the state to be initially displayed may be determined arbitrarily.

[0162] When the person in charge selects one of the contract display fields 4011 in the contract list display field 4010, the contract processing unit 314 sends a request to acquire a document related to the contract corresponding to the selected contract display field 4011 to the screen information providing unit 21. The document acquisition request includes a document ID.

[0163] 9. In step S2103, upon receiving the document acquisition request from the contract processing unit 314, the screen information providing unit 21 transfers the document acquisition request to the contract management unit 22.

[0164] In step S2203, the contract transmission unit 223 included in the contract management unit 22 receives a document acquisition request from the screen information providing 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 person in charge terminal 30-1.

[0165] In step S3008, the contract processing unit 314 included in the person in charge terminal 30-1 receives the document from the contract transmission unit 223. The browser 31 included in the person in charge terminal 30-1 requests a contract setting screen from the screen information providing unit 21. The screen information providing unit 21 returns screen information representing the contract setting screen stored in the screen information storage unit 201 to the browser 31. The browser 31 displays the contract setting screen based on the screen information received from the screen information providing unit 21.

[0166] Details of the contract setting screen will now be described with reference to Fig. 20. Fig. 20 is a diagram showing an example of the contract setting screen 4100 in this embodiment.

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

[0168] The destination display field 4101 displays the sender and destination of the document related to the contract being set. The sender is information that has been set in advance. The destination is destination information that has been set in the contract. The input item selection field 4102 displays 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 set.

[0169] After the user selects the input item they want to set from the input item selection field 4102, they press the position in the file preview field 4103 where they want to add it, and the contents of the document related to the contract with the input item set at that position are displayed 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 indicating the type and position of each input item set in the file preview field 4103 to the screen information providing unit 21. The contract setting request includes the document ID and setting information indicating the type and position of each input item.

[0171] 9. In step S2104, when the screen information providing unit 21 receives the contract setting request from the contract processing unit 314, the screen information providing unit 21 transfers the setting request to the contract management unit 22.

[0172] In step S2204, the contract setting unit 222 included in the contract management unit 22 receives the contract setting request from the screen information providing 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, in response to an operation by the person in charge, the browser 31 provided on the person in charge terminal 30-1 transmits a request to send a request for signing a contract to the screen information providing unit 21. The request to send a request for signing a contract includes a document ID that identifies a document related to the contract.

[0174] In step S2105, when the screen information providing unit 21 receives a transmission request for requesting conclusion of a contract from the browser 31, the screen information providing unit 21 transfers the transmission request to the contract management unit 22.

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

[0176] The request for signing the contract is sent by a communication means corresponding to the destination information set in the document related to the contract to be sent. In this embodiment, the request for signing the contract is sent by email containing the connection destination identifier of the document. However, the communication means is not limited to email, and various communication means capable of electronic transmission, such as various SNSs, 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. In response to an operation by the trading partner user, the browser 41 provided in the trading partner terminal 40 requests a contract conclusion screen from the screen information providing unit 21 using the connection destination identifier included in the contract conclusion request. The screen information providing unit 21 generates screen information representing the contract conclusion screen using the connection destination identifier and returns it to the browser 41. The browser 41 displays the contract conclusion screen based on the screen information received from the screen information providing unit 21. This starts the contract conclusion unit 411.

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

[0179] As shown in FIG. 21, the contract conclusion screen 4200 includes a destination display field 4201, an item input field 4202, a file preview field 4203, and an Agree button 4204.

[0180] The destination display field 4201 displays the sender and destination of the document related to the contract that is the subject of the conclusion request. The item input field 4202 accepts input contents for input items 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 for which the input contents in the item input field 4202 have been set.

[0181] When the user presses the Agree button 4204 after entering content in the item input field 4202, the contract conclusion unit 411 transmits a contract conclusion request representing the input content in the item input field 4202 to the screen information providing unit 21. The contract conclusion request includes the document ID and agreement information representing the input content for each input field.

[0182] 9. In step S2106, when the screen information providing unit 21 receives a request for signing a contract from the contract signing unit 411, the screen information providing unit 21 transfers the request for signing to the contract management unit 22.

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

[0184] In step S2207, the contract setting unit 222 sends a contract conclusion notification to the person in charge terminal 30-1, including the connection destination identifier of the document specified by the document ID included in the contract conclusion request. In this embodiment, the contract conclusion notification is sent by email containing the connection destination identifier of the document. However, the communication method is not limited to email, and various communication methods capable of electronic transmission can be used.

[0185] In step S3010, the person in charge terminal 30-1 receives a contract conclusion notification from the electronic contract server 20. In response to an operation by the person in charge, the browser 31 provided on the person in charge terminal 30-1 requests a contract confirmation screen from the screen information providing unit 21 using the connection destination identifier included in the contract conclusion notification. The screen information providing unit 21 generates screen information representing the contract confirmation screen using the connection destination identifier and returns it to the browser 31. The browser 31 displays the contract confirmation screen based on the screen information received from the screen information providing unit 21.

[0186] Details of the contract confirmation screen will now be described with reference to Fig. 22. Fig. 22 is a diagram showing an example of the contract confirmation screen 4300 in this embodiment.

[0187] 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 destination display field 4313, and a contract preview field 4314.

[0188] The status display field 4311 displays the status of the contract to be confirmed. The contract name display field 4312 displays the name of the contract to be confirmed. The destination display field 4313 displays the destination of the contract to be confirmed and the status of each destination. The contract preview field 4314 displays the contents of the document related to the contract after the contract is concluded.

[0189] The status selection field 4320 is the same as the status selection field 4020 provided on the contract selection screen 4000 shown in Fig. 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 contracts in the status corresponding to that status selection button 4321 is displayed. Then, when the person in charge selects one of the contracts, information about the selected contract is displayed in the contract details display field 4310.

[0190] <Processing Procedure of Information Processing Method in 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 Fig. 23. Fig. 23 is a sequence diagram showing the processing procedure of the information processing method in this embodiment.

[0191] Fig. 24 is a specific example of workflow information for realizing the processing procedure shown in Fig. 23. As shown in Fig. 24, workflow information 1042 in this embodiment represents a workflow that starts when "saving a document and setting metadata (including destination)" is executed, and that executes "reviewer's review process," "approval process by approver," "uploading a document to the electronic contract system and setting destination information," and "obtaining processing results from the electronic contract system" in that order, and then executes "document processing by person in charge" and ends.

[0192] Returning to Fig. 23, the processing 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 Fig. 8.

[0193] In step S2211, the identification information transmission unit 224 included in 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. Then, the identification information transmission unit 224 transmits the connection destination identifier for the document related to the contract to the document management server 10.

[0194] At the time of step S2211, a request for signing a contract has not been sent to the business partner. Therefore, the connection destination identifier generated by the identification information sending unit 224 identifies a document related to a contract before the contract is signed. Hereinafter, the connection destination identifier generated in step S2211 is also referred to as a "pre-contract connection destination identifier."

[0195] In step S1311, the identification information acquisition unit 134 included in the document management server 10 receives the pre-contract connection destination identifier from the electronic contract server 20. Then, the workflow execution unit 133 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 included in the document management unit 12 receives a request to save the identification information from the workflow execution unit 133. Then, the metadata setting unit 122 updates the metadata stored in the metadata storage unit 103 so that the pre-contract connection destination identifier is included in the metadata associated with the document ID included in the request to save the identification information.

[0197] Here, details of the metadata table in this embodiment will be described with reference to Fig. 25. Fig. 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, as data items, document ID, document type, destination, contract partner, contract date, expiration date, etc., similar to the metadata table 1030 shown in Figure 16, and further has the URL of the pre-contract document.

[0199] The URL of the pre-contract document is the pre-contract connection destination identifier included in the request to save the identification information. That is, the metadata table 1031 in this embodiment differs from the metadata table 1030 shown in Fig. 16 in that a pre-contract connection destination identifier is added.

[0200] Fig. 25(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 Fig. 25(A), at this time, only the document ID is stored.

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

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

[0203] Returning to Fig. 23, in step S1212, the metadata setting unit 122 transmits a metadata storage notification notifying that storage of the metadata has been completed to the workflow control unit 13. The metadata storage notification includes a document ID.

[0204] In step S1312, the workflow execution unit 133 included in the workflow control unit 13 transmits a setting task to the person in charge terminal 30-1 to request the person in charge to set up the contract, in accordance with the workflow information acquired by the workflow acquisition unit 132. The setting task includes a document ID.

[0205] In step S3011, the contract processing unit 314 included in the person in charge terminal 30-1 receives the setting task from the workflow execution unit 133. In response to an operation by the person in charge, the browser 31 included in the person in charge terminal 30-1 requests the screen information providing unit 11 to provide a metadata setting screen related to the document identified by the document ID included in the setting task. The screen information providing 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 providing unit 11.

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

[0207] As shown in Figure 26, the metadata setting screen 2110 in this embodiment, like the metadata setting screen 2100 shown in Figure 15, has a document type input field 2101, a destination input field 2102, a contract destination input field 2103, a contract date input field 2104, an expiration date input field 2105, and a confirm button 2106, and further has a pre-contract document display field 2111.

[0208] The pre-contract document display field 2111 displays the pre-contract connection destination identifier set in the URL of the pre-contract document stored in the metadata table 1031. That is, the metadata setting screen 2110 in this embodiment differs from the metadata setting screen 2100 shown in Fig. 15 in that a pre-contract connection destination identifier is added.

[0209] The browser 31 provided in the person in charge terminal 30-1 requests a contract setting screen from the screen information providing unit 21 using the pre-contract connection destination identifier in response to an operation by the person in charge on the metadata setting screen 2110. The screen information providing unit 21 generates screen information representing the contract setting screen using the pre-contract connection destination identifier and returns the screen information to the browser 31. The browser 31 displays the contract setting screen based on the screen information received from the screen information providing unit 21.

[0210] The operation of displaying the contract setting screen from the metadata setting screen 2110 is, for example, an operation of clicking the URL of the pre-contract document on the metadata setting screen 2110.

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

[0212] Thereafter, the processes from step S2104 to step S3010 are carried out in the same manner as the process procedure of the information processing system 1 in the conventional technology shown in FIG.

[0213] <Effects of the first embodiment> The information processing system 1 in this embodiment stores documents managed by the document management server 10 in association with a connection destination identifier that identifies the document in the electronic contract server 20, and outputs screen information to the user terminal 30 that displays the connection destination identifier in association with information related to the document.

[0214] This allows the user to directly display the documents stored in the electronic contract server 20 based on the connection destination identifier displayed on the screen output by the document management server 10. This eliminates the need for the user to log in to the electronic contract server 20 each time and find the desired document from among many documents in order to check the contents of the documents stored in the electronic contract server 20.

[0215] [Second embodiment] In the first embodiment, when the electronic contract server 20 receives a document from the document management server 10, it transmits a connection destination identifier that identifies the document related to the contract before the contract is concluded to the document management server 10. The document management server 10 stores the connection destination 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 acquires, at predetermined time intervals, a connection identifier that identifies a document related to a contract from the electronic contract server 20. The document management server 10 stores the connection identifier corresponding to each state of the contract (for example, before and after the contract is concluded) in metadata associated with the document.

[0217] <Processing Procedure of Information Processing Method in 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 Fig. 27 and Fig. 28. Fig. 27 and Fig. 28 are sequence diagrams showing the processing procedure of the information processing method in this embodiment, and indicate that the processing procedure shown in Fig. 28 follows the processing procedure shown in Fig. 27.

[0218] Fig. 29 is a specific example of workflow information for realizing the processing procedures shown in Fig. 27 and Fig. 28. As shown in Fig. 29, workflow information 1043 in this embodiment represents a workflow that starts when "saving a document and setting metadata (including destination)" is executed, and that executes "examination processing by reviewer," "approval processing by approver," "uploading a document to the electronic contract system and setting destination information," "obtaining processing results from the electronic contract system," "document processing by person in charge," "obtaining document information from the electronic contract system (periodic execution)," and "notifying the approver that contract conclusion has been completed," in that order, and then ends by executing "approver confirms document after contract conclusion."

[0219] Returning to Fig. 27, the processing 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 Fig. 23 .

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

[0221] In step S1322, the identification information acquisition unit 134 included in 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 sending unit 224 included in the contract management unit 22 receives a request to acquire a connection destination identifier from the identification information acquisition unit 134. The identification information sending unit 224 generates a connection destination identifier for a document related to a pre-contract contract for which a connection destination identifier has not been transmitted, and returns the generated identifier to the identification information sending unit 224.

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

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

[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 FIG.

[0226] The description will proceed to Fig. 28. The processing 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 Fig. 9.

[0227] In step S1323, the identification information acquisition unit 134 included in 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 sending unit 224 included in the contract management unit 22 receives a request to acquire a connection destination identifier from the identification information acquisition unit 134. The identification information sending unit 224 generates a connection destination identifier for a document related to a contract after the contract is concluded for which a connection destination identifier has not been transmitted, and returns the generated identifier to the identification information sending 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 a document related to the contract after the contract is concluded. Hereinafter, the connection destination identifier generated in step S2222 will also be referred to as a "post-contract conclusion connection destination identifier."

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

[0231] In step S1323, the identification information acquisition unit 134 included in the document management server 10 receives the post-contract connection destination identifier from the electronic contract server 20. Then, the workflow execution unit 133 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 included in the document management unit 12 receives a request to save the identification information from the workflow execution unit 133. Then, the metadata setting unit 122 updates the metadata stored in the metadata storage unit 103 so that the post-contract connection destination identifier is included in the metadata associated with the document ID included in the request to save the identification information.

[0233] Here, details of the metadata table in this embodiment will be described with reference to Fig. 30. Fig. 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, as data items, the document ID, document type, destination, contract partner, contract date, expiration date, and URL of the pre-contract document, similar to the metadata table 1031 shown in Figure 25, and further has 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. That is, the metadata table 1032 in this embodiment differs from the metadata table 1031 shown in Fig. 25 in that a post-contract connection destination identifier is added.

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

[0237] Fig. 30(B) is an example of metadata after the metadata setting unit 122 updates the metadata to include the post-contract connection destination identifier. As shown in Fig. 30(B), at this timing, the post-contract connection destination identifier received from the identification information sending unit 224 is stored in association with the document ID.

[0238] 28. In step S1324, the workflow execution unit 133 included in the workflow control unit 13 transmits a confirmation task to the approver terminal 30-3, requesting the approver to confirm the contract after the contract is concluded, 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 included in the approver terminal 30-3 receives the confirmation task from the workflow execution unit 133. In response to the operation of the approver, the browser 31 included in the approver terminal 30-3 requests the screen information providing unit 11 to provide a metadata setting screen related to the document identified by the document ID included in the confirmation task. The screen information providing 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 providing unit 11.

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

[0241] As shown in Figure 31, the metadata setting screen 2120 in this embodiment, like the metadata setting screen 2110 shown in Figure 26, has a document type input field 2101, a destination input field 2102, a contract destination input field 2103, a contract date input field 2104, an expiration date input field 2105, a confirm button 2106, and a pre-contract document display field 2111, and further has a post-contract document display field 2121.

[0242] The post-contract document display field 2121 displays the post-contract connection destination identifier set in the URL of the post-contract document stored in the metadata table 1032. That is, the metadata setting screen 2120 in this embodiment differs from the metadata setting screen 2110 shown in Fig. 26 in that a post-contract connection destination identifier is added.

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

[0244] The operation of displaying the contract confirmation screen from the metadata setting screen 2120 is, for example, an operation of clicking the URL of the pre-contract document or the URL of the post-contract document on the metadata setting screen 2120.

[0245] The metadata setting screen in this embodiment simultaneously displays the pre-contract connection destination identifier and the post-contract connection destination identifier. This allows the contents of the document related to the pre-contract contract and the document related to the post-contract contract to be directly displayed on the same screen. For example, if a user wants to compare and confirm the document related to the pre-contract contract and the document related to the post-contract contract, the operation effort is significantly reduced compared to conventional methods, making it highly convenient.

[0246] <Effects of the second embodiment> The information processing system 1 in this embodiment acquires, at predetermined time intervals, connection destination identifiers that identify documents related to contracts from the electronic contract server 20. This enables the document management server 10 to associate and store connection destination identifiers related to contracts before and after the contract is concluded.

[0247] Because the electronic contract server 20 sends a notification that the contract has been concluded only to the person in charge's terminal 30-1, it was previously difficult for anyone other than the person in charge to recognize that the contract had been concluded. According to the information processing system 1 of this embodiment, a document in which a connection destination identifier is set after the contract has been concluded indicates that the contract has been concluded, so even anyone other than the person in charge can recognize that the contract has been concluded.

[0248] In addition, since the connection identifier before the contract is concluded and the connection identifier after the contract is concluded are associated, even if the user wants to compare documents related to the contract before the contract is concluded and documents related to the contract after the contract is concluded, they can smoothly check both documents.

[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 sending unit 123 is an example of a sending unit. The identification information sending unit 224 is an example of a generating unit. The browser 31 is an example of a screen display unit. Step S1206 executed by the document sending unit 123 is an example of a sending procedure. Step S1311 executed by the identification information acquisition unit 134 is an example of an acquisition procedure. Step S3011 executed by the screen information providing unit 11 is an example of a providing procedure.

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

[0251] The devices described in the example are merely illustrative of one of several computing environments for implementing 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, configured to communicate with each other via any type of communication link, including a network, shared memory, etc., and to perform the processes disclosed herein.

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

[0253] 1. Information Processing Systems 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 Department 122 Metadata setting section 123 Document Transmission Department 13 Workflow control section 131 Workflow Settings 132 Workflow Acquisition Unit 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 Setting information storage unit 221 Contract Receiving Department 222 Contract Setting Section 223 Contract Transmission Department 224 Identification information transmission unit 30 User terminals 31 Browsers 311 Workflow Registration Department 312 Document Registration Department 313 Document Processing Unit 314 Contract Processing Department 40 Customer terminal 41 Browser 411 Contracting Department [Prior art documents] [Patent documents]

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

Claims

1. An information processing device capable of communicating with a second information processing device via a network, a storage unit that stores first electronic data transmitted from a user terminal, the storage unit generating an ID that identifies the first electronic data, and storing the generated ID and the first electronic data in association with each other; a screen information providing unit that provides a first screen that displays a preview of the content of the first electronic data stored in the storage unit to the user terminal; a transmitting unit that transmits the first electronic data stored in the storage unit to the second information processing device; an identification information acquisition unit that acquires, from the second information processing device, identification information that identifies second electronic data obtained after the first electronic data is processed in the second information processing device; Equipped with the storage unit further stores the identification information for identifying the second electronic data acquired by the identification information acquisition unit from the second information processing device in association with the ID stored before transmitting the first electronic data to the second information processing device; the screen information providing unit provides the user terminal with a second screen requesting the second electronic data from the second information processing device. Information processing device.

2. 2. The information processing device according to claim 1, the identification information is a URL, the screen information providing unit provides the second screen including the URL to the user terminal. Information processing device.

3. 2. The information processing device according to claim 1, the second information processing device is an electronic contract system used to electronically conclude a contract, Information processing device.

4. 4. The information processing device according to claim 3, a workflow execution unit that transmits an examination task requesting examination of the first electronic data to the user terminal; The first screen is a task processing screen for processing the examination task. Information processing device.

5. 5. The information processing device according to claim 1, the screen information providing unit provides the user terminal with a third screen for inputting metadata to be associated with the first electronic data; the identification information acquisition unit includes the identification information in the metadata received from the user terminal; Information processing device.

6. 6. The information processing device according to claim 5, the identification information acquisition unit receives the identification information generated by the second information processing device; Information processing device.

7. 6. The information processing device according to claim 5, the identification information acquisition unit acquires the identification information from the second information processing device at predetermined time intervals; Information processing device.

8. An information processing system in which a second information processing device and a first information processing device can communicate with each other via a network, The first information processing device a storage unit that stores first electronic data transmitted from a user terminal, the storage unit generating an ID that identifies the first electronic data, and storing the generated ID and the first electronic data in association with each other; a screen information providing unit that provides a first screen that displays a preview of the content of the first electronic data stored in the storage unit to the user terminal; a transmitting unit that transmits the first electronic data stored in the storage unit to the second information processing device; an identification information acquisition unit that acquires, from the second information processing device, identification information that identifies second electronic data obtained after the first electronic data is processed in the second information processing device; Equipped with the storage unit further stores the identification information for identifying the second electronic data acquired by the identification information acquisition unit from the second information processing device in association with the ID stored before transmitting the first electronic data to the second information processing device; the screen information providing unit provides the user terminal with a second screen requesting the second electronic data from the second information processing device; The second information processing device a receiving unit that receives the first electronic data from the first information processing device; a generation unit that generates the identification information; Equipped with The user terminal a screen display unit that displays the first screen and the second screen received from the first information processing device, Information processing system.

9. a computer capable of communicating with the second information processing device via a network, a storage procedure for storing first electronic data transmitted from a user terminal in a storage unit, the storage procedure including generating an ID for identifying the first electronic data, and storing the generated ID and the first electronic data in association with each other; a provision step of providing a first screen that displays a preview of the content of the first electronic data stored in the storage unit to the user terminal; a transmission step of transmitting the first electronic data stored in the storage unit to the second information processing device; an identification information acquisition step of acquiring, from the second information processing device, identification information for identifying second electronic data obtained after the first electronic data has been processed in the second information processing device; Run the storing step further includes storing the identification information for identifying the second electronic data acquired from the second information processing device in the identification information acquiring step in association with the ID stored before transmitting the first electronic data to the second information processing device; the providing step provides the user terminal with a second screen requesting the second electronic data from the second information processing device. Information processing methods.

10. a computer that can communicate with the second information processing device via a network; a storage procedure for storing first electronic data transmitted from a user terminal in a storage unit, the storage procedure including generating an ID for identifying the first electronic data, and storing the generated ID and the first electronic data in association with each other; a provision step of providing a first screen that displays a preview of the content of the first electronic data stored in the storage unit to the user terminal; a transmission step of transmitting the first electronic data stored in the storage unit to the second information processing device; an identification information acquisition step of acquiring, from the second information processing device, identification information for identifying second electronic data obtained after the first electronic data has been processed in the second information processing device; Execute the storing step further includes storing the identification information for identifying the second electronic data acquired from the second information processing device in the identification information acquiring step in association with the ID stored before transmitting the first electronic data to the second information processing device; the providing step provides the user terminal with a second screen requesting the second electronic data from the second information processing device. program.

Images