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

Abstract

To enable users to access cloud services within a workflow, each user should have their own dedicated account, rather than having to reuse accounts. [Solution] The information processing system according to the embodiment comprises a creation unit, a registration unit, and an execution unit. The creation unit uses a first account for accessing the cloud service to create a workflow that includes access to the cloud service, in accordance with the operations of the workflow creator. The registration unit registers a second account associated with a user for accessing the cloud service in response to instructions from a user via the network. When the execution unit executes a workflow in response to instructions from a user via the network, it uses the second account, which is registered and associated with the user who made the instruction, instead of the first account to access the cloud service.

Description

Technical Field

[0001] Embodiments of the present invention relate to an information processing system, an information processing apparatus, and an information processing program.

Background Art

[0002] For example, Patent Document 1 defines a workflow that standardizes a series of operations related to a certain task, such as scanning a paper document with an image forming apparatus to obtain an electronic document and uploading this electronic document to a cloud service specified by the user using the account of the cloud service, and executes a service providing system that executes a task based on the defined workflow. In this service providing system, when a logged-in user scans a paper document with an image forming apparatus, after specifying a workflow to start the workflow, by performing scanning of the paper document, it becomes possible to automatically perform the operation contents defined in the workflow.

[0003] By the way, in a workflow such as uploading to a cloud service as described above, a connection to the cloud service is made within the workflow, and the account used for this is the one that is reused as the account used at the time of creating the workflow.

[0004] On the other hand, in various currently used cloud services, at least some of them prohibit reusing accounts by regulations.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] The problem that the embodiments of the present invention aim to solve is to provide an information processing system, information processing device, and information processing program that enable the use of individual user accounts without reusing accounts when accessing cloud services within a workflow. [Means for solving the problem]

[0007] In one embodiment, the information processing system comprises a creation unit, a registration unit, and an execution unit. The creation unit is a unit that creates a workflow in response to the operations of a workflow creator, and creates a workflow that includes access to a cloud service using a first account for accessing a cloud service. The registration unit registers a second account associated with a user for accessing a cloud service in response to instructions from a user via the network. When the execution unit executes a workflow in response to instructions from a user via the network, it accesses the cloud service using the second account, which is registered and associated with the user who made the instruction, instead of the first account. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 is a block diagram showing an example of the overall configuration of a service provision system as an information processing system according to the first embodiment. [Figure 2] Figure 2 is a block diagram showing an example of the configuration of a workflow creation server in a service delivery system. [Figure 3] Figure 3 is a schematic diagram showing an example of the contents stored in the management table storage section of the workflow creation server. [Figure 4] Figure 4 is a block diagram showing an example of the configuration of the creator terminal and user terminal in a service delivery system. [Figure 5] Figure 5 is a block diagram showing an example of the configuration of a user setting server as an information processing device according to the first embodiment. [Figure 6]Figure 6 is a schematic diagram showing an example of the contents stored in the user settings storage section of the user settings server. [Figure 7] Figure 7 is a sequence diagram illustrating the operation during workflow creation in the service delivery system. [Figure 8] Figure 8 is a flowchart showing an example of the workflow creation process performed by the processor of the workflow creation server. [Figure 9] Figure 9 shows an example of the registered services list screen displayed on the creator's terminal when a workflow is created. [Figure 10] Figure 10 is a sequence diagram illustrating the process of registering an account for a user utilizing cloud services within the service provision system. [Figure 11] Figure 11 is a flowchart showing an example of the account registration process performed by the user configuration server's processor. [Figure 12] Figure 12 shows an example of the cloud service list screen displayed on the user's device during account registration. [Figure 13] Figure 13 is a sequence diagram illustrating the operation during workflow execution in the service delivery system. [Figure 14] Figure 14 is a flowchart showing an example of workflow execution processing behavior performed by the user configuration server's processor. [Figure 15] Figure 15 shows an example of an account invalidation warning window that appears on the user terminal when it is confirmed that no valid user account is registered prior to the execution of the workflow. [Figure 16] Figure 16 shows an example of an access denied warning window displayed on the user's terminal when it is confirmed that the cloud service's destination folder cannot be accessed prior to the execution of the workflow. [Figure 17] Figure 17 is a sequence diagram illustrating the operation during workflow creation in the service provision system, which is an information processing system according to the second embodiment. [Figure 18] FIG. 18 is a flowchart showing an example of the operation of a workflow creation process executed by a processor of a workflow creation server. [Figure 19] FIG. 19 is a sequence diagram for explaining the operation at the time of workflow execution in a service providing system as an information processing system according to the third embodiment. [Figure 20] FIG. 20 is a flowchart showing an example of the operation at the time of workflow execution executed by a processor of a user setting server as an information processing apparatus according to the third embodiment. [Figure 21] FIG. 21 is a block diagram showing an example of the overall configuration of a service providing system as an information processing system according to the fourth embodiment. [Figure 22] FIG. 22 is a block diagram showing an example of the configuration of an integrated server as an information processing apparatus according to the fourth embodiment.

Mode for Carrying Out the Invention

[0009] [First Embodiment] FIG. 1 is a block diagram showing an example of the overall configuration of a service providing system as an information processing system according to the first embodiment. In the present embodiment, the service providing system includes, for example, a workflow creation server 1, at least one creator terminal 2, a plurality of user terminals 3, a user setting server 4, and a plurality of cloud service providing servers 5, which are connected via a network NW such as the Internet. The workflow creation server 1 has at least a function of creating a workflow in the service providing system. The creator terminal 2 is a terminal operated by a specific creator such as a dealer, a service man, or an administrator, and functions as a client of the workflow creation server 1 to create a workflow. Each of the plurality of user terminals 3 is a terminal operated by a user, and each functions as a client of the user setting server 4. The user setting server 4 registers information related to the user in response to an instruction from each user terminal 3 and executes the workflow created by the workflow creation server 1. Each of the plurality of cloud service providing servers 5 provides a service for storing an arbitrary file of an arbitrary user in a cloud storage. In the present embodiment, the cloud service providing server 5 preliminarily prepares a shared folder for sharing by the creator and each user in the cloud storage, associated with the accounts of the creator and the user corresponding to the creator.

[0010] The workflow creation server 1 may be an information processing device such as a server computer. FIG. 2 is a block diagram showing an example of the configuration of the workflow creation server 1. As shown in FIG. 2, the workflow creation server 1 includes a processor 11, a main memory 12, an auxiliary storage device 13, a communication interface 14, and the like. These components are connected to each other via a bus line 15 such as a data bus.

[0011] The processor 11 is, for example, a CPU (Central Processing Unit), but is not limited to that. The processor 11 may be multi-core / multi-threaded and capable of executing multiple processes in parallel. The processor 11 may also be an MPU (Micro Processing Unit). The processor 11 has the function of controlling the operation of the entire workflow creation server 1. The processor 11 may be equipped with internal memory and various interfaces. The processor 11 performs various processes by executing programs that are pre-stored in internal memory or auxiliary storage device 13.

[0012] Furthermore, some of the various functions realized by the processor 11 executing a program may be realized by various types of hardware circuits, including integrated circuits such as ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), FPGAs (Field-Programmable Gate Arrays), GPUs (Graphics Processing Units), SoCs (System on a Chip), and PLDs (Programmable Logic Devices). In this case, the processor 11 controls the functions executed by the hardware circuits.

[0013] Main memory 12 is volatile memory. Main memory 12 is working memory or buffer memory. Main memory 12 can store various application programs based on instructions from processor 11. Main memory 12 may also have a temporary storage unit that stores data necessary for executing control programs and application programs stored in auxiliary storage device 13, as well as the execution results of those programs.

[0014] The auxiliary storage device 13 is a non-volatile internal storage device that allows data to be written to and rewritten. The auxiliary storage device 13 employs inexpensive storage devices with low fault tolerance, such as an HDD (Hard Disk Drive), SSD (Solid State Drive), or flash memory. The auxiliary storage device 13 stores control programs, application programs, and various data according to the operational needs of the workflow creation server 1. For example, the auxiliary storage device 13 includes a workflow creation program storage unit 131, a workflow storage unit 132, and a management table storage unit 133.

[0015] The workflow creation program storage unit 131 stores a workflow creation program in the processor 11 that causes the processor 11 to create a workflow in response to instructions from the creator terminal 2. The workflow creation program can, for example, present a creation screen for workflow creation to the user terminal 3, allowing the user to interactively create the workflow through operations from the creator terminal 2. The created workflow could, for example, upload files as needed to a specified folder in the cloud storage provided by the cloud service provider server 5. In creating this workflow, the cloud storage folder is set using account information for accessing the cloud service linked to the company account, which is specified from the creator terminal 2.

[0016] The workflow storage unit 132 is a storage unit that stores workflows created in accordance with instructions from the creator through operations on the creator terminal 2.

[0017] The management table storage unit 133 stores the creator's account specified by the creator terminal 2. Figure 3 is a schematic diagram showing an example of the contents stored in the management table storage unit 133. As shown in Figure 3, for each unique creator ID that identifies the creator, the management table storage unit 133 stores, linked to a unique cloud service ID that identifies the cloud service of the cloud service provider server 5, a company account which is, for example, a company account that has a contract with the cloud service, and a destination folder which identifies the shared folder of the cloud storage to which the files will be uploaded.

[0018] The communication interface 14 is an interface for communicating with external devices on the network NW, namely the creator terminal 2 and the cloud service provider server 5.

[0019] In addition to the configuration shown in Figure 2, the workflow creation server 1 may also have other configurations as needed. For example, the workflow creation server 1 may include a reader device for reading information from a recording medium that stores various information such as programs and data. The programs stored on the recording medium may include workflow creation programs.

[0020] The creator terminal 2 may be an information processing device such as a personal computer. Figure 4 is a block diagram showing an example of the configuration of the creator terminal 2. As shown in Figure 4, the creator terminal 2 includes a processor 21, main memory 22, auxiliary storage device 23, input / output interface 24, input device 25, output device 26, communication interface 27, etc. The processor 21, main memory 22, auxiliary storage device 23, input / output interface 24 and communication interface 27 are connected to each other via a bus line 28 such as a data bus. The input device 25 and output device 26 are connected to the input / output interface 24. In addition to the configuration shown in Figure 4, the creator terminal 2 may have other configurations as needed, or certain configurations may be excluded from the configuration shown in Figure 4.

[0021] The processor 21 is, for example, a CPU, but is not limited to that. The processor 21 may be multi-core / multi-threaded and capable of executing multiple processes in parallel. The processor 21 may also be an MPU. The processor 21 has the function of controlling the operation of the entire creator terminal 2. The processor 21 may be equipped with internal memory and various interfaces. The processor 21 realizes various processes by executing programs that are pre-stored in the internal memory or auxiliary storage device 23. Some of the various functions realized by the processor 21 executing programs may be realized by various types of hardware circuits, including integrated circuits such as ASICs, DSPs, FPGAs, GPUs, SoCs, and PLDs. In this case, the processor 21 controls the functions executed by the hardware circuits.

[0022] Main memory 22 is volatile memory. Main memory 22 is working memory. Main memory 22 can store various application programs based on instructions from processor 21. Main memory 22 can also store data necessary for executing control programs and application programs stored in auxiliary storage device 23, as well as the execution results of those programs.

[0023] The auxiliary storage device 23 is a non-volatile internal storage device that allows data to be written to and rewritten. The auxiliary storage device 23 stores control programs, application programs, and various data according to the operational use of the creator terminal 2. For example, as one of the application programs, the auxiliary storage device 23 can function as a client of the workflow creation server 1 and store a program that causes the workflow creation server 1 to create a workflow. For example, if the workflow creation program of the workflow creation server 1 is a program that provides a predetermined creation screen for workflow creation as a web page, the program stored in the auxiliary storage device 23 may be a program that provides a web browser.

[0024] The input / output interface 24 is an interface with the input device 25 and the output device 26. The input device 25 is used by the creator to input instructions and information necessary for the operation of the creator terminal 2. The input device 25 includes, for example, a keyboard, a mouse or touchpad, and other pointing devices. The input device 25 may also include a touch panel, operation buttons, and other elements located on the display screen of the output device 26. The input device 25 may also include a reader device for reading information from a recording medium that stores various information such as programs and data. The output device 26 includes a display that displays various information generated by the creator terminal 2, such as an LCD monitor, an OLED (Electro-Luminescence) monitor, a projector screen, or a head-mounted display. The output device 26 may also include a speaker that transmits various information to the creator by sound. Furthermore, the output device 26 may include a writer device for writing the information generated by the creator terminal 2 to a recording medium.

[0025] The communication interface 27 is an interface for communicating with the workflow creation server 1, which is an external device on the network NW.

[0026] User terminal 3, like creator terminal 2, may be an information processing device such as a personal computer. That is, user terminal 3 can have the same configuration as creator terminal 2, as shown in parentheses in Figure 4, except that the operator is a user instead of a creator. Specifically, user terminal 3 is equipped with a processor 31, main memory 32, auxiliary storage device 33, input / output interface 34, input device 35, output device 36, communication interface 37, etc. In user terminal 3, auxiliary storage device 33 can function as one of the application programs, acting as a client of user configuration server 4, and can store a program for registering user accounts for various cloud services and executing workflows on user configuration server 4. This program may use a web browser as the user interface.

[0027] The user configuration server 4 is an information processing device according to the first embodiment. The user configuration server 4, like the workflow creation server 1, may be an information processing device such as a server computer. Figure 5 is a block diagram showing an example of the configuration of this user configuration server 4. As shown in Figure 5, the user configuration server 4, like the workflow creation server 1, includes a processor 41, main memory 42, auxiliary storage device 43, communication interface 44, etc. Each of these parts is connected to each other via a bus line 45 such as a data bus. The auxiliary storage device 43 includes a user configuration program storage unit 431, a user configuration storage unit 432, a workflow list storage unit 433, a workflow execution program storage unit 434, and a selected workflow storage unit 435.

[0028] The user configuration program storage unit 431 stores a user configuration program that causes the processor 41 to configure user information based on instructions from the user terminal 3. The user information includes the cloud service of the cloud service provider server 5 used by the user, and the user account, which is the user's account within that cloud service.

[0029] The user configuration storage unit 432 stores information about the configured user. Figure 6 is a schematic diagram showing an example of the contents stored in the user configuration storage unit 432. As shown in Figure 6, the user configuration storage unit 432 stores the configured cloud service ID and user account, linked to a unique user ID that identifies the user. The cloud service ID is identification information that uniquely identifies the cloud service of the cloud service provider server 5 used by the user.

[0030] The workflow list storage unit 433 stores workflow list information that is sent by the workflow creation server 1 each time it creates a workflow, and which shows a list of workflows stored in the workflow storage unit 132 of the workflow creation server 1.

[0031] The workflow execution program storage unit 434 stores a workflow execution program that allows the processor 41 to receive a selection of a workflow to be executed from the user terminal 3, and retrieves the selected workflow from the workflow creation server 1 for execution.

[0032] The selected workflow storage unit 435 stores the selected workflow obtained from the workflow creation server 1.

[0033] The communication interface 44 is an interface for communicating with external devices on the network NW, namely the workflow creation server 1, the user terminal 3, and the cloud service provision server 5. The communication interface 44 is an example of a receiving unit that receives instructions from the user via the network NW.

[0034] In addition to the configuration shown in Figure 5, the user configuration server 4 may also have other configurations as needed. For example, the user configuration server 4 may include a reader device for reading information from a recording medium that stores various information such as programs and data. The programs stored on the recording medium may include at least one of a user configuration program and a workflow execution program.

[0035] The following describes the operation of a service provision system as an information processing system with the above configuration when creating a workflow. Figure 7 is a sequence diagram illustrating the operation of a workflow in the service provision system.

[0036] When the workflow creator instructs the workflow creation server 1 to execute the workflow creation program from the creator terminal 2, a predetermined creation screen provided by the workflow creation server 1 is displayed on the creator terminal 2. Here, the creator logs in to the workflow creation server 1 using their creator ID on this creation screen (step S11). Then, on the creation screen, they select and specify the cloud service to be used for the workflow to be created, and enter a company account that is pre-registered with that cloud service, for example, the account of the company to which the creator belongs (step S12).

[0037] When the workflow creation server 1 obtains the selection results of these cloud services and the company account from the creator terminal 2 (step S13), it logs in to the cloud service provider server 5 of the selected cloud service using that company account (step S14). Then, the workflow creation server 1 searches for a shared folder in the cloud storage provided by the cloud service provider server 5, which is the storage location used in the workflow, and which is linked to the company account (step S15). The workflow creation server 1 stores the cloud service ID, company account, and storage location folder in the management table storage unit 133, linked to the creator ID used to log in to the workflow creation server 1 (step S16). Here, the cloud service ID is identification information that identifies the cloud service selected by the creator, obtained from the creator terminal 2, and the company account is the company account also obtained from the creator terminal 2. The storage location folder is information indicating the searched shared folder.

[0038] The creator performs a creation operation to create the desired workflow on a predetermined creation screen provided by the workflow creation server 1 displayed on the creator terminal 2 (step S17). The workflow creation server 1 creates the workflow according to the operation and saves the created workflow to the workflow storage unit 132 (step S18). If the workflow being created includes work that requires uploading files to cloud storage, the workflow creation server 1 sets and defines the cloud ID and save destination folder stored in the management table storage unit 133 as the upload destination within the workflow.

[0039] Once the workflow creation is complete, the workflow creation server 1 creates a workflow list, which is a list of workflows stored in the workflow storage unit 132, and sends it to the user configuration server 4 (step S19). The workflow list may simply be a list of workflow names, or it may include additional information such as the creator's name or the name of the cloud service used. The user configuration server 4 saves this workflow list sent from the workflow creation server 1 to the workflow list storage unit 433 (step S20).

[0040] The following describes the operation of the workflow creation server 1 to realize the operations during workflow creation. Figure 8 is a flowchart showing an example of the workflow creation process operation performed by the processor 11 of the workflow creation server 1. Figure 8 shows the operation after the creator has logged in using the creator ID. The processor 11 can perform this workflow creation process operation by executing the workflow creation program, which is stored as a control program in the workflow creation program storage unit 131 of the auxiliary storage device 13. Unless otherwise specified, the processing operation of the processor 11 shown in the flowchart of Figure 8 is assumed to transition from ACTn (where n is a natural number) to ACT(n+1). The same applies to the flowcharts of other figures described later.

[0041] As ACT101, the processor 11 transmits screen data, for example, the registered services list screen, to the creator terminal 2 via the network NW using the communication interface 14, thereby displaying the registered services list on the output device 26, which is the display, of the creator terminal 2. The processor 11 can create the registered services list screen based on the information stored in the management table storage unit 133, which is linked to the creator ID of the logged-in creator.

[0042] Figure 9 shows an example of the registered services list screen 261 presented on the creator terminal 2. As shown in Figure 9, the registered services list screen 261 can include a "Create Workflow" button 262, an "Add Account" button 263, and a registered services list 264. The "Create Workflow" button 262 is operated when instructing the creation of a workflow. The "Add Account" button 263 is operated when instructing the addition of an account for a cloud service to be used. The registered services list 264 displays the cloud service ID and company account for registered cloud services. This registered services list 264 can also include a "Delete" button 265, which is operated when instructing the deletion of an account for that cloud service.

[0043] Returning to the explanation of Figure 8, in ACT102, the processor 11 determines whether or not it has received an account registration instruction corresponding to the operation of the "Add Account" button 263, which is transmitted from the creator terminal 2 via the network NW through the communication interface 14. If an account registration instruction has been received, the processor 11 determines YES in ACT102 and proceeds to the process of ACT104, which will be described later. If an account registration instruction has not been received, the processor 11 determines NO in ACT102 and proceeds to the process of ACT103.

[0044] As ACT103, the processor 11 determines whether or not it has received a workflow creation instruction corresponding to the operation of the "Create Workflow" button 262, which is transmitted from the creator terminal 2 via the network NW through the communication interface 14. If a workflow creation instruction has been received, the processor 11 determines YES in ACT103 and proceeds to the process of ACT106 described later. If a workflow creation instruction has not been received, the processor 11 determines NO in ACT103 and proceeds to the process of ACT101 described above.

[0045] As ACT104, processor 11 performs account registration processing. In this account registration processing, processor 11 transmits screen data of the account registration screen to creator terminal 2 via the network NW using communication interface 14, thereby transitioning the display on creator terminal 2 from the registered service list screen 261 to the account registration screen. Processor 11 receives the cloud service and account to be added specified on this account registration screen, transmitted from creator terminal 2 via the network NW, using communication interface 14, and stores them in management table storage unit 133.

[0046] As ACT105, the processor 11 logs in to the cloud service provider server 5 of the specified cloud service via the network NW using the registered company account through the communication interface 14. After that, the processor 11 proceeds to the processing of ACT103.

[0047] As ACT106, the processor 11 presents the workflow creation screen to the creator terminal 2 by sending the workflow creation screen data to the creator terminal 2 via the network NW through the communication interface 14.

[0048] As ACT107, processor 11 displays available shared folders on creator terminal 2. Specifically, processor 11 searches for available shared folders pre-prepared in the cloud storage of the logged-in cloud service provider server 5. Then, processor 11 sends screen data displaying the searched available shared folders on the workflow creation screen to creator terminal 2 via the network NW using the communication interface 14.

[0049] As ACT108, processor 11 registers the searched available shared folders as destination folders in the management table storage unit 133.

[0050] Note that the processing action when an account deletion instruction is received in response to the operation of the "Delete" button 265 is simply to delete the corresponding information from the management table storage unit 133, so it is omitted in Figure 8.

[0051] As ACT109, the processor 11 determines whether or not it has received a workflow setting instruction via the communication interface 14, which is sent from the creator terminal 2 via the network NW in response to a workflow setting operation on the creator terminal 2's workflow creation screen. If the workflow setting instruction has not been received, the processor 11 determines NO in ACT109 and proceeds to the process of ACT111 described later. If the workflow setting instruction has been received, the processor 11 determines YES in ACT109 and proceeds to the process of ACT110.

[0052] As ACT110, the processor 11 temporarily saves the workflow settings in the main memory 12 or auxiliary storage device 13 according to the received workflow setting instructions. The workflow setting instructions include instructions for setting the upload destination if the workflow being created includes work that requires uploading files to cloud storage. Since the instructions for setting the upload destination specify a cloud service ID, the processor 11 retrieves the company account and save location folder corresponding to the specified cloud service ID from the management table storage unit 133 as the upload destination for the workflow to be created and temporarily stores them. After that, the processor 11 proceeds to the processing of ACT106 above and presents a workflow creation screen that reflects the settings of the workflow to be created according to the setting instructions.

[0053] As ACT111, processor 11 determines via the communication interface 14 whether or not it has received a save command sent from creator terminal 2 via the network NW in response to a save operation on the workflow creation screen of creator terminal 2. If no save command has been received, processor 11 determines NO in ACT111 and proceeds to the process of ACT108. If a save command has been received, processor 11 determines YES in ACT111 and proceeds to the process of ACT112.

[0054] As ACT112, processor 11 saves the workflow based on the temporarily stored workflow settings to workflow storage unit 132 as a created workflow.

[0055] As ACT113, processor 11 creates a workflow list, which is a list of workflows stored in workflow storage unit 132, including the workflow registered this time.

[0056] As ACT114, processor 11 sends the created workflow list to user configuration server 4 via the network NW using communication interface 14. Then, processor 11 terminates the workflow creation process operation shown in this flowchart.

[0057] Next, we will explain the operation when a user registers an account to use the cloud service in the information processing system. Figure 10 is a sequence diagram illustrating the operation when a user registers an account to use the cloud service in the service provision system as an information processing system according to the first embodiment.

[0058] When a user instructs the user configuration server 4 to execute the user configuration program from the user terminal 3, a predetermined registration screen provided by the user configuration server 4 is displayed on the user terminal 3. Here, the user logs in to the user configuration server 4 using their user ID on this registration screen (step S31). Then, on the registration screen, the user selects and specifies the cloud services they may use, and enters their account, which is pre-registered with the said cloud service, as the user account (step S32).

[0059] When the user configuration server 4 obtains the selection results of these cloud services and the user account from the user terminal 3, it stores the obtained cloud service ID of the selected cloud service and the obtained user account in the user configuration storage unit 432, linked to the user ID used to log in to the user configuration server 4 (step S33).

[0060] The following describes the operation of the user configuration server 4 to realize the user account registration process described above. Figure 11 is a flowchart showing an example of the account registration process performed by the processor 41 of the user configuration server 4. Note that Figure 11 shows the operation after the user has logged in using their user ID. The processor 41 can perform this account registration process by executing the user configuration program, which is stored as a control program in the user configuration program storage unit 431 of the auxiliary storage device 43.

[0061] As ACT401, the processor 41 transmits screen data, for example, the cloud service list screen, to the user terminal 3 via the network NW using the communication interface 44, thereby displaying the cloud service list on the display, which is the output device 36 of the user terminal 3. The processor 41 can create the cloud service list screen based on pre-registered information on available cloud services and information stored in the user setting storage unit 432 linked to the user ID of the logged-in user.

[0062] Figure 12 shows an example of the cloud service list screen 361 displayed on the user terminal 3. As shown in Figure 12, the cloud service list screen 361 can include an available services list 362 and a "back" button 363. The available services list 362 displays a list of pre-registered available cloud services, and for those cloud services where the logged-in user's account is registered, it displays that user account. The available services list 362 also includes a "delete" button 364 for cloud services where the user account is registered, and an "add" button 365 for cloud services where the user account is not registered. The "delete" button 364 is operated to instruct the deletion of the account for that cloud service. The "add" button 365 is operated to instruct the addition of an account for that cloud service. The "back" button 363 is operated to instruct the termination of this account registration process.

[0063] Returning to the explanation of Figure 11, in ACT402, the processor 41 determines whether or not it has received an account registration instruction corresponding to the operation of the "Add" button 365, transmitted from the user terminal 3 via the network NW through the communication interface 44. If no account registration instruction has been received, the processor 41 determines NO in ACT402 and proceeds to the process of ACT404, which will be described later. If an account registration instruction has been received, the processor 41 determines YES in ACT402 and proceeds to the process of ACT403.

[0064] As ACT403, the processor 41 performs the account registration process. This account registration process involves receiving the specification of the additional cloud service and the account, which are subsequently transmitted from the user terminal 3 via the network NW, through the communication interface 44, and storing them in the user setting storage unit 432. After that, the processor 41 proceeds to the process of ACT401.

[0065] As ACT404, the processor 41 determines whether or not it has received an account deletion instruction in response to the operation of the "delete" button 364, which is transmitted from the user terminal 3 via the network NW through the communication interface 44. If no account deletion instruction has been received, the processor 41 determines NO in ACT404 and proceeds to the process of ACT406 described later. If an account deletion instruction has been received, the processor 41 determines YES in ACT404 and proceeds to the process of ACT405.

[0066] As ACT405, processor 41 performs account deletion processing. The account deletion instruction includes specifying the cloud service to be deleted. Therefore, in this account deletion processing, processor 41 deletes the cloud service ID and user account for the cloud service stored in user setting storage unit 432. After that, processor 41 proceeds to the processing of ACT401.

[0067] As ACT406, the processor 41 determines whether or not it has received a termination instruction in response to the operation of the "back" button 363 via the network NW through the communication interface 44. If no termination instruction has been received, the processor 41 determines NO in ACT406 and proceeds to the process of ACT401. If a termination instruction has been received, the processor 41 determines YES in ACT406 and terminates the account registration process operation shown in this flowchart.

[0068] Next, we will explain the operation during workflow execution in the information processing system. Figure 13 is a sequence diagram illustrating the operation during workflow execution in the service provision system, which is an information processing system according to the first embodiment.

[0069] When a user instructs the user configuration server 4 to execute a workflow execution program from the user terminal 3, a predetermined login screen provided by the user configuration server 4 is displayed on the user terminal 3. Here, the user logs in to the user configuration server 4 using their user ID on this login screen (step S41).

[0070] When a user logs in, the user configuration server 4 sends workflow list screen data based on the workflow list stored in the workflow list storage unit 433 to the user terminal 3, thereby displaying the workflow list to the user terminal 3 (step S42).

[0071] On user terminal 3, select the workflow to execute from this list of workflows (step S43).

[0072] The user configuration server 4 receives the selection of the workflow to be executed, retrieves the selected workflow from the workflow creation server 1, and saves the retrieved workflow to the selected workflow storage unit 435 (step S44). As mentioned above, if the workflow includes tasks that require uploading files to cloud storage when executed, the cloud ID and the destination folder are defined as the upload destination within the workflow.

[0073] Therefore, the user configuration server 4 performs an account validity check (step S45). Specifically, the user configuration server 4 checks whether a user account corresponding to the cloud ID defined in the workflow stored in the selected workflow storage unit 435 is stored, linked to the user ID of the logged-in user stored in the user configuration storage unit 432. If the user account is stored, the user configuration server 4 logs in to the cloud service provider server 5 with that user account (step S46).

[0074] Furthermore, the user configuration server 4 performs a check to determine whether the save location is accessible (step S47). Specifically, the user configuration server 4 checks whether it can access the save location folder defined in the selected workflow storage unit 435 for the workflow stored there. If it can access the folder, the user configuration server 4 starts executing the workflow stored in the selected workflow storage unit 435 (step S48).

[0075] The user terminal 3 performs a series of tasks defined in the workflow (step S49), and the user configuration server 4 executes the workflow based on the results of the work performed on the user terminal 3, that is, it executes each task defined in the workflow (step S50).

[0076] When a file upload is required during the execution of the workflow, the user configuration server 4 uploads the file. The destination for this upload is the storage folder of the cloud storage of the cloud service provider server 5, which is defined in the workflow settings. The user configuration server 4 uploads the file to the storage folder defined in the workflow settings using the user account of the logged-in user stored in the user configuration storage unit 432, instead of the company account used when the workflow was created.

[0077] The cloud service provider server 5, upon receiving the uploaded file, saves the file to the designated storage folder in the cloud storage (step S51).

[0078] The operation of the user configuration server 4 to realize the operation during such workflow execution will be described below. Figure 14 is a flowchart showing an example of workflow execution processing operation performed by the processor 41 of the user configuration server 4. Note that Figure 14 shows the operation after a user has logged in using their user ID. The processor 41 can perform this workflow execution processing operation by executing the workflow execution program, which is stored as a control program in the workflow execution program storage unit 434 of the auxiliary storage device 43.

[0079] As ACT411, the processor 41 transmits data of the workflow list screen, based on the workflow list stored in the workflow list storage unit 433, to the user terminal 3 via the network NW using the communication interface 44.

[0080] As ACT412, the processor 41 determines whether or not it has received a workflow selection instruction corresponding to a workflow selection operation, which is transmitted from the user terminal 3 via the network NW through the communication interface 44. If no workflow selection instruction has been received, the processor 41 determines NO in ACT412 and repeats the process of ACT412. In this way, the processor 41 waits for a workflow selection instruction to be sent. If a workflow selection instruction has been received, the processor 41 determines YES in ACT412 and proceeds to the process of ACT413.

[0081] As ACT413, the processor 41 acquires the workflow indicated by the workflow selection instruction received from the workflow creation server 1 via the network NW through the communication interface 44, and stores the acquired workflow in the selected workflow storage unit 435.

[0082] As ACT414, processor 41 checks whether the user account associated with the user ID of the logged-in user stored in user setting storage unit 432 is valid for the cloud service of the cloud ID defined in the workflow stored in selected workflow storage unit 435.

[0083] As ACT415, processor 41 determines whether the account validity check is valid or not. If the user account is valid, processor 41 determines YES in ACT415 and proceeds to the process of ACT417 described later. If the user account is not valid, processor 41 determines NO in ACT415 and proceeds to the process of ACT416.

[0084] As ACT416, processor 41 sends a warning to the logged-in user's terminal 3 via the network NW through the communication interface 44. Then, processor 41 terminates the workflow execution processing operation shown in this flowchart.

[0085] Upon receiving this warning, user terminal 3 displays an account invalid warning window. Figure 15 shows an example of the account invalid warning window 366 displayed on user terminal 3 when it is confirmed that no valid user account is registered prior to the execution of the workflow. As shown in Figure 15, this account invalid warning window 366 may include a warning message indicating that it is not possible to connect to the save location defined in the workflow selected by the user, and prompting the user to register a valid user account.

[0086] Returning to the explanation of Figure 14, as ACT417, the processor 41 logs in to the cloud service defined in the selected workflow stored in the selected workflow storage unit 435 via the network NW using the user account determined to be valid via the communication interface 44.

[0087] As ACT418, the processor 41 performs a check via the communication interface 44 over the network NW to determine whether or not it is possible to access the destination folder defined in the workflow.

[0088] As ACT419, processor 41 determines whether the access to the destination folder is permitted or not. If access is permitted, processor 41 determines YES in ACT419 and proceeds to the process of ACT421 described later. If access is not permitted, processor 41 determines NO in ACT419 and proceeds to the process of ACT420.

[0089] As ACT420, processor 41 sends a warning to the logged-in user's terminal 3 via the network NW through the communication interface 44. Then, processor 41 terminates the workflow execution processing operation shown in this flowchart.

[0090] Upon receiving this warning, user terminal 3 displays an access denied warning window. Figure 16 shows an example of an access denied warning window 367 displayed on the user terminal when it is confirmed that the user does not have access to the destination folder of the cloud service prior to the execution of the workflow. As shown in Figure 16, this access denied warning window 367 may include a warning message informing the user that they do not have permission to use the destination folder defined in the workflow selected by the user.

[0091] Returning to the explanation of Figure 14, as ACT421, the processor 41 starts executing the selected workflow stored in the selected workflow storage unit 435.

[0092] As ACT422, processor 41 executes each task defined in the workflow and determines whether or not it is necessary to upload a file, i.e., save it to the destination folder in cloud storage. If saving the file to the destination folder is not necessary, processor 41 determines NO in ACT422 and proceeds to the process of ACT424 described below. If saving the file to the destination folder is necessary, processor 41 determines YES in ACT422 and proceeds to the process of ACT423.

[0093] As ACT423, processor 41 sends the file via the network NW using the communication interface 44 to the cloud service provider server 5 of the destination folder defined in the workflow, and saves it to the destination folder in the corresponding cloud storage. At this time, the user account that is the account for the cloud service provider server 5 was logged into in ACT417. Therefore, the file upload is performed using the user account instead of the company account used when the workflow was created. Processor 41 then proceeds to the processing of ACT422.

[0094] As ACT424, the processor 41 determines whether or not to terminate the workflow execution process shown in this flowchart. This determination can be made, for example, by whether or not it has received a termination instruction from the logged-in user's terminal 3 via the network NW through the communication interface 44. Alternatively, this determination may be made by whether or not all the work defined in the workflow has been completed. If the workflow execution process is not to be terminated, the processor 41 determines NO in ACT424 and proceeds to the process in ACT422. If the workflow execution process is to be terminated, the processor 41 determines YES in ACT424 and terminates this workflow execution process.

[0095] As described above, the service provision system as an information processing system according to the first embodiment creates a workflow in response to the operations of the workflow creator on the creator terminal 2, using the processor 11 of the workflow creation server 1. The workflow creation server 1 uses a company account for accessing the cloud service provided by the cloud service provision server 5 to create a workflow that includes access to the cloud service. Thus, the processor 11 of the workflow creation server 1 is an example of a creation unit, and the company account is an example of a first account. Furthermore, the service provision system uses the processor 41 of the user setting server 4 to register a user account associated with a user for accessing the cloud service in response to instructions from the user terminal 3 via the network NW. When executing a workflow in response to instructions from a user via the network NW, the system uses the registered user account associated with the user who made the instruction, instead of the company account, to access the cloud service. Thus, the processor 41 of the user setting server 4 is an example of a registration unit and an execution unit, and the user account is an example of a second account. Furthermore, the user setting server 4, which is an example of an information processing device according to the first embodiment, is configured such that the processor 41 stores a user account associated with a user for accessing the cloud service provided by the cloud service provider server 5 in the user setting storage unit 432 of the auxiliary storage device 13 in response to instructions from a user via the network NW, and when executing a workflow that includes access to a cloud service created using a company account for accessing the cloud service in response to instructions from a user via the network NW, the user account associated with the user who made the instruction, stored in the user setting storage unit 432, is used instead of the company account to access the cloud service. The user setting storage unit 432 is an example of a storage unit that stores information based on instructions received from a user. Thus, in the first embodiment, a workflow including access to a cloud service is created using a company account, and users register a user account to execute the workflow. When a user executes the workflow, they use their user account instead of the company account to access the cloud service. Therefore, according to the first embodiment, when accessing a cloud service within a workflow, it becomes possible to use a separate account for each user without reusing accounts.

[0096] Furthermore, in the first embodiment, when executing a workflow, the processor 41 of the user configuration server 4 checks whether a user account associated with the user who issued the instruction is registered. If it is not registered, the processor does not execute the workflow and instead issues a warning to the user terminal 3 of the user who issued the instruction via the network NW. Therefore, according to the first embodiment, if a user does not have a registered cloud service account associated with them when executing a workflow, a warning is issued and the workflow is not executed. This allows users to receive a warning before executing a workflow, preventing them from executing unnecessary workflows.

[0097] Furthermore, in the first embodiment, the cloud service provided by the cloud service provider server 5 is a service that provides cloud storage having a destination folder for saving files. When a user executes a workflow, the processor 41 of the user setting server 4 checks whether it is possible to access the destination folder of the cloud storage using the user account associated with the user who made the registered instruction. If access is not possible, the processor does not execute the workflow and instead sends a warning to the user terminal 3 of the user who made the instruction via the network NW. Therefore, according to the first embodiment, when a user executes a workflow, the system checks in advance whether the user has access to the workflow's storage location using the cloud service account associated with the individual user. If access is not possible, a warning is issued and the workflow is not executed. This allows the user to receive a warning before executing the workflow, preventing unnecessary workflow execution by the user.

[0098] [Second Embodiment] In the first embodiment described above, the cloud service provider server 5 pre-prepared a shared folder in the cloud storage that would serve as the save destination, linked to the accounts of the creator and the user corresponding to that creator. However, it is not necessary for the shared folder to be prepared in advance. For example, the shared folder may be created when the workflow is created. This will be described below as the second embodiment. Note that the same configuration and operation as in the first embodiment will be denoted by the same reference numerals as in the first embodiment, and their explanation will be omitted.

[0099] Figure 17 is a sequence diagram illustrating the operation during workflow creation in the service provision system, which is an information processing system according to the second embodiment.

[0100] Steps S11 to S14 are as described in the first embodiment with reference to Figure 7.

[0101] In step S12, the creator selects a cloud service from creator terminal 2 and enters the company account, and then further specifies the destination folder to be created in the cloud storage (step S61). This destination folder specification includes the user account of each user who will share the shared folder.

[0102] The workflow creation server 1, in response to the creator terminal 2 specifying the destination folder, instructs the cloud service provider server 5, which is logged in with a company account, to configure the specified destination folder (step S62).

[0103] Upon receiving this instruction, the cloud service provider server 5 registers the user accounts of the users to be shared and secures the specified destination folder in the cloud storage (step S63). Subsequently, steps S17 to S21 described in the first embodiment are carried out.

[0104] The following describes the operation of the workflow creation server 1 to achieve the operations described above when creating a workflow. Figure 18 is a flowchart showing an example of the workflow creation process operation performed by the processor 11 of the workflow creation server 1.

[0105] The processes of ACT101 to ACT106 and ACT108 to ACT114 are as described in the first embodiment with reference to Figure 8. In the first embodiment, the processor 11 searched for available shared folders as ACT107 and displayed them on the creator terminal 2. In contrast, in this embodiment, the processor 11 performs a process to create an available shared folder in the cloud storage of the logged-in cloud service provider server 5.

[0106] Specifically, following the processing of ACT106, the processor 11, as ACT121, determines whether or not it has received a save location instruction sent from the creator terminal 2 via the network NW through the communication interface 14. This save location instruction is sent in response to the operation of specifying the save location folder and the user accounts of each user who will share that save location folder on the account registration screen of the creator terminal 2. That is, the save location instruction includes information about the save location folder and the user account. Alternatively, it may include only the save location folder and then proceed to the specification of the user account. If the save location instruction has not been received, the processor 11 determines NO in ACT121 and repeats the processing of ACT121. In this way, the processor 11 waits for the save location instruction to be sent. If the save location instruction has been received, the processor 11 determines YES in ACT121 and proceeds to the processing of ACT122.

[0107] As ACT122, processor 11 instructs the cloud service provider server 5, which is logged in with a company account, to create the destination folder. Specifically, processor 11 instructs the cloud service provider server 5 via the network NW using the communication interface 44 to create the specified destination folder. Processor 11 also sends a list of accounts that share the destination folder to the cloud service provider server 5 via the network NW using the communication interface 44. These accounts include company accounts and user accounts. After that, processor 11 proceeds to the process of ACT108 described above.

[0108] As described above, the service provision system as an information processing system and the user setting server 4 as an information processing device according to the second embodiment can achieve the same effects as the information processing system and information processing device according to the first embodiment.

[0109] Furthermore, according to the second embodiment, when the processor 11 of the workflow creation server 1 sets a destination folder, which is a cloud service to be accessed, during the workflow to be created, it registers the sharing settings for that folder and the user accounts that will share, i.e., access, with the cloud service provider server 5 that provides the said cloud service. Therefore, according to the information processing system and information processing device of the second embodiment, the cloud service to be accessed and the user account that can access it can be registered with the cloud service when creating a workflow, even if they have not been registered with the cloud service in advance.

[0110] [Third Embodiment] The first and second embodiments described above were examples in which it was assumed that the user's user account had already been registered with the user configuration server 4 when the user executed the workflow. However, it is not necessary for the user account to be registered in advance. Some workflows do not require access to cloud services. Therefore, the user account may be registered only when the workflow execution has started and access to cloud services becomes necessary. This will be described below as the third embodiment. Note that the same configuration and operation as in the first embodiment will be denoted by the same reference numerals as in the first embodiment, and their explanation will be omitted.

[0111] In this embodiment, the operation for prior user account registration, as described with reference to Figures 10 and 11, is not performed. Furthermore, the user configuration program is incorporated into the workflow execution program, and therefore, the auxiliary storage device 43 of the user configuration server 4 does not have a user configuration program storage unit 431. Alternatively, the user configuration program storage unit 431 may be retained so that it calls the workflow execution program from another workflow execution program.

[0112] Figure 19 is a sequence diagram illustrating the operation during workflow execution in the service provision system as an information processing system according to the third embodiment.

[0113] Steps S41 to S44 are as described in the first embodiment with reference to Figure 13.

[0114] In this embodiment, once the user setting server 4 has acquired the workflow selected from the workflow creation server 1 in step S44 and saved it in the selected workflow storage unit 435, it immediately starts executing that workflow (step S48).

[0115] Then, as described in the first embodiment, the user terminal 3 performs the work related to the work defined in the workflow (step S49), and the user setting server 4 executes the workflow based on the work results on the user terminal 3, that is, it executes each work defined in the workflow (step S50).

[0116] When a file upload is required during the execution of the workflow, the user configuration server 4 performs an account validity check (step S71). Specifically, the user configuration server 4 checks whether a user account corresponding to the cloud ID defined in the workflow saved in the selected workflow storage unit 435 is stored, linked to the user ID of the logged-in user stored in the user configuration storage unit 432. If the user account is saved, the user configuration server 4 proceeds to step S74, which will be described later. However, if the user account is not saved, it displays a user account input screen on the user terminal 3. This input screen includes information about the cloud service of the destination folder defined in the workflow.

[0117] On this input screen, the user enters their user account for the cloud service (step S72).

[0118] The user configuration server 4 obtains this user account from the user terminal 3 and registers it (step S73). That is, the user configuration server 4 stores the cloud service ID of the cloud service defined in the workflow and the obtained user account in the user configuration storage unit 432, linked to the user ID used to log in to the user configuration server 4.

[0119] Then, the user configuration server 4 logs in to the corresponding cloud service provider server 5 using the registered user account (step S74).

[0120] Furthermore, the user configuration server 4 performs a check to determine whether the save location is accessible (step S75). Specifically, the user configuration server 4 checks whether it can access the save location folder defined in the workflow stored in the selected workflow storage unit 435. If it can access the folder, the user configuration server 4 uses the user account of the logged-in user stored in the user configuration storage unit 432 to upload the file to the save location folder of the cloud storage of the cloud service provider server 5, which is defined in the workflow.

[0121] As described in the first embodiment, the cloud service provider server 5 that receives the uploaded file saves the file to the destination folder of the cloud storage specified as the upload destination (step S51).

[0122] The following describes the operation of the user configuration server 4 to achieve the behavior during the execution of such a workflow. Figure 20 is a flowchart showing an example of the workflow execution processing operation performed by the processor 41 of the user configuration server 4.

[0123] The processing of ACT411 to ACT413 is as described in the first embodiment with reference to Figure 14.

[0124] In this embodiment, the processor 41 retrieves a workflow from the workflow creation server 1 in ACT 413 and stores it in the selected workflow storage unit 435. Then, as ACT 421, it starts executing the selected workflow stored in the selected workflow storage unit 435.

[0125] As ACT422, the processor 41 executes each task defined in the workflow and determines whether or not it is necessary to upload a file, i.e., save it to the destination folder in cloud storage. If it is not necessary to save the file to the destination folder, the processor 41 determines NO in ACT422 and proceeds to the process of ACT424 described later. If it is necessary to save the file to the destination folder, the processor 41 determines YES in ACT422 and, in this embodiment, proceeds to the process of ACT414.

[0126] The processing of ACT414 to ACT416 is as described in the first embodiment.

[0127] After sending an account invalidation warning to the user terminal 3 in ACT416, the processor 41, in this embodiment, sends an account acquisition request to the user terminal 3 via the network NW through the communication interface 44 as ACT431. This account acquisition request may include data from the user account input screen, which includes information about the cloud service of the destination folder defined in the workflow settings.

[0128] As ACT432, the processor 41 performs the account registration process. This account registration process involves receiving the user account transmitted from the user terminal 3 via the network NW through the communication interface 44 and storing it in the user setting storage unit 432. After that, the processor 41 proceeds to the process of ACT417.

[0129] The processing of ACT417 to ACT420 is as described in the first embodiment. However, in ACT419, if access is possible and the result is determined to be YES, in the first embodiment the process proceeds to ACT421, but in this embodiment the process proceeds to ACT423. The processing of ACT423 is as described in the first embodiment, and the processor 41 then proceeds to the processing of ACT422.

[0130] As described above, the service provision system as an information processing system and the user setting server 4 as an information processing device according to the third embodiment can achieve the same effects as the information processing system and information processing device according to the first embodiment.

[0131] Furthermore, according to the third embodiment, the processor 41 of the user configuration server 4 accepts registration of a user account from the user through operations on the user terminal 3 when executing a workflow. Therefore, according to the third embodiment, the necessary user account can be obtained by the user's user terminal 3 only when executing a workflow that uses a user account. Conversely, when executing a workflow that does not use a user account, the unnecessary prior user account registration operation can be omitted.

[0132] [Fourth Embodiment] The first to third embodiments described above used two independent servers, a workflow creation server 1 and a user configuration server 4. However, the functions of both servers may be implemented by a single server. This will be described below as the fourth embodiment. Note that the same configuration and operation as in the first embodiment will be denoted by the same reference numerals as in the first embodiment, and their explanation will be omitted.

[0133] Figure 21 is a block diagram showing an example of the overall configuration of a service provision system as an information processing system according to the fourth embodiment. In this embodiment, instead of the workflow creation server 1 and user setting server 4 shown in Figure 1, an integrated server 6 is provided as an information processing device according to the fourth embodiment.

[0134] Figure 22 is a block diagram showing an example of the configuration of the integrated server 6. The integrated server 6 may be an information processing device such as a server computer. As shown in Figure 22, the integrated server 6 includes a processor 61, main memory 62, auxiliary storage device 63, communication interface 64, etc. These parts are connected to each other via a bus line 65 such as a data bus. The processor 61, main memory 62, communication interface 64 and bus line 65 are the same as the processor 11, main memory 12, communication interface 14 and bus line 15 of the workflow creation server 1 in the first embodiment. The auxiliary storage device 63 is a non-volatile internal storage that allows data to be written to and rewritten. For example, the auxiliary storage device 63 employs an inexpensive storage device with low fault tolerance, such as an HDD, SSD, or flash memory. The auxiliary storage device 63 stores control programs, application programs, and various data, etc., depending on the operational use of the integrated server 6. For example, the auxiliary storage device 63 includes a workflow creation / execution program storage unit 631, a workflow storage unit 632, a management table storage unit 633, a user setting program storage unit 634, and a user setting storage unit 635.

[0135] The workflow creation and execution program storage unit 631 stores a workflow creation and execution program that causes the processor 61 to create a workflow in response to instructions from the creator terminal 2, and also executes the workflow selected by the user terminal 3.

[0136] The workflow storage unit 632 and the management table storage unit 633 are the same as the workflow storage unit 132 and the management table storage unit 133 of the workflow creation server 1 described in the first embodiment. Furthermore, the user setting program storage unit 634 and the user setting storage unit 635 are the same as the user setting program storage unit 431 and the user setting storage unit 432 described in the first embodiment.

[0137] Furthermore, the auxiliary storage device 63 of the integrated server 6 does not have a storage unit corresponding to the workflow list storage unit 433 and the selected workflow storage unit 435 described in the first embodiment.

[0138] In this configuration, the integrated server 6 functions as the workflow creation server 1 in the first embodiment for the creator terminal 2. That is, the processor 61 saves the workflow defined by the creator's operation on the creator terminal 2 to the workflow storage unit 632, according to the workflow creation and execution program stored in the workflow creation and execution program storage unit 631.

[0139] Furthermore, the integrated server 6 functions as the user configuration server 4 in the first embodiment for the user terminal 3. That is, when registering a user account, the processor 61 creates a workflow list based on the workflow stored in the workflow storage unit 632, according to the user configuration program stored in the user configuration program storage unit 634, and provides it to the user terminal 3. The processor 61 then obtains the results of the cloud service selection by the user operation on the user terminal 3 and the user account, and saves them in the user configuration storage unit 635.

[0140] Furthermore, when executing a workflow, the processor 61 accepts a selection of a workflow to be executed from the workflows stored in the workflow storage unit 632 from the user terminal 3, according to the workflow creation and execution program stored in the workflow creation and execution program storage unit 631, and then executes the selected workflow.

[0141] As described above, the service provision system as an information processing system and the integrated server 6 as an information processing device according to the fourth embodiment realize the functions of the workflow creation server 1 and the user setting server 4 according to the first embodiment. Therefore, the information processing system and information processing device according to the fourth embodiment can achieve the same effects as the information processing system and information processing device according to the first embodiment.

[0142] The above explanation assumes that the integrated server 6 implements the functions of the workflow creation server 1 and user setting server 4 according to the first embodiment. However, it goes without saying that the integrated server 6 can also implement the functions of the workflow creation server 1 and user setting server 4 according to the second or third embodiment.

[0143] [Other embodiments] The embodiments of the information processing system and information processing device have been described above, but the embodiments are not limited thereto.

[0144] For example, in the first to third embodiments, the workflow creation server 1 sends the workflow list to the user configuration server 4, which stores it in the workflow list storage unit 433. However, the user configuration server 4 may request and obtain the workflow list from the workflow creation server 1 as needed. This eliminates the need for the workflow list storage unit 433.

[0145] Furthermore, the integrated server 6 as an information processing device according to the fourth embodiment may be a multi-function peripheral (MFP; hereinafter abbreviated as MFP) located in the workplace, which has at least a scanning function, a printing function, and a communication function. In this case, for example, the scanning function can also function as a user terminal 3 that performs the task of scanning documents. That is, by the integrated server 6 functioning as a user terminal 3, the service provision system does not need to have a user terminal 3. In this case, the workflow created may be, for example, one that performs optical character recognition on scanned documents and uploads them to cloud storage in a specified file format.

[0146] Furthermore, the information processing flow described above by processors 11, 21, or 61, as explained with reference to the flowchart, is merely an example and is not limited to this order. The order of processing can be changed, or multiple processes can be performed in parallel, as long as there is no conflict with preceding or succeeding processes.

[0147] In the above embodiment, a company account was used as an example for the first account, but the invention is not limited to this. The first account may be a group account for various groups such as organizations, groups, doujin circles, apartment buildings, neighborhood associations, etc. In other words, the first account may be an account set up for a group of multiple users.

[0148] Furthermore, in the above embodiment, various control programs are pre-stored in the auxiliary storage device 13 of the workflow creation server 1, the auxiliary storage device 23 of the user setting server 4, or the auxiliary storage device 63 of the integrated server. In this regard, control programs that are individually transferred to each server may be written to the writable storage device provided by each server in response to operations by an administrator or other person. These control programs can be transferred by storing them on a removable computer-readable storage medium or by communication over a network. The computer-readable storage medium can take any form as long as it can store programs and is readable by the device, such as a CD-ROM or memory card.

[0149] In addition, several embodiments of the present invention have been described, but these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be carried out in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments are included within the scope of the invention and within the scope of the invention and its equivalents as described in the claims. [Explanation of symbols]

[0150] 1…Workflow creation server, 2…Creator terminal, 3…User terminal, 4…User configuration server, 5…Cloud service provider server, 6…Integration server, 11,21,31,41,61…Processor, 12,22,32,42,62…Main memory, 13,23,33,43,63…Auxiliary storage device, 14,27,37,44,64…Communication interface, 15,28,38,45,65…Bus line, 24,34…Input / output interface, 25,35…Input device, 26,36…Output device, 131…Workflow creation program storage unit, 132,632…Workflow storage unit, 133,633…Management table storage unit, 431,634…User configuration program storage unit, 432,635…User configuration storage unit, 261…Registered service list screen, 262... "Create Workflow" button, 263... "Add Account" button, 264... Registered Services List, 265, 364... "Delete" button, 361... Cloud Services List screen, 362... Available Services List, 363... "Back" button, 365... "Add" button, 366... ​​Account Invalid Warning Window, 367... Access Denied Warning Window, 433... Workflow List Storage Unit, 434... Workflow Execution Program Storage Unit, 435... Selected Workflow Storage Unit, 631... Workflow Creation / Execution Program Storage Unit, NW... Network.

Claims

1. A creation unit that creates a workflow in response to the operations of the workflow creator, and which uses a first account for accessing a cloud service to create a workflow that includes access to the said cloud service, A registration unit that registers a second account linked to a user for accessing the cloud service in response to instructions from the user via the network, When executing the workflow in response to instructions from the user via the network, the execution unit accesses the cloud service using the second account, which is registered and linked to the user who issued the instructions, instead of the first account. An information processing system equipped with the following features.

2. The information processing system according to claim 1, wherein the execution unit, when executing the workflow, checks whether the second account associated with the user who issued the instruction is registered, and if it is not registered, does not execute the workflow but issues a warning to the user who issued the instruction via the network.

3. The aforementioned cloud service is a service that provides cloud storage having a destination folder for saving files, The information processing system according to claim 1 or 2, wherein when the user executes the workflow, the execution unit checks whether the user can access the destination folder in the cloud storage using the second account associated with the user who issued the registered instruction, and if access is not possible, it does not execute the workflow and issues a warning to the user who issued the instruction via the network.

4. A registration unit that stores a second account linked to a user for accessing cloud services in a storage unit in response to instructions from the user via the network, When executing a workflow that includes access to the cloud service, created using a first account for accessing the cloud service, in response to instructions from the user via the network, the execution unit accesses the cloud service using a second account associated with the user who made the instructions, which is stored in the storage unit, instead of the first account. An information processing device equipped with the following features.

5. When executed by the processor of an information processing device comprising: a receiving unit that receives instructions from a user via a network; a storage unit that stores information based on the received instructions from the user; and a processor that performs processing based on the received instructions and the stored information, The aforementioned processor, In response to the received instruction, the storage unit is made to store a second account associated with the user for accessing the cloud service. In response to the received instruction, when executing a workflow that includes access to the cloud service created using a first account for accessing the cloud service, instead of using the first account, the system uses a second account associated with the user who issued the instruction, which is stored in the storage unit, to access the cloud service. Information processing program.

Images