JP2020013277A - Information processing apparatus, icon generation method, and program - Google Patents

Abstract

To generate an icon that is different from an icon for a similar workflow when generating an icon for a new workflow.SOLUTION: An information processing apparatus is configured to generate an icon using a plurality of task images corresponding to a plurality of tasks included in a workflow. The information processing apparatus generates, if there is a similar workflow similar to the new workflow, an icon corresponding to the new workflow using a task image different from at least one of the plurality of task images used for generating the icon corresponding to the similar workflow.SELECTED DRAWING: Figure 5

Description

  The present invention relates to a technique for generating an icon used to execute a workflow.

  A workflow system capable of executing a plurality of processing steps (tasks) as one job has been proposed. In a workflow system, a button for starting the execution of a workflow is generally displayed on a screen of a personal computer (PC) or a multifunction printer (MFP).

  In Patent Literature 1, when an operation of the same processing content is repeatedly performed, an icon for designating the processing content is generated and displayed, and when the user presses the icon, the corresponding process is executed. Is described.

JP 2018-32248 A

  However, Patent Document 1 does not disclose generating a new icon in consideration of an existing icon. For this reason, if the MFP or the like generates an icon of a workflow whose processing content is similar to that of an existing icon by applying the technology of Patent Document 1, there is a possibility that an icon having the same appearance as the existing icon may be generated. is there. In such a case, the user cannot distinguish the processing content corresponding to each icon.

  An information processing apparatus according to the present invention is an information processing apparatus that generates an icon corresponding to a workflow by using a plurality of task images corresponding to a plurality of tasks included in the workflow, and obtains a new workflow. Means, if there is a similar workflow similar to the new workflow, using a task image different from at least one of the plurality of task images used to generate the icon corresponding to the similar workflow, Generating means for generating an icon corresponding to the new workflow.

  According to the present invention, when an icon for a new workflow is generated, an icon different from an icon for a similar workflow can be generated.

FIG. 11 illustrates an existing UI that displays an icon of a workflow execution button. FIG. 2 is a diagram illustrating a system configuration that implements an execution device. FIG. 3 is a diagram illustrating a hardware configuration of an execution device. FIG. 3 is a diagram illustrating a software configuration of an execution device and a management server. FIG. 3 is a diagram illustrating a functional configuration of a workflow execution button generation unit. It is a flowchart which shows the process which produces | generates a button icon. FIG. 14 is a diagram illustrating a UI for displaying an icon of a new workflow execution button. It is a flowchart which shows the process which produces | generates a button icon. It is a figure showing UI of a button icon using a reduced image. FIG. 3 is a diagram illustrating a functional configuration of a workflow execution button generation unit. It is a flowchart which shows the process which produces | generates a button icon. FIG. 9 is a diagram illustrating a UI of a button icon for displaying attribute information. FIG. 3 is a diagram illustrating a functional configuration of a workflow execution button generation unit. It is a flowchart which shows the process which changes a button icon manually. FIG. 9 is a diagram illustrating a UI for manually changing a button icon.

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. The embodiments do not limit the present invention, and all configurations described in the embodiments are not necessarily indispensable means for solving the problems of the present invention.

[Definition of terms]
Hereinafter, terms used in the present specification will be described before describing the embodiments. “Workflow” refers to a job that sequentially processes a plurality of tasks. A “task” refers to a single job that can be independently processed by a user.

  For example, jobs such as document approval, document file name change, document file transmission by e-mail, document reading, transfer, or printing correspond to the task. Therefore, as an example of the workflow, there is a workflow in which processing is performed in the order of document reading, transfer, and printing. Hereinafter, when an example of a workflow is shown, “document reading → transfer → printing” is described in succession in the order of task processing. A configuration in which the tasks are processed in order is called a “task configuration”.

  The tasks have “setting items” for setting the processing contents of each task. For example, the document reading task has setting items such as resolution, color setting, and page setting. Usually, one task includes a plurality of setting items.

  The value actually set in the setting item is called “parameter”. For example, in the case of the setting item of “color setting”, the parameter is a value to be actually set such as color or black and white. Hereinafter, when exemplifying the contents of a task including parameters, parameters are represented in parentheses next to the name of the task (in this example, “read original”), such as “read original (color)” (in this example, "(Color)").

  The “task image” refers to an image representing the content of the task processing. An icon in which an execution button for executing a job of a workflow is converted into a UI is configured by combining task images indicating tasks included in the workflow. Hereinafter, an icon obtained by converting a button for executing a job of this workflow into a UI will be simply referred to as a “button icon”. Specific examples of the button icons will be described later.

  "New workflow" refers to a workflow in which a button icon is newly generated. The “similar workflow” is a workflow including a task configuration that matches a task configuration of a new workflow among workflows for which a button icon has already been generated. For example, when the task configuration included in the new workflow is “document reading → 2D code analysis → SMB transmission”, the workflow of “document reading → 2D code analysis → SMB transmission” that matches the task order is performed. Similar workflow.

  It should be noted that the task configurations of the new workflow and the similar workflow do not need to be all the same, as long as they match at least a predetermined number. For example, a workflow in which two-thirds or more of the task configuration in the workflow matches may be a similar workflow. Alternatively, a workflow in which the input task (first task) matches the output task (last task) may be a similar workflow. For example, in the above specific example, “document reading → SMB transmission” may be a similar workflow. In the present embodiment, the similar workflow is not limited to the example described above.

[Description of button icons]
FIG. 1 is an example of button icons displayed on touch panel 100 of the MFP. In FIG. 1, button icon 103 and button icon 104 are displayed on touch panel 100. The button icon 103 and the button icon 104 are button icons in which the task image 101 of “document reading” and the task image 102 of “SMB transmission” are combined. The “document reading” task image 101 is a task image indicating a “document reading” task of reading a document with a scanner. The “SMB transmission” task image 102 is a task image indicating a “SMB transmission” task of transmitting a document file to a predetermined shared folder.

  The task configuration of the workflow executed by the button icon 103 is “document reading → SMB transmission”. Also, the task configuration of the workflow executed by the button icon 104 is “document reading → SMB transmission” similarly to the button icon 103. Therefore, the button icon 103 and the button icon 104 have the same appearance and are composed of the same task image.

  However, both workflows have different task parameters. Specifically, the parameter of the “SMB transmission” of the workflow executed by the button icon 104 is “B company folder”, which is a task in which the MFP transmits a document file to the B company folder. On the other hand, the parameter of the “SMB transmission” of the workflow of the button icon 103 is “Company A folder”, which is a task for the MFP to transmit a document file to the Company A folder. Therefore, the workflow executed by the button icon 103 and the workflow executed by the button icon 104 are workflows that have the same task configuration but perform different processes.

  Therefore, the button icon 103 and the button icon 104 have a problem that the user cannot distinguish them even though they are button icons for executing different workflows. In the embodiment described below, a mode in which a button icon that is easily distinguishable by a user will be described.

<First embodiment>
FIG. 2 shows a system configuration diagram according to the first embodiment of the present invention. This system includes a plurality of image forming apparatuses 201, a plurality of client PCs 202, and a management server 203. The client PC 202 is a PC on which an application necessary for performing a task of the user is installed, and is an information processing capable of performing document processing such as approval of a document, renaming of a document file, and transmission of a document file by e-mail. Device. The image forming apparatus 201 is an information processing apparatus such as an MFP having various functions related to document processing such as reading, printing, transmitting and receiving, and managing a document. The client PC 202 or the image forming apparatus 201 is an example of the execution device 300 (see FIG. 3) that executes a workflow. The above-described processing described as being performed by the client PC 202 may be performed by the image forming apparatus 201.

  Each device is connected to the management server 203 via the network 204. Each device is connected to a communication network 205 such as a LAN that can communicate, and a system capable of exchanging information with each other is constructed.

[Hardware configuration]
FIG. 3 is a diagram illustrating a hardware configuration of the execution device 300. The execution device 300 includes a calculation unit 301, an information storage unit 302, an operation unit 303, and a display unit 304.

  The arithmetic unit 301 is a unit that controls each unit of the execution device 300. For example, the arithmetic unit 301 is realized by a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), or the like.

  The information storage unit 302 is a unit that stores various programs and data executed by the calculation unit 301. For example, the information storage unit 302 is realized by a RAM (Random Access Memory), a ROM (Read Only Memory), a HDD (Hard Disk Drive), and the like. Note that functions and processes described later of the execution device 300 are realized by the arithmetic unit 301 reading and executing a program stored in the information storage unit 302.

  The operation unit 303 is a unit that receives various operations by the user, such as pressing of a button icon by the user. The operation unit 303 is realized by a mouse, a keyboard button, a touch panel, or the like. The display unit 304 is a unit that displays various information for a user who operates the execution device 300. The display unit 304 is realized by a touch panel or a display.

[Software configuration]
FIG. 4 is a diagram illustrating a functional configuration of software of the execution device 300 and the management server 203. The execution device 300 includes a control unit 401, a display control unit 402, a management unit 403, and a workflow execution button generation unit 404. The management server 203 has a workflow generation unit 411, a workflow management unit 412, and a workflow distribution unit 413. A program that implements the software of the execution device 300 is stored in the information storage unit 302. The management server 203 also has an information storage unit (not shown) like the execution device 300, and the software of the management server 203 is stored in the information storage unit of the management server 203.

  First, the software configuration of the management server 203 will be described. The workflow generation unit 411 converts each procedure of the workflow performed by each user into a task, and generates a workflow based on parameters of setting items of the task used in the workflow. The workflow management unit 412 manages the workflow generated by the workflow generation unit 411 and the parameters set for each task. The workflow distribution unit 413 distributes the workflow generated by the workflow generation unit 411 to the execution device 300.

  In the present embodiment, the management server 203 periodically refers to the record of the processing performed by the user and manages the generated workflow. When the user requests generation of a button icon from the execution device 300, the request for generation of the button icon is transmitted from the execution device 300 to the management server 203. The request to generate a button icon includes information for specifying a workflow. The management server 203 specifies a workflow for which button icon generation has been requested from among the managed workflows, and distributes information of the specified workflow to the execution device 300.

  Next, a software configuration of the execution device 300 will be described. The control unit 401 controls the program, and instructs and manages each module. The display control unit 402 provides the display unit 304 with a UI (User Interface) for a user to operate software.

  The management unit 403 manages a workflow distributed from the workflow distribution unit 413 described below to the execution device 300. In the present embodiment, a workflow ID for identifying a workflow, a task ID for identifying a task, and a task image ID for identifying a task image are assigned. The management unit 403 manages the workflow, the task, and the task image with the respective IDs. are doing. The management unit 403 stores and manages the button icons and the workflow IDs of the workflows executed by the button icons in association with each other.

  The workflow execution button generation unit 404 generates a button icon in which a button for executing a workflow is converted into a UI, and displays the button icon on the display unit 304 via the display control unit 402. Details of the process in the workflow execution button generation unit 404 will be described later.

  The task image storage unit 405 is a storage unit that stores task images corresponding to each task. The task image storage unit 405 manages task image IDs for identifying image data of task images in a table format. Table 1 is an example of a table of the task image storage unit 405. In the task image storage unit 405, the task image is stored in association with the task ID. In the present embodiment, a plurality of task images corresponding to the task of the task ID are associated with one task ID. For example, the task ID 001 in Table 1 is associated with two task images “001_A.jpg” and “001_B.jpg”. In the present embodiment, it is assumed that task images associated with the same task ID have the same shape and different colors.

  Further, as shown in Table 1, a default image is stored in the task image storage unit 405 according to each task. The default image is used in a button icon generation process described later. When a button icon is generated, a default image is generally selected. Therefore, even if the button icons of different workflows have the same task configuration, button icons having the same appearance as in FIG. 1 are generated.

  Note that the task image storage unit 405 may be connected to the execution device 300 via the network 204, or the configuration of the execution device 300 may include the task image storage unit 405.

  FIG. 5 is a diagram illustrating a functional configuration of the workflow execution button generation unit 404. The workflow execution button generation unit 404 includes an acquisition unit 501, a determination unit 502, a comparison unit 503, and a generation unit 504. The acquisition unit 501 acquires information on tasks and parameters included in a new workflow. The determination unit 502 determines whether a similar workflow exists. The comparing unit 503 compares the parameter of the task included in the new workflow with the parameter of the task included in the similar workflow. The generation unit 504 generates a button icon by combining task images. Details of the processing performed by each unit will be described with reference to the flowchart in FIG.

[Process of generating a new button icon]
FIG. 6 is a flowchart illustrating a process in which the execution device 300 generates a button icon in the present embodiment. A series of processing shown in the flowchart of FIG. 6 is performed by the CPU expanding the program code stored in the ROM into the RAM and executing the program. Further, some or all of the functions of the steps in FIG. 6 may be realized by hardware such as an ASIC or an electronic circuit. The symbol “S” in the description of each process means that it is a step in the flowchart.

  When the execution device 300 instructs the execution device 300 to generate a button icon by a user operation, the management server 203 acquires the instruction via the network 204 and distributes the workflow to the execution device 300 as described above. After this process, the process of generating a new button icon shown in FIG. 6 starts.

  In step S601, the acquisition unit 501 acquires information such as a task ID and parameters included in a new workflow distributed from the workflow distribution unit 413 via the network 204.

  In step S <b> 602, the acquisition unit 501 acquires information such as a task ID and a parameter registered in the management unit 403 and included in an existing workflow in which a button icon is generated.

  In step S603, the determination unit 502 searches the existing workflows for a similar workflow similar to the new workflow.

  In step S604, the determination unit 502 determines whether a similar workflow exists as a search result. If it is determined in S604 that there is no similar workflow, the process proceeds to S615.

  In step S615, the generation unit 504 acquires, from the task image storage unit 405, a default task image corresponding to each task shown in Table 1 for each task included in the new workflow. The absence of a similar workflow means that there is no button icon having the same appearance, and thus a button icon is generated in S614 described below using a default task image.

  If it is determined in S604 that a similar workflow exists, in S605, the similar workflows S606 to S609 are repeated. That is, a similar workflow to be processed is selected from unprocessed similar workflows, and the processes of S606 to S609 are performed. When the processing for the similar workflow to be processed ends, a similar workflow to be processed is selected again from unprocessed similar workflows. When there are no more unprocessed similar workflows, the process proceeds to S610.

  In S606, S607 to S609 are repeated for the tasks included in the new workflow. That is, a task to be processed is selected from unprocessed tasks, and the processing of S607 to S609 is performed. When the processing for the task to be processed ends, the task to be processed is selected again from the unprocessed tasks. When there are no unprocessed tasks, the process returns to S605.

  In S607, the comparison unit 503 compares the parameter of the task to be processed included in the new workflow with the parameter of the task included in the similar workflow. For example, when the task to be processed is the first task of the new workflow, the comparing unit 503 compares the parameter with the parameter of the first task of the similar workflow to be processed.

  If the parameters match, in step S608, the generation unit 504 stores a comparison result indicating that the parameters of the tasks to be processed in the new workflow and the similar workflow are “matched” in the list. Further, the generation unit 504 acquires, from the management unit 403, the task ID of the task to be processed, the task image ID used in the similar workflow to be processed as the task image of the task, and the workflow ID of the similar workflow. The generation unit 504 stores the acquired IDs together with the comparison result in a list. The list is a list that manages the result of the comparison in S607 in association with the information of the similar workflow to be compared. The list will be described later.

  If the parameters are different, in step S609, the generation unit 504 stores a comparison result indicating that the parameters of the tasks to be processed in the new workflow and the similar workflow are “different” in the list. Further, the generation unit 504 acquires, from the management unit 403, the task ID of the task to be processed, the task image ID used in the similar workflow to be processed as the task image of the task, and the workflow ID of the similar workflow. The generation unit 504 stores the acquired IDs together with the comparison result in a list.

  Table 2 is an example in which the parameters of each task and the parameters of the new workflow are compared between workflow A and workflow B, which are similar workflows having the same task configuration as the new workflow of “document reading → SMB transmission”. A specific example of the processing of S605 to 609 will be described with reference to Table 2.

  Assuming that workflow A and workflow B have not been processed, workflow A is selected as an unprocessed workflow in S605. In step S606, “document reading” of a new workflow is selected as an unprocessed task. In step S <b> 607, the comparison unit 503 compares the parameters of the new workflow and the workflow A with respect to the color setting, size, and resolution parameters, which are the setting items of “document reading”. Regarding the setting items of the color setting of “document reading”, the parameter of the workflow A is “color”, and the parameter of the new workflow is “black and white”, so there are different parameters. Accordingly, the process proceeds to S609, and the result of the comparison is stored in the list.

  Returning to S606, “SMB transmission” is selected as an unprocessed task. In step S <b> 607, the comparison unit 503 compares the parameter of the setting item “SMB transmission” between the new workflow and the workflow A. Regarding the folder path parameter, the parameter of the workflow A is "\ 2018 \ B company" and the parameter of the new workflow is "\ 2018 \ A company", so there are different parameters. Accordingly, the process proceeds to S609, and the result of the comparison is stored in the list.

  Since the comparison with the task of the workflow A has been completed, the process returns to S605, and the workflow B is selected as an unprocessed workflow. In step S606, “read original” is selected as an unprocessed task. The comparing unit 503 compares the parameters of the setting items of “document reading” between the workflow B and the new workflow. The parameters of the setting items of color setting, size, and resolution of “document reading” match the new workflow and the similar workflow. Accordingly, the process transits to S608, and the result of the comparison is stored in the list.

  Returning to S606, the “SMB transmission” task is selected as an unprocessed task. In step S607, the comparison unit 503 compares the parameter of the setting item “SMB transmission” between the new workflow and the workflow B. Regarding the parameter of the folder path, the parameter of the workflow A is “\ 2018 \ B company” and the parameter of the new workflow is “\ 2018 \ A company”, so there are different parameters. Accordingly, the process proceeds to S609, and the result of the comparison is stored in the list. Since there are no unprocessed similar workflows, the process proceeds to S610.

  Table 3 is an example of a list that stores the comparison results in S608 and S609.

  The information stored in the list will be described using the example of the first line. For example, the parameter of the task with the task ID “001” included in the new workflow is different from the parameter of the task with the task ID “001” included in the workflow with the workflow ID “A”. For this reason, the fact that the comparison result is “different” is stored in association with the workflow ID and task ID to be compared. In the workflow ID “A” to be processed, the task image ID “001_A.jpg” used as the task image with the task ID “001” is further stored in the list in association with each other. The task image ID stored in the list is used to select a task image used when generating a button icon described later.

  In S610, S611 to S613 are repeated for the task ID of the task included in the new workflow. That is, a task ID to be processed is selected from the task IDs of the tasks included in the new workflow, and the processes in S611 to S613 are performed. When the processing for the processing target task ID is completed, the processing target task ID is selected again from the unprocessed task IDs. When there is no unprocessed task ID, the process proceeds to S614. In the example of Table 3, since the task IDs of the new workflow are “001” and “002”, the repetition processing is performed twice.

  In the subsequent processing, when there is a task with a matching result, that is, when there is a task with a matching parameter, a task image used as the task image of the task is acquired. If there is no task with a matching result, that is, if there is no task with a matching parameter, a task image not used in a similar workflow is acquired. Then, a process of generating a button icon by combining the acquired task images is performed. Hereinafter, a specific description will be given.

  In step S611, the determination unit 502 determines whether there is a task ID to be processed in the new workflow in which the result of comparing the task parameters of the similar workflow and the new workflow is “matched”. The determination unit 502 determines the task ID of the processing target as “matching task” when there is “match”, and determines the task ID of the processing target as “different task” when there is no “match”.

  If it is determined that the task is the “matching task”, the generation unit 504 acquires from the task image storage unit 405 the task image of the task image ID whose list comparison result is “match” in S612.

  For example, assume that the task ID to be processed is the task ID “001”. In Table 3, there is a task ID “001” whose comparison result is “matched”. Therefore, the determination unit determines the task with the task ID “001” as a “matching task”. The generation unit generates a task image with the task ID “001” and the comparison result “match” with the task image ID “001_B.jpg” as the task image used in the task image with the task ID “001” of the new workflow. Get a task image.

  Of the button icons in the new workflow, for a task image of a task having the same parameter, a task image used by a similar workflow is used. As a result, when the new workflow is compared with the button icons of the similar workflow, the task images of the tasks having different parameters can be relatively emphasized.

  If the task is determined to be “different task”, in S613, the generation unit 504 searches the task image storage unit 405 for a task image with a task ID of a processing target that is not used in any similar workflow. ,get.

  For example, assume that the task ID to be processed is the task ID “002”. In Table 3, there is no task ID “002” that is “matched” in the comparison result. Therefore, the determination unit determines the task with the task ID “002” as “different task”. The generation unit generates a task image ID “002_B.jpg” other than the task image ID of the task ID “002” in the workflow IDs “A” and “B” as the task image used in the task ID “002” of the new workflow. Get a task image.

  Among the button icons in the new workflow, task images other than the task images used by similar workflows are used for task images of tasks having different parameters. As a result, when the button icons of the new workflow and the similar workflow are compared, the task images of the tasks having different parameters can be emphasized.

  In S614, the generation unit 504 generates a button icon by combining the task images acquired in S612 and S613 or by combining the task images acquired in S615. In the button icon generation process, one button icon image file may be generated by combining a plurality of task image files. Alternatively, control may be such that a plurality of images are combined and displayed as a button icon on a UI screen without generating one button icon image file.

  FIG. 7 is a diagram illustrating the button icons displayed on the display unit 304 when the button icons are generated based on the present embodiment. On the home screen 700, a button icon 701 of the registered workflow A “Document reading (color) → SMB transmission (Company A)” is displayed. Also, the home screen 700 displays a registered workflow B “document reading (monochrome) → SMB transmission (Company A)” button icon 702, other button icons 703 and button icons 704.

  The home screen 705 is a home screen after the button icon 706 of the new workflow “document reading (black and white) → SMB transmission (company B)” is generated. Similar workflows similar to the new workflow are registered workflows A and B. The parameters of “document reading” of the new workflow and workflow B, which is a similar workflow, are identical because they are “black and white”. Therefore, the task image (001_B.jpg) used in the workflow B is used as the task image of the “document reading” of the button icon of the new workflow. Also, the parameters of “SMB transmission” between the new workflow and the similar workflows A and B are different. Therefore, the task image of the "Send SMB" button icon of the new workflow does not use the task image (002_A.jpg) used in workflow A and workflow B, but uses a different task image (002_B.jpg). Is done. The button icon 706 of the new workflow is generated using the task image (001_B.jpg) and the task image (002_B.jpg). The generated button icon 706 is displayed on the display unit 304 via the display control unit 402.

  As described above, according to the present embodiment, when a button icon of a new workflow is generated, a button icon different from a button icon of a similar workflow can be generated. In other words, among tasks included in the new workflow, for a task having a different parameter from the task of the new workflow and the task of the similar workflow, a button icon is generated using a different task image. Since the workflow button icons include a plurality of task images, the button icons generated in this manner are displayed with task images of tasks executed with different parameters substantially emphasized.

  Therefore, even when a plurality of button icons of a similar workflow are displayed on the display unit 304, the user can easily identify different tasks, thereby preventing the user from accidentally pressing another button icon. it can.

  In the present embodiment, a method of changing the color of a task image as a task image of a different task has been described, but is not limited to this example. Any method may be used as long as it can be distinguished from a task image of a similar workflow by image color, image frame color (highlight), image size, image animation, task parameter display, and the like.

<Second embodiment>
In the present embodiment, an embodiment will be described in which the task image of a new workflow and a similar workflow has the same task parameters and the task image is reduced. As a result, the effect on the user's visual perception of the task image of the task having the same parameter is reduced. In the present embodiment, both processes of generating a button icon of a new workflow and updating a button icon of a similar workflow are performed. This embodiment will be described focusing on differences from the first embodiment. Unless otherwise specified, the configuration and processing are the same as in the first embodiment.

  FIG. 8 is a flowchart illustrating a process in which the execution device 300 generates a button icon in the present embodiment. Steps S801 to S811 are the same as steps S601 to S611 in FIG.

  In step S <b> 812, the generation unit 504 specifies the task ID of the task whose parameters match and the task image ID of a similar workflow including the task. The generation unit 504 acquires a reduced image of the task image with the specified task image ID from the task image storage unit 405. The reduced image is an image obtained by reducing the task image stored in the task image storage unit 405. The reduced image may be prepared in advance and stored in the task image storage unit 405, or may be generated by performing a process of reducing the size of the button icon to a task image.

  Table 4 is an example of a list storing comparison results obtained by comparing task parameters in the present embodiment. In the present embodiment, the similar workflow similar to the new workflow is the workflow with the workflow ID “C”.

  In Table 4, in the task ID “001”, the workflow ID “C” and the task parameter of the new workflow “match”. Therefore, the generation unit 504 acquires a reduced image of the task image with the image ID “001_B.jpg” of the workflow ID “C” from the task ID “001”. Step S813 is the same as step S613 in FIG. 6, and a description thereof will be omitted.

  In S814, the generation unit updates the button icon of the similar workflow. Specifically, the generation unit 504 changes the task image of the task whose parameters match among the button icons of the similar workflow to the reduced image acquired in S812.

  In step S815, the generation unit 504 generates a button icon for a new workflow using the images acquired in steps S812 and S813. That is, the generation unit 504 uses the reduced image acquired in S812 as the task image of the task whose parameters match among the button icons of the new workflow. Further, the generation unit 504 uses the task image acquired in S813 as the task image of the task having a different parameter among the button icons of the new workflow. Step S816 is the same as step S615 in FIG. 6, and a description thereof will be omitted.

  FIG. 9 is a diagram illustrating the button icons displayed on the display unit 304 when the button icons are generated based on the present embodiment. On the home screen 900, a button icon 901 of the registered workflow C “read original (black and white) → SMB transmission (Company A)” is displayed.

  The home screen 910 displays the home screen after the button icon 912 of the new workflow “document reading (monochrome) → SMB transmission (company B)” is generated. The parameters of “document reading” of the new workflow and the workflow C, which is a similar workflow, are “black and white” and therefore match. Therefore, a reduced image 913 of the task image 902 corresponding to the “document reading” task of the workflow C is used as the task image of the “document reading” of the button icon of the new workflow. The task image 902 of “document reading” of the button icon 901 of the workflow C is changed to a reduced image 913 obtained by reducing the task image 902, and the button icon 901 of the workflow is updated to the button icon 911.

  As described above, according to the present embodiment, among the task images of the button icons of the new workflow and the similar workflow, the task images of the tasks having the same parameters are reduced in size, thereby reducing the influence on the user's visual sense. Let it be less. Therefore, task images having different task parameters between the new workflow and the similar workflow are displayed relatively emphasized. This allows the user to easily identify different task locations from the plurality of button icons.

  In the present embodiment, an example has been described in which a task image corresponding to a task having the same task parameter as that of a new workflow and a similar workflow is set as a reduced image. May be reduced. For example, a method of reducing the color of the task image, not displaying the task image on the button icon, or simplifying the task image may be used. Also, the process of updating the similar workflow in S814 of FIG. 8 may not be performed. That is, in the present embodiment, only a process of generating a button icon of a new workflow may be performed.

<Third embodiment>
In the present embodiment, the contents of the parameters are displayed near the task images of the tasks having different parameters. This embodiment will be described focusing on differences from the first embodiment. Unless otherwise specified, the configuration and processing are the same as in the first embodiment.

  FIG. 10 is a diagram illustrating a functional configuration of the workflow execution button generation unit 404 according to the present embodiment. The workflow execution button generation unit 404 includes an acquisition unit 501, a determination unit 502, a comparison unit 503, a generation unit 504, and a parameter acquisition unit 505.

  The functions of the acquisition unit 501, the determination unit 502, the comparison unit 503, and the generation unit 504 are the same as in the first embodiment. The parameter acquisition unit 505 acquires character string information that is character information indicating the content of the parameter of each task having a different parameter.

[Button icon generation and update processing]
FIG. 11 is a flowchart illustrating a process in which the execution device 300 generates a button icon in the present embodiment. Steps S1101 to S1108 are the same as steps S601 to S608 in FIG.

  As a result of the comparison in S1107, if the parameters are different, in S1109, the generation unit 504 stores in the list that the parameters of the task to be processed are “different”, as in S609. Further, the generation unit 504 acquires the task ID, the task image ID used as the task image, and the workflow ID of the similar workflow from the management unit 403, and stores them in the list, as in S609.

  In S1109, the parameter obtaining unit 505 further obtains character string information of the parameter. More specifically, the character string information of the parameter of the part where the comparison result differs between the new workflow and the similar workflow is acquired from the management unit 403. The parameter acquiring unit 505 stores the character string information of the acquired parameter as “difference parameter” in the list. The character string information of the parameter is, for example, in the case of the color setting of the setting item of the document reading task, the character itself indicating the content of the parameter such as “black and white” or “color” indicating the value of the color setting.

  Table 5 is an example of the list recorded in S1108 and S1109. The list used in the present embodiment will be described with reference to Table 5. The list according to the present embodiment is a list obtained by adding items of difference parameters to the list described in the first embodiment. In the present embodiment, the workflow with the workflow ID “D” is a similar workflow.

  In Table 5, as a result of the comparison in S1107, the parameter of the task with the task ID “002” included in the similar workflow with the workflow ID “D” is different from the parameter of the task with the task ID “002” included in the new workflow. ing. Therefore, the comparison result is stored as “different”, and the character string information indicating the contents of the different parameter of the task ID “002” between the new workflow and the workflow ID “D” is stored. In Table 5, among the setting items of the task ID “002”, the parameters of the setting items of the folder path are different. For this reason, "\ 2018 \ B company" which is a parameter of the folder path of the new workflow is stored in the difference parameter. Further, the parameter “\ 2018 \ Company A” of the folder path of the workflow ID “D” is stored in the difference parameter.

  In S1110, as in S610 of FIG. 6, S1111 to S1115 are repeated for the task ID of the new workflow. That is, a task ID to be processed is selected from the unprocessed task IDs stored in the list, and the processing from S1111 to S1115 is performed. When the processing for the processing target task ID is completed, the processing target task ID is selected again from the unprocessed task IDs. If there are no unprocessed task IDs, the process proceeds to S1116. Steps S1111 to S1113 are the same as steps S611 to 613 in FIG.

  In step S1114, the generation unit 504 acquires character string information of the “difference parameter” of the new workflow from the “difference parameter” in the task ID to be processed. For example, in Table 5, assuming that the task ID to be processed is “002”, the generation unit 504 determines “\ 2018 \ B” in the difference parameter with the task ID “002” that is associated with the new workflow. Get the character string information of "company".

  In step S1115, the generation unit 504 acquires character string information of the “difference parameter” of the similar workflow from the “difference parameter” of the list in the task ID to be processed. For example, in Table 5, assuming that the task ID to be processed is “002”, the generating unit 504 determines “\ 2018” that is associated with the workflow ID “D” among the difference parameters with the task ID “002”. Get the character string information of "\ A company".

  In step S1116, the generation unit 504 updates the button icons of the similar workflow. That is, the generation unit 504 updates the button icon of the similar workflow so that the character string information of the parameter acquired in S1115 is displayed near the task image of the task having a different parameter. Here, the provision near the task image may be, for example, a form provided near the task image or a form displayed so as to overlap the task image. The character string information provided near the task image is referred to as “attribute information”. An example of the button icon will be described later in the description of FIG.

  In step S1117, the generation unit 504 uses the task image acquired in step S1113 as a task image of a task having a different parameter to generate a button icon for a new workflow. Here, the generation unit 504 generates a button icon so that the character string information acquired in S1114 is displayed near a task image of a task having a different parameter. As for the task image of the task whose parameters match, the task image used by the similar workflow is used to generate the button icon of the new workflow as in the first embodiment. The generating unit 504 generates a button icon of a new workflow using the task image and the character string information. Step S1118 is the same as step 615 in FIG. 6, and a description thereof will be omitted.

  FIG. 12 is a diagram illustrating the button icons displayed on the display unit 304 when the button icons are generated based on the present embodiment. On the home screen 1200, a button icon 1201 of the registered workflow D “Read original (black and white) → SMB transmission (Company A)” is displayed.

  The home screen 1210 is a home screen after the button icon 1212 of the new workflow “document reading (black and white) → SMB transmission (Company B)” is generated. The parameters of the “SMB transmission” between the new workflow and the similar workflow D are different. Therefore, a task image different from the task image used in the workflow D is used as the task image of the “SMB transmission” of the button icon of the new workflow as in the first embodiment. In the present embodiment, “2018 @ B company” of the character string information 1214 of the parameter of “SMB transmission” stored as the difference parameter is added to the vicinity of the task image as the attribute information of “SMB transmission”. .

  Also for the button icon of the workflow D, the character string information 1213 “2018 @ A company” of the parameter of the “SMB transmission” of the workflow D stored as the difference parameter is added as the attribute information of the task image of “SMB transmission”. You. Then, the button icon 1201 is updated to the button icon 1211.

  As described above, in the present embodiment, attribute information is assigned to task images having different parameters, and the user can recognize the contents of different parameters of tasks of a new workflow and a similar workflow. Therefore, even when the button icons of a plurality of similar workflows are registered, the user can easily distinguish the workflow processed by the button icon.

  This embodiment may be implemented in combination with the second embodiment. By implementing the second embodiment, the reduced task image is used as the task image of the task in which the task parameters of the new workflow and the similar workflow match, and the space for displaying the attribute information is reduced. Can be caused. Note that, similarly to the second embodiment, the similar workflow update process in S1116 in FIG. 11 may not be performed. That is, a mode in which only the process of generating the button icon of the new workflow may be performed.

<Fourth embodiment>
In the present embodiment, a task image and attribute information are manually changed. The description of the present embodiment focuses on the differences from the third embodiment described above, and the components and processes that are not specified are the same as those of the third embodiment.

  FIG. 13 is a diagram illustrating a functional configuration of the workflow execution button generation unit 404 according to the present embodiment. The workflow execution button generation unit 404 includes an acquisition unit 501, a determination unit 502, a comparison unit 503, a generation unit 504, a parameter acquisition unit 505, and a change unit 506.

  The functions of the acquisition unit 501, the determination unit 502, the comparison unit 503, the generation unit 504, and the parameter acquisition unit 505 are the same as in the third embodiment. The changing unit 506 changes the task image of the button icon and the attribute information of the task image according to the user's instruction.

[Processing of button icon change]
FIG. 14 is a flowchart illustrating a process in which the execution device 300 changes the button icon in the present embodiment.

  In step S1401, when the user requests a change of a button icon from the operation unit 303, the acquisition unit 501 obtains the change request and requests the change unit 506 to change the button icon.

  In step S1402, the changing unit 506 specifies the task of the task image for which the change has been requested, and acquires information on the task whose change has been requested from the management unit 403.

  In step S1403, an instruction is input as to whether the task image is to be changed or the attribute information of the task image is to be changed in response to a user operation. The change unit 506 determines whether the input command changes the task image or changes the attribute information of the task image.

  If it is determined that the task image has been changed, in step S1404, the changing unit 506 acquires, from the task image storage unit 405, another task image of the task ID to which the task image whose change has been requested belongs. The acquired task image is displayed on the display unit 304 via the display control unit 402 as a task image candidate to be changed by the user.

  If it is determined that the attribute information has been changed, in step S1405, the changing unit 506 causes the display unit 304 to display an input dialog for receiving character string information of the attribute information changed by the user via the display control unit 402. The input dialog is a UI that allows the user to request the change unit 506 to change the attribute information by inputting an arbitrary character. Further, the user can select not to display the attribute information by not inputting a character in the input dialog.

  In step S1406, the changing unit 506 acquires the content according to the user's input. For example, the user selects a task image to be changed from the candidates displayed in S1404 and requests the content of the button icon change. Alternatively, the user inputs the character string information in the input dialog displayed in step S1405 and requests the contents of the change of the attribute information. Alternatively, the user makes a request not to display the attribute information without inputting the character string information in the input dialog. The change unit 506 acquires the content of the change.

  For example, assume that “2018 @ A company” is displayed as attribute information of “SMB transmission” of the button icon. When the user changes the display of the attribute information to “Company A”, the user inputs “Company A” in the input dialog. The change unit 506 acquires “Company A” as the content of the attribute information to be changed, and the attribute information is changed to “Company A” by a process described later.

  In step S1407, the changing unit 506 changes the task image or the attribute information based on the request acquired in step S1406, and changes the button icon.

  FIG. 15 is a diagram illustrating the button icons according to the present embodiment displayed on the touch panel of the execution device 300 that also serves as the operation unit 303 and the display unit 304. On the home screen 1500 of the touch panel, a button icon 1501 of a registered workflow “read original (black and white) → SMB transmission (company B)” is displayed. The user long-presses the task image to be changed or the task image 1502 of the task to which the attribute information to be changed belongs among the task images of the button icons 1501. When the task image 1502 is held down, a command to change the button icon is issued, and a button icon change dialog 1503 is displayed on the touch panel. In the button icon change dialog 1503, the user can select whether to change the task image or the attribute information. When changing the task image, the user selects the task image to be changed from the task image candidates shown in the button icon change dialog 1503. When changing the attribute information, the user inputs characters to be displayed as attribute information in the input dialog displayed on the button icon change dialog 1503. Then, the task icon or the attribute information of the button icon is changed.

  As described above, in the present embodiment, the task image and the attribute information of the button icon can be changed according to the user's preference. Therefore, the user can select a task image or attribute information that can be easily distinguished, so that the user can easily distinguish the button icons.

  The method of specifying the task image to be changed by the user is as follows: When the user presses and holds any part of the button icon, a selection screen for selecting the task image to be changed is displayed, and the user can select which task image to change. A method of allowing the user to select whether to do so may be used.

  Also, the method of displaying the button icon change dialog 1503 is to long-press the task image, but is not limited to this. An operation (flick operation) in which the button icon is pressed with a finger and then moved so as to flick the finger may be used. Further, the change is not necessarily performed by the display of the button icon change dialog 1503. For example, an operation method in which the task image is sequentially switched to another task image each time the user presses the task image on the button icon twice lightly may be used.

<Other embodiments>
In the above-described embodiment, the execution device 300 that executes a workflow is described as a device that generates a button icon. However, the execution device that executes a workflow and the device that generates a button icon may be different. For example, the management server 203 may generate a button icon. That is, a program for realizing the workflow execution button generation unit 404 is stored in an information storage unit (not shown) of the management server 203, and the management server 203 generates a button icon, and the icon generated by the workflow distribution unit 413. May be delivered to the execution device 300. This eliminates the need for the user to request generation of a button icon for executing the same workflow for each execution device 300 when a plurality of execution devices 300 are arranged.

  It is described that the programs for realizing the workflow generation unit 411 and the workflow management unit 412 are stored in the information storage unit (not shown) of the management server 203, but are stored in the information storage unit 302 of the execution device 300. Is also good.

  In the above-described embodiment, a new button icon is generated by a user's operation on the execution device 300. However, a button icon may be generated without an instruction from the user. For example, each time a user performs a process on the execution device 300, a workflow and its button icon may be generated. In addition, a workflow and its button icon may be generated for a process performed by the user over a certain number of times in the execution device 300.

  The present invention supplies a program for realizing one or more functions of the above-described embodiments to a system or an apparatus via a network or a storage medium, and one or more processors in a computer of the system or the apparatus read and execute the program. This processing can be realized. Further, it can also be realized by a circuit (for example, an ASIC) that realizes one or more functions.

404 workflow execution button generation unit 501 acquisition unit 502 determination unit 503 comparison unit 504 generation unit

Claims (17)

An information processing apparatus that generates an icon corresponding to the workflow by using a plurality of task images corresponding to a plurality of tasks included in the workflow,
Acquisition means for acquiring a new workflow;
When there is a similar workflow similar to the new workflow, the new workflow is created by using a task image different from at least one task image among a plurality of task images used to generate an icon corresponding to the similar workflow. Generating means for generating an icon corresponding to the workflow;
An information processing apparatus comprising: Comparing means for comparing a parameter indicating a value of a setting item of the first task included in the new workflow with a parameter indicating a value of a setting item of the first task included in the similar workflow. The information processing apparatus according to claim 1, wherein: The generation means,
As a result of the comparison by the comparing means, when the parameter of the first task included in the new workflow is different from the parameter of the first task included in the similar workflow, generation of an icon corresponding to the similar workflow 3. An icon corresponding to the new workflow is generated by using a first task image different from a task image corresponding to the first task included in the similar workflow used in (1). An information processing apparatus according to claim 1. The generation means,
In the comparing means, as a result of comparing the parameters of the second task included in the new workflow and the parameters of the second task included in the similar workflow, if the parameters of the second task match, A task image corresponding to the second task used for generating the icon corresponding to the similar workflow is used as a task image corresponding to the second task of the new workflow to correspond to the new workflow. The information processing apparatus according to claim 2, wherein the icon is generated. The generation means,
In the comparing means, as a result of comparing the parameters of the second task included in the new workflow and the parameters of the second task included in the similar workflow, if the parameters of the second task match, An icon corresponding to the new workflow is generated by using, as a task image corresponding to the second task included in the new workflow, a task image that has less influence on the user's vision. The information processing device according to claim 2. The generating unit further updates an icon corresponding to the similar workflow by using a task image having a reduced effect on the user's vision as a task image corresponding to the second task included in the similar workflow. The information processing apparatus according to claim 5, wherein: The task image with less influence on the user's vision, by reducing the task image according to the second task, or by lightening the color of the task image according to the second task, The information processing apparatus according to claim 5, wherein the task image is an obtained task image. The generation means,
In the comparing means, as a result of comparing the parameters of the second task included in the new workflow and the parameters of the second task included in the similar workflow, if the parameters of the second task match, The information processing apparatus according to claim 2, wherein an icon corresponding to the new workflow is generated without using a task image corresponding to the second task. As a result of the comparison by the comparing means, when the parameter of the first task included in the new workflow and the parameter of the first task included in the similar workflow are different, character string information indicating the different parameter is Further comprising parameter acquisition means for acquiring
The generation means corresponds to the new workflow in which character string information indicating a parameter of the first task included in the new workflow is displayed near a task image corresponding to the first task. The information processing apparatus according to claim 2, wherein the information processing apparatus generates an icon to be executed. The generation unit may further include a step of displaying character string information indicating a parameter of the first task included in the similar workflow in the vicinity of a task image corresponding to the first task. The information processing device according to claim 9, wherein a corresponding icon is updated. The information according to any one of claims 1 to 10, wherein the similar workflow is a workflow that includes a configuration of a task that matches a configuration of a plurality of tasks included in the new workflow at least a predetermined number of times. Processing equipment. The execution device that executes the workflow is the same device as the information processing device,
The information processing apparatus according to claim 1, further comprising a display unit configured to display an icon generated by the generation unit. The information processing apparatus according to claim 1, further comprising a change unit configured to change a task image included in the icon generated by the generation unit in accordance with a user instruction. A change unit configured to change the character string information displayed near a task image corresponding to the first task included in the icon generated by the generation unit in accordance with a user's instruction. The information processing device according to claim 9. 12. The information processing apparatus according to claim 1, further comprising: a distribution unit configured to distribute an icon generated by the generation unit to an execution device that executes the workflow via a network. 13. Information processing device. A generation method for generating an icon corresponding to the workflow using a task image corresponding to each of a plurality of tasks included in the workflow,
An acquiring step of acquiring a new workflow, wherein the acquiring means of the device acquires
When a similar workflow similar to the new workflow exists, the generation unit of the device includes a task image different from at least one of a plurality of task images used for generating an icon corresponding to the similar workflow. A generating step of generating an icon corresponding to the new workflow using
A method for generating an icon, comprising:   A program for causing a computer to function as each unit of the information processing apparatus according to claim 1.

Images