JP7476572B2 - Service providing system, information processing system, information processing method, and program - Google Patents

Description

The present invention relates to a service providing system, an information processing system, an information processing method, and a program.

There is a known technology called Web applications, which allows a terminal device to use services provided over a network using a Web browser or the like, but it is also possible to use such services from devices such as image forming devices. For example, there is a known service provision system that scans an original document using an image forming device, generates image data, and stores the image data in an external storage service or prints it.

In a service providing system, in order to reduce the burden on users when using services from a device, the user can configure the use of the device in advance (see, for example, Patent Document 1). Patent Document 1 describes a technology in which an information processing system accepts default values for print settings, etc., that a user sets on an application settings screen.

However, conventional service provision systems have the problem of being unable to link with databases. For example, even if conventional service provision systems can store image data in an external storage service, they cannot store, for example, the fax number of a received facsimile or user information using the device in the appropriate items in the database.

In view of the above problems, the present invention aims to provide a service provision system etc. that can be linked to a database.

In view of the above problems, the present invention provides a service providing system including an apparatus and an information processing system that transmits data acquired from the apparatus to an external service system, the system comprising: a setting receiving unit that receives settings of first identification information indicating a storage destination of the data in the external service system, second identification information indicating a storage destination of associated information to be stored in the external service system in association with the data, and an identification information of a second application operating in the external service system; the apparatus has a communication unit that acquires the data and the associated information and requests the information processing system to store the data and the associated information in the external service system according to the settings, the data and the associated information relate to a first application operating in the information processing system that is requested to be executed by the apparatus, and the information processing system has an external service processing unit that transmits the data, the first identification information, the associated information, the second identification information, and the identification information of the second application to the external service system when execution of the first application is requested by the apparatus .

It is possible to provide a service provision system that can be linked to a database.

FIG. 2 is a diagram illustrating the overall operation of the service providing system. FIG. 1 illustrates a system configuration of an example of a service providing system. FIG. 2 is a hardware configuration diagram of an example of an information processing system and a terminal device. FIG. 2 is a diagram illustrating a hardware configuration of an example of an image forming apparatus, which is an example of a device. FIG. 2 is a diagram illustrating a functional configuration of an example of a service providing system. FIG. 2 is a diagram illustrating a functional configuration of an example of an external service system. FIG. 4 is a diagram illustrating an example of application processing information stored in an application processing information storage unit. FIG. 11 is a diagram illustrating another example of application processing information. FIG. 11 is a sequence diagram illustrating an example of a registration process of application processing information. FIG. 13 illustrates an example of an application processing information creation screen. FIG. 13 is a diagram showing an example of a linkage target application registration screen (part 1) displayed on the terminal device; FIG. 13 is a diagram showing an example of a linked application registration screen (part 2) displayed on the terminal device; FIG. 13 is a diagram showing an example of a linkage target application registration screen (part 3) displayed on the terminal device; 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. FIG. 13 is a diagram showing an example of a linked application registration screen (part 4) on which work items are displayed. 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. FIG. 13 is a diagram illustrating an example of a linked application list screen displayed on the terminal device. FIG. 13 is a diagram showing an example of an authority setting screen for authority information for a record. 11 is an example of a sequence diagram illustrating a procedure in which an administrator registers an application in an external service system. FIG. 13 is a diagram showing an example of an initial screen displayed by the terminal device. FIG. 13 is a diagram showing an example of a My Page screen (part 1) displayed on the terminal device. FIG. 13 is a diagram showing an example of a My Page screen (part 2) displayed on the terminal device. FIG. 13 is a diagram illustrating an example of an authentication information setting pop-up screen displayed by the terminal device. 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 is able to log in to the external service system. 11 is an example of a sequence diagram illustrating a procedure in which an administrator registers authentication information in an information processing system. FIG. 13 is a diagram showing an example of an initial screen displayed by the terminal device. FIG. 11 is a diagram showing an example of a service selection screen displayed by the terminal device. FIG. 11 is a diagram illustrating an example of a cooperation source application selection screen displayed on the terminal device. 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. FIG. 13 is a diagram illustrating an example of a coordination source application setting screen (part 2) displayed on the terminal device. FIG. 13 is a diagram illustrating an example of a coordination source application setting screen (part 3) displayed on the terminal device. FIG. 13 is a diagram showing an example of a coordination source application setting screen (part 4) displayed on the terminal device. 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. FIG. 13 is a diagram illustrating an example of a coordination source application setting screen having a record setting field. FIG. 13 is a diagram illustrating an example of a cooperation source application list screen displayed on the device. FIG. 13 is a diagram showing an example of a “new record registration” setting screen displayed by the device. FIG. 13 is a diagram showing an example of a setting screen for "register new record" that is displayed when the transition button is pressed. 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. FIG. 13 illustrates an example of a record list displayed by a device. 11 is a sequence diagram illustrating an example of a terminal device displaying a name of a linked application in an external service system. 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. 11 is a sequence diagram illustrating an example of a process in which the terminal device displays a field code based on a cooperation destination application ID. 13 is a diagram showing an example of a list of field codes displayed on a coordination source application setting screen. FIG. 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. 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. FIG. 13 is a diagram illustrating an example of a linked application registration screen on which a case manager is registered. 13 is a diagram illustrating an example of a cooperation source application setting screen of a cooperation source application of “FAX reception registration” displayed on the terminal device. FIG. 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. 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. FIG. 13 is a diagram illustrating an example of a coordination source application setting screen displayed on the terminal device. 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. 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.

Below, a service providing system and an information processing method executed by the service providing system will be described as an example of a form for implementing the present invention.

<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 coordination source application (an example of a first application, hereinafter referred to as a coordination source app) and a coordination destination application (an example of a second application, hereinafter referred to as a coordination 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 coordination source app and the coordination source app cooperates with the coordination destination app.

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 or organization 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 also subscribe to the service individually. When subscribing to a service individually, the user himself/herself inputs settings to associate the source app with the destination app on the source app settings screen.

Regarding the processing performed by the administrator, some processing may be performed by personnel such as vendors or dealers who encourage tenants to subscribe to the services provided by the service providing system 100 or who sell the applications provided by the service providing system 100. In addition, there may be cases where the processing performed by the administrator can be performed by users.

(1) The administrator causes the terminal device 30 to communicate with the external service system 40 and displays a linked 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). The overall content of the functions provided by this service is fixed, but the administrator can customize the service to use it as a desired linked application. In other words, a part (or the entirety) of the functions of the service becomes the linked application.

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

(3) The external service system 40 assigns a linked application ID (an example of identification information of a second application) that identifies the linked application to the linked application and transmits it to the terminal device 30. The terminal device 30 displays the linked application ID, so that the administrator can know the linked application ID. Note that in the embodiment described below, the administrator can cause the terminal device 30 to display the linked application ID via the information processing system 10.

(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 app 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 apps executed by devices such as image forming devices. The information processing system 10 links with link destination apps of an external service system 40 to provide services to users. The information processing system 10 can link with various external service systems 40, and further links with various link destination apps provided by an external service system 40, thereby enabling the information processing system 10 to provide a variety of services to users. As explained in FIG. 1(b), this service is used as a link source app by devices such as image forming devices.

(5) The administrator sets the link information including the link destination application ID on the link source application setting screen. The link information is information for the information processing device system to link with a link destination application registered in the external service system 40. In addition to the link destination application ID, a field code is set. When the link destination application is an application that operates a database, the field code is identification information that identifies a field. In other words, it is identification information of an item managed by an application provided by the external service system. The administrator can specify a field code for each data to be registered in the external service system, such as a field code for image data or a field code for a fax number. 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 in the information processing system 10.

(6) Through the above process, the information processing system 10 is now in a state in which it can link with the linked application of the external service system 40 using the linked application ID. In addition, the information processing system 10 can obtain the value of a specific field from the external service system 40 using the field code.

(7) For example, a facsimile receiving function of the device 20 receives a facsimile. An application that performs processing related to the facsimile (a facsimile processing unit described later) requests the information processing system 10 to execute a cooperation source application associated with the application. The cooperation source application performs, for example, the following processing.
(i) Transmitting the received image data and FAX number to the information processing system 10
(ii) The information processing system 10 transmits a processing request for the image data and the FAX number to the external service system 40.

(8) The facsimile processing unit specifies the linked application associated with the application, and obtains the linked application ID and field code, etc., set for the linked application from the information processing system.

(9) The device 20 sends the image data, the linked application ID, the field code, and the fax number, etc. to the information processing system 10.

(10) The information processing system 10 specifies the linked application ID and the field code and sends a processing request for the image data and the fax number to the external service system 40. This allows the link source application to link with the linked application.

(11) The external service system 40 accepts the image data and the fax number as targets for processing in a field identified by a field code of a linked application identified by a linked application ID. For example, the external service system 40 stores the data in the field.

When image data or a fax number becomes a processing target of a linked application, it means that it is processed by the linked application. Therefore, the content of the processing varies depending on the linked application. For example, the data may be converted into a data format that the linked application can process, the image data or fax number may be assigned some attribute and stored in a state where the type of image data or the fax number is managed, image processing may be performed on the image data, the data may be transferred externally, or the 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 data into a data format, assign some attribute to the image data and store the data in a state where the type of image data is managed, perform image processing on the image data, etc., and then transfer the processed image data to the linked application.

In this manner, the service providing system 100 of this embodiment accepts settings (linkage information) for the information processing system 10 to link with the external service system 40 from the linkage source app setting screen. When the device 20 receives a facsimile or the like, the linkage source app associated with the facsimile receiving function is executed, and the device 20 can transmit not only image data but also fax numbers and other data to the information processing system 10. The information processing system 10 saves data other than image data in a specific field of a specific linked app of the external service system 40 according to the settings accepted on the linkage source app setting screen, and can request appropriate processing of this data.

<Terminology>
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.

An application is often used to manipulate data in a database. In this embodiment, the linked application operates the database. Operation includes storing, searching, and updating information.

The data transmitted by the service providing system includes not only data transmitted from the device (image data, fax numbers, etc.), but also data held by the information processing system (user names, etc.).

Collaboration refers to two or more parties working together to execute a process. In this embodiment, collaboration refers to a collaboration source app of the information processing system 10 working together with a collaboration destination app of the external service system 40, and the information processing system 10 providing a service.

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 in a database.

A field refers to a column of tabular data held by the linked application, and shows each column in the table in Figure 11.

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

The link source application is an application by which the information processing system 10 provides 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. In addition, 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.

The information processing system 10 provides a service, and one of the means for providing the service is the execution of a linking source app. When the linking source app is executed, it may (or may not) link with a linking destination app provided by the external service system 40. The service provided by the linking source app is realized by executing a series of processes in order, so the content and order of the series of processes are defined in the linking source app.

The external service system 40 also provides services, and one of the means of providing the services is the execution of a linked application. The external service system 40 can provide services to users 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 makes it possible for a user to use a linked application of the external service system 40, which can be used by a user from a terminal device 30 or the like, from the device 20 via the information processing system 10.

The services of the external service system 40 may be called linked apps (applications) or may be called programs, software, sites, etc. In other words, the linked apps do not need to be called applications as long as they are related to the services of the external service system 40.

The user refers to a so-called end user on the customer side, and is a person who uses the device 20 including the link source app. The administrator is a person who registers the link destination app and the link source app so that the user can use the link source app, 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 merely for convenience.

<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 an example of the system configuration of the service providing system 100 according to this embodiment.

The service providing system 100 shown in FIG. 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.

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 the series of processes is provided by a single coordinating source app, and the series of processes is also referred to as a "processing flow" or "workflow".

The device 20 is various electronic devices used by the 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 device 20 is connected to the network N2. The user can use the device 20 to utilize various services provided by at least one of the information processing system 10 or the external service system 40.

Note that hereafter, when multiple devices 20 are to be distinguished from one another, they will be referred to using subscripts such as "device 201" and "device 202."

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 terminal device 30 is connected to the network N2. 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 linked app or a linked source app.

In the following description, when distinguishing between the multiple terminal devices 30, they will be referred to using subscripts such as "terminal device 30 ₁ " and "terminal device 30 ₂ ".

The external service system 40 is one or more information processing devices that provide services by executing linked applications via the network N1. Data is managed or processed by executing linked applications, and the data itself or the results of the processing become the services.

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

In the following description, when distinguishing between the multiple external service systems 40, the illustrated "external service system 40 ₁ " will be referred to as external service system A, the "external service system 40 ₂ " will be referred to as external service system B, etc.

<Hardware configuration example>
The hardware configuration 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.

<<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, a HD 504, a 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.

Of these, the CPU 501 controls the overall operation of the information processing system 10 and the terminal device 30. The ROM 502 stores programs used to drive the CPU 501, such as IPL. The RAM 503 is used as a work area for the CPU 501. The HD 504 stores various data such as programs. The HDD controller 505 controls the reading or writing of various data from the HD 504 according to the control of the CPU 501. The display 506 displays various information such as a cursor, menu, window, character, or 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.

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

＜＜Equipment＞＞
Fig. 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.

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, a HDD controller 908, and a 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.

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

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

SB904 is a bridge for connecting NB903 with PCI devices and peripheral devices. ASIC906 is an IC (Integrated Circuit) for image processing applications that has hardware elements for image processing, and acts as a bridge connecting AGP bus921, PCI bus922, HDD controller908, and MEM-C907. This ASIC906 is composed of a PCI target and AGP master, an arbiter (ARB) that is the core of ASIC906, a memory controller that controls MEM-C907, multiple DMACs (Direct Memory Access Controllers) that rotate image data using hardware logic, and a PCI unit that transfers data between scanner unit931, printer unit932, and facsimile unit via PCI bus922. In addition, a USB (Universal Serial Bus) interface or an IEEE 1394 (Institute of Electrical and Electronics Engineers 1394) interface may be connected to the ASIC 906.

MEM-C907 is a local memory used as an image buffer for copying and a code buffer. HD909 is a storage for storing image data, font data used during printing, and forms. HD909 controls the reading and writing of data from and to HD909 under the control of CPU901. AGP bus921 is a bus interface for a graphics accelerator card proposed to speed up graphic processing, and by directly accessing MEM-P902 with high throughput, the graphics accelerator card can be made faster.

The short-range communication circuit 920 also includes a short-range communication circuit antenna 920a. The short-range communication circuit 920 is a communication circuit such as NFC or Bluetooth (registered trademark).

The engine control unit 930 further includes a scanner unit 931, a printer unit 932, and a facsimile unit 933. The operation panel 940 includes a panel display unit 940a, such as a touch panel, that displays current settings and selection screens and receives input from the operator, and hard keys 940b, such as a numeric keypad that receives settings for image formation conditions such as density settings and a start key that receives a copy start command. The controller 910 controls the entire image forming apparatus, and controls, for example, drawing, communication, and 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.

The image forming device can sequentially switch between 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 device enters document box mode, when the copy function is selected, the device enters copy mode, when the printer function is selected, the device enters printer mode, and when the facsimile mode is selected, the device enters facsimile mode.

The network I/F 950 is an interface for 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 the PCI bus 922.

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

＜＜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).

The second communication unit 21 transmits and receives various information to and from the information processing system 10. In this embodiment, it receives screen information of the collaboration source app list screen from the information processing system 10, and transmits image data, collaboration information, and the like to the information processing system 10.

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

When the link source app 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 requests the information processing system 10 to execute the link source app that has been associated in advance when a facsimile is received. Note that a link source app that corresponds to the sender of the facsimile (fax number) may be requested.

The email processing unit 26 performs processing related to sending and receiving emails, and when an email is received, it requests the information processing system 10 to execute a pre-associated link source app. It is also possible to request a link source app that corresponds to the sender (email address) of the email.

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

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, it 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 the administrator or user to the information processing system 10 or the external service system 40.

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

<<Information Processing System>>
The information processing system 10 includes 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 "coordination source application" executed in the information processing system 10.

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 (e.g., a link 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 link source application setting screen, etc., that allows an administrator to set information required for executing the link source application. In response to an HTTP request from the terminal device 30, the terminal screen providing unit 42 generates screen information written in HTML, XML, CSS (Cascade Style Sheet), JavaScript (registered trademark), etc., and transmits the screen information to the terminal device 30 as an HTTP response.

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

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

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 each process included in the coordination source application to the component 18. 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 is set to indicate which process the coordination source application performs and in what order (for example, requesting processing from the external service system 40 after OCR). The screen information 54 is information on the 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 screen information 54 for each coordination source application.

The authentication service unit 14 performs processes related to authentication of users (including administrators) 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 user names and passwords. The authentication information includes information from the information processing system 10 and information from 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 tenants in association with the devices 20, and when the device 20 is identified, the tenant is also identified.

Component 18 is a collective term for the 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.

表１は、アプリ処理情報記憶部１７が保持する情報の一例を示す。アプリ処理情報記憶部１７は外部サービスシステム４０に対応付けられており、連携元アプリＩＤ（第一のアプリケーションの識別情報の一例）、アプリ名、画面情報、アプリ処理情報、及び、共有アプリの各項目を有している。連携元アプリＩＤは連携元アプリを識別する識別情報である。アプリ名は管理者が付与した連携元アプリの名称である。また、連携元アプリのアイコンや設定画面を機器２０が表示する際に使用される画面情報５４（ＨＴＭＬ等で記述された）が連携元アプリに対応付けられる。連携元アプリには一連の処理の内容と順番（処理フロー）が定義されるので、各連携元アプリにはアプリ処理情報５３が対応付けられる。共有アプリとは、一般の連携元アプリがユーザごとに利用権限が与えられるのに対し、共有アプリはテナントのユーザが共通に使えるアプリであることを示す。表１ではメール受信登録とＦＡＸ受信登録が共有アプリである。これらは各ユーザが利用するためである。

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 each item of the coordination source application ID (an example of identification information of a first application), 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 in the coordination source application, each coordination source application is associated with application processing information 53. The shared application indicates that, while a general coordination source application is given a usage authority for each user, the 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.

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

表２はユーザ管理部４４が管理するユーザに関する情報の一例を示す。ユーザに関する情報として、情報処理システム１０におけるユーザＩＤ、ユーザ名、メールアドレス、パスワード、利用できる連携元アプリ、外部サービスシステムの認証情報、及び、連携設定の各項目を有している。このユーザには管理者も含まれる。ユーザＩＤ、ユーザ名又はメールアドレスの少なくとも１つと、パスワードは、ユーザが情報処理システム１０にログインするための認証情報である。利用できる連携元アプリはこのユーザに利用権限が与えられている連携元アプリである。利用できる連携元アプリには個人アプリと共有アプリがある。個人アプリも共有アプリも複数のユーザに使用されるが、個人アプリは個人のユーザの外部サービスの認証情報を使用し、共有アプリは複数のユーザが共有で外部サービスの認証情報を使用する。表２では、U001～U003に共通のapp003が共有アプリである。その他は個人アプリである。個人アプリの場合、ユーザごとに外部連携サービスの認証情報の登録が必要である。

Table 2 shows an example of information about a user managed by the user management unit 44. The information about the user includes the user ID, user name, email address, password, available link source application, authentication information of the external service system, and each of the link settings in the information processing system 10. The user includes an administrator. At least one of the user ID, user name, and email address, and the password are authentication information for a user to log in to the information processing system 10. The available link source application is a link source application for which the user has been granted usage authority. The available link source applications include personal applications and shared applications. Both personal applications and shared applications are used by multiple users, but the personal application uses authentication information of an external service for a personal user, and the shared application uses authentication information of an external service shared by multiple users. In Table 2, app003, which is common to U001 to U003, is a shared application. The others are personal applications. In the case of a personal application, it is necessary to register authentication information for an external link service for each user.

The authentication information of the external service system is authentication information for a user to log in to the external service system 40. The authentication information may differ for each external service system 40. In this way, each user of the service providing system 40 and the user of the external service system 40 are associated one-to-one. It is not necessary to link them one-to-one, and when there are multiple link source applications that use the same external service system 40, users of different external service systems 40 may be associated with each application. Therefore, the information processing system 10 identifies a user (user identification information, etc.) of the linked external service system 40 according to user information such as the user ID and password of the information processing system 10 acquired from the device 20. Alternatively, the user of the linked external service system 40 is identified according to the user information of the information processing system 10 and the link source application. The link setting item becomes "done" when it is confirmed that the user wishes to link with the external service system 40 and can log in with the authentication information of the external service system 40. The link setting is used to determine whether the user can execute the application of the external service system 40.

The authentication information may be authentication information of the external service system 40 or authentication information required for linking with the external service system, and may be a token obtained from the external service system 40 when linking with the external service system 40, in addition to a user ID and password.

表３は、アプリデータ記憶部１３に記憶されているアプリデータの一例を示す。アプリデータは、外部サービスシステム４０に対応付けて、連携元アプリＩＤ、連携先アプリＩＤ、スペースＩＤ、連携元アプリ設定画面、及び、ｎ個（１つ以上）のフィールドコードの各項目を有している。つまり、アプリデータは連携元アプリと連携先アプリを対応付ける。連携元アプリ設定画面の項目は連携元アプリが設定される上記の連携元アプリ設定画面の画面情報を指定する情報である。各フィールドコードは、連携先アプリのどのフィールドにどのデータを保存するかを特定する情報である。例えば、スキャンした画像データはフィールドコード１のフィールドに格納することが登録されている。なお、フィールドとは項目であり、表形式のデータベースではカラムに相当する。

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. In other words, the application data associates a coordination source application with a coordination destination application. The items of the coordination source application setting screen are information that specifies screen information of the coordination source application setting screen in which the coordination source application is set. Each field code is information that specifies 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.

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

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 linking 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, the API (Application Interface) of the external service system 40 is used.

The app registration reception unit 64 provides a linked app registration screen to the terminal device 30 and accepts registration and editing of linked apps set by the administrator on the linked app registration screen. The administrator can register linked apps simply by customizing the services provided by the information processing system 10. The app registration reception unit 64 assigns unique linked app IDs to the linked apps. The app registration reception unit 64 stores information related to the registered linked apps in the app information storage unit 65.

The application determination unit 62 determines the linked application that processes the image data, etc., which is the target of the processing request, based on the linked application ID transmitted from the information processing system 10. The data processing unit 63 processes the image data, etc., with processing content specific to the linked application, which is the processing performed by the linked 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 linked application ID and 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 linked application ID, field code, and record ID. In addition, for example, the data is converted into a data format processed by the linked application, the image data is stored in a state in which the type of image data is managed by adding some attribute to the image data, image processing is performed on the image data, the image data is transferred to the outside, and the image data is provided in response to a request. In the following embodiment, a linked application that provides a database in a table format will be described. In this case, the data format is converted, managed, and provided.

表４は、外部サービスシステム４０のアプリ情報記憶部６５に保存されるアプリ情報の一例である。表４のアプリ情報はデータベース形式の連携先アプリに関するものなのでフィールド名のリストである。アプリ情報はスペースＩＤ、連携先アプリＩＤ及び連携先アプリ名に対応付けられている。スペースとはいくつかの連携先アプリをグループ化したものであり、スペースＩＤはその識別情報（グループの識別情報の一例）である。外部サービスシステム４０によってはスペースＩＤがない場合がある。

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.

In Table 4, the field names are Record Number, Customer Name, Phone Number, Case Status, New/Added, Delivery Date, Design Request, Design Proposal, Fixed String, and Numerical Values, but these have been registered by the administrator and are merely examples. Note that "Design Request" is intended to indicate that the user would like 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 that has been revised by an expert.

Each field has a field code. The field code is identification information that identifies the field. Note that some fields may not have a field code, but in this case, it becomes difficult to link by specifying the field. As described below, 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.

The 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 specifies the field code for "design preference" as the field in which to set image data on the link source app setting screen.

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

The application processing information 53A shown in FIG. 7 is information regarding a series of processes for realizing a service that requests "external service system A" to process image data generated by scanning with device 20.

The application processing information 53A includes a flow ID 1201A indicating the 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 linked application.

Furthermore, flow details 1203A includes processing content 1223A indicating that a processing request is to be made to "external service system A."

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 the processing request, and the parameters "AppId", "FieldCode", and "UserName" are specified. The linked application ID is stored in "AppId", the field code is stored in "FieldCode", and the user name (or 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, the record ID is also set as a parameter.

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 this embodiment can transmit linkage information, etc. to the external service system 40 using parameters of the application processing information, and link with the linked application.

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

It includes a flow ID 1201C indicating the 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 processing contents of the series of processes.

Furthermore, flow details 1203C includes processing content 1213C indicating OCR processing, and processing content 1223C indicating distribution (uploading) to "external service system A". Processing content 1213C specifies the component ID "ocr" of component 18 that performs OCR processing, the operation ID "process", and the parameters "language" and "outputType". Processing 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, information processing system 10 can transmit multiple field codes to external service system 40 by specifying which field they belong to.

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

The execution order of the processes defined in each processing content is from top to bottom in flow details 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 limited to the above, and the application processing information may, for example, define information indicating the execution order of the processes defined in each processing content.

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

First, the 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 the process of registering application processing information.

The administrator uses the terminal device 30 to start creating the app processing information. For example, the administrator can start creating the app processing information by logging in to the information processing system 10 using the terminal device 30 and then selecting a "Create app processing information" button or the like on a portal screen or the like that is displayed after the login.

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

S3 to S5: Next, the administrator performs an operation to select a template of the coordination source app for creating app processing information from the app list screen. When the operation acceptance unit 33 of the terminal device 30 accepts the template selection operation, the first communication unit 31 transmits an acquisition request for an app 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 app processing information creation screen to the app management unit 49. As a result, the first communication unit 31 of the terminal device 30 receives screen information of the app processing information creation screen. An example of the app processing information creation screen is shown in FIG. 10.

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

S7, S8: When the administrator creates the application processing information, the first communication unit 31 of the terminal device 30 sends 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 sends the application name, application processing information, and screen information to the application management unit 49. The application management unit 49 numbers 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 sent to the terminal device 30.

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

In addition, in the terminal device 30, the administrator associates the link source application ID with the functions of the terminal device 30. For example, when a link source application that uses a fax reception component is created, an operation is performed to register this link source application ID in the facsimile processing unit 25.

In this way, the source application can be identified from the facsimile processing unit 25, etc. In addition, when the source application is executed from the facsimile processing unit 25, etc., it is not possible to identify the source application to be executed. Therefore, when the source application is released, a unique ID (source application ID) is set in the terminal device 30 and the application data, so that the facsimile processing unit 25 can specify the source application to the information processing system 10.

Figure 10 shows an example of an application processing information creation screen. The application processing information can be set by the administrator by placing 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 the arrow 2003. Figure 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.

<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 linked 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.

When an 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 Figures 11 to 17 are displayed by the terminal device 30 when the terminal device 30 sends an HTTP request to the external service system 40 and the external service system 40 sends the screen information in the HTTP response.

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

For ease of explanation, FIG. 11 displays the field names of linked applications that have already been registered in the information processing system 10. If a new field is to be set, the field name is not displayed, but the method for registering linked applications from FIG. 12 onwards is the same.

In this embodiment, the application ID 212 is displayed in the URL.
https://company.ExService_A.com/2575/
This “2575” is the application ID 212 .

The linked app registration screen (1) 200 displays each of the fields: authority information 214 for each record, the field names shown in the app information in Table 4 (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, numeric value 210), and case manager 213, and a value is set for each field. One line is called a record (an example of a storage location) and is assigned a record number. The user can display and edit the field values using the linked app registration screen (1) 200. In Figure 11, blank spaces are fields for which no value is set (or for which there is no authority to display).

In addition, it is possible to set authorized users for a record. In addition, types of authorization include, for example, viewing authorization, editing authorization, and deletion authorization. If a user has editing authorization, he or she can register or replace image codes or character strings for a record or field. In the authorization information 214, the names of users (identification information) who have the authorization are registered in association with the viewing authorization, editing authorization, and deletion authorization. In FIG. 11, the authorization information 214 can be registered for each record of the linked application, but it is also possible to set the authorization information for each field.

The case manager 213 is the person in charge of the record. It can also be called the administrator. The case manager may be, for example, the user who registered the record. When the record is registered, the user (logged-in user) of the external service system 40 corresponding to the user operating the device 20 is automatically set in the case manager 213 field (see FIG. 46). In addition, the administrator can set the case manager 213 from the linked app registration screen (part 1) 200 in FIG. 11.

When users are managed in groups in the external service system 40, other users in the same group as the registered user may be given one or more of viewing authority, editing authority, and deletion authority. It is also possible to set the app so that the authority for records that match the specified conditions is given to a specified user, as shown in FIG. 18 described later.

When image data is registered in an existing record, the user operating the device 20 may be registered as the case manager. In this case, the user may be added or replaced by the case manager 213.

The linked app registration screen (part 1) 200 has a settings button 211. When the administrator presses the settings button 211, the terminal device 30 displays the linked app registration screen (part 2) 210, allowing the administrator to edit the field name.

12 is an example of a linked application registration screen (part 2) 210 displayed by the terminal device 30. The linked 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 linked 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 the desired form by dragging it from the form column 222 into the work area. This form becomes a field.

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". In other words, the image data is positioned as an attachment 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.

In FIG. 12, the work area 223 displays the names of each field in Table 4 and a column for its value (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.

Figure 13 is an example of a linked app registration screen (part 3) 220 displayed by the terminal device 30 on which the work item 221 is displayed. In Figure 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 displays a details pop-up screen that allows the form to be edited.

14 is an example of a details pop-up screen 230 in which details of a form called an attachment (the "design preference" 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 item," a thumbnail size selection column 234, and a field code column 235.
Field name column 231: The 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 item": When checked, the field name becomes a required item.
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 column 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 column is displayed and an arbitrary field code can be input.

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 reception 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 are no duplicates within the application, the user can set an appropriate field code using letters, numbers, alphabets, etc. or a combination of these. In FIG. 14, "7" is set as the field code (see FIG. 43). The field code is set to uniquely identify the field in the linked application, since there is a possibility that the same field name may be given to different fields.

Similarly, editing of the field code in the numeric field 223C will be described with reference to Figures 15 and 16. Figure 15 is an example of a linked app registration screen (part 4) 220 displayed by the terminal device 30 on which the work items are displayed. In Figure 15, the mouse pointer has been moved to the top right of the numeric field 223C. As a result, the work item 221 is displayed. The user has pressed the edit button 221A.

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.
Decimal point display digits field 243: When there is a decimal point, the number of digits to be displayed is specified.
Unit symbol column 244: A column in which the unit of the 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".

Figure 17 is a diagram showing an example of a linked app list screen 249 displayed by the terminal device 30. The administrator, for example, specifies a space ID to display a list of linked apps. The linked app list screen 249 has items such as app ID 249A and app name 249B. App ID 249A represents the linked app ID. The administrator can also confirm the linked app ID from this screen. If the administrator selects the app name, a linked app registration screen (part 2) 210 as shown in Figure 12 is displayed.

Figure 18 shows an example of a permission setting screen 440 for permission information for a record. The permission setting screen 440 is a screen on which an administrator can specify a record and set permissions for each linked application of the external service system 40. The permission setting screen 440 has a record condition setting field 441 and a permission setting field 442.

The record condition setting field 441 has several items a1 to a3, and conditions can be set according to the field. In FIG. 18, "Delivery date" is specified as a field in item a1. This "Delivery date" is set in the delivery date 206 on the linked application registration screen (part 1) 200 or the delivery date field 223F on the linked application registration screen (part 2) 210 in FIG. 11.

The greater-less symbol "<" is specified in item a2. The administrator can also specify other symbols such as <, =, ≧, ≦, etc. An example of a date, "2020/2/17", is specified in item a3.

Therefore, the record condition setting field 441 is set with a condition that specifies "records with a due date set to before 2/17/2020."

The authority setting column 442 has a user selection column 443, a field code selection column 444, and an authority type column 448. The user selection column 443 and the field code selection column 444 are input columns for setting which user to grant authority to. For example, in the user selection column 443, the administrator can select an individual user, an organization (job title, etc.), or a group (department, team, etc.). In the field code selection column 444, a field can be specified by a field code and authority can be set for the user of that field. For example, authority can be automatically set for the case registrant.

In the authority type column 448, "view" 445, "edit" 446, or "delete" 447 can be selected by corresponding check boxes. "View" 445 is the authority to display a record, "Edit" 446 is the authority to edit a record, and "Delete" 447 is the authority to delete a record.

Each user of the external service system 40 can belong to one or more organizations or groups. A user may belong to, for example, a managerial group, a general employee group, an external employee group, team A, team B, etc. In FIG. 18, the field of delivery date 206 is set as a condition in the record condition setting column 441, but it is also possible to set, for example, the field of case manager 213 in FIG. 11 in the condition setting column 441. By setting in this way, it is also possible to give authority only to the case manager, or to give authority only to users who belong to the case manager's group.

<<Setup flow>>
FIG. 19 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.

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 checks the linked application ID.

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

S13: The fourth communication unit 61 of the external service system 40 receives the 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.

S14: The first communication unit 31 of the terminal device 30 receives the screen information of the linked app registration screen (part 2) 210, and the display control unit 32 of the terminal device 30 displays it on the display 506. The administrator edits the form as appropriate, and the operation reception unit 33 accepts the edits to the form.

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

S16: This causes the display control unit 32 to display the details 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.

S17: Next, when the administrator sets the field code, the operation reception unit 33 of the terminal device 30 receives the field code. Note that steps S14 to S17 are repeatedly executed as appropriate.

S18: When the administrator finishes registering the linked app and presses a specified button, the first communication unit 31 sends the settings 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 settings, and the app registration reception unit 64 stores the field name, field code, etc. in the app information storage unit 65. With this, the linked app in which the service provided by the external service system 40 is customized has been registered.

<Setting authentication information in an information processing system that cooperates with an external service system>
Next, a description will be given of the setting of authentication information in the information processing system 10 so that the information processing system 10 can link with a link target 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.

When a user operates the device 20, in order to link with a linked app in 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 user's authentication information and the like 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 Figures 20 to 24 below are displayed by the terminal device 30 when the terminal device 30 sends an HTTP request to the information processing system 10 and the information processing system 10 sends the screen information in the HTTP response.

Figure 20 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 the My Page button 252 to display the My Page for setting user information. When the My Page button 252 is pressed, the initial screen 250 transitions to the My Page screen.

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

The details display field 262 in FIG. 21 displays a user ID 268, email address 263, last name field 264, first name field 265, and email reply language field 266. The administrator can edit the last name field 264 and first name field 265, and select the 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 integration 267 in the setting content selection field 261, the screen transitions to the My Page screen (part 2).

Figure 22 shows an example of a My Page screen (part 2) 270 displayed by the terminal device 30. The details display field 262 of the My Page screen (part 2) 270 has an external service account login settings field 271 and an external service file transmission/reception settings field 272.

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 for 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.

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 "Unlink" button 277. The external service name 273 is a list of services that can be purchased by the company (called a tenant by 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 stating that there is no license will occur when the link source app is executed.

The linkage column 274 is a column that displays whether or not the linkage settings have been completed. The linkage settings are displayed as "Settings Completed" when the information processing system 10 can log in to the external service system 40 using the user's authentication information. In other words, the value of the "Linkage Settings" managed by the user management unit 44 in Table 2 is displayed.

The sharing field 275 displays whether or not the linked app of the external service system 40 can be shared with other users. The administrator can set whether or not to share on the screen of FIG. 23.

The "Link" button 276 is a button that allows the user to make settings regarding linkage with a linked application of the external service system 40, and the "Unlink" 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. 23 is displayed. The "Unlink" button 277 can only be pressed when the linkage column 274 is "Settings Completed." When the "Unlink" 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 erased from the linkage column 274.

Figure 23 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 username 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 for the external service system 40 is also displayed in Figure 23.

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" contains information that can identify the company. "Company" is the information that can identify the company. This is called a subdomain. The login screen is prepared in this way due to the design of the external service system 40, and subdomains are not necessary.

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 using the subdomain, username, and password. In this embodiment, a case where logging in is successful will be described.

The checkbox 284 "Allow linked services to be shared accounts within the tenant" is a checkbox that allows the administrator to set the linked source app as a shared app. When checked, "Yes" is set in the sharing column 275 in FIG. 22.

Figure 24 is an example of a My Page screen (part 3) 290 displayed by the terminal device 30 when the information processing system 10 is able to log in to the external service system 40. The My Page screen (part 3) 290 in Figure 24 displays a message 291 saying "Success." In other words, it displays that login has been successful and that the linkage settings have been completed. If 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.

<<Operation procedure for setting authentication information in the information processing system>>
25 is an example of a sequence diagram illustrating 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 the sake of convenience of explanation.

S21: The administrator logs in to the information processing system 10 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 specifies the user name and password and sends a login request to the terminal screen providing unit 42.

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

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 for the initial screen 250, the My Page screen (part 1) 260, and the My Page screen (part 2) 270 in response to the administrator's operation.

S24: The first communication unit 31 of the terminal device 30 receives the screen information of the initial screen 250, the My Page screen (part 1) 260, and the My Page screen (part 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 the administrator's operation.

S25: The administrator enters a subdomain, 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 subdomain, the user name, and the password to the terminal screen providing unit 42.

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 save the subdomain, the user name, and the password. The subdomain may not be required.

S27: The input/output processing unit 48 requests authentication of the external service system 40 by specifying the subdomain, user name, and password to the external service processing unit 52.

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

S29: If the authentication is successful, the input/output processing unit 48 sends 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 this, the authentication information of the external service system 40 has been registered in the information processing system 10.

If the linked app is not a shared app, the authentication information set here will be the account used by the linked app. For shared apps, each user can use the authentication information set by the administrator.

For personal apps that are not shared apps, the authentication process in FIG. 25 is performed for each user. This makes it possible to associate each user of the service providing system with a user of the external service system on a one-to-one basis.

Therefore, each user of the service providing system can make an operation request from within the service providing system as a different specific user of the external service system 40. As a result, for example, as described below, the app screen of the external service system 40 can display the user name of the external service system 40 in which the user registered image data. Also, it becomes possible to display information of the external service system 40 that differs for each user on the screen of the link source app displayed by the device 20. In contrast, a shared app has the advantage that each user does not need to perform authentication processing.

<Setting of a link source application of an information processing system for linking with an external service system>
Next, a description will be given of the setting of a link source application of the information processing system 10 so that the information processing system 10 can link with a 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 a client-side administrator for a shared application, and by each user for a personal link source application.

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

The administrator or user sets the linked application ID, field code, etc. as link information in this application processing information. In addition, information related to the screen display is set in the screen information.

The administrator or user connects the terminal device 30 to the information processing system 10 and displays the initial screen. The screens in the following Figures 26 to 32 are displayed by the terminal device 30 when the terminal device 30 sends an HTTP request to the information processing system 10 and the information processing system 10 sends the screen information in the HTTP response.

Figure 26 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, so 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 that allows the administrator to add, delete, edit, etc. a user. The tenant information icon 302 is an icon that allows the administrator to confirm and change what kind of contract the customer has for the provision of the link source application. The application management icon 303 is an icon that allows the administrator to add, delete, edit, etc. a link source application (i.e., application processing information). The device management icon 304 is an icon that allows the administrator to manage how the device 20 is being used. The administrator presses the application management icon 303 to edit the link source application. This causes a service selection screen to be displayed.

Figure 27 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 link. To link with an external service system 40, a tenant needs to purchase a license, but the list of names of external service systems 40 is displayed regardless of whether a license is available or not.

When the administrator selects "External service system A" 311 from the list, the information processing system 10 transmits the app name of the coordination source app associated with "External service system A" to the terminal device 30. That is, the app data management unit 41 identifies the coordination source app associated with "External service system A" from the app data, and obtains the app name of this coordination source app from the app management unit 49.

Figure 28 is an example of a coordination source app selection screen 320 displayed by the terminal device 30. Because the administrator selected "External service system A" from the list in Figure 27, the coordination source app selection screen 320 displays a list of coordination source apps that coordinate with the coordination destination app of "External service system A". In Figure 28, icons 321-326 of six coordination source apps are displayed, but the number of coordination source apps depends on the number of app processing information registered by the administrator. There should be at least one, but there may be zero before the coordination source app is registered.

All six link source apps can link with a link destination app of "external service system A", but the link destination app 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, or 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 explanation, it is assumed that the link source app of "Register a new record" has been selected.

Figure 29 is an example of a coordination source app setting screen (part 1) 330 displayed by the terminal device 30 when the "Register new record" coordination source app is selected, Figure 30 is an example of a coordination source app setting screen (part 2) 340, Figure 31 is an example of a coordination source app setting screen (part 3) 350, and Figure 32 is an example of a coordination source app setting screen (part 4) 360. For convenience of drawing, each screen in Figures 29, 30, 31, and 32 is divided into four parts.

These screens also include link information settings (A) such as the link destination app ID and field code described above, as well as icon display settings (B) for how the device 20 displays the icon of the link source app, settings (C) related to the execution of the link source app, and scan settings (D). Note that the link information settings (A) are set in the app data, the settings (C) related to the execution of the link source app and the scan settings (D) are set in the app processing information, and the icon display settings (B) are set in the screen information.

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 field 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 designation field 349, a dictionary display width field 350, and a default print setting field 351 (a reading color mode field, a manuscript surface field, a manuscript set direction field, a reading resolution field, a manuscript size field, a manual density field, a reading method field, and a preview field).
External service name 331...the name of the external service system 40 selected in "External service system A" 311 in FIG.
User name selection field 332(C)...This is where the administrator's authentication information is set when using a shared application. 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 used to set which destination application in the external service system 40 the source application is to cooperate with. The destination application ID is displayed on the terminal device 30 as shown in FIG.
Space ID column 334 (A)...Identification information of a space for grouping and managing a plurality of coordination source apps is set.
- String field code column 335(A)...This is a column in which the field code of the string column of the coordination source application is set. The field code is displayed on the terminal device 30 as shown in Fig. 14. The information processing system 10 can also display it on the terminal device 30. In this way, it is possible to accept settings related to the items in which data is saved.
Character string field input section 336 (B)...An initial value for the character string field is set here.
- Image data field code column 337 (A)... A field code of the field in which image data is stored is set (an example of first identification information). In this way, settings related to the items in which data is saved can be accepted. In addition to the administrator manually inputting the field code, it is preferable that the field code can be displayed from a pull-down menu or the like. When a linkage destination application ID is input in the application ID setting column 333, the terminal device 30 transmits the linkage destination application ID to the information processing system 10, and the information processing system 10 obtains all field codes set in the linkage destination application specified by the linkage 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)...An email address to contact in case an error occurs during execution of the coordination source application is set.
E-mail subject field 339 (C) - The e-mail subject is also set here.
-OCR language selection field 340(C)...The language to be recognized by OCR is selected. If this setting is not made, the language is automatically selected.
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.
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 separating the numbers in the date (such as "-" in YY-MM-DD) is specified.
Date format column 346 (B) - The date display format (in the order of YY, MM, DD) is selected.
Dictionary label column 347(B)...A display name of the dictionary column 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 designation column 349(B) are displayed on the device 20.
Dictionary delimiter column 348(B) - A delimiter between dictionaries (such as "," or ":") is specified.
Dictionary designation field 349(B)... A list of words to be displayed by device 20 is designated. "Design", "estimate", 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.
Read color mode field 351A(D) - This sets 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.
Read resolution column 351D(D) - The resolution at the time of reading is set.
Document size column 351E(D): The size of the document is set.
Manual Density Column 351F(D) - The density at the time of reading is set.
Scanning method column 351G(D): Bulk scan or individual scan (normal) is set.
Preview column 351H(D): Whether or not to display a preview is set.

<<Operation procedure for setting linkage information, etc. in the information processing system>>
FIG. 33 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.

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 that shown in FIG. 25.

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 app 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 app selection screen 320 from the terminal screen providing unit 42.

S35: The terminal screen providing unit 42 receives a request for the coordination source application selection screen 320. The terminal screen providing unit 42 specifies 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 associated with the external service system 40 (application names can be obtained from the application management unit 49) to the terminal screen providing unit 42. The application list may include applications that coordinate with other external service systems and applications that do not coordinate with other systems, in addition to 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. The authority is managed by the user management unit 44 as shown in Table 2.

S36: When the administrator selects a link source app, the operation reception unit 33 of the terminal device 30 accepts it.

S37: The first communication unit 31 of the terminal device 30 transmits the coordination source app ID of the selected coordination source app to the terminal screen providing unit 42.

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

S39 to S41 are executed when the app selected by the administrator to link with is a shared app.

S39: In the case of a shared app, 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.

S40: The terminal screen providing unit 42 receives the account list. The terminal screen providing unit 42 requests the account list from the user management unit 44. The user management unit 44 obtains authentication information for administrators who belong to the same tenant as the logged-in administrator.

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., selectable 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 linked source app, this setting is not necessary because each individual's authentication information is used.

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

If the link source app is for "register new record," this completes the setup. However, if the link source app is for "register existing record," the user will be registering image data to an existing record in the linked app's table, so steps S43 to S50 are used to set the initial value for which record to register the data to.

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

S44: The terminal screen providing unit 42 receives the record list request. The terminal screen providing unit 42 specifies the linked application ID and sends the record list request to the input/output processing unit 48.

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

S46: The authentication processing unit 51 obtains authentication information for the external service system 40 associated with the administrator from the user management unit 44.

S47: The input/output processing unit 48 specifies the authentication information of the external service system 40 and the linked application ID, and requests the external service processing unit 52 to obtain a list of records.

S48: The external service processing unit 52 specifies the authentication information (subdomain, user name, password) and the linked application ID, and obtains 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 sent to the external service system 40, and in this case, it is preferable to obtain a record list of the field specified by the field code.

S49: The record list is sent to the terminal device 30, and the display control unit 32 of the terminal device 30 displays the record list. Figure 34 describes the link source app setting screen on which the record list is displayed.

S50: The administrator sets an initial value for which record the scanned image data will be registered from the record list. The operation reception unit 33 of the terminal device 30 accepts the setting.

S50-2: When the administrator performs a process to save the information set on the source application setting screen, the operation acceptance unit 33 accepts it, and the first communication unit 31 transmits the collaboration 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.

S50-3: The terminal screen providing unit 42 receives the link information (A), icon display settings (B), settings related to execution of the link source application (C), and 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 screen information. In this way, 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.

Figure 34 is an example of a coordination source app setting screen 370 having a record setting field. This coordination source app setting screen 370 has a record ID field 353. When the administrator presses the record ID field 353, the coordination source app setting screen 370 displays a list of records. In Figure 34, "2" is specified in the field code field 352, so a list of customer names is displayed as a record list in the record ID field 353. For example, in the example of Figure 11, "Osaka Umeko" and "Umeda Taro" are displayed. When the administrator selects a record, the record ID is displayed in the 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 app in the "Register Existing Record" screen information.

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 for the data storage destination. In addition, 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 for the record list.

When storing associated information other than the data acquired by the coordination source app in the coordination target app, the coordination source app setting screen 370 accepts the designation of the field in which to store the associated information, in addition to the designation of the field in which to store the data acquired by the coordination source app. The associated information is data other than image data, such as scan data, fax data, and attachment data acquired by the coordination source app, and is, for example, information such as the user name of the user logging in to the service providing system from the device 20, the affiliation information of the logged-in user, the fax number, and the date and time of receipt. In this case, the field code column 352 for each associated information is displayed on the coordination source app setting screen 370, and the designation of the field code is accepted from the administrator.

It should be noted that the source app for linking "new record registration" can also store associated information in the destination app. In this case, the field code column 352 for each piece of associated information can be displayed on the app settings screen of the source app for linking "new record registration" and the field code can be specified by the administrator.

<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 are displayed by the device 20 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.

The user can select a link source app and perform some simple settings such as a file name. The user operates the device 20 to display a link source app list screen. The screens in the following Figures 35, 36, and 39 are displayed by the device 20 when the device 20 sends an HTTP request to the information processing system 10 and the information processing system 10 sends the screen information in the HTTP response.

Figure 35 is an example of a link source app list screen 380 displayed by device 20. As described above, device 20 can communicate with one or more external service systems 40 via information processing system 10 and link with the service (customized link destination app). When a user selects one external service system 40, the app management unit 49 of information processing system 10 acquires the link source app associated with the external service system 40 and transmits screen information of a link source app list screen 380 on which icons of each link source app are displayed to device 20.

The coordination source app list screen 380 in FIG. 35 has six icons 381-386 corresponding to six coordination source apps. One of these icons is the "Register new record" icon 381. When the user presses the "Register new record" icon 381, a notification to that effect is sent to the information processing system 10, the app management unit 49 of the information processing system 10 obtains screen information 54 associated with the coordination source app ID of "Register new record", and the device screen providing unit 47 generates screen information 54 for the "Register new record" settings screen and sends it to the device 20.

Fig. 36 is an example of a setting screen 390 for "Register new record" displayed by the device 20. The setting screen 390 for "Register new record" has a file name field 391, a calendar field 392, a dictionary field 393, a read setting field 394, and a start button 395. Since the coordination source application in Fig. 36 is "Register new record", the user cannot select a record in this setting screen.
File name field 391: The file name set in the file name field 343 in Fig. 30 is automatically displayed. In Fig. 36, it is today's date.
Calendar field 392: Displays the text set in the date label field 344 in Fig. 30. The calendar field 392 has a Today button and a Calendar button. The Today button inputs today's date into the file name field 391, and the Calendar button displays a calendar.
Dictionary column 393: The dictionary set in the dictionary designation column 349 in Fig. 31 is displayed. When a dictionary is pressed, the corresponding characters such as "design" are input into the file name column 391.
Read setting field 394: Displays the read settings set in the scan settings (D) in Fig. 32. 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 coordination source application "Register new record."
Transition button 396: This button transitions the "new record registration" setting screen 390 to the next screen.

Figure 37 (a) is an example of a "Register new record" settings screen 390-2 that is displayed when transition button 396 is pressed. A delivery date column 397 is displayed on settings screen 390-2. The administrator can specify the information to be entered into the field specified in "Field code to store character string" in Figure 29. For example, if field code 6 is specified (not set in Figure 29), delivery date column 397 is displayed. The user may enter a character string (date) directly from the keyboard, or may specify a character string by selecting calendar column 392 and choosing a date from the calendar.

Figure 37 (b) is an example of a "Register new record" setting screen 390-3 that is displayed when transition button 398 is pressed. A fixed string field 399 is displayed on setting screen 390-3. For example, if a setting has been made to display a field with field code 9 as shown in Figure 29, fixed string field 399 is displayed. The user may enter a string directly from the keyboard, or may select a string from the dictionary field 393.

The character string displayed in the dictionary specification field 349 can be set by the administrator from the link source application setting screen (part 3) in FIG. 31. When the administrator adds a character string, candidate character strings are displayed in the dictionary specification field 349.

In the example of FIG. 31, character strings for the design, quotation, and order form are displayed as a dictionary as shown in FIG. 37. The user can select character strings from this dictionary or combine character strings in the dictionary. Alternatively, the user can combine character strings in the dictionary with character strings entered directly on a keyboard displayed on the device 20. The administrator can specify the items (items into which the user enters character strings) displayed on the device 20 using FIG. 29 to FIG. 31. Fields into which any character string can be entered are associated with the linked app on the link source app setting screen.

In this way, data other than image data received by facsimile that is registered in the external service system 40 may also be a character string specified by the device 20.

<<Operation procedure until the device executes the linked app>>
FIG. 38 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.

S51: The operation reception unit 23 of the device receives input of authentication information for the information processing system 10 from the user, and the second communication unit 21 requests login to the user management unit 44 of the information processing system 10. Here, it is assumed that the login is approved. In response to this, the second communication unit 21 of the device 20 receives a link source app list screen from the Web service processing unit 15, and the display control unit 22 displays it on the display.

S51-2: The user performs an operation to select a desired coordination source app from the coordination source app list screen 380. The following explanation assumes that the user has selected "Register existing record" 382 from the coordination source app list screen 380.

S52: When the operation reception unit 23 of the device 20 receives the operation to select the link source app, the second communication unit 21 requests the app data management unit 41 of the information processing system 10 to obtain app data (space ID, link destination app ID, field code, etc.). The space ID is not necessary. The link source app ID specifies which link destination app the image data, etc. will be saved in. The field code specifies which field of the link destination app the image data, etc. will be saved in.

S53: The first communication unit 31 specifies the coordination source app ID of the coordination source app selected by the user and requests the device screen providing unit 47 to display the "Register existing record" settings screen.

S54: The device screen providing unit 47 receives a request for the settings screen for "Register existing record." The device screen providing unit 47 specifies the coordination source app ID and requests the settings screen of this coordination source app from the app management unit 49.

S55: The application management unit 49 acquires screen information identified by the link 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 "registering existing record."

S56: Because this 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 required.

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

S58: The input/output processing unit 48 requests the authentication processing unit 51 for authentication information of the external service system 40 shown in Table 2 corresponding to the logged-in user (user name is known). In the case of a shared application, since the administrator's authentication information is used by multiple users, this common authentication information is requested from the authentication processing unit 51. In the case of a personal application, the authentication processing unit 51 requests authentication information of the external service system 40 corresponding to the user of the information processing system. In the case of an information processing system configured such that users of different external service systems can be associated with each other depending on the application, even if they are users of the same information processing system, the input/output processing unit 48 may specify the cooperation source application ID specified in S53 in addition to the information of the user of the logged-in information processing system, and request authentication information of the external service system 40 from the authentication processing unit 51.

S59: The authentication processing unit 51 obtains the user's authentication information (subdomain, user name, password) from the user management unit 44.

S60: The input/output processing unit 48 requests a list of records from the external service processing unit 52 by specifying the authentication information, space ID, link source application ID, and field code. The space ID and field code are not necessary. If there is no field code, all fields are obtained.

S61: The external service processing unit 52 is authenticated by the authentication information, and requests the external service system 40 for a list of records for which the user has editing authority, specifying the linked application ID and field code. The data processing unit 63 of the external service system 40 transmits to the external service processing unit 52 only those records for which the user identified by authentication has editing authority. That is, as described in FIG. 11, since authority information is set for each record, the data processing unit 63 provides the record when the user name registered as having editing authority in the authority information matches the user name identified by authentication (the user operating the device 20). As described above, since viewing authority and editing authority can be set for each user or for each user or group managed by the external service system 40, even if the device 20 acquires a record for which the user has only viewing authority, the user cannot register data in that record.

Therefore, in the case of personal apps, the records retrieved may differ depending on the user. For example, if a user has editing permissions for all records in the linked app, all records will be displayed on the device as a record list, but if a user has editing permissions for only some of the records in the linked app, only those some of the records will be displayed as options.

Note that the user here refers to a user of the external service linkage system associated with the user of the service provision system who logged in using a device. The permissions differ depending on the settings of the records and fields of each linked app in the external service system. For example, user X can view and edit all records (or fields) in linked app A, and has editing permissions for only some records in linked app B, but does not have viewing permissions for other records. When user X links with linked app A, all records are displayed on the "Register Existing Record" settings screen, and when linking with linked app B, only records for which user X has editing permissions (only some of the records in the linked app) are displayed. Additionally, it is possible to set linked app C so that all users have viewing and editing permissions for all records.

S62, S63: The record list is sent to the device 20, and the second communication unit 21 acquires data relating to the link source app held by the external service system 40, for which the user of the external service system 40 associated with the user of the information processing system 10 has authority. The display control unit 22 displays a screen that accepts a selection from the data for which the user has authority. The user can select the record to which the image file is to be registered. The operation acceptance unit 23 accepts the data selected via the screen. 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 Figure 39.

S64: Next, the user presses the start button 395 to execute scanning. The image data generating unit 24 of the device 20 scans the document and generates image data.

S65: The second communication unit 21 of the device 20 transmits the image data, the linkage destination application ID, the field code, and the record ID to the linkage source application execution unit 46. In other words, the second communication unit 21 requests the external service system 40 to store the information acquired by the device 20 in association with the received data.

S66: The coordination source application execution unit 46 specifies 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.

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

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

S70: The external service processing unit 52 is authenticated using 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 image data, to the external service system 40. This enables the data processing unit 63 to register the image data in the record identified by the record ID in the field identified by the field code of the linked application identified by the linked application ID.

In the process of FIG. 38, the device 20 passes the app data of the coordination source app via the coordination source app execution unit 46, but if there are no changes to the parameters (if what is set on the coordination source app setting screen is sent as is to the external service system), the input/output processing unit 48 may directly refer to the app data associated with the coordination source app ID from the app data management unit 41. In terms of the sequence, the coordination source app execution unit 46 requests the input/output processing unit 48 to perform the process, but the process may be executed via the app data service unit 11.

Figure 39 is an example of a record list displayed by device 20. Figure 39 is a part of the settings screen for "Register Existing Record." Figure 39 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. In Figure 39, eight "Customer Names" are displayed 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 displays the field name that corresponds to the field code set on the link source app settings screen.

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 was registered when "Register new record" was executed, and the record itself exists, but the "Customer name" has not been registered.

As explained in step S61 of FIG. 38, the records displayed are those for which the user has editing authority. If the user has editing authority for all records in the linked app, all records are displayed. If the user has editing authority for only some of the records in the linked app, only those some of the records are displayed as options.

For a personal app, records that users of the external service system 40 linked to the users of each service providing system have editing authority are displayed. Also, for a shared app, records that the user (administrator) indicated by the authentication information of the external service system 40 associated with the link source app has authority are displayed.

From this list, the user can select a record in which to save image data. Therefore, the device 20 executing the link source application can display a settings screen for the record and configure settings related to the external service system to be used.

Immediately after the device 20 displays the record list, the record set in the record ID field 353 in FIG. 34 is set.

In addition, in FIG. 39, a record list of a certain field is displayed because the field code of the application data set on the link source application setting screen is specified, 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 that field from the information processing system 10.

<Other settings on the linked app settings screen>
FIG. 29 and other figures 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.

Figure 40 is an example of a sequence diagram in which the terminal device 30 displays the name of a linked application of the external service system 40. Note that the process of Figure 40 is performed following or as part of the link source application setting screen of Figures 29 to 32. This process is effective in cases where an administrator wants to confirm which linked application the link source application ID belongs to.

S81: The administrator inputs the space ID of the linked app in the external service system 40 and the linked app ID. The operation reception unit 33 of the terminal device 30 receives the input. Note that the space ID is not necessary.

S82: The first communication unit 31 of the terminal device 30 specifies the space ID of the linked app and the linked app ID, and requests the app name from the terminal screen providing unit 42.

S83: The terminal screen providing unit 42 receives a request for the application name. The terminal screen providing unit 42 specifies the space ID of the linked application and the linked application ID, and requests the application name from the input/output processing unit 48.

S84, S85: The input/output processing unit 48 obtains the authentication information of the logged-in administrator from the user management unit 44 via the authentication processing unit 51 (subdomain, user name, password).

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

S88: The app name is sent to the terminal device 30. The display control unit 32 of the terminal device 30 displays the app name of the linked app.

When the terminal device 30 can display the app name of the linked app in this way, the administrator can confirm which linked app the link source app ID belongs to.

<<Display whether the user has permission to use the linked app specified by the administrator or user>>
Fig. 41 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 linkage target application. The process in Fig. 41 is performed following or as part of the linkage source application setting screen in Fig. 29 to Fig. 32. Such a confirmation is effective because the linkage source application cannot be executed even if the linkage target application that the user does not have the authority to use is linked to the information processing system 10.

S91: The administrator or user inputs the space ID of the linked app in the external service system 40 and the linked app ID. The operation reception unit 33 of the terminal device 30 receives the input. Note that the space ID is not necessary.

S92: The first communication unit 31 of the terminal device 30 specifies the space ID of the linked application and the linked application ID, and requests the terminal screen providing unit 42 to check the permissions.

S93: The terminal screen providing unit 42 receives a request for an authority check. The terminal screen providing unit 42 specifies the space ID of the linked application and the linked application ID and requests the input/output processing unit 48 to check the authority.

S94, S95: The input/output processing unit 48 obtains the 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.

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

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

S99: The first communication unit 31 of the terminal device 30 also transmits to the application data management unit 41 a notification that the user has the authority, and stores the notification in association with the linked application ID and the user name. A user who does not have the authority will know that the authority check has not been performed, and can display this information when the linked application is executed from the device 20.

S100: If authority is not granted, the display control unit 32 of the terminal device 30 displays a message indicating that authority is not granted for the linked app.

By doing so, the fact that the authority exists is stored in the application data management unit 41, and it becomes clear that the user can use the link source application that links with the link destination application. Note that while FIG. 41 shows that the authority of the logged-in administrator or user is being checked, the authority of any user may be checked.

<<Get the field code from the linked app ID and display it as an option>>
Fig. 42 is an example of a sequence diagram in which the terminal device 30 displays a field code based on a link destination application ID. The process in Fig. 42 is performed following or as part of the link source application setting screen in Fig. 29 to Fig. 32. 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.

S101: The administrator inputs the space ID and the linked application ID of the linked 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.

S102: The first communication unit 31 of the terminal device 30 specifies the space ID of the linked application and the linked application ID, and requests a list of field codes from the terminal screen providing unit 42.

S103: The terminal screen providing unit 42 receives a request for a list of field codes. The terminal screen providing unit 42 specifies the space ID of the linked application and the linked application ID, and requests the input/output processing unit 48 to send a list of field codes.

S104, S105: The input/output processing unit 48 obtains the authentication information of the logged-in user from the user management unit 44 via the authentication processing unit 51 (subdomain, user name, password).

S106, S107: The input/output processing unit 48 is authenticated using the authentication information via the external service processing unit 52, and acquires a list of field codes for 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 sent to the terminal device 30. Since the field name cannot be determined from the field code alone, it is preferable that the field name be sent as well.

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

S109: The administrator can set which field code to register image data to from the field code list.

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

S110 to S117: Same as steps S56 to S63 in Figure 38.

Figure 43 shows an example of a list of field codes displayed on the link source application settings screen. As shown in Figure 43, a list of field names and field codes is displayed. Field codes can be selected, and the administrator can select the field code in which image data, etc. is to be saved. The administrator can specify a field and set the selected field code in, for example, the image data field code column 337 in Figure 30. It can also be set for other fields.

＜＜Search for linked apps＞＞
Fig. 44 is an example of a sequence diagram showing a procedure for an administrator to search for a linked application in the external service system 40. The process in Fig. 44 is performed following or as part of the link source application setting screen in Figs. 29 to 32. This process is effective when an administrator wants to check a linked application. The administrator can display a list of linked applications, etc. Once a linked application is displayed, a list of field codes and a list of records can also be displayed.

S121: The administrator performs an operation to obtain a space list. The operation reception unit 33 of the terminal device 30 receives the operation, and the first communication unit 31 transmits a request to obtain the space list to the terminal screen providing unit 42.

S122: The terminal screen providing unit 42 receives a request for a space list. The terminal screen providing unit 42 sends a request to obtain a space list to the input/output processing unit 48.

S123, S124: The input/output processing unit 48 obtains the authentication information of the logged-in user from the user management unit 44 via the authentication processing unit 51 (subdomain, user name, password).

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

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

S128: The administrator selects the space to which the linked app of which the administrator wishes to view a list belongs from the space list. The operation reception unit 33 of the terminal device 30 receives the selection.

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

S135: The display control unit 32 of the terminal device 30 displays the app list. At this time, the app name of the linked app, the linked app ID, or both may be displayed. Since the administrator specified a space ID when obtaining the app list, the app list within the space is displayed. If no space is specified, all linked apps are displayed.

S136: The administrator selects a linking app from the displayed list of apps. The operation reception unit 33 of the terminal device 30 receives the selection. For example, the administrator selects a linking app that the administrator wants to link with the linking source app that he or she is setting.

S137: The first communication unit 31 specifies the space ID and the linked application ID and sends a request to obtain a list of field codes to the terminal screen providing unit 42.

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

S139, S140: The input/output processing unit 48 obtains the authentication information of the logged-in administrator from the user management unit 44 via the authentication processing unit 51 (subdomain, user name, password).

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

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

S144: The administrator selects the field in which he/she wants to register image data from the displayed list of field codes. The operation acceptance unit 33 of the terminal device 30 accepts the selection. As shown in FIG. 43, the selected field code is set in the field code column 337 for image data.

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

In this way, the administrator can display a list of spaces, apps, field codes, and records, and set the linked app ID, field code, and records, etc., in the linked app.

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

S160: The operation reception unit 23 of the device 20 receives input of authentication information for the information processing system 40 from the user, and the second communication unit 21 requests login to the user management unit 44 of the information processing system 10. Here, it is assumed that the login has been approved.

S161: Using 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 device 20 accepts authentication information of the user of information processing system 10, and the second communication unit 21 transmits a request to the application data management unit 41 of information processing system 10 to acquire a list of coordination source apps, specifying the authentication information of the user of the information processing system and "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 app list may include apps provided by a service providing system other than the coordination source app associated with "external service system A".

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

S163 to S167: Same as S51 to S55 in Figure 38.

Then, steps S168 to S175 are executed if "Register existing record" is selected.

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. 39 is displayed. The operation reception unit 23 of the device 20 receives the operation.

S169 to S174: Same as S56 to S61 in Figure 38.

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

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

S177: The second communication unit 21 transmits the image data and the record ID (not present 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 associated information (user name). In addition, if the coordination source application is a native application, the data may be transferred directly from the device 20 to the external service system 40.

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

S179, S180: The input/output processing unit 48 obtains the user information of the logged-in user (which may be information that identifies the user, such as the user name, in this case) via the authentication processing unit 51.

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

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

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

S185: The external service processing unit 52 is authenticated using 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 no record ID is 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 the field codes set as the storage destinations for each associated information and data on the link source application setting screen.

In both the cases of "Register existing record" and "Register new record", the data processing unit 63 registers the user name in the case manager 213 field in FIG. 11. Note that in the case of "Register existing record", a case manager may already be registered. In this case, the data processing unit 63 may leave the original case manager unchanged, overwrite the existing one, or add a new case manager.

The data processing unit 63 also sets default authority information 214. For example, the user who registered the image data is given the authority to view, edit, and delete.

Note that while Figure 45 shows a case where the data acquired by the link source app is a scan, the same process can be used when the data acquired by the link source app is a fax, and the fax data and associated information can be saved in the link destination app.

Figure 46 is an example of the linked application registration screen (part 1) 200 in which a case manager is registered. Assume that the user who logged in to the information processing system 10 in the process of Figure 45 is U002 shown in Table 2. Assume also that the record number in which the user registered image data is 70. For this reason, "taro", which is the user name of the external service system corresponding to user U002 in the service providing system, is registered in the case manager 213 column. By registering the case manager in this manner, it becomes possible to set the authority according to the user who registered the record on the authority setting screen 440 shown in Figure 18. As a result, the device 20 can display records for which the user has editing authority, including records registered by the user from the device, on the "Register existing record" setting screen as shown in Figure 39.

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

Fig. 47 is an example of a coordination source application setting screen 410 for a coordination source application called "FAX reception registration" displayed by the terminal device 30. Note that the explanation of Fig. 47 will mainly explain the differences from Figs. 29 to 32. The coordination source application setting screen 410 in Fig. 47 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 a reception date and time.
Field code 491 for registering a fax number: A field code in which a fax number is to be registered is specified (an example of second identification information).
Field code 492 for registering image data: A field code in which image data received by facsimile is registered is specified (an example of first identification information).
Field code 493 for registering the reception date and time: A field code in which the reception date and time is to be registered is specified.

In this way, the administrator can set field codes such as image data and a fax number on the link source application setting screen 490. This allows the device 20 to register not only image data received by facsimile but also data other than image data in the external service system 40. Figure 47 (and Figure 48) is an example of "accepting the setting of first identification information indicating the storage destination of the data in the external service system and second identification information indicating the storage destination of associated information to be stored in the external service system in association with the data".

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 data about data, not the data itself, it is called meta (higher-level) data. For example, it is data managed in EXIF for JPEG images.

Next, the "Email reception registration" cooperation source application setting screen 420 will be described. Fig. 48 is an example of the cooperation source application setting screen 420 of the "Email reception registration" cooperation source application displayed by the terminal device 30. The cooperation source application setting screen 420 in Fig. 48 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 (an example of second identification information).
Field code 422 for registering the body of the email: A field code in which the body of the email is to be registered is specified (an example of second identification information).
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 (an example of second identification information).
Field code 424 for registering sender: A field code in which the sender of an e-mail is registered is specified (an example of second identification information).
Field code 425 for registering an attached file: A field code in which a file attached to an e-mail is registered is specified (an example of first identification information).

Therefore, in the case of e-mail, the device 20 can register not only image data received via e-mail, but also data other than image data, in the external service system 40.

<<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 link source application settings screen, and the device saves the data in a specific field of the link destination application when a facsimile is received>>
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.

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

S192: When the facsimile processing unit 25 receives a reception notification, it acquires the image data received from the facsimile unit 933.

S193: The facsimile processing unit 25 requests device authentication from 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 authentication of the device 20 is successful when the device ID, UUID (Universally Unique Identifier), etc. are sent.

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

S195: As shown in FIG. 8, the facsimile processing unit 25 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.

S196: The facsimile processing unit 25 transmits the image data received by facsimile, the linked application ID, field code, and 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 linked application. In other words, the second communication unit 21 requests the storage of the data (image data) and associated information (fax number) in the external service system according to the settings.

S197, S198: The input/output processing unit 48 obtains the 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. In other words, since this is a shared application, the authentication information of the administrator is used.

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

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

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

In FIG. 49, the device 20 acquires the application data (space ID, linked application ID, field code, etc.) in step S194, but this is not necessarily required. In this case, when the linked application ID of the link source application related to facsimile reception is sent to the information processing system 10, the information processing system 10 can identify the linked application ID, etc. based on the application data.

<<The device transmits image data and non-image data only from specific fax numbers to an external service system>>
A method for 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.

Figure 50 shows an example of a collaboration source app setting screen 430 displayed by the terminal device 30. This collaboration source app setting screen 430 is a whitelist of fax numbers that the device 20 registers in the external service system 40 (the data of senders registered in the list is registered in the external service system). The whitelist is stored in the app data storage unit 13.

When the facsimile processing unit 25 receives a facsimile, it receives the application data from the information processing system 10, and if the value is on the whitelist, it executes the subsequent processing, but if it is not, it does not register it. This makes it possible to register only image data received from important senders.

Alternatively, the component 18 may determine whether the fax number is registered on the whitelist. Figure 51 shows a schematic diagram of application processing information for registering image data, etc., only from 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, it refers to the whitelist and determines whether the fax number set in the parameters of the application processing information is registered on 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 email sending component 432 sends an email and does not register it.

In this way, application processing information can be branched depending on the sender of the fax or the sender of the email. The same processing can be done for the sender of the email. Furthermore, characters contained in the OCR results of image data received by facsimile, or characters contained in email (subject, body) can be compared with a whitelist and processed in the same way.

In addition, in FIG. 51, the system simply switches between saving and not saving image data, but it is also possible to associate processing content with characters contained in the OCR results of image data received by facsimile or characters contained in e-mail, and execute a specified process. Also, the whitelist may be a blacklist (data from senders registered on the list is not registered in the external service system).

Figure 52 is an example of a sequence diagram showing the 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 Figure 52 will mainly focus on the differences from Figure 49.

S196: The whitelist included in the app data is sent to the input/output processing unit 48.

S198-2: The input/output processing unit 48 specifies the fax number and the whitelist and requests the judgment unit 55 to decide whether or not to register the fax number and the whitelist in the external service system 40. If the judgment unit 55 determines that the fax number and the whitelist should be registered, step S200 is executed.

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

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

For example, the configuration example in FIG. 5 and the like is divided according to main functions 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 also be divided into even more processing units depending on the processing content. Also, it can be divided so that one processing unit includes even more processes.

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. The computing devices are configured to communicate with each other via any type of communication link, including a network, shared memory, etc., and perform the processes disclosed herein.

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

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

Reference Signs List 10 Information processing system 20 Device 30 Terminal device 100 Service providing system

JP 2017-076368 A

Claims (21)

A service providing system including a device and an information processing system that transmits data acquired from the device to an external service system,
a setting receiving unit that receives settings of first identification information indicating a storage destination of the data in the external service system, second identification information indicating a storage destination of associated information to be stored in the external service system in association with the data, and identification information of a second application that operates in the external service system ;
the device has a communication unit that acquires the data and the associated information and requests the information processing system to store the data and the associated information in the external service system according to the setting;
the data and the associated information are related to a first application that is requested to be executed by the device and that is running on the information processing system;
the information processing system has an external service processing unit that transmits the data, the first identification information, the associated information, the second identification information, and the identification information of the second application to the external service system when execution of the first application is requested from the device;
A service providing system comprising: 2. The service providing system according to claim 1, wherein the first identification information and the second identification information indicate items in a table of a database in the external service system. the setting reception unit receives settings of the first identification information of the item to which the data is associated, the second identification information of the item to which the associated information is associated, and identification information of the second application that operates the database;
The external service processing unit:
The service providing system according to claim 2, characterized in that when the device requests execution of the first application, the data, the first identification information, the associated information, the second identification information and the identification information of the second application are transmitted to the external service system. the second application is an application that manages the items, the data, and the associated information in association with each other;
the setting reception unit receives the second identification information of the item in which the associated information is stored among the items in the database for each of the associated information;
The service providing system described in claim 3, characterized in that when execution of the first application is requested, the external service processing unit transmits the data, the first identification information, the identification information of the second application, and the second identification information of each of the items of the associated information to the external service system. When the device receives image data from an external device, an application corresponding to a function for receiving the image data is executed;
the application requests the information processing system to execute the first application with which the application is associated in advance, and transmits the image data, the first identification information, the associated information, and the second identification information to the information processing system;
The service providing system according to claim 4, characterized in that the information processing system transmits the image data, the first identification information, the associated information, the second identification information of each of the items of the associated information, and the identification information of the second application to the external service system. The application corresponds to a facsimile receiving function,
6. The service providing system according to claim 5, wherein the associated information is at least one of a FAX number and a reception date and time. When the device receives the data and the associated information from an external device, an application corresponding to a receiving function of the data and the associated information is executed;
the application requests the information processing system to execute the first application with which the application is associated in advance, and transmits the data and the associated information to the information processing system;
The service providing system described in claim 4, characterized in that the information processing system transmits the data, the first identification information, the associated information, the second identification information of each of the items of the associated information, and the identification information of the second application to the external service system. The application supports an e-mail receiving function,
8. The service providing system according to claim 7, wherein the associated information is at least one of the subject, the body, the date and time of receipt of the e-mail, and the e-mail address of the sender. When the device transmits image data generated by scanning a document to the information processing system, the device requests the information processing system to execute the first application.
The service providing system described in claim 4, characterized in that the external service processing unit transmits the image data, the first identification information, the associated information, the identification information of the second application, and the second identification information of each of the items of the associated information to the external service system. The service providing system according to claim 9, characterized in that the associated information is information about a logged-in user. The information processing system includes:
A service providing system as described in any one of claims 3 to 8, characterized in that the associated information transmitted from the device is analyzed and whether or not to transmit the associated information to the external service system is controlled. the setting reception unit receives registration of the associated information to be transmitted to the external service system or the associated information not to be transmitted to the external service system for a list of items associated with the first application requested to be executed by the device;
The service providing system according to claim 11, characterized in that the information processing system controls whether or not to transmit the data to the external service system by comparing the list of items with the associated information transmitted from the device. the setting reception unit transmits to the terminal device screen information for receiving an order of the processes to be arranged based on the icons corresponding to the processes;
The terminal device
receiving an arrangement of the icons displayed based on the screen information, and transmitting application processing information related to a setting of the first application to the information processing system;
The service providing system according to claim 12 , wherein the function of analyzing the associated information is set as the icon. a second communication unit configured to transmit to the device identification information of the second application associated with the first application requested by the device, the first identification information of the item in the database, and the second identification information;
A service providing system as described in any one of claims 5 to 10, characterized in that when the external service processing unit receives a request from the device to execute the first application, it transmits to the external service system the identification information of the second application, the first identification information of the item, the second identification information, the data, and the associated information transmitted from the device. The service providing system according to any one of claims 5 to 10, characterized in that, when the external service processing unit receives a request from the device to execute the first application, it transmits to the external service system identification information of the second application that is previously associated with the first application, the first identification information of the item in the database, the second identification information, the data, and the associated information. The service providing system according to claim 5, characterized in that the associated information is a character string entered or selected on the screen of the first application displayed by the device. when the device displays a screen of the first application, the information processing system accepts registration of a dictionary to be displayed on the screen;
17. The service providing system according to claim 16, wherein the character string includes a character string selected from the dictionary displayed on the screen. 2. The service providing system according to claim 1, wherein the settings received by the setting receiving unit are settings for the first application . An information processing system that transmits data acquired from a device to an external service system,
a setting receiving unit that receives settings of first identification information indicating a storage destination of the data in the external service system, second identification information indicating a storage destination of associated information to be stored in the external service system in association with the data, and identification information of a second application that operates in the external service system ;
the data and the associated information are related to a first application that is requested to be executed by the device and that is running on the information processing system;
an external service processing unit that acquires the data and the associated information from the device, and transmits the data, the first identification information, the associated information, the second identification information, and the identification information of the second application to the external service system when execution of the first application is requested;
An information processing system comprising: 1. An information processing method performed by a service providing system including a device and an information processing system that transmits data acquired from the device to an external service system,
a setting receiving unit receiving settings of first identification information indicating a storage destination of the data in the external service system, second identification information indicating a storage destination of associated information to be stored in the external service system in association with the data , and identification information of a second application operating in the external service system ;
The device comprises:
a communication unit acquiring the data and the associated information, and requesting the information processing system to store the data and the associated information in the external service system according to the setting;
the data and the associated information are related to a first application that is requested to be executed by the device and that is running on the information processing system;
The information processing system includes:
a step of transmitting, when an external service processing unit receives a request for execution of the first application from the device, the data, the first identification information, the associated information, the second identification information, and the identification information of the second application to the external service system;
23. An information processing method comprising: An information processing system that transmits data acquired from a device to an external service system,
a setting receiving unit that receives settings of first identification information indicating a storage destination of the data in the external service system, second identification information indicating a storage destination of associated information to be stored in the external service system in association with the data, and identification information of a second application that operates in the external service system ;
the data and the associated information are related to a first application that is requested to be executed by the device and that is running on the information processing system;
A program characterized by functioning as an external service processing unit that acquires the data and the associated information from the device, and when a request is made to execute the first application, transmits the data, the first identification information, the associated information, the second identification information, and the identification information of the second application to the external service system .

Images