JP7165373B1 - Inter-enterprise data linkage system, information processing device and program - Google Patents

Abstract

[Problems] When inter-company data is linked between SaaS, manual double input is not required, security is ensured without passing the company's SaaS authentication information to other companies, and data leakage and data leakage are prevented. To provide technology that reduces the risk of falsification and contributes to internal control (IT control). A data linkage server, a first user terminal of a linkage source user, and a first SaaS side server are connected via a network, and the data linkage server and a second user terminal of a linkage destination user are connected to each other via a network. An inter-company data linkage system in which a second SaaS side server is connected via the network, wherein the recipe registration unit of the first user terminal is packaged with a function suitable for the purpose of the inter-company data linkage. Information about the recipe that was created, which includes at least the SaaS type used by the collaboration source user, the folder ID of the collaboration source user, the SaaS authentication information of the collaboration source user, the email address of the collaboration source user, and the collaboration destination user setting registration of the recipe information including the e-mail address of the data link server, and the recipe management unit of the data link server stores the recipe information of the link source user in a predetermined storage unit. Then, the e-mail sending/receiving unit of the data linkage server sends an e-mail to the second user terminal to notify the request for data linkage of the predetermined service provided by the SaaS from the linkage source user. , the recipe registration unit of the second user terminal is information about the recipe, at least the SaaS type used by the collaboration destination user, the folder ID of the collaboration destination user, and the SaaS of the collaboration destination user setting registration of the recipe-related information including the authentication information of the data linking server, and the recipe management unit of the data linking server stores the recipe-related information of the cooperation destination user in the predetermined storage unit. and the e-mail transmitting/receiving unit of the data linkage server transmits the e-mail to the first user terminal to notify completion of setting and registration of the recipe-related information of the cooperation destination user, and A recipe execution instruction unit of one user terminal issues an instruction to start execution of the recipe to the data linkage server, and a recipe execution unit of the data linkage server issues an instruction to start execution of the recipe or the executing the recipe based on automatic execution timing information stored in a predetermined storage unit by the setting registration from the first user terminal as information about the recipe, and using the SaaS authentication information of the cooperation source user; API connection is made to the first SaaS side server, predetermined data is acquired from the folder of the collaboration source user, and the collaboration destination user the API connection to the second SaaS side server using the user's SaaS authentication information, save the predetermined data in the folder of the cooperation destination user, and change the SaaS type of the first user terminal When changing the SaaS type of the cooperation source user among the information related to the recipe, the unit notifies the data linkage server of the SaaS type after the change, and determines the SaaS type of the second user terminal. When changing the SaaS type of the cooperation source user among the information related to the recipe, the changing unit notifies the data linkage server of the changed SaaS type, and controls the recipe management unit of the data linkage server. stores the SaaS type after the change received from the first user terminal or the second user terminal in the predetermined storage unit, and the folder change unit of the first user terminal is related to the recipe When changing the folder ID of the linking source user among the information, the folder ID after the change is notified to the data linking server, and the folder changing unit of the second user terminal changes the recipe When changing the folder ID of the cooperation source user among the information related to the first or the second user terminal, and stores the changed folder ID in the predetermined storage unit. [Selection drawing] Fig. 1

Description

The present invention relates to technology for linking data between companies.

First, the inter-company data linkage service provided by the company in which the information processing apparatus of the present invention that executes the program of the present invention is installed (built or owned) is hereinafter referred to as "this service". In addition, the inter-company data linkage system of the present invention is constructed by including the provider side and the provided side of this service.
Moreover, the present invention is a product-level product that is developed and released through trial and error, and does not remain at the mere idea stage.

Recently, due to the rapid progress in the use of cloud services depending on the purpose, the data of one company is scattered in various services, and the integration of the data is becoming more complicated day by day.
Therefore, by enabling data linkage between cloud services such as SaaS, PaaS, and IaaS (hereinafter collectively referred to as "SaaS") on the cloud to be expanded or reduced according to needs, business automation and efficiency Platform services are provided that can optimize business processes and strengthen internal controls (IT controls) while reducing total costs. This eliminates the need to provide a data input screen and to use a closed network, unlike EDI, which has been common in the past, for data linkage.

By the way, conventionally, inter-company data exchange, cooperation, and sharing have been carried out between subsidiaries within a company's group or between parent-subsidiary companies.
In other words, it has not generally been practiced to link the SaaS used by each company for the purpose of its own use among other companies.
This is because the use of SaaS requires the company's own authentication information (for example, token), and it is impossible from the security point of view to pass such important confidential information to other companies. In token authentication, user information is specified by exchanging authentication information called Token between the browser and the server.

Therefore, when sharing folders (sharing cloud storage/data) between other companies (for example, Company A and Company B), for example, create and send an e-mail each time, send the data to the other party, and then call However, in case Company A, the owner of the data, disappears due to bankruptcy, merger, etc., Company B copies the same data and keeps it in-house as a backup. I needed it. This double entry of data is manual and complicated, and there is a risk of falsification (internal control/IT control problems).

Here, as a related technique, a technique has been proposed for efficiently achieving cooperation between SaaS without burdening development on the user side (see Patent Literature 1).

Japanese Patent No. 6440571

However, with the technology disclosed in Patent Document 1 above, when inter-company data is linked between SaaS, inter-company data linkage is performed in a state in which security is ensured without passing company authentication information to other companies. It was difficult to plan.
In addition, the technology disclosed in Patent Document 1 above provides a mechanism that contributes to internal control (IT control) by reducing the risk of data leakage and data falsification when inter-company data is linked between SaaS. There was a problem that it was difficult to

The object of the present invention is to eliminate the need for manual double input when inter-company data is linked between SaaS, and to ensure security without passing the company's SaaS authentication information to other companies, and data It is to provide technology that contributes to internal control (IT control) by reducing the risk of leakage and data falsification.

The inter-company data linkage system of the present invention is
The data linkage server, the first user terminal of the collaboration source user, and the first SaaS side server are connected via a network, and the data linkage server, the second user terminal of the collaboration destination user, and the second SaaS server are connected via a network. An inter-company data linkage system in which a side server is connected via the network,
The recipe registration unit of the first user terminal stores information related to recipes packaged with functions suited to the purpose of inter-company data linkage, including at least the SaaS type used by the linkage source user, the folder of the linkage source user ID, SaaS authentication information of the collaboration source user, the e-mail address of the collaboration source user, and the e-mail address of the collaboration destination user.
The recipe management unit of the data linkage server stores information about the recipe of the collaboration source user in a predetermined storage unit,
The e-mail transmission/reception unit of the data linkage server notifies the second user terminal of a request for data linkage of the predetermined service provided by the SaaS from the linkage source user by sending an e-mail to the second user terminal,
The recipe registration unit of the second user terminal is information about the recipe, at least the SaaS type used by the collaboration destination user, the folder ID of the collaboration destination user, and the SaaS of the collaboration destination user setting and registering information related to the recipe, including authentication information, to the data linkage server;
The recipe management unit of the data linkage server stores information about the recipe of the collaboration destination user in the predetermined storage unit,
The e-mail transmission/reception unit of the data linkage server transmits the e-mail to the first user terminal to notify the completion of setting and registration of the recipe-related information of the cooperation destination user;
a recipe execution instruction unit of the first user terminal issues an instruction to start execution of the recipe to the data linkage server;
The recipe execution unit of the data link server receives an instruction to start execution of the recipe or automatic execution timing information stored as information on the recipe in the predetermined storage unit by the setting registration from the first user terminal. Execute the recipe based on, API-connect to the first SaaS side server using the SaaS authentication information of the collaboration source user, acquire predetermined data from the folder of the collaboration source user, making the API connection to the second SaaS-side server using the SaaS authentication information of the collaboration destination user, saving the predetermined data in the folder of the collaboration destination user;
The SaaS type changing unit of the first user terminal, when changing the SaaS type of the cooperation source user among the information related to the recipe, notifies the data linkage server of the changed SaaS type,
The SaaS type changing unit of the second user terminal notifies the data linkage server of the changed SaaS type when changing the SaaS type of the cooperation source user among the information related to the recipe. ,
The recipe management unit of the data linkage server stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit,
the folder changing unit of the first user terminal, when changing the folder ID of the cooperation source user among the information related to the recipe, notifies the data link server of the changed folder ID;
The folder changing unit of the second user terminal notifies the data linkage server of the changed folder ID when changing the folder ID of the cooperation source user among the information related to the recipe. ,
The recipe management unit of the data linkage server stores the changed folder ID received from the first user terminal or the second user terminal in the predetermined storage unit.

The information processing device of the present invention includes:
Connected to a first user terminal of a collaboration source user and a first SaaS side server via a network, and connected to a second user terminal of a collaboration destination user and a second SaaS side server via the network A connected information processing device,
Information about recipes packaged with functions suited to the purpose of inter-company data linkage, from the recipe registration unit of the first user terminal, at least the SaaS type used by the linkage source user, the type of the linkage source user Receiving setting registration of information related to the recipe including a folder ID, SaaS authentication information of the collaboration source user, the email address of the collaboration source user, and the email address of the collaboration destination user, and storing the collaboration source in a predetermined storage unit a recipe management unit that stores information about the user's recipe;
an e-mail transmitting/receiving unit that transmits an e-mail to the second user terminal and notifies a request for data linkage of a service provided by the predetermined SaaS from the cooperation source user;
The recipe management unit receives information about the recipe from the recipe registration unit of the second user terminal, and includes at least the SaaS type used by the collaboration destination user, the folder ID of the collaboration destination user, and the Accepting setting registration of information about the recipe including authentication information of the SaaS of the collaboration destination user, storing the information about the recipe of the collaboration destination user in the predetermined storage unit,
The e-mail transmission/reception unit sends the e-mail to the first user terminal to notify the completion of setting and registration of the recipe-related information of the cooperation destination user;
An instruction to start execution of the recipe from the recipe execution instruction unit of the first user terminal or automatic execution stored as information on the recipe in the predetermined storage unit by the setting registration from the first user terminal Execute the recipe based on the timing information, use the SaaS authentication information of the collaboration source user to make an API connection to the first SaaS side server, and acquire predetermined data from the folder of the collaboration source user. and further comprising a recipe execution unit that connects the API to the second SaaS-side server using the SaaS authentication information of the collaboration destination user and saves the predetermined data in the folder of the collaboration destination user,
The recipe management unit stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit,
The recipe management unit stores the changed folder ID received from the first user terminal or the second user terminal in the predetermined storage unit.

The program of the present invention is
Connected to a first user terminal of a collaboration source user and a first SaaS side server via a network, and connected to a second user terminal of a collaboration destination user and a second SaaS side server via the network to the connected information processing device,
Information about a recipe packaged with a function matching the purpose of inter-company data linkage from the recipe registration unit of the first user terminal by the recipe management unit, at least the SaaS type used by the linkage source user, Receiving setting registration of information related to the recipe including the folder ID of the collaboration source user, SaaS authentication information of the collaboration source user, the e-mail address of the collaboration source user, and the e-mail address of the collaboration destination user, and storing in a predetermined storage a process of storing information about the recipe of the cooperating user in a section;
A process of sending an e-mail to the second user terminal by the e-mail transmission/reception unit to notify the request for data cooperation of the predetermined service provided by the SaaS from the cooperation source user;
Information about the recipe from the recipe registration unit of the second user terminal by the recipe management unit, at least the SaaS type used by the cooperation destination user, the folder ID of the cooperation destination user and the A process of accepting setting registration of information about the recipe including authentication information of the SaaS of the collaboration destination user, and storing the information about the recipe of the collaboration destination user in the predetermined storage unit;
a process of sending the e-mail to the first user terminal by the e-mail transmission/reception unit to notify completion of setting and registration of the recipe-related information of the cooperation destination user;
By the recipe execution unit, an instruction to start execution of the recipe from the recipe execution instruction unit of the first user terminal or the setting registration from the first user terminal as information about the recipe in the predetermined storage unit Execute the recipe based on the stored automatic execution timing information, use the authentication information of the SaaS of the collaboration source user to make an API connection to the first SaaS side server, and from the folder of the collaboration source user A process of acquiring predetermined data, making the API connection to the second SaaS-side server using the SaaS authentication information of the collaboration destination user, and storing the predetermined data in the folder of the collaboration destination user. When,
a process of storing the changed SaaS type received from the first user terminal or the second user terminal by the recipe management unit in the predetermined storage unit;
and storing the changed folder ID received from the first user terminal or the second user terminal in the predetermined storage unit by the recipe management unit.

According to the present invention, when inter-company data is linked between SaaS, manual double input is unnecessary, and security is ensured without passing the company's SaaS authentication information to other companies, and data It is possible to provide technology that reduces the risk of leakage and data falsification and contributes to internal control (IT control).

1 is a diagram showing the configuration of an inter-company data linkage system according to an embodiment of the present invention; FIG. 1 is a functional block diagram of a data linkage server and user terminals that constitute an inter-company data linkage system according to an embodiment of the present invention; FIG. It is a figure which shows an example of each table structure of each DB of the inter-company data linkage system which concerns on embodiment of this invention. It is a figure explaining the flow of processing of the inter-company data linkage system which concerns on embodiment of this invention. 4 is a sequence diagram showing processing operations of the inter-company data linkage system according to the embodiment of the present invention; FIG. It is a figure which shows an example of the display screen in the user terminal by the side of A company of the inter-company data linkage system which concerns on embodiment of this invention. It is a figure which shows an example of the display screen in the user terminal by the side of B company of the inter-company data linkage system which concerns on embodiment of this invention. BRIEF DESCRIPTION OF THE DRAWINGS It is a figure which shows the 1st Example of the inter-company data linkage system based on embodiment of this invention. It is a figure which shows the 2nd Example of the inter-company data linkage system based on embodiment of this invention. It is a figure which shows the 3rd Example of the inter-company data linkage system based on embodiment of this invention. FIG. 13 is a diagram showing a fourth example of the inter-company data linkage system according to the embodiment of the present invention;

The present invention provides cloud services such as SaaS, PaaS, and IaaS (hereinafter collectively referred to as "SaaS") used by one company for its own use, and SaaS used by other companies for its own use, Utilizing the functions of the Web API provided by these SaaS, inter-company data exchange (especially between other companies) via the Internet (on the Web) will be performed on behalf of each other, and inter-company business transactions will be made more efficient. It is something to do. Therefore, as long as the SaaS is provided with a Web API, data linkage can be realized in any combination.

A first embodiment of the present invention will be described below with reference to the drawings.
The configuration of the inter-company data linkage system according to this embodiment will be described with reference to FIG. It is assumed that Company A is the linking source user (consignor) of the inter-company data linking in this service (inter-company data linking service) and B company is the linking destination user (trustee).

As shown in FIG. 1, the inter-company data linkage system 10 includes a data linkage server 100 as an information processing device installed at a company that provides this service, and a company A as a company that performs data linkage between companies. A user terminal 200a installed on the side, a SaaS-side server 300a of SaaS used by company A, a user terminal 200b installed on the side of company B as another company that performs data linkage between companies, and a user terminal 200b on the side of company B It is composed of a SaaS server 300b that is used in.
At least the data linkage server 100, the user terminal 200a, and the SaaS side server 300a are connected by a predetermined network such as the Internet. At least the data linkage server 100, the user terminal 200b, and the SaaS side server 300b are connected by a predetermined network such as the Internet.
Here, the data linkage server 100 and the SaaS side servers 300a and 300b are shown as one information processing device, but the functions may be realized by a plurality of information processing devices.
When the SaaS used by company A and the SaaS used by company B are the same, the SaaS side server 300a and the SaaS side server 300b may be the same information processing device.

The data linking server 100 is an information processing device that is controlled by a CPU (Central Processing Unit) and that includes storage means such as ROM (Read Only Memory) and RAM (Random Access Memory), and known input/output means. For example, workstations, high-performance personal computers, and the like. It may be a cloud server. It may be operated by a company that provides this service.

The user terminal 200a and the user terminal 200b are controlled by a CPU (Central Processing Unit) and include storage means such as ROM (Read Only Memory) and RAM (Random Access Memory). is. For example, smart phones, tablet terminals, small personal computers, mobile terminals, and the like. It is an information processing device operated by a user of this service.

The SaaS side server 300a and the SaaS side server 300b are controlled by a CPU (Central Processing Unite) and include storage means such as ROM (Read Only Memory) and RAM (Random Access Memory). processing equipment. For example, workstations, high-performance personal computers, and the like. It may be a cloud server. It may be managed by each SaaS provider.
The SaaS side server 300a provides the SaaS Web API. The SaaS side server 300b also provides the SaaS Web API.
Here, the Web API is an API (Application Programming Interface) realized on the Web. Many APIs that are not Web APIs are provided using the same programming language as the programming language used by the user, but Web APIs are HTTP/HTTPS-based, which allows communication even if the programming language is different, so they are different. There is an advantage that it can be used between applications (between SaaS) developed in a programming language. In addition, since the Web API uses HTTP/HTTPS, which are known protocols, it is highly transparent and has the advantage of establishing secure communication means.

Each device constituting the inter-enterprise data linkage system 10 is mainly an information processing device, and various known techniques may be applied to their detailed configuration, and descriptions other than those described above are omitted here.

FIG. 2 shows functional blocks of the data linkage server 100, the user terminal 200a, and the user terminal 200b, which constitute the inter-company data linkage system 10 according to the present embodiment.

Referring to FIG. 2, the data linkage server 100 includes an account management unit 101, a recipe management unit 102, a recipe execution unit 103, an e-mail creation unit 104, an e-mail transmission/reception unit 105, and a user terminal screen management unit 106. , a display unit 107 and a storage unit 108 . Each unit may be implemented by a known input/output I/F, CPU, or the like, or by an HDD or the like.

The account management unit 101 has a function of storing the user ID (e-mail address, password, etc.) received from the user terminal 200a or the user terminal 200b at the time of account registration (user registration) in this service in the user master table of the user management DB 210. Also, it has a function of searching a user master table or the like of the user management DB 210 based on the user ID and executing user authentication.

The recipe management unit 102 has a function of managing recipe information. Here, a linkage program that packages functions that match the purpose of data linkage between companies in this service is called a "recipe (recipe for linkage between companies)". In the case of storage sharing, the SaaS type (SaaS name) of the collaborating user (Company A/consignor), the folder ID of the collaborating user (Company A/consignor) (or a URL indicating the location of the folder, etc.) etc., authentication information of the relevant SaaS of the collaborating user (Company A/Consignor), e-mail address of the collaborating user (Company A/Consignor), e-mail address of the cooperating user (Company B/Consignor), electronic E-mail description information, recipe automatic execution timing information, SaaS type of collaboration destination user (Company B, trustee), folder ID of collaboration destination user (Company B, trustee), etc., collaboration destination user (Company B, trustee) authentication information of the SaaS concerned.
Therefore, the recipe management unit 102 receives from the user terminal 200a the SaaS type of the collaborating user (Company A/consignor), the SaaS type of the collaborating user (Company A/consignor), and the Folder ID, etc., SaaS authentication information of the collaboration source user (Company A, outsourcer), email address of the collaboration source user (Company A, outsourcer), email address of the collaboration destination user (Company B, outsourcer) , recipe automatic execution timing information, etc., in each table of the recipe management DB 112 and managed. In addition, as recipe information related to a specific recipe in this service received from the user terminal 200b, the SaaS type of the collaboration destination user (company B, trustee), the folder ID of the collaboration destination user (company B, trustee), etc. It has a function of storing and managing the authentication information of the user (Company B/trustee) of the SaaS in each table of the recipe management DB 112 . It also has a function of storing and managing change information of the SaaS type and folder ID received from the user terminal 200a and the user terminal 200b in the SaaS type table and folder ID table of the recipe management DB 112 .

The recipe execution unit 103 has a function of executing recipes. The recipe execution unit 103 executes recipes based on instructions (manually, so to speak) from the recipe execution instruction unit 210 of the user terminal 200a, and automatically executes recipes stored in the recipe automatic execution table of the recipe management DB 112. A recipe is automatically executed at a predetermined timing (schedule) based on the execution timing information. Note that instructions from the recipe execution instruction unit 209 can be issued only to cooperation source users (A company/consignor) whose recipe execution instruction buttons are displayed on the display unit 207 by the user terminal screen management unit 106 of the data linkage server 100. Only the user terminal 200a on the other side, and such an instruction cannot be issued from the user terminal 200b on the side of the cooperation destination user (Company B, trustee).
For example, when the purpose of inter-company data linkage is storage sharing, the recipe execution unit 103 first uses the SaaS authentication information of the linking source user (Company A/consignor) to connect to the SaaS used by Company A via an API. Then, the file is acquired from the folder of the collaboration source user (Company A, outsourcer), and then, using the SaaS authentication information of the collaboration destination user (Company B, outsourcer), API to the SaaS used by Company B Connect and save the file in the folder of the destination user (Company B/consignee). In addition, when the recipe execution is successful, the recipe execution unit 103 causes the user terminal 200a (collaboration source user (company A, consignor)) and the user terminal 200b (cooperation destination user (company B, consignee)) to On the other hand, if the recipe execution fails, only the user terminal 200a cooperating source user (A company/consignor) is notified of the success by e-mail.

The e-mail creation unit 104 stores the e-mail description information stored in the e-mail description information table of the recipe management DB 112, the e-mail address table of the cooperation source user (company A, consignor), and the cooperation destination user (company B, consignor). It has a function to create an e-mail based on each e-mail address stored in the e-mail address table of the trustee).
For example, when the purpose of inter-company data linkage is storage sharing, the information described in the e-mail is text data such as "Storage sharing between partner company A and partner company B".・It is registered as part of the recipe information from the user terminal 200a on the consignor's side.

The e-mail transmission/reception unit 105 has a function of sending e-mails to a predetermined information processing device and receiving e-mails from a predetermined information processing device.

The user terminal screen management unit 106 has a function of displaying a recipe execution instruction button or the like on the display unit 207 of the user terminal 200a of the cooperating user (Company A/entrustor).

The display unit 107 has a function of displaying various screens on a display mechanism such as a display.

The storage unit 108 has a function of storing a user management DB 111, a recipe management DB 112, and the like.
The user management DB 111, the recipe management DB 112, and the like are databases having predetermined tables in which various data of the collaboration source user and the collaboration destination user are stored in association with predetermined user IDs, recipe IDs, and the like. An example of the structure is shown in FIG. For example, there are a user master table, a SaaS type table, a folder ID table, a SaaS authentication information table, an e-mail address table, an e-mail description information table, and a recipe automatic execution table.

Referring to FIG. 2, the user terminal 200a includes an account registration unit 201, a recipe registration unit 202 (only the user terminal 200a contains information described in the e-mail), an e-mail transmission/reception unit 203, a SaaS type change unit 204, a folder change It includes a unit 205 , a SaaS utilization unit 206 , a display unit 207 , a storage unit 208 and a recipe execution instruction unit 209 . Each unit may be implemented by a known input/output I/F, CPU, or the like, or by an HDD or the like.

The account registration unit 201 has a function of performing account registration (user registration) for this service on the data linkage server 100 and a function of requesting user authentication from the data linkage server 100 based on the user ID. there is

The recipe registration unit 202 has a function of setting and registering various types of recipe information in the data link server 100 . Among the recipe information, the information described in the e-mail is, for example, text data such as "cloud storage sharing between partner company A and partner company B" when the purpose of data linking between companies is cloud storage sharing. , is registered only from the user terminal 200a of the cooperation source user (company A/consignor) (not registered from the user terminal 200b of the cooperation destination user (company B/consignor)).

The e-mail transmission/reception unit 203 has a function of sending an e-mail to a predetermined information processing device and receiving an e-mail from a predetermined information processing device.

The SaaS type changing unit 204 changes the SaaS type used by Company A for a specific recipe (the SaaS side server 300a is also replaced with one that provides the changed SaaS). , the changed SaaS type is notified, and the data linkage server 100 has a function of changing the information stored in the SaaS type table of the recipe management DB 112 . Note that even if the information stored in the SaaS type table of the recipe management DB 112 is overwritten and changed by the SaaS type change, the specific recipe itself can be used and operated as it is. Further, as will be described later, regarding the change of the SaaS type used by Company B, the change can be similarly reflected from the user terminal 200b.

The folder change unit 205 notifies the data link server 100 of the changed folder ID and the like when changing the folder ID and the like used by Company A for a specific recipe, and the data link server 100 changes the recipe. It has a function to change the information stored in the folder ID table of the management DB 112 . Note that even if the information stored in the folder ID table of the recipe management DB 112 is overwritten and changed by changing the folder, the specific recipe itself can still be used and operated. Further, as will be described later, regarding the change of folder used by company B, the change can be similarly reflected from the user terminal 200b.

The SaaS utilization unit 206 has a function of utilizing SaaS provided by the SaaS side server 300a of the SaaS used by the user terminal 200a on the A company side.

The display unit 207 has a function of displaying various screens on a display mechanism such as a display.

The storage unit 208 has a function of storing various data.

The recipe execution instruction unit 209 has a function of issuing an instruction to start executing a recipe to the data linkage server 100 . The user of the user terminal 200 a presses a recipe execution instruction button or the like displayed on the display unit 207 by the user terminal screen management unit 106 of the data link server 100 to instruct recipe execution. Note that the recipe execution instruction unit 210 is provided only in the user terminal 200a of the cooperating user (Company A, consignor), and not in the user terminal 200b of the cooperating user (Company B, consignor).

The functions of the user terminal 200b will be described below, and the functions that are substantially the same as those of the user terminal 200a described above are denoted by the same reference numerals.
Referring to FIG. 2, the user terminal 200b includes an account registration unit 201, a recipe registration unit 202, an e-mail transmission/reception unit 203, a SaaS type change unit 204, a folder change unit 205, a SaaS use unit 206, a display A unit 207 and a storage unit 208 are provided. Each unit may be implemented by a known input/output I/F, CPU, or the like, or by an HDD or the like.

The account registration unit 201 has a function of performing account registration (user registration) for this service on the data linkage server 100 and a function of requesting user authentication from the data linkage server 100 based on the user ID. there is

The recipe registration unit 202 has a function of setting and registering various types of recipe information in the data link server 100 .

The e-mail transmission/reception unit 203 has a function of sending an e-mail to a predetermined information processing device and receiving an e-mail from a predetermined information processing device.

The SaaS type changing unit 204 changes the SaaS type used by Company B for a specific recipe (the SaaS side server 300b is also replaced with one that provides the changed SaaS). , the changed SaaS type is notified, and the data linkage server 100 has a function of changing the information stored in the SaaS type table of the recipe management DB 112 . Note that even if the information stored in the SaaS type table of the recipe management DB 112 is overwritten and changed by the SaaS type change, the specific recipe itself can be used and operated as it is.

The folder change unit 205 notifies the data link server 100 of the changed folder ID and the like when changing the folder ID and the like used by Company B with respect to a specific recipe. It has a function to change the information stored in the folder ID table of the management DB 112 . Note that even if the information stored in the folder ID table of the recipe management DB 112 is overwritten and changed by changing the folder, the specific recipe itself can still be used and operated.

The SaaS utilization unit 206 has a function of utilizing SaaS provided by the SaaS side server 300b of the SaaS used by the user terminal 200b on the B company side.

The display unit 207 has a function of displaying various screens on a display mechanism such as a display.

The storage unit 208 has a function of storing various data.

Next, the processing flow of the inter-company data linkage system 10 according to the present embodiment will be described in detail with reference to the explanatory diagram of FIG. 4 and the sequence diagram of FIG. An example of each screen shown in FIGS. 6 and 7 will also be referred to as appropriate.
The following data transmission/reception is carried out via the Internet or a predetermined network shown in FIG.
Note that the SaaS Web API and the like are well-known mechanisms, and various known techniques may be applied. Therefore, only the minimum necessary description will be given here, and detailed description thereof will be omitted.

Referring to FIGS. 4 and 5, first, the account registration unit 201 of the user terminal 200a registers account registration (user registration) for this service in the data link server 100 (step S1). Online sign-up is possible according to browser operations. Note that this step S1 is not essential.
In response, the account management unit 101 of the data linkage server 100 stores the user ID (user name, password, etc.) received from the user terminal 200 a in the user master table of the user management DB 111 of the storage unit 108 .
When logging in to this service for the second time or later, the account registration unit 201 of the user terminal 200a requests the data linkage server 100 for user authentication based on the user ID, and the account management unit 101 of the data linkage server 100 searches the user master table of the user management DB 111 and executes user authentication.
Since this is general account registration and user authentication processing at the time of login, detailed description is omitted.

Next, the recipe registration unit 202 of the user terminal 200a sets and registers various information of the recipe to the data link server 100, and registers the recipe information in a predetermined DB of the data link server 100 (step S2). That is, recipe information related to a "recipe (recipe for cooperation between companies)", which is a package of functions suited to the purpose of data cooperation between companies, is set and registered according to browser operations (see also FIG. 6).
For example, if the purpose of inter-company data linkage is cloud storage sharing, the following is registered as recipe information.
・Collaboration source user (A company, consignor) SaaS type ・Collaboration source user (A company, consignor) folder ID, etc. ・Collaboration source user (A company, consignor) SaaS authentication information (for example, OAuth2. 0 authentication, etc.)
・E-mail address of the source user (Company A, outsourcer) ・Email address of the destination user (Company B, outsourcer) ``Regarding cloud storage sharing between partner company A and partner company B,'' etc. This is optional registration information.)
・Automatic execution timing information (for example, automatically executing a recipe every minute. This is optional registration information.)
In response, the recipe management unit 102 of the data linkage server 100 stores the SaaS type table, the folder ID table, the SaaS authentication information table, the e-mail address table, the e-mail description information table, and the recipe in the recipe management DB 112 of the storage unit 108. Each data is stored in an automatic execution table, etc., and recipe information is managed.

Next, the e-mail transmission/reception unit 105 of the data linkage server 100 sends (sends) an e-mail to the user terminal 200b (company B side) to request the cooperation destination user (company B/trustee) to create an account for this service. Prompted (step S3), the e-mail transmission/reception unit 203 of the user terminal 200b receives the e-mail. Note that if the cooperation destination user (company B/trustee) already has an account for this service, this step S3 and the next step S4 are skipped. Note that this step S3 and the next step S4 are not essential in the first place.

Next, the account registration unit 201 of the user terminal 200b registers account registration (user registration) for this service in the data link server 100 (step S4). Online sign-up is possible according to browser operations.
In response, the account management unit 101 of the data linkage server 100 stores the user ID (user name, password, etc.) received from the user terminal 200b in the user master table of the user management DB 111 of the storage unit .

Next, the e-mail sending/receiving unit 105 of the data linkage server 100 sends an e-mail to the user terminal 200b (company B side) so that the cooperating user (company A/consignor) can, for example, share the cloud storage. A request (desired) is notified (step S5). Data linkage of not only cloud storage sharing but also all SaaS-provided services (for example, large-scale data sharing, transmission and reception of PDF invoices, etc.) can be targeted.
Here, the e-mail creation unit 104 of the data linkage server 100 stores the message information stored in the e-mail description information table of the recipe management DB 112 (optional, if it exists) and the e-mail address table. An e-mail is created based on the e-mail addresses of the collaboration source user and the collaboration destination user.
For example, if the purpose of inter-company data linkage is storage sharing, the message information is text data such as "Regarding storage sharing between partner company A and partner company B". It is registered as a part of the recipe information from the user terminal 200a on the person's side. Note that the message information may be automatically created by determining the message type from an icon or the like selected by the cooperating user (Company A/consignor).

Next, when partner company B agrees to share the cloud storage, the recipe registration unit 202 of the user terminal 200b performs setting registration of various recipe information on the data linkage server 100, register the recipe information in the DB of (step S6). That is, recipe information related to a "recipe (recipe for cooperation between companies)", which is a package of functions suited to the purpose of data cooperation between companies, is set and registered according to browser operations (see also FIG. 7). A registration screen of recipe information paired with the recipe information registered in step S2 may be opened from the link destination of the e-mail sent in step S5. At this time, the collaboration destination user (Company B, trustee) cannot see (hidden) the recipe information of the collaboration source user (Company A, trustee). However, as an option, if there is a check box such as "Disclose the SaaS type to the partner user (Company B/contractor)", the user The SaaS type of the cooperation source user (Company A/entrustor) may be displayed read-only on the display unit 207 of the terminal 200b.
For example, if the purpose of inter-company data linkage is cloud storage sharing, the following is registered as recipe information.
・Collaboration destination user (B company, trustee) SaaS type ・Collaboration destination user (B company, trustee) folder ID, etc. ・Collaboration destination user (B company, trustee) SaaS authentication information The recipe management unit 102 of the data link server 100 stores each data in the SaaS type table, the folder ID table, the SaaS authentication information table, etc. of the recipe management DB 112 of the storage unit 108, and manages the recipe information.

Next, the e-mail sending/receiving unit 105 of the data linkage server 100 sends an e-mail to the user terminal 200a (Company A side), and notifies the cooperation source user (Company A/consignor) to the cooperation destination user ( (Company B, trustee) notifies that the setting registration of the recipe information has been completed (step S7).

Next, the user terminal screen management unit 106 of the data linkage server 100 executes the recipe displayed on the display unit 207 of the user terminal 200a at any timing when the cooperation source user (Company A/consignor) wishes to execute the recipe. Recipe execution is instructed by pressing an instruction button or the like through a browser operation. In response to the pressing of the recipe execution instruction button or the like, the recipe execution instruction unit 209 of the user terminal 200a issues an instruction to start executing the recipe to the data link server 100 (step S8). Note that the recipe execution instruction unit 210 is provided only in the user terminal 200a of the cooperation source user (company A/consignor), and does not exist in the user terminal 200b of the cooperation destination user (company B/contractor). A recipe execution instruction button or the like is not displayed on the display unit 207 of the user terminal 200b.
Also, when the collaboration source user (Company A/consignor) manually executes a recipe, the collaboration source user (Company A/consignor) cannot see the recipe information of the cooperation destination user (Company B/consignor). It is not possible (hidden), so basically you cannot see the SaaS type of the collaboration destination user (company B, trustee). If a check box such as "disclose type" is provided and checked, the SaaS type of the collaboration destination user (company B, trustee) is displayed in a read-only manner on the display unit 207 of the user terminal 200a. good.
This step S8 is automatically performed based on the automatic execution timing information (for example, automatically executing a recipe every minute) stored in the recipe automatic execution table of the recipe management DB 112 of the storage unit 108 of the data linkage server 100. may be replaced with a process of starting execution of the recipe with .

Next, the recipe execution unit 103 of the data linkage server 100 executes the recipe (step S9). For example, when the purpose of inter-company data linkage is storage sharing, the recipe execution unit 103 first uses the SaaS authentication information of the collaboration source user (Company A/consignor) to API connection to the server 300a, acquisition of files (data) from the folder of the collaboration source user (Company A, consignor), and then using the SaaS authentication information of the collaboration destination user (Company B, consignor) The API connection is made to the SaaS side server 300b of the SaaS used by Company B, and the file (data) is saved in the folder of the cooperation destination user (Company B/trustee). The SaaS utilization unit 206 of the user terminal 200a uses SaaS provided by the SaaS side server 300a, and the SaaS utilization unit 206 of the user terminal 200b uses SaaS provided by the SaaS side server 300b. is doing.
The recipe execution unit 103 of the data link server 100 executes recipes based on instructions (manually, so to speak) from the recipe execution instruction unit 210 of the user terminal 200a. The recipe is automatically executed at a predetermined timing (schedule) based on the automatic execution timing information of the recipe.
The recipe execution unit 103 of the data linkage server 100 logically divides the SaaS authentication information of the collaboration source user (Company A, outsourcer) and the SaaS authentication information (security Countermeasure) can be ensured in terms of security by not showing A company and B company to each other. The data collaboration server 100 acquires and holds each authentication information, accesses each SaaS, and executes processing. There is also value in not storing data, i.e., there is no risk of data leakage, and there is no risk of data disappearance. .

Next, when the recipe execution in step S9 is successful, the e-mail transmission/reception unit 105 of the data linkage server 100 sends the user terminal 200a (collaboration source user (A company/consignor)) and the user terminal 200b (collaboration destination). User (Company B/contractor)) is notified by e-mail that the recipe has been successfully executed. It is notified by e-mail to the effect that it was successful only in (step S10). Note that this step S10 is not essential.
In response, the e-mail transmission/reception unit 203 of the user terminal 200a and the e-mail transmission/reception unit 203 of the user terminal 200b receive the e-mail.

Furthermore, the SaaS type changing unit 204 of the user terminal 200a changes the SaaS type used by the cooperating user (Company A/consignor) side with respect to a specific recipe at any timing (the SaaS side server 300a also changes to ), the data linkage server 100 is notified of the changed SaaS type, and the data linkage server 100 changes the information stored in the SaaS type table of the recipe management DB 112. It may be to Even if the information stored in the SaaS type table of the recipe management DB 112 is overwritten and changed due to the SaaS type change, the specific recipe itself is still used and operated (the same recipe execution instruction button, etc. is pressed). recipe can be executed by operation). In addition, by the SaaS type change unit 204 of the user terminal 200b, the SaaS type change can be similarly reflected from the user terminal 200b for the change of the SaaS type used by the cooperation destination user (company B, trustee) side. .
In response, the recipe management unit 102 of the data linkage server 100 stores the SaaS type change information received from the user terminal 200a or the user terminal 200b in the SaaS type table of the recipe management DB 112 and manages it.
The SaaS type may be changed by, for example, selecting the SaaS type from a pull-down menu. It is not necessary to set a new recipe from scratch, and it can be said that an existing recipe can be replaced. In addition, changing the SaaS type can be easily changed independently from both sides of the consignor and the consignee, which improves convenience and is particularly advantageous when there are many affiliated companies. Become.

Furthermore, the folder change unit 205 of the user terminal 200a can change the folder ID, etc. used by the cooperation source user (Company A/consignor) with respect to a specific recipe at an arbitrary timing. On the other hand, the changed folder ID or the like may be notified, and the information stored in the folder ID table of the recipe management DB 112 by the data link server 100 may be changed. Note that even if the information stored in the folder ID table of the recipe management DB 112 is overwritten and changed by changing the folder, the specific recipe itself can be used and operated as it is (the same recipe execution instruction button, etc. can be pressed down). recipe execution). In addition, the folder change unit 205 of the user terminal 200b can similarly reflect the change of the folder used by the cooperation destination user (company B/trustee) from the user terminal 200b.
In response to this, the recipe management unit 102 of the data linkage server 100 stores and manages the folder ID change information received from the user terminal 200a or the user terminal 200b in the folder ID table of the recipe management DB 112 .
The setting of the folder ID and the like may be changed by, for example, selecting a predetermined folder from a pull-down menu or a folder list screen. It is not necessary to set a new recipe from scratch, and it can be said that an existing recipe can be replaced. In addition, both the consignor and the consignee can easily change the settings of the folder ID, etc., independently of each other, which improves convenience. Cases are also assumed, and if there are many affiliated companies, the merit will be particularly large. Furthermore, it is not necessary to use a function provided by a predetermined SaaS (even if the storage destination folder is changed, it can be used as it is if the linkage to the folder ID is changed).

As described above, the collaborating user (Company A, consignor) starts setting and registering recipe information, the collaborating user (Company B, consignee) responds, and the recipe is executed by the collaborating user (Company A, (Consignor) only (only one side, automation setting and manual buttons are displayed only on the screen of the user terminal 200a on the side of Company A.) image of possession). This simplifies the processing flow, facilitates management in the data link server 100, and reduces the processing load. In addition, compared to general cloud storage sharing settings, it is possible to visualize "who, what, and for what purpose" is linked, so it is very beneficial from the viewpoint of security and internal control (IT control) becomes. For example, if an employee arbitrarily shares a folder with another company, there is a risk that the company will not be able to notice it, but this service makes it visible. Every time a recipe is executed, not only company A but also company B are automatically notified by e-mail, etc., so there is no need to create and send individual e-mails or communicate over the phone. Flow is optimized.

Next, examples 1 to 3 of the inter-company data linkage system 10 according to this embodiment will be described.

[Example 1]
As shown in FIG. 8, this is inter-company cloud storage cooperation.
Data (e.g. invoice PDF) sharing with the outside using conventional cloud storage SaaS is to save the file in the SaaS used by the sender, set the recipient as the sharing partner, and send e-mail etc. was notified by However, in this method, data is not saved in the receiver's environment, so in actual operation, there was an operation to copy and back up the shared sender's data to the company's environment. In this service, the operation of both companies can be minimized by linking the SaaS of Company A, which is the consignor, and Company B, which is the consignee.

[Example 2]
As shown in FIG. 9, this is inter-company cloud storage cooperation.
When Company B (for example, a large company with many business partners) collects invoices from multiple trading companies A1, A2, and A3, management should be performed if they were exchanged individually by e-mail, mail, invoice issuing SaaS, etc. becomes complicated. Therefore, it becomes possible to urge each business partner to use this service, and collect receipt of invoice PDFs in a specific folder of the cloud storage SaaS.

[Example 3]
As shown in FIG. 10, it is cooperation between different services.
If you want to securely share a large amount of data between two companies, Company A and Company B, conventionally, it was necessary to connect to the "SFTP server" with an "SFTP client", but with this service, the two companies can completely share data. You can share data even if you are using another application. For example, when company A prohibits access from a specific cloud storage SaaS according to company policy, or when company policy prohibits the use of an SFTP server and client, the data linkage server 100 is an SFTP client. By acting as a company, it is possible to exchange data using the cloud service used by the company. Note that SFTP (SSH File Transfer Protocol) is a file transfer protocol that encrypts files transferred by FTP using "SSH (Secure Shell)".
Furthermore, by performing change registration of the SaaS type, it is also possible to transition from the third embodiment to the first embodiment or the like.

Next, a second embodiment of the invention will be described with reference to the drawings.
In the above-described first embodiment, the setting change of the folder ID, etc., can be changed independently from both sides of the consignor and the trustee. is different in that only the consignor side is permitted.

Next, Example 4 of the inter-company data linkage system 10 according to this embodiment will be described.
[Example 4]
As shown in FIG. 11, this is the linkage between the invoice issuing SaaS and the invoice receiving SaaS linkage. For example, by linking the invoice PDF issued by Company A from the invoice issuance SaaS to the invoice receipt SaaS with AI-OCR function used by Company B, invoices can be issued even if different systems are used. It will be possible to seamlessly link from delivery to receipt. It has the effect of reducing the operation cost related to sending and receiving invoices and preventing omissions in processing. Invoice-receiving SaaS has an intake folder that directly takes in all invoice PDFs, and the processing image is to save the PDF files there. Only Company A/consignor can change the folder ID. Invoice Receipt SaaS is a cloud service that can solve the business flow that has been a problem in accounting, such as collection of invoices, journal entry, transfer, and storage. Subsequent work such as journal entry, registration in the accounting system, creation of transfer data, and data storage can also be completed.
It goes without saying that Examples 1 to 3 described above can also be applied as the present embodiment by partially changing (partially omitted).

Next, a third embodiment of the present invention will be described with reference to the drawings.
In the first embodiment and the second embodiment described above, the folder ID and the like can be changed independently of each other by both the consignor and the consignee. However, the difference is that there is no function/process for changing the folder ID or the like.
It goes without saying that the above-described Examples 1 to 4 can also be applied as the present embodiment by partially changing (partially omitted).

Next, a fourth embodiment of the present invention will be described with reference to the drawings.
In the first embodiment and the second embodiment described above, the folder ID and the like can be changed, but the present embodiment differs in that there is no function or process for changing the folder ID or the like.
Also, in the first to third embodiments described above, the SaaS type can be changed, but this embodiment differs in that there is no function or process for changing the SaaS type.
It goes without saying that the above-described Examples 1 to 4 can also be applied as the present embodiment by partially changing (partially omitted).

According to the above embodiments, when inter-company data is linked between SaaS, manual double input is not required, and security is ensured without passing the company's SaaS authentication information to other companies. Moreover, it is possible to realize a technology that reduces the risk of data leakage and data falsification and contributes to internal control (IT control).

In addition, although not exemplified one by one, the present invention may be implemented with various modifications within the scope of the invention. For example, a program for realizing the function of each device/system may be loaded into each device/system and executed to implement the function of each device/system. Furthermore, the program is transmitted to other computer systems by transmission waves via computer-readable recording media such as CD-ROMs or magneto-optical disks, or via transmission media such as the Internet and telephone lines. good too. Also, some systems may be implemented through human actions. Note that the e-mail as an electronic notification method is only one example, and may be replaced by other methods of electronically notifying each device.
In addition, each of the above-described processes may be performed by combining a plurality of each device, and the known data used at that time may be obtained from a network in cooperation with a known database or the like. , the acquired data may be stored in the database of this system and used. That is, description of details that a person skilled in the art can understand and implement from common technical knowledge may be omitted as appropriate.
Further, as long as the above effects are achieved, the order of the steps in the above sequence diagram may be changed, performed in parallel, or non-essential processing may be omitted.

10 inter-company data linkage system 100 data linkage server 200a, 200b user terminal 300a, 300b SaaS side server

Claims (3)

The data linkage server, the first user terminal of the collaboration source user, and the first SaaS side server are connected via a network, and the data linkage server, the second user terminal of the collaboration destination user, and the second SaaS server are connected via a network. An inter-company data linkage system in which a side server is connected via the network,
The recipe registration unit of the first user terminal stores information related to recipes packaged with functions suited to the purpose of inter-company data linkage, including at least the SaaS type used by the linkage source user, the folder of the linkage source user ID, SaaS authentication information of the collaboration source user, the e-mail address of the collaboration source user, and the e-mail address of the collaboration destination user.
The recipe management unit of the data linkage server stores information about the recipe of the collaboration source user in a predetermined storage unit,
The e-mail transmission/reception unit of the data linkage server notifies the second user terminal of a request for data linkage of the predetermined service provided by the SaaS from the linkage source user by sending an e-mail to the second user terminal,
The recipe registration unit of the second user terminal is information about the recipe, at least the SaaS type used by the collaboration destination user, the folder ID of the collaboration destination user, and the SaaS of the collaboration destination user setting and registering information related to the recipe, including authentication information, to the data linkage server;
The recipe management unit of the data linkage server stores information about the recipe of the collaboration destination user in the predetermined storage unit,
The e-mail transmission/reception unit of the data linkage server transmits the e-mail to the first user terminal to notify the completion of setting and registration of the recipe-related information of the cooperation destination user;
a recipe execution instruction unit of the first user terminal issues an instruction to start execution of the recipe to the data linkage server;
The recipe execution unit of the data link server receives an instruction to start execution of the recipe or automatic execution timing information stored as information on the recipe in the predetermined storage unit by the setting registration from the first user terminal. Execute the recipe based on, API-connect to the first SaaS side server using the SaaS authentication information of the collaboration source user, acquire predetermined data from the folder of the collaboration source user, making the API connection to the second SaaS-side server using the SaaS authentication information of the collaboration destination user, saving the predetermined data in the folder of the collaboration destination user;
The SaaS type changing unit of the first user terminal, when changing the SaaS type of the cooperation source user among the information related to the recipe, notifies the data linkage server of the changed SaaS type,
The SaaS type changing unit of the second user terminal notifies the data linkage server of the changed SaaS type when changing the SaaS type of the cooperation source user among the information related to the recipe. ,
The recipe management unit of the data linkage server stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit,
the folder changing unit of the first user terminal, when changing the folder ID of the cooperation source user among the information related to the recipe, notifies the data link server of the changed folder ID;
The folder changing unit of the second user terminal notifies the data linkage server of the changed folder ID when changing the folder ID of the cooperation source user among the information related to the recipe. ,
The inter-company data linkage system, wherein the recipe management unit of the data linkage server stores the changed folder ID received from the first user terminal or the second user terminal in the predetermined storage unit. Connected to a first user terminal of a collaboration source user and a first SaaS side server via a network, and connected to a second user terminal of a collaboration destination user and a second SaaS side server via the network A connected information processing device,
Information about recipes packaged with functions suited to the purpose of inter-company data linkage, from the recipe registration unit of the first user terminal, at least the SaaS type used by the linkage source user, the type of the linkage source user Receiving setting registration of information related to the recipe including a folder ID, SaaS authentication information of the collaboration source user, the email address of the collaboration source user, and the email address of the collaboration destination user, and storing the collaboration source in a predetermined storage unit a recipe management unit that stores information about the user's recipe;
an e-mail transmitting/receiving unit that transmits an e-mail to the second user terminal and notifies a request for data linkage of a service provided by the predetermined SaaS from the cooperation source user;
The recipe management unit receives information about the recipe from the recipe registration unit of the second user terminal, and includes at least the SaaS type used by the collaboration destination user, the folder ID of the collaboration destination user, and the Accepting setting registration of information about the recipe including authentication information of the SaaS of the collaboration destination user, storing the information about the recipe of the collaboration destination user in the predetermined storage unit,
The e-mail transmission/reception unit sends the e-mail to the first user terminal to notify the completion of setting and registration of the recipe-related information of the cooperation destination user;
An instruction to start execution of the recipe from the recipe execution instruction unit of the first user terminal or automatic execution stored as information on the recipe in the predetermined storage unit by the setting registration from the first user terminal Execute the recipe based on the timing information, use the SaaS authentication information of the collaboration source user to make an API connection to the first SaaS side server, and acquire predetermined data from the folder of the collaboration source user. and further comprising a recipe execution unit that connects the API to the second SaaS-side server using the SaaS authentication information of the collaboration destination user and saves the predetermined data in the folder of the collaboration destination user,
The recipe management unit stores the changed SaaS type received from the first user terminal or the second user terminal in the predetermined storage unit,
The recipe management unit stores the changed folder ID received from the first user terminal or the second user terminal in the predetermined storage unit. Connected to a first user terminal of a collaboration source user and a first SaaS side server via a network, and connected to a second user terminal of a collaboration destination user and a second SaaS side server via the network to the connected information processing device,
Information about a recipe packaged with a function matching the purpose of inter-company data linkage from the recipe registration unit of the first user terminal by the recipe management unit, at least the SaaS type used by the linkage source user, Receiving setting registration of information related to the recipe including the folder ID of the collaboration source user, SaaS authentication information of the collaboration source user, the e-mail address of the collaboration source user, and the e-mail address of the collaboration destination user, and storing in a predetermined storage a process of storing information about the recipe of the cooperating user in a section;
A process of sending an e-mail to the second user terminal by the e-mail transmission/reception unit to notify the request for data cooperation of the predetermined service provided by the SaaS from the cooperation source user;
Information about the recipe from the recipe registration unit of the second user terminal by the recipe management unit, at least the SaaS type used by the cooperation destination user, the folder ID of the cooperation destination user and the A process of accepting setting registration of information about the recipe including authentication information of the SaaS of the collaboration destination user, and storing the information about the recipe of the collaboration destination user in the predetermined storage unit;
a process of sending the e-mail to the first user terminal by the e-mail transmission/reception unit to notify completion of setting and registration of the recipe-related information of the cooperation destination user;
By the recipe execution unit, an instruction to start execution of the recipe from the recipe execution instruction unit of the first user terminal or the setting registration from the first user terminal as information about the recipe in the predetermined storage unit Execute the recipe based on the stored automatic execution timing information, use the authentication information of the SaaS of the collaboration source user to make an API connection to the first SaaS side server, and from the folder of the collaboration source user A process of acquiring predetermined data, making the API connection to the second SaaS-side server using the SaaS authentication information of the collaboration destination user, and storing the predetermined data in the folder of the collaboration destination user. When,
a process of storing the changed SaaS type received from the first user terminal or the second user terminal by the recipe management unit in the predetermined storage unit;
and storing the changed folder ID received from the first user terminal or the second user terminal in the predetermined storage unit by the recipe management unit.

Images