JP2020027472A - Workflow support device, workflow execution device, workflow system, workflow support method, workflow execution method, and program - Google Patents

Abstract

To provide a workflow support device and others that enable a user to easily select a desired workflow irrespective of whether the user logs in or not, in an information device such as an MFP.SOLUTION: A workflow support device, which generates information for executing an operation performed by a user by logging in to the first device as a workflow on a second device, includes: acquisition means that acquires the user operation log; determination means that analyzes the acquired operation log and determines an operation related to the second device as a plurality of tasks constituting a workflow; generation means that generates a file describing an operation definition for displaying a button for instructing execution of a workflow composed of the plurality of determined tasks on a UI screen of the second device; and distribution means that distributes the generated file to the second device, in which the file includes at least information for specifying the plurality of tasks and a classification parameter for classifying and displaying buttons on the UI screen.SELECTED DRAWING: Figure 4

Description

  The present invention relates to a technology that facilitates execution of a workflow.

  For many tasks performed in a company, a plurality of information devices such as a PC (Personal Computer) and an MFP (Multi Function Printer) are used. In the business, there are a plurality of steps (tasks) such as digitizing a paper manuscript such as a contract with a scanning function of the MFP and transferring the obtained scan file data to a PC or a server for storage. Many are included. In addition, such a task often involves a plurality of systems such as a management system and an approval system. For this reason, the execution procedure of a plurality of tasks constituting a task is complicated. Therefore, in order to easily and efficiently perform a series of complicated tasks, a workflow system has been proposed in which execution procedures of a plurality of tasks are integrated into one.

  In the above-mentioned workflow system, the execution start button is generally displayed on an operation screen of an information device such as a PC or an MFP. For example, Patent Document 1 discloses an MFP that allows a login user to display a list of workflows registered in association with the user and select a desired workflow. Patent Literature 1 also describes that when a search button is pressed, a workflow related to another user of the group to which the login user belongs can be searched.

JP 2010-198430 A

  In the technique of Patent Document 1, first, a workflow directly associated with a user who has logged in to the MFP is displayed in a list, and when a search button is pressed, the workflow associated with another user belonging to the same group as the login user is displayed. The workflow to be performed is displayed. That is, Patent Literature 1 is a technique on the assumption that a user logs in to the MFP. Therefore, when the user uses the MFP without logging in, the user ID cannot be obtained, and all the workflows registered in the MFP are displayed in a list. That is, in the technique of Patent Document 1, a user who wants to use the MFP without logging in cannot enjoy the advantage, and it takes time to search for a desired workflow.

  A workflow support device according to the present invention is a workflow support device that generates information for executing an operation performed by a user logged in on a first device as a workflow on a second device, Acquiring means for acquiring an operation log; determining means for analyzing the acquired operation log to determine an operation related to the second device as a plurality of tasks constituting a workflow; and the determined plurality of tasks. Generating means for generating a file in which an operation definition for displaying a button for instructing execution of the workflow on the UI screen of the second device is described; Distribution means for distributing the information to the device, wherein the file includes information for specifying the plurality of tasks, and the buttons are classified on the UI screen. A classification parameter for display is included at least, characterized in that.

  According to the present invention, in an information device such as an MFP, a user can easily select a desired workflow regardless of whether or not the user logs in.

(A) and (b) are diagrams showing an example of the configuration of a business system FIG. 2A is a diagram illustrating a main hardware configuration of an MFP, and FIG. 2B is a diagram illustrating a main hardware configuration of a client terminal and a workflow support device. FIG. 2A is a diagram illustrating a main software configuration of an MFP, and FIG. 2B is a diagram illustrating a main software configuration of a workflow support apparatus. 5 is a flowchart showing a flow from when the workflow support apparatus analyzes a PC operation log and generates a WF definition file according to the first embodiment. 5 is a flowchart showing a flow of displaying a WF button on a UI screen based on a WF definition file in the MFP. (A) is a diagram showing an example of a UI screen in a login unnecessary mode, and (b) is a diagram showing an example of a UI screen in a my flow mode. 9 is a flowchart showing a flow from when the workflow support apparatus analyzes a PC operation log and generates a WF definition file according to the second embodiment. (A) and (b) are diagrams showing an example of a UI screen in a login unnecessary mode. 9 is a flowchart showing a flow from when the workflow support apparatus analyzes a PC operation log and generates a WF definition file according to the third embodiment. A diagram illustrating an example of a UI screen in a login unnecessary mode.

  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.

Embodiment 1

  FIGS. 1A and 1B are diagrams illustrating an example of the configuration of a business system according to the present embodiment. The business system 100 shown in FIG. 1A is composed of three types of information devices: an MFP 101, client PCs 102a / 102b, and a workflow support device 103. The MFP 101 is a so-called multifunction peripheral having various functions related to document processing such as scanning and printing, and has a role as a workflow execution device. The "client PCs" 102a and 102b are information devices as user terminals on which applications necessary for business execution are installed, and may be tablets, for example. The workflow support device 103 is an information device serving as a dedicated terminal for the SE or the administrator to collectively create and manage workflows for a plurality of users, and is, for example, a server computer. The information devices are mutually connected via the network 104, and can exchange information with each other.

  A business system 100 ′ shown in FIG. 1B includes an MFP 101 and one client PC 102. This is an aspect in which the workflow support device 103 is integrated with the client PC 102, and the client PC 102 has the following functions of the workflow support device 103. The system configuration in FIG. 1B assumes a case where each user himself creates his or her own workflow. In the following, the description will focus on the case of FIG. 1A, and will refer to the case of FIG. 1B as necessary. In the case of FIG. 1A, there is no need to distinguish between the client PCs 102a and 102b.

[Hardware configuration]
Next, the hardware configuration of each information device that configures the business system 100 will be described. FIG. 2A illustrates a main hardware configuration of the MFP 101, and FIG. 2B illustrates a main hardware configuration of the client PC 102 and the workflow support apparatus 103, respectively.

  As illustrated in FIG. 2A, the MFP 101 includes an arithmetic unit 201, a storage unit 202, a display unit 203, an operation unit 204, a communication unit 205, a printer unit 206, and a scanner unit 207. The operation unit 201 is realized by, for example, a CPU, a GPU, or the like, and controls various units in the MFP 100 by executing various programs. The storage unit 202 is realized by, for example, a RAM, a ROM, an HDD, and the like, and stores various programs and data executed by the arithmetic unit 201. The operation unit 203 is realized by, for example, a mouse, a keyboard, and the like, and receives various operations by a user. The display unit 204 is realized by, for example, a liquid crystal display or the like, and displays various information to a user. Note that the touch panel display may serve as both the operation unit 203 and the display unit 204. The communication unit 205 is a network interface that transmits and receives various information to and from other devices on the network 104. The printer unit 206 prints and outputs image data input from the client PC 102 or the like on a recording medium such as paper using, for example, an electrophotographic method or an inkjet method. The scanner unit 207 optically reads a document set on a document table (not shown) or an ADF (Auto Document Feeder) and converts the document into image data.

  As illustrated in FIG. 2B, the client PC 102 and the workflow support device 103 include an arithmetic unit 211, a storage unit 212, an operation unit 213, a display unit 214, and a communication unit 215. These units correspond to the arithmetic unit 201, the storage unit 202, the display unit 203, the operation unit 204, and the communication unit 205 of the MFP 101, respectively, and there is no particular difference.

[Software Configuration]
Next, the software configuration of each information device constituting the business system will be described. 3A illustrates a main software configuration of the MFP 101, and FIG. 3B illustrates a main software configuration of the workflow support apparatus 103. In the following description, “WF” means a workflow.

  As illustrated in FIG. 3A, the MFP 101 includes a main control module 301, a UI control module 302, and a WF control module 303. The WF control module 303 includes a WF button generation module 304 as a sub module. The main control module 301 issues instructions and management to each module. The UI control module 302 generates a user interface screen (UI screen) for the user to input various operations and displays the user interface screen on the display unit 204. The WF control module 303 controls overall processing related to the workflow, such as registration and execution of the workflow, according to an instruction from the main control module 301. The WF button generation module 304 generates a button (hereinafter, referred to as a “WF button”) for instructing a user to execute a desired workflow on the UI screen based on information transmitted from the workflow support apparatus 103. I do.

  As shown in FIG. 3B, the workflow support device 103 includes a WF creation module 311, a WF management module 312, and a WF definition file distribution module 313. The workflow creation module 311 creates a workflow by converting each procedure of a task performed by each user into a task. Here, for example, when the task includes a task of "scanning a document, transferring image data obtained by scanning, and printing out with a destination printer", "scan document", "scan image" Refers to elements that are delimited in units such as "transfer" and "print at destination". The workflow is composed of a series of such tasks. A task has a plurality of setting items, and a parameter is set for each item. For example, the setting items in the case of the task “scan original” correspond to “reading resolution”, “color setting”, “page setting”, “destination”, and the like. The parameter in “color setting” is “color”. Alternatively, it corresponds to an actual applied value such as “gray scale”. The WF management module 312 manages the workflow created by the WF creation module 311 and parameters set for each task constituting the workflow. The WF definition file distribution module 313 distributes a data file (hereinafter, referred to as a “WF definition file”) describing the workflow operation definition created by the WF creation module 311 to the MFP 101.

  In the system configuration of FIG. 1B in which the client PC 102 also has the function of the workflow support device 103, it is assumed that applications realizing the above three modules 311 to 313 are installed in the client PC 102.

[Generation of WF definition file]
FIG. 4 is a flowchart showing a flow until the workflow support apparatus 103 according to the present embodiment analyzes an operation log (hereinafter, referred to as “PC operation log”) of the client PC 102 and generates a WF definition file. is there. This flow is realized by the arithmetic unit 211 executing a predetermined program stored in the storage unit 212 in response to an execution instruction from an operator such as an administrator to the workflow support apparatus 103. Hereinafter, description will be given along the flow of FIG. The symbol “S” at the beginning of each process means a step.

  In step S <b> 401, the WF creation module 311 acquires a predetermined range of PC operation logs from the client terminal 102. Here, the predetermined range refers to a time range such as the past one day, for example, and a specific acquisition target period is specified by, for example, an operator. In the present embodiment, each client PC 102 is associated with a user on a one-to-one basis, and it is assumed that a plurality of users do not log in and use the same client PC 102 jointly. Table 1 below shows an example of an operation log of the client PC 102 used by a specific user (user name: Yuji).

  In Table 1 above, the column of the event name describes the content operated by the user "Yuji" on the client PC 102, and shows three "login", "mail reception", and "data duplication". . In the column of “date and time”, information on the date and time when the target event was performed is described. In “variable 1” to “variable 3”, detailed information for specifying details of the target event is described. Now, as for the event name “login”, the user name “Yuji” for identifying the logged-in user is shown in variable 1, and the device name “PC1” for identifying the client PC 102 that made the login is shown in variable 3. . The event name “mail reception” indicates that the scan image data sent by the SEND function of the MFP 101 has been received by mail. The variable 1 indicates the mail address “yuji@mail.mfp1” indicating that the MFP 101 is the transmission source, and the variable 2 indicates the file name “180529_01.pdf” of the transmitted scan image data. It is shown. As for the event name “data duplication”, the file path “C: \ attach180529_01.pdf” of the duplication source is indicated in the variable 1. The file path “\\ sample.net \ A company” of the copy destination is shown in variable 2 and its file name “contract.pdf” is shown in variable 3. It is assumed that a series of actions performed by the specific user on the client PC 102 are acquired from the client PC 102 as a PC operation log. The file format of the PC operation log is arbitrary.

  In S402, the WF creation module 311 extracts the operation content (task) described in the event name of the PC operation log acquired in S401. In the case of the PC operation log in Table 1 described above, three “login”, “mail reception”, and “data duplication” are extracted.

  In step S403, the WF creation module 311 analyzes the tasks extracted in step S402, and determines a task configuring a workflow based on the relevance of the tasks. From the PC operation log in Table 1 above, it can be seen that data replication has been performed after receiving the mail for the same file “180529_01.pdf”. Based on the analysis result, a task constituting a workflow executed by the MFP 101 is determined. In the above-described example, “document reading” is determined as the first task and “transfer (SMB transmission)” is determined as the next task in the time series of the extracted operation contents. This determination is made, for example, by referring to a table in which operations related to the MFP 101 among tasks extracted from the PC operation log are associated with tasks in the workflow. Alternatively, it is determined according to an algorithm for converting a task in the PC operation log into a task in the workflow.

  In S404, the WF creation module 311 extracts a PC login user name from the “login” task extracted in S402. The PC login user name is held as character string information on the PC operation log. In the case of the PC operation log shown in Table 1, the character string information of the variable 1 “Yuji” is extracted.

  In S405, the WF creation module 311 creates a WF definition file for creating a WF button according to the task determined in S403. Table 2 below is an example of a WF definition file according to the present embodiment.

  In Table 2 above, the identifier column indicates the type of the identifier name, the identifier “parameter” indicates information about the WF button, and the identifier “task” indicates the content of processing executed according to the WF button. Here, the identifier name “classification parameter” is information for classifying the WF button on the MFP 101, and the value of the parameter of the identifier name having the same character string as the value of “classification parameter” is used as the classification information. It indicates that you want to. The value of the “classification parameter” is set only when the login function of the MFP 101 is invalid, and is not set when the login function is valid. Here, when the login function is valid, it means an operation mode in which the MFP 101 cannot be used without logging in, and when the login function is invalid, it means an operation mode in which the MFP 101 can be used without logging in. In which operation mode an information device that executes a workflow such as the MFP 101 is to be used is usually considered to be determined in units of groups or offices. In the present embodiment, the WF definition file is generated in consideration of such usage of the MFP 101. In Table 2 above, the value of the “classification parameter” is “PC login user name”. Then, the value of “PC login user name” is “Yuji” (set in S409 described later). Therefore, the user name “Yuji” is associated with the WF button. The “WF button name” is information for identifying the WF button on the UI screen of the MFP 101, and its value is “contract”. As described above, a character string extracted from the PC operation log (for example, a file name included in the “data duplication” task) may be adopted as the value of the identifier name “WF button name”, or the user may use a specific character string. May be input from the UI and set. The generated WF definition file is stored in the storage unit 212 by the WF management module 312.

  In S406, the WF creation module 311 executes the WF definition file generated in S405 from the “mail reception” task among the tasks extracted in S402, and sets the information device (hereinafter referred to as “WF execution device”). Get address information. In the case of the present embodiment, the IP address and the domain name of the MFP 101 are acquired as the address information using the source address of the “received mail” task extracted in S402. Specifically, for example, it is acquired by referring to a CSV format data file in which the mail address and the IP address of each MFP are associated with each other as “usera @ mail.mfp1,192.168.18.1”.

  In S407, the WF creation module 311 accesses the MFP 101 as the WF execution device using the address information acquired in S406, and acquires login setting information indicating whether the login function of the MFP 101 is valid or invalid. This login setting information may be acquired from the MIB (Management Information Base) of the MFP 101 using, for example, SNMP (Simple Network Management Protocol).

  In S408, the next step to be executed is assigned based on the login setting information acquired in S407. Specifically, it is determined whether to set the value of the “classification parameter” described above. If the login function is invalid, the process proceeds to S409 to set the value of the "classification parameter". On the other hand, if the login function is valid, the process proceeds to S410 to skip setting the value of the “classification parameter”.

  In step S409, the WF creation module 311 reads out the WF definition file generated in step S405 via the WF management module 312, and sets the “PC login user name” extracted in step S404 as the value of the identifier name “classification parameter”. . The WF definition file after the setting is stored in the storage unit 212 by the WF management module 312 again.

  In S410, the WF definition file distribution module 313 reads out the WF definition file via the WF management module 312, and transmits the file to the MFP 101 as the WF execution device. The MFP 101 receives the WF definition file via the communication unit 205 and stores the WF definition file in the storage unit 202.

  The above is the content of the process of generating the WF definition file based on the analysis result of the PC operation log in the workflow support device 103.

[Generation of WF button]
FIG. 5 is a flowchart illustrating a flow until the MFP 101 displays a WF button on the UI screen based on the WF definition file received from the workflow support device 103 according to the present embodiment. This flow is realized by the arithmetic unit 201 executing a predetermined program stored in the storage unit 202 in response to an execution instruction from an administrator or a specific user who has generated the WF definition file. Hereinafter, a description will be given along the flow of FIG. 5 assuming that the execution instruction has been issued by the specific user (user name: “Yuji”) corresponding to the WF definition file in Table 2 described above. The symbol “S” at the beginning of each process means a step.

  In step S501, the WF control module 303 reads the WF definition file distributed from the workflow support device 103 from the storage unit 202 and acquires the WF definition file. The obtained WF definition file is passed to the WF button generation module 304.

  In S502, the WF button generation module 304 generates a WF button based on the WF definition file. Specifically, a WF button icon (thumbnail image) to be displayed on the UI screen of the display unit 204 and a program (a task group constituting a workflow and an instruction group defining an execution order thereof) associated with the icon are generated. Will be done. In the case of Table 2 described above, a program that specifies that the task of “document reading” is executed first, and then the task of “SMB transmission” is specified, and a button icon for instructing the user to start the execution is a button icon. Will be generated. The generated data of the WF button is stored in the storage unit 202.

  In step S <b> 503, the WF control module 303 determines whether the login function of the MFP 101 is enabled or disabled. If the login function is valid, in step S511, the WF control module 303 sets the display mode of the UI screen related to the workflow to the my flow mode. FIG. 6B shows an example of a UI screen in the my flow mode. The UI screen 610 under the My Flow mode has a mode information display area 611 and a WF button selection area 612. In subsequent S512, the WF control module 303 acquires the information of the login user of the MFP 101, and after the acquisition, proceeds to S513. On the other hand, if the login function is invalid, the process proceeds to S504.

  In step S504, the WF control module 303 sets the display mode of the UI screen related to the workflow to the login unnecessary mode. FIG. 6A shows an example of a UI screen in the login unnecessary mode. The UI screen 600 in the login unnecessary mode includes a mode information display area 601, a classification selection area 602, and a WF button selection area 603. The display format is not limited to the list format, but may be a drop-down format or a tree format.

  In step S505, the WF button generation module 304 refers to the WF definition file and determines whether or not there is a value of the identifier name “classification parameter”. If there is a value of “classification parameter”, the process proceeds to S506; otherwise, the process proceeds to S510.

  In S506, the WF button generation module 304 specifies an identifier name having the same content as the value of the “classification parameter”, and acquires the value as the classification information. In the case of Table 2, as described above, the value of the “classification parameter” is “PC login user name”. Therefore, "Yuji" which is the value of the identifier name "PC login user name" is obtained.

  In step S507, the WF button generation module 304 determines whether the same content as the classification information acquired in step S506 already exists in the classification selection area 602. If the same content as the acquired classification information does not already exist in the classification selection area 602, the process proceeds to S508; otherwise, the process proceeds to S509.

  In step S <b> 508, the WF button generation module 304 adds the classification information acquired in step S <b> 506 to the items displayed in the list so as to be displayed in the classification selection area 601. In the case of Table 2 above, “Yuji” acquired as the classification information is added as an item to be displayed in a list.

  In S509, the WF button generation module 304 associates the WF button (button icon + program) generated in S502 with the item (here, “Yuji”) added in S508 and the [ALL] item. Upon completion of the association, the process proceeds to S513. In S510, the WF button generation module 304 associates the WF button (button icon + program) generated in S502 with the [ALL] item. Upon completion of the association, the process proceeds to S513.

  In step S513, the WF control module 303 instructs the UI control module 302 to generate and display the UI screen in the content of the display mode set in step S504 or S511. In response to this, the UI control module 302 displays a UI screen related to the workflow on the display unit 204 in the indicated display mode.

  In the case of the login unnecessary mode, as shown in FIG. 6A, a name and the like for identifying a user are displayed in a list in the category selection area 602. In the WF button selection area 603, an icon of a WF button associated with an item selected from the item group displayed in the category selection area 602 is displayed. In FIG. 6A, “Yuji” is selected in the classification selection area 602, and two icons “contract” and “quotation” associated with this “Yuji” are displayed in the WF button selection area 603. It has been done. In this case, the icon of “contract” is the icon added in S508, and the icon of “quotation” indicates the icon already associated with “Yuji” at the time of addition in S508.

  On the other hand, in the case of the My Flow mode, the WF button is searched using the login user information acquired in S512 as a search key, and the WF button corresponding to the user who is logging in to the MFP 101 is displayed in the WF button selection area 612. become. In the example of FIG. 6B, two icons “contract” and “quotation” associated with the login user “Yuji” are displayed in the WF button selection area 612.

  The above is the content of the process of displaying the WF button corresponding to the specific user on the UI screen based on the WF definition file received from the workflow support device 103 in the MFP 101.

  According to the present embodiment, when the login function of an apparatus such as an MFP that executes a workflow is disabled, a button for instructing execution of the workflow is displayed on the UI screen in user units in association with the user. Therefore, the user can easily select a desired workflow without logging in.

Embodiment 2

  In the first embodiment, the PC login user name is used as the classification information on the assumption that each client PC 102 is associated with the user on a one-to-one basis. However, for example, there is an environment in which a plurality of users use different client PCs by using a common PC login user name. In such a usage environment, even if the PC login user name is used as the classification information, the workflow related to each user cannot be classified and displayed. Accordingly, a second embodiment will be described as a second embodiment in which the name “client device name” for identifying each client PC is used as the value of the “classification parameter” when it is determined that the use environment is as described above. The description of the contents common to the first embodiment will be omitted or simplified, and the following description will focus on the differences.

[Generation of WF definition file]
FIG. 7 is a flowchart showing a flow until the workflow support device 103 according to the present embodiment analyzes a PC operation log of the client PC 102 and generates a WF definition file. This flow is also realized by the arithmetic unit 211 executing a predetermined program stored in the storage unit 212 in response to an execution instruction from an operator such as an administrator to the workflow support apparatus 103. Hereinafter, description will be given along the flow of FIG.

  S701 to S703 correspond to S401 to S403 in the flow of FIG. 4 of the first embodiment. That is, the WF creation module 311 obtains a PC operation log (S701), extracts a task therefrom (S702), and determines a task constituting a workflow based on the relevance of the tasks (S703). Here, a PC operation log as shown in Table 3 below is acquired, and “reading of a document” is set as the first task, and “transfer (SMB transmission)” is set as the next task, as in Table 1 described above. It is assumed that the workflow has been determined.

  As shown in Table 3 above, first, the user logs in to the client PC 102 with the client device name “PC1” at 14:26 with the login user name “Administrator”. The client PC 102 with the client device name “PC2” is also logged in at 15:20 with the login user name “Administrator”. That is, this indicates that the user is logged in to different client PCs using the same user name. Here, the PC operation log is represented by one table, but it may be managed by a separate file for each client PC and acquired.

  In S704, the WF creation module 311 extracts the PC login user name and the client device name from the “login” task extracted in S702. In the case of the PC operation log shown in Table 3 above, character string information of "Administrator" is extracted as the PC login user name, and "PC1" and "PC2" are extracted as the client device names.

  S705 to S708 correspond to S405 to S408 in the flow of FIG. First, in S705, the WF creation module 311 generates a WF definition file based on the tasks constituting the workflow determined in S703 and the PC login user name and the client device name extracted in S704. Then, in S706, the address information of the MFP 101 as the WF execution device is obtained, and in S707, the login setting information of the MFP 101 is obtained. In S708, the next step to be executed is assigned based on the login setting information acquired in S707. If the login function is invalid, the process proceeds to S709, and if it is valid, the process proceeds to S712.

  In S709, the WF creation module 311 determines whether the PC login user name extracted in S704 and the client device name correspond one-to-one. If the result of determination is that there is a one-to-one correspondence, the process proceeds to S710. On the other hand, if there is no one-to-one correspondence (when there is a different client device name for one PC login user name), the process proceeds to S711.

  In S710, as in S409 of the flow in FIG. 4, the WF creation module 311 reads the WF definition file generated in S705, and sets the “PC login user name” extracted in S704 as the value of the identifier name “classification parameter”. I do. In step S711, the WF creation module 311 reads the WF definition file generated in step S705, and sets the “client device name” extracted in step S704 as the value of the identifier name “classification parameter”. The WF definition file after the setting process in S710 or S711 is stored again in the storage unit 212 by the WF management module 312.

  In S712, the WF definition file distribution module 313 transmits the WF definition file generated as described above to the MFP 101, as in S410 of the flow in FIG.

  The above is the contents of the processing for generating the WF definition file based on the analysis result of the PC operation log according to the present embodiment. Table 4 below is an example of a WF definition file according to the present embodiment.

  In the case of the WF definition file of Table 4 above, the value of the identifier name “classification parameter” is “client device name”, unlike Table 2 of Embodiment 1. Here, as the value of the identifier name “WF button name”, the file name included in the “data duplication” task extracted from the PC operation log is adopted to be “workflow contract”.

[Generation of WF button]
The process of displaying a WF button on the UI screen based on the WF definition file received from the workflow support device 103 by the MFP 101 is the same as the flow in FIG. 5 of the first embodiment. FIG. 8A shows an example of the UI screen displayed when the login mode is disabled and the display mode of the UI screen relating to the workflow is set to the login unnecessary mode (S504) in the present embodiment. 6A, the UI screen 800 of the login unnecessary mode includes a mode information display area 801, a classification selection area 802, and a WF button selection area 803. However, in the category selection area 802, a name and the like for identifying the client PC are displayed in a list. In the WF button selection area 803, an icon as a WF button associated with an item selected from the group of items displayed in the category selection area 802 is displayed. Now, “PC1” is selected in the category selection area 802, and two icons “contract” and “payment application” associated with this “PC1” are displayed in the WF button selection area 803. In this case, the icon of “contract” indicates the icon newly added in S508, and the icon of “payment application” indicates the icon already associated with “PC1” at the time of addition in S508. ing.

  Furthermore, a plurality of items may be selectable from the group of items displayed in the category selection area 802, and a WF button may be displayed for each selected item. FIG. 8B shows a state where a plurality of items are selected on the UI screen 800 shown in FIG. 8A. “PC1” and “PC2” are selected in the classification selection area 802, and WF buttons associated with “PC1” and “PC2” are displayed in the WF button selection area 803. That is, two icons “contract” and “payment application” associated with “PC1” are displayed in the area 803a corresponding to “PC1”, and “PC2” is displayed in the area 803b corresponding to “PC2”. "Travel expenses" and "Travel expenses" associated with "" are displayed. In the present embodiment, the WF button selection area 803 itself is divided into a plurality according to the selected item, but the present invention is not limited to this. For example, all the WF buttons associated with the selected item are displayed in the WF button selection area 803. At this time, information (for example, a character string) that can identify the client PC name is included in a part of each WF button icon. Etc.) may be superimposed. Furthermore, when a user selects a desired WF button, a message indicating the client PC name set for the selected WF button may be displayed in order to suppress an operation error by the user.

  Note that the method of allowing a plurality of items to be selected from the group of items displayed in the classification selection area and displaying the WF button for each selected item is also applicable to the first embodiment.

  According to the present embodiment, when the login function of an apparatus such as an MFP that executes a workflow is disabled, a button for instructing execution of the workflow is associated with the client terminal and displayed on the UI screen for each client apparatus. . Therefore, the user can easily select a desired workflow without logging in.

Embodiment 3

  Next, an embodiment will be described in which each user can efficiently select a desired WF button even when a business system is used by a large number of users by using classification information of a group unit in addition to a user unit. 3 will be described. The description of the contents common to the first and second embodiments will be omitted or simplified, and the following description will focus on the differences.

[Generation of WF definition file]
FIG. 9 is a flowchart illustrating a flow until the workflow support apparatus 103 according to the present embodiment analyzes a PC operation log of the client PC 102 and generates a WF definition file. In the present embodiment, the workflow button support apparatus 103 has a domain controller function, and login to the client PC 102 is managed using a domain authentication service provided by the workflow support apparatus 103. This flow is also realized by the arithmetic unit 211 executing a predetermined program stored in the storage unit 212 in response to an execution instruction from an operator such as an administrator to the workflow support apparatus 103. Hereinafter, description will be given along the flow of FIG.

  S901 to S903 correspond to S401 to S403 in the flow of FIG. 4 of the first embodiment. That is, the WF creation module 311 obtains a PC operation log (S901), extracts a task therefrom (S902), and determines a task constituting a workflow based on the relevance of the tasks (S903). Here, a PC operation log as shown in Table 5 below is acquired, and as in Tables 1 and 3 above, “document reading” is the first task, and “transfer (SMB transmission)” is the next task. It is assumed that a workflow as a task has been determined.

The difference from Table 1 of the first embodiment is that the domain of the workflow support apparatus 103 that has performed login authentication is described as the variable 2 of the event name “login”.
In S904, the WF creation module 311 extracts a domain name and a PC login user name from the “login” task extracted in S902. In the case of the PC operation log shown in Table 5, the character string information of "Domain1" of variable 2 as the domain name and the character string information of "Yuji" of variable 1 as the PC login user name are respectively extracted.

  In S905, the WF creation module 311 generates a WF definition file based on the tasks constituting the workflow determined in S903 and the domain name and the PC login user name extracted in S904. Table 6 below is an example of a WF definition file according to the present embodiment.

  In the above Table 6, two values of “domain name” and “PC login user name” are included as values of the identifier name “classification parameter”, and indicate that these two are used as classification information. Now, the value of the identifier name “domain name” is “domain1”, and the value of the identifier name “PC login user name” is “Yuji” (set in S909 described later). Therefore, “Domain1” and “Yuji” are used in association with the WF button.

  Steps S906 to S907 correspond to steps S406 to S408 in the flow of FIG. First, in step S906, the address information of the MFP 101 that is the WF execution device is obtained, and in step S907, the login setting information of the MFP 101 is obtained. In step S908, the next step to be executed is assigned based on the login setting information acquired in step S907. If the login function is invalid, the process proceeds to S909, and if it is valid, the process proceeds to S910.

  In step S909, the WF creation module 311 reads the WF definition file generated in step S905, and sets the “domain name” and the “PC login user name” extracted in step S904 as the value of the identifier name “classification parameter”. The WF definition file after the setting process is stored again in the storage unit 212 by the WF management module 312.

  In S910, the WF definition file generated as described above is transmitted to the MFP 101 by the WF definition file distribution module 313 as in S410 of the flow in FIG.

  The above is the contents of the processing for generating the WF definition file based on the analysis result of the PC operation log according to the present embodiment.

[Generate WF button]
The process of displaying a WF button on the UI screen based on the WF definition file received from the workflow support device 103 by the MFP 101 is the same as the flow in FIG. 5 of the first embodiment. FIG. 10A illustrates an example of the UI screen displayed when the login mode is disabled and the display mode of the UI screen related to the workflow is set to the login unnecessary mode (S504) in the present embodiment. 6A, a mode information display area 1001, a classification selection area 1002, and a WF button selection area 1003 exist on the UI screen 1000 in the login unnecessary mode. However, the category selection area 1002 of the present embodiment is divided into a category selection area 1002a for each domain (group) to which a plurality of users belong and a category selection area 1002b for each user. In these two areas, the category selection area 1002a has a higher (main) relationship and the category selection area 1002b has a lower (sub) relationship, and only the user names belonging to the domain selected in the category selection area 1002a are in the category selection area 1002b. Will be displayed. Now, “Domain1” is selected in the classification selection area 1002a. At this point, “Yuji” and “Taro” are displayed in the classification selection area 1002b. Then, when “Yuji” is selected in the classification area 1002b, the WF buttons “Contract” and “Estimate” are displayed in the WF button selection area 1003. As in FIG. 6A of the first embodiment, the “contract” icon is an icon newly added in S508, and the “estimate” icon is an icon already associated with “Yuji” at the time of addition. .

  As described above, in the login unnecessary mode of the present embodiment, the classification selection area in the UI screen is divided into two, and the WF button is displayed in two stages, upper and lower. The user specifies the domain of the group to which the user belongs in the category selection area 1002a, and then specifies his or her login user name in the category selection area 1002b. Accordingly, the WF button associated with both “Domain1” and “Yuji” is displayed in the WF button selection area 1003.

  As described above, according to the present embodiment, when the login function of an apparatus such as an MFP that executes a workflow is disabled, a button for instructing execution of the workflow is displayed in units of domains. Thus, even if the number of users increases, each user can easily select a desired workflow.

(Other Examples)
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 be realized by a circuit (for example, an ASIC) that realizes one or more functions.

Claims (15)

What is claimed is: 1. A workflow support device that generates information for executing an operation performed by a user logged in on a first device as a workflow on a second device,
Acquiring means for acquiring an operation log of the user;
A determination unit that analyzes the acquired operation log and determines an operation related to the second device as a plurality of tasks configuring a workflow;
Generating means for generating a file describing an operation definition for displaying a button for instructing execution of the workflow constituted by the plurality of determined tasks on a UI screen of the second device;
Distribution means for distributing the generated file to the second device;
With
The file includes at least information for specifying the plurality of tasks and a classification parameter for classifying and displaying the button on the UI screen.
A workflow support device characterized by the following.   The workflow support device according to claim 1, wherein the value of the classification parameter is a user name for identifying the user.   The workflow support device according to claim 1, wherein the value of the classification parameter is a device name for identifying the first device. Login of the user to the first device is managed by a domain authentication service;
4. The workflow support apparatus according to claim 2, wherein a domain name in the domain authentication service is further set as a value of the classification parameter.   5. The apparatus according to claim 1, wherein the generation unit acquires login setting information in the second device, and sets the classification parameter when a login function is disabled. 6. Workflow support device.   The workflow support device according to claim 1, further comprising a function of the first device. A workflow execution device that executes, as a workflow, a plurality of operations performed by a user logged in with another device,
Communication means for receiving a file describing an operation definition of a workflow composed of a plurality of tasks determined based on an analysis result of the operation log by the user in the another device;
UI control means for displaying a button for instructing execution of the workflow on a UI screen based on the received file,
The file includes at least information for specifying the plurality of tasks and a classification parameter for classifying and displaying the button on the UI screen.
The workflow execution device, wherein the UI control means classifies and displays the buttons based on the classification parameters. The value of the classification parameter is a user name for identifying the user,
The workflow execution device according to claim 7, wherein the UI control unit displays the button for each user. The value of the classification parameter is a device name for identifying the other device,
The workflow execution device according to claim 7, wherein the UI control unit displays the button in units of other devices. Login of the user to the other device is managed by a domain authentication service,
The file further includes a domain name in the domain authentication service as a value of the classification parameter,
The workflow execution device according to claim 8, wherein the UI control unit further displays the button for each domain. A workflow system that executes an operation performed by a user logged in on a first device as a workflow on a second device,
Determining means for analyzing the operation log of the user and determining an operation related to the second device as a plurality of tasks constituting a workflow;
A file describing an operation definition for displaying a button for instructing execution of the workflow constituted by the plurality of determined tasks on a UI screen of the second device, wherein the file specifies the plurality of tasks. Generating means for generating a file including at least information to be classified and a classification parameter for classifying and displaying the button on the UI screen;
Distribution means for distributing the generated file to the second device;
And a UI control unit for classifying and displaying a button for instructing execution of the workflow based on the received file in the second device. A method for generating information for executing an operation performed by a user logged in on a first device as a workflow on a second device,
An acquiring step of acquiring an operation log of the user;
A determination step of analyzing the acquired operation log and determining an operation related to the second device as a plurality of tasks constituting a workflow;
A generation step of generating a file describing an operation definition for displaying a button for instructing execution of the workflow including the determined plurality of tasks on a UI screen of the second device;
A distribution step of distributing the generated file to the second device;
Including
The file includes at least information for specifying the plurality of tasks and a classification parameter for classifying and displaying the button on the UI screen.
A method comprising: A method of executing, as a workflow, a plurality of operations performed by a user logged in with another device,
A communication step of receiving a file describing an operation definition of a workflow including a plurality of tasks determined based on an analysis result of the operation log by the user in the another device;
Displaying a button for instructing execution of the workflow on a UI screen based on the received file,
The file includes at least information for specifying the plurality of tasks and a classification parameter for classifying and displaying the button on the UI screen.
In the displaying, the buttons are classified and displayed based on the classification parameter.   A program for causing a computer to function as the workflow support device according to any one of claims 1 to 6.   A program for causing a computer to function as the workflow execution device according to any one of claims 7 to 10.