JP2016174228A - Apparatus, information processing system, information processing method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an apparatus that can restrict prescribed communication by the apparatus.SOLUTION: An apparatus includes: a reading unit that reads image data from an original document; and a control unit that displays a first screen including a list of a plurality of processing flows each including one or more processing units related to the image data read by the reading unit, and controls the execution of a processing flow selected from the list of the processing flows. If restriction information indicating that data transmission of image data to a prescribed communication destination is restricted is stored in association with identification information on an operator of the apparatus, the control unit displays the first screen in the state in which the selection of a processing flow including a processing unit to perform the data transmission is restricted.SELECTED DRAWING: Figure 4

Description

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

  Some devices such as multifunction peripherals can execute a workflow using image data scanned by the device using a cloud service or the like as described in the cited document 1. Since the cloud service has abundant resources, it is possible to obtain a high-quality processing result at high speed by causing the cloud service to execute a part or all of each processing unit constituting the workflow.

  However, it is not preferable in terms of security that communication with the outside of the intranet in a company is used without limitation. Even if the device itself is designed firmly against the threat to communication with the outside, there is a possibility of information leakage due to communication with the outside. Therefore, as a system administrator, the communication with the outside is left open. I am worried about keeping it. Therefore, it is desirable to appropriately limit communication with the outside.

  The present invention has been made in view of the above points, and an object of the present invention is to make it possible to limit predetermined communication by a device.

In order to solve the above problem, the device includes a reading unit that reads image data from a document, and a processing flow that includes one or more processing units related to image data read by the reading unit. And a control unit that controls execution of a processing flow selected from the list of processing flows.
The control unit is associated with the identification information of the operator of the device, and when the restriction information indicating that data transmission of the image data to a predetermined communication destination is restricted is stored, the data The first screen is displayed in a state where selection of a processing flow including a processing unit for transmission is limited.

  Predetermined communication by the device can be restricted.

It is a figure which shows the structural example of the information processing system in embodiment of this invention. It is a figure which shows the hardware structural example of the cloud server in embodiment of this invention. It is a figure which shows the hardware structural example of the apparatus in embodiment of this invention. It is a figure which shows the function structural example of each apparatus in the information processing system of embodiment of this invention. It is a figure which shows the function structural example corresponding to a server version. It is a figure which shows the function structural example corresponding to a serverless version. It is a figure which shows the function structural example corresponding to a cloud version. It is a figure for demonstrating an example of the outline | summary of the process sequence of the workflow in a server version. It is a figure for demonstrating an example of the outline | summary of the process sequence of the workflow in a serverless version. It is a figure for demonstrating an example of the outline | summary of the 1st process procedure of the workflow in a cloud version. It is a figure for demonstrating an example of the outline | summary of the 2nd processing procedure of the workflow in a cloud version. It is a figure which shows the example of a display of an installation screen. It is a sequence diagram for demonstrating an example of the process sequence of the construction process of a serverless system configuration. It is a figure which shows the example of a display of a menu screen. It is a figure which shows the example of a display of a cloud cooperation setting screen. It is a figure which shows the example of a display of a profile edit screen. It is a figure which shows the example of a display of a profile setting screen. It is a figure which shows the example of a display of a project setting screen. It is a figure which shows the structural example of a profile table. It is a figure which shows the structural example of a project table. It is a figure which shows the example of a display of an apparatus setting screen. It is a figure which shows the structural example of an apparatus information table. It is a figure which shows the example of a display of a user setting screen. It is a figure which shows the structural example of a user information table. It is a sequence diagram for demonstrating an example of the process sequence of the synchronous process of the setting information in a serverless version. It is a sequence diagram for demonstrating an example of the process sequence of the execution process of a workflow in case a login user is yoko. It is a figure which shows the example of a display of a project list screen. It is a figure which shows the example of a display of a setting change screen. It is a figure which shows the example of a display of a reading condition setting screen. It is a sequence diagram for demonstrating an example of the process sequence of the execution process of a workflow in case a login user is taro.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration example of an information processing system according to an embodiment of the present invention. In the information processing system 1 shown in FIG. 1, the user environment E1, the cloud server 20, and one or more online storage systems 90 can be communicated via a wide area network such as the Internet.

  The cloud server 20 executes, as a cloud service, a part or all of a process relating to image data (hereinafter referred to as “scanned image (image data)”) scanned from a document in the device 10 of the user environment E1. This is the above computer. A workflow refers to, for example, a process flow (process flow) realized by an arbitrary combination of one or more processing units (tasks) that realize functions independently or independently. In the present embodiment, a workflow including image conversion for a scanned image and distribution processing for the scanned image or image conversion result as processing units (components) will be described. However, the contents of image conversion, the distribution method, and the like may differ for each defined workflow. In the present embodiment, a cloud service will be described as a specific example. However, the present embodiment relates to a service provided via a network such as a service provided by an ASP (Application Service Provider) or a Web service. Forms may be applied.

  The online storage system 90 is a computer system that provides a cloud service called online storage via a network. Online storage is a service that lends a storage area of the storage. In the present embodiment, the storage area lent out by the online storage is a candidate for a storage destination (distribution destination) of a scanned image or data obtained by performing image processing on the scanned image in a workflow.

  The user environment E1 is a system environment (for example, an intranet) of a person who has signed a use contract for a service provided by the cloud server 20 (hereinafter referred to as “tenant”). The tenant is, for example, a company. A department that constitutes a company, or an organization, group, or individual other than the company may be a tenant. In the user environment E1, one or more devices 10, the local server 30, the administrator terminal 40, the authentication server 50, the file server 60, the FTP server 70, and the like are connected via a network constituting an intranet such as a LAN (Local Area Network). Connected.

  The device 10 is an image forming apparatus having a scanning function. In addition to the scan function, a multifunction device having functions such as printing, copying, or fax (FAX) communication may be used as the device 10. In the present embodiment, the device 10 also functions based on the input of a scan image that is a processing target of a workflow.

  The local server 30 is one or more computers that execute part or all of the processing units of the workflow relating to the scanned image. The devices 10 and the like that can access the local server 30 are limited to the devices 10 and the like that belong to the same user environment E1.

  The authentication server 50 is one or more computers that perform authentication of a user who operates the device 10.

  The administrator terminal 40 is a terminal used by a system administrator in the user environment E1. Examples of the administrator terminal 40 include a PC (Personal Computer), a PDA (Personal Digital Assistance), a tablet-type terminal, a smartphone, or a mobile phone. In the present embodiment, the administrator terminal 40 is used for setting for enabling the use of a workflow.

  The file server 60 and the FTP server 70 are computers that are candidates for storage destinations (distribution destinations) of scanned images or data obtained by performing image processing on the scanned images in a workflow.

  FIG. 2 is a diagram illustrating a hardware configuration example of the cloud server according to the embodiment of the present invention. The cloud server 20 of FIG. 2 includes a drive device 200, an auxiliary storage device 202, a memory device 203, a CPU 204, and an interface device 205 that are connected to each other via a bus B.

  A program for realizing processing in the cloud server 20 is provided by a recording medium 201 such as a CD-ROM. When the recording medium 201 storing the program is set in the drive device 200, the program is installed from the recording medium 201 to the auxiliary storage device 202 via the drive device 200. However, it is not always necessary to install the program from the recording medium 201, and the program may be downloaded from another computer via a network. The auxiliary storage device 202 stores the installed program and stores necessary files and data.

  The memory device 203 reads the program from the auxiliary storage device 202 and stores it when there is an instruction to start the program. The CPU 204 executes functions related to the cloud server 20 according to programs stored in the memory device 203. The interface device 205 is used as an interface for connecting to a network.

  The cloud server 20 may be composed of a plurality of computers having hardware as shown in FIG. That is, the processing executed by the cloud server 20 in the later description may be executed by being distributed to a plurality of computers.

  Further, the local server 30, the authentication server 50, the administrator terminal 40, the file server 60, the FTP server 70, and the like may have hardware as shown in FIG.

  FIG. 3 is a diagram illustrating a hardware configuration example of the device according to the embodiment of the present invention. 3, the device 10 includes hardware such as a controller 11, a scanner 12, a printer 13, a modem 14, an operation panel 15, a network interface 16, and an SD card slot 17.

  The controller 11 includes a CPU 111, a RAM 112, a ROM 113, an HDD 114, an NVRAM 115, and the like. The ROM 113 stores various programs and data used by the programs. The RAM 112 is used as a storage area for loading a program, a work area for the loaded program, and the like. The CPU 111 realizes various functions by processing a program loaded in the RAM 112. The HDD 114 stores a program and various data used by the program. The NVRAM 115 stores various setting information and the like.

  The scanner 12 is hardware (image reading means) for reading image data from a document. The printer 13 is hardware (printing means) for printing print data on printing paper. The modem 14 is hardware for connecting to a telephone line, and is used to execute transmission / reception of image data by FAX communication. The operation panel 15 is hardware including input means such as buttons for accepting input from the user, display means such as a liquid crystal panel, and the like. The network interface 16 is hardware for connecting to a network such as a LAN (whether wired or wireless). The SD card slot 17 is used for reading a program stored in the SD card 80. That is, in the device 10, not only the program stored in the ROM 113 but also the program stored in the SD card 80 can be loaded into the RAM 112 and executed. The SD card 80 may be replaced by another recording medium (for example, a CD-ROM or a USB (Universal Serial Bus) memory). That is, the type of recording medium corresponding to the positioning of the SD card 80 is not limited to a predetermined one. In this case, the SD card slot 17 may be replaced by hardware corresponding to the type of recording medium.

  By the way, in this embodiment, three types of system configurations can be selected for the information processing system 1 shown in FIG. The first is a server version, the second is a serverless version, and the third is a cloud version.

  The server version is a system configuration when the local server 30 is used in the execution of a workflow.

  The serverless version is a system configuration when the local server 30 is not used in the execution of the workflow. That is, the server version and the serverless version “server” refer to the local server 30.

  In the cloud version, the local server 30 is not used in the execution of the workflow, and information managed in the user environment E1 (for example, information for authenticating the user) in the server version and the serverless version This is a system configuration in which management is performed by the cloud server 20.

  Note that the system configuration of the server version, the serverless version, and the cloud version can be freely selected for each tenant, for example. For example, each tenant adopts one of these three system configurations according to the convenience of the user environment E1 of the tenant. That is, in these three system configurations, not all devices shown in FIG. 1 are necessarily required. For example, the local server 30 is unnecessary in the serverless version. In the cloud version, in addition to the local server 30, the authentication server 50 is also unnecessary.

FIG. 4 is a diagram illustrating a functional configuration example of each device in the information processing system according to the embodiment of this invention. Function In FIG. 4, the device 10 includes a flow control unit 121. The flow control unit 121 is realized by processing in which one or more programs installed in the device 10 are executed by the CPU 111. The device 10 also uses the flow setting storage unit 122. The flow setting storage unit 122 can be realized using the HDD 114, for example.

  The flow control unit 121 controls reading of a scanned image from a document and executes processing for starting a workflow related to the scanned image. In the server version, the flow control unit 121 transmits the scanned image to the flow control unit 31 of the local server 30. In this case, the execution of the workflow is controlled by the local server 30. For example, the local server 30 performs image conversion on the scanned image, distribution of the converted data, and the like.

  In the serverless version, the flow control unit 121 controls the execution of the workflow. For example, the flow control unit 121 distributes the scanned image. However, even in the serverless version, when it is specified that the cloud server 20 performs image conversion in the workflow setting, the flow control unit 121 sends the scanned image to the image conversion unit 25 of the cloud server 20. The data is transmitted and the converted data is taken from the cloud server 20 and transmitted to the distribution destination.

  In the cloud version, if the distribution destination is external (such as the online storage system 90 outside the user environment E1), the flow control unit 121 transmits the scanned image to the flow control unit 21 of the cloud server 20. In this case, the execution of the workflow is controlled by the cloud server 20. For example, the cloud server 20 executes image conversion regarding the scanned image, distribution of the converted data, and the like. On the other hand, if the distribution destination is the file server 60 or the FTP server 70 in the user environment E1, the flow control unit 121 controls the execution of the workflow. In this case, the flow control unit 121 transmits the scanned image to the image conversion unit 25 of the cloud server 20, takes the converted data from the cloud server 20, and transmits it to the distribution destination.

  The flow setting storage unit 122 stores setting information related to a workflow (hereinafter referred to as “flow setting information”). The flow setting information stored in the flow setting storage unit 122 is necessary when the flow control unit 121 controls execution of a workflow.

  The local server 30 includes a flow control unit 31, a setting processing unit 32, a cloud cooperation unit 33, and the like. Each of these units is realized by processing that one or more programs installed in the local server 30 cause the CPU of the local server 30 to execute. The local server 30 also uses the flow setting storage unit 34 and the cloud cooperation information storage unit 35. Each of these storage units can be realized using, for example, an auxiliary storage device of the local server 30 or a storage device that can be connected to the local server 30 via a network.

  The flow control unit 31 controls the execution of the workflow for the scan image transmitted from the flow control unit 121 of the device 10. In the workflow setting, when it is specified that the cloud server 20 performs image conversion, the flow control unit 31 transmits the scanned image to the image conversion unit 25 of the cloud server 20, and converts the converted data. It is taken from the cloud server 20 and transmitted to the distribution destination.

  The flow setting storage unit 34 stores flow setting information. The flow setting information stored in the flow setting storage unit 34 is necessary when the flow control unit 31 controls the execution of the workflow.

  The setting processing unit 32 receives input such as flow setting information.

  The cloud cooperation unit 33 receives input of setting information related to cooperation with the cloud server 20 (hereinafter referred to as “cloud cooperation information”). The cloud cooperation information storage unit 35 stores cloud cooperation information.

  The administrator terminal 40 includes a setting processing unit 41, a cloud cooperation unit 42, and the like. Each of these units is realized by processing that one or more programs installed in the administrator terminal 40 cause the CPU of the administrator terminal 40 to execute. The administrator terminal 40 also uses the flow setting storage unit 43 and the cloud cooperation information storage unit 44. The flow setting storage unit 43 and the cloud cooperation information storage unit 44 can be realized using, for example, an auxiliary storage device of the administrator terminal 40 or a storage device that can be connected to the administrator terminal 40 via a network.

  The function of each function unit in the administrator terminal 40 is the same as the function of the function unit having the same name in the local server 30. The local server 30 and the administrator terminal 40 have functions that overlap each other. Each function unit of the local server 30 is used in the server version, and each function unit of the administrator terminal 40 is used in the serverless version and the cloud version.

  The authentication server 50 performs user authentication in the server version and the serverless version. In FIG. 4, the authentication server 50 includes an authentication unit 51. The authentication unit 51 is realized by a process that causes the CPU of the authentication server 50 to execute one or more programs installed in the authentication server 50. The authentication server 50 also uses the authentication information storage unit 52. The authentication information storage unit 52 can be realized using, for example, an auxiliary storage device of the authentication server 50 or a storage device that can be connected to the authentication server 50 via a network.

  The authentication unit 51 authenticates the user (operator) of the device 10. The authentication information storage unit 52 stores authentication information (user name, password, etc.) of the user for each legitimate user.

  The cloud server 20 includes a flow control unit 21, a setting processing unit 22, a cloud cooperation unit 23, an authentication unit 24, an image conversion unit 25, and the like. Each of these units is realized by processing executed by the CPU 204 by one or more programs installed in the cloud server 20. The cloud server 20 also uses a flow setting storage unit 26, an authentication information storage unit 27, and the like. Each of these storage units can be realized using, for example, a storage device that can be connected to the auxiliary storage device 202 or the cloud server 20 via a network.

  The flow control unit 21 controls the execution of the workflow for the scanned image transmitted from the flow control unit 121 of the device 10. When image conversion is specified in the workflow setting, the flow control unit 21 performs image conversion using the image conversion unit 25.

  The setting processing unit 41 receives input such as flow setting information.

  The cloud cooperation unit 23 has an application program interface (API) for receiving a cooperation request (activation request) with the cloud server 20 from the cloud cooperation unit 33 and the cloud cooperation unit 42.

  The authentication unit 24 authenticates the user of the device 10 in the cloud version.

  The image conversion unit 25 executes image conversion processing on the scanned image in response to an image conversion request from the device 10 or an image conversion request from the flow control unit 21. For example, examples of the types of image conversion include conversion to PDF with text (Portable Document Format), conversion to document data of a predetermined application, and the like. In addition, OCR (Optical Character Reader) processing, information extraction processing from barcodes, and the like may be included in the image conversion processing. Note that the hardware resource performance of the cloud server 20 may be very high compared to the device 10 and the local server 30. Therefore, in such a case, the image conversion unit 25 performs high-function and high-quality image conversion compared to the image conversion processing executed by the flow control unit 121 of the device 10 or the flow control unit 31 of the local server 30. Processing can be executed. In this respect, it is meaningful to cause the cloud server 20 to execute image processing.

  The flow setting storage unit 26 stores flow setting information. The authentication information storage unit 27 stores authentication information of the user for each legitimate user.

  The contents of the flow setting storage unit 122, the flow setting storage unit 34, the flow setting storage unit 43, and the flow setting storage unit 26 are synchronized. Therefore, the storage contents of these storage units are basically the same. However, the flow setting storage unit 122, the flow setting storage unit 34, and the flow setting storage unit 43 store flow setting information related to one tenant, whereas the flow setting storage unit 26 stores information related to a plurality of tenants. The difference is that the flow setting information is stored. This also applies to the relationship between the authentication information storage unit 52 and the authentication information storage unit 27.

  Note that not all the functional configurations shown in FIG. 4 are required for each of the three system configurations. For example, FIG. 5 is a diagram illustrating a functional configuration example corresponding to the server version.

  In the tenant adopting the server version, the authentication server 50 is installed, and therefore the authentication unit 24 and the authentication information storage unit 27 of the cloud server 20 are not used for the tenant. Further, in the tenant adopting the server version, since the workflow is controlled by the local server 30, the flow control unit 21 and the flow setting storage unit 26 of the cloud server 20 are not used for the tenant. Further, in the tenant adopting the server version, the setting processing unit 32 of the local server 30 is used, and therefore the setting processing unit 22 of the cloud server 20 is not used for the tenant. Moreover, in the tenant where the server version is adopted, the administrator terminal 40 may not be installed.

  FIG. 6 is a diagram illustrating a functional configuration example corresponding to the serverless version. In a tenant adopting the serverless version, since the authentication server 50 is installed, the authentication unit 24 and the authentication information storage unit 27 of the cloud server 20 are not used for the tenant. In addition, in a tenant adopting the serverless version, since the workflow is controlled by the device 10, the flow control unit 21 and the flow setting storage unit 26 of the cloud server 20 are not used for the tenant. Further, in the tenant adopting the serverless version, since the setting processing unit 41 of the administrator terminal 40 is used, the setting processing unit 22 of the cloud server 20 is not used for the tenant. Further, the local server 30 is not installed in a tenant that adopts the serverless version.

  Further, FIG. 7 is a diagram illustrating an example of a functional configuration corresponding to the cloud version. In a tenant adopting the cloud version, the authentication server 50 does not need to be installed. Therefore, the authentication unit 24 and the authentication information storage unit 27 of the cloud server 20 are valid for the tenant. In the tenant adopting the cloud version, the workflow is controlled by the device 10 or the cloud server 20. Therefore, the flow control unit 21 and the flow setting storage unit 26 of the cloud server 20 are valid for the tenant. In addition, since the setting processing unit 22 of the cloud server 20 is used in a tenant adopting the cloud version, the setting processing unit 41 and the flow setting storage unit 43 of the administrator terminal 40 are not used for the tenant. Further, the local server 30 is not installed in a tenant that adopts the cloud version.

  Next, an outline of a workflow processing procedure in each of the server version, the serverless version, and the cloud version will be described.

  FIG. 8 is a diagram for explaining an example of an outline of a workflow processing procedure in the server version.

  When the user inputs a user name and password to the device 10 to start using the workflow, the flow control unit 121 requests the authentication unit 51 of the authentication server 50 to authenticate the user name and password (S11). When the device 10 performs a scan in response to an instruction from a user who has succeeded in authentication, the flow control unit 121 transmits a scan image to the flow control unit 31 of the local server 30 to execute the workflow to the flow control unit 31. Request (S12). The flow control unit 31 controls the execution of the workflow based on the flow setting information stored in the flow setting storage unit 34. For example, if it is specified in the flow setting information that image conversion is to be executed by the cloud server 20, the flow control unit 31 sends an image conversion execution request including the scanned image to the image conversion unit 25 of the cloud server 20. (S13). When the image conversion is completed, the flow control unit 31 takes over the data generated by the image conversion and distributes the data to the distribution destination specified in the flow setting information (S14).

  FIG. 9 is a diagram for explaining an example of an outline of a workflow processing procedure in the serverless version. In FIG. 9, the same steps as those in FIG. 8 are denoted by the same step numbers, and the description thereof is omitted.

  When the device 10 performs a scan in response to an instruction from a user who has been successfully authenticated, the flow control unit 121 controls the execution of the workflow based on the flow setting information stored in the flow setting storage unit 122. For example, if it is specified in the flow setting information that the image conversion is to be executed by the cloud server 20, the flow control unit 121 sends an image conversion execution request including the scanned image to the image conversion unit 25 of the cloud server 20. (S22). When the image conversion ends, the flow control unit 121 collects the data generated by the image conversion and distributes the data to the distribution destination specified in the flow setting information (S23).

  FIG. 10 is a diagram for explaining an example of an outline of a workflow processing procedure in the cloud version. 10, the same steps as those in FIG. 9 are denoted by the same step numbers, and the description thereof is omitted. FIG. 10 shows a processing procedure when the distribution destination is a local storage.

  When the user inputs a user name and password to the device 10 to start using the workflow, the flow control unit 121 requests the authentication unit 24 of the cloud server 20 to authenticate the user name and password (S31). The subsequent steps are as described in FIG. However, the distribution destination in step S23 is limited to the local storage.

  FIG. 11 is a diagram for explaining an example of the outline of the second processing procedure of the workflow in the cloud version. In FIG. 11, the same steps as those in FIG. 10 are denoted by the same step numbers, and the description thereof is omitted. FIG. 11 shows a processing procedure when the distribution destination is an external storage.

  When the device 10 executes a scan in response to an instruction from a user who has succeeded in authentication, the flow control unit 121 transmits the scan image to the flow control unit 21 of the cloud server 20 to execute the workflow to the flow control unit 21. A request is made (S42). The flow control unit 21 controls the execution of the workflow based on the flow setting information stored in the flow setting storage unit 26. For example, if execution of image conversion is specified in the flow setting information, the flow control unit 21 requests the image conversion unit 25 to execute the image conversion (S43). When the image conversion ends, the flow control unit 21 takes over the data generated by the image conversion and distributes the data to the distribution destination (external storage) specified in the flow setting information (S44).

  8, 9, and 10, the local storage is, for example, the file server 60 or the FTP server 70. The external storage is, for example, an online storage system 90. In FIG. 8, FIG. 9, and FIG. 10, the dashed arrows indicate steps in which the route can change according to the contents of the flow setting information.

  Next, a construction procedure of a serverless version system configuration among the three system configurations of the server version, the serverless version, and the cloud version will be described.

  In order to construct a system configuration of the serverless version, first, a program corresponding to the surless version is installed in the user environment E1. The serverless version is installed by using the administrator terminal 40. It is assumed that an installation package has been downloaded to the administrator terminal 40 in advance. When the installer of the installation package is activated, an installation screen as shown in FIG. 12 is displayed.

  FIG. 12 is a diagram illustrating a display example of the installation screen. 12 includes buttons 511 to 513 and the like. A button 511 is a button for receiving a server version installation instruction. When the button 511 is selected, the flow control unit 31, the setting processing unit 32, and the cloud cooperation unit 33 are installed in the local server 30. In addition, the flow control unit 121 is installed in the device 10.

  A button 513 is a button for receiving a cloud version installation instruction. When the button 513 is selected, the cloud cooperation unit 42 is installed in the administrator terminal 40. In addition, the flow control unit 121 is installed in the device 10.

  The button 512 is a button for accepting a serverless version installation instruction. When the button 512 is selected, the processing shown in FIG. 13 is executed, and the setting processing unit 41 and the cloud cooperation unit 42 are installed in the administrator terminal 40. In addition, the flow control unit 121 is installed in the device 10.

  FIG. 13 is a sequence diagram for explaining an example of the processing procedure of the serverless version system configuration construction processing.

  When the user selects the button 512 on the installation screen 510 and inputs a serverless version installation start instruction (S101), the installer of the administrator terminal 40 functions as the setting processing unit 41. The program to be installed is installed in the administrator terminal 40 (S102). Subsequently, for example, the setting processing unit 41 generates a storage area (for example, a database) as the flow setting storage unit 43 in the auxiliary storage device of the administrator terminal 40 (S103).

  Subsequently, the installer installs a program that causes the administrator terminal 40 to function as the cloud cooperation unit 42 in the administrator terminal 40 (S104). Subsequently, the cloud cooperation unit 42 generates a storage area (for example, a database) as the cloud cooperation information storage unit 44 in the auxiliary storage device of the administrator terminal 40 (S105).

  Further, the installer installs a program that causes the device 10 to function as the flow control unit 121 in the device 10 (S106). For example, the flow control unit 121 generates a storage area as the flow setting storage unit 122 in the HDD 114 (S107).

  This completes the installation. Subsequently, processing for enabling cooperation with the cloud server 20 is executed.

  In response to a user operation, the setting processing unit 41 displays a menu screen for accepting various setting instructions. FIG. 14 is a diagram illustrating a display example of a menu screen. In FIG. 14, the menu screen 520 includes buttons 521 to 524 and the like. The button 521 is a button for accepting a setting request for cloud cooperation information. The button 522 is a button for accepting a profile setting request. A profile is a collection of projects. A project is flow setting information related to one workflow. Therefore, it can be said that a profile is a set of flow setting information related to one or more workflows.

  The button 523 is a button for accepting a setting request regarding the device 10. The button 524 is a button for accepting a setting request regarding the user.

  When the button 521 is selected, the setting processing unit 41 displays a cloud cooperation setting screen. FIG. 15 is a diagram illustrating a display example of the cloud cooperation setting screen. 15, the cloud cooperation setting screen 530 includes a radio button 531, an account information input area 532, a service ID input area 533, an apply button 534, and the like.

  The radio button 531 is a radio button for selecting whether to use the cloud service (cloud server 20). When the radio button 531 is selected to use the cloud service, the account information input area 532 and the service ID input area 533 can be input. When the radio button 531 is selected not to use the cloud service, the account information input area 532 and the service ID input area 533 cannot be input. Therefore, in this case, input to the cloud cooperation setting screen 530 is not necessary. In the case of the cloud version, the radio button 531 may not be displayed. This is because the cloud version requires the use of the cloud server 20.

  The account information input area 532 is an area for accepting input of account information for accessing the cloud server 20. The account information includes a tenant ID, an administrator ID, an administrator password, and the like. The tenant ID is identification information for each tenant, and is notified in advance from the operator of the cloud server 20 to the tenant. The administrator ID is identification information of the administrator and may be unique within the tenant. The administrator password is an administrator password. As the administrator ID and the administrator password, arbitrary values are input via the cloud cooperation setting screen 530.

  The service ID input area 533 is an area for receiving an input of a service ID. The service ID is identification information of a service used by the tenant (user environment E1) among services provided by the cloud server 20. The service ID is issued to the tenant in, for example, a prior service use contract between the tenant and the operator of the cloud server 20. The service ID may have a role as a license key. That is, the service ID may be information for certifying that the user is a valid service contractor (legal tenant).

  When the radio button 531 is selected to use the cloud service, when the account information and the service ID are input and the apply button 534 is pressed (S111 in FIG. 13), the cloud cooperation unit 42 performs the cloud cooperation. An activation request including information input on the setting screen 530 is transmitted to the cloud server 20 (S112). The activation request corresponds to a service use start request related to the service ID. Then, the cloud cooperation part 42 memorize | stores the information input into the cloud cooperation setting screen 530 in the cloud cooperation information storage part 44 (S113). However, among the information input on the cloud cooperation setting screen 530, only the tenant ID may be stored in the cloud cooperation information storage unit 44.

  When receiving the activation request, the cloud cooperation unit 23 of the cloud server 20 stores the account information and the service ID in association with each other in, for example, the authentication information storage unit 27. Note that the tenant ID of the account information included in the activation request and the service ID included in the activation request are information issued in advance. Therefore, the validity of the activation request may be verified based on whether or not the association between the tenant ID and the service ID is registered in the cloud server 20.

  Subsequently, when the button 522 is selected on the menu screen 520 (FIG. 14), the setting processing unit 41 displays a profile editing screen.

  FIG. 16 is a diagram illustrating a display example of the profile editing screen. A profile editing screen 540 shown in FIG. 16 includes a tree area 541, a project editing area 542, and the like.

  In the tree area 541, a tree component in which a profile is assigned to each node below the root node is displayed.

  For example, when a right click is performed at the root node in the tree area 541, the setting processing unit 41 displays a context menu including a menu item “add profile”. When the “add profile” menu item is selected, the setting processing unit 41 displays a profile setting screen.

  FIG. 17 is a diagram illustrating a display example of the profile setting screen. In FIG. 17, the profile setting screen 550 includes a profile name input area 551, a radio button 552, a project layout input area 553, and the like.

  A profile name input area 551 is an area for receiving an input of a profile name. The profile name is identification information for each profile. A radio button 552 transmits data such as a scanned image (image data) to a communication destination outside the user environment E1, such as the cloud server 20 or the online storage system 90, for any project (workflow) belonging to the profile ( Hereinafter, it is a radio button for selecting whether to permit “cloud communication”). The radio button 552 may be able to select “permitted” when the use of the cloud service is selected in the radio button 531 of the cloud cooperation setting screen 530.

  The project layout input area 553 is an icon for each project on a screen (hereinafter referred to as a “project list screen”) for selecting a project to be executed from projects belonging to the profile displayed on the device 10. This is an area for receiving input of layout information. For example, “4 × 2” indicates that four icons can be arranged in the horizontal direction and two icons can be arranged in the vertical direction.

  When the value of each item is input and the OK button 554 is pressed, the setting processing unit 41 adds a new node related to the profile name to the tree area 541. The setting processing unit 41 stores the information input on the profile setting screen 550 in association with the node, for example, in the memory device of the administrator terminal 40.

  In the profile edit screen 540 of FIG. 16, the project edit area 542 includes a project list area 543, a new project button 544, an edit button 545a, a copy button 545b, a delete button 545c, an OK button 546, and the like.

  In the project list area 543, information on projects is displayed in a list format for each project belonging to the profile selected in the tree area 541. That is, one line in the project list area 543 corresponds to one project. When “▼” or “▲” in the “change order” column of the project list area 543 is operated, the setting processing unit 41 changes the order of the rows. Specifically, when “▼” is selected, the setting processing unit 41 swaps the line where “▼” is selected with the line below the line. When “▲” is selected, the setting processing unit 41 swaps the line on which “▲” is selected with the line above the line. The line order corresponds to the display order of the icons corresponding to the project.

  When the new project button 544 is pressed, the setting processing unit 41 adds a new line to the project list area 543. When the copy button 545b is pressed, a copy of the line selected in the project list area 543 is added after the line or at the end of the project list area 543. When the delete button 545c is pressed, the setting processing unit 41 deletes the row (that is, the project) selected in the project list area 543.

  When the edit button 545a is pressed, the setting processing unit 41 displays a project setting screen for setting each parameter related to the project relating to the row selected in the project list area 543.

  FIG. 18 is a diagram illustrating a display example of the project setting screen. 18 includes a project name input area 561, an icon name input area 562, a radio button 563, an image conversion list area 564, a distribution method list area 565, a flow edit area 566, an OK button 567, and the like. Including.

  The project name input area 561 is an area for receiving an input of a project name. The project name is identification information for each project (each workflow). The icon name input area 562 is an area for receiving an input of a file name of a file storing an icon for expressing the project on the project list screen.

  The radio button 563 is a radio button for selecting whether to permit cloud communication for the project (workflow). When the radio button 563 is set to permit cloud communication regarding the profile to which the project belongs, selection of “permitted” may be possible.

  The image conversion list area 564 is an area in which a display component is displayed for each image conversion that can be selected as a processing unit constituting the workflow. The distribution method list area 565 is an area in which a display component is displayed for each distribution method that can be selected as a processing unit constituting the workflow.

  The flow editing area 566 is an area for accepting the setting of the context of processing units constituting the workflow. For example, by dragging and dropping the display component in the image conversion list area 564 or the distribution method list area 565 to the flow editing area 566, a workflow including the image conversion or distribution method related to the display component is created. . For example, when the image conversion or distribution method rectangle dropped in the flow editing area 566 is clicked, the setting processing unit 41 displays a setting screen for accepting input of setting information regarding the image conversion or distribution method. To do. For example, in the case of image conversion, parameters relating to image conversion can be set on the setting screen. With the distribution method, it is possible to set the address information of the distribution destination on the setting screen.

  In addition, in the flow editing area 566, when “◯” indicating the starting point of the workflow is clicked, the setting processing unit 41 receives a setting information (initial value of the reading condition) related to scanning in the device 10. Is displayed.

  If the cloud communication is not permitted for the profile to which the project belongs, the setting processing unit 41 performs image conversion or online processing executed in the cloud server 20 in the image conversion list area 564 and the distribution method list area 565. A display component corresponding to a distribution method in which an external storage such as the storage system 90 is a distribution destination may be disabled. The inoperable state may be realized by non-display of display parts, grayout, or the like.

  When cloud communication is permitted for the profile to which the project belongs, the setting processing unit 41 executes the same processing when “prohibited” of cloud communication is selected with the radio button 563. May be. At this time, if the image conversion executed in the cloud server 20 or the distribution method or the like where the external storage such as the online storage system 90 is the distribution destination is already a component of the workflow in the flow editing area 566 The setting processing unit 41 may display a screen (dialog) for inquiring the user whether to discard the current editing state of the workflow in the flow editing area 566. When discarding is selected, the setting processing unit 41 returns the contents of the flow editing area 566 to an initial state (a state in which no image conversion and distribution method is arranged). When it is selected not to discard, the setting processing unit 41 may return the radio button 563 to a state where “permitted” is selected.

  Whether each image conversion is executed in the cloud server 20 is determined based on information indicating whether the image conversion is executed in the cloud server 20 associated with each image conversion. It's fine. Similarly, if each distribution method determines whether or not the external storage is a distribution destination, the determination is made based on information associated with each distribution method and indicating whether or not the external storage is a distribution destination. Good. In FIG. 18, it is assumed that “cloud image conversion” is image conversion executed in the cloud server 20 and “external storage distribution” is a distribution method in which the external storage is a distribution destination.

  When a value of each item is input on the project setting screen 560 and an OK button 567 is pressed, the setting processing unit 41 reflects the set value on the line selected in the project list area 543.

  When the OK button 546 on the profile editing screen 540 is pressed (S121 in FIG. 13), the setting processing unit 41 stores the flow setting information set via the profile editing screen 540 or the like in the flow setting storage unit 43. (S122). Of the set information, information set via the profile setting screen 550 is stored in a profile table that configures the flow setting storage unit 43.

  FIG. 19 is a diagram illustrating a configuration example of a profile table. In FIG. 19, the profile table stores the profile name, project layout, and cloud communication permission / prohibition for each profile.

  Information set via the project setting screen 560 is stored in a project table that configures the flow setting storage unit 43.

  FIG. 20 is a diagram illustrating a configuration example of a project table. The project table stores, for each project, a profile name, a project name, an icon name, a distribution method, a distribution destination, an image conversion, a reading condition initial value, permission / inhibition of cloud communication, and the like. The profile name is the profile name of the profile to which the project belongs. The delivery destination is delivery destination identification information set for each delivery method. That is, the delivery destination set for the delivery method included in the flow editing area 566 of the project setting screen 560 is stored in the project table in association with the delivery method.

  In FIG. 20, two distribution methods and distribution destinations are registered in the first project. This is because a workflow that branches the delivery method into two after image conversion is set.

  Subsequently, when the button 523 is selected on the menu screen 520 (FIG. 14), the setting processing unit 41 displays a device setting screen.

  FIG. 21 is a diagram illustrating a display example of the device setting screen. 21 includes a machine number input area 571, an IP address input area 572, a profile selection area 573, a remark input area 574, a radio button 575, an OK button 576, and the like.

  The machine number input area 571 is an area for receiving an input of a machine number of the device 10 that is a candidate for a scan image input to the workflow. In the present embodiment, the machine number is an example of identification information for each machine of the device 10. The IP address input area 572 is an area for accepting input of the IP address of the device 10.

  The profile selection area 573 is an area for selecting a profile name of a profile to be assigned (associated) to the device 10 from the profile names registered in the profile table (FIG. 19). In the present embodiment, each device 10 is associated with one profile.

  The remarks input area 574 is an area for receiving input of remarks related to the device 10. For example, the installation location of the device 10 may be input as a remark.

  The radio button 575 is a radio button for selecting whether to permit cloud communication for the device 10. The radio button 575 may be able to select “permitted” when the use of the cloud service is selected in the radio button 531 of the cloud cooperation setting screen 530.

  When the value of each item is input on the device setting screen 570 and the OK button 576 is pressed (S131 in FIG. 13), the setting processing unit 41 flows the device information input via the device setting screen 570 as a flow. It memorize | stores in the apparatus information table of the setting memory | storage part 43 (S132).

  FIG. 22 is a diagram illustrating a configuration example of the device information table. The device information table shown in FIG. 22 stores, for each device 10, the machine number, IP address, remarks, assignment profile name, cloud communication permission / denial, and the like.

  For each device 10 that is a scan image input candidate for the workflow, the device information of the device 10 needs to be registered in the device information table.

  Subsequently, when the button 524 is selected on the menu screen 520 (FIG. 14), the setting processing unit 41 displays a user setting screen.

  FIG. 23 is a diagram illustrating a display example of the user setting screen. A user setting screen 580 shown in FIG. 23 includes a user name input area 581, an organization name input area 582, radio buttons 583, an OK button 584, and the like.

  The user name input area 581 is an area for accepting input of a user name. The organization name input area 582 is an area for receiving the input of the organization name of the organization (department or the like) to which the user related to the user name belongs. The radio button 583 is a radio button for selecting whether to allow cloud communication for the user. The radio button 583 may allow “permitted” to be selected when the use of the cloud service is selected in the radio button 531 of the cloud cooperation setting screen 530.

  When the value of each item is input on the user setting screen 580 and the OK button 584 is pressed (S141 in FIG. 13), the setting processing unit 41 sets the user information input via the user setting screen 580 as the flow setting. It memorize | stores in the user information table of the memory | storage part 43 (S142).

  FIG. 24 is a diagram illustrating a configuration example of a user information table. The user information shown in FIG. 24 stores, for each user, a user name, an organization name, permission for cloud communication, and the like. In the present embodiment, cloud communication is permitted for the user taro, and cloud communication is prohibited for the user yoko.

  The processing for constructing the serverless system configuration is thus completed. In the serverless version, the setting information stored in the flow setting storage unit 43 of the administrator terminal 40 is copied (synchronized) to the flow setting storage unit 122 of the device 10 at a predetermined timing.

  In the case of the server version, setting information stored in the flow setting storage unit 43 of the administrator terminal 40 at a predetermined timing in the flow setting storage unit 122 of the device 10 and the flow setting storage unit 34 of the local server 30. Is copied (synchronized).

  In the case of the cloud version, the flow setting information, device information, and user information are stored in the flow setting storage unit 26 of the cloud server 20 when each information is set. Thereafter, the setting information stored in the flow setting storage unit 26 is copied (synchronized) to the flow setting storage unit 122 of the device 10 at a predetermined timing.

  For example, FIG. 25 is a sequence diagram for explaining an example of a processing procedure of setting information synchronization processing in the serverless version. In FIG. 25, the administrator operates the administrator terminal 40.

  For example, when the administrator instructs the setting processing unit 41 of the administrator terminal 40 to synchronize setting information (S201), the setting processing unit 41 receives a profile (flow setting information), a device from the flow setting storage unit 43. Information and user information are acquired (S202). Subsequently, the setting processing unit 41 distributes the acquired setting information to each device 10 registered in the device information (S203). At this time, as for the information stored in the profile table and the problem table, the profile assigned to each device 10 and the information of the project belonging to the profile may be distributed. Each piece of device information may be distributed to the device 10 corresponding to each piece of device information.

  When receiving the setting information, the flow control unit 121 of each device 10 stores the setting information in the flow setting storage unit 122 (S204).

  Note that the cloud cooperation information stored in the administrator terminal 40 may be stored in the device 10 in accordance with the processing of FIG. For example, the cloud cooperation information may be acquired from the cloud cooperation information storage unit 44 in S202, the setting information including the cloud cooperation information may be distributed in S203, and the setting information including the cloud cooperation information may be stored in S204. As a result, the cloud cooperation information is stored in the profile setting storage unit 122 of the device 10. In this case, the device 10 acquires cloud cooperation information from the probe setting storage unit 122 when performing cloud communication. The device 10 may have a cloud cooperation information storage unit in order to hold cloud cooperation information. In this case, the cloud cooperation information distributed from the administrator terminal 40 may be stored in the cloud cooperation information storage unit of the device 10.

  Note that the processing of FIG. 25 may be automatically started instead of in response to an instruction from the administrator.

  Next, a processing procedure when executing a workflow will be described. In the following, each of the user yoko (hereinafter simply referred to as “yoko”) and the user taro (hereinafter simply referred to as “taro”) in which user information as shown in FIG. A case where the user is an operator will be described. The difference between yoko and taro is that cloud communication is prohibited in yoko, and cloud communication is allowed in taro. It is assumed that the system configuration is a serverless version.

  FIG. 26 is a sequence diagram for explaining an example of a processing procedure of a workflow execution process when the login user is yoko. In FIG. 26, it is assumed that the device 10 operated by yoko (hereinafter referred to as “target device 10”) is the device 10 whose machine number is “1A23-45678”. Therefore, the profile assigned to the target device 10 is a profile whose profile name is “development” (hereinafter referred to as “target profile”), as shown in FIG. As illustrated in FIG. 22, the target device 10 is permitted to perform cloud communication. Further, as shown in FIG. 19, cloud communication is permitted for the target profile.

  When yoko inputs a login request to the device 10 (S301), the flow control unit 121 of the target device 10 authenticates an authentication request for authentication information (user name, password, etc.) input with the login request. It transmits to the server 50 (S302). If authentication information matching the authentication information specified in the authentication request is stored in the authentication information storage unit 52 (S303, S304), the authentication unit 51 of the authentication server 50 sends a response indicating a successful authentication to the flow. It returns to the control part 121 (S305). If the authentication is successful, the processes after step S306 are executed.

  In step S306, the flow control unit 121 acquires setting information stored in the flow setting storage unit 122. Subsequently, the flow control unit 121 generates a project list screen based on each record including the profile name of the target profile among the records stored in the project table (S307). Specifically, a project list screen in which icons relating to the icon names of the records are arranged is generated.

  Subsequently, the flow control unit 121 sets the “cloud communication permission / inhibition” value for the target profile in the profile table (FIG. 19), the “cloud communication permission / inhibition” value for the target device in the device information table (FIG. 22), and the user information table ( Based on the value of “cloud communication permission / inhibition” for the logged-in user in FIG. 24) and the value of “cloud communication permission / inhibition” in the project table (FIG. 20) for each project in which an icon is arranged on the project list screen. Thus, any icon on the project list screen is rendered inoperable (selection is restricted) (S308).

  First, based on the “distribution method” in the project table (FIG. 20), a project (hereinafter referred to as “cloud transmission required project”) in which data is necessarily distributed outside the user environment E1 is specified. In the present embodiment, “external storage distribution” is a distribution method for distributing to the online storage system 90. Therefore, a project whose “distribution method” value in the project table (FIG. 20) is only “external storage distribution” is identified as a cloud transmission-required project. Of the projects specified as cloud transmission indispensable projects, an icon corresponding to a project whose “cloud communication permission / prohibition” value in the project table (FIG. 20) is “prohibited” is rendered inoperable.

  Further, among the projects specified as cloud transmission indispensable projects, even if the value of “cloud communication permission / rejection” in the project table (FIG. 20) is “permitted”, the value of “cloud communication permission / rejection” for the target profile, the target device If any of the “cloud communication permission / rejection” value for the login user and the “cloud communication permission / rejection” value for the login user is “prohibited”, the icons corresponding to all the specified projects are disabled.

  In the project shown in FIG. 20, the value of the “distribution method” of a project whose project name is “analysis” (hereinafter referred to as “analysis project”, and the names of other projects follow the same naming convention) is , “External storage distribution” only. Therefore, the analysis project is identified as a cloud transmission required project. For the presentation project, the value of “distribution method” includes “external storage distribution”, but also includes “FTP server”, which is a distribution method that uses local storage as the distribution destination. Not applicable to projects.

  Here, the value of “cloud communication permission / denial” in the analysis project is “permitted”, but as shown in FIG. 24, cloud communication is prohibited for yoko. Therefore, the icon corresponding to the analysis project cannot be operated.

  Subsequently, the flow control unit 121 displays a project list screen on the operation panel 15 of the target device 10 (S309).

  FIG. 27 is a diagram showing a display example of the project list screen. A project list screen 610 shown in FIG. 27 includes icons 611 to 613 and the like. The icon 611 is an icon corresponding to the presentation project. The icon 612 is an icon corresponding to the analysis project. The icon 613 is an icon corresponding to the design project 613. As described above, the icon 612 corresponding to the analysis project is disabled. In FIG. 27, the icon 612 is grayed out and cannot be operated, but the icon 612 may be hidden.

  When the icon 611 or 613 is selected, a project setting change screen corresponding to the selected icon is displayed.

  FIG. 28 is a diagram illustrating a display example of the setting change screen. In FIG. 28, a setting change screen 620 is a screen for accepting change instructions such as a delivery method and a reading condition of the selected project. The setting change screen 620 includes a distribution method setting area 621, a file name input area 622, a reading condition button 623, and the like.

  The distribution method setting area 621 is an area for accepting a setting change of a distribution method and a distribution destination, and an operation area is arranged for each distribution method set in the selected project. FIG. 28 shows an example in which a presentation project is selected. As shown in FIG. 20, FTP distribution and external storage distribution are set as distribution methods in the presentation project. Therefore, operation areas corresponding to these two distribution methods are provided. However, the operation area corresponding to the external storage distribution cannot be operated. This is because the value of “cloud communication permission / inhibition” for yoko is “prohibited”. That is, the flow control unit 121 disables the operation area for the external storage distribution if the value of “cloud communication permission / prohibition” for the login user is “prohibited”. It should be noted that such an operation restriction regarding the distribution method may be grasped as a restriction on the selection of the project icon. That is, restrictions such as editing on a part of information regarding the project may be grasped as restrictions on selection of the project itself.

  Note that even if the value of “cloud communication permission / inhibition” for yoko is “permitted”, if the value of “cloud communication permission / inhibition” for the target profile or target device is “prohibited”, the flow control unit 121 uses the external storage The operation area corresponding to the distribution is disabled.

  For example, when the detail button 6211 is pressed, the flow control unit 121 causes the operation panel 15 to display a screen for setting a distribution method and a distribution destination.

  The file name input area 622 is an area for receiving an input of a scan image file name.

  The reading condition button 623 is a button for accepting a reading condition setting instruction. That is, when the reading condition button 623 is pressed, the flow control unit 121 causes the operation panel 15 to display a screen for setting reading conditions (hereinafter referred to as “reading condition setting screen”).

  FIG. 29 is a diagram illustrating a display example of the reading condition setting screen. On the reading condition setting screen 630, the value of each item constituting the reading condition can be set. The initial state of the reading condition setting screen 630 follows the initial reading condition value for the project selected on the project list screen 610.

  Note that the reading condition setting screen 630 includes a tab 632. A tab 632 is a tab for a tab window for accepting input of setting information related to cloud image conversion. Since the cloud communication is prohibited for yoko, the flow control unit 121 makes the tab 632 inoperable.

  When the values of some or all items are changed on the reading condition setting screen 630 and the OK button 631 is pressed, the display target screen changes to the setting change screen 620. When the return button 624 is pressed on the setting change screen 620, the display target screen changes to the project list screen 610.

  For example, when a scan execution instruction is input in a state where a presentation project is selected on the project list screen 610 (S311), the flow control unit 121 scans (reads) a document to the scanner 12 of the target device 10. Is executed. Subsequently, the flow control unit 121 recognizes that the image conversion cannot be performed based on the fact that the “image conversion” of the presentation project is “cloud image conversion” and that cloud communication is prohibited for yoko. To do. This is because “cloud image conversion” causes the cloud server 20 to perform image conversion, and cloud communication is prohibited for yoko. Therefore, the flow control unit 121 transmits the scanned image to the FTP server 70 by FTP based on the fact that the “distribution method” of the presentation project is “FTP distribution” and the “distribution destination” is the FTP server 70. (S312). That is, the scan image is distributed without performing image conversion on the scan image. In the presentation project, external storage distribution is also included as a distribution method, but since cloud communication is prohibited in yoko, the flow control unit 121 does not execute external storage distribution.

  A project whose value of “image conversion” is only “cloud image conversion” may also be a cloud transmission required project. In this case, regarding yoko, the presentation project cannot be selected on the project list screen 610.

  On the other hand, when a scan execution instruction is input while a design project is selected on the project list screen 610 (S321), the flow control unit 121 causes the target device 10 to scan a document. Subsequently, the flow control unit 121 converts the scanned image into PDF data based on the “image conversion” of the presentation project being “PDF conversion” (S322). Subsequently, based on the fact that the “distribution method” of the design project is “folder distribution” and the “distribution destination” is the file server 60, the flow control unit 121 converts the PDF data into a predetermined file server 60. It transmits to the folder (S323).

  Next, the case of taro will be described. FIG. 30 is a sequence diagram for explaining an example of a processing procedure of workflow execution processing when the logged-in user is taro. In FIG. 30, the same steps as those in FIG. 26 are denoted by the same step numbers. In FIG. 30, the target device 10 and the target profile are the same as those in FIG.

  Steps S301 to S307 are the same as described in FIG. 26 except that the login user is taro.

  In step S308, the logic of the processing executed by the flow control unit 121 is the same as that in FIG. 26, but the processing result is different from that in FIG. First, the project specified as the cloud transmission indispensable project is an analysis project as in FIG. However, as shown in FIG. 24, the value of “cloud communication permission / denial” for taro is “permitted”. The value of “cloud communication permission / denial” for each of the target device and the target profile is also “permitted”. Therefore, in FIG. 30, the project list screen 610 is displayed in a state where the icon 612 corresponding to the analysis project is also operable (S309).

  For example, when a scan execution instruction is input in a state where a presentation project is selected on the project list screen 610 (S311), the flow control unit 121 causes the scanner 12 of the target device 10 to scan a document. . Subsequently, based on the fact that the “image conversion” of the presentation project is “cloud image conversion (text)”, the flow control unit 121 sends an execution request for conversion to text data to the image conversion unit 25 of the cloud server 20. Transmit (S412). The execution request includes a scanned image.

  The image conversion unit 25 performs the requested image conversion on the scanned image. Here, an OCR process is executed to convert the scanned image into a text format. The image conversion unit 25 returns the text data generated by the image conversion to the flow control unit 121 (S413). Subsequently, based on the fact that one of the “distribution methods” of the presentation project is “FTP distribution” and the “distribution destination” is “FTP server”, the flow control unit 121 converts the text data to FTP by FTP. It transmits to the server 70 (S414). Further, the flow control unit 121 changes the text data to “GDriv” based on the fact that one of the “distribution methods” of the presentation project is “external storage distribution” and the “distribution destination” is “GDdrive”. The data is transmitted to the corresponding online storage system 90 (S415).

  In addition, when a scan execution instruction is input in the state where the analysis project is selected on the project list screen 610 (S421), the flow control unit 121 causes the scanner 12 of the target device 10 to scan the document. . Subsequently, the flow control unit 121 recognizes that it is not necessary to perform image conversion based on the fact that the “image conversion” value of the analysis project is empty. Therefore, the flow control unit 121 converts the scanned image into an online corresponding to “SPOnline” based on the “delivery method” of the analysis project being “external storage delivery” and the “delivery destination” being “SPOnline”. The data is transmitted to the storage system 90 (S422).

  Note that the process executed when a design project is selected on the project list screen 610 is the same as in the case of yoko (S321 to S323).

  As described above, according to the present embodiment, permission / inhibition of cloud communication can be set for each user, for each device 10, for each profile, and for each project. Based on such a setting, the project list screen 610 is displayed in a state where selection is limited for a project including a processing unit for performing cloud communication. Therefore, it is possible to limit the predetermined communication by the device 10.

  In the present embodiment, special distinction may not be made between the data obtained by performing image processing on the scanned image and the scanned image (image data).

  In addition, permission / inhibition of cloud communication may be determined based on a combination of settings for permission / inhibition of cloud communication (limitation of cloud communication) set in units of profiles, projects, devices 10, and users. For example, in the case of “user: permission”, “device: prohibition”, and “project: permission”, the selection of the project may not be restricted. For example, for each combination, whether or not the selection of the project is restricted may be set separately.

  In the present embodiment, the scanner 12 is an example of a reading unit. The flow control unit 121 is an example of a control unit. The cloud server 20 is an example of an information processing device. The setting information regarding permission / inhibition of cloud communication is an example of restriction information.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

DESCRIPTION OF SYMBOLS 1 Information processing system 10 Apparatus 11 Controller 12 Scanner 13 Printer 14 Modem 15 Operation panel 16 Network interface 17 SD card slot 20 Cloud server 21 Flow control part 22 Setting process part 23 Cloud cooperation part 24 Authentication part 25 Image conversion part 26 Flow setting memory | storage Unit 27 authentication information storage unit 30 local server 31 flow control unit 32 setting processing unit 33 cloud cooperation unit 34 flow setting storage unit 35 cloud cooperation information storage unit 40 administrator terminal 41 setting processing unit 42 cloud cooperation unit 43 flow setting storage unit 44 Cloud cooperation information storage unit 50 Authentication server 51 Authentication unit 52 Authentication information storage unit 60 File server 70 FTP server 80 SD card 90 Online storage system 111 CPU
112 RAM
113 ROM
114 HDD
115 NVRAM
121 Flow Control Unit 122 Flow Setting Storage Unit 200 Drive Device 201 Recording Medium 202 Auxiliary Storage Device 203 Memory Device 204 CPU
205 Interface device B Bus E1 User environment

JP, 2014-042130, A

Claims (10)

Equipment,
A reading unit for reading image data from a document;
A processing flow including one or more processing units related to image data read by the reading unit, the first screen including a list of a plurality of the processing flows is displayed, and selected from the list of the processing flows A control unit that controls execution of the processing flow,
The control unit is associated with the identification information of the operator of the device, and when the restriction information indicating that data transmission of the image data to a predetermined communication destination is restricted is stored, the data Displaying the first screen in a state where selection of a processing flow including a processing unit for transmission is limited;
Equipment characterized by that. When the restriction information is stored in association with the identification information of the device, the control unit is configured in a state where selection of a processing flow including a processing unit for performing the data transmission is restricted. Display the screen,
The device according to claim 1. A set of one or more processing flows is associated with each device,
When the restriction information is stored in association with the set of processing flows associated with the device, the control unit restricts selection of a processing flow including a processing unit for performing the data transmission. In the state, the first screen is displayed.
The apparatus according to claim 1 or 2, characterized by the above. The processing flow includes a processing flow that is associated with the processing flow and stores the restriction information.
The control unit displays the first screen in a state where selection of a processing flow in which the restriction information is stored is restricted;
The device according to claim 1, wherein the device is a device. The control unit associates the restriction information stored in association with the identification information of the operator, and further associates with one or more pieces of information among the identification information of the device, a set of processing flows, and the processing flow. 5. The device according to claim 1, wherein the first screen is displayed in a state where selection of a processing flow is restricted based on the restriction information stored and stored. . The control unit displays a second screen including a list of processing contents used to select processing contents to be executed in the processing unit included in the processing flow, and is selected from the processing contents list Control processing content to be executed in the processing unit,
2. The device according to claim 1, wherein, when the restriction information is stored, the second screen is displayed in a state where selection of processing contents for performing the data transmission is restricted. The control unit displays a third screen including a list of execution conditions used for selecting an execution condition of a process executed in the processing unit, and the execution condition selected from the list of execution conditions is Control to apply to processing executed in the processing unit,
3. The device according to claim 1, wherein, when the restriction information is stored, the third screen is displayed in a state where selection of an execution condition related to the data transmission is restricted. 4. An information processing system including an apparatus and an information processing apparatus connected to each other via a network,
The equipment is
A reading unit for reading image data from a document;
A processing flow including one or more processing units related to image data read by the reading unit, the first screen including a list of a plurality of the processing flows is displayed, and selected from the list of the processing flows A control unit that controls execution of the processing flow,
The control unit is associated with the identification information of the operator of the device, and when the restriction information indicating that data transmission of the image data to a predetermined communication destination is restricted is stored, the data Displaying the first screen in a state where selection of a processing flow including a processing unit for transmission is limited;
An information processing system characterized by this. Equipment
A reading procedure for reading image data from a document;
A processing flow including one or more processing units related to image data read in the reading procedure, wherein a first screen including a list of a plurality of processing flows is displayed, and selected from the list of processing flows Execute a control procedure for controlling the execution of the processing flow,
The control procedure is associated with identification information of an operator of the device, and when the restriction information indicating that data transmission of the image data to a predetermined communication destination is restricted is stored, the data Displaying the first screen in a state where selection of a processing flow including a processing unit for transmission is limited;
An information processing method characterized by the above. On the equipment,
A reading procedure for reading image data from a document;
A processing flow including one or more processing units related to image data read in the reading procedure, wherein a first screen including a list of a plurality of processing flows is displayed, and selected from the list of processing flows Execute a control procedure for controlling the execution of the processing flow,
The control procedure is associated with identification information of an operator of the device, and when the restriction information indicating that data transmission of the image data to a predetermined communication destination is restricted is stored, the data Displaying the first screen in a state where selection of a processing flow including a processing unit for transmission is limited;
A program characterized by that.

Images