Information processing system, service providing system, information processing method, and program

Abstract

To provide an information processing system, etc. capable of cooperating a first application provided by the information processing system with a second application provided by an external service system.SOLUTION: A service provision system 100 used for transmitting data regarding a first application requested to be executed from a device to an external service system, includes: a setting reception unit 12 which receives a setting regarding a correspondence between the first application and a second application provided by the external service system from a terminal device; and an external service processing unit 2 which transmits identification information of the second application and the data to the external service system when the first application is requested to be executed from the device.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] There is a known technology called Web applications, which allows a terminal device to use services provided on a network with a Web browser, etc., but it is also possible to use such services from devices such as image forming devices. For example, there is an information processing system that scans an original with an image forming device, generates image data, and stores the image data in an external storage service or prints it.

[0003] In an information processing system, in order to reduce the burden on a user when using a service from a device, the user can set the use of the device in advance (for example, see Patent Document 1). Patent Document 1 describes a technology in which the information processing system accepts default values ​​of print settings, etc., set by the user on an application setting screen. Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the past, there was a problem that a first application provided by an information processing system and a second application provided by an external service system could not be linked together. That is, in the past information processing system, even if a user could set in advance to save image data or the like in an external storage service, the user could not set which second application provided by the external service system the first application provided by the information processing system should link with.

[0005] In view of the above-mentioned problems, the present invention aims to provide an information processing system etc. capable of linking a first application provided by the information processing system with a second application provided by an external service system. [Means for solving the problem]

[0006] In view of the above problem, the present invention provides an information processing system that transmits data related to a first application requested for execution from a device to an external service system, the information processing system including: a setting receiving unit that receives settings related to a correspondence between the first application and a second application provided by the external service system; and an external service processing unit that transmits identification information and the data of the second application to the external service system when execution of the first application is requested from the device. The external service processing unit designates authentication information of a logged-in user and identification information of the second application received from a terminal device, and acquires from the external service system whether or not the user is authorized to use the second application, and transmits to the terminal device whether or not the user is authorized to use the second application. The present invention is characterized by the above. Effect of the Invention

[0007] It is possible to provide an information processing system etc. that can link a first application provided by the information processing system with a second application provided by an external service system. [Brief description of the drawings]

[0008] [Figure 1] FIG. 2 is a diagram illustrating the overall operation of the service providing system. [Diagram 2] FIG. 1 illustrates a system configuration of an example of a service providing system. [Diagram 3] FIG. 2 is a diagram illustrating an example of a hardware configuration of an information processing system and a terminal device. [Figure 4] FIG. 2 is a diagram illustrating a hardware configuration of an example of an image forming apparatus, which is an example of a device. [Diagram 5] FIG. 2 is a diagram illustrating a functional configuration of an example of a service providing system. [Figure 6] FIG. 2 is a diagram illustrating a functional configuration of an example of an external service system. [Figure 7] FIG. 4 is a diagram illustrating an example of application processing information stored in an application processing information storage unit. [Figure 8] FIG. 11 is a diagram illustrating another example of application processing information. [Figure 9] FIG. 11 is a sequence diagram illustrating an example of a registration process of application processing information. [Figure 10] FIG. 13 illustrates an example of an application processing information creation screen. [Figure 11] FIG. 13 is a diagram showing an example of a linkage target application registration screen (part 1) displayed on the terminal device. [Figure 12] FIG. 13 is a diagram showing an example of a linked application registration screen (part 2) displayed on the terminal device. [Figure 13] FIG. 13 is a diagram showing an example of a linkage target application registration screen (part 3) displayed on the terminal device. [Figure 14] FIG. 13 is a diagram showing an example of a details pop-up screen in which details of a form called an attachment are set. [Figure 15] FIG. 13 is a diagram showing an example of a linked application registration screen (part 4) on which work items are displayed. [Figure 16] FIG. 13 is a diagram showing an example of a details pop-up screen in which details of a form called a numerical value field are set. [Figure 17] FIG. 13 is a diagram illustrating an example of a linked application list screen displayed on the terminal device. [Figure 18] 11 is an example of a sequence diagram illustrating a procedure in which an administrator registers an application in an external service system. [Figure 19] FIG. 13 is a diagram showing an example of an initial screen displayed by the terminal device. [Figure 20] FIG. 13 is a diagram showing an example of a My Page screen (part 1) displayed on the terminal device. [Figure 21] FIG. 13 is a diagram showing an example of a My Page screen (part 2) displayed on the terminal device. [Figure 22] FIG. 13 is a diagram illustrating an example of an authentication information setting pop-up screen displayed by the terminal device. [Diagram 23]FIG. 13 is a diagram showing an example of a My Page screen (part 3) displayed on the terminal device when the information processing system can log in to the external service system. [Figure 24] 11 is an example of a sequence diagram illustrating a procedure in which an administrator registers authentication information in an information processing system. [Diagram 25] FIG. 13 is a diagram showing an example of an initial screen displayed by the terminal device. [Figure 26] FIG. 13 is a diagram illustrating an example of a service selection screen displayed on the terminal device. [Figure 27] FIG. 11 is a diagram illustrating an example of a cooperation source application selection screen displayed on the terminal device. [Figure 28] FIG. 13 is a diagram showing an example of a coordination source application setting screen (part 1) displayed on the terminal device when a coordination source application "Register new record" is selected. [Figure 29] FIG. 13 is a diagram showing an example of a coordination source application setting screen (part 2) displayed on the terminal device. [Diagram 30] FIG. 13 is a diagram showing an example of a coordination source application setting screen (part 3) displayed on the terminal device. [Diagram 31] FIG. 13 is a diagram showing an example of a coordination source application setting screen (part 4) displayed on the terminal device. [Diagram 32] 11 is an example of a sequence diagram illustrating a procedure in which an administrator sets collaboration information and the like in an information processing system. [Diagram 33] FIG. 13 is a diagram illustrating an example of a coordination source application setting screen having a record setting field. [Diagram 34] FIG. 13 is a diagram illustrating an example of a cooperation source application list screen displayed on the device. [Diagram 35] FIG. 13 is a diagram showing an example of a “new record registration” setting screen displayed by the device. [Diagram 36] 11 is an example of a sequence diagram illustrating a procedure in which a user operates a device, the device displays a coordination source application list screen, and executes a coordination source application selected by the user. [Figure 37] FIG. 13 illustrates an example of a record list displayed by the device. [Figure 38]11 is a sequence diagram illustrating an example of a terminal device displaying a name of a linked application of an external service system. [Figure 39] 11 is an example of a sequence diagram in which a terminal device displays whether a user has the authority to use a linked application. [Diagram 40] 13 is a sequence diagram illustrating an example of a process in which the terminal device displays a field code based on a linked application ID. [Diagram 41] 13 is a diagram showing an example of a list of field codes displayed on a coordination source application setting screen. FIG. [Diagram 42] 11 is a sequence diagram illustrating an example of a procedure in which an administrator searches for a linked application in an external service system. [Diagram 43] 11 is an example of a sequence diagram illustrating a procedure in which a user operates a device, the device displays a coordination source application list screen, and executes a coordination source application selected by the user. [Diagram 44] 13 is a diagram showing an example of a cooperation source application setting screen of a cooperation source application of “FAX reception registration” displayed on the terminal device. FIG. [Diagram 45] 13 is a diagram illustrating an example of a coordination source application setting screen of a coordination source application for “email reception registration” displayed on the terminal device. FIG. [Figure 46] 11 is a sequence diagram showing an example of a procedure in which a device receives a facsimile and registers image data and data other than image data in a field of an external service system. [Figure 47] FIG. 13 is a diagram illustrating an example of a coordination source application setting screen displayed on the terminal device. [Figure 48] 11 is a diagram showing a schematic diagram of application processing information for registering image data and the like only from a specific FAX number in an external service system. FIG. [Figure 49] 11 is a sequence diagram showing an example of a procedure in which a device receives a facsimile and registers image data and data other than image data in a field of an external service system based on a whitelist. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A service providing system and an information processing method executed by the service providing system will be described in detail below with reference to the drawings as an example of an embodiment of the present invention.

[0010] <Outline of operation> First, an overview of the processing performed by the service providing system 100 will be described with reference to Fig. 1. Fig. 1 is a diagram for explaining the overall operation of the service providing system 100. Fig. 1(a) shows the operation in a preparation stage in which an administrator or the like sets up a link source application (an example of a first application, hereinafter referred to as a link source app) and a link destination application (an example of a second application, hereinafter referred to as a link destination app) for using the service providing system 100, and Fig. 1(b) shows the operation in an execution stage in which a user executes the link source app and the link source app cooperates with the link destination app.

[0011] In the following, the term "user" refers to a general user, and the term "administrator" refers to a tenant administrator. A tenant is a company, organization, etc. that has entered into a contract to receive a service from a service provider (an information processing system in this embodiment). As an example, a user belongs to a tenant, but the user may subscribe to the service individually. When subscribing to a service individually, the user himself / herself inputs settings that associate the coordination source app with the coordination destination app from the coordination source app setting screen.

[0012] Some of the processes performed by the administrator may be performed by a person in charge of a vendor or dealer who promotes subscription to the services provided by the service providing system 100 to tenants or sells applications provided by the service providing system 100. In addition, there may be cases where the processes performed by the administrator can be performed by a user.

[0013] (1) The administrator causes the terminal device 30 to communicate with the external service system 40, and displays a linkage destination application registration screen provided by the external service system 40. The external service system 40 provides a service that is used in the form of a Web application (hereinafter, referred to as a Web application). Although the overall content of the functions provided by this service is fixed, the administrator can customize the service to use it as a desired linkage destination application. In other words, a part (or the entirety) of the functions of the service becomes the linkage destination application.

[0014] (2) The administrator registers a linked application suitable for the tenant's business by combining forms (functions modularized) prepared by the external service system 40. When the administrator combines the forms and performs necessary settings, the terminal device 30 registers the linked application in the external service system 40.

[0015] (3) The external service system 40 assigns a destination link application ID for identifying the destination link application to the destination link application, and transmits the destination link application ID to the terminal device 30. The terminal device 30 displays the destination link application ID, so that the administrator can grasp the destination link application ID. Note that in an embodiment described later, the administrator can cause the terminal device 30 to display the destination link application ID via the information processing system 10.

[0016] (4) Next, the administrator operates the terminal device 30 to communicate with the information processing system 10, and the terminal device 30 displays a link source application setting screen provided by the information processing system 10. The information processing system 10 is a server that accepts registration and execution of link source applications executed by devices such as an image forming device. The information processing system 10 provides services to users in cooperation with link destination applications of an external service system 40. The information processing system 10 can link with various external service systems 40, and further, by linking with various link destination applications provided by a certain external service system 40, it becomes possible to provide various services to users. As described in FIG. 1(b), the services of the information processing system 10 are used as link source applications by devices such as an image forming device.

[0017] (5) The administrator sets the link information including the link destination application ID on the link source application setting screen. The link information will be described later, but is information for the information processing system 10 to link with a link destination application registered in the external service system 40. The link information includes a link destination application ID and a field code, which will be described later. The terminal device 30 transmits the link information to the information processing system 10. As a result, the link destination application and the link source application to be linked are associated with each other in the information processing system 10.

[0018] Through the above process, the information processing system 10 can identify the link destination application of the external service system 40 by the link destination application ID, and therefore the link source application and the link destination application are able to link with each other.

[0019] (6) It is assumed that a user wishes to use a registered link destination app. As shown in FIG. 1(b), the user operates device 20 such as an image forming apparatus to display a link source app list screen. The user selects a link source app that uses the link destination app. The link destination app ID is specified by the selection of the link source app. For example, a case will be described where the link source app executes the following process. (i) Scan the original to generate image data (ii) The image forming device transmits image data to the information processing system 10. (iii) The information processing system 10 specifies a linkage application and transmits a processing request for image data to the external service system 40. (7) The device 20 such as an image forming device scans an original and transmits the generated image data together with the cooperation destination application ID to the information processing system 10.

[0020] (8) The information processing system 10 designates the link-destination application ID and transmits a request to process the image data to the external service system 40. This enables the link-source application to link with the link-destination application.

[0021] (9) The external service system 40 accepts image data as a processing target of the linked application identified by the linked application ID. When image data becomes a processing target of the linked application, it means that the image data is processed by the linked application. Therefore, the contents of the processing vary depending on the linked application. For example, the image data may be converted into a data format that the linked application processes, the image data may be stored in a state in which the type of image data is managed by adding some attribute to the image data, image processing may be performed on the image data, the image data may be transferred to the outside, or the image data may be provided in response to a request. In addition, the linked application or a module of the service providing system may convert the image data into a data format, add some attribute to the image data and store the image data in a state in which the type of image data is managed, image processing may be performed on the image data, and the processed image data may be transferred to the linked application.

[0022] In this way, the service providing system 100 of this embodiment accepts settings (coordination information) for the information processing system 10 to collaborate with the external service system 40 from the collaboration source app setting screen, and when the information processing system 10 accepts a request to execute the collaboration source app from the device 20, it can collaborate with a specific collaboration target app of the external service system 40 in accordance with the settings accepted on the collaboration source app setting screen.

[0023] <Terminology> The setting related to the correspondence is a setting for associating a coordination source application with a coordination destination application. The storage locations of data managed by the coordination source application and the coordination destination application may be associated with each other. In this embodiment, an example will be described in which a coordination destination application ID (an example of identification information of a second application) is associated with a coordination source application ID (an example of identification information of a first application).

[0024] Cooperation means that two or more parties cooperate to execute a process. In this embodiment, cooperation means that a cooperation source application of the information processing system 10 cooperates with a cooperation destination application of the external service system 40, and the information processing system 10 provides a service.

[0025] The link information is information for the information processing system 10 to link with the external service system 40. In this embodiment, a link destination application ID for using a service provided by the external service system 40 is taken as an example. The link information may further include a field code (field identification information) or a record ID (record identification information). The field code may also be referred to as a column ID that specifies a column of a database.

[0026] A field indicates a column of tabular data held by the linked application, and shows each column in the table in Figure 11.

[0027] A record refers to a row of tabular data held by a linked application, and indicates each row of the table in Figure 11.

[0028] The link source application is an application for the information processing system 10 to provide a service to the device 20 included in the service providing system. A server and a client on a network communicate with each other to process data, and the client can use the results. Such an application can be provided as a Web application. A server is a computer or software that provides information and processing results in response to a request from a client. A screen that a client acquires from a server and displays may be called a Web page. The link source application is not limited to a Web application, and may be provided as a native application. The device 20 downloads a link source application, which is a native application, from the information processing system 10 and executes it, so that the device 20 and the information processing system 10 transmit and receive data such as image data. When the link source application is a native application, the device may acquire the link source application from a device or system different from the information processing system 10. For example, the device 20 may acquire the link source application from an application providing server or the like.

[0029] The information processing system 10 provides a service, and one of the means for providing the service is the execution of a link-source application. The execution of the link-source application may (or may not) link with a link destination application provided by an external service system 40. Since the service provided by the link-source application is realized by executing a series of processes in order, the content and order of the series of processes are defined in the link-source application.

[0030] The external service system 40 also provides a service, and one of the means for providing the service is the execution of a linked application. The external service system 40 can provide a service to a user without linking with the information processing system 10, but in this case, the linked application provided by the external service system 40 is a Web application provided by communication between a server and a client. The service providing system 100 of this embodiment enables a linked application of the external service system 40, which can be used by a user from a terminal device 30 or the like, to be used from the device 20 via the information processing system 10.

[0031] The service of the external service system 40 may be called a linked app (application), or may be called a program, software, site, etc. In other words, the linked app does not need to be called an application as long as it is related to the service of the external service system 40.

[0032] A database is a collection of organized information. It is possible to store, search, and update information. There are relational, hierarchical, and network databases, but any database in which values ​​are stored in items will do. In this embodiment, items are described using the term "field." Setting an item in which data is saved means setting a field in which data is saved.

[0033] In many cases, applications are used to operate data in a database. In this embodiment, a linked application operates the database. The operation includes storing, searching, updating, etc. of information.

[0034] The user means a so-called end user on the customer side, and refers to a person who uses the device 20 including the coordination source application. The administrator is a person who registers the coordination target application and the coordination source application so that the user can use the coordination source application, and is mainly an administrator on the customer side (tenant side). However, it is not necessary to clearly distinguish between the user and the administrator, and the terms are used differently in this embodiment only for convenience.

[0035] <System configuration> First, the system configuration of the service providing system 100 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a diagram showing the system configuration of an example of the service providing system 100 according to this embodiment.

[0036] 2 includes an information processing system 10, a device 20, and a terminal device 30, which are communicatively connected via a wide area network N1 such as the Internet. The service providing system 100 communicates with an external service system 40, which is an external system.

[0037] The information processing system 10 is realized by one or more information processing devices, and provides various services realized by a series of processes in cooperation with an external service system 40 such as a cloud service via a network N1. Specific examples of services provided by the information processing system 10 according to this embodiment will be described later. The information processing system 10 may be realized by cloud computing, or may be realized by a single information processing device. Cloud computing refers to a form of use in which resources on a network are used without being aware of specific hardware resources. The information processing system 10 may exist on the Internet or on-premise. Note that a series of processes is provided by one cooperation source application, and the series of processes is also called a "processing flow" or "workflow."

[0038] The device 20 is various electronic devices used by a user. The device 20 is, for example, an image forming device such as an MFP (Multifunction Peripheral), a PC (Personal Computer), a projector, an electronic whiteboard, a digital camera, etc. The user can use various services provided by at least one of the information processing system 10 and the external service system 40 using the device 20.

[0039] In the following description, when multiple devices 20 are to be distinguished from one another, the term "device 20" will be used. 1 ”, “Equipment 20 2 " etc. should be written using subscripts.

[0040] The terminal device 30 is, for example, a desktop PC, a notebook PC, a smartphone, a tablet terminal, etc., used by an administrator or a user. The administrator or user can operate the terminal device 30 to use various services provided by the information processing system 10 or the external service system 40, and can further configure a linkage destination app or a linkage source app.

[0041] In the following description, when multiple terminal devices 30 are to be distinguished from one another, they will be referred to as "terminal device 30 1 ", "Terminal device 30 2 " etc. should be written using subscripts.

[0042] The external service system 40 is one or more information processing devices that provide a service by executing a link target application via the network N1. The link target application is executed to manage or process data, and the data itself or the processing result becomes the service.

[0043] Examples of the external service system 40 include a cloud service, an ASP (Application Service Provider), and the like, and may include various external services provided via a network. In this embodiment, a table-format database will be described as an example of a service. The external service system 40 may exist on the Internet or on-premise.

[0044] In the following description, when distinguishing between the multiple external service systems 40, the external service systems 40 will be referred to as "external service systems 40" as shown in the figure. 1 "External service system A, "External service system 40 2 " will be described as external service system B, etc.

[0045] <Hardware configuration example> The hardware configurations of the information processing system 10 and the terminal device 30 included in the service providing system 100 according to this embodiment will be described with reference to FIG.

[0046] <<Information processing system and terminal device>> Fig. 3 is a diagram showing an example of a hardware configuration of the information processing system 10 and the terminal device 30 according to the present embodiment. As shown in Fig. 3, the information processing system 10 and the terminal device 30 are constructed by a computer, and include 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.

[0047] Among these, the CPU 501 controls the overall operation of the information processing system 10 and the terminal device 30. The ROM 502 stores programs such as an IPL used to drive the CPU 501. The RAM 503 is used as a work area for the CPU 501. The HD 504 stores various data such as programs. The HDD controller 505 controls the reading or writing of various data from the HD 504 under the control of the CPU 501. The display 506 displays various information such as a cursor, a menu, a window, a character, or an image. The external device connection I / F 508 is an interface for connecting various external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory or a printer. The network I / F 509 is an interface for data communication using the communication network N2. The bus line 510 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 501 shown in FIG. 3.

[0048] Moreover, the keyboard 511 is a type of input means having a plurality of 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 as an example of a removable recording medium. Note that this is not limited to DVD-RW, and may be 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.

[0049] <<Equipment>> 4 is a hardware configuration diagram of an image forming apparatus, which is an example of the device 20. As shown in FIG. 4, the image forming apparatus includes a controller 910, a short-range communication circuit 920, an engine control unit 930, an operation panel 940, and a network I / F 950.

[0050] 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.

[0051] Among these, the CPU 901 is a control unit that performs overall control of the image forming apparatus. The NB 903 is a bridge for connecting 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.

[0052] The MEM-P 902 is composed of a ROM 902a which is a memory for storing programs and data for implementing the various functions of the controller 910, and a RAM 902b which is used for developing the programs and data, and as a drawing memory during memory printing, etc. The programs stored in the RAM 902b may be provided by being recorded in a computer-readable recording medium such as a CD-ROM, CD-R, or DVD in the form of an installable or executable file.

[0053] The SB904 is a bridge for connecting the NB903 to a PCI device and a peripheral device. The ASIC906 is an IC (Integrated Circuit) for image processing purposes having hardware elements for image processing, and plays the role of a bridge connecting the AGP bus 921, the PCI bus 922, the HDD controller 908, and the MEM-C907. The ASIC906 is composed of a PCI target and an AGP master, an arbiter (ARB) that is the core of the ASIC906, a memory controller that controls the MEM-C907, a plurality of DMACs (Direct Memory Access Controllers) that rotate image data using hardware logic, and a PCI unit that transfers data between the scanner unit 931, the printer unit 932, and the facsimile unit via the PCI bus 922. The ASIC906 may be connected to a Universal Serial Bus (USB) interface or an Institute of Electrical and Electronics Engineers 1394 (IEEE1394) interface.

[0054] 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 graphic processing, and by directly accessing the MEM-P902 at high throughput, the graphics accelerator card can be made faster.

[0055] Further, the short-range communication circuit 920 is provided with a short-range communication circuit antenna 920a. The short-range communication circuit 920 is a communication circuit such as NFC or Bluetooth (registered trademark).

[0056] Furthermore, the engine control unit 930 has a scanner unit 931, a printer unit 932, and a facsimile unit 933. The operation panel 940 has a panel display unit 940a such as a touch panel that displays current setting values ​​and a selection screen, etc., and receives input from an operator, and hard keys 940b consisting of 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 instruction. The controller 910 controls the entire image forming apparatus, and controls, for example, drawing, communication, and input from the operation panel 940. The scanner unit 931 or the printer unit 932 includes an image processing unit such as error diffusion and gamma conversion.

[0057] 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 mode becomes document box mode, when the copy function is selected, the mode becomes copy mode, when the printer function is selected, the mode becomes printer mode, and when the facsimile mode is selected, the mode becomes facsimile mode.

[0058] The network I / F 950 is an interface for performing data communication using the communication network N2. The short-range communication circuit 920 and the network I / F 950 are electrically connected to the ASIC 906 via a PCI bus 922.

[0059] <About the function> Next, the functional configuration of the service providing system 100 according to this embodiment will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the functional configuration of the service providing system 100 according to this embodiment.

[0060] <<Equipment>> First, the device 20 has a second communication unit 21, a display control unit 22, an operation acceptance unit 23, an image data generation unit 24, a facsimile processing unit 25, and an email processing unit 26. Each of these functional units is a function or means realized by the CPU 901 executing instructions included in one or more programs installed in the device 20. For example, the second communication unit 21, the display control unit 22, and the operation acceptance unit 23 are realized by a Web browser, and the others are realized by individual applications (native apps).

[0061] The second communication unit 21 transmits and receives various information to and from the information processing system 10. In this embodiment, the second communication unit 21 receives screen information of the coordination source application list screen from the information processing system 10 and transmits image data, coordination information, and the like to the information processing system 10.

[0062] The display control unit 22 interprets screen information of various screens and displays it on the panel display unit 940a. The operation receiving unit 23 receives various operations by the user on the various screens displayed on the panel display unit 940a.

[0063] When the cooperation source application selected by the operation receiving unit 23 generates image data, the image data generating unit 24 scans an original with the scanner unit 931 to generate image data. The facsimile processing unit 25 performs processing related to the reception and transmission of facsimiles by the facsimile unit 933, and when a facsimile is received, requests the information processing system 10 to execute a cooperation source application that is associated in advance. Note that the cooperation source application corresponding to the sender of the facsimile (FAX number) may be requested.

[0064] The email processing unit 26 performs processing related to sending and receiving emails, and when an email is received, requests the information processing system 10 to execute a link source application that is associated with the email in advance. Note that the link source application that corresponds to the sender (email address) of the email may be requested.

[0065] <<Terminal Device>> The terminal device 30 has a first communication unit 31, a display control unit 32, and an operation reception unit 33. Each of these functional units is a function or means realized by the CPU 501 executing instructions included in one or more programs installed in the terminal device 30. The programs may be a web browser or dedicated software.

[0066] The first communication unit 31 transmits and receives various types of information between the information processing system 10 or the external service system 40. In this embodiment, the first communication unit 31 receives various types of screen information and the like from the information processing system 10 or the external service system 40, and transmits information set by an administrator or a user to the information processing system 10 or the external service system 40.

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

[0068] <<Information Processing System>> The information processing system 10 has an application data service unit 11, a setting reception unit 12, an authentication service unit 14, a Web service processing unit 15, an input / output service unit 16, a component 18, and a communication unit 19. Each of these functional units is a function or means realized by the CPU 501 executing instructions included in one or more programs installed in the information processing system 10. Note that, regarding the functions of the information processing system 10 shown in FIG. 5, an "application" refers to a function related to a "linked application" executed in the information processing system 10.

[0069] The communication unit 19 transmits and receives various information between the terminal device 30 and the device 20. The setting reception unit 12 provides a setting site to the terminal device 30 and receives settings for the setting site. The site may refer to a Web page or a Web application (for example, a coordination source application setting screen), or may refer to a server-side system that provides a Web page or a Web application to the terminal device 30. The setting reception unit 12 has a terminal screen providing unit 42, which provides a coordination source application setting screen or the like that allows an administrator to set information required for executing the coordination source application. The terminal screen providing unit 42 generates screen information described in HTML, XML, CSS (Cascade Style Sheet), JavaScript (registered trademark), or the like in response to an HTTP request from the terminal device 30, and transmits the screen information to the terminal device 30 as an HTTP response.

[0070] The application data service unit 11 has an application data management unit 41. The application data management unit 41 manages application data 43 of a purchased link source application for each tenant. The application data 43 is data for mainly associating with a link destination application, such as the above-mentioned link information. The application data 43 is stored in the application data storage unit 13.

[0071] The Web service processing unit 15 provides screen information to the device 20 and accepts execution of a coordination source application from the device 20. The Web service processing unit 15 has a coordination source application execution unit 46 and a device screen providing unit 47. The coordination source application execution unit 46 accepts execution of a coordination source application from the device 20, and requests processing of the coordination source application from the input / output processing unit 48 based on application processing information 53. The device screen providing unit 47 uses screen information 54 to provide screen information such as a coordination source application list screen to the device 20.

[0072] The input / output service unit 16 inputs and outputs data using the authentication service unit 14 and the component 18. The input / output service unit 16 has an input / output processing unit 48 and an application management unit 49. The input / output processing unit 48 executes the coordination source application requested by the coordination source application execution unit 46. During execution, the input / output processing unit 48 refers to the application processing information 53 and requests the component 18 to perform each process included in the coordination source application. The application management unit 49 manages the application processing information 53 and screen information 54 of the coordination source application stored in the application processing information storage unit 17. The application processing information 53 sets which process and in what order the coordination source application performs (for example, a processing request is made to the external service system 40 after OCR). The screen information 54 is information on a screen displayed by the device 20, such as a coordination source application list screen and a setting screen for each application. The application processing information storage unit 17 stores the application processing information 53 and the screen information 54 for each coordination source application.

[0073] The authentication service unit 14 performs processing related to authentication of users (including an administrator) and devices 20. The authentication service unit 14 has a user management unit 44 and a device management unit 45. The user management unit 44 manages information related to users. For example, it holds authentication information such as a user name and a password. The authentication information includes information for the information processing system 10 and information for the external service system 40. The device management unit 45 manages devices 20 associated with tenants. In other words, it manages the identification information of the tenant and the device 20 in association with each other, and when the device 20 is identified, the tenant is also identified.

[0074] Component 18 is a collective term for individual functions that actually perform each process. One block in component 18 corresponds to one process. Component 18 has, for example, an authentication processing unit 51, an external service processing unit 52, and a judgment unit 55. The authentication processing unit 51 is a component 18 that requests authentication-related processing from the authentication service unit 14. The external service processing unit 52 is a component 18 that requests a processing request from the external service system 40. In other words, the external service processing unit 52 is a function for linking with the external service system 40. An external service processing unit 52 is prepared for each type of external service system 40. The judgment unit 55 makes various judgments and controls the branching of the processing flow. In addition to those shown in the figure, the component may have components such as OCR and translation.

[0075] [Table 1] Table 1 shows an example of information stored in the application processing information storage unit 17. The application processing information storage unit 17 is associated with the external service system 40, and has items of the coordination source application ID, application name, screen information, application processing information, and shared application. The coordination source application ID is identification information for identifying the coordination source application. The application name is the name of the coordination source application given by the administrator. In addition, screen information 54 (described in HTML or the like) used when the device 20 displays the icon or setting screen of the coordination source application is associated with the coordination source application. Since the contents and order of a series of processes (processing flow) are defined for the coordination source application, each coordination source application is associated with application processing information 53. A shared application indicates that, while a general coordination source application is given a usage authority for each user, a shared application is an application that can be commonly used by users of a tenant. In Table 1, email reception registration and fax reception registration are shared applications. These are for use by each user.

[0076] When, for example, "external service system A" is specified by the device 20, the application management unit 49 provides the device 20 with a list of coordination source applications associated with "external service system A" from the application processing information storage unit 17. Furthermore, when a coordination source application is specified from the list of coordination source applications, the application management unit 49 identifies screen information and application processing information associated with the coordination source application.

[0077] [Table 2] Table 2 shows an example of information about a user managed by the user management unit 44. The information about a user includes items such as a user ID in the information processing system 10, a user name, an email address, a password, and available coordination source apps. This user also includes an administrator. At least one of the user ID, the user name, and the email address, and the password are authentication information for a user to log in to the information processing system 10. Available coordination source apps are coordination source apps that the user has been given permission to use. Available coordination source apps do not include shared apps.

[0078] The user management unit 44 also has a subdomain, a user name, and a password in the external service system 40 as information about the user. The subdomain is information that identifies a customer (company) in the external service system. The user name and password are authentication information for the user to log in to the external service system 40. The user management unit 44 also has a linkage setting item as information about the user. The linkage setting item becomes "completed" when it is confirmed that the user wishes to link with the external service system 40 and can log in using the authentication information of the external service system 40. The linkage setting is used to determine whether the user can run an app of the external service system 40.

[0079] [Table 3] Table 3 shows an example of application data stored in the application data storage unit 13. The application data has items of a coordination source application ID, a coordination destination application ID, a space ID, a coordination source application setting screen, and n (one or more) field codes, in association with the external service system 40. That is, the application data associates a coordination source application with a coordination destination application. The items of the coordination source application setting screen are information specifying screen information of the coordination source application setting screen in which the coordination source application is set. Each field code is information specifying which data is to be saved in which field of the coordination destination application. For example, it is registered that scanned image data is to be stored in a field with field code 1. Note that a field is an item, and corresponds to a column in a tabular database.

[0080] <<External service system>> 6 is a diagram showing an example of a functional configuration of the external service system 40. The external service system 40 has a fourth communication unit 61, an application determination unit 62, a data processing unit 63, and an application registration acceptance unit 64. Each of these functional units is a function or means realized by the CPU 501 executing instructions included in one or more programs installed in the external service system 40.

[0081] The fourth communication unit 61 transmits and receives various information between the information processing system 10 or the terminal device 30. In this embodiment, it receives information related to the registration of a linked application from the terminal device 30, and receives a processing request for the linked application together with image data and link information from the information processing system 10. It also transmits data to be processed by the linked application (a list of spaces, a list of linked applications, a list of fields / field codes, a list of records, transmitted image data, etc.) to the information processing system 10. When the fourth communication unit 61 communicates with the information processing system 10, an API (Application Interface) of the external service system 40 is used.

[0082] The application registration reception unit 64 provides a link destination application registration screen to the terminal device 30 and accepts registration and editing of link destination applications set by an administrator on the link destination application registration screen. The administrator can register link destination applications simply by customizing the services provided by the information processing system 10. The application registration reception unit 64 assigns unique link destination application IDs to the link destination applications. The application registration reception unit 64 stores information related to the registered link destination applications in the application information storage unit 65.

[0083] The application determination unit 62 determines an application to process image data, etc., which is the target of the processing request, based on the application ID transmitted from the information processing system 10. The data processing unit 63 processes image data, etc., with processing content specific to the application, which is the processing performed by the application determined by the application determination unit 62. In the case of registering a new record, the image data, etc. are stored in a field specified by the application ID and a field code. In the case of registering an existing record, the image data, etc. are stored in a field of the record specified by the application ID, a field code, and a record ID. In addition, for example, the application converts the data into a data format processed by the application, adds some attribute to the image data and stores the image data in a state in which the type of image data, etc. is managed, performs image processing on the image data, transfers the image data to the outside, and provides the image data in response to a request. In the following embodiment, a description will be given of an application to provide a database in a table format. In this case, the data format is converted, managed, and provided.

[0084] [Table 4] Table 4 is an example of application information stored in the application information storage unit 65 of the external service system 40. The application information in Table 4 is in the form of a database regarding linked applications, and is therefore a list of field names. The application information is associated with a space ID, a linked application ID, and a linked application name. A space is a group of several linked applications, and the space ID is its identification information (an example of identification information for a group). Some external service systems 40 may not have a space ID.

[0085] In Table 4, the field names are Record Number, Customer Name, Phone Number, Case Status, New / Added, Delivery Date, Design Request, Design Proposal, Fixed Character String, and Numerical Values, but these have been registered by the administrator and are merely examples. Note that "Design Request" is intended to indicate a request for an expert to revise the color and shape of the image data, and this field name is merely an example. Similarly, "Design Proposal" is the proposal revised by the expert.

[0086] Each field has a field code. The field code is identification information that identifies the field. Note that there may be fields without field codes, but in this case, it becomes difficult to link by specifying the field. As will be described later, the field name and field code can be set arbitrarily by the administrator. The field code may be assigned by the external service system 40.

[0087] A value corresponding to each field is set from the device 20 or from the terminal device 30. For example, image data generated by the device 20 is set in a field called "design preference." This is the case when the administrator designates the field code of "design preference" as the field in which image data is to be set on the coordination source application setting screen.

[0088] <Application processing information> Next, details of the application processing information will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of the application processing information stored in the application processing information storage unit 17.

[0089] Application processing information 53A shown in FIG. 7 is information related to a series of processes for implementing a service of requesting "external service system A" to process image data generated by scanning with device 20.

[0090] The application processing information 53A includes a flow ID 1201A indicating identification information of the application processing information 53A, a flow name 1202A indicating the name of the application processing information 53A, and flow details 1203A indicating the processing contents of a series of processes. The flow name 1202A also serves as the name of the coordination source application.

[0091] Furthermore, the detailed flow 1203A includes processing content 1223A indicating a processing request to be made to "external service system A."

[0092] In the processing content 1223A, the component ID "ExService_A" of the component 18 that executes processing in cooperation with "external service system A", the operation ID "processFile" indicating a processing request, and the parameters "AppId", "FieldCode", and "UserName" are specified. The linked application ID is stored in "AppId", a field code is stored in "FieldCode", and a user name (or a user ID) is stored in "UserName". Note that the parameters shown in the figure are only a partial list, and the application processing information may include many more parameters. For example, a record ID is also set as a parameter.

[0093] As a result, in a series of processes based on the application processing information, a processing request can be made to the "external service system A" for the scanned image data. In this manner, the information processing system 10 according to the present embodiment can transmit linkage information and the like to the external service system 40 using parameters of the application processing information, and link with the link destination application.

[0094] 8 is a diagram showing another example of the application processing information. The application processing information shown in Fig. 8 is information regarding a series of processes in which the device 20 performs OCR on image data of a facsimile received, and transmits a processing request for the image data to the "external service system A."

[0095] It includes a flow ID 1201C indicating identification information of the application processing information, a flow name 1202C indicating the name of the application processing information 53C, and flow details 1203C indicating the content of a series of processes.

[0096] Furthermore, the flow details 1203C includes a process content 1213C indicating OCR processing, and a process content 1223C indicating distribution (uploading) to "external service system A". The process content 1213C specifies the component ID "ocr" of the component 18 that executes the OCR processing, the operation ID "process", and the parameters "language" and "outputType". The process content 1223C adds two parameters "FaxNumber" and "FileCodeFax". "FaxNumber" is the fax number of the sender, and "FileCodeFax" is the field code of the linked application in which the fax number is registered. In this way, the information processing system 10 can transmit multiple field codes to the external service system 40 by specifying which field the codes belong to.

[0097] As a result, in a series of processes based on the application processing information 53, the facsimile image data and the FAX number can be stored in the "external service system A."

[0098] The execution order of the processes defined in each processing content is from top to bottom in flow detail 1203C. That is, in a series of processes (application processing information) based on application processing information 53C shown in Fig. 8, the processes defined in processing content 1213C are executed first, followed by the processes defined in processing content 1223C. However, this is not limiting, and the application processing information may define, for example, information indicating the execution order of the processes defined in each processing content.

[0099] <Processing details> Next, the details of the processing of the information processing system 10 according to this embodiment will be described.

[0100] First, a process in which an administrator creates application processing information using the terminal device 30 and registers the application processing information in the application processing information storage unit 17 will be described with reference to Fig. 9. Fig. 9 is a sequence diagram showing an example of a process for registering application processing information.

[0101] The administrator performs an operation to start creating application processing information using the terminal device 30. For example, the administrator can perform an operation to start creating application processing information by logging in to the information processing system 10 using the terminal device 30 and then selecting a “Create application processing information” button or the like on a portal screen or the like that is displayed after the login.

[0102] S1, S2: When the operation receiving unit 33 of the terminal device 30 receives an operation to start creating application processing information, the first communication unit 31 transmits an application list request to the terminal screen providing unit 42 of the information processing system 10. When the terminal screen providing unit 42 receives the application list request, it transmits the application list request to the application management unit 49. The application list is information for displaying a list of coordination source applications for providing a service. This coordination source application is a template of the coordination source application, such as a scan application or a print application. The administrator creates the coordination source application by editing the template of the coordination source application. The first communication unit 31 of the terminal device 30 receives screen information of the application list screen.

[0103] S3 to S5: Next, the administrator performs an operation to select a template of the coordination source app for creating application processing information from the application list screen. When the operation accepting unit 33 of the terminal device 30 accepts the operation to select the template, the first communication unit 31 transmits an acquisition request for an application processing information creation screen to the terminal screen providing unit 42 of the information processing system 10. The acquisition request includes information for identifying the template of the coordination source app selected by the administrator. The terminal screen providing unit 42 transmits an acquisition request for the application processing information creation screen to the application management unit 49. As a result, the first communication unit 31 of the terminal device 30 receives screen information of the application processing information creation screen. An example of the application processing information creation screen is shown in FIG. 10.

[0104] S6: On the application processing information creation screen, the administrator can edit the template, give an application name such as "new record registration", and create application processing information. The administrator also sets items that the user should set when executing the link source application and items that should not be set. For example, the administrator can set to display the scan reading settings but not to display the save destination. This becomes the screen information stored in the application processing information storage unit 17.

[0105] S7, S8: When the administrator creates the application processing information, the first communication unit 31 of the terminal device 30 transmits a registration request for the application name, application processing information, and screen information to the terminal screen providing unit 42 of the information processing system 10. The terminal screen providing unit 42 transmits the application name, application processing information, and screen information to the application management unit 49. The application management unit 49 assigns a number to the coordination source application ID, associates it with the coordination source application ID, and stores the application name, application processing information, and screen information in the application processing information storage unit 17. The coordination source application ID is transmitted to the terminal device 30.

[0106] S9, S10: The administrator performs an operation to release the application. Releasing refers to making the coordination source application available to the user. When the operation receiving unit 33 of the terminal device 30 receives the operation, the first communication unit 31 designates the coordination source application ID and transmits an application release request to the terminal screen providing unit 42. The terminal screen providing unit 42 transmits the coordination source application ID and the application release request to the application data management unit 41. The application data management unit 41 associates the coordination source application ID with the coordination source application setting screen and stores them in the application data storage unit 13. Screen information of the coordination source application setting screen is prepared in advance for each external service system 40. Therefore, in the application data of Table 3, the external service system 40, the coordination source application ID, and the coordination source application setting screen are registered. Then, the coordination source application ID and n field codes are also registered in the application data of Table 3 by settings from the coordination source application setting screen described later.

[0107] Furthermore, in the terminal device 30, an administrator associates the cooperation source application ID with the function of the terminal device 30. For example, when a cooperation source application using a FAX reception component is created, an operation is performed to register this cooperation source application ID in the facsimile processing unit 25.

[0108] In this way, the link source application can be specified from the facsimile processing unit 25, etc. In addition, when the link source application is executed from the facsimile processing unit 25, etc., the link source application to be executed cannot be specified, so that the facsimile processing unit 25 can specify the link source application to the information processing system 10 by setting a unique ID (link source application ID) in the terminal device 30 and the application data at the timing of releasing the link source application.

[0109] Fig. 10 is a diagram showing an example of an application processing information creation screen. The application processing information can be set by an administrator by arranging icons 2001, 2002 representing each process in a square. These icons 2001, 2002 correspond to one process in the component 18. The processes are executed in order from left to right, and the execution order is indicated by an arrow 2003. Fig. 10 shows application processing information in which the information processing system 10 registers image data scanned by a device in a record in the external service system 40 and then sends an email.

[0110] <Screen example for registering a linked app to an external service system> The following describes an example of a screen displayed by the terminal device 30 using screen information acquired from the external service system 40 when the user registers a linkage destination application in the external service system 40. Registering an application in the external service system 40 is one phase of the preparation stage described in FIG.

[0111] When the administrator registers a new linked application, the terminal device 30 is connected to the external service system 40 and a linked application registration screen is displayed. The screens in the following Figs. 11 to 17 are displayed by the terminal device 30 when the terminal device 30 transmits an HTTP request to the external service system 40 and the external service system 40 transmits the screen information in an HTTP response.

[0112] Fig. 11 is an example of a linked application registration screen (part 1) 200 displayed by the terminal device 30. Field names for identifying fields are listed at the top of the columns in Fig. 11. For example, "record number," "customer name," "telephone number," and the like in Fig. 11 are called field names. Note that the same field name may be assigned to different fields. For this reason, field identification information for identifying the field in the linked application is stored in the linked application in association with each field.

[0113] For ease of explanation, Fig. 11 shows the field names of the linked applications that have already been registered in the information processing system 10. When setting a new field, the field names are not displayed, but the method of registering the linked application from Fig. 12 onwards is the same.

[0114] In this embodiment, the application ID 212 is displayed in the URL. https: / / company.ExService_A.com / 2575 / This "2575" is app ID 212.

[0115] The linked application registration screen (type 1) 200 displays the field names (record number 201, customer name 202, phone number 203, case status 204, new / added 205, delivery date 206, design request 207, design proposal 208, fixed string 209, and numeric value 210) shown in the application information in Table 4, and a value is set for each field. One line is called a record and is assigned a record number. The user can display and edit the field values ​​on the linked application registration screen (type 1) 200. In FIG. 11, blank fields are fields for which no value is set (or for which the user does not have permission to display).

[0116] The link-destination application registration screen (type 1) 200 has a setting button 211. When the administrator presses the setting button 211, the terminal device 30 displays the link-destination application registration screen (type 2) 210, and the administrator can edit the field name.

[0117] 12 is an example of a link destination application registration screen (part 2) 210 displayed by the terminal device 30. The link destination application registration screen (part 2) 210 has an application name field 229, a form field 222, and a work area 223. The administrator can set an application name in the application name field 229, and the application name in the application name field 229 becomes the link destination application name in Table 4. In the form field 222, functions available in the service provided by the external service system 40 are displayed as a form. For example, there are forms such as a label field 222A, a character input field 222B, a rich editor 222C, a character string field 222D, a numerical value field 222E, a calculator 222F, a radio button 222G, a check box 222H, a multiple selection field 222I, a drop-down field 222J, a date field 222K, a time field 222L, a date and time field 222M, an attachment field 222N, a link field 222O, and a user selection field 222P. The user can place a desired form by dragging it from the form column 222 to the work area. This form becomes a field.

[0118] For example, the attachment field 222N is a field in which scanned image data is registered. In this embodiment, image data generated by the device 20 is set in a field called "design request", but the field called "design request" is created in a form called "attachment file". In other words, the image data is positioned as an attachment file to be attached to the linked application. If there is another form such as "image", the "design request" field may be created in this form.

[0119] 12, the work area 223 displays the names of the fields in Table 4 and their values ​​(currently blank). Specifically, it has a customer name column 223A, a phone number column 223B, a numerical value column 223C, a case status column 223D, a new / added column 223E, a delivery date column 223F, a design request column 223G, and a design proposal column 223H. The user can edit, duplicate, or delete fields, or set new fields. For example, when the user moves the mouse pointer to the top right of a field, possible work items 221 are displayed.

[0120] Fig. 13 is an example of a linkage destination application registration screen (part 3) 220 displayed by the terminal device 30 on which the work item 221 is displayed. In Fig. 13, an edit button 221A, a duplicate button 221B, and a delete button 221C are displayed as the work item 221. It is assumed that the user presses the edit button 221A. This causes a details pop-up screen that enables editing of the form to be displayed.

[0121] 14 is an example of a details pop-up screen 230 in which details of a form called an attachment (the "design request" field) are set. The details pop-up screen 230 has a field name column 231, a check box 232 associated with "Do not display field name," a check box 233 associated with "Make required field," a thumbnail size selection column 234, and a field code column 235. Field name column 231: Field name A check box 232 corresponding to "Do not display field names": When checked, the field names are not displayed. A check box 233 corresponding to "make required field": When checked, the field name becomes a required field. Thumbnail size selection field 234: The size of the thumbnail of the attached file (image data) is displayed in a pull-down menu. Field code field 235: The field code of this form ("Design request") is displayed and can be edited. When the user moves the mouse pointer to the pen mark 235A, a field code input field is displayed and any field code can be input.

[0122] In FIG. 14, "7" is the field code for the "Design Desired" field. In this way, the field code may be the same as the field name. Also, the application registration acceptance unit 64 of the external service system 40 may set a default field code that is the same as the field name. As long as there is no duplication within the application, the user can set the field code appropriately using letters, numbers, alphabets, etc., or a combination thereof. In FIG. 14, "7" is set as the field code (see FIG. 41). Since the same field name may be given to different fields, the field code is set to uniquely identify the field in the linked application.

[0123] Similarly, editing of the field code in the numerical value field 223C will be described with reference to Fig. 15 and Fig. 16. Fig. 15 is an example of a linked application registration screen (part 4) 220 displayed by the terminal device 30 on which the work items are displayed. In Fig. 15, the mouse pointer has been moved to the upper right of the numerical value field 223C. Therefore, the work items 221 are displayed. The user has pressed the edit button 221A.

[0124] 16 is an example of a details pop-up screen 240 in which details of a form called a numeric value field 223C are set. The details pop-up screen 240 in FIG. 16 has a value restriction field 241, an initial value field 242, a number of decimal places to be displayed field 243, a unit symbol field 244, and a field code field 245. Value restriction field 241: The maximum and minimum values ​​that can be input into the numerical value field are specified. Initial value column 242: An initial value that is displayed without the user having to input a value is specified. Number of decimal points to be displayed field 243: When there is a decimal point, the number of decimal points to be displayed is specified. Unit symbol column 244: A column in which the unit of a numerical value is specified. Field code column 245: may be the same as in Fig. 14. The field code in Fig. 16 is "numeric value".

[0125] 17 is a diagram showing an example of a link destination application list screen 249 displayed by the terminal device 30. The administrator specifies, for example, a space ID to display a list of link destination applications. The link destination application list screen 249 has items such as an application ID 249A and an application name 249B. The application ID 249A indicates the link destination application ID. The administrator can also confirm the link destination application ID from this screen. If the administrator selects the application name, a link destination application registration screen (part 2) 210 as shown in FIG. 12 is displayed.

[0126] <<Setup flow>> FIG. 18 is an example of a sequence diagram illustrating a procedure for an administrator to register an application in the external service system 40. In FIG.

[0127] S11: The administrator connects the terminal device 30 to the external service system 40, logs in, and displays the linked application registration screen (part 1) 200. The administrator confirms the linked application ID.

[0128] S12: When the administrator presses the setting button 211, the operation reception unit 33 of the terminal device 30 receives the pressing, and the first communication unit 31 transmits to the external service system 40 a message that the setting button 211 has been pressed.

[0129] S13: The fourth communication unit 61 of the external service system 40 receives a notification that the setting button 211 has been pressed, and the app registration reception unit 64 transmits screen information of the linked app registration screen (part 2) 210 to the terminal device 30 via the fourth communication unit 61.

[0130] S14: The first communication unit 31 of the terminal device 30 receives the screen information of the linked application registration screen (part 2) 210, and the display control unit 32 of the terminal device 30 displays it on the display 506. The administrator appropriately edits the form, and the operation receiving unit 33 receives the edits of the form.

[0131] S15: When the administrator presses the edit button 221A to edit a field, the operation acceptance unit 33 accepts the pressing of the edit button 221A.

[0132] S16: As a result, the display control unit 32 displays the detail pop-up screen 230 on the display 506. Note that JavaScript (registered trademark) is used for screen transitions that do not communicate with the external service system 40.

[0133] S17: Next, when the administrator sets a field code, the operation acceptance unit 33 of the terminal device 30 accepts the field code. Note that steps S14 to S17 are repeatedly executed as appropriate.

[0134] S18: When the administrator finishes registering the linked app and presses a predetermined button, the first communication unit 31 transmits the setting details for the linked app set by the administrator to the external service system 40. The fourth communication unit 61 of the external service system 40 receives the setting details, and the app registration reception unit 64 stores the field name, field code, etc. in the app information storage unit 65. With the above, the linked app in which the service provided by the external service system 40 is customized has been registered.

[0135] <Setting authentication information for the information processing system that links with the external service system> Next, a description will be given of setting of authentication information in the information processing system 10 so that the information processing system 10 can cooperate with a cooperation destination application of the external service system 40. Although this phase is not described in Fig. 1, it is one of the preparation phases. In addition, this phase is performed by an administrator or a user, but for convenience of description, it will be described as being mainly performed by an administrator.

[0136] In order for each user to operate the device 20 and link with a link target application of the external service system 40, the user must be able to log in to the external service system 40 through the information processing system 10. For this reason, the administrator registers the authentication information of the user in the external service system 40 in the information processing system 10 as follows. The administrator connects the terminal device 30 to the information processing system 10 and displays a user information registration screen. The screens in the following Figs. 19 to 23 are displayed by the terminal device 30 when the terminal device 30 transmits an HTTP request to the information processing system 10 and the information processing system 10 transmits the screen information in the HTTP response.

[0137] 19 shows an example of an initial screen 250 displayed by the terminal device 30. Since the administrator has already logged in to the information processing system 10, the user name is displayed in the user name field 251. When the administrator presses the user name field 251, a menu is displayed, and the administrator presses a My Page button 252 to display a My Page for setting user information. When the My Page button 252 is pressed, the initial screen 250 transitions to a My Page screen.

[0138] 20 shows an example of a MyPage screen (part 1) 260 displayed by the terminal device 30. The MyPage screen 260 has a setting content selection field 261 and a detail display field 262. Immediately after the MyPage screen 260 is displayed, the contents of the basic settings in the setting content selection field 261 are displayed in the detail display field 262. The information processing system 10 transmits information managed by the user management unit 44 to the terminal device 30.

[0139] The details display field 262 in Fig. 20 displays a user ID 268, email address 263, a surname field 264, a first name field 265, and an email reply language field 266. The administrator can edit the surname field 264 and the first name field 265, and select an email reply language in the email reply language field 266. Editing the user ID and email address requires a connection to another system. When the administrator presses external service linkage 267 in the setting content selection field 261, the screen transitions to the My Page screen (part 2).

[0140] 21 shows an example of a MyPage screen (part 2) 270 displayed by the terminal device 30. The details display field 262 of the MyPage screen (part 2) 270 has an external service account login setting field 271 and an external service file transmission / reception setting field 272.

[0141] The external service account login setting field 271 is a field where the administrator sets whether or not to perform so-called single sign-on using a mechanism such as OAUTH. When the administrator presses the "Link" button 271A of the external service system 40 with which he or she wants to link, the administrator logs into the information processing system 10 with the account (user ID and password) of the external service system 40 displayed in the external service account login setting field 271. Therefore, in this case, the administrator does not need to register authentication information for the external service system 40.

[0142] In this embodiment, OAUTH may be used, but below, a method of authentication using a password or the like registered in the external service system 40 will be described. The external service file transmission / reception setting field 272 has an external service name 273, a link field 274, a share field 275, a "Link" button 276, and a "Cancel link" button 277. The external service name 273 is a list of services that can be purchased by the company (called a tenant from the information processing system 10) to which this administrator belongs. The services are displayed regardless of whether they have actually been purchased. If the administrator sets up a link with an external service system 40 that the company has not purchased, an error message stating that there is no license will be displayed when the link source app is executed.

[0143] The linkage field 274 is a field that displays whether or not linkage settings have been made. The linkage settings are displayed as "Settings Made" when the information processing system 10 can log in to the external service system 40 with the user's authentication information. That is, the value of the "Linkage Settings" managed by the user management unit 44 in Table 2 is displayed.

[0144] The sharing field 275 displays whether or not the linked application of the external service system 40 can be shared with other users. Whether or not to share can be set by the administrator on the screen of FIG.

[0145] The "Link" button 276 is a button that allows the user to make settings regarding linkage with a link destination application of the external service system 40, and the "Cancel Link" button 277 is a button for canceling the linkage. When the "Link" button 276 is pressed, the authentication information setting pop-up screen of FIG. 22 is displayed. The "Cancel Link" button 277 can only be pressed when the linkage field 274 is "Settings Completed." When the "Cancel Link" button 277 is pressed, the value of "Linkage Settings" in Table 2 managed by the user management unit 44 is no longer "Settings Completed," and "Settings Completed" is deleted from the linkage field 274.

[0146] Fig. 22 shows an example of an authentication information setting pop-up screen 280 displayed by the terminal device 30. The authentication information setting pop-up screen 280 has a subdomain field 281, a user name field 282, a password field 283, a check box 284 that reads "Allow linked services to be used as shared accounts within the tenant," and a confirmation button 285. For the sake of explanation, a login screen 286 of the external service system 40 is also displayed in Fig. 22.

[0147] The login screen 286 of the external service system 40 is prepared for each group, such as a company to which the user belongs, and the URL of the login screen is also for a specific company. For this reason, the URL "https: / / company.ExService_A.com" has information that can identify the company. "Company" is the information that can identify the company. This is called a subdomain. The reason that the login screen is prepared in this way is due to the design of the external service system 40, and subdomains are not necessary.

[0148] The administrator enters a subdomain in the subdomain field 281, a username for logging in to the external service system 40 in the username field 282, and a password for logging in to the external service system 40 in the password field 283. When the administrator presses the confirmation button 285, the terminal device 30 transmits the subdomain, username, and password to the information processing system 10. The authentication processing unit 51 of the information processing system 10 attempts to log in to the external service system 40 with the subdomain, username, and password. In this embodiment, a case will be described where logging in is successful.

[0149] A checkbox 284 "Allow the linked service to be a shared account within the tenant" is a checkbox for the administrator to set the link source app as a shared app. When checked, "OK" is set in the sharing column 275 in FIG. 21.

[0150] Fig. 23 is an example of a My Page screen (part 3) 290 displayed by the terminal device 30 when the information processing system 10 has successfully logged in to the external service system 40. The My Page screen (part 3) 290 in Fig. 23 displays a message 291 saying "Success." In other words, it displays that login has been successful and that the linkage settings have been completed. When login is successful, as shown in Table 2, the authentication processing unit 51 of the information processing system 10 registers the subdomain, user name, and password in the user management unit 44, and registers "Completed" in the linkage settings.

[0151] <<Operation procedure for setting authentication information in the information processing system>> 24 is an example of a sequence diagram explaining a procedure in which an administrator registers authentication information in the information processing system 10. Note that, although the communication unit 19 performs communication in the information processing system 10, the communication unit 19 is omitted in the following sequence diagram for convenience of explanation.

[0152] S21: The administrator logs in to the information processing system 10 by using a user name and password for the information processing system 10. The operation reception unit 33 of the terminal device 30 receives the input, and the first communication unit 31 designates the user name and password and transmits a login request to the terminal screen providing unit 42.

[0153] S22: The terminal screen providing unit 42 receives the login request. The terminal screen providing unit 42 designates a user name and password and transmits the login request to the user management unit 44. The user management unit 44 authenticates the administrator based on whether the transmitted user name and password are registered in the user information it manages. In this embodiment, it is assumed that the authentication is successful.

[0154] S23: Since the authentication is successful, the first communication unit 31 of the terminal device 30 requests the terminal screen providing unit 42 to provide screen information of the initial screen 250, the My Page screen (type 1) 260, and the My Page screen (type 2) 270 in response to the administrator's operation.

[0155] S24: The first communication unit 31 of the terminal device 30 receives the screen information of the initial screen 250, the My Page screen (type 1) 260, and the My Page screen (type 2) 270, and the display control unit 32 of the terminal device 30 displays these screens. In addition, the display control unit 32 displays the authentication information setting pop-up screen 280 in response to an operation by the administrator.

[0156] S25: The administrator inputs a sub-domain, a user name, and a password into the authentication information setting pop-up screen 280. The operation reception unit 33 of the terminal device 30 receives these, and the first communication unit 31 transmits the sub-domain, the user name, and the password to the terminal screen providing unit 42.

[0157] S26: The terminal screen providing unit 42 receives the subdomain, the user name, and the password. The terminal screen providing unit 42 requests the input / output processing unit 48 to store the subdomain, the user name, and the password. The subdomain may not be essential.

[0158] S27: The input / output processing unit 48 requests the external service processing unit 52 to authenticate the external service system 40 by specifying the sub-domain, the user name, and the password.

[0159] S28: The external service processing unit 52 requests authentication using the subdomain, the user name, and the password to the external service system 40. In this embodiment, it is assumed that the authentication is successful.

[0160] S29: If the authentication is successful, the input / output processing unit 48 transmits the authentication information (subdomain, user name, and password) of the external service system 40 to the user management unit 44, and the user management unit 44 stores the authentication information. With the above, the authentication information of the external service system 40 is registered in the information processing system 10.

[0161] If the app is not a shared app, the authentication information you set here will be the account used by the app. If the app is a shared app, each user can use the authentication information set by the administrator.

[0162] <Settings for the source app of the information processing system to link with the external service system> Next, a description will be given of the setting of the link source application of the information processing system 10 so that the information processing system 10 can link with the link destination application of the external service system 40. This phase is one of the preparation phases described in Fig. 1. This phase is performed by the client's administrator for shared applications, and by each user for personal link source applications.

[0163] The administrator sets the link information in the link source application so that each user can link with the link destination application of the external service system 40. The administrator or the user has already registered the application processing information and the screen information of "new record registration" for linking with the link destination application of the external service system 40 in the information processing system 10 on the application processing information creation screen as described in FIG. 10. The "new record registration" application is the link source application that adds the data transmitted from the device 20 as a new record in the link destination application shown in FIG. 11. That is, it is the link source application for adding a new row to the table managed by the link destination application shown in FIG. 11 and saving the data. Also, "existing record registration" is the link source application that saves the data transmitted from the device 20 in an already existing record in the link destination application shown in FIG. 11. That is, it is an application for saving the data in any row specified by the device 20 in the table managed by the link destination application shown in FIG. 11.

[0164] The administrator or user sets the linkage destination application ID, field code, etc. as linkage information in the application processing information, and sets information related to screen display in the screen information.

[0165] An administrator or a user connects the terminal device 30 to the information processing system 10 and displays an initial screen. The screens in the following Figs. 25 to 31 are displayed by the terminal device 30 when the terminal device 30 transmits an HTTP request to the information processing system 10 and the information processing system 10 transmits screen information in an HTTP response.

[0166] FIG. 25 shows an example of an initial screen 300 displayed by the terminal device 30. The initial screen 300 has an administrator menu and a general user menu, and the administrator menu will be described below. The initial screen 300 has a user management icon 301, a tenant information icon 302, an application management icon 303, and a device management icon 304. The user management icon 301 is an icon for the administrator to add, delete, edit, etc. a user. The tenant information icon 302 is an icon for confirming and changing what kind of contract the customer has for the provision of the cooperation source application. The application management icon 303 is an icon for adding, deleting, editing, etc. a cooperation source application (i.e., application processing information). The device management icon 304 is an icon for managing how the device 20 is used. The administrator presses the application management icon 303 to edit the cooperation source application. This causes a service selection screen to be displayed.

[0167] 26 shows an example of a service selection screen 310 displayed by the terminal device 30. The service selection screen 310 displays a list of the names of external service systems 40 with which the information processing system 10 can cooperate. To cooperate with the external service system 40, a tenant needs to purchase a license, but the list of names of the external service systems 40 is displayed regardless of whether or not a license is purchased.

[0168] When the administrator selects “External service system A” 311 from the list, the information processing system 10 transmits the application name and the like of the coordination source application associated with “External service system A” to the terminal device 30. That is, the application data management unit 41 identifies the coordination source application associated with “External service system A” from the application data, and obtains the application name of the coordination source application from the application management unit 49.

[0169] Fig. 27 is an example of a coordination source application selection screen 320 displayed by the terminal device 30. Since the administrator selected "external service system A" from the list in Fig. 26, the coordination source application selection screen 320 displays a list of coordination source applications that coordinate with the coordination destination application of "external service system A". In Fig. 27, icons 321-326 of six coordination source applications are displayed, but the number of coordination source applications depends on the number of application processing information registered by the administrator. At least one is sufficient, but there may be zero before the coordination source application is registered.

[0170] All six link source apps can link with a link destination app of "external service system A", but the link destination apps of "external service system A" may be the same or different. In other words, different link destination apps may correspond to the same link source app, the same link destination app may correspond to different link source apps, or different link destination apps may correspond to different link source apps. Even if the link destination app of multiple link source apps is the same, the field codes may be the same or different. In the following description, it is assumed that the link source app of "Register new record" is selected.

[0171] Fig. 28 is an example of a coordination source application setting screen (part 1) 330 displayed by the terminal device 30 when the coordination source application "Register new record" is selected, Fig. 29 is an example of a coordination source application setting screen (part 2) 340, Fig. 30 is an example of a coordination source application setting screen (part 3) 350, and Fig. 31 is an example of a coordination source application setting screen (part 4) 360. For convenience of drawing, each screen is divided into four in Figs. 28, 29, 30, and 31.

[0172] Furthermore, these screens include, in addition to the above-mentioned coordination information settings (A) such as the coordination destination application ID and field code, icon display settings (B) as to how the device 20 displays the icon of the coordination source application, settings (C) related to the execution of the coordination source application, and scan settings (D). Note that the coordination information settings (A) are set in application data, the settings (C) related to the execution of the coordination source application and the scan settings (D) are set in application processing information, and the icon display settings (B) are set in screen information.

[0173] The link source application setting screens (part 1) to (part 4) each have an external service name 331, a user name selection field 332, an application ID setting field 333, a space ID field 334, a field code field for strings 335, an input field for string fields 336, a field code field for image data 337, an email address field 338, an email subject field 339, an OCR language selection field 340, an output format selection field 341, a blank page removal setting field 342, a file name field 343, a date label field 344, a date separator field 345, a date format field 346, a dictionary label field 347, a dictionary separator field 348, a dictionary specification field 349, a dictionary display width field 350, and a default print setting field 351 (a reading color mode field, a document surface field, a document set direction field, a reading resolution field, a document size field, a manual density field, a reading method field, and a preview field). External service name 331 . . . This is the name of the external service system 40 selected in the "External service system A" 311 in FIG. User name selection field 332(C)...This is where the administrator's authentication information to be used when using a shared application is set. This is because in the case of a shared application, the user is not specified and there may be multiple administrators. This specifies the authentication information of the user management unit 44. · Application ID setting field 333(A)... A destination application ID is set to indicate which destination application in the external service system 40 the source application is to be coordinated with. The destination application ID is displayed on the terminal device 30 as shown in FIG. Space ID field 334(A): Identification information of a space for grouping and managing a plurality of link source applications is set. Character string field code column 335(A)...This is a column in which a field code of a character string column of the coordination source application is set. The field code is displayed on the terminal device 30 as shown in Fig. 14. Also, the information processing system 10 can cause the terminal device 30 to display it. · String field input column 336 (B)...The initial value of the string field is set. Image data field code column 337(A): The field code of the field in which image data is stored is set. The field code may be manually entered by the administrator or may be displayed from a pull-down menu or the like. When a link destination application ID is entered in the application ID setting column 333, the terminal device 30 transmits the link destination application ID to the information processing system 10, and the information processing system 10 obtains all field codes set in the link destination application identified by the link destination application ID from the external service system 40. This allows the terminal device 30 to display a list of field codes. ·Email address field 338 (C)...The email address of the contact in case an error occurs during execution of the linked application is set. · Email subject field 339(C)…The email subject is also set. ·OCR language selection field 340(C)…The language to be recognized by OCR is selected. If this setting is not present, the language will be selected automatically. Output format selection field 341(C): The format in which image data is output is selected. Blank page removal setting field 342(C): Whether or not to remove blank pages is selected. File name field 343(C): The file name of the image data is set here. Date label field 344(B): The display name of the date field is set (eg, "Created Date and Time"). · Date separator field 345 (B)…The character used to separate numbers in a date (such as “-” in YY-MM-DD) is specified. Date format field 346(B): The date display format (in the order of YY, MM, DD) is selected. Dictionary label field 347(B)...A display name for the dictionary field is set. A dictionary is a list of words that assists the user in inputting information in the device 20. The words in the dictionary specification field 349(B) are displayed on the device 20. Dictionary delimiter field 348(B): A delimiter between dictionaries (such as "," or ":") is specified. Dictionary designation field 349(B): A list of words to be displayed by the device 20 is designated. "Design", "quote", and "order form" are examples of words. Dictionary display width field 350(B)...The size at which the device 20 displays the dictionary field is set. A read color mode field 351A(D) is used to set whether the document is to be read in color, monochrome, or in an automatic determination mode. Document surface field 351B(D): The reading surface (single-sided or double-sided) is set. Document Set Direction Column 351C(D): The document read direction is set. · Scan resolution field 351D(D)…The resolution at the time of scanning is set. · Original size column 351E(D)... The size of the original is set. Manual Density Column 351F(D)…The density at the time of scanning is set. Scan method field 351G(D): Bulk scan or individual scan (normal) is set. Preview column 351H(D): Specifies whether or not to display the preview.

[0174] <<Operation procedure for setting linkage information etc. to the information processing system>> FIG. 32 is an example of a sequence diagram illustrating a procedure in which an administrator sets cooperation information and the like in the information processing system 10. In FIG.

[0175] S31 to S33: The administrator connects the terminal device 30 to the information processing system 10 and logs in. The login method may be the same as in FIG.

[0176] S34: The terminal device 30 displays the above-mentioned initial screen 300 and service selection screen 310, and the user performs an operation to specify the external service system 40 and display the coordination source application selection screen 320. The operation acceptance unit 33 of the terminal device 30 accepts the operation, and the first communication unit 31 requests the coordination source application selection screen 320 from the terminal screen providing unit 42.

[0177] S35: The terminal screen providing unit 42 receives a request for the coordination source application selection screen 320. The terminal screen providing unit 42 designates the identification information of the external service system 40 and requests the application data management unit 41 to send a list of coordination source applications. The application data management unit 41 transmits a list of applications (the application names can be acquired from the application management unit 49) associated with the external service system 40 to the terminal screen providing unit 42. The application list may include applications that cooperate with other external service systems and applications that do not cooperate with other systems, in addition to the applications associated with the external service system 40. In this way, the terminal screen providing unit 42 generates screen information for the coordination source application selection screen 320. Note that the coordination source application selection screen 320 includes the coordination source application ID. In addition, the terminal screen providing unit 42 includes only the coordination source applications that the logged-in administrator or user has authority to use (the administrator has authority for personal applications and all shared applications, and the user has authority for personal applications) in the coordination source application selection screen 320. As shown in Table 2, the user management unit 44 manages the authority.

[0178] S36: When the administrator selects a link source application, the operation reception unit 33 of the terminal device 30 receives the selection.

[0179] S37: The first communication unit 31 of the terminal device 30 transmits the coordination source application ID of the selected coordination source application to the terminal screen providing unit .

[0180] S38: The terminal screen providing unit 42 receives the coordination source application ID. The terminal screen providing unit 42 specifies the coordination source application ID and acquires the screen information of the coordination source application setting screens (No. 1) 330 to (No. 4) 360 registered in the application data management unit 41 at the time of application release. Since the screen information of the coordination source application setting screen is transmitted to the terminal device 30, the terminal device 30 displays the coordination source application setting screens (No. 1) 330 to (No. 4) 360.

[0181] Steps S39 to S41 are executed when the link source application selected by the administrator is a shared application.

[0182] S39: In the case of a shared application, since it is necessary to set an administrator who will log in, the first communication unit 31 requests a list of accounts from the terminal screen providing unit 42. In this case, authentication information of an administrator in the same tenant as the logged-in administrator is requested.

[0183] S40: The terminal screen providing unit 42 receives the account list. The terminal screen providing unit 42 requests an authentication information list from the user management unit 44. The user management unit 44 acquires the authentication information of administrators who belong to the same tenant as the logged-in administrator.

[0184] S41: The first communication unit 31 receives the account list, and the display control unit 32 of the terminal device 30 displays the administrator's user name, etc., in a selectable manner in the user name selection field 332(C). The administrator sets the administrator to be used in the shared app. In the case of a personal collaboration source app, this setting is not necessary because the authentication information of each individual is used.

[0185] S42: The administrator inputs collaboration information (A), icon display settings (B), settings related to the execution of the collaboration source application (C), and scan settings (D) into the collaboration source application setting screens (1) 330 to (4) 360. The operation reception unit 33 of the terminal device 30 receives the input.

[0186] If the source application is for "Register New Record," the above completes the setup. However, if the source application is for "Register Existing Record," the user will be registering image data into an existing record in the table of the destination application, so the initial value for which record to register is set in steps S43 to S50.

[0187] S43: The administrator performs an operation to obtain a record list, and the operation receiving unit 33 of the terminal device 30 receives the operation. The first communication unit 31 specifies the linked application ID and transmits a record list request to the terminal screen providing unit 42. The record list may be requested without any operation by the administrator.

[0188] S44: The terminal screen providing unit 42 receives the record list request. The terminal screen providing unit 42 sends the record list request to the input / output processing unit 48 by specifying the linked application ID.

[0189] S45: The input / output processing unit 48 designates the logged-in administrator (or user) and requests the authentication processing unit 51 for authentication information of the external service system 40.

[0190] S46: The authentication processing unit 51 acquires, from the user management unit 44, the authentication information of the external service system 40 associated with the administrator.

[0191] S47: The input / output processing unit 48 designates the authentication information of the external service system 40 and the linked application ID, and requests the external service processing unit 52 to acquire a record list.

[0192] S48: The external service processing unit 52 specifies the authentication information (subdomain, user name, password) and the linked application ID, and acquires a record list from the external service system 40. Note that it is preferable that the field code specified by the administrator in step S42 is transmitted to the external service system 40, and in this case, it is preferable to acquire a record list of the field specified by the field code.

[0193] S49: The record list is transmitted to the terminal device 30, and the display control unit 32 of the terminal device 30 displays the record list. The coordination source application setting screen on which the record list is displayed will be described with reference to FIG.

[0194] S50: The administrator sets an initial value for which record the scanned image data is to be registered from the record list. The operation reception unit 33 of the terminal device 30 receives the setting.

[0195] S50-2: When the administrator performs a process to save the information set on the source application setting screen, the operation receiving unit 33 receives it, and the first communication unit 31 transmits the link information (A), icon display settings (B), settings related to the execution of the source application (C), and scan settings (D) to the terminal screen providing unit 42.

[0196] S50-3: The terminal screen providing unit 42 receives the link information (A), the icon display settings (B), the settings related to the execution of the link source application (C), and the scan settings (D). The terminal screen providing unit 42 sets these in the application data management unit 41 or the application management unit 49, so that the application data management unit 41 sets these in the application data, and the application management unit 49 sets these in the application processing information and the screen information. As a result, the link source application of the information processing system 10 and the link destination application of the external service system 40 are associated with each other.

[0197] FIG. 33 is an example of a coordination source application setting screen 370 having a record setting field. This coordination source application setting screen 370 has a record ID field 353. When the administrator presses record ID field 353, the coordination source application setting screen 370 displays a list of records. In FIG. 33, since "2" is specified in field code field 352, a list of customer names is displayed as a record list in record ID field 353. For example, in the example of FIG. 11, "Osaka Umeko" and "Umeda Taro" are displayed. When the administrator selects a record, the record ID is displayed in record ID field 353 corresponding to the selected record. The set record ID is set as the default storage destination for data acquired by the coordination source application in the "Register Existing Record" screen information.

[0198] With this setting, on the device 20, the "customer name" (such as "Osaka Umeko" or "Umeda Taro") of the record with the record ID set in the record ID column 353 is displayed as the initial value of the data storage destination. Also, in the field code column 352, it is possible to display a list of field codes by associating each field code with a field name using the field code and field name obtained from the linked application. The administrator can specify a field code from the displayed list of field codes. The display setting column 354 specifies the display method of the record list.

[0199] When storing associated information other than the data acquired by the coordination source application in the coordination destination application, the coordination source application setting screen 370 accepts the designation of a field for storing the associated information in addition to the designation of a field for storing the data acquired by the coordination source application. The associated information is data other than image data, such as scan data, fax data, and attachment data, acquired by the coordination source application, and is, for example, information such as the user name of a user who logs into the service providing system from the device 20, the affiliation information of the logged-in user, a fax number, and the date and time of reception. In this case, the field code column 352 of each associated information may be displayed on the coordination source application setting screen 370, and the designation of the field code may be accepted from the administrator.

[0200] In addition, the link source app of "new record registration" can also store the associated information in the link destination app. In this case, the field code column 352 of each associated information may be displayed on the app setting screen of the link source app of "new record registration" and the field code may be specified by the administrator.

[0201] <Example of device screen display> As described above, the registration of the link destination application in the external service system 40, the acquisition of the link destination application ID, and the setting of the link source application in the information processing system 10 are completed, so the user can operate the device 20 to execute the link source application. Next, several screens that the device 20 displays when the user operates the device 20 will be described. This phase is one of the execution phases described in FIG. 1. This phase is also performed by the user on the customer side.

[0202] The user can select a link source application and perform some simple settings such as a file name. The user operates the device 20 to display a link source application list screen. The screens in the following Figs. 34, 35, and 37 are displayed by the device 20 when the device 20 transmits an HTTP request to the information processing system 10 and the information processing system 10 transmits the screen information in the HTTP response.

[0203] 34 is an example of a coordination source application list screen 380 displayed by the device 20. As described above, the device 20 can communicate with one or more external service systems 40 via the information processing system 10 and coordinate with the services (customized coordination destination applications). When the user selects one external service system 40, the application management unit 49 of the information processing system 10 acquires the coordination source application associated with the external service system 40 and transmits to the device 20 screen information of the coordination source application list screen 380 on which the icon of each coordination source application is displayed.

[0204] 34 has six icons 381-386 corresponding to six coordination source applications. One of them is a “new record registration” icon 381. When a user presses the “new record registration” icon 381, a notification to that effect is transmitted to the information processing system 10, and the application management unit 49 of the information processing system 10 acquires screen information 54 associated with the coordination source application ID of the “new record registration”, and the device screen providing unit 47 generates screen information of a setting screen for the “new record registration”, and transmits the screen information to the device 20.

[0205] Fig. 35 is an example of a "New Record Registration" settings screen 390 displayed by the device 20. The "New Record Registration" settings screen 390 has a file name field 391, a calendar field 392, a dictionary field 393, a read settings field 394, and a start button 395. The link source application in Fig. 35 is "New Record Registration", so the user cannot select a record in this settings screen. File name field 391: The file name set in the file name field 343 in Fig. 29 is automatically displayed. In Fig. 35, it is today's date. Calendar field 392: Displays the text set in the date label field 344 in Fig. 29. The calendar field 392 has a Today button and a Calendar button. The Today button enters today's date in the file name field 391, and the Calendar button displays a calendar. Dictionary field 393: The dictionary set in the dictionary designation field 349 in Fig. 30 is displayed. When a dictionary is pressed, the corresponding characters such as "design" are input into the file name field 391. Read setting field 394: Displays the read settings set in the scan settings (D) in Fig. 31. The user can press a read setting button 394A to change the contents set in the scan settings (D). Start button 395: A button for the user to start execution of the link source application "Register New Record."

[0206] <<Operation procedure until the device executes the linking app>> FIG. 36 is an example of a sequence diagram illustrating a procedure in which the user operates the device 20 to cause the device 20 to display the coordination source application list screen 380 and execute a coordination source application selected by the user.

[0207] S51: The user performs an operation to select a desired coordination source application from the coordination source application list screen 380. The following description will be given assuming that the user selects "Register Existing Record" 382 from the coordination source application list screen 380.

[0208] S52: When the operation reception unit 23 of the device 20 receives a selection operation of the coordination source application, the second communication unit 21 requests the application data management unit 41 of the information processing system 10 to acquire application data (space ID, coordination destination application ID, field code, etc.). The space ID is not necessary. The coordination source application ID specifies which coordination destination application the image data, etc. is to be saved in. The field code specifies which field of the coordination destination application the image data, etc. is to be saved in.

[0209] S53: The first communication unit 31 designates the coordination source application ID of the coordination source application selected by the user and requests the device screen providing unit 47 to display a setting screen for “register existing record”.

[0210] S54: The device screen providing unit 47 receives the request for the setting screen of “Register Existing Record.” The device screen providing unit 47 designates the coordination source application ID and requests the application management unit 49 for the setting screen of the coordination source application.

[0211] S55: The application management unit 49 acquires screen information identified by the cooperation source application ID from the application processing information storage unit 17, and transmits it to the device screen providing unit 47. This enables the device screen providing unit 47 to generate a setting screen for “register existing record”.

[0212] S56: Since the selection is "Register existing record", the terminal device 30 acquires information about the records from the information processing system 10 so that the user can select a record. The second communication unit 21 specifies the space ID, the coordination target application ID, and the field code, and transmits a record list acquisition to the coordination source application execution unit 46. The space ID is not necessary.

[0213] S57: The coordination source application execution unit 46 designates the space ID, the coordination destination application ID, and the field code, and requests the input / output processing unit 48 to acquire a record list.

[0214] S58: The input / output processing unit 48 requests the authentication processing unit 51 for authentication information of the logged-in user (whose user name is known).

[0215] S59: The authentication processing unit 51 acquires the authentication information of this user (sub-domain, user name, password) from the user management unit 44.

[0216] S60: The input / output processing unit 48 specifies the authentication information, the space ID, the cooperation source application ID, and the field code, and requests a record list from the external service processing unit 52. The space ID and the field code are not necessary. If there is no field code, all fields are acquired.

[0217] S61: The external service processing unit 52 is authenticated by the authentication information, and requests a record list from the external service system 40 by specifying the linked application ID and the field code.

[0218] S62, S63: The record list is sent to the device 20, and the user can select a record to which the image file is to be registered. The initial value of the record is set, so the user does not need to make a selection. The displayed record list is shown in FIG.

[0219] S64: Next, the user executes scanning by pressing the start button 395. The image data generating unit 24 of the device 20 scans the document and generates image data.

[0220] S65: The second communication unit 21 of the device 20 transmits to the coordination source application execution unit 46 the image data, the coordination destination application ID, the field code, and the record ID.

[0221] S66: The coordination source application execution unit 46 designates the image data, the coordination destination application ID, the field code, and the record ID, and requests the input / output processing unit 48 to execute the coordination source application.

[0222] S67, S68: The input / output processing unit 48 acquires, via the authentication processing unit 51, the authentication information of the logged-in user.

[0223] S69: The input / output processing unit 48 sets the linked application ID, the field code, and the record ID in the parameters of the application processing information, and transmits the image data to the external service processing unit 52 together with the authentication information.

[0224] S70: The external service processing unit 52 is authenticated by the authentication information, and transmits the linked application ID, field code, and record ID set in the parameters of the application processing information, as well as the image data, to the external service system 40. This enables the data processing unit 63 to register the image data in the record specified by the record ID in the field specified by the field code of the linked application specified by the linked application ID.

[0225] 36, the device 20 passes the application data of the coordination source application via the coordination source application execution unit 46, but if there is no change in parameters (if what is set on the coordination source application setting screen is sent as is to the external service system), the input / output processing unit 48 may directly refer to the application data associated with the coordination source application ID from the application data management unit 41. In terms of the sequence, the coordination source application execution unit 46 requests the input / output processing unit 48 to perform processing, but the processing may be performed via the application data service unit 11.

[0226] FIG. 37 is an example of a record list displayed by device 20. FIG. 37 is a part of the settings screen for "Register Existing Record." FIG. 37 shows a case where the "Customer Name" field is set in the field code, and a list of "Customer Names" (list of records) is displayed. FIG. 37 shows eight "Customer Names" on one screen. "Customer Names" that cannot be displayed are displayed when the user switches pages using page switching button 371. Currently, the second of four pages is displayed. Field name 372 shows the field name that corresponds to the field code set on the link source app settings screen.

[0227] If a "Customer Name" is not displayed (the list is blank), this is because the "Customer Name" has not yet been registered in the external service system 40. In other words, image data has been registered by executing "Register New Record", and the record itself exists, but the "Customer Name" has not been registered.

[0228] From this list, the user can select a record in which to save image data. Therefore, the device 20 that executes the coordination source application can display a setting screen for the record, and can perform settings related to the external service system to be used.

[0229] Immediately after the device 20 displays the record list, the record set in the record ID column 353 in FIG. 33 is set.

[0230] 37, since the field code of the application data set on the coordination source application setting screen is specified, a record list of a certain field is displayed, but a field list of all fields may be displayed. Also, the user may select a field from this field list, and the device 20 may request a record list of the field from the information processing system 10.

[0231] <Other settings on the link source app settings screen> FIG. 28 etc. have described the setting of the coordination destination application ID, field code, or record ID on the coordination source application setting screen. Next, other settings that the administrator or the like can perform on the coordination source application setting screen will be described.

[0232] Fig. 38 is an example of a sequence diagram in which the terminal device 30 displays the name of a link destination application of the external service system 40. The process of Fig. 38 is performed following or as part of the link source application setting screen of Figs. 28 to 31. This process is effective in cases where an administrator wants to confirm which link destination application the link source application ID belongs to.

[0233] S81: The administrator inputs the space ID and the link destination application ID of the link destination application of the external service system 40. The operation reception unit 33 of the terminal device 30 receives the input. Note that the space ID is not necessarily required.

[0234] S82: The first communication unit 31 of the terminal device 30 requests the terminal screen providing unit 42 to provide the application name by specifying the space ID and the application ID of the link destination application.

[0235] S83: The terminal screen providing unit 42 receives the request for the application name. The terminal screen providing unit 42 requests the application name from the input / output processing unit 48 by specifying the space ID of the link destination application and the link destination application ID.

[0236] S84, S85: The input / output processing unit 48 acquires the authentication information of the logged-in administrator from the user management unit 44 via the authentication processing unit 51 (sub-domain, user name, password).

[0237] S86, S87: The input / output processing unit 48 is authenticated with the authentication information via the external service processing unit 52, and obtains the application name of the linked application from the external service system 40 using the specified linked application ID (or space ID, if necessary).

[0238] S88: The application name is transmitted to the terminal device 30. The display control unit 32 of the terminal device 30 displays the application name of the cooperation destination application.

[0239] When the terminal device 30 can display the application name of the link destination application in this manner, the administrator can confirm which link destination application the link source application ID belongs to.

[0240] <<Displays whether the user has permission to use the linked app specified by the administrator or user>> Fig. 39 is an example of a sequence diagram in which the terminal device 30 displays whether or not the user has the authority to use the link target application. The process in Fig. 39 is performed following or as part of the link source application setting screen in Fig. 28 to Fig. 31. Such a confirmation is effective because the link source application cannot be executed even if the information processing system 10 links with a link target application that the user does not have the authority to use.

[0241] S91: The administrator or user inputs the space ID and the link destination application ID of the link destination application of the external service system 40. The operation reception unit 33 of the terminal device 30 receives the input. Note that the space ID is not necessary.

[0242] S92: The first communication unit 31 of the terminal device 30 requests the terminal screen providing unit 42 to check the authority by specifying the space ID of the link-destination application and the link-destination application ID.

[0243] S93: The terminal screen providing unit 42 receives the request for checking the authority. The terminal screen providing unit 42 requests the input / output processing unit 48 to check the authority by specifying the space ID of the link destination application and the link destination application ID.

[0244] S94, S95: The input / output processing unit 48 acquires authentication information of the logged-in administrator or user from the user management unit 44 via the authentication processing unit 51. Therefore, the user name of the external service system 40 is known.

[0245] S96, S97: The input / output processing unit 48 is authenticated by the authentication information via the external service processing unit 52, and acquires whether the administrator or the user who has logged in from the external service system 40 has authority for the linked application by specifying the linked application ID (space ID, if necessary) and the user name. The presence or absence of authority is transmitted to the terminal device 30.

[0246] S98: If the authority exists, the display control unit 32 of the terminal device 30 displays a message indicating that the authority exists for the linked application.

[0247] S99: The first communication unit 31 of the terminal device 30 transmits a notice of authority to the application data management unit 41, and stores the notice in association with the link destination application ID and the user name. A user who does not have the authority notice knows that the authority check has not been performed, and a message to that effect can be displayed when the link source application is executed from the device 20.

[0248] S100: If the authority is not granted, the display control unit 32 of the terminal device 30 displays a message indicating that the authority for the cooperation target application is not granted.

[0249] In this way, the fact that the authority exists is stored in the application data management unit 41, and it is known that the user can use the coordination source application that coordinates with the coordination target application. Note that although the authority of the logged-in administrator or user is checked in Fig. 39, the authority of any user may be checked.

[0250] <<Get the field code from the linked app ID and display it as an option>> Fig. 40 is an example of a sequence diagram in which the terminal device 30 displays a field code from a link destination application ID. The process in Fig. 40 is performed following or as part of the link source application setting screen in Fig. 28 to Fig. 31. This process is effective in cases where a list of field codes is displayed when the administrator does not know the field code in which the administrator wants to save image data.

[0251] S101: The administrator inputs the space ID and the link destination application ID of the link destination application of the external service system 40. The operation reception unit 33 of the terminal device 30 receives the input. Note that the space ID is not necessarily required.

[0252] S102: The first communication unit 31 of the terminal device 30 requests the terminal screen providing unit 42 to send a field code list by specifying the space ID of the link destination application and the link destination application ID.

[0253] S103: The terminal screen providing unit 42 receives the request for the field code list. The terminal screen providing unit 42 designates the space ID of the link destination application and the link destination application ID, and requests the input / output processing unit 48 to send the field code list.

[0254] S104, S105: The input / output processing unit 48 acquires the authentication information of the logged-in user from the user management unit 44 via the authentication processing unit 51 (sub-domain, user name, password).

[0255] S106, S107: The input / output processing unit 48 is authenticated by the authentication information via the external service processing unit 52, and acquires a list of field codes of the linked application from the external service system 40 by specifying the specified linked application ID (or space ID, if necessary). The list of field codes is transmitted to the terminal device 30. Since the field name cannot be determined from the field code alone, it is preferable that the field name is also transmitted.

[0256] S108: The display control unit 32 of the terminal device 30 displays the list of field codes.

[0257] S109: The administrator can set, from the field code list, which field code is to be the registration destination of image data, etc.

[0258] Similarly, the administrator can display a list of records in steps S110 to S117.

[0259] S110 to S117: These may be the same as steps S56 to S63 in FIG.

[0260] Fig. 41 shows an example of a list of field codes displayed on the link source application setting screen. As shown in Fig. 41, a list of field names and field codes is displayed. The field code can be selected, and the administrator can select the field code in which he / she wants to save image data, etc. The administrator can specify a field and set the selected field code in, for example, the field code column 337 for image data in Fig. 29. It can also be set for other fields.

[0261] <<Search for linked apps>> Fig. 42 is an example of a sequence diagram showing a procedure in which an administrator searches for a linking application in the external service system 40. The process in Fig. 42 is performed following or as part of the linking source application setting screen in Figs. 28 to 31. This process is effective when an administrator wants to check a linking application. The administrator can display a list of linking applications, etc. Once the linking application is displayed, a list of field codes and a list of records can also be displayed.

[0262] S121: The administrator performs an operation to acquire a space list. The operation acceptance unit 33 of the terminal device 30 accepts the operation, and the first communication unit 31 transmits a request to acquire the space list to the terminal screen providing unit .

[0263] S122: The terminal screen providing unit 42 receives the request for the space list. The terminal screen providing unit 42 transmits a space list acquisition request to the input / output processing unit 48.

[0264] S123, S124: The input / output processing unit 48 acquires the authentication information of the logged-in user from the user management unit 44 via the authentication processing unit 51 (sub-domain, user name, password).

[0265] S125, S126: The input / output processing unit 48 is authenticated using the authentication information, and acquires a space list from the external service system 40. The space list is transmitted to the terminal device 30.

[0266] S127: The display control unit 32 of the terminal device 30 displays the list of spaces.

[0267] S128: The administrator selects the space to which the linked application of which the administrator wishes to view the list from the space list. The operation reception unit 33 of the terminal device 30 receives the selection.

[0268] S129 to S134: The terminal device 30 specifies the space ID of the space selected by the user, and displays a list of applications belonging to this space. This process may be the same as steps S121 to S126, except that the space ID is specified.

[0269] S135: The display control unit 32 of the terminal device 30 displays the application list. At this time, the application name of the linked application, the linked application ID, or both may be displayed. Since the administrator specified the space ID when obtaining the application list, the application list in the space is displayed. If no space is specified, all linked applications are displayed.

[0270] S136: The administrator selects a link destination application from the displayed application list. The operation reception unit 33 of the terminal device 30 receives the selection. For example, the administrator selects a link destination application to be linked with the link source application set by the administrator.

[0271] S137: The first communication unit 31 designates the space ID and the cooperation destination application ID, and transmits a request to acquire a field code list to the terminal screen providing unit 42.

[0272] S138: The terminal screen providing unit 42 receives the request for the field code list. The terminal screen providing unit 42 specifies the space ID and the linked application ID, and transmits a request to obtain the field code list to the input / output processing unit 48.

[0273] S139, S140: The input / output processing unit 48 acquires the authentication information of the logged-in administrator from the user management unit 44 via the authentication processing unit 51 (sub-domain, user name, password).

[0274] S141, S142: The input / output processing unit 48 is authenticated by the authentication information via the external service processing unit 52, and acquires a list of field codes of the linked application from the external service system 40 by specifying the space ID and the linked application ID. It is preferable to also acquire the field name. The list of field codes is transmitted to the terminal device 30.

[0275] S143: The display control unit 32 of the terminal device 30 displays the list of field codes. The field codes, the field names, or both may be displayed.

[0276] S144: The administrator selects a field in which image data is to be registered from the displayed field code list. The operation acceptance unit 33 of the terminal device 30 accepts the selection. As shown in Fig. 41, the selected field code is set in the image data field code column 337.

[0277] S145 to S152: As in steps S56 to S63 in FIG. 36, the terminal device 30 displays a list of records, and the administrator can set initial values ​​for the records.

[0278] In this way, the administrator can display a space list, an application list, a field code list, and a record list, and set a link destination application ID, a field code, a record, and the like, in the link source application.

[0279] <Procedure for registering user names and other information in an external service system when a device executes a linked application> Next, a modified example of the process in which the device 20 executes a coordination source app will be described with reference to Fig. 43. Fig. 43 is an example of a sequence diagram illustrating a procedure in which the user operates the device 20, the device 20 displays a coordination source app list screen, and executes a coordination source app selected by the user. In Fig. 43, when the coordination source app is executed, associated information such as the user name of the user who has logged in to the service providing system to use the coordination source app is automatically transmitted to the external service system 40. Note that the explanation of Fig. 43 will explain the difference from Fig. 36.

[0280] S161: Using the device 20, the user performs a display operation to display a list of coordination source apps that coordinate with "external service system A." The operation acceptance unit 23 of the device 20 accepts the operation, and the second communication unit 21 transmits a request to the application data management unit 41 of the information processing system 10 to acquire a list of coordination source apps by specifying "external service system A." Upon receiving the acquisition request, the application data management unit 41 replies with a list of coordination source apps associated with "external service system A" in the application data storage unit 13. This application list may include apps provided by a service providing system other than the coordination source app associated with "external service system A."

[0281] S162: The second communication unit 21 of the device 20 receives the list of coordination source applications, and the display control unit 22 causes the panel display unit 940a to display a coordination source application list screen. The coordination source application list screen may display a coordination source application ID associated with each coordination source application.

[0282] S163 to S167: These may be the same as S51 to S55 in FIG.

[0283] The following steps S168 to S175 are executed when "register existing record" is selected.

[0284] S168: The user performs an operation to display a list of records to be registered. As an example, a record list screen as shown in Fig. 37 is displayed. The operation acceptance unit 23 of the device 20 accepts the operation.

[0285] S169 to S174: These may be the same as S56 to S61 in FIG.

[0286] S175: The record list is sent to the device 20, and the user can select a record to which the image file is to be registered. The displayed record list may be the same as that shown in FIG.

[0287] S176: Next, the user presses the start button to execute scanning, and the image data generating unit 24 of the device 20 scans the document and generates image data.

[0288] S177: The second communication unit 21 transmits the image data and the record ID (none in the case of "Register new record") to the coordination source application execution unit 46. That is, the second communication unit 21 requests the external service system to store the data (image data) and the associated information (user name). In addition, when the coordination source application is a native application, the data may be transferred directly from the device 20 to the external service system 40.

[0289] S178: The coordination source application execution unit 46 designates the image data and the record ID and requests the input / output processing unit 48 to execute the coordination source application.

[0290] S179, S180: The input / output processing unit 48 acquires, via the authentication processing unit 51, user information of the logged-in user (here, information for identifying the user, such as a user name, may be used).

[0291] S181: The input / output processing unit 48 sets a user name in a parameter of the application processing information. The parameter for setting the user name is determined in advance. The user name is set to "UserName" described in FIG.

[0292] S182, S183: The input / output processing unit 48 acquires the authentication information in the same manner as in steps S67, S68 of FIG.

[0293] S184 : The input / output processing unit 48 sets the linked application ID, the field code, and the record ID in the application processing information, and transmits the authentication information and the image data to the external service processing unit 52 .

[0294] S185: The external service processing unit 52 is authenticated by the authentication information, and transmits the linked application ID, the field code for saving the scan data, the field code for saving the user name, the user name, the record ID, and the image data set in the parameters to the external service system 40. This enables the data processing unit 63 to register the image data in the record specified by the record ID in the field specified by the field code of the linked application specified by the linked application ID. In the case of "register new record", since the record ID is not specified, the data processing unit 63 numbers the record ID and registers the image data in the specified field of the new record. Note that the field code for saving the scan data and the field code for saving the user name are field codes set as the storage destinations of the associated information and data on the link source application setting screen.

[0295] Note that Figure 43 shows a case where the data obtained by the source application is a scan, but the same process can be used when the data obtained by the source application is a fax, and the fax data and associated information can be saved in the destination application.

[0296] <Registering image data received by facsimile to an external service system> The following describes the registration of image data received by facsimile and data other than image data in the external service system 40.

[0297] Fig. 44 is an example of a cooperation source application setting screen 410 of the cooperation source application of "FAX reception registration" displayed by the terminal device 30. Note that the explanation of Fig. 44 mainly explains the differences from Figs. 28 to 31. The cooperation source application setting screen 410 of Fig. 44 has a field code 491 for registering a FAX number, a field code 492 for registering image data, and a field code 493 for registering the reception date and time. · Field code 491 for registering FAX number...The field code in which the FAX number is registered is specified. Field code 492 for registering image data: The field code in which image data received by facsimile is registered is specified. Field code 493 for registering the reception date and time: The field code in which the reception date and time is registered is specified.

[0298] In this way, the administrator can set field codes for image data, FAX numbers, and the like on the coordination source application setting screen 490. This allows the device 20 to register in the external service system 40 not only image data received by facsimile but also data other than image data.

[0299] Data other than image data does not include metadata that is an integral part of image data, but is data that is handled independently of image data. What constitutes data other than image data varies depending on the linked application. Metadata is data that describes the meaning of data. In other words, metadata is data that contains information about certain data. Since it is not the data itself but data about data, it is called meta (higher-level) data. For example, it is data managed by EXIF ​​for JPEG images.

[0300] Next, the cooperation source application setting screen 420 for "Email reception registration" will be described. Fig. 45 is an example of the cooperation source application setting screen 420 for the cooperation source application for "Email reception registration" displayed by the terminal device 30. The cooperation source application setting screen 420 in Fig. 45 has a field code 421 for registering a subject, a field code 422 for registering a body text, a field code 423 for registering a reception date and time, a field code 424 for registering a sender, and a field code 425 for registering an attachment. Field code 421 for registering a subject: A field code in which the subject of an e-mail is registered is specified. Field code 422 for registering the body of the email: The field code in which the body of the email is registered is specified. · Field code 423 for registering reception date and time: A field code in which the reception date and time of the e-mail is registered is specified. · Field code 424 for registering sender: A field code in which the sender of an e-mail is registered is specified. Field code 425 for registering attached files: The field code in which the files attached to the e-mail are registered is specified.

[0301] Therefore, in regard to e-mails, the device 20 can register not only image data received by e-mail, but also data other than image data in the external service system 40.

[0302] <<A process in which, in addition to the image data received by the facsimile processing unit, the administrator sets data other than image data (such as the sender's fax number) on the linking application settings screen, and the device saves the data in a specific field of the linking application when a facsimile is received.>> FIG. 46 is an example of a sequence diagram showing a procedure in which the device 20 receives a facsimile and registers image data and data other than image data in a field of the external service system 40. In FIG.

[0303] S191: The facsimile processing unit 25 receives a facsimile reception notification from the facsimile unit 933.

[0304] S 192 : Upon receiving the reception notification, the facsimile processing unit 25 acquires the image data received from the facsimile unit 933 .

[0305] S193: The facsimile processing unit 25 requests device authentication to the device management unit 45 of the information processing system 10 via the second communication unit 21, and obtains an authentication ticket. Note that the device 20 is registered in advance in the device management unit 45, and the authentication of the device 20 is successful when the device ID, UUID (Universally Unique Identifier), etc. are transmitted.

[0306] S194: The facsimile processing unit 25 specifies the authentication ticket and the source application ID set for itself (which is set in the facsimile processing unit 25 when the source application is installed), and acquires application data (space ID, destination application ID, field code, etc.) and application processing information 53 from the application data management unit 41.

[0307] S195: The facsimile processing unit 25, as shown in FIG. 8, sets the acquired application data (linked application ID, field code) and the FAX number of the sender of the received facsimile in association with the parameters of the application processing information.

[0308] S196: The facsimile processing unit 25 transmits the image data received by facsimile, the link destination application ID, the field code, and the FAX number set in the parameters to the input / output processing unit 48 via the second communication unit 21 of the device 20, and requests the input / output processing unit 48 to execute the link source application. The second communication unit 21 requests the external service system to store the data (image data) and associated information (FAX number).

[0309] S197, S198: The input / output processing unit 48 acquires authentication information of the administrator set in the user name selection field 332 of the coordination source application setting screen from the user management unit 44 via the authentication processing unit 51. The administrator is set in the application data. That is, since it is a shared application, the authentication information of the administrator is used.

[0310] S199: The input / output processing unit 48 transmits to the external service processing unit 52 the image data, the authentication information, the linked application ID set in the parameters, the field code, and the FAX number.

[0311] S200: The external service processing unit 52 receives authentication from the external service system 40 using the authentication information, and transmits to the external service system 40 the linked application ID, field code, FAX number, and image data set as parameters of the application processing information.

[0312] In this manner, the device 20 can register image data and a fax number in a field of the external service system.

[0313] 46, the device 20 acquires application data (space ID, link destination application ID, field code, etc.) in step S194, but it is not necessary to acquire them. In this case, when the link destination application ID of the link source application related to facsimile reception is transmitted to the information processing system 10, the information processing system 10 can identify the link destination application ID, etc. based on the application data.

[0314] <<The device transmits image data and non-image data only from a specific fax number to an external service system>> A method of registering image data and the like only from a specific sender's FAX number or a specific sender of e-mail in the external service system 40 will be described.

[0315] 47 is an example of the cooperation source application setting screen 430 displayed by the terminal device 30. This cooperation source application setting screen 430 is a whitelist of FAX numbers that the device 20 registers in the external service system 40 (data of senders registered in the list is registered in the external service system). The whitelist is stored in the application data storage unit 13.

[0316] When the facsimile processor 25 receives a facsimile, it receives the application data from the information processing system 10, and if the value is in the whitelist, it executes the subsequent processing, and if not, it does not register the data. This allows only image data received from important senders to be registered.

[0317] Alternatively, the component 18 may determine whether the FAX number is registered in the whitelist. Fig. 48 shows a schematic diagram of application processing information for registering image data, etc., from only a specific FAX number in the external service system 40. The determination unit 55, which is the component 18 for determination, analyzes the parameters of the application processing information. That is, by referring to the whitelist, it is determined whether the FAX number set in the parameters of the application processing information is registered in the whitelist. If it is registered, the external service processing unit 52 registers it in the external service system 40, but if it is not registered, for example, the mail sending component 432 sends an email and does not register it.

[0318] In this way, application processing information can be branched according to the sender of the fax or the sender of the email. The sender of the email can be processed in the same way. In addition, characters included in the OCR results of image data received by facsimile or characters included in the email (subject, body) can be compared with a whitelist and processed in the same way.

[0319] 48 simply switches whether or not to save image data, but it is also possible to associate processing contents with characters included in the OCR results of image data received by facsimile or characters included in e-mail, and execute a specified process. Also, the whitelist may be a blacklist (data of senders registered in the list is not registered in the external service system).

[0320] Fig. 49 is an example of a sequence diagram showing a procedure in which the device 20 receives a facsimile and registers image data and data other than image data in a field of the external service system 40 based on the whitelist. The explanation of Fig. 49 will mainly focus on the differences from Fig. 46.

[0321] S196: The input / output processor 48 receives the whitelist included in the application data.

[0322] S198-2: The input / output processing unit 48 designates the FAX number and the whitelist and requests the determination unit 55 to determine whether or not to register the FAX number and the whitelist in the external service system 40. If the determination unit 55 determines that the FAX number and the whitelist should be registered, step S200 is executed.

[0323] <Major Effects> As described above, the service providing system 100 of this embodiment accepts settings (coordination information) for the information processing system 10 to cooperate with the external service system 40 from a coordinating source app setting screen, and when the information processing system 10 accepts a request to execute the coordinating source app from the device 20, it can cooperate with a specific coordinating target app of the external service system 40 in accordance with the settings accepted on the coordinating source app setting screen.

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

[0325] For example, the configuration example in Fig. 5 and the like is divided according to main functions in order to facilitate understanding of the processing by the terminal device 30, the device 20, and the information processing system 10. The present invention is not limited by the manner in which the processing units are divided or the names of the processing units. The processing by the terminal device 30, the device 20, and the information processing system 10 can be divided into more processing units depending on the processing content. Also, it can be divided so that one processing unit includes more processes.

[0326] Additionally, the devices described in the examples are merely illustrative of one of several computing environments for implementing the embodiments disclosed herein. In one embodiment, the information processing system 10 includes a plurality of computing devices, such as a server cluster, configured to communicate with each other via any type of communication link, including a network, shared memory, and the like, and to implement the processes disclosed herein.

[0327] Furthermore, the information processing system 10 can be configured to share the processing steps disclosed in this embodiment, such as those shown in FIG. 24, in various combinations. For example, a process executed by a specific unit can be executed by multiple information processing devices included in the information processing system 10. Also, the information processing system 10 may be integrated into one server device, or may be divided into multiple devices.

[0328] 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 execute each function by software, such as a processor implemented by an electronic circuit, and a device such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), or a conventional circuit module designed to execute each function described above. [Explanation of symbols]

[0329] 10. Information Processing Systems 20 equipment 30 Terminal Equipment 100 Service Delivery System [Prior art documents] [Patent documents]

[0330] [Patent Document 1] JP 2017-076368 A

Claims

1. An information processing system that transmits data related to a first application requested to be executed by a device to an external service system, a setting receiving unit that receives a setting regarding a correspondence between the first application and a second application provided by the external service system; an external service processing unit that transmits identification information and the data of the second application to the external service system when execution of the first application is requested from the device; The external service processing unit designates authentication information of a logged-in user and identification information of the second application received from a terminal device, obtaining from the external service system whether the user has an authority to use the second application; The information processing system according to the present invention, wherein the external service processing unit transmits to the terminal device information indicating whether or not the terminal device has authority to use the second application.

2. the setting reception unit receives, as the setting related to the correspondence, a setting of identification information for identifying the second application, and associates the identification information of the second application with the first application; The information processing system according to claim 1, characterized in that, when the device requests execution of the first application, the external service processing unit transmits the data and identification information of the second application to the external service system.

3. the second application is an application that manages fields and their values ​​in association with each other, the setting reception unit receives a setting of the field in which the data is to be saved, among the fields of the second application; The information processing system according to claim 2, characterized in that when the external service processing unit receives a request from the device to execute the first application, it transmits the data, identification information of the second application, and identification information of the field to the external service system.

4. the setting reception unit receives a setting of identification information of a record in a database managed by the second application; The information processing system according to claim 3, characterized in that when the external service processing unit receives a request from the device to execute the first application, it transmits the data, identification information of the second application, identification information of the field, and identification information of the record to the external service system.

5. The external service processing unit: acquiring a name of the second application from the external service system by specifying the identification information of the second application received from the terminal device, and transmitting the name of the second application to the terminal device; 5. The information processing system according to claim 3, wherein the terminal device displays a name of the second application.

6. the second application is an application that manages fields and their values ​​in association with each other, the external service processing unit specifies the identification information of the second application received from the terminal device and acquires, from the external service system, identification information or a field name of the field that the second application has; the external service processing unit transmits the identification information of the field or the name of the field to the terminal device; 6. The information processing system according to claim 5, wherein the terminal device displays at least one of identification information and a field name of the field.

7. The identification information or the field name of the field displayed by the terminal device can be selected; the terminal device transmits identification information of the field for which the selection has been accepted to an information processing system; the setting reception unit receives a setting of identification information of the field associated with the second application; The information processing system according to claim 6, characterized in that when the external service processing unit receives a request from the device to execute the first application, it transmits the data, identification information of the second application, and identification information of the field to the external service system.

8. the second application is an application that manages a field and its value in association with each other for each record of a database managed by the second application, the external service processing unit acquires a list of the records held by the second application from the external service system by specifying the identification information of the second application and the identification information of the field received from the terminal device; The external service processing unit transmits the list of records to the terminal device; 8. The information processing system according to claim 7, wherein the terminal device displays a list of the records.

9. a selection of a record can be accepted from the list of records displayed by the terminal device; the terminal device transmits identification information of the record for which the selection has been accepted to an information processing system; the setting reception unit receives a setting of identification information of the record in association with the second application; The information processing system according to claim 8, characterized in that when the external service processing unit receives a request from the device to execute the first application, it transmits the data, identification information of the second application, identification information of the field, and identification information of the record to the external service system.

10. the external service system manages the second applications in groups; the external service processing unit, when receiving a request for the list of groups from the terminal device, acquires the list of groups from the external service system; the external service processing unit transmits the list of groups to the terminal device; the external service processing unit acquires a list of the second applications included in the group from the external service system by specifying the identification information of the group received from the terminal device; the external service processing unit transmits a list of the second applications to the terminal device; the external service processing unit specifies identification information of the second application received from the terminal device and acquires a list of the fields included in the second application from the external service system; The external service processing unit transmits the list of fields to the terminal device; the external service processing unit acquires a list of records included in the first application from the external service system by specifying the identification information of the second application and the identification information of the field received from the terminal device; 10. The information processing system according to claim 3, wherein the external service processing unit transmits the list of records to the terminal device.

11. The information processing system according to any one of claims 1 to 10, characterized in that the setting reception unit receives settings regarding correspondence between multiple identical first applications and different second applications from a terminal device.

12. The information processing system according to any one of claims 1 to 10, characterized in that the setting reception unit receives settings regarding correspondence between a plurality of different first applications and the same second application from a terminal device.

13. a communication unit configured to transmit, to the device, identification information of the second application associated with the first application requested by the device based on a setting related to the association; An information processing system according to any one of claims 1 to 12, characterized in that when the external service processing unit receives a request from the device to execute the first application, it transmits identification information of the second application and the data transmitted from the device to the external service system.

14. An information processing system as described in any one of claims 1 to 12, characterized in that when the external service processing unit receives a request from the device to execute the first application, it transmits identification information and the data of the second application that is associated with the first application in the correspondence settings to the external service system.

15. A service providing system including a device and an information processing system that transmits data related to a first application requested to be executed by the device to an external service system, The device comprises: a communication unit that transmits an execution request of the first application to the information processing system; The information processing system includes: a setting receiving unit that receives, from a terminal device, a setting regarding a correspondence between the first application and a second application provided by the external service system; an external service processing unit that transmits identification information and the data of the second application to the external service system when execution of the first application is requested from the device; The external service processing unit designates authentication information of a logged-in user and identification information of the second application received from a terminal device, obtaining from the external service system whether the user has an authority to use the second application; The service providing system according to the present invention, wherein the external service processing unit transmits to the terminal device information indicating whether or not the terminal device has authority to use the second application.

16. 1. An information processing method performed by a service providing system that transmits data related to a first application requested to be executed by a device to an external service system, comprising: a setting receiving unit receiving, from a terminal device, a setting regarding a correspondence between the first application and a second application provided by the external service system; an external service processing unit, when receiving a request from the device to execute the first application, transmitting identification information of the second application and the data to the external service system; the external service processing unit designating authentication information of a logged-in user and identification information of the second application received from a terminal device, and acquiring from the external service system whether or not the user has authority to use the second application; a step of the external service processing unit transmitting to the terminal device information indicating whether or not the terminal device has an authority to use the second application; 13. An information processing method comprising:

17. an information processing system that transmits data related to a first application requested to be executed by a device to an external service system; a setting receiving unit that receives, from a terminal device, a setting regarding a correspondence between the first application and a second application provided by the external service system; functioning as an external service processing unit that, when execution of the first application is requested from the device, transmits identification information of the second application and the data to the external service system; The external service processing unit designates authentication information of a logged-in user and identification information of the second application received from a terminal device, obtaining from the external service system whether the user has an authority to use the second application; The external service processing unit is a program for transmitting to the terminal device information indicating whether or not the terminal device has authority to use the second application.

Images