JP2017126155A - Information processing device, system, information processing method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technology for improving operability about the selection of an operation instruction object about a workflow and reducing a push error of an operation instruction object, or the like.SOLUTION: An information processing device includes acquisition means for acquiring text information of a plurality of documents about a workflow, determination means for determining text information to be displayed in each of a plurality of operation instruction objects about the workflow on the basis of difference of a plurality of pieces of the text information acquired by the acquisition means, and generation instruction means for designating the text information determined by the determination means, to be displayed in the operation instruction object, and instructing the image processing device to generate the operation instruction object.SELECTED DRAWING: Figure 6

Description

  The present invention relates to an information processing apparatus, system, information processing method, and program related to a workflow.

At present, automatic execution of a document workflow using a workflow engine is attracting attention in order to improve the efficiency of routine work dealing with documents.
The workflow engine operates on the server, and executes tasks such as printing a document file on the server with a printer and notifying an operator of an email in accordance with a predetermined workflow procedure. The workflow engine can cause a device such as a PC connected to the server via a network to execute processing such as saving, moving, and editing a document file. Furthermore, the workflow engine can cause a device such as an MFP connected to the server as a network to execute processing such as printing of a document file and transmission of stored electronic data as tasks in the workflow.
However, a process involving scanning of a paper document, such as scanning and transmitting electronic data, cannot be automatically executed by the workflow engine alone because a physical paper document needs to be set in the scanner. For this reason, an operation instruction button for executing the scan determined in the workflow procedure is generated in advance on the operation unit on the MFP, and the user manually sets a paper document on the scanner and selects the operation instruction button. By doing so, it is necessary to execute the scanning process. Usually, the operation instruction button is generated in advance on the operation unit of the MFP by the administrator or the creator of the workflow.
Patent Document 1 discloses a technique in which a workflow execution system generates a scan execution instruction button on an MFP at the start of a workflow.
In addition, documents having the same format but different contents may be executed in parallel by the same workflow. For example, there are cases where a plurality of article purchase application forms with different articles to be purchased are processed in the same workflow, or outing application notifications with different visiting places and dates / times are processed in the same workflow. In this case, a plurality of scan execution instruction buttons for processing the same workflow are generated for each document to be processed on the MFP.

JP 2010-160762 A

When a plurality of documents having different contents are simultaneously executed by the same workflow, a plurality of buttons for executing scanning by the workflow engine are generated for each document on the MFP. Here, depending on the contents of the document, they are set to change the storage destination and file name of the file after scanning. Therefore, it is necessary for the user to clearly distinguish which scan execution button is instructed for which document.
However, when there are a plurality of scan execution buttons, it is difficult for the user to accurately grasp the difference between them and select and instruct the buttons. For this reason, there is a possibility that the user instructs the wrong scan execution button for each document to be scanned.

  The information processing apparatus according to the present invention displays an acquisition unit that acquires text information of a plurality of documents related to a workflow, and displays each of the plurality of operation instruction objects related to the workflow based on a difference between the plurality of text information acquired by the acquisition unit. Determination means for determining text information to be performed, and generation instruction means for designating text information to be displayed on the operation instruction object determined by the determination means and instructing the image processing apparatus to generate the operation instruction object.

  ADVANTAGE OF THE INVENTION According to this invention, while improving the operativity regarding selection of the operation instruction | indication object regarding a workflow, the technique which reduces a pressing mistake etc. of an operation instruction object can be provided.

It is a figure which shows an example of the system configuration | structure of a workflow system. 2 is a diagram illustrating an example of a hardware configuration of an MFP. FIG. It is a figure which shows an example of the hardware constitutions of WF server. It is a figure which shows the example of a workflow typically. It is a flowchart explaining the flow of a process of instance management. It is a flowchart explaining the flow of a process of a workflow instance. 6 is a diagram illustrating an example of an operation screen displayed on an operation display unit of the MFP. FIG. It is a flowchart explaining the flow of a process of a workflow instance. It is a figure which shows an example of the document converted into image data. 6 is a diagram illustrating an example of an operation screen displayed on an operation display unit of the MFP. FIG. It is a flowchart explaining the flow of a process of a workflow instance. FIG. 10 is a diagram illustrating an example of a document printed in S1107. 6 is a diagram illustrating an example of an operation screen displayed on an operation display unit of the MFP. FIG. It is a flowchart explaining the flow of a process of a workflow instance.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

<Embodiment 1>
FIG. 1 is a diagram illustrating an example of a system configuration of a workflow system.
In the workflow system, an MFP 101, a server (hereinafter referred to as a WF server) 102 in which a workflow engine is mounted, and a PC 103 are connected by a network configured by a LAN 104. The MFP 101 is an example of an image processing apparatus. The WF server 102 is an example of an information processing apparatus.
The MFP 101 scans a paper medium, forms an image on a sheet based on the scan data, and prints it. The scan function transmits scan data as electronic data to the WF server 102 or the PC 103 via a network. have. Further, the MFP 101 also has a function of printing out the transmitted image data or scanning and transmitting it in response to a request from an external device connected to the network such as the WF server 102. At this time, setting values for the print, copy, and scan transmission functions are specified by the WF server 102 that is a request for processing execution when the execution is requested.
The WF server 102 has a function of a workflow engine (hereinafter referred to as WF engine) that executes processing in order according to a processing order designated in advance. The WF engine automatically performs processing such as a file operation in the WF server 102 or the PC 103, mail transmission to the mail server, processing execution request to the MFP 101, etc., in accordance with the workflow definition in which the processing order designated in advance is described.

FIG. 2 is a diagram illustrating an exemplary hardware configuration of the MFP 101.
The MFP 101 includes a controller unit 200 to which a scanner 213 and a printer 214 can be connected and an operation display unit 211, an operation input unit 212, and a LAN 104 can be connected.
The controller unit 200 includes a CPU 201 that executes various control programs.
The CPU 201 activates the MFP 101 based on the boot program stored in the ROM 203. Further, the CPU 201 reads a control program stored in the HDD 204 and executes predetermined processing using the RAM 202 as a work area.
The HDD 204 stores various control programs including copy and scan transmission functions, and stores scan data read from the scanner 213.
The operation unit output I / F 205 performs data output communication control to the operation display unit 211.
The operation unit input I / F 206 performs data input communication control from the operation input unit 212.
A network I / F 207 is connected to the LAN 104 and performs input / output control of information via the LAN 104.
A scanner I / F 208 inputs image data from the scanner 213 and inputs / outputs scanner control data.
A printer I / F 209 outputs output image data to the printer 214 and inputs / outputs printer control data.
As described above, the devices 201 to 209 are arranged on the system bus 210.

The operation input unit 212 is an instruction input interface from a user including input devices such as a touch panel and hard keys. The hard key includes a start button and the like for instructing start of scanning of a paper document.
The operation display unit 211 is a display interface for a user including a display device such as an LCD or LED.
The scanner 213 includes an optical reading device such as a CCD, and has a function of optically scanning a paper medium and reading it as electronic image data.
The printer 214 has a function of forming electronic image data as an image on a recording medium such as paper.
Further, the MFP 101 can accept an execution request for print processing or the like from a device outside the apparatus via the network I / F 207. The processing execution request is requested from an external device together with the type of execution processing, setting value information at the time of execution, etc., temporarily stored in the HDD 204, RAM 202, etc., and then executed by the CPU 201.
Furthermore, when the execution request process is a process involving a scan such as scan transmission, the MFP 101 can display an instruction button or the like for starting the process execution on the operation display unit 211. In this case, when the user sets a document on the scanner 213 and designates a start instruction button via the operation input unit 212, the MFP 101 executes a scan process according to a setting value designated by an external request.
The function of the MFP 101 is realized by the CPU 201 executing a process based on a program stored in the ROM 203 or the HDD 204.

FIG. 3 is a diagram illustrating an example of a hardware configuration of the WF server 102.
The WF server 102 has a control unit 300 that can be connected to the LAN 104.
The control unit 300 includes a CPU 301 that executes various control programs, and controls the overall operation of the WF server 102.
The CPU 301 reads a control program stored in the ROM 303 or the HDD 304, and executes predetermined processing using the RAM 302 as a work area. The HDD 304 stores various control programs including functions such as a WF engine, a WEB server, and a workflow editor. The HDD 304 also stores a workflow definition executed by the WF engine.
A network I / F 305 performs input / output control of information via the LAN 104.
An operation unit output I / F 306 controls data output communication to the operation display unit 308.
The operation unit input I / F 307 performs data input communication control from the operation input unit 309.
As described above, the devices 301 to 307 are arranged on the system bus 310.

The operation display unit 308 is a display interface for a user including a display device such as an LCD or LED.
The operation input unit 309 is an instruction input interface from a user including input devices such as a keyboard and a mouse.
In the WF server 102, a WEB server is operating. The WF engine can provide HTML content using a WEB server. The WF engine can dynamically generate content by CGI (Common Gateway Interface) or the like, and can provide an operation screen for workflow execution. When the CPU 301 executes processing based on a program stored in the ROM 303 or the HDD 304, the following functions and processing are realized. That is, the function of the WF server 102, the WF engine, the WEB server, a workflow editor described later, and the like are realized. Further, the processing of the flowcharts of FIGS. 5, 6, 8, 11, and 14 to be described later is realized.
The PC 103 has the same hardware configuration as the WF server 102. The functions of the PC 103 are realized by executing processing based on a program stored in the CPU of the PC 103 or the ROM or HDD of the PC 103.

FIG. 4 is a diagram schematically illustrating an example of a workflow.
Flow processes 401 to 404 represent processes of the workflow executed by the WF engine. A workflow indicated by the flow processes 401 to 404 is a workflow for processing a document. In the example of FIG. 4, the flow processes 401 to 404 are continuously executed. The WF engine controls the electronic data document designated at the start of the workflow to continuously execute these processes.
The flow process 401 is an approval process. The approval process is a process for obtaining, for example, the approval of the contents described in the document from the superior of the user who designates the document and instructs the start of the workflow. More specifically, the WF engine obtains the superior email address of the user who started the workflow from the directory service or database, and sends an approval request and an input instruction on the WEB screen provided by the WF engine by email. Send. When an approval result indicating that the superior is allowed on the WEB screen provided by the WF engine is input, the WF engine executes the following flow process 402. Here, the case where the upper manager inputs something other than permission, such as rejection, is omitted for the sake of simplicity.
A flow process 402 is a process for printing a document by the MFP 101. More specifically, the WF engine displays an instruction screen related to printing on the WEB screen. When the user instructs printing, the WF engine transmits a document to the MFP 101 and instructs printing. Since printing a document involves obtaining printed paper, the WF engine does not automatically print, but allows the user to instruct printing to execute printing. At this time, if there are a plurality of printable MFPs, the WF engine can also instruct the user which MFP to print.

When printing is executed in the flow process 402, the WF engine executes the next flow process 403. A flow process 403 is a process for causing the MFP 101 to scan a paper document and transmitting the scanned electronic data to the WF server 102. More specifically, first, the WF engine instructs the MFP 101 to generate an instruction button for executing scan transmission. Here, the WF engine specifies a setting value of scan transmission executed when the button is instructed in association with the instruction button. Furthermore, the WF engine notifies the user who started the workflow by e-mail that the scan transmission start instruction button has been generated for the MFP 101. When the user designates a scan transmission start instruction button in the MFP 101 and executes scan transmission, the electronic data read by scanning is transmitted to the transmission destination setting designated by the WF engine. The WF engine monitors the reception of the electronic data, and executes the next flow process 404 when confirming that the electronic data has been received.
The flow process 404 is a process for storing electronic data as a file in a file system such as a PC or a file server. More specifically, the WF engine converts the received electronic data into a predetermined file format or changes the file name, and then moves the file to a designated location in the file system.
In the flow process 404, when the movement of the file is completed, the WF engine sends an email indicating that all the workflow processes have been executed to the user, and the execution of the workflow is completed.

In the workflows from the flow processes 401 to 404, the following processes are performed in order. In other words, for the application form generated as electronic data, confirmation and approval by the superior, printing, stamping or signing the printed paper document, saving the paper document after sealing as electronic data and submitting the paper document Processing is performed in order.
This is an example based on an application form processing flow processed in a general office.
The workflow shown in FIG. 4 is used as an example of a workflow executed by the WF engine in the following description of the embodiments. In addition, the flow processes 401 to 404 in the workflow can be subdivided into several fine processes as described above.
An execution unit of a workflow in which a certain amount of detailed processing, such as the flow processing 401 to 404, is called a task for convenience. In addition, a detailed processing execution unit such as mail transmission or file name change in each task is called an action for convenience. For example, the flow process 401 can be expressed as one task.
Furthermore, a series of workflows in the flow processes 401 to 404 may be executed simultaneously by the same user. This is the case where a plurality of article purchase application forms with different articles to be purchased are processed with the same workflow, or when an outing application report with different visiting destinations and dates / times is processed with the same workflow.
As described above, when there are a plurality of application forms that are actually processed by the same workflow, and these are simultaneously processed by the WF engine, the processing of each workflow is referred to as a workflow instance for convenience. When the WF engine executes a workflow, an instance of the workflow is generated, and workflow tasks and actions are executed in the instance. Even when a plurality of the same workflows are simultaneously executed, each document is processed separately by each instance.
In the present embodiment, a case where instance processing of the same workflow by the same user is executed at the same time will be described.

FIG. 5 is a flowchart for explaining the flow of instance management processing by the WF engine.
The flow described in FIG. 5 is a main process executed by the WF engine, and is a process for generating and managing a workflow instance in response to a workflow execution request. The process of an instance that performs processes related to actual workflow tasks and actions will be described later.
First, in S501, the WF engine waits to receive an event related to workflow execution. Events related to workflow execution include a workflow start instruction from the user, a print execution notification from the MFP by the workflow execution, a scan transmission execution notification, a file reception notification from the WF server or PC, and the like.
In step S502, the WF engine determines whether an event related to workflow execution has been received. If no event has been received (NO in S502), the WF engine returns to the process of S501. On the other hand, if it is determined that an event related to workflow execution has been received (YES in S502), the WF engine proceeds to S503. In step S503, the WF engine determines whether the received event is a workflow start instruction.
If it is determined that the instruction is a workflow execution instruction (YES in S503), the WF engine proceeds to S507. In step S507, the WF engine generates and executes a workflow instance. Each instance is executed by the WF engine, but is executed as a separate process from the instance management flow of the WF engine.
The WF engine that generated and executed the instance returns to the process of S501.

On the other hand, if it is determined that the instruction is not a workflow start instruction (NO in S503), the WF engine proceeds to S504. In S504, the WF engine determines whether the received event is an end notification from the instance. In each instance, when the process in the instance ends, the end event is notified to the instance management of the WF engine.
If it is determined that it is not an instance termination notification (NO in S504), the WF engine proceeds to S506. In S506, the WF engine notifies the event to the instance. Here, the WF engine determines in which instance the received event is processed and notifies the appropriate instance of the event. On the other hand, if it is determined that the notification is an end notification from the instance (YES in S504), the WF engine proceeds to S505. In step S505, the WF engine determines whether all instances generated by the instance management of the WF engine have been completed. If there is an instance that has not ended yet (NO in S505), the WF engine returns to the process of S501. If all instances have been completed (YES in S505), the WF engine completes the process of the flowchart shown in FIG.
As described above, the WF engine generates and manages workflow instances.

FIG. 6 is a flowchart for explaining the flow of processing of a workflow instance. As described above, each instance is executed by the WF engine, but is executed as a separate process from the instance management flow of the WF engine.
First, in S601, the WF engine accepts the start of a workflow. In S507 of FIG. 5, the user receives a workflow instruction and receives a document to be processed in the workflow, which are notified when the execution is instructed as a separate process.
In step S <b> 602, the WF engine reads the workflow definition of the designated workflow from the HDD 304.
In step S603, the WF engine reads workflow tasks and actions included in the workflow tasks and executes them in order according to the workflow definition that has been read.
First, in step S <b> 604, the WF engine determines whether the read action is an action that instructs the MFP 101 to generate a scan execution button. If it is determined that the action is to instruct generation of a scan execution button (YES in S604), the WF engine proceeds to S605.
In step S605, the WF engine determines whether there are a plurality of instances that are currently being executed. If it is determined that the instance executing the workflow is only its own instance (NO in S605), the WF engine proceeds to S609.

On the other hand, if it is determined that there are a plurality of instances executing the workflow (YES in S605), the WF engine proceeds to S606. In S606, the WF engine acquires text information of the document being processed in each instance. The process of S606 is a process of extracting text information expressed as a character code from the document. The process of S606 may be a method of simply extracting text information from a file or a method of extracting text information by OCR or the like.
In step S <b> 607, the WF engine compares text information extracted from the document in each instance, and obtains difference text information. The processing in S607 may be a simple character string comparison, or a comparison considering font size, layout information, and the like.
When the text information that becomes the difference is acquired for the document in each instance, in step S608, the WF engine adds the text information that becomes the difference to the button display name of the scan execution button generated by the MFP in each instance. As a text information to be added, when there are a plurality of text information as differences, the WF engine may select any of them. In the present embodiment, it is assumed that the WF engine selects the one having the largest number of consecutive characters as a difference.

As an example, assume that there are two workflow instances and the text information extracted from the documents processed by each is as follows.
Instance 1:
“Purchase Request Application Form July 10, 2015 Development Department Ichiro Suzuki Product Name: USB Memory Unit Price: 2000 Yen Quantity: 1 Amount: 2000 Yen Remarks:”
Instance 2:
“Purchase Request Application Form July 11, 2015 Development Department Ichiro Suzuki Product Name: Security Software Unit Price: 10,000 Yen Quantity: 1 Unit Amount: 10,000 Yen Remarks:”
From here, the WF engine can obtain the difference between the text information by obtaining the minimum edit distance or the like between the text information. Here, the edit distance is a value indicating how different two character strings are. The edit distance is obtained based on how much editing such as insertion, replacement, and deletion is added to a certain character string to form another character string. When the editing distance is minimized, the part where the editing operation of insertion, replacement, and deletion is performed for each character string is obtained as the difference between the text information of both character strings. For example, when the minimum edit distance of the text information between the instance 1 and the instance 2 is obtained, when the edit portion is obtained from the front of the text information, “0” of “July 10” and “July 11” is set to “1”. The place to be replaced with "is first determined. Therefore, “0” and “1” are obtained as text information difference candidates. The WF engine repeats this to the rear of the text information, and extracts the text information difference when the number of editing operations is minimized. As described above, when the WF engine obtains the minimum edit distance between the text information, the difference between the text information is obtained as follows.
Instance 1:
“0”, “USB memory”, “2”, “2”
Instance 2:
“1”, “security software”, “10”, “10”
Among these, the character string “USB memory” is added to the scan execution button in the instance 1 flow, and the character string “security software” is added to the scan execution button in the instance 2 flow. In addition, the WF engine may select the one with the largest font size or the one located at the center of the document by using the layout information and the decoration information of the text information. The processing of S608 is an example of processing for determining text information to be displayed on each of a plurality of operation instruction objects related to the workflow.
In step S609, the WF engine instructs the MFP 101 to generate a scan execution button together with the text information determined in step S608.

FIG. 7 is a diagram illustrating an example of an operation screen displayed on the operation display unit 211 of the MFP 101 in step S609.
A screen 701 is a screen on which a user sets processing contents and setting values in advance and generates and displays a button for executing the processing. Normally, the user generates a button by setting from the operation unit screen of the MFP 101, but similarly generates a processing execution button on the screen 701 by instructing setting value data for button generation from the outside of the MFP 101. You can also.
Buttons 702 and 703 are buttons generated on the screen of the operation display unit 211 by the MFP 101 in response to the scan execution button generation instruction of the WF engine in step S <b> 609.
Here, the button 702 is a button generated in the execution of the workflow of the instance 1. A button 703 is a button generated in the execution of the workflow of the instance 2.
Text information 704 and 705 is difference information of the text information of the documents being processed in different instances, which is obtained earlier. Thus, the difference information of the text information of the document processed by both instances is displayed as text information on the scan execution button in each instance. Since the text information displayed on the button is obtained from the text information in the document to be scanned from now on, the text information displayed on the button is described in any one of the documents. This allows users to easily associate documents with buttons, and even when multiple instances of the same workflow are running, it is easy to determine which button to press to scan a document. Can be recognized.

After the scan execution button is generated in S609, in S610, the WF engine notifies the user of an e-mail containing a message prompting the MFP 101 to execute scan transmission. At this time, the WF engine attaches the document processed by the workflow instance and the text information displayed on the scan execution instruction button to the mail. As a result, the user who has received the e-mail can confirm which document should be pressed to execute scan transmission by confirming the attached content of the e-mail.
Thereafter, in S611, the WF engine reads the next action.
In step S612, the WF engine determines whether the read action is an action indicating the end of the workflow. If it is determined that the action is not an action indicating the end of the workflow (NO in S612), the WF engine returns to the process of S604. If it is determined that the action is a workflow end action (YES in S612), the WF engine proceeds to S613.
In step S613, the WF engine notifies the workflow instance end event, and ends the processing of the flowchart illustrated in FIG.

On the other hand, if it is determined that the action is not an action for instructing generation of a scan execution button (NO in S604), the WF engine proceeds to S614. In step S <b> 614, the WF engine determines whether the action is to wait for the user to perform a scan. If it is determined that it is a scan execution standby action (YES in S614), the WF engine proceeds to S615. In S615, the WF engine confirms reception of the file transmitted by the scan transmission. The process of S615 is a process of confirming whether a preset file has been generated in the folder set as the scan transmission destination. In addition, the WF engine inquires of the MFP 101 as to whether or not a job has been executed by pressing a button instructed to be generated by the WF engine, and determines whether or not the job has been executed based on the result of the inquiry. Good.
When the reception of the file is not confirmed (NO in S615), the WF engine repeats the process of S615. If the reception of the file is confirmed (YES in S615), the WF engine proceeds to S616. In step S616, the WF engine instructs the MFP 101 to delete the scan execution button. When the scan execution button is generated in S609, the WF engine passes an ID or the like that can uniquely identify the button as a part of the setting value, and instructs the ID in the deletion instruction to delete the corresponding button.
Thereafter, the WF engine performs the process of S611.
On the other hand, if it is determined that the action is not a scan execution standby action (NO in S614), the WF engine proceeds to S617. In S617, the WF engine actually executes processing related to the action. The process related to the action includes a print process to the MFP 101 and an approval process by the boss user, but a detailed description thereof is omitted.
Thereafter, the WF engine performs the process of S611 as before.

According to the above processing, when a plurality of workflow instances are executed at the same time, a scan execution button on which text information that can distinguish each workflow instance is displayed on the MFP is automatically generated. . The text information displayed on each button is differential text information extracted from the text information in the document processed by each instance. Therefore, the user can easily associate the scan execution button with the document to be processed by pressing it. In addition, since the combination of the document and the text information described in the scan execution button for processing the document is notified to the user by e-mail before executing the process, the user knows the combination before executing the process. Can do.
As a result, even when a plurality of workflow instances are executed at the same time, it is possible to prevent a mistake such as pressing a wrong scan execution button to scan a document, and to improve the operability of the MFP for the user.

(Modification 1)
In addition, when a plurality of workflow instances are executed, the WF engine converts each document into image data, obtains the difference between the image data, and then displays the difference image data on the scan execution button of the MFP. You may make it make it.
FIG. 8 is a flowchart for explaining the flow of processing of a workflow instance. Here, the processing from S801 to S805 is equivalent to the processing from S601 to S605 in FIG.
If it is determined that there are a plurality of instances executing the workflow (YES in S805), the WF engine proceeds to S806. In step S806, the WF engine converts the document being processed in each instance into image data. The conversion to image data includes a method of converting to raster data for printing using a printer driver. In addition, there is a method of generating image data for display display by a display application corresponding to the document format and capturing the image. The WF engine may convert the image data by any method.
In step S <b> 807, the WF engine compares image data generated from the documents in the respective workflow instances, and acquires difference information of the image data. There are several methods for acquiring difference information of image data. The WF engine removes noise, etc., and simply compares the data in units of pixels, or recursively divides the area using a quadtree and identifies the area of the image data that is different. Difference information may be acquired by a method.

FIG. 9 is a diagram illustrating an example of a document converted into image data in S806.
The image data 901 and the image data 902 in FIG. 9A are obtained by converting documents processed by different workflow instances into image data. Further, the image data 911 and the image data 912 in FIG. 9B are obtained by the WF engine comparing the two image data in S807 and reflecting the difference information of the images on the image data. In the example of FIG. 9, the WF engine expresses the difference between the image data by changing the background color of the area in the detected image difference from the original image. Difference areas of the image data 911 from the image data 912 are an area 913 and an area 915. Also, the difference areas of the image data 912 from the image data 911 are an area 914 and an area 916. A region 913 and a region 914, and a region 915 and a region 916 are difference regions detected as corresponding image differences.
In S808, the WF engine adds the difference data of the image data detected in S807 or part of the image data as image data to be displayed on the scan execution button generated by the MFP.
In step S809, the WF engine instructs the MFP 101 to generate a scan execution button together with the image data added in step S808.

FIG. 10 is a diagram illustrating an example of an operation screen displayed on the operation display unit 211 of the MFP 101 in step S809.
A screen 1001 is a screen for generating and displaying a button for executing processing by setting a processing content and a setting value in advance by the user, similarly to the screen 701 in FIG.
The scan execution buttons 1002 and 1003 in FIG. 10A are buttons generated on the screen of the operation display unit 211 by the MFP 101 in response to the scan execution button generation instruction of the WF engine in S809. As described above, the difference image data 1004 and 1005 of the document processed by the instance are displayed on both buttons.
The difference image data 1004 is a part of the data of the image difference area 915 detected by the image difference data extraction in S807. The difference image data 1004 is displayed on a scan execution button in a workflow instance that processes the document indicated by the image data 901.
Similarly, the difference image data 1005 is a part of the data of the image difference area 916 detected by the image difference data extraction in S807. The difference image data 1005 is displayed on a scan execution button in a workflow instance that processes the document indicated by the image data 902.
In this way, a part of the image data that can identify the document to be processed is displayed on the scan execution button in the instance of the workflow being executed.
Accordingly, the user can easily confirm which button corresponds to which document by comparing the document to be scanned with the image displayed on the scan execution button.

FIG. 10B is an operation screen displayed when the scan execution button 1002 is pressed in FIG.
When the scan execution button 1002 is pressed, a dialog 1011 is displayed on the screen. In the dialog 1011, a document image 1012 processed by the workflow instance related to the scan execution button 1002 is displayed. The document image 1012 is the image data generated in S806, and is transmitted to the MFP together with the scan execution button generation instruction in S809.
In the document image 1012, the image differences 1013 and 1014 detected when the image data is compared in S807 are highlighted by changing the background color. As a result, even if the difference image of the document displayed on the scan execution button is small and difficult for the user to discriminate, the entire document image actually processed by the button can be displayed on the entire screen of the operation display unit. . This makes it easier for the user to determine the correspondence between a document and a button that scans the document.
Further, since the difference between the document images is highlighted, it is possible to know which part of the document should be noticed and the user can easily identify the correspondence between the button and the document. Here, when there are a plurality of difference image data in the document, the WF engine may display any difference image data as the difference image data to be displayed on the scan execution button. For example, the WF engine selects the difference image data having the widest area among the plurality of difference image data, or selects the difference image data close to the center of the document, and displays the difference image data on the scan execution button. You may do it.
Further, the WF engine may change only a part of the document to image data and compare the difference between the image data without changing the entire document to image data.
Further, when image data is included in the document itself, the WF engine may compare the image data itself. However, the WF engine compares the image data included in the documents when the formats of the documents to be compared are the same and the position and area of the image data with respect to the documents are the same.

In S809, after a button for instructing execution of scanning is generated, in S810, the WF engine notifies the user of an e-mail that prompts the MFP 101 to execute scanning transmission. At this time, the WF engine attaches the document being processed in the workflow instance and the difference image data displayed on the scan execution instruction button to the mail. As a result, the user who has received the e-mail can confirm which button should be pressed to execute the scan by checking the attached content of the e-mail.
The subsequent processing from S811 to S817 is the same as the processing from S611 to S617, and thus the description thereof is omitted.

As described above, when a plurality of workflow instances are simultaneously executed, a scan execution button on which image data capable of distinguishing each workflow instance is displayed on the MFP is automatically generated.
In addition, the WF engine converts a document processed by each instance into image data and compares the difference. For this reason, even when the document does not have text information such as a character code, the difference information that can be identified by the user can be displayed on the button processed by each instance. The image data displayed on the button is the image difference of the document processed by each instance. By comparing the image on the button with the document, the user can determine which button is to process which document. Can be easily identified. Further, since the combination of the document and the image data displayed on the scan execution button for processing the document is notified to the user by e-mail or the like before executing the process, the user knows the combination before executing the process. be able to.
As a result, even when a plurality of workflow instances are executed at the same time, it is possible to prevent a mistake such as pressing a wrong scan execution button to scan a document, and to improve the operability of the MFP for the user.

(Modification 2)
When a plurality of workflow instances are executed, the workflow system may add an identifier that can uniquely identify the instance in the document printing of each instance and print the instance. The workflow system may display the identifier on the scan execution button of the MFP.
FIG. 11 is a flowchart for explaining the flow of processing of a workflow instance. Here, the processing from S1101 to S1103 is equivalent to the processing from S601 to S603 in FIG.
After the processing of S1103, in S1104, the WF engine determines whether or not the read action is an action for printing a document to the MFP 101. That is, the WF engine determines whether or not the document print action is included in the flow process 402 of FIG.
If it is determined that it is a document printing action (YES in S1104), the WF engine proceeds to S1105. In step S1105, the WF engine determines whether there are multiple instances that are currently being executed. If it is determined that the instance executing the workflow is only its own instance (NO in S1105), the WF engine proceeds to S1107.
If it is determined that there are a plurality of instances executing the workflow (YES in S1105), the WF engine proceeds to S1106. In step S1106, the WF engine generates an identifier that can uniquely identify each instance, and adds the identifier to the print document. Here, the identifier may be anything such as a number, alphabet, or a combination thereof as long as the instance can be uniquely identified. It may be a figure or mark as long as it can be identified by the user. The identifier is fixedly added at a position such as a document header or footer that does not overlap the contents of the original document.
In addition, since the WF engine adds the generated identifier to the document, the WF engine does not compare the documents in different instances. For this reason, the WF engine may always perform the processing of S1106 without confirming the existence of another instance of S1105.
In step S1107, the WF engine instructs the MFP to print the document processed by the workflow instance. The process of S1107 is an example of a print instruction.

FIG. 12 is a diagram illustrating an example of a document printed in step S1107 when a plurality of workflow instances are executed.
Document 1201 and document 1202 are examples of documents that are executing the same workflow but are processed in different instances. Although the workflow is to process the same application form, the contents of the application form are different.
Here, identifiers 1203 and 1204 are identifiers generated in S1106, and are added to the document and printed in S1107.
In this way, an identifier that can be recognized by the user, such as alphanumeric characters, is added to the corner of the document and printed.
Thereafter, in S1108, the WF engine reads the next action. The processing from S1108 to S1110 is equivalent to the processing from S611 to S613 in FIG.

If it is determined that the read action is not an action for printing a document (NO in S1104), the WF engine proceeds to S1111. In step S1111, the WF engine determines whether the action is an action for instructing the MFP 101 to generate a scan execution button.
If it is determined that the action is an instruction to generate a scan execution button (YES in S1111), the WF engine proceeds to S1112. In step S1112, the WF engine adds the identifier generated in step S1106 to the button name for display on the scan execution button.
Thereafter, in step S1113, the WF engine instructs the MFP 101 to generate a scan execution button together with the identifier information added in step S1112.
FIG. 13 is a diagram illustrating an example of an operation screen displayed on the operation display unit 211 of the MFP 101 in step S1113.
A screen 1301 is a screen for generating and displaying a button for executing processing in advance by setting the processing contents and setting values in advance by the user, as in 701 of FIG.
Buttons 1302 and 1303 are buttons generated by the MFP 101 on the screen of the operation display unit 211 in response to the scan execution button generation instruction of the WF engine in S1113.
In this way, identifiers 1304 and 1305 that can uniquely identify instances are displayed on both buttons. The identifiers 1304 and 1305 are generated by the processing of S1106 in each instance, and are the same as the identifiers 1203 and 1204 added at the time of document printing in FIG. That is, an identifier is printed on a document processed by each instance, and the same identifier is displayed on a scan execution button for scanning the document.
Thus, the user can easily identify which document should be scanned by which scan execution button by confirming that the identifiers are the same.

In S1113, after a button for instructing scan execution is generated, in S1114, the WF engine notifies the user of an e-mail that prompts the MFP 101 to execute scan transmission. At this time, the WF engine attaches the document being processed in the workflow instance and the identifier information assigned to the instance to the mail.
As a result, the user who received the e-mail can confirm which of the same identifier is displayed by confirming the contents attached to the e-mail, and press which button for which document to execute scan transmission. I know what to do.
Thereafter, the WF engine executes the process of step 1108.
On the other hand, if it is determined that the action is not a scan execution button generation instruction action (NO in S1111), the WF engine proceeds to S1115. In step S <b> 1115, the WF engine determines whether the read action is an action waiting for the user to perform scan execution.
The processing from S1115 to S1118 is equivalent to the processing from S614 to S617 in FIG.

As described above, according to the process shown in FIG. 11, when a plurality of workflow instances are simultaneously executed, an identifier for specifying the instance is printed on the document, and an identifier corresponding to the document is displayed on the MFP. A scan execution button is generated. For this reason, even if the difference between the text information and image data of the document in each instance is small and it is difficult for the user to recognize the difference even if the difference information is displayed, the user associates the document with a button for scanning the document. Can be easily performed. In addition, since the identifier displayed on the document and the scan execution button for processing the document is notified to the user by e-mail or the like before executing the process, the user can know the combination before executing the process.
As a result, even when a plurality of workflow instances are executed at the same time, it is possible to prevent a mistake such as pressing a wrong scan execution button to scan a document, and to improve the operability of the MFP for the user.

(Modification 3)
In this modification, when a plurality of workflow instances are executed, after a scan execution button is generated in one instance, execution of document printing in another instance is made to wait until the scan is executed by pressing the button.
A difference from Modification 2 will be described.
FIG. 14 is a flowchart for explaining the flow of processing of a workflow instance. Here, the processing from S1401 to S1404 is equivalent to the processing from S1101 to S1104 in FIG.
If it is determined that the action is an instruction to instruct printing of the document (YES in S1404), the WF engine proceeds to S1405. In step S1405, the WF engine determines whether there is a workflow instance that is currently in a scan wait state. That is, whether there is a workflow instance in the state after the document printing action is executed and the scan transmission is actually executed by the user's instruction through the scan execution button until the scan effective button is deleted. Judge whether. If it is determined that there is no workflow instance in the scan waiting state (NO in S1405), the WF engine proceeds to S1408.
If it is determined that there is another workflow instance waiting for scanning (YES in step S1405), the WF engine proceeds to step S1406. In S1406, the WF engine waits for execution of another workflow instance. The processing of S1405 and S1406 is an example of standby processing.

In step S1407, the WF engine determines whether scan transmission in another workflow instance has been executed. For example, the WF engine determines whether or not scan transmission in another workflow instance has been executed by a method such as periodically polling to determine the state of the workflow instance.
If it is determined that scan transmission in another workflow instance has not been executed (NO in step S1407), the WF engine returns to the processing in step S1406 and waits for execution of another workflow instance.
If it is determined that scan transmission in another workflow instance has been executed (YES in S1407), the WF engine proceeds to S1408. In step S <b> 1408, the WF engine instructs the MFP 101 to print a document processed by its own workflow instance.
Thereafter, the WF engine reads the next action in S1409, but the processing from S1409 to S1411 is equivalent to the processing from S1108 to S1110 in FIG.
If it is determined that the read action is not an action for printing a document (NO in S1404), the WF engine proceeds to S1412. In step S <b> 1412, the WF engine determines whether the action is an action for instructing the MFP 101 to generate a scan execution button.

If it is determined that the action is an action for instructing generation of a scan execution button (YES in S1412), the WF engine proceeds to S1413. In step S1413, the WF engine instructs the MFP 101 to generate a scan execution button. At that time, the WF engine does not particularly add information for specifying the workflow instance on the button. However, even when a plurality of workflow instances are executed, while the scan execution button is generated in one instance, the processing of the other instances is in a state before the document is executed. For this reason, only one scan execution button is displayed on the MFP. Since the printing of the document is executed only in one instance, there is only one set of the printed document and the scan execution button, and the user can easily determine the association.
In step S1413, after a button for instructing scan execution is generated, in step S1414, the WF engine notifies the user of an e-mail that prompts the MFP 101 to execute scan transmission. Also at this time, the WF engine does not attach information that associates the document with the scan execution button to the mail. However, as described above, the user can easily identify the relationship.
Thereafter, the WF engine executes the process of step 1409.
If it is determined that the action is not a scan execution button generation instruction action (NO in S1412), the WF engine proceeds to S1415. In step S1415, the WF engine determines whether the read action is an action waiting for scanning.
The processing from S1415 to S1418 is the same as the processing from S1115 to S1118 in FIG.

As described above, when a plurality of workflow instances are simultaneously executed, a document is printed and a scan execution button is generated, and there is always only one workflow instance waiting for scan transmission execution. Other workflow instances wait in a state before execution of an action for printing a document. For this reason, there is always only one set of a document that is actually printed and a scan execution button, and the user can easily perform the association.
As a result, even when a plurality of workflow instances are executed at the same time, it is possible to prevent a mistake such as pressing a wrong scan execution button to scan a document, and to improve the operability of the MFP for the user.

<Other embodiments>
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium. It can also be realized by a process in which one or more processors in the computer of the system or apparatus read and execute the program. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

  As mentioned above, although preferable embodiment of this invention was explained in full detail, this invention is not limited to the specific embodiment which concerns. In the embodiment described above, the WF engine has been described using an example mounted on a server. However, the WF engine may be mounted on one of the MFPs that collectively manage the workflow. Further, the hardware configuration of the WF server 102 is not limited to that shown in FIG. 3, and the WF server 102 may include a plurality of CPUs 301, a network I / F 305, and the like.

  As described above, according to the processing of the above-described embodiment, it is possible to provide a technique for improving the operability related to the selection of the operation instruction object related to the workflow and reducing the pressing mistake of the operation instruction object.

101 MFP
102 WF server 301 CPU

Claims (17)

An acquisition means for acquiring text information of a plurality of documents related to the workflow;
Determining means for determining text information to be displayed on each of the plurality of operation instruction objects related to the workflow based on the difference between the plurality of text information acquired by the acquiring means;
Generation instruction means for designating text information to be displayed on the operation instruction object determined by the determination means, and instructing the image processing apparatus to generate the operation instruction object;
An information processing apparatus.   2. The transmission device according to claim 1, further comprising: a transmission unit configured to transmit a message for prompting an operation instruction via the operation instruction object including the document and text information to be displayed on the operation instruction object to a user who performs the operation instruction. Information processing device. Acquisition means for acquiring image data of a plurality of documents related to the workflow;
Determining means for determining image data to be displayed on each of the plurality of operation instruction objects related to the workflow based on the difference between the plurality of image data acquired by the acquiring means;
Generation instruction means for designating image data to be displayed on the operation instruction object determined by the determination means and instructing an image processing apparatus to generate the operation instruction object;
An information processing apparatus.   4. The transmission device according to claim 3, further comprising: a transmission unit configured to transmit a message for prompting an operation instruction via the operation instruction object including the document and image data to be displayed on the operation instruction object to a user who performs the operation instruction. Information processing device. Generating means for generating an identifier for identifying a document related to the workflow;
Print instruction means for instructing an image processing apparatus to print the document including the identifier generated by the generation means;
A generation instruction unit that specifies an identifier generated by the generation unit as information to be displayed on an operation instruction object related to the document, and that instructs the image processing apparatus to generate the operation instruction object;
An information processing apparatus.   The information processing apparatus according to claim 5, further comprising: a transmission unit configured to transmit a message for prompting an operation instruction via the operation instruction object including the document and the identifier to a user who performs the operation instruction. If there is another instance that is waiting for scanning, a waiting unit that waits for processing of the other instance;
A print instruction means for instructing the image processing apparatus to print a document relating to the workflow when the processing of the other instance is completed;
Generation instruction means for instructing the image processing apparatus to generate an operation instruction object related to the document;
An information processing apparatus.   The information processing apparatus according to claim 1, further comprising a deletion instruction unit that instructs the image processing apparatus to delete the operation instruction object.   The information processing apparatus according to claim 1, wherein the operation instruction object is a scan execution button. Generating means for generating the operation instruction object displaying the text information based on an instruction for generating an operation instruction object related to a workflow, which specifies text information to be displayed on the operation instruction object;
Display means for displaying the operation instruction object displaying the text information on an operation screen of an image processing apparatus;
Having a system. Generating means for generating the operation instruction object displaying the image data based on an instruction to generate the operation instruction object related to the workflow, which specifies image data to be displayed on the operation instruction object;
Display means for displaying the operation instruction object displaying the image data on an operation screen of an image processing apparatus;
Having a system. Printing means for printing the document displaying the identifier based on an instruction to print the document, specifying an identifier for identifying the document;
Generating means for generating the operation instruction object displaying the identifier based on an instruction to generate an operation instruction object related to the workflow, which specifies the identifier;
Display means for displaying the operation instruction object displaying the identifier on an operation screen of an image processing apparatus;
Having a system. An information processing method executed by an information processing apparatus,
An acquisition step for acquiring text information of a plurality of documents related to the workflow;
A determination step for determining text information to be displayed on each of the plurality of operation instruction objects related to the workflow based on the difference between the plurality of text information acquired by the acquisition step;
A generation instruction step of designating text information to be displayed on the operation instruction object determined in the determination step, and instructing an image processing apparatus to generate the operation instruction object;
An information processing method including: An information processing method executed by an information processing apparatus,
An acquisition step of acquiring image data of a plurality of documents related to the workflow;
A determination step of determining image data to be displayed on each of the plurality of operation instruction objects related to the workflow based on the difference between the plurality of image data acquired in the acquisition step;
A generation instruction step for designating image data to be displayed on the operation instruction object determined in the determination step, and instructing an image processing apparatus to generate the operation instruction object;
An information processing method including: An information processing method executed by an information processing apparatus,
A generating step for generating an identifier for identifying a document related to the workflow;
A print instruction step for instructing an image processing apparatus to print the document including the identifier generated by the generation step;
A generation instruction step that specifies the identifier generated by the generation step as information to be displayed on the operation instruction object related to the document, and instructs the image processing apparatus to generate the operation instruction object;
An information processing method including: An information processing method executed by an information processing apparatus,
If there is another instance waiting to be scanned, a waiting step for waiting for processing of the other instance;
A print instruction step for instructing the image processing apparatus to print a document related to the workflow when the processing of the other instance is completed;
A generation instruction step for instructing the image processing apparatus to generate an operation instruction object related to the document;
An information processing method including:   A program for causing a computer to function as each unit of the information processing apparatus according to any one of claims 1 to 9.

Images