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

Abstract

Embodiments of the present invention relate to an information processing system, an information processing device, and an information processing program product, which make it possible to use an account of each user without repeatedly using the account when accessing a cloud service within a workflow. An information processing system according to an embodiment includes a creation unit, a registration unit, and an execution unit. The creation unit creates a workflow including accessing a cloud service in accordance with an operation by a workflow producer using a first account for accessing the cloud service. The registration unit registers a second account associated with the user for accessing the cloud service in accordance with an instruction from the user via the network. When executing the workflow in accordance with an instruction from the user via the network, the execution unit accesses the cloud service in place of the first account using the registered second account associated with the instructed user.

Description

Technical Field

[0001] The embodiments of the present invention relate to information processing systems, information processing devices, and information processing program products. Background Technology

[0002] For example, existing technology discloses a service provisioning system that defines workflows and executes business processes based on these defined workflows. In these workflows, a series of processes related to a specific business task are standardized according to the job content. For instance, scanning a paper original using an image forming device to create an electronic document, and then uploading this electronic document to a user-specified cloud service using a cloud service account. In this service provisioning system, when a logged-in user scans a paper original using an image forming device, after specifying and starting the workflow, the scanning of the paper original automatically executes the job content defined in the workflow.

[0003] However, in the aforementioned workflow of uploading to the cloud service, a connection is established with the cloud service within the workflow, but the account used for this connection is the same account that was used when the workflow was created.

[0004] On the other hand, at least some of the various cloud services currently in use prohibit the repeated use of accounts through their regulations. Summary of the Invention

[0005] The technical problem that the invention aims to solve

[0006] The technical problem to be solved by the embodiments of the present invention is to provide an information processing system, an information processing device, and an information processing program, so that when accessing cloud services within a workflow, each user's account can be utilized without repeatedly using the account.

[0007] Technical solutions for solving technical problems

[0008] In one embodiment, the information processing system includes a creation unit, a registration unit, and an execution unit. The creation unit creates a workflow based on the operations of a workflow creator, using a first account for accessing cloud services to create a workflow that includes accessing cloud services. The registration unit registers a second account associated with a user for accessing cloud services based on instructions from the user via the network. When the execution unit executes the workflow based on instructions from the user via the network, it uses the registered second account associated with the user who gave the instructions, instead of the first account, to access the cloud services. Attached Figure Description

[0009] Figure 1 This is a block diagram illustrating an example of the overall structure of a service provisioning system as an information processing system according to the first embodiment.

[0010] Figure 2 This is a block diagram illustrating an example of the structure of a workflow creation server in a service provision system.

[0011] Figure 3 This is a schematic diagram illustrating an example of the stored content in the management table storage section of a workflow creation server.

[0012] Figure 4 This is a block diagram illustrating an example of the structure of the producer terminal and the user terminal in a service providing system.

[0013] Figure 5 This is a block diagram illustrating an example of the structure of a user setting server in the information processing apparatus according to the first embodiment.

[0014] Figure 6 This is a schematic diagram illustrating an example of the content stored in the user settings storage section of a user settings server.

[0015] Figure 7 It is a sequence diagram used to illustrate the actions involved in creating a workflow in a service provision system.

[0016] Figure 8 This is a flowchart illustrating an example of workflow creation processing actions performed by the processor of the workflow creation server.

[0017] Figure 9 This is an example of a screenshot showing a list of registered services displayed on the creator's terminal during workflow creation.

[0018] Figure 10 It is a sequence diagram used to illustrate the actions of a user registering an account using cloud services in a service provider system.

[0019] Figure 11 This is a flowchart illustrating an example of an account registration process executed by the server's processor, as configured by the user.

[0020] Figure 12 This is an example of a cloud service overview screen displayed on a user's terminal during account registration.

[0021] Figure 13 It is a sequence diagram used to illustrate the actions of workflow execution in a service provision system.

[0022] Figure 14 This is a flowchart illustrating an example of the processing actions performed when a user-defined server processor executes a workflow.

[0023] Figure 15 This is an example of an invalid account warning window displayed on the user's terminal when it is confirmed that no valid user account has been registered before the workflow is executed.

[0024] Figure 16 This is an example of an inaccessible warning window displayed on the user terminal when it is confirmed that the cloud service's save destination folder cannot be accessed before the workflow is executed.

[0025] Figure 17 This is a sequence diagram illustrating the actions involved in creating a workflow in a service provisioning system of an information processing system according to the second embodiment.

[0026] Figure 18 This is a flowchart illustrating an example of workflow creation processing actions performed by the processor of the workflow creation server.

[0027] Figure 19 This is a sequence diagram illustrating the actions during workflow execution in a service provision system of an information processing system according to the third embodiment.

[0028] Figure 20 This is a flowchart illustrating an example of the processing actions performed by the processor of the user setting server, which is part of the information processing apparatus according to the third embodiment, during workflow execution.

[0029] Figure 21 This is a block diagram illustrating an example of the overall structure of a service provisioning system as an information processing system according to the fourth embodiment.

[0030] Figure 22 This is a block diagram illustrating an example of the structure of an integrated server, which is part of the information processing apparatus according to the fourth embodiment.

[0031] Explanation of reference numerals in the attached figures

[0032] 1: Workflow creation server; 2: Creator terminal; 3: User terminal; 4: User setting server; 5: Cloud service provider server; 6: Integrated server; 11, 21, 31, 41, 61: Processors; 12, 22, 32, 42, 62: Main memory; 13, 23, 33, 43, 63: Auxiliary storage devices; 14, 27, 37, 44, 64: Communication interfaces; 15, 28, 38, 45, 65: Bus; 24: Input / output interface; 25, 35: Input devices; 26, 36: Output devices; 131: Workflow creation program storage unit; 132, 632: Workflow storage unit; 133, 633: Management table storage unit; 431, 6 34: User settings storage; 432, 635: User settings storage; 261: Service overview screen after registration; 262: "Workflow Creation" button; 263: "Account Addition" button; 264: Service overview after registration; 265, 364: "Delete" button; 361: Cloud service overview screen; 362: Available services overview; 363: "Back" button; 365: "Add" button; 366: Invalid account warning window; 367: Inaccessible warning window; 433: Workflow overview storage; 434: Workflow execution program storage; 435: Select workflow storage; 631: Workflow creation / execution program storage; NW: Network. Detailed Implementation

[0033] [First Implementation Method]

[0034] Figure 1 This is a block diagram illustrating an example of the overall structure of a service provisioning system as an information processing system according to the first embodiment. In this embodiment, the service provisioning system includes, for example, a workflow creation server 1 connected via a network such as the Internet, at least one creator terminal 2, multiple user terminals 3, a user configuration server 4, and multiple cloud service provisioning servers 5. The workflow creation server 1 at least has the function of creating workflows within the service provisioning system. Creator terminals 2 are terminals operated by specific creators such as distributors, service personnel, and managers, and function as clients of the workflow creation server 1 to create workflows. The multiple user terminals 3 are terminals operated by users, and each functions as a client of the user configuration server 4. The user configuration server 4 registers user-related information according to instructions from each user terminal 3 and executes the workflow created by the workflow creation server 1. The multiple cloud service provisioning servers 5 each provide a service to save any file of any user in cloud storage. It should be noted that in this embodiment, the cloud service provisioning servers 5 are associated with the respective accounts of the creator and the users corresponding to that creator, and shared folders for sharing among the creator and users are pre-prepared in the cloud storage.

[0035] Workflow creation server 1 can also have information processing equipment such as server computers. Figure 2 This is a block diagram illustrating an example of the structure of workflow creation server 1. For example... Figure 2 As shown, the workflow creation server 1 includes a processor 11, a main memory 12, an auxiliary storage device 13, a communication interface 14, etc. These components are interconnected via a data bus or other bus 15.

[0036] Processor 11 is, for example, a CPU (Central Processing Unit), but is not limited to this. Processor 11 can be a multi-core / multi-threaded processor capable of executing multiple processes in parallel. Alternatively, processor 11 can also be an MPU (Microprocessor). Processor 11 has the function of controlling the overall operation of the workflow creation server 1. Processor 11 may also have internal memory and various interfaces. Processor 11 performs various processes by executing pre-stored programs in internal memory or auxiliary storage devices 13.

[0037] It should be noted that some of the various functions implemented by the processor 11 executing programs can also be implemented using various forms of hardware circuits, including 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.

[0038] Main memory 12 is volatile memory. Main memory 12 is either working memory or buffer memory. Main memory 12 is capable of storing various application programs based on commands from processor 11. In addition, main memory 12 may have a temporary storage section that stores data required to execute control programs and application programs stored in auxiliary storage device 13, as well as the execution results of these programs.

[0039] The auxiliary storage device 13 is a non-volatile internal memory capable of writing and rewriting data. In the auxiliary storage device 13, inexpensive storage devices with low failure tolerance, such as HDDs (Hard Disk Drives), SSDs (Solid State Drives), or flash memory, are used. The auxiliary storage device 13 stores control programs, application programs, and various data according to the application 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.

[0040] Workflow creation program storage unit 131 stores a workflow creation program that enables processor 11 to create workflows according to instructions from creator terminal 2. The workflow creation program may, for example, be a program that prompts a creation screen for workflow creation to user terminal 3, allowing for interactive workflow creation through operations from creator terminal 2. The created workflow may, for example, involve uploading files to a designated folder in cloud storage provided by cloud service provider server 5 as needed. In the creation of this workflow, the cloud storage folder is set using account information specified by creator terminal 2 for accessing the cloud service associated with the company account.

[0041] Workflow storage unit 132 is a storage unit that stores workflows created according to instructions from the maker through the operation of the maker terminal 2.

[0042] The management table storage unit 133 stores the account of the maker specified by the maker terminal 2. Figure 3 This is a schematic diagram illustrating an example of the stored content in the management table storage unit 133. For example... Figure 3 As shown, the management table storage unit 133 stores, for each identified creator's unique creator ID, a unique cloud service ID associated with the cloud service provided by the cloud service provider server 5, a company account that has signed a contract with the cloud service, such as a company account, and a save destination folder for the shared folder of the cloud storage that is determined to be the upload destination.

[0043] Communication interface 14 is an interface for communicating with the manufacturer terminal 2, which is an external device, and the cloud service provider server 5 on the network NW.

[0044] It should be noted that, in addition to workflow creation server 1 Figure 2 In addition to the structure shown, other structures may be provided as needed. For example, the workflow creation server 1 may include a reading device for reading information from a recording medium that stores various information such as programs and data. The program stored in the recording medium may include a workflow creation program.

[0045] The creator terminal 2 can be an information processing device such as a personal computer. Figure 4 This is a block diagram illustrating an example of the structure of the maker's terminal 2. For example... Figure 4 As shown, 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, and communication interface 27. The processor 21, main memory 22, auxiliary storage device 23, input / output interface 24, and communication interface 27 are interconnected via a data bus or other bus 28. Input device 25 and output device 26 are connected to input / output interface 24. It should be noted that, in addition to... Figure 4 In addition to the structure shown, it can also have structures as needed, and can also be derived from... Figure 4 Remove specific structures from the structure shown.

[0046] Processor 21 may be a CPU, but is not limited to this. Processor 21 may be a multi-core / multi-threaded processor capable of executing multiple processes in parallel. Alternatively, processor 21 may be an MPU. Processor 21 has the function of controlling the overall operation of the manufacturer's terminal 2. Processor 21 may also have internal memory and various interfaces. Processor 21 performs various processes by executing pre-stored programs in internal memory or auxiliary storage devices 23. It should be noted that some of the various functions implemented by processor 21 executing programs may also be implemented by various forms of hardware circuits, including integrated circuits such as ASICs, DSPs, FPGAs, GPUs, SoCs, and PLDs. In this case, processor 21 controls the functions executed by the hardware circuits.

[0047] Main memory 22 is volatile memory. Main memory 22 is working memory. Main memory 22 can store various application programs based on commands from processor 21. In addition, main memory 22 can store data required to execute control programs and application programs stored in auxiliary storage device 23, as well as the execution results of these programs.

[0048] Auxiliary storage device 23 is a non-volatile internal memory capable of writing and rewriting data. Auxiliary storage device 23 stores control programs, application programs, and various data according to the intended use of the creator terminal 2. For example, as one of the application programs, auxiliary storage device 23 functions as a client of workflow creation server 1 and can store programs used to enable workflow creation server 1 to create workflows. For example, if the workflow creation program of workflow creation server 1 is a program that provides a specified creation screen for creating workflows as a web page, the program stored in auxiliary storage device 23 could be a program that provides a web browser.

[0049] Input / output interface 24 is an interface with input device 25 and output device 26. Input device 25 is used by the creator to input instructions and information required for the actions of the creator terminal 2. Input device 25 includes, for example, pointer devices such as keyboards, mice, and touchpads. Additionally, input device 25 may include touch panels, operation buttons, etc., configured on the display screen of output device 26. Furthermore, input device 25 may include a reading device for reading information from a recording medium storing various information such as programs and data. Output device 26 includes displays such as liquid crystal monitors, organic EL (Electroluminescence) monitors, projector screens, head-mounted displays, etc., that display various information generated by the creator terminal 2. Additionally, output device 26 may include a speaker that transmits various information to the creator through sound. Furthermore, output device 26 may include a writing device for writing the information generated by the creator terminal 2 into a recording medium.

[0050] Communication interface 27 is an interface used to communicate with workflow creation server 1, which is an external device on network NW.

[0051] User terminal 3, like producer terminal 2, can be an information processing device such as a personal computer. That is, user terminal 3, by having an operator act instead of the producer, can achieve the same functionality. Figure 4 As shown in square brackets, the user terminal 3 has the same structure as the manufacturer's terminal 2. That is, the user terminal 3 includes 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 the user terminal 3, the auxiliary storage device 33 functions as a client of the user configuration server 4, serving as one of the application programs. It can store programs used to register user accounts for various cloud services or execute workflows on the user configuration server 4. This program can also use a web browser as the user interface.

[0052] User setting server 4 is the information processing device involved in the first embodiment. Like workflow creation server 1, user setting server 4 may also have information processing equipment such as server computer. Figure 5 This is a block diagram illustrating an example of the structure of the user-configured server 4. For example... Figure 5 As shown, similar to workflow creation server 1, user setting server 4 includes processor 41, main memory 42, auxiliary storage device 43, communication interface 44, etc. These components are interconnected via bus 45, such as data bus. Auxiliary storage device 43 includes user setting program storage unit 431, user setting storage unit 432, workflow overview storage unit 433, workflow execution program storage unit 434, and workflow selection storage unit 435.

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

[0054] User setting storage unit 432 stores the user's information. Figure 6 This is a schematic diagram illustrating an example of the saved content of the user-defined storage unit 432. For example... Figure 6 As shown, the user setting storage unit 432 stores the set cloud service ID and user account in association with a unique user ID used to identify the user. The cloud service ID is unique identification information that identifies the cloud service provided by the cloud service provider server 5 used by the user.

[0055] Workflow overview storage unit 433 stores workflow overview information, which represents a list of workflows sent by workflow creation server 1 each time a workflow is created and stored in workflow storage unit 132 of workflow creation server 1.

[0056] The workflow execution program storage unit 434 stores the workflow execution program, which enables the processor 41 to receive the selection of the workflow to be executed from the user terminal 3, obtain the selected workflow from the workflow creation server 1, and execute it.

[0057] The selected workflow is stored in the Workflow Storage Unit 435, which is obtained from the Workflow Creation Server 1.

[0058] Communication interface 44 is an interface used to communicate with workflow creation server 1, user terminal 3, and cloud service provider server 5, which are external devices on network NW. Communication interface 44 is an example of a receiving unit that receives instructions from the user via network NW.

[0059] It should be noted that, in addition to user-configured server 4, Figure 5 In addition to the structure shown, other structures may be provided as needed. For example, the user configuration server 4 may include a reading device for reading information from a recording medium storing various information such as programs and data. The program stored in the recording medium may include at least one of a user configuration program and a workflow execution program.

[0060] The following describes the actions involved in creating a workflow within the service provision system of this information processing system. Figure 7 It is a sequence diagram used to illustrate the actions involved in creating a workflow in a service provision system.

[0061] When the workflow creator instructs the workflow creation program to be executed from the creator terminal 2 to the workflow creation server 1, the prescribed creation screen provided by the workflow creation server 1 is displayed on the creator terminal 2. Here, the creator logs into the workflow creation server 1 using their own creator ID on this creation screen (step S11). Then, on the creation screen, the creator selects the cloud service to be used in the created workflow and enters a company account that is pre-registered in the cloud service, such as an account belonging to the creator's company (step S12).

[0062] After obtaining the cloud service selection results and company account from the creator terminal 2 (step S13), the workflow creation server 1 logs into the cloud service provider server 5 of the selected cloud service using the company account (step S14). Then, the workflow creation server 1 retrieves the save destination used within the workflow, namely the shared folder prepared in the cloud storage provided by the cloud service provider server 5 and associated with the company account (step S15). The workflow creation server 1 saves the cloud service ID, company account, and save destination folder in the management table storage unit 133 in association with the creator ID used in the login of the workflow creation server 1 (step S16). Here, the cloud service ID is obtained from the creator terminal 2 and is used to identify the cloud service selected by the creator; the company account is also obtained from the creator terminal 2. In addition, the save destination folder is information indicating the retrieved shared folder.

[0063] The creator performs the workflow creation operation in the specified 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 in the workflow storage unit 132 (step S18). It should be noted that in the creation of this workflow, if the created workflow includes work that requires uploading files to cloud storage, the workflow creation server 1 sets the cloud ID and save destination folder stored in the management table storage unit 133 as the upload destination in the workflow.

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

[0065] The actions of the workflow creation server 1 used to implement such workflow creation are described below. Figure 8 This is a flowchart illustrating an example of a workflow creation processing action performed by the processor 11 of the workflow creation server 1. It should be noted that... Figure 8 This demonstrates the actions taken by the creator after logging in using their creator ID. The processor 11 executes the workflow creation process by running a workflow creation program, which is a control program stored in the workflow creation program storage unit 131 of the auxiliary storage device 13. It should be noted that, unless otherwise stated, Figure 8 The flowchart shows that the processing action of processor 11, after ACTn (where n is a natural number), transitions to ACT(n+1). It should be noted that the flowcharts for other diagrams described later are similar.

[0066] As ACT101, processor 11 sends screen data, such as a registration completion service overview screen, to creator terminal 2 via network NW through communication interface 14, thereby displaying the registration completion service overview on the display of output device 26, which is creator terminal 2. Processor 11 can create the registration completion service overview screen based on information stored in management table storage unit 133 associated with the creator ID of the registered creator.

[0067] Figure 9 This is an example of a screenshot 261 showing a completed service overview displayed in the maker's terminal 2. (See screenshot 261.) Figure 9 As shown, the completed service overview screen 261 can include a "Workflow Creation" button 262, an "Account Addition" button 263, and a completed service overview 264. The "Workflow Creation" button 262 is used when instructing the creation of a workflow. The "Account Addition" button 263 is used when instructing the addition of an account for the cloud service to be used. The completed service overview 264 displays the cloud service ID and company account for the registered cloud service. Additionally, the completed service overview 264 can include a "Delete" button 265, used when instructing the deletion of an account for the cloud service.

[0068] Return to Figure 8 The following is an explanation. As in ACT102, the processor 11 determines whether it has received an account registration instruction sent via the network NW from the creator terminal 2 through the communication interface 14, corresponding to the operation of the "Account Addition" button 263. If an account registration instruction is received, the processor 11 determines it as YES in ACT102 and proceeds to the processing in ACT104 (described later). If no account registration instruction is received, the processor 11 determines it as NO in ACT102 and proceeds to the processing in ACT103.

[0069] In ACT103, processor 11 determines whether it has received a workflow creation instruction corresponding to the operation of the "Workflow Creation" button 262, sent from the creator terminal 2 via network NW through communication interface 14. If a workflow creation instruction is received, processor 11 determines it as YES in ACT103 and proceeds to the processing of ACT106 described later. If no workflow creation instruction is received, processor 11 determines it as NO in ACT103 and proceeds to the processing of ACT101 mentioned above.

[0070] As ACT104, processor 11 performs account registration processing. In this account registration process, processor 11 sends screen data of the account registration screen to the creator terminal 2 via network NW through communication interface 14, thereby changing the display on the creator terminal 2 from the registration completion service overview screen 261 to the account registration screen. Processor 11 receives the additional cloud services and accounts specified in the account registration screen sent from the creator terminal 2 via network NW through communication interface 14, and stores them in the management table storage unit 133.

[0071] As ACT105, processor 11 logs into cloud service provider server 5, which uses the cloud service specified by the registered company account, via network NW through communication interface 14. Then, processor 11 transfers to the processing of ACT103 described above.

[0072] As ACT106, processor 11 sends the screen data of the workflow production screen to the producer terminal 2 via network NW through communication interface 14, thereby prompting the producer terminal 2 with the workflow production screen.

[0073] As ACT107, processor 11 causes creator terminal 2 to display available shared folders. Specifically, processor 11 retrieves pre-prepared available shared folders from the cloud storage of the logged-in cloud service provider server 5. Then, processor 11 sends screen data via communication interface 14 through network NW to creator terminal 2, displaying the retrieved available shared folders in the workflow production screen.

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

[0075] It should be noted that the processing action when receiving an account deletion instruction corresponding to the "Delete" button 265 only involves deleting the corresponding information from the management table storage unit 133. Figure 8 omitted.

[0076] In ACT109, the processor 11 determines whether it has received a workflow setting instruction sent from the creator terminal 2 via the network NW based on workflow setting operations in the workflow creation screen of the creator terminal 2 through the communication interface 14. If no workflow setting instruction is received, the processor 11 determines NO in ACT109 and proceeds to the processing of ACT111 described later. If a workflow setting instruction is received, the processor 11 determines YES in ACT109 and proceeds to the processing of ACT110.

[0077] As ACT110, processor 11 temporarily saves the workflow settings according to the received workflow setting instructions in main memory 12 or auxiliary storage device 13. It should be noted that the workflow setting instructions include instructions for setting the upload destination in cases where the created workflow includes work requiring file uploads to cloud storage. The upload destination setting instruction is designated as a cloud service ID, so in the created workflow, processor 11, as the upload destination, retrieves the company account and save destination folder corresponding to the designated cloud service ID from the management table storage unit 133 and temporarily stores them. Then, processor 11 transfers to the processing of ACT106 described above, prompting a workflow creation screen that reflects the settings of the workflow to be created according to the setting instructions.

[0078] In ACT111, processor 11 determines whether it has received a save instruction sent from the creator terminal 2 via network NW based on the save operation of the workflow in the workflow creation screen of the creator terminal 2 through communication interface 14. If no save instruction is received, processor 11 determines NO in ACT111 and proceeds to the process described in ACT108. If a save instruction is received, processor 11 determines YES in ACT111 and proceeds to the process described in ACT112.

[0079] As ACT112, processor 11 saves the workflow set based on temporary storage as the created workflow in workflow storage unit 132.

[0080] As ACT113, processor 11 creates a workflow overview, including the workflow registered this time, stored in workflow storage unit 132.

[0081] As ACT114, processor 11 sends a summary of the created workflow to user configuration server 4 via network NW through communication interface 14. Then, processor 11 terminates the workflow creation processing action shown in the flowchart.

[0082] Next, the actions of users registering accounts using cloud services in the information processing system will be explained. Figure 10This is a sequence diagram illustrating the actions of a user registering an account using a cloud service in a service provisioning system of an information processing system according to the first embodiment.

[0083] When a user instructs the user configuration server 4 to execute the user configuration procedure from the user terminal 3, the 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 own user ID on the registration screen (step S31). Then, on the registration screen, the user selects a cloud service that may be used and enters their own account, which is pre-registered in that cloud service, as the user account (step S32).

[0084] When the user setting server 4 obtains the selection results of these cloud services and the user account from the user terminal 3, it associates the user ID used to log in to the user setting server 4 with the cloud service ID of the selected cloud service and the user account obtained (step S33).

[0085] The following describes the actions of the user setting server 4 used to implement the actions when registering such user accounts. Figure 11 This is a flowchart illustrating an example of an account registration processing action performed by the processor 41 of the user-configured server 4. It should be noted that... Figure 11 The actions performed after a user logs in using their user ID are shown. The processor 41 can perform the account registration process by executing the user setting program, which is a control program stored in the user setting program storage unit 431 of the auxiliary storage device 43.

[0086] As ACT401, processor 41 sends screen data, such as a cloud service overview screen, to user terminal 3 via network NW through communication interface 44, thereby displaying the cloud service overview on the display of output device 36, which is user terminal 3. Processor 41 can create the cloud service overview screen based on information of pre-registered available cloud services and information stored in user setting storage unit 432 associated with the user ID of the logged-in user.

[0087] Figure 12 This is an example of a cloud service overview screen 361 displayed on user terminal 3. For example... Figure 12As shown, the cloud service overview screen 361 can include an overview of available services 362 and a "back" button 363. The available service overview 362 displays a list of pre-registered available cloud services, and for accounts registered with logged-in users in these cloud services, it displays the user's account. Additionally, the available service overview 362 includes a "delete" button 364 for cloud services with registered user accounts and an "add" button 365 for cloud services without registered user accounts. The "delete" button 364 is used when instructing the deletion of an account for that cloud service. The "add" button 365 is used when instructing the addition of an account for that cloud service. The "back" button 363 is used when instructing the end of the account registration process.

[0088] Return to Figure 11 The following is an explanation. As ACT402, processor 41 determines whether it has received an account registration instruction corresponding to the operation of the "Add" button 365, sent from user terminal 3 via network NW through communication interface 44. If no account registration instruction is received, processor 41 determines it as NO in ACT402 and proceeds to the processing of ACT404 (described later). If an account registration instruction is received, processor 41 determines it as YES in ACT402 and proceeds to the processing of ACT403.

[0089] As ACT403, processor 41 performs account registration processing. This account registration processing involves receiving the cloud service specification and account to be added from user terminal 3 via network NW through communication interface 44, and storing it in user setting storage unit 432. Then, processor 41 transfers to the processing of ACT401 described above.

[0090] In ACT404, processor 41 determines whether it has received an account deletion instruction corresponding to the operation of the "Delete" button 364 from user terminal 3 via network NW through communication interface 44. If no account deletion instruction is received, processor 41 determines it as NO in ACT404 and proceeds to ACT406 (described later). If an account deletion instruction is received, processor 41 determines it as YES in ACT404 and proceeds to ACT405.

[0091] As ACT405, processor 41 performs account deletion processing. The account deletion instruction includes the specification of 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 the user settings storage unit 432. Then, processor 41 transfers to the processing of ACT401 described above.

[0092] In ACT406, processor 41 determines whether it has received an end instruction corresponding to the operation of the "Back" button 363 via network NW through communication interface 44. If no end instruction is received, processor 41 determines it as NO in ACT406 and proceeds to the processing in ACT401 above. If an end instruction is received, processor 41 determines it as YES in ACT406 and terminates the account registration processing action shown in the flowchart.

[0093] Next, the actions performed during workflow execution in the information processing system will be explained. Figure 13 This is a sequence diagram illustrating the actions performed during workflow execution in a service provisioning system of an information processing system according to the first embodiment.

[0094] When a user instructs the user configuration server 4 to execute a workflow execution program from the user terminal 3, the 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 own user ID on this login screen (step S41).

[0095] When a user logs in, the user setting server 4 sends data based on the workflow overview screen stored in the workflow overview storage unit 433 to the user terminal 3, thereby prompting the user terminal 3 to display the workflow overview (step S42).

[0096] In user terminal 3, select the workflow to be executed from the workflow overview (step S43).

[0097] The user sets the server 4 to accept the selection of the workflow to be executed, obtains the selected workflow from the workflow creation server 1, and saves the obtained workflow in the selected workflow storage unit 435 (step S44). As mentioned above, when the execution of the workflow includes a task that requires uploading files to cloud storage, the cloud ID and the save destination folder are set as the upload destination in the workflow.

[0098] Therefore, the user configuration server 4 performs an account validity check (step S45). That is, the user configuration server 4 confirms whether the user account corresponding to the cloud ID defined in the workflow settings stored in the selection workflow storage unit 435 is stored in association with 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 uses the user account to log in to the cloud service provider server 5 (step S46).

[0099] Furthermore, the user setting server 4 performs a check on whether the save destination can be accessed (step S47). That is, the user setting server 4 confirms whether it is possible to access the save destination folder defined in the workflow settings stored in the selected workflow storage unit 435. If it is possible to access, the user setting server 4 begins to execute the workflow stored in the selected workflow storage unit 435 (step S48).

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

[0101] When executing this workflow, if a file needs to be uploaded, the user-configured server 4 uploads the file. The upload destination is the cloud storage destination folder of the cloud service provider server 5, which is defined in the workflow. The user-configured server 4 uses the user account of the logged-in user stored in the user-configured storage unit 432 instead of the company account used when creating the workflow to upload the file to the save destination folder defined in the workflow.

[0102] The cloud service provider server 5 that receives the uploaded file saves the file in the save destination folder of the cloud storage designated as the upload destination (step S51).

[0103] The following describes the actions of the user-defined server 4 used to implement such workflow execution. Figure 14 This is a flowchart illustrating an example of the processing actions performed during the execution of a workflow configured by the user on server 4's processor 41. It should be noted that... Figure 14 The actions performed after a user logs in using their user ID are shown. The processor 41 can execute the workflow execution processing actions by executing the workflow execution program, which is a control program stored in the workflow execution program storage unit 434 of the auxiliary storage device 43.

[0104] As ACT411, processor 41 sends data based on the workflow overview screen stored in workflow overview storage unit 433 to user terminal 3 via communication interface 44 and network NW.

[0105] As ACT412, processor 41 determines whether it has received a workflow selection instruction corresponding to the workflow selection operation sent from user terminal 3 via network NW through communication interface 44. If no workflow selection instruction is received, processor 41 determines it as NO in ACT412 and repeats the processing of ACT412. Thus, processor 41 waits for the transmission of the workflow selection instruction. If a workflow selection instruction is received, processor 41 determines it as YES in ACT412 and proceeds to the processing of ACT413.

[0106] As ACT413, processor 41 obtains the workflow represented by the received workflow selection instruction from workflow creation server 1 via network NW through communication interface 44, and saves the obtained workflow in selection workflow storage unit 435.

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

[0108] As ACT415, processor 41 determines whether the account validity check result is valid. If the user account is valid, processor 41 determines it as YES in ACT415 and proceeds to the processing in ACT417 (described later). If the user account is invalid, processor 41 determines it as NO in ACT415 and proceeds to the processing in ACT416.

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

[0110] On user terminal 3 that received the warning, an invalid account warning window is displayed. Figure 15 This is an example of an invalid account warning window 366 displayed in user terminal 3 when it is confirmed that no valid user account has been registered before the workflow is executed. Figure 15 As shown, the invalid account warning window 366 is in a state where it cannot connect to the save destination defined in the workflow selected by the user, and can include a warning message that prompts the registration of a valid user account.

[0111] Return to Figure 14 The explanation is as follows. As ACT417, the processor 41 uses a user account that has been determined to be valid via the network NW through the communication interface 44 to log in to the cloud service defined in the selected workflow stored in the selected workflow storage unit 435.

[0112] As ACT418, processor 41 checks via network NW through communication interface 44 whether it can access the save destination folder defined in the workflow.

[0113] As ACT419, processor 41 determines whether the access permission check for the destination folder can be performed. If access is permitted, processor 41 determines it as YES in ACT419 and proceeds to the processing of ACT421 (described later). If access is not permitted, processor 41 determines it as NO in ACT419 and proceeds to the processing of ACT420.

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

[0115] On user terminal 3 that received the warning, an inaccessible warning window is displayed. Figure 16 This is an example of an inaccessibility warning window (367) displayed on the user's terminal when it is confirmed that the cloud service's save destination folder cannot be accessed before the workflow is executed. Figure 16 As shown, the inaccessible warning window 367 can include a warning message that notifies the user that the save destination folder defined in the selected workflow does not have access permissions.

[0116] Return to Figure 14 The explanation is as follows. As ACT421, processor 41 begins to execute the selected workflow stored in the selection workflow storage unit 435.

[0117] As ACT422, processor 41, while executing the tasks defined in the workflow, prohibits file uploads, that is, prohibits saving files to the cloud storage destination folder. If saving files to the destination folder is not required, processor 41 determines NO in ACT422 and proceeds to ACT424 (described later). If saving files to the destination folder is required, processor 41 determines YES in ACT422 and proceeds to ACT423.

[0118] As in ACT423, processor 41 sends a file via communication interface 44 through network NW to the cloud service provider server 5, which is defined as the save destination folder in the workflow, and saves it to the corresponding cloud storage save destination folder. At this time, in ACT417 above, the user account that is the account of the cloud service provider server 5 logs in to the cloud service provider server 5. Therefore, the file upload is implemented through the user account, rather than through the company account used when the workflow was created. After this, processor 41 moves on to the processing of ACT422 above.

[0119] As ACT424, processor 41 determines whether the processing action during the execution of the workflow shown in the flowchart should be terminated. This determination can be made, for example, based on whether an termination instruction has been received from the logged-in user's terminal 3 via the network NW through the communication interface 44. Alternatively, this determination can be based on whether all the work defined in the workflow has been completed. If the processing action during workflow execution is not terminated, processor 41 determines NO in ACT424 and proceeds to the processing in ACT422 described above. If the processing action during workflow execution is terminated, processor 41 determines YES in ACT424 and terminates the processing action during workflow execution.

[0120] As described above, the service provision system of the information processing system according to the first embodiment creates a workflow based on the operations of the workflow creator on the creator terminal 2 via the processor 11 of the workflow creation server 1. The workflow creation server 1 uses a company account for accessing cloud services provided by the cloud service provider server 5 to create a workflow that includes accessing cloud services. 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 registers a user account associated with the user for accessing cloud services via the processor 41 of the user setting server 4 according to instructions from the user terminal 3 via the network NW. When executing a workflow according to instructions from the user via the network NW, the registered user account associated with the user who gave the instructions is used 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.

[0121] Furthermore, as an example of the information processing apparatus according to the first embodiment, the user setting server 4 is configured such that the processor 41, based on an instruction from a user via the network NW, causes the user setting storage unit 432 of the auxiliary storage device 13 to store user accounts associated with users accessing cloud services provided by the cloud service provider server 5. When executing a workflow that includes accessing cloud services using a company account for accessing cloud services, based on an instruction from a user via the network NW, the user account associated with the user who gave the instruction, stored in the user setting storage unit 432, is used instead of the company account to access the cloud services. The user setting storage unit 432 is an example of a storage unit that stores information based on the received instructions from the user.

[0122] Thus, in the first embodiment, a workflow including accessing cloud services is pre-created using a company account, and users pre-register user accounts to execute this workflow. When a user executes the workflow, the user account is used instead of the company account to access the cloud service. Therefore, according to the first embodiment, when accessing cloud services within a workflow, each user's account can be utilized without repeatedly using the account.

[0123] In addition, in the first embodiment, when the processor 41 of the user setting server 4 executes the workflow, it checks whether a user account associated with the user who made the instruction is registered. If no account is registered, the workflow is not executed, and a warning is sent to the user terminal 3 of the user who made the instruction via the network NW.

[0124] Therefore, according to the first embodiment, if a user does not have a cloud service account associated with their personal account when executing a workflow, a warning is issued and the workflow is not executed. Thus, the user can receive a warning before the workflow is executed, which can prevent the user from executing useless workflows.

[0125] In addition, in the first embodiment, the cloud service provided by the cloud service provider server 5 is a cloud storage service that provides a destination folder for saving files. When the user executes the workflow, the processor 41 of the user setting server 4 checks whether the destination folder for saving the cloud storage can be accessed using the user account associated with the user who made the instruction. If access is not possible, the workflow is not executed, and a warning is issued to the user terminal 3 of the user who made the instruction via the network NW.

[0126] Therefore, according to the first embodiment, when a user executes a workflow, the cloud service account associated with the user confirms in advance whether access to the workflow's storage destination is permitted. If access is denied, a warning is issued and the workflow is not executed. Thus, the user can receive a warning before the workflow is executed, preventing the user from executing useless workflows.

[0127] [Second Implementation]

[0128] The first embodiment described above is an example where the cloud service provider server 5, the creator, and the user corresponding to the creator each have their own accounts, and a shared folder in cloud storage is prepared in advance as the destination folder. However, it is also possible not to prepare a shared folder in advance. For example, a shared folder can be created when the workflow is created. Hereinafter, this will be described as a second embodiment. It should be noted that for structures and operations that are the same as in the first embodiment, the same reference numerals are used as in the first embodiment, and their description is omitted.

[0129] Figure 17 This is a sequence diagram illustrating the actions involved in creating a workflow in a service provisioning system of an information processing system according to the second embodiment.

[0130] Steps S11 to S14 and reference Figure 7 The same applies to the first embodiment.

[0131] In step S12, after the creator inputs the cloud service selection and company account information from the creator terminal 2, they further specify the destination folder for saving the creation in cloud storage (step S61). The specification of the destination folder includes the user accounts of each user sharing the shared folder.

[0132] Workflow creation server 1, based on the specified save destination folder from creator terminal 2, instructs cloud service provider server 5, which is logged in through the company account, to set the specified save destination folder (step S62).

[0133] Upon receiving the instruction, the cloud service provider server 5 registers the user account of the user to be shared and ensures the specified save destination folder in the cloud storage (step S63). Then, steps S17 to S21 as described in the first embodiment are performed.

[0134] The actions of the workflow creation server 1 used to implement such workflow creation are described below. Figure 18 This is a flowchart illustrating an example of a workflow creation processing action performed by the processor 11 of the workflow creation server 1.

[0135] The processing of ACT101 to ACT106 and the processing and reference of ACT108 to ACT114 Figure 8The same applies as described in the first embodiment. In the first embodiment, processor 11, as ACT107, retrieves available shared folders and displays them on the creator terminal 2. In contrast, in this embodiment, processing is performed to create available shared folders in the cloud storage of the logged-in cloud service provider server 5.

[0136] That is, after the processing of ACT106, the processor 11, in ACT121, determines whether it has received a save destination instruction sent from the creator terminal 2 via the network NW through the communication interface 14. This save destination instruction is sent based on the save destination folder in the account registration screen of the creator terminal 2 and the specified operations of the user accounts of each user sharing that save destination folder. That is, the save destination instruction includes information about the save destination folder and the user accounts. Alternatively, it may only include the save destination folder and continue to accept user account specifications. If no save destination instruction is received, the processor 11 determines NO in ACT121 and repeats the processing of ACT121. Thus, the processor 11 waits for the transmission of the save destination instruction. If a save destination instruction is received, the processor 11 determines YES in ACT121 and proceeds to the processing of ACT122.

[0137] As ACT122, processor 11 instructs cloud service provider server 5, logged in through a company account, to create a save destination folder. Specifically, processor 11 instructs the corresponding cloud service provider server 5 via communication interface 44 through network NW to create the specified save destination folder. Additionally, processor 11 sends a list of accounts sharing the save destination folder to the corresponding cloud service provider server 5 via communication interface 44 through network NW. These accounts include company accounts and user accounts. Then, processor 11 proceeds to the processing described in ACT108 above.

[0138] As described above, the service providing system of the information processing system according to the second embodiment and the user setting server 4 of the information processing device according to the second embodiment can also achieve the same effect as the information processing system and information processing device according to the first embodiment.

[0139] Furthermore, according to the second embodiment, when the processor 11 of the workflow creation server 1 sets the folder as the save destination folder of the cloud service to be accessed in the created workflow, it registers the sharing settings of the folder and the shared user account that can access it with the cloud service provider server 5 that provides the cloud service.

[0140] Therefore, according to the information processing system and information processing apparatus of the second embodiment, even without prior registration of the cloud service to be accessed and the user account that can be accessed, the cloud service can be registered when the workflow is created.

[0141] [Third Implementation Method]

[0142] The first and second embodiments described above are examples where the user's account registration is completed on the user-configuration server 4 when the user executes the workflow. However, user account registration may not be necessary beforehand. Depending on the workflow to be executed, there may be workflows that do not require access to cloud services. Therefore, the execution of the workflow can begin, and user account registration can start at the point when access to cloud services is required. Hereinafter, this will be described as a third embodiment. It should be noted that for structures and operations identical to those in the first embodiment, the same reference numerals as in the first embodiment are used, and their descriptions are omitted.

[0143] In this embodiment, the reference is not performed. Figure 10 as well as Figure 11 The description describes the actions used for pre-registering user accounts. Furthermore, since the user configuration program is incorporated into the workflow execution program, 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 as a program that calls the workflow execution program from the workflow execution program.

[0144] Figure 19 This is a sequence diagram illustrating the actions during workflow execution in a service provision system of an information processing system according to the third embodiment.

[0145] Steps S41 to S44 and reference Figure 13 The same applies to the first embodiment.

[0146] In this embodiment, if the user setting server 4 obtains the workflow selected by the workflow creation server 1 in step S44 and saves it in the selected workflow storage unit 435, the execution of the workflow will start immediately (step S48).

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

[0148] When executing a workflow in this way, if file upload is required, the user configuration server 4 performs an account validity check (step S71). That is, the user configuration server 4 confirms whether the user account corresponding to the cloud ID defined in the workflow settings stored in the selection workflow storage unit 435 is saved in association with 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 described later; otherwise, the user terminal 3 displays an input screen for the user account. This input screen includes information about the cloud service for the save destination folder defined in the workflow settings.

[0149] The user enters their own user account for the cloud service on the input screen (step S72).

[0150] User configuration server 4 obtains the user account from user terminal 3 and registers it (step S73). That is, user configuration server 4 stores the cloud service ID of the cloud service defined in the workflow and the obtained user account in user configuration storage unit 432 in association with the user ID used in the login of user configuration server 4.

[0151] Then, the user setting server 4 uses the registered user account to log in to the corresponding cloud service provider server 5 (step S74).

[0152] Furthermore, the user setting server 4 performs a check on whether the save destination can be accessed (step S75). That is, the user setting server 4 confirms whether it can access the save destination folder defined in the workflow settings stored in the selected workflow storage unit 435. If it can access the folder, the user setting server 4 uses the user account of the logged-in user stored in the user setting storage unit 432 to upload the file to the save destination folder of the cloud storage of the cloud service provider server 5 defined in the workflow settings.

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

[0154] The following describes the actions of the user-defined server 4 used to implement such workflow execution. Figure 20 This is a flowchart illustrating an example of the processing actions performed when the processor 41 of the user-configured server 4 executes a workflow.

[0155] Processing and reference of ACT411 to ACT413 Figure 14 The same applies to the first embodiment.

[0156] In ACT413, after the processor 41 obtains the workflow from the workflow creation server 1 and saves it in the selected workflow storage unit 435, in this embodiment, as ACT421, the selected workflow saved in the selected workflow storage unit 435 is executed.

[0157] As ACT422, processor 41, while executing the tasks defined in the workflow, prohibits file uploads, that is, prohibits saving files to the cloud storage destination folder. If it is not necessary to save the file to the destination folder, processor 41 determines NO in ACT422 and proceeds to ACT424 (described later). If it is necessary to save the file to the destination folder, processor 41 determines YES in ACT422, and in this embodiment, proceeds to ACT414.

[0158] The processing in ACT414 to ACT416 is the same as that described in the first embodiment.

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

[0160] As ACT432, processor 41 performs account registration processing. This account registration processing involves receiving user accounts sent from user terminal 3 via network NW through communication interface 44 and storing them in user setting storage unit 432. Then, processor 41 transfers the processing to ACT417.

[0161] The processing of ACT417 to ACT420 is the same as that described in the first embodiment. However, in ACT419, if it is determined to be accessible and the result is YES, the processing of ACT421 is entered in the first embodiment, but the processing of ACT423 is entered in this embodiment. The processing of ACT423 is the same as that described in the first embodiment, and the processor 41 then transfers to the processing of ACT422 described above.

[0162] As described above, the service providing system of the information processing system according to the third embodiment and the user setting server 4 of the information processing device according to the third embodiment can also achieve the same effect as the information processing system and information processing device according to the first embodiment.

[0163] Furthermore, according to the third embodiment, when the processor 41 of the user setting server 4 executes the workflow, it accepts the registration of user accounts from the user based on the operation of the user terminal 3.

[0164] Therefore, according to the third embodiment, the required user account can be obtained through the user's 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 can be omitted.

[0165] [Fourth Implementation Method]

[0166] The first to third embodiments described above use two independent servers: a workflow creation server 1 and a user setting server 4. However, the functions of two servers can also be achieved using a single server. Hereinafter, this will be described as the fourth embodiment. It should be noted that for structures and operations identical to those in the first embodiment, the same reference numerals are used as in the accompanying drawings, and their descriptions are omitted.

[0167] Figure 21 This is a block diagram illustrating an example of the overall structure of a service provision system as an information processing system according to the fourth embodiment. In this embodiment, instead of Figure 1 The workflow creation server 1 and user setting server 4 shown are combined with an integrated server 6, which is an information processing device according to the fourth embodiment.

[0168] Figure 22 This is a block diagram illustrating an example of the structure of the integrated server 6. The integrated server 6 may include information processing equipment such as server computers. Figure 22 As shown, the integrated server 6 includes a processor 61, main memory 62, auxiliary storage device 63, communication interface 64, etc. These components are interconnected via a data bus or other bus 65. The processor 61, main memory 62, communication interface 64, and bus 65 are the same as those of the workflow creation server 1 in the first embodiment, including the processor 11, main memory 12, communication interface 14, and bus 15. The auxiliary storage device 63 is a non-volatile internal memory capable of writing and rewriting data. In the auxiliary storage device 63, for example, a low-cost storage device with low failure tolerance, such as an HDD, SSD, or flash memory, is used. The auxiliary storage device 63 stores control programs, application programs, and various data according to the application 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.

[0169] The workflow creation / execution program storage unit 631 causes the processor 61 to create a workflow according to the instructions from the creator terminal 2, and stores the workflow creation / execution program, which executes the workflow according to the selection of the workflow to be executed from the user terminal 3.

[0170] 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. In addition, 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.

[0171] It should be noted that the auxiliary storage device 63 of the integrated server 6 does not have a storage unit equivalent to the workflow overview storage unit 433 and the selection workflow storage unit 435 described in the first embodiment.

[0172] In the integrated server 6 with such a structure, the workflow creation server 1 in the first embodiment functions as the creator terminal 2. That is, the processor 61 saves the workflow defined by the creator's operation on the creator terminal 2 in the workflow storage unit 632 according to the workflow creation / execution program stored in the workflow creation / execution program storage unit 631.

[0173] Furthermore, the integrated server 6 functions as the user setting server 4 in the first embodiment, relative to the user terminal 3. Specifically, when registering a user account, the processor 61 creates a workflow overview based on the workflow stored in the workflow storage unit 632, according to the user setting program stored in the user setting program storage unit 634, and provides it to the user terminal 3. Then, the processor 61 obtains the cloud service selection results and user account information from the user's actions on the user terminal 3 and saves them in the user setting storage unit 635.

[0174] In addition, when executing a workflow, the processor 61 receives the workflow to be executed from the workflow stored in the workflow storage unit 632 from the user terminal 3 according to the workflow creation / execution program stored in the workflow creation / execution program storage unit 631, and executes the selected workflow.

[0175] As described above, the service providing system of the information processing system according to the fourth embodiment and the integrated server 6 of the information processing device according to the fourth embodiment implement the functions of the workflow creation server 1 and the user setting server 4 according to the first embodiment.

[0176] Therefore, the information processing system and information processing apparatus according to the fourth embodiment can achieve the same effect as the information processing system and information processing apparatus according to the first embodiment.

[0177] It should be noted that the above description describes the situation where the integrated server 6 implements the functions of the workflow creation server 1 and the user setting server 4 involved in the first embodiment. However, the integrated server 6 can also implement the functions of the workflow creation server 1 and the user setting server 4 involved in the second or third embodiment.

[0178] [Other Implementation Methods]

[0179] The above describes the implementation methods of the information processing system and the information processing device, but the implementation methods are not limited thereto.

[0180] For example, in the first to third embodiments, a workflow overview is sent from the workflow creation server 1 to the user setting server 4 and stored in the workflow overview storage unit 433. However, the user setting server 4 may also request and obtain the workflow overview from the workflow creation server 1 as needed. Therefore, the workflow overview storage unit 433 is no longer needed.

[0181] Furthermore, the integrated server 6, as the information processing apparatus according to the fourth embodiment, can be located in the workplace, for example, a multi-function peripheral (hereinafter referred to as MFP) having at least scanning, printing, and communication functions. In this case, for example, the scanning function can also function as a user terminal 3 performing the task of scanning documents. That is, the integrated server 6 functions as a user terminal 3, so the service providing system may not need to have a user terminal 3. In this case, the created workflow may, for example, consider a workflow that performs optical character recognition on the scanned document and uploads the document to cloud storage in a specified file format.

[0182] Furthermore, the aforementioned information processing flow described with reference to the flowchart by processors 11, 21, or 61 is an example and is not limited to this order. The processing order can be changed, or multiple processes can be performed in parallel, as long as it does not cause inconsistency with preceding or subsequent processing.

[0183] It should be noted that in the above implementation, a company account was used as an example of the first account, but it is not limited to this. The first account can be a group account of various groups within a company, such as organizations, groups, fan clubs, residences and apartments, and self-governing associations. That is, the first account can be an account that has set up multiple users for a group.

[0184] Furthermore, in the above embodiments, 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 transferred to each server can also be written to the writable storage devices of each server according to the operation of administrators, etc. The transfer of these control programs can be stored in a removable computer-readable storage medium or performed via communication over a network. The computer-readable storage medium is not limited in method, as long as it can store programs such as a CD-ROM or memory card and the device can read them.

[0185] While several embodiments have been described, these embodiments are merely illustrative and not intended to limit the scope of the invention. These embodiments can be implemented in various other ways, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included within the scope and spirit of the invention, and likewise within the scope of the invention as described in the claims and its equivalents.

Claims

1. An information processing system, comprising: The production department creates workflows based on the operations of the workflow creator, and the production department uses a first account used to access the cloud service to create workflows that include accessing the cloud service. The registration department, based on instructions from the user via the network, registers a second account associated with the user for accessing the cloud service; as well as The execution unit, when executing the workflow according to instructions from the user via the network, uses a second account, which is registered and associated with the user who gave the instructions, instead of the first account, to access the cloud service.

2. The information processing system according to claim 1, wherein, When executing the workflow, the execution unit checks whether a second account associated with the user who made the instruction is registered. If no account is registered, the workflow is not executed, and the user who made the instruction is warned via the network.

3. The information processing system according to claim 1 or 2, wherein, The cloud service mentioned is a cloud storage service that provides a destination folder for saving files. When the user executes the workflow, the execution unit checks whether the second account associated with the user who made the instruction can be used to access the save destination folder of the cloud storage. If access is not possible, the workflow is not executed, and the user who made the instruction is warned via the network.

4. An information processing device, comprising: The registration department, based on instructions from users via the network, stores a second user-associated account in the storage department for accessing cloud services; and When the execution unit executes a workflow created using a first account for accessing the cloud service in accordance with an instruction from the user via the network, it uses a second account stored in the storage unit associated with the user who gave the instruction to access the cloud service instead of the first account, the workflow including accessing the cloud service.

5. The information processing apparatus according to claim 4, wherein, When executing the workflow, the execution unit checks whether a second account associated with the user who made the instruction is registered. If no account is registered, the workflow is not executed, and the user who made the instruction is warned via the network.

6. The information processing apparatus according to claim 4, wherein, The cloud service mentioned is a cloud storage service that provides a destination folder for saving files. When the user executes the workflow, the execution unit checks whether the second account associated with the user who made the instruction can be used to access the save destination folder of the cloud storage. If access is not possible, the workflow is not executed, and the user who made the instruction is warned via the network.

7. The information processing apparatus according to claim 4, wherein, The information processing device also includes: A receiving unit that receives instructions from the user via the network; and The storage unit stores information based on the instructions received from the user.

8. An information processing product, comprising an information processing program, When the information processing program is executed by a 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 processor is instructed to perform the following processing: According to the received instructions, a second user-associated account used for accessing cloud services is stored in the storage unit; and When executing a workflow that includes accessing the cloud service using a first account for accessing the cloud service, the second account associated with the user who made the instruction, stored in the storage unit, is used instead of the first account to access the cloud service.

9. The information processing program product according to claim 8, wherein, When the information processing program executes the workflow by the processor of the information processing device, it checks whether a second account associated with the user who made the instruction is registered. If no account is registered, the workflow is not executed, and the user who made the instruction is warned via the network.

10. The information processing program product according to claim 8, wherein, The cloud service mentioned is a cloud storage service that provides a destination folder for saving files. When the user executes the workflow, the processor checks whether the saved destination folder of the cloud storage can be accessed using the registered second account associated with the user who made the instruction. If access is not possible, the processor does not execute the workflow, but instead issues a warning to the user who made the instruction via the network.

Images