Print system, workflow platform and control method for print system

Abstract

To improve processing for smoothly progressing a workflow.SOLUTION: A print system that executes printing from a workflow includes a workflow platform that executes the workflow, chat service capable of notifying a user of notifications, and print service that executes printing with a printer. The workflow platform includes workflow construction means that constructs the workflow in cooperation with the chat service and the print service, and workflow execution means that executes the workflow. The workflow execution means allows the print service to execute printing according to the workflow to be executed, and allows the chat service to notify the user of a result of the printing executed by the print service.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a print system, a workflow platform, and a method for controlling a print system. [Background technology]

[0002] In recent years, the use of chat services and cloud services has been increasing. For example, there are workflow platforms that allow users to build workflows that combine various in-house services or various external online services from a chat service and automate tasks. The workflow platforms also provide a means for users or third-party developers to add external online services.

[0003] On the other hand, printing is also performed by a printer in cooperation with a workflow. In addition, the printer is also used to notify the user of the print execution result. Patent Document 1 discloses a means for managing a print operation log by an exception process in a printer, a means for acquiring the permission or prohibition of printing based on the print log, and a means for notifying an administrative user when printing is not permitted. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2019-200600 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in Patent Document 1, the point of notification is when exception processing is performed, and does not assume the need for notification when printing is successful. In printing in a workflow, various document-related tasks are automated and executed, so the point at which printing actually occurs may differ from the point at which the user starts the workflow. In that case, even when printing is successful, the user must periodically check the progress of the workflow in order to start subsequent tasks that use the printed matter, which hinders automation. For this reason, there is room for improvement in the configuration for smoothly progressing the workflow.

[0006] An object of the present invention is to improve the process for smoothly progressing a workflow. [Means for solving the problem]

[0007] A print system according to one embodiment of the present invention is a print system that prints from a workflow, and includes a workflow platform that executes the workflow, a chat service that can notify a user, and a print service that prints on a printer, the workflow platform including a workflow construction means that constructs the workflow in cooperation with the chat service and the print service, and a workflow execution means that executes the workflow, the workflow execution means executing printing with the print service in accordance with the workflow being executed, and notifying the results of the printing executed by the print service via the chat service. Effect of the Invention

[0008] According to the present invention, it is possible to improve the process for smoothly progressing a workflow. [Brief description of the drawings]

[0009] [Figure 1] 1 is a diagram showing an overall configuration of a system according to a first embodiment of the present invention; [Diagram 2]1 is a hardware configuration diagram of a printer according to a first embodiment of the present invention. [Diagram 3] 1 is a hardware configuration diagram of a client PC, a workflow platform, and a print service according to a first embodiment of the present invention. [Figure 4] FIG. 2 is a software configuration diagram of the system according to the first embodiment of the present invention. [Diagram 5] FIG. 2 is a software configuration diagram of the system according to the first embodiment of the present invention. [Figure 6] FIG. 2 is a software configuration diagram of the system according to the first embodiment of the present invention. [Figure 7] FIG. 2 is a diagram showing a workflow list screen displayed on a chat service in the system according to the first embodiment of the present invention. [Figure 8] FIG. 13 is a diagram showing a screen for setting a workflow trigger displayed on a chat service in the system according to the first embodiment of the present invention. [Figure 9] FIG. 13 is a diagram showing a screen for setting an action of a workflow displayed on a chat service in the system according to the first embodiment of the present invention. [Figure 10] FIG. 13 is a diagram showing a screen for setting details of a workflow trigger or action displayed on a chat service in the system according to the first embodiment of the present invention. [Figure 11] 5 is a flowchart showing a file trigger setting process according to the first embodiment of the present invention. [Figure 12] 5 is a flowchart showing a setting process of a file acquisition action according to the first embodiment of the present invention. [Figure 13] 4 is a flowchart of a workflow platform showing a print action according to the first embodiment of the present invention. [Figure 14] 5 is a flowchart of a print service showing a print action according to the first embodiment of the present invention. [Figure 15] 4 is a flowchart of a workflow platform showing a reserve print action according to a first embodiment of the present invention. [Figure 16] 4 is a flowchart of a workflow platform showing a notification action according to a first embodiment of the present invention; [Figure 17] 4 is a flowchart of the workflow platform during workflow execution according to the first embodiment of the present invention. [Figure 18] 5 is a flowchart of a print service during execution of a workflow according to the first embodiment of the present invention. [Figure 19] 5 is a flowchart illustrating a printing process performed by a printer during execution of a workflow according to the first embodiment of the present invention. [Figure 20] 6 is a flowchart illustrating reservation printing performed by a printer during execution of a workflow according to the first embodiment of the present invention. [Figure 21] 11 is a flowchart showing how a chat service transmits and receives a notification request during workflow execution according to the first embodiment of the present invention. [Figure 22] 6 is a flowchart showing a notification performed by a print service during execution of a workflow according to the first embodiment of the present invention. [Diagram 23] 6 is a flowchart showing a notification performed by a print service during execution of a workflow according to the first embodiment of the present invention. [Figure 24] 5 is a flowchart showing a process for determining a notification destination by a print service during execution of a workflow according to the first embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, the embodiments of the present invention will be described with reference to the drawings. Note that the following embodiments do not limit the invention according to the claims, and all of the combinations of features described in the embodiments are not necessarily essential to the solution of the invention.

[0011] [First embodiment] <Overall composition> FIG. 1 is a diagram showing the overall configuration of a system according to a first embodiment of the present invention. The workflow system 10 has a workflow platform 130, a print service 120, a chat service 140, a cloud storage 150, a printer 110, and a client PC 111. PC is an abbreviation for Personal Computer. The workflow platform 130, the print service 120, and the chat service 140 may be separate computers, or at least any of them may be the same computer. The workflow system 10 is an example of a print system. The print service 120 and the chat service 140 are examples of online services.

[0012] The printer 110 and the client PC 111 are communicably connected to a server that provides various services on the Internet via a LAN (LAN is an abbreviation for Local Area Network).

[0013] The workflow platform 130 is a service that allows users to build workflows. The workflow platform 130 is a service provided by OS development companies, etc., and allows users to build workflows in conjunction with services such as cloud storage and chat services provided by the OS development companies, etc. OS is an abbreviation for Operating System.

[0014] A workflow is data for executing actions, which are individual processes, in a determined order. The actions are, for example, a process of printing with the printer 110 or the like, a process of reservation printing with the printer 110 or the like, and a process of scanning with the printer 110 or the like. Printing-related processes such as a process of printing with the printer 110 or the like and a process of reservation printing with the printer 110 or the like may be called print actions. Scanning-related processes such as a process of scanning with the printer 110 or the like may be called scan actions. Actions are not limited to processes related to printing or scanning, and may be processes that do not involve an image processing device such as the printer 110, such as approval requests, notification requests, file saving, conditional branching, and repetitive processes.

[0015] Furthermore, the workflow platform 130 has a customization function that allows it to be linked to online services provided by other companies, making it possible to create workflows that are linked to many services.

[0016] The print service 120 connects to the printer 110 and provides a service of receiving an image file scanned by the printer 110. The print service 120 provides a service of transferring a file to a service capable of storing the file, such as a storage service. The print service 120 provides a service of transmitting a file from the storage service or the like, and a file and a print job from the client PC 111 to the printer 110, and printing the file on the printer 110. The print service 120 is an online service.

[0017] The chat service 140 is a communication service for chatting. The chat service 140 cooperates with the workflow platform 130 and can notify users by chat. The chat service 140 is not limited to a service for chatting, and may have a function for notifying users of email, an approval system, a task management system, or the like. Furthermore, each of these services that provide a function for notifying users may be an independent service.

[0018] Cloud storage 150 is a service that allows users to store files over the Internet and retrieve files using a web browser.

[0019] The client PC 111 is a client PC for displaying and operating each service provided by the workflow platform 130. A user can use each service through a web browser or application running on the client PC 111.

[0020] The printer 110 is a multifunction device having multiple functions such as a scanner and a printer, and is an example of an image processing device.

[0021] Although the workflow system 10 of the present embodiment has the above-mentioned services, the present invention is not limited to this, and may have other configurations.

[0022] <Printer hardware configuration> 2 is a diagram showing the hardware configuration of the printer 110. The printer 110 includes a control unit 210, an operation unit 220, a printer unit 221, a scanner unit 222, and an authentication device 223.

[0023] The control unit 210 controls the overall operation of the printer 110. The control unit 210 includes a CPU 211, a ROM 212, a RAM 213, a HDD 214, an operation unit I / F 215, a printer I / F 216, a scanner I / F 217, an authentication device I / F 218, and a network I / F 219.

[0024] The CPU 211 realizes and controls various functions provided by the printer 110, such as reading, printing, and communication, by reading and executing programs stored in the ROM 212 and the HDD 214. The ROM 212 is a non-volatile memory and stores programs and data executed by the CPU 211. The ROM is an abbreviation for Read Only Memory. The RAM 213 is used as a temporary storage area such as the main memory and work area of ​​the CPU 211. The RAM is an abbreviation for Random Access Memory. The HDD 214 is a large-capacity storage unit that stores programs and data executed by the CPU 211. The HDD is an abbreviation for Hard Disk Drive. In this embodiment, one CPU 211 uses one memory (RAM 213 or HDD 214) to execute each process shown in the flowchart described below, but the present invention is not limited to this. For example, each process may be executed by cooperating multiple CPUs and multiple RAMs or HDDs.

[0025] The operation unit I / F 215 is an interface that connects the operation unit 220 and the control unit 210. I / F is an abbreviation of interface. The operation unit 220 has a touch panel, a keyboard, and the like, and accepts operations, inputs, and instructions from a user.

[0026] The printer I / F 216 is an interface that connects the printer unit 221 and the control unit 210. Image data to be printed is transferred from the control unit 210 to the printer unit 221 via the printer I / F 216, and is printed on a recording medium.

[0027] The scanner I / F 217 is an interface that connects the scanner unit 222 and the control unit 210. The scanner unit 222 reads an original placed on a platen or ADF (not shown) to generate image data, and outputs the generated image data to the control unit 210 via the scanner I / F 217. ADF is an abbreviation for Auto Document Feeder.

[0028] The printer 110 can print out (copy) image data generated by a scanner unit 222 from a printer unit 221, and can also transmit the image data as a file or by email.

[0029] The authentication device I / F 218 is an interface that connects the authentication device 223 to the control unit 210. The authentication device 223 is, for example, a card reader that reads an IC card or a fingerprint authentication device that reads a fingerprint, and is used for authentication for a user to use the printer 110.

[0030] The network I / F 219 is an interface that connects the control unit 210, i.e., the printer 110, to a LAN. The printer 110 uses the network I / F 219 to transmit and receive various information such as image data and other information to and from each service on the Internet.

[0031] <Hardware configuration of client PC, workflow platform and print service> 3 is a diagram showing the hardware configuration of each of the client PC 111, the print service 120, and the workflow platform 130. Each of the client PC 111, the print service 120, and the workflow platform 130 includes a control unit 310. The control unit 310 includes a CPU 311, a ROM 312, a RAM 313, a HDD 314, and a network I / F 315.

[0032] The CPU 311 realizes various functions by reading and executing programs stored in the ROM 312 and the HDD 314, and controls the overall operation. The ROM 312 is a non-volatile memory, and stores the programs and data executed by the CPU 311. The RAM 313 is used as a temporary storage area such as the main memory and work area of ​​the CPU 311. The HDD 314 is a large-capacity storage unit that stores the programs and data executed by the CPU 311. The network I / F 315 is an interface that connects each of the client PC 111, the print service 120, and the workflow platform 130 to the Internet. The client PC 111, the print service 120, and the workflow platform 130 receive processing requests and transmit and receive various information to and from other devices and services via the network I / F 315.

[0033] <Workflow system software configuration> Figures 4, 5 and 6 are software configuration diagrams of the workflow system 10 according to this embodiment. The circled letters shown in Figure 4 are connected to the same letters in the circled letters shown in Figure 6. Also, the circled letters shown in Figure 5 are connected to the same letters in the circled letters shown in Figure 6.

[0034] 4, the workflow platform 130 includes a request control unit 431, an account management unit 432, a display control unit 433, a workflow management unit 434, and a workflow control unit 435. The request control unit 431 is in a standby state in which it can receive requests from the print service 120, the chat service 140, the cloud storage 150, the printer 110, and the client PC 111.

[0035] The account management unit 432 manages account information for logging in to the workflow platform 130. In this embodiment, the workflow platform 130 and the other services each have different account information. The present invention is not limited to this, and a common account management service may be separately provided for each service, allowing single sign-on to each service using the same account. For example, the accounts for the workflow platform 130 and the chat service 140 may be managed as the same account by the same account management unit.

[0036] The display control unit 434 receives a request from a web browser running on the client PC 111 connected via the Internet and returns screen configuration information required for screen display. The screen configuration information is HTML, CSS, or the like. HTML is an abbreviation for HyperText Markup Language. CSS is an abbreviation for Cascading Style Sheets. The display control unit 434 can also receive a request from a web browser running on another terminal device such as a mobile terminal device and return the screen configuration information.

[0037] A workflow management unit 434 creates a workflow in the workflow print service 120 and manages it by editing, saving, etc. A workflow control unit 435 controls the execution and stop of a workflow stored in the workflow management unit 434 in response to a workflow execution request from the request control unit 431. This execution of a workflow is an example of a workflow execution means.

[0038] 4, the print service 120 includes a request control unit 421, an account management unit 422, a display control unit 423, a printer management unit 424, and a job management unit 425. The request control unit 421 waits in a state in which it can receive requests from the printer 110 and the workflow platform 130.

[0039] The account management unit 422 manages account information for logging in to the print service 120. In addition, the account information for logging in to the print service 120 may be linked to user information used to log in to the printer 110.

[0040] The display control unit 423 receives a request from a web browser running on the client PC 111 connected via the Internet and returns screen configuration information required for screen display. The display control unit 423 can also receive a request from a web browser running on another terminal device such as a mobile terminal device and return screen configuration information.

[0041] The printer management unit 424 manages the printers registered in the print service 424. In addition, the printer management unit 424 can acquire the status, printing performance, scanning performance, and various settings of the registered printers.

[0042] The job management unit 425 receives and manages print and scan jobs from the workflow platform 130, the client PC 111, and the chat service 140. The job management unit 425 transmits the jobs it manages to a printer registered in the print service 120 in response to a request, and causes the printer to execute the job.

[0043] 5, the chat service 140 has a request control unit 441, an account management unit 442, a display control unit 443, an approval management unit 444, and a notification control unit 445. The request control unit 441 waits in a state in which it can receive requests from the client PC 110, the print service 120, and the workflow platform 130.

[0044] The account management unit 442 manages account information for logging in to the chat service 140. As described in the explanation of the account management unit 432, the accounts for the workflow platform 130 and the chat service 140 may be managed as the same account by the same account management unit.

[0045] The display control unit 443 receives a request from a web browser running on the client PC 111 connected via the Internet and returns screen configuration information necessary for screen display. The display control unit 443 can also receive a request from a web browser running on another terminal device such as a mobile terminal device and return screen configuration information.

[0046] The approval management unit 444 receives approval requests from external services such as the chat service 140, the workflow system 130, or the print service 120, and manages the approval requests and the approval status for accounts on the chat service 140. For example, a user of the chat service 140 can issue an approval request for a quote on the chat service 140 to another user who has an account on the chat service 140, and the account that receives the approval request can process the approval or denial.

[0047] The notification control unit 445 receives a notification request from an external service such as the chat service 140 , the workflow system 130 or the print service 120 , and issues a notification to an account on the chat service 140 .

[0048] 5, the cloud storage 150 includes a request control unit 451, an account management unit 452, a display control unit 453, and a file management unit 454. The request control unit 451 is in a standby state in which it can receive requests from the client PC 110, the print service 120, and the workflow platform 130.

[0049] The account management unit 452 manages account information for logging in to the cloud storage 150. Furthermore, the accounts for the workflow platform 130 and the cloud storage 150 may be managed as the same account by the same account management unit.

[0050] The display control unit 453 receives a request from a web browser running on the client PC 111 connected via the Internet and returns screen configuration information necessary for screen display. The display control unit 453 can also receive a request from a web browser running on another terminal device such as a mobile terminal device and return screen configuration information.

[0051] The file management unit 454 manages files stored on the cloud storage 150, and stores, modifies, deletes, transmits, etc., files upon request.

[0052] 6, the printer 110 has a request control unit 411, a data management unit 412, and a display control unit 413. The request control unit 411 stands by in a state in which it can receive a processing request from the print service 120. When the printer 110 receives a processing request, it instructs the display control unit 413 and the data management unit 434 to perform the processing as appropriate in response to the request.

[0053] A data management unit 412 manages user information, connection information with the print service 120, and the like. A display control unit 413 displays a UI screen for receiving operations by a user on a liquid crystal display unit having a touch panel function of the operation unit 220 of the printer 110. Although only one printer 110 connected to the print service 120 is shown in Figs. 4, 5, and 6, the workflow system 10 may have multiple printers connected to the print service 120. Furthermore, when the printer 110 has been registered with the print service 120, the printer 110 communicates with the print service 120 constantly or periodically so as to be able to receive requests from the print service 120.

[0054] 6, the client PC 111 has a request control unit 414 and a display control unit 415. The client PC 111 accesses the print service 120, the workflow platform 130, the chat service 140, and the cloud storage 150 via the request control unit 414. A user operates the workflow platform 130 and various online services via a screen displayed in a web browser by the display control unit 415 of the client PC 111.

[0055] <Processing flow> First, a description will be given of a procedure for constructing a workflow on the workflow platform 130. This procedure is an example of a workflow construction means for constructing a workflow.

[0056] 7 is a diagram showing a workflow list screen displayed on a chat service in the system according to the first embodiment of the present invention. The chat service 140 cooperates with the workflow platform 130 by being authenticated with an account of the workflow platform 130. By cooperating with the workflow platform 130, the chat service 140 can display a workflow list screen 500 on the screen of the chat service 140. As described above, the account of the chat service 140 may be the same account as that of the workflow platform 130, in which case authentication for cooperation is not required.

[0057] The workflow list screen 500 is divided into two parts: a sidebar and a main screen. The workflow list screen 500 displays a button 501 for transitioning to a chat screen, a button 502 for transitioning to a notification screen, a button 503 for transitioning to a workflow list screen, and a button 504 for transitioning to an approval screen in the sidebar. The workflow list screen 500 displays a button 505 for creating a new workflow, a field 506 for displaying the titles of workflows that have already been created, a button 507 for editing a workflow, and a button 508 for executing a workflow in the main screen.

[0058] When transitioning from workflow list screen 500 to a chat screen, a notification screen, or an approval screen, the sidebar display does not change, and only the main screen display changes. Workflow list screen 500 is displayed when the user presses button 503. Workflows can be created, edited, and executed from workflow list screen 500. Note that, depending on the workflow, the start condition for the workflow may be created so that it is executed by, for example, a specific date and time or a specific action. In that case, when button 508 is pressed, the content of the specific action that serves as the condition can be manually set and executed.

[0059] Badge 509 is a badge indicating the number of unread notifications that have arrived at chat service 140. When there are zero unread notifications, badge 509 is not displayed. Badge 510 is a badge indicating the number of unprocessed approval notifications that have arrived at chat service 140. When there are zero unprocessed approval notifications, badge 510 is not displayed.

[0060] Fig. 8 is a diagram showing an example of a workflow editing screen 600 that is displayed when a button 505 for creating a new workflow is pressed. Fig. 8 is a diagram showing a screen for setting a trigger for a workflow that is displayed on a chat service in a system according to a first embodiment of the present invention. The workflow editing screen 600 is an example of a screen for setting a trigger for a workflow.

[0061] The workflow editing screen 600 is configured to be divided into two parts, a sidebar and a main screen, similar to the workflow list screen 500. The main screen of the workflow editing screen 600 has a box 601 for editing the workflow name, a workflow trigger list screen 602, and a button 603 for selecting a workflow trigger. The main screen of the workflow editing screen 600 has a button 604 for searching for workflow triggers, a button 605 for adding a workflow action, and a button 606 for saving the workflow.

[0062] A workflow in the workflow platform 130 is constructed by combining a trigger, which is a workflow execution condition, and an action, which is the processing content of the workflow. Since a workflow must be started with a trigger, a trigger is set before an action on the workflow editing screen 600.

[0063] The workflow trigger list screen 602 displays a list of triggers available in the workflow platform 130. Examples of triggers include a schedule trigger that periodically starts a workflow, a file trigger that is executed when any cloud storage is updated, a scan trigger that is executed when scanning is started with a printer, etc. These are merely examples, and the actions provided by the workflow platform 130 and other external services are not limited to these examples.

[0064] When the button 603 is pressed, a trigger setting screen is displayed if the external service that provides the trigger and the account logged in to the workflow platform 130 are already linked. If there is no linkage, an authentication screen for linking is displayed, and the trigger setting screen is displayed after authentication.

[0065] The button 604 is for searching for workflow triggers displayed on the workflow trigger list screen 602, and allows the user to search for triggers using an input character string. This searches for triggers for the workflow platform 130 itself, triggers for other external services, and triggers for the print service. For example, if the user enters the character string "save" and searches, a list of triggers related to saving, such as actions triggered when data is saved in the cloud storage 150, is displayed. Similarly, if the user searches for "scan", a list of triggers that start a workflow when the print service 120 performs a scan is displayed. The trigger that starts the execution of the workflow is determined by the user selecting an action to be used in the workflow from these search results.

[0066] When a button 605 is pressed, a workflow action addition screen is displayed, and when a button 606 is pressed, the created workflow is saved.

[0067] Fig. 9 is a diagram showing an example of a workflow editing screen 700 displayed when the button 605 is pressed. Fig. 9 is a diagram showing a screen for setting an action of a workflow displayed on a chat service in the system according to the first embodiment of the present invention.

[0068] A workflow action is a process of a workflow, and performs some kind of transmission or reception to or from an external service, or performs control processing of the workflow itself, such as waiting, branching, or repeating the workflow.

[0069] The main screen of the workflow editing screen 700 has a workflow action list screen 701, a button 702 for selecting a workflow action, and a button 703 for searching for a workflow action. The main screen of the workflow editing screen 700 displays the name of a trigger that has already been set, and has a button 704 that displays a trigger editing screen when pressed. The main screen of the workflow editing screen 700 has a button 705 for adding a workflow action, and a button 706 for saving the workflow.

[0070] The workflow action list screen 701 displays a list of actions available on the workflow platform 130. Examples of actions include a print action that starts printing on a printer, a reservation print action that reserves and prints on a printer, and a scan action that starts scanning on a printer. These are merely examples, and the actions may not involve a printer, and include, for example, approval requests, notification requests, file saving, and conditional branching and repetitive processing. Furthermore, the actions provided by the workflow platform 130 and other external services are not limited to these examples.

[0071] When the button 702 is pressed, an action setting screen is displayed if the external service that provides the action is already linked to the account logged in to the workflow platform 130. If there is no linkage, an authentication screen for linking is displayed, and the action setting screen is displayed after authentication.

[0072] The button 703 is for searching for workflow actions displayed on the workflow action list screen 701, and allows the user to search for actions using an input character string. This searches for actions of the workflow platform 130 itself, actions of other external services, and actions of the print service 120. For example, if the user inputs the character string "notify" and searches, actions for the chat service 140 to notify any user or group are displayed. Alternatively, if the user inputs the character string "save" and searches, a list of actions related to saving, such as saving data to the cloud storage 150, is displayed. Similarly, if the user searches for "print", a list of actions of the connector that the print service 120 uses to print is displayed. The action of the workflow is determined by the user selecting an action to be used in the workflow from the search results.

[0073] A button 704 displays the name of a trigger that has already been set. When the button 704 is pressed, a trigger editing screen is displayed.

[0074] When the button 705 is pressed, a new workflow action list screen 701 is displayed below the already displayed workflow action list screen 701. This makes it possible to create a workflow that combines multiple workflow actions. When the button 706 is pressed, the created workflow is saved.

[0075] Fig. 10 illustrates a screen for setting workflow actions and workflow triggers. Fig. 10 illustrates a screen for setting details of workflow triggers or actions displayed on a chat service in a system according to a first embodiment of the present invention. Here, a workflow action setting screen 800 for printing is shown as an example.

[0076] A workflow action setting screen 800 has a field 801 for displaying an action name and an action setting list 802. The action setting list 802 has action settings 803, 804, 805, 806, and 807. The action settings 803, 804, 805, 806, and 807 are examples of print action settings. This action setting accepts input by a method such as free character string input, selection from options, and use of values ​​obtained in previous or next workflows. Also, option candidates in the action setting can be obtained from an external service and displayed. Also, these settings are not limited to action settings, but are similar to trigger settings.

[0077] A field 801 displays the name of the action. The name displayed in the field 801 may be freely changeable by the user. The workflow action setting screen 800 sets a workflow action with the action name in the field 801 according to the contents specified in each action setting in the action setting list 802.

[0078] The action setting 803 accepts the designation of the print printer to be used for printing. When the action setting 803 is pressed, options are displayed, and the print printer is designated when the user selects from the options. The print printers that can be selected here are printers that have been registered in the print service 120.

[0079] The action setting 804 accepts the specification of a target file to be printed. The specification method here is to specify a file acquired by a workflow trigger or a workflow action executed prior to the print action, or a URL indicating the file. For example, a file acquired from the cloud storage 150 is specified. URL is an abbreviation for Uniform Resource Locator.

[0080] The action setting 805 accepts the specification of the paper size. The action setting 806 accepts the specification of the print color setting. When the action settings 805 and 806 are pressed, options are displayed, and the user selects from the options to specify the option. These are examples of print settings, and more detailed print settings may be specified. The print settings depend on the performance of the printer used for printing. Therefore, the options of the action settings 805 and 806 receive selectable print settings from the print service 120 after the printer is specified in the action setting 803, and display them as options. In addition, for these print settings, values ​​obtained by a workflow trigger or workflow action executed prior to the print action may be used. In addition, when a conflict occurs between these settings, the display may be grayed out or disabled so that setting items that cannot be selected at the same time cannot be selected.

[0081] The action setting 807 accepts the specification of whether or not to notify about printing, the notification content, and the notification destination. When the action setting 807 is pressed, options are displayed, and the user selects from the options to specify the notification. The notification destination here can be an account or group of the workflow platform 130, or any account or group of the linked chat service 140 or print service 120.

[0082] Furthermore, the workflow platform 130 or the print service 120 may determine the notification destination depending on the error content and send the notification. In this case, the notification destination may be the user who executed the workflow, the user who executed the printing, and the user who performs the work of the subsequent process in the workflow.

[0083] Note that, here, the notification is set as a setting of the workflow action that performs printing, but a workflow may be constructed so that the result of the print action is obtained and a notification is made as a separate action of the workflow platform 130. Also, only specific notifications from among various notification types may be included in the print action. For example, a workflow may be defined as a separate notification action of the workflow platform 130 for the notification of successful printing, and the print action itself may be configured to notify of print failure so that a separate notification action does not need to be incorporated.

[0084] Next, the procedure for actually connecting to and setting up each service in order to build a workflow will be described with reference to respective flowcharts. Fig. 11 is a flowchart showing details of building a workflow in cooperation with cloud storage 150 in the workflow platform 130 in this system. Fig. 11 is a flowchart showing the setting process of a file trigger according to the first embodiment of the present invention. As an example, in this embodiment, a file creation trigger that executes a workflow when a file is created is built as a workflow trigger.

[0085] In step S1001, the workflow platform 130 detects a request to add a file creation trigger.

[0086] In step S1002, the workflow platform 130 checks whether collaboration with the cloud storage 150 that provides a file creation trigger has been set, and determines whether it is necessary to log in to the cloud storage 150. If the workflow platform 130 determines that it is necessary to log in to the cloud storage 150, the process of step S1003 is executed. If the workflow platform 130 determines that it is not necessary to log in to the cloud storage 150, the process of step S1005 is executed.

[0087] In step S1003, the workflow platform 130 sends a login request to the cloud storage 150.

[0088] In step S1004, the workflow platform 130 receives the login result from the cloud storage 150. After that, the workflow platform 130 can communicate with the cloud storage 150, assuming that the workflow platform 130 and the cloud storage 150 have been linked.

[0089] In step S1005, the workflow platform 130 acquires a list of file creation trigger settings.

[0090] In step S1006, the workflow platform 130 displays a list of file creation trigger settings acquired in step S1005. Note that options for each setting can be displayed as options acquired from an external service, in this case, the linked cloud storage 150.

[0091] In the file creation trigger, it is necessary to set in which folder the trigger should be executed when a file is created. In step S1007, the workflow platform 130 first displays a list of root folders in the cloud storage 150.

[0092] In step S1008, the workflow platform 130 determines whether it has detected that any folder has been selected from the list. If the workflow platform 130 determines that a folder has been selected, the process proceeds to step S1009. If the workflow platform 130 determines that a folder has not been selected, the process proceeds to step S1013.

[0093] In step S1009, the workflow platform 130 transmits a request to acquire a list of folders in the selected folder.

[0094] In step S1010, the workflow platform 130 receives the folder list acquisition result.

[0095] In step S1011, the workflow platform 130 displays the folder list received in step S1010.

[0096] In step S1012, the workflow platform 130 determines whether or not a selection of a folder to be triggered has been detected. If the workflow platform 130 determines that a selection of a folder to be triggered has been detected, the process of step S1013 is executed. If the workflow platform 130 determines that a selection of a folder to be triggered has not been detected, the process of step S1008 is executed.

[0097] In step S1013, the workflow platform 130 saves the file creation trigger settings.

[0098] 11, the workflow platform 130 can incorporate a file creation trigger into any workflow. The file creation trigger provides for obtaining metadata related to a created file, such as the name, ID, time, and folder path of the created file, in a workflow action that is executed after the file creation trigger.

[0099] Fig. 12 is a flowchart showing details of constructing a workflow in cooperation with the cloud storage 150 in the workflow platform 130 in this system. Fig. 12 is a flowchart showing a setting process of a file acquisition action according to the first embodiment of the present invention. In this embodiment, as an example, a file acquisition action for acquiring a file in the cloud storage 150 is constructed as an action of the workflow. The file acquisition action is an action for acquiring the contents of a specified file, a public URL, or a restricted URL.

[0100] In step S1101, the workflow platform 130 detects a request to add a file acquisition action.

[0101] In step S1102, the workflow platform 130 checks whether collaboration with the cloud storage 150 that provides the file acquisition action has been set, and determines whether logging in to the cloud storage 150 is necessary. If the workflow platform 130 determines that logging in to the cloud storage 150 is necessary, the process of step S1103 is executed. If the workflow platform 130 determines that logging in to the cloud storage 150 is not necessary, the process of step S1105 is executed. For example, if the process of the flowchart shown in Fig. 11 has already been executed, collaboration has been completed and therefore logging in is not necessary.

[0102] In step S1103, the workflow platform 130 sends a login request to the cloud storage 150.

[0103] In step S1104, the workflow platform 130 receives the login result from the cloud storage 150. After that, the workflow platform 130 can communicate with the cloud storage 150, assuming that the workflow platform 130 and the cloud storage 150 have been linked.

[0104] In step S1105, the workflow platform 130 acquires a list of settings for the file acquisition action.

[0105] In step S1106, the workflow platform 130 displays a setting screen for the file acquisition action acquired in step S1105. In the file acquisition action, it is necessary to set the target file to be acquired. For example, a workflow is constructed so that the target file to be acquired can be specified from the file path that can be acquired as a result of executing the file creation trigger in Fig. 11 and values ​​that can be acquired from other triggers and actions.

[0106] In step S1107, the workflow platform 130 saves the settings of the set file acquisition action.

[0107] The procedure of FIG. 12 allows the workflow platform 130 to incorporate a get file action into any workflow.

[0108] Fig. 13 is a flowchart showing details of the workflow platform 130 in this system cooperating with the print service 120 to construct a workflow. Fig. 13 is a flowchart of the workflow platform showing a print action according to the first embodiment of the present invention. As an example, in this embodiment, an action for printing a file with a printer specified by the print service 120 is constructed as a workflow action.

[0109] In step S1201, the workflow platform 130 detects a request to add a print action.

[0110] In step S1202, the workflow platform 130 checks whether cooperation with the print service 120 that provides the print action has been set, and determines whether logging in to the print service 120 is required. If the workflow platform 130 determines that logging in to the print service 120 is required, the process of step S1203 is executed. If the workflow platform 130 determines that logging in to the print service 120 is not required, the process of step S1205 is executed.

[0111] In step S 1203 , the workflow platform 130 sends a login request to the print service 120 .

[0112] In step S1204, the workflow platform 130 receives a login result from the print service 120. After that, the workflow platform 130 can communicate with the print service 120, assuming that the workflow platform 130 and the print service 120 have been linked.

[0113] In step S1205, the workflow platform 130 acquires a list of print action settings.

[0114] In step S1206, the workflow platform 130 displays a setting screen for the print action acquired in step S1205. In the print action, for example, as shown in Fig. 10, the specification of the printer to be used for printing, print settings, and settings for specifying the file to be printed are displayed.

[0115] In step S1207, the workflow platform 130 transmits a request to the print service 120 to obtain a printer.

[0116] In step S 1208 , the workflow platform 130 obtains a list of printers from the print service 120 .

[0117] In step S1209, the workflow platform 130 displays the list of printers acquired in step S1208.

[0118] In step S1210, the workflow platform 130 detects that a printer has been selected by the user.

[0119] In step S1211, the workflow platform 130 transmits a print setting acquisition request to the print service 120. At this time, the print setting acquisition request transmitted in step S1211 includes information for identifying the printer.

[0120] In step S1212, the workflow platform 130 receives the print settings from the print service 120.

[0121] In step S1213, the workflow platform 130 displays the print settings received in step S1212.

[0122] In step S1214, the workflow platform 130 detects a change in print settings by the user.

[0123] In step S1215, the workflow platform 130 detects a change in the file to be printed by the user.

[0124] In step S1216, the workflow platform 130 saves the settings of the print action.

[0125] According to the procedure in FIG. 13, the workflow platform 130 cooperates with the print service 120, and can incorporate a print action for performing printing into any workflow.

[0126] Fig. 14 is a flowchart showing details of constructing a workflow in cooperation with the print service 120 in the workflow platform 130 in this system. Fig. 14 is a flowchart of the print service showing a print action according to the first embodiment of the present invention.

[0127] In step S1301, the print service 120 receives a login request from the workflow platform .

[0128] In step S1302, the print service 120 verifies the login request.

[0129] In step S1303, the print service 120 transmits a login result to the workflow platform 130. As a result, the workflow platform 130 and the print service 120 enter a linked state, and can communicate with each other thereafter.

[0130] In step S1304, the print service 120 receives a printer list acquisition request from the workflow platform .

[0131] In step S1305, the print service 120 acquires a list of printers available on the workflow platform 130 from the printers managed by the print service 120. At this time, the available printers may be restricted by, for example, an administrator of the print service 120, who limits whether the account of the print service 120 logged in in steps S1301 to S1303 can use the printers.

[0132] In step S1306, the print service 120 transmits the list of printers acquired in step S1305 to the workflow platform .

[0133] In step S1307, the print service 120 receives the request to obtain print settings from the workflow platform 130. At this time, the request to obtain print settings received in step S1307 includes information for identifying the printer.

[0134] In step S1308, the print service 120 identifies the target printer from the information identifying the printer, and acquires the print settings for that printer model. At this time, the configurable setting items are linked to the account of the print service 120 logged in in steps S1301 to S1303, and the administrator of the print service 120 may be able to restrict each setting. For example, even if the specified printer is capable of single-sided printing, if the administrator has limited it to double-sided printing only, only double-sided printing is transmitted as the print setting.

[0135] In step S1309, the print service 120 transmits the acquired print settings to the workflow platform .

[0136] According to the procedure in FIG. 14, the print service 120 can cooperate with the workflow platform 130 to set a print action for performing printing.

[0137] Fig. 15 is a flowchart showing details of constructing a workflow in cooperation with the print service 120 in the workflow platform 130 in this system. Fig. 15 is a flowchart of the workflow platform showing a reservation printing action according to the first embodiment of the present invention. As an example, in this embodiment, an action for reservation printing of a file on an arbitrary printer managed by the print service 120 is constructed as a workflow action.

[0138] In step S1401, the workflow platform 130 detects a request to add a print action.

[0139] In step S1402, the workflow platform 130 checks whether cooperation with the print service 120 that provides the print action has been set, and determines whether logging in to the print service 120 is required. If the workflow platform 130 determines that logging in to the print service 120 is required, the process of step S1403 is executed. If the workflow platform 130 determines that logging in to the print service 120 is not required, the process of step S1405 is executed.

[0140] In step S 1403 , the workflow platform 130 sends a login request to the print service 140 .

[0141] In step S1404, the workflow platform 130 receives the login result from the print service 140. After that, the workflow platform 130 can communicate with the print service 120, assuming that the workflow platform 130 and the print service 120 have been linked.

[0142] In step S1405, the workflow platform 130 acquires a list of print action settings.

[0143] In step S1406, the workflow platform 130 displays the setting screen for the print action acquired in step S1405. The setting items for the reservation print action are different from those for printing shown in FIG. 14. For example, if reservation print can be printed from any printer, there is no need to specify the print printer. Also, in the case of reservation print, print settings are not necessary because they can be set on the printer screen before printing. Alternatively, print settings may be made possible on the workflow platform 130 as in FIG. 14, with settings that can be changed on the printer screen but are set by default.

[0144] In step S1407, the workflow platform 130 saves the settings of the print action.

[0145] According to the procedure in FIG. 15, the workflow platform 130 cooperates with the print service 120 to incorporate a reservation printing action for performing reservation printing into any workflow.

[0146] Fig. 16 is a flowchart showing details of constructing a workflow in cooperation with chat service 140 in workflow platform 130 in this system. Fig. 16 is a flowchart of the workflow platform showing a notification action according to the first embodiment of the present invention. As an example, in this embodiment, an action for notifying a notification destination specified by chat service 140 is constructed as a workflow action.

[0147] In step S1501, the workflow platform 130 detects a request to add a notification action.

[0148] In step S1502, the workflow platform 130 checks whether cooperation with the chat service 140 that provides the notification action has been set, and determines whether logging in to the chat service 140 is required. If the workflow platform 130 determines that logging in to the chat service 140 is required, the process of step S1503 is executed. If the workflow platform 130 determines that logging in to the chat service 140 is not required, the process of step S1505 is executed.

[0149] In step S 1503 , the workflow platform 130 sends a login request to the chat service 140 .

[0150] In step S1504, the workflow platform 130 receives a login result from the chat service 140. Thereafter, the workflow platform 130 can communicate with the chat service 140, assuming that the workflow platform 130 and the chat service 140 have been linked. As described above, the account for the chat service 140 may be the same account as that for the workflow platform 130, in which case login for linkage is not required.

[0151] In step S1505, the workflow platform 150 acquires a list of notification action settings.

[0152] In step S1506, the workflow platform 150 displays the setting screen for the notification action acquired in step S1505.

[0153] In step S1507, the workflow platform 130 transmits a request to the chat service 140 to obtain a list of notification destinations.

[0154] In step S1508, the workflow platform 130 receives a list of notification destinations from the chat service 140. The notification action settings include the designation of the user or group / channel of the chat service 140 to be the notification destination, the type of notification, the message content of the notification, and the response deadline for the notification. These are only examples, and the notification may not include these or may include other items. The types of notifications include normal general-purpose message notifications, as well as printable notifications, print completion notifications, print error notifications, and approval request notifications. The approval request notification temporarily stops the workflow processing of the workflow platform 130 until approval is permitted. The approval request notification can also specify not only the approval request destination, but also the approval request completion notification destination, which is notified when the approval request is completed. If the approval request completion notification destination is not specified, the notification destination will be the user who executed the workflow.

[0155] In step S1509, the workflow platform 130 saves the notification action settings.

[0156] According to the procedure of FIG. 16, the workflow platform 130 cooperates with the chat service 140, and an action for sending a notification from the chat service 140 can be incorporated into any workflow.

[0157] Next, a flowchart for executing a workflow configured by the procedures described in FIG. 11 to FIG. 16 will be described. In this embodiment, the operation at the time of execution of a workflow in which approval of a quotation is obtained, the quotation is automatically printed when approved, and the print result is notified is shown. Note that this embodiment is merely an example, and the services to be combined and the order of the services are not limited to this. For example, in this embodiment, the workflow is started by being triggered by saving a file in the cloud storage 150, but the present invention is not limited to this. For example, a workflow may be triggered by scanning with the printer 110. Also, a list of workflows already constructed in the workflow platform 130 may be displayed on the chat service 140, so that a workflow selected from the chat service 140 can be executed.

[0158] Fig. 17 is a flowchart showing the operation when the workflow is executed in the workflow platform 130 in this system. Fig. 17 is a flowchart of the workflow platform when executing a workflow according to the first embodiment of the present invention.

[0159] In step S1601, the workflow platform 130 receives a message that a file has been saved in a specified folder from the cloud storage 150. The file is, for example, a document file of an estimate.

[0160] In step S1602, the workflow platform 130 receives the notification and starts the corresponding workflow.

[0161] In step S1603, the workflow platform 130 acquires file information from the file received in step S1601. The acquired file information is information necessary for the print service 120 to print the file, such as the contents of the file itself, or a URL and file name from which the file can be downloaded.

[0162] In step S1604, the workflow platform 130 transmits an approval notification request to the chat service 140. This approval notification request includes the notification destination set in advance in the flowchart of FIG.

[0163] In step S1605, the workflow platform 130 receives from the chat service 140 whether the result of the approval request is successful or rejected, and determines the result. If the workflow platform 130 determines that the result of the approval request is successful, the process of step S1606 is executed. If the workflow platform 130 determines that the result of the approval request is not successful, the process is terminated.

[0164] In step S1606, the workflow platform 130 transmits a print job to the print service 120. The file that is transmitted at this time is the file acquired in step S1603. Furthermore, at this time, the printing may be either normal printing as shown in Fig. 15 or reservation printing as shown in Fig. 16.

[0165] In step S1607, the workflow platform 130 receives the print result from the print service 120.

[0166] In step S1608, the workflow platform 130 determines whether the print result received in step S1607 was successful. If the workflow platform 130 determines that the print was successful, the process proceeds to step S1609. If the workflow platform 130 determines that the print was not successful, the process proceeds to step S1610.

[0167] In step S1609, the workflow platform 130 sends a print success notification request to the chat service 140, and ends the process. This print success notification request includes the notification destination information set in advance in the flowchart of FIG.

[0168] In step S1610, the workflow platform 130 transmits a print failure notification request to the chat service 140. This print failure notification request includes notification destination information that is set in advance in the flowchart of FIG.

[0169] In this embodiment, the workflow platform 130 notifies the user of the success or failure of printing through the chat service 140, but the print service 120 may perform a similar notification process instead of the workflow platform 130. In this case, the notification may be sent to, for example, the user who started the workflow, the user who executed the printing included in the workflow, or multiple users including these.

[0170] In step S1611, the workflow platform 130 determines whether or not a reprint instruction has been received from the print service 120. If the workflow platform 130 determines that a reprint instruction has been received, the process of step S1606 is executed. If the workflow platform 130 determines that a reprint instruction has not been received, the process is terminated.

[0171] According to the procedure in FIG. 17, the workflow platform 130 can cooperate with the print service 120, the cloud storage 150, and the chat service 140 to execute a workflow and print a file.

[0172] Fig. 18 is a flowchart showing the operation when a workflow is executed in the workflow platform 130 in this system. Fig. 18 is a flowchart of a print service when a workflow is executed according to the first embodiment of the present invention.

[0173] In step S1701, the print service 120 receives a print job from the workflow platform .

[0174] In step S1702, the print service 120 determines whether the received job is reservation printing. If the print service 120 determines that the job is reservation printing, the process proceeds to step S1703. If the print service 120 determines that the job is not reservation printing, the process proceeds to step S1707.

[0175] In step S1703, the print service 120 adds the received print job to the print job list.

[0176] In step S 1704 , the print service 120 receives a print job list acquisition request from the printer 110 .

[0177] In step S1705, the print service 120 transmits the print job list to the printer 110. The print job list includes a print job identifier that identifies the print job.

[0178] In step S1706, the print service 120 receives a print instruction from the printer 110. The print instruction includes a print job identifier that identifies the print job.

[0179] In step S 1707 , the print service 120 identifies the print job to be sent from the print job identifier, and sends the print job to the printer 110 .

[0180] In step S 1708 , the print service 120 receives the print result from the printer 110 .

[0181] In step S1709, the print service 120 determines whether the printing was successful. If the print service 120 determines that the printing was successful, the process proceeds to step S1710. If the print service 120 determines that the printing was not successful, the process proceeds to step S1713.

[0182] In step S1710, the print service 120 notifies the workflow platform 130 of the success of printing.

[0183] In step S1711, the print service 120 determines whether the successfully printed job is reservation printing. If the print service 120 determines that the job is reservation printing, the process of step S1712 is executed. If the print service 120 determines that the job is not reservation printing, the process is terminated.

[0184] In step S1712, the print service 120 deletes the successfully printed print job from the print job list, and ends the process.

[0185] In step S1713, the print service 120 notifies the workflow platform 130 of the print failure. If the print failure occurs, reprinting is possible.

[0186] In step S1714, the print service 120 determines whether or not a reprint instruction has been received from the printer 110. If the print service 120 determines that a reprint instruction has been received, the process proceeds to step S1715. If the print service 120 determines that a reprint instruction has not been received, the process ends.

[0187] In step S1715, the print service 120 sends a reprint instruction to the workflow platform 130, and ends the process.

[0188] According to the procedure in FIG. 18, the print service 120 can cooperate with the printer 110 and the workflow platform 130 to execute the workflow and print the file.

[0189] Fig. 19 is a flowchart showing print processing when a workflow is executed in this system, Fig. 19 is a flowchart showing printing by a printer when a workflow is executed according to the first embodiment of the present invention.

[0190] In step S 1801 , the printer 110 receives a print job from the print service 120 .

[0191] In step S1802, the printer 110 executes and prints the received print job.

[0192] In step S1803, the printer 110 determines whether or not the printing was successful. If the printer 110 determines that the printing was successful, the process proceeds to step S1804. If the printer 110 determines that the printing was not successful, the process proceeds to step S1805.

[0193] In step S1804, the printer 110 transmits a notification of printing success to the print service 120, and the process ends.

[0194] In step S1805, the printer 110 notifies the print service 120 of the printing failure.

[0195] In step S1806, the printer 110 waits for a reprint instruction from the user and determines whether or not a reprint instruction is detected. If the printer 110 determines that a reprint instruction is detected, the process proceeds to step S1807. If the printer 110 determines that a reprint instruction is not detected, the process ends.

[0196] In step S1807, the printer 110 transmits a reprint instruction to the print service 120. After that, the printer 110 executes the process again from step S1801.

[0197] The procedure in FIG. 19 enables the printer 110 to print a file in cooperation with the print service 120.

[0198] Fig. 20 is a flowchart showing reservation printing processing when a workflow is executed in this system. Fig. 20 is a flowchart showing reservation printing performed by a printer when a workflow is executed according to the first embodiment of the present invention.

[0199] In step S1901, the printer 110 displays a print job list.

[0200] In step S1902, the printer 110 detects a print job selection by the user. At this time, print settings may be made on the UI of the printer 110.

[0201] In step S1903, the printer 110 transmits a print instruction for the detected print job. The subsequent processes in steps S1904 to S1910 are similar to the processes in steps S1801 to S1807 described above, and therefore will not be described here.

[0202] According to the procedure in FIG. 20, the printer 110 can cooperate with the print service 120 to reserve and print a file.

[0203] Fig. 21 is a flowchart showing the operation of approval and notification when a workflow is executed in this system. Fig. 21 is a flowchart showing the sending and receiving of notification requests by a chat service when a workflow is executed according to the first embodiment of the present invention.

[0204] In step S2001, the chat service 140 receives a notification request from the workflow platform 130.

[0205] In step S2002, the chat service 140 acquires the notification destination included in the notification request received in step S2001.

[0206] In step S2003, the chat service 140 determines whether the notification request received in step S2001 is an approval request. If the chat service 140 determines that the notification request is an approval request, the process proceeds to step S2004. If the chat service 140 determines that the notification request is not an approval request, the process proceeds to step S2010.

[0207] In step S2004, the chat service 140 acquires the requester of the approval request, which is the notification request received in step S2001.

[0208] In step S2005, the chat service 140 acquires the post-approval notification destination of the approval request, which is the notification request received in step S2001.

[0209] In step S2006, the chat service 140 adds the approval request to the approval list of notification destinations acquired in step S2002, together with the requester acquired in step S2004 and the post-approval notification destination acquired in step S2005.

[0210] Also, in step S2006, the chat service 140 changes the display of the badge 510 on the workflow list screen 500 of the client PC 111 that operates the chat service 140. The badge 510 is a badge that indicates the number of unprocessed approval notifications that have arrived at the chat service 140. If the number of unprocessed approval notifications up to now is zero, the badge 510 is not displayed, so the chat service 140 displays the badge 510. If the number of unprocessed approval notifications up to now is other than zero, the badge 510 is displayed, so the chat service 140 increments the number displayed in the badge 510 by 1. The chat service 140 can inform the user that an approval request has arrived by displaying the badge 510. Also, the chat service 140 may display a notification of the approval request in a notification area of ​​the client PC 111 that operates the chat service 140.

[0211] In step S2007, the chat service 140 determines whether the added approval request has been approved. If the chat service 140 determines that the approval request has been approved, the process proceeds to step S2008. If the chat service 140 determines that the approval request has not been approved, the process proceeds to step S2009.

[0212] In step S2008, the chat service 140 notifies the workflow platform 130 that the request has been approved.

[0213] In step S2009, the chat service 140 notifies the workflow platform 130 of the denial.

[0214] In step S2010, the chat service 140 adds the notification contents to the notification list of the notification recipient. Here, if it was not an approval request, the notification result that came with the notification request is added, and if it was an approval request, the approval result is added.

[0215] Also, in step S2010, the chat service 140 changes the display of the badge 509 on the workflow list screen 500 of the client PC 111 that operates the chat service 140. The badge 509 is a badge that indicates the number of unread notifications that have arrived at the chat service 140. If the number of unread notifications up to now is 0, the badge 509 is not displayed, so the chat service 140 displays the badge 509. If the number of unread notifications up to now is other than 0, the badge 509 is displayed, so the chat service 140 increments the number displayed in the badge 509 by 1. The chat service 140 can inform the user that a notification has arrived by displaying the badge 509. Also, the chat service 140 may display the presence of an unread notification in a notification area of ​​the client PC 111 that operates the chat service 140.

[0216] The procedure in FIG. 21 enables the chat service 140 to cooperate with the workflow platform 130 to display a notification to the user.

[0217] Next, a workflow for sending a notification will be described with reference to Fig. 22, Fig. 23, and Fig. 24. Fig. 22 and Fig. 23 are flowcharts showing a notification performed by a print service when a workflow is executed according to the first embodiment of the present invention. The circled letters shown in Fig. 22 are connected to the same letters in the circled letters shown in Fig. 23. Fig. 24 is a flowchart showing a notification destination determined by a print service when a workflow is executed according to the first embodiment of the present invention.

[0218] In this embodiment, in the series of flowcharts, a maximum of four notifications are issued: when a reserved print job is submitted (step S2104), when printing is interrupted (step S2111), when printing is successful (step S2114), and when printing fails (step S2115).

[0219] The notification is sent from the print service 120, but may also be sent from the workflow platform 130. When sending a notification from the workflow platform 130, another process may be performed between the execution of the print job and the notification of the print result, and the result may be reflected in the notification content. The notification may be sent not only at the time of printing but also at the time of scanning, and may be sent before or after the job is executed. For example, the result data may be included in the notification content after the execution of a scan job. For example, a request for approval of the print content may be sent before printing, or a notification may be sent that the print job has been reserved at the printer. Note that this embodiment is merely an example, and the combined processes, their order, and the method of obtaining the notification destination are not limited to this.

[0220] 22 and 23 are flowcharts showing a notification process in the print service 120 when a print connector is executed in the workflow platform 130. Steps S2101 to S2103 are similar to the above-mentioned steps S1701 to S1703, and therefore will not be described here.

[0221] In step S2104, the print service 120 notifies the chat service 140 of the addition of a print job. Steps S2105 to S2109 are similar to the above-mentioned steps 1704 to 1708, and therefore a description thereof will be omitted here.

[0222] In step S2110, the print service 120 determines whether the print result indicates that printing has been interrupted. If the print service 120 determines that printing has been interrupted, the process proceeds to step S2111. If the print service 120 determines that printing has not been interrupted, the process proceeds to step S2113.

[0223] In step S2111, the print service 120 notifies the chat service 130 of the reason for the interruption and the countermeasure, and allows printing to be resumed or terminated. Note that the notification destination does not need to be unified within one workflow, and may be set individually depending on the purpose of the notification. For example, the notification destination may be the print executor set as the notification destination of successful printing, and the printer administrator who handles device errors such as running out of ink or paper jams.

[0224] In step S2112, the print service 120 waits for a print resume notification from the chat service 140, and determines whether or not the print resume notification has been received. In step S2112, the print service 120 may receive the print resume notification from the printer 110. If the print service 120 determines that the print resume notification has been received, the process proceeds to step S2109. If the print service 120 determines that the print resume notification has not been received due to a timeout or the like, the process proceeds to step S2117.

[0225] In step S2113, the print service 120 determines whether the printing was successful. If the print service 120 determines that the printing was successful, the process proceeds to step S2114. If the print service 120 determines that the printing was not successful, the process proceeds to step S2115.

[0226] In step S2114, the print service 120 notifies the chat service 140 of the success of the printing. The print result may be notified not only to an individual address but also to a group of the chat service 140.

[0227] In step S2115, the print service 120 notifies the chat service 140 of the printing failure, allowing reprinting or terminating the print job.

[0228] In step S2116, the print service 120 waits for a reprint notification from the chat service 140 and determines whether or not a reprint notification has been received. In step S2116, the print service 120 may receive a reprint notification from the printer 110. If the print service 120 determines that a reprint notification has been received, the process proceeds to step S2109. If the print service 120 determines that a reprint notification has not been received due to a timeout or the like, the process proceeds to step S2117.

[0229] In step S2117, the print service 120 determines whether the print is reservation printing. If the print service 120 determines that the print is reservation printing, the process proceeds to step S2118. If the print service 120 determines that the print is not reservation printing, the process proceeds to step S2119.

[0230] In step S2118, the print service 120 deletes the print job.

[0231] In step S2119, the print service 120 notifies the workflow platform 130 of the end of the print job, and ends the process.

[0232] 22 and 23, the print service 120 can cooperate with the chat service 140 to notify the print result.

[0233] FIG. 24 is a flowchart of a process relating to a method for determining a notification destination when a notification request occurs in step S2104, step S2111, step S2114, or step S2115 in FIGS.

[0234] In step S2201, the print service 120 detects a notification request.

[0235] In step S2202, the print service 120 checks the print job and determines whether a notification destination has been specified. If the print service 120 determines that a notification destination has been specified, the process proceeds to step S2203. If the print service 120 determines that a notification destination has not been specified, the process proceeds to step S2204.

[0236] In step S2203, the print service 120 sends a notification to the chat service 140 that is the designated notification destination.

[0237] If the notification destination is not specified, the print service 120 checks the cause of the notification in step S2204 and subsequent steps.

[0238] In step S2204, the print service 120 determines whether printing has been interrupted. If the print service 120 determines that printing has been interrupted, the process proceeds to step S2205. If the print service 120 determines that printing has not been interrupted, the process proceeds to step S2207.

[0239] In step S2205, the print service 120 acquires the notification destination of the printer administrator in the chat service 140 from the printer administrator information. The printer administrator information is information managed in the print service 120, for example, by linking information capable of identifying a printer with the notification destination in the chat service 140 of the printer administrator who manages the printer.

[0240] In step S2206, the print service 120 notifies the notification destination of the printer administrator acquired in step S2205 of a method for dealing with the error that caused the printing interruption.

[0241] In step S2207, the print service 120 determines whether or not printing has failed. If the print service 120 determines that printing has failed, the process proceeds to step S2208. If the print service 120 determines that printing has not failed, the process ends.

[0242] In step S2208, the print service 120 acquires the notification destination of the print performer in the chat service 140 from the print performer information. The print performer information is information managed in the print service 120, for example, by linking information capable of identifying a print job with the notification destination in the chat service 140 of the print performer who executed the print job.

[0243] In step S2209, the print service 120 notifies the notification destination of the print executor acquired in step S2208 of the print failure.

[0244] In this embodiment, the notification destination is obtained from the print service 120, but a request to obtain account information may be made to the workflow service 130. When notification of the print result is not essential, such as when printing is successful or when a reserved print job is submitted, the process ends without notification.

[0245] By using the procedure in FIG. 24, even if a notification destination has not been set, an appropriate notification destination can be obtained and notified when an error occurs.

[0246] As described above, according to this embodiment, the workflow platform 130 can print a file using the printer 110 while cooperating with a plurality of services and the print service 120, and can notify the chat service 140 of the print result.

[0247] (Other embodiments) The present invention can also be realized by a process in which a program for realizing one or more functions of the above-mentioned embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. Also, the present invention can be realized by a circuit (e.g., ASIC) for realizing one or more functions.

[0248] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of the gist of the present invention.

[0249] The disclosure of this embodiment includes the following configurations and methods. (Configuration 1) A print system that performs printing from a workflow, a workflow platform for executing the workflow; A chat service capable of notifying a user; A print service that prints on a printer; having the workflow platform includes a workflow construction unit that constructs the workflow in cooperation with the chat service and the print service, and a workflow execution unit that executes the workflow; The workflow execution means executes printing using the print service in accordance with the workflow to be executed, and notifies the result of the printing executed using the print service via the chat service. A printing system comprising: (Configuration 2) The workflow execution means notifies the user through the chat service when a reserved print job is created. 2. The printing system according to claim 1, (Configuration 3) The workflow execution means notifies the user through the chat service when printing is interrupted. 3. The print system according to configuration 1 or 2. (Configuration 4) The workflow execution means notifies the user through the chat service when printing is successful or unsuccessful. 4. The printing system according to any one of configurations 1 to 3. (Configuration 5) When a notification destination is not specified when notifying via the chat service, the workflow execution means notifies the notification destination of the printer manager or the print executor. 5. The printing system according to any one of configurations 1 to 4. (Configuration 6) The workflow execution means determines whether or not login to the chat service is required, and if login is required, transmits a login request to the chat service and then communicates with the chat service. 6. The printing system according to any one of configurations 1 to 5, (Configuration 7) The workflow execution means transmits an approval notification request to the chat service, and receives a result of the approval notification request via the chat service. 7. The printing system according to any one of configurations 1 to 6, (Configuration 8) The workflow execution means notifies the print result of the print service via the chat service. 8. The printing system according to any one of configurations 1 to 7, (Configuration 9) The workflow execution means notifies a printer manager via the chat service when the print result in the print service is interrupted. 9. The printing system according to configuration 8. (Configuration 10) If the print result in the print service is unsuccessful, the workflow execution means notifies the print executor via the chat service. 10. The print system according to configuration 8 or 9. (Configuration 11) When the print result in the print service is interrupted, the workflow execution means notifies the user of the reason for the interruption and a method of dealing with the interruption via the chat service. 11. The printing system according to any one of configurations 8 to 10. (Configuration 12) When the print result in the print service is interrupted and a print restart notification is not received, if the print is a reserved print, the workflow execution means deletes the print job of the print. 12. The printing system according to any one of configurations 1 to 11. (Configuration 13) The workflow execution means executes creation, execution and approval of the workflow via the chat service. 13. The printing system according to any one of configurations 1 to 12. (Configuration 14) A workflow platform for executing a workflow, comprising: The method includes: constructing the workflow in cooperation with a chat service that notifies a user and a print service that prints on a printer; and executing the workflow, The workflow execution means executes printing using the print service in accordance with the workflow to be executed, and notifies the result of the printing executed using the print service via the chat service. A workflow platform characterized by: (Method 1) A control method for a print system that performs printing from a workflow, comprising the steps of: The print system includes a workflow platform that executes the workflow, a chat service that notifies a user, and a print service that prints using a printer; the workflow platform includes a workflow construction step for constructing the workflow in cooperation with the chat service and the print service, and a workflow execution step for executing the workflow, The workflow execution step executes printing by the print service in accordance with the workflow to be executed, and notifies the result of the printing executed by the print service by the chat service. A method for controlling a print system comprising: [Explanation of symbols]

[0250] 10: Workflow system 110: Printer 120: Print service 130: Workflow Platform 140: Chat service

Claims

1. A print system that performs printing from a workflow, a workflow platform for executing the workflow; A chat service for notifying the user; A print service that prints on a printer; having the workflow platform includes a workflow construction unit that constructs the workflow in cooperation with the chat service and the print service, and a workflow execution unit that executes the workflow; The workflow execution means executes printing using the print service in accordance with the workflow to be executed, and notifies the result of the printing executed using the print service via the chat service. A printing system comprising:

2. The workflow execution means notifies the user through the chat service when a reserved print job is created.

2. The printing system according to claim 1.

3. The workflow execution means notifies the user through the chat service when printing is interrupted.

2. The printing system according to claim 1.

4. The workflow execution means notifies the user through the chat service when printing is successful or unsuccessful.

2. The printing system according to claim 1.

5. When a notification destination is not specified when notifying via the chat service, the workflow execution means notifies the notification destination of the printer manager or the print executor.

2. The printing system according to claim 1.

6. The workflow execution means determines whether or not login to the chat service is required, and if login is required, transmits a login request to the chat service and then communicates with the chat service.

2. The printing system according to claim 1.

7. The workflow execution means transmits an approval notification request to the chat service, and receives a result of the approval notification request via the chat service.

2. The printing system according to claim 1.

8. The workflow execution means notifies the print result of the print service via the chat service.

2. The printing system according to claim 1.

9. The workflow execution means notifies a printer manager via the chat service when the print result in the print service is interrupted.

9. The printing system according to claim 8.

10. If the print result in the print service is unsuccessful, the workflow execution means notifies the print executor via the chat service.

9. The printing system according to claim 8.

11. When the print result in the print service is interrupted, the workflow execution means notifies the user of the reason for the interruption and a method of dealing with the interruption via the chat service.

9. The printing system according to claim 8.

12. When the print result in the print service is interrupted and a print restart notification is not received, if the print is a reserved print, the workflow execution means deletes the print job of the print.

9. The printing system according to claim 8.

13. The workflow execution means executes creation, execution and approval of the workflow via the chat service.

2. The printing system according to claim 1.

14. A workflow platform for executing a workflow, comprising: The method includes: constructing the workflow in cooperation with a chat service that notifies a user and a print service that prints on a printer; and executing the workflow, The workflow execution means executes printing using the print service in accordance with the workflow to be executed, and notifies the result of the printing executed using the print service via the chat service. A workflow platform characterized by:

15. A control method for a print system that performs printing from a workflow, comprising the steps of: The print system includes a workflow platform that executes the workflow, a chat service that notifies a user, and a print service that prints using a printer; the workflow platform includes a workflow construction step for constructing the workflow in cooperation with the chat service and the print service, and a workflow execution step for executing the workflow, The workflow execution step executes printing by the print service in accordance with the workflow to be executed, and notifies the result of the printing executed by the print service by the chat service. A method for controlling a print system comprising:

Images