Information processing apparatus, control method of information processing apparatus, and program

Abstract

To implement workflow sharing among a plurality of users in a preferable manner.SOLUTION: In a software configuration of an information processing system, a workflow management unit 423 manages a series of workflows for which a plurality of pieces of processing for target data are defined, in association with a plurality of users or user groups among which the workflows are to be shared. In response to receiving access from a user, a display control unit 422 notifies the user of information about a workflow which was registered or updated at and after the date when access was received from the user before, out of a series of workflows managed by the workflow management unit 423 and is associated with the user or a user group to which the user belongs to, as the object of sharing.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present disclosure relates to an information processing device, a control method for an information processing device, and a program. [Background technology]

[0002] In recent years, various network services such as so-called cloud services (hereinafter also referred to as workflow providing services) have been proposed that provide workflows that automatically execute a series of multiple processes on target data in sequence. As such workflow providing services, services have been proposed that provide workflows that execute multiple processes in sequence on data scanned by a multifunction device or data sent from a client terminal. Patent Document 1 discloses a technique for proposing a modified workflow to the owner of an existing workflow when the existing workflow is modified in a service that provides workflows. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2007-25953 A Summary of the Invention [Problem to be solved by the invention]

[0004] Some of the above-mentioned workflow providing services have a function that enables a workflow created by an administrator or the like to be shared by other members within an organization by granting them usage rights. When a workflow shared among multiple users (hereinafter also referred to as a shared workflow) is added or updated, it may be desirable to inform other users who are users of the workflow that the workflow has been added or updated. On the other hand, even if a technology that proposes updating an existing workflow is applied, such as the technology disclosed in Patent Document 1, when a new shared workflow is added by a certain user, the target of the proposal is the user who is the owner of the shared workflow. In other words, in this case, the other users with whom the added shared workflow is shared are not included in the proposed targets of the revised workflow. Therefore, it is difficult for the other users with whom the workflow is shared to recognize that the newly added shared workflow has been added, even if the newly added shared workflow is useful to them.

[0005] In view of the above problems, an object of the present invention is to realize sharing of a workflow among a plurality of users in a more suitable manner. [Means for solving the problem]

[0006] The information processing device of the present invention is characterized by having a management means for managing a workflow, in which a series of multiple processes for target data are defined, in association with multiple users or user groups to which the workflow is to be shared, and a notification means for, when access is received from a user, notifying the user of information regarding a workflow, from the series of workflows managed by the management means, that has been registered or updated since the date and time when access was previously received from the user, and that is associated with the user or a user group to which the user belongs as a sharing target. Effect of the Invention

[0007] According to the present invention, it is possible to realize sharing of a workflow among a plurality of users in a more preferable manner. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 illustrates an example of a system configuration of an information processing system. [Diagram 2] FIG. 2 illustrates an example of a hardware configuration of a multifunction peripheral. [Diagram 3] FIG. 2 is a diagram illustrating an example of a hardware configuration of an information processing device. [Figure 4] FIG. 2 is a diagram illustrating an example of a software configuration of the information processing system. [Diagram 5] FIG. 13 is a diagram showing an example of a user management screen. [Figure 6] FIG. 13 is a diagram showing an example of a workflow management screen. [Figure 7] FIG. 13 is a diagram showing an example of a setting screen for a workflow update notification function. [Figure 8] FIG. 11 is a diagram showing an example of a workflow execution history. [Figure 9] FIG. 11 is a diagram showing an example of a method for notifying information related to a workflow. [Figure 10] 11 is a flowchart showing an example of processing of an information processing system. [Figure 11] 11 is a flowchart showing an example of processing of an information processing system. [Figure 12] FIG. 13 is a diagram showing an example of a screen presented after login. [Figure 13] FIG. 13 is a diagram showing an example of a user group management screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this specification and the drawings, components having substantially the same functional configurations are denoted by the same reference numerals, and redundant description will be omitted. In addition, in each embodiment of the present disclosure, a workflow refers to a predetermined sequence of processes for target data. The workflow may include a sequence of multiple processes such as input, processing, and output of data.

[0010] <First embodiment> A first embodiment of the present disclosure will be described below. (System Configuration) An example of a system configuration of an information processing system according to this embodiment will be described with reference to FIG. The multifunction device 101 corresponds to a multifunction device having multiple functions such as a scanner, a printer, etc. Moreover, the multifunction device 101 according to this embodiment is capable of uploading data to a workflow providing cloud service 103, which will be described later, and printing data received from the workflow providing cloud service 103. The client terminal 102 is capable of uploading data to the workflow providing cloud service 103 and receiving data from the workflow providing cloud service 103. The client terminal 102 can be realized by, for example, an information processing device having a communication function, such as a personal computer or a smartphone. In the following description, when there is no need to distinguish between the multifunction peripheral 101 and the client terminal 102, they will also be referred to as clients. In other words, when the term client is used, it can refer to either the multifunction peripheral 101 or the client terminal 102 unless otherwise specified.

[0011] The workflow providing cloud service 103 is a cloud service (network service) that provides a workflow mechanism, and has a function of processing data received from a client according to a set workflow. The workflow providing cloud service 103 also manages the workflow itself and the users who use the workflow service. The workflow providing cloud service 103 provides a user who logs in via a client (in other words, a user who has accepted access) with a data processing function based on the workflow that the user is authorized to use.

[0012] With the above configuration, a client transmits data to the workflow providing cloud service 103, which enables the workflow providing cloud service 103 to process the data in accordance with the workflow. Furthermore, the workflow providing cloud service 103 can transmit data that has been processed in accordance with the workflow to the client. Note that, although the present embodiment has been illustrated with a configuration in which the client is the input source and output destination of data, a configuration in which the other cloud service (not shown) is used as the input source and output destination of data may also be applied by linking with the other cloud service (not shown). Furthermore, in this embodiment, the client realizes cooperation with the workflow providing cloud service 103 by using an authentication and authorization mechanism such as OAuth. Moreover, each of the above-mentioned components is configured to be able to communicate with other components via a network. As the network, various networks capable of transmitting and receiving data, such as the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), and a telephone line, can be applied. Furthermore, the network connecting the multiple components is not limited to a single network, and a combination of multiple networks can be applied.

[0013] (Hardware configuration of multifunction printer) An example of the hardware configuration of the multifunction device 101 will be described with reference to Fig. 2. The multifunction device 101 includes a control unit 200, an operation unit 210, a printer unit 211, a scanner unit 212, and a modem 213. The control unit 200 includes a series of components which will be described below with reference numerals 201 to 209, and controls the overall operation of the multifunction device 101. A CPU (Central Processing Unit) 201 reads and executes a control program stored in a ROM (Read Only Memory) 202 to control the operation of each component, thereby implementing various functions of the multifunction device 101. The functions of the multifunction device 101 may include, for example, reading a document, printing a printed matter, and communicating with other devices. A RAM 203 is used as a temporary storage area such as the main memory and work area of ​​the CPU 201. In this embodiment, one CPU 201 executes each process shown in the flowchart described below using one memory (RAM 203 or HDD 204), but the present invention is not necessarily limited to this configuration. For example, each process may be executed by cooperating with multiple CPUs, RAMs, or HDDs. The HDD 204 is a storage area for storing image data and various programs.

[0014] The operation unit I / F 205 is an interface that connects the operation unit 210 and the control unit 200. The operation unit 210 is realized by input devices such as a touch panel, a keyboard, and a pointing device, and receives operations, inputs, instructions, and the like from a user. The printer I / F 206 is an interface that connects the printer unit 211 and the control unit 200. Image data to be printed is transferred from the control unit 200 to the printer unit 211 via the printer I / F 206. The printer unit 211 prints an image indicated by the image data transferred from the control unit 200 on a recording medium such as paper. The scanner I / F 207 is an interface that connects the scanner unit 212 and the control unit 200. The scanner unit 212 reads an original placed on a platen or an ADF (Auto Document Feeder) (not shown), generates image data, and inputs the image data to the control unit 200 via the scanner I / F 207.

[0015] The multifunction peripheral 101 is capable of causing a printer unit 211 to print (copy) image data generated by a scanner unit 212, as well as transmitting files or e-mails. The modem I / F 208 is an interface that connects the modem 213 and the control unit 200. The modem 213 transmits image data by facsimile communication with a facsimile device on a PSTN (Public Switched Telephone Network). The network I / F 209 is a communication interface for connecting the control unit 200 (multifunction device 101) to a network such as a LAN. The multifunction device 101 transmits image data and information to each service on a network such as the Internet via the network I / F 209, and receives various information from each service on the network.

[0016] (Hardware configuration of client terminal and information processing device) An example of the hardware configuration of an information processing device such as the client terminal 102 or a server that provides the workflow providing cloud service 103 will be described with reference to FIG. The client terminal 102 and the information processing device that provides the workflow providing cloud service 103 include a CPU 301, a ROM 302, a RAM 303, a HDD 304, and a network I / F 307. The client terminal 102 also includes a display 305 and an input device 306 in addition to the above components.

[0017] The CPU 301 controls the overall operation of the target device by reading and executing a control program stored in the ROM 302. The RAM 303 is used as a temporary storage area such as the main memory and work area of ​​the CPU 301. The HDD 304 is a storage area for storing image data and various programs. The network I / F 307 is a communication interface that connects target devices (the client terminal 102, the information processing device that provides the workflow providing cloud service 103) to a network such as the Internet. The client terminal 102 and the information processing device that provides the workflow providing cloud service 103 accept processing requests from each other via the network I / F 307 and transmit and receive various information. The display 305 displays various types of information in a predetermined display area (screen, etc.) to present the information to the user. The input device 306 is realized by input devices such as a pointing device such as a mouse, a keyboard, and a touch panel, and receives input of various information from the user.

[0018] (Overall system software configuration) An example of the software configuration of the information processing system according to this embodiment will be described with reference to FIG. The multifunction device 101 includes a data management unit 401 , a display control unit 402 , and a request control unit 403 . A data management unit 401 holds various data to be transmitted to and received from the workflow providing cloud service 103 . The display control unit 402 displays the progress of each process in the print process or workflow, and displays a UI screen for receiving operations from the user, in a predetermined display area (for example, the operation unit 210 realized as a liquid crystal display unit having a touch panel function). Examples of information that the display control unit 402 displays in the display area include print settings, a list of workflows managed by the workflow providing cloud service 103, and various management screens. A request control unit 403 issues a login request to the workflow providing cloud service 103 and requests various processes in accordance with the selected workflow.

[0019] The client terminal 102 includes a data management unit 411 , a display control unit 412 , and a request control unit 413 . The data management unit 411 holds various data transmitted and received between the workflow providing cloud service 103 . The display control unit 412 displays on the display screen configuration information constituting the screen to be displayed upon receiving a request from an application running on the client terminal 102. Examples of information that the display control unit 412 displays on the display include a menu for accepting designation of data to be input into workflow processing, a list of workflows managed by the workflow providing cloud service 103, and various management screens. A request control unit 413 issues to the workflow providing cloud service 103 a request to log in to the service and requests various processes according to the selected workflow.

[0020] The workflow providing cloud service 103 includes a user management unit 421 , a display control unit 422 , a workflow management unit 423 , and a workflow execution unit 424 . The user management unit 421 manages a user account for a user to use the workflow providing cloud service 103 in association with a group to which the user belongs. In addition, the user management unit 421 accepts a login request from a client and performs login processing for the user who is the target of the login request. In this embodiment, the case where the workflow providing cloud service 103 manages user accounts is exemplified, but the subject related to the management of the user accounts is not necessarily limited to the workflow providing cloud service 103. For example, the management of the user accounts of users who use the workflow providing cloud service 103 may be realized by cooperation with an external authentication server. As a more specific example, the management of user accounts may be realized by cooperation with the Active Directory service provided by Microsoft (registered trademark) or the Azure (registered trademark) Active Directory service.

[0021] Upon receiving a request from a client, the display control unit 422 transmits to the client screen configuration information (e.g., information written in a language such as HTML or CSS) for the web browser running on the client to display a screen. The client (more precisely, the web browser running on the client) displays various screens in a predetermined display area (e.g., the operation unit 210, the display 305, etc.) based on the above screen configuration information received from the workflow providing cloud service 103. This enables the user to refer to information on workflows that the user can use, the processing status of the workflows, etc., via the screen displayed on the web browser. The workflow management unit 423 holds and manages workflows. In addition, the workflow management unit 423 provides information on workflows that can be used by users, and adds, edits, and deletes workflows in response to requests from clients. The workflow execution unit 424 sequentially executes a series of processes corresponding to a target workflow in accordance with a workflow processing request made by a client. The workflow execution unit 424 also associates the executed workflow with the executing user and the group to which the user belongs, and stores the workflow execution history in a predetermined storage area (for example, the HDD 304).

[0022] (Workflow cloud service operation settings) An example of the operation of the workflow providing cloud service 103 and the settings of the operation will be described with reference to FIG. 5 to FIG. First, user management in the workflow providing cloud service 103 will be described with reference to Fig. 5. Fig. 5 shows an example of a user management screen that the workflow providing cloud service 103 presents to a user via a client upon receiving a request from the client. Settings made via the user management screen shown in Fig. 5 are stored in a predetermined storage area (for example, HDD 304) by the workflow providing cloud service 103, and are referred to as appropriate when the workflow providing cloud service 103 performs various controls.

[0023] The registration key is a key for accepting an instruction from a user relating to the registration of a new user. The edit key is a key for accepting an instruction from a user relating to the editing of a selected user account. The example shown in Fig. 5 shows a situation in which the user accounts of "Alice" and "Bob" are registered in the workflow providing cloud service 103. The workflow providing cloud service 103 manages the user ID, password, and group to which the user belongs in association with each other. The group to which the user belongs shown in Fig. 5 is a user group to which the target user belongs.

[0024] Here, a user group will be described with reference to Fig. 13. Fig. 13 shows an example of a user group management screen that the workflow providing cloud service 103 presents to a user via a client upon receiving a request from the client. Settings made via the user group management screen shown in Fig. 13 are stored in a predetermined storage area (for example, HDD 304) by the workflow providing cloud service 103, and are referred to as appropriate when the workflow providing cloud service 103 performs various controls.

[0025] The user group management screen 1310 corresponds to an example of a screen displaying a list of user groups managed by the workflow providing cloud service 103. The workflow providing cloud service 103 manages each user group by assigning a group ID that can uniquely identify each user group to each of a series of user groups to be managed. The registration key is a key for receiving an instruction from a user for registering a new user group. The edit key is a key for receiving an instruction from a user for editing a selected user group. When the workflow providing cloud service 103 detects that either the registration key or the edit key on the user group management screen 1310 has been selected in response to a request from a client, it displays the user group edit screen 1320.

[0026] The user group editing screen 1320 corresponds to an example of a screen for receiving various instructions from a user regarding editing of a user group. The member setting area 1321 is an input area for receiving an instruction from a user regarding addition of a user account as a member of the target user group. At this time, the user accounts registered in the workflow providing cloud service 103 by an instruction via the user management screen described with reference to FIG. 5 become candidates for registration to the user group. In addition, it is also possible to delete any member from the target user group by an operation via the member setting area 1321. In the example shown in FIG. 13, a user account named "Alice" illustrated in FIG. 5 is registered as a member for a user group named "Group-A". When the workflow providing cloud service 103 detects that the Apply key has been selected, it stores the content specified via the user group editing screen 1320 in a predetermined storage area (for example, HDD 304) and displays the user group management screen 1310. Furthermore, when the workflow providing cloud service 103 detects that the Cancel key has been selected, it displays the user group management screen 1310 without storing the content specified via the user group editing screen 1320 in a predetermined storage area.

[0027] Next, the workflow management function of the workflow providing cloud service 103 will be described with reference to Fig. 6. Fig. 6 shows an example of a workflow management screen that the workflow providing cloud service 103 presents to a user via a client upon receiving a request from the client. Settings made via the workflow management screen shown in Fig. 6 are stored in a predetermined storage area (for example, HDD 304) by the workflow providing cloud service 103, and are referred to as appropriate when the workflow providing cloud service 103 performs various controls.

[0028] The workflow management screen 610 corresponds to an example of a screen presenting a list of workflows managed by the workflow providing cloud service 103. The workflow providing cloud service 103 manages each workflow by assigning an ID that can uniquely identify the workflow to each of a series of workflows. The registration key is a key for receiving an instruction from a user for registering a new workflow. The edit key is a key for receiving an instruction from a user for editing a selected workflow. The copy key is a key for receiving an instruction from a user for registering a new workflow based on a selected workflow. A workflow newly registered by receiving an operation of the copy key is assigned an ID in a format indicating that it is derived from the ID of the original workflow. For example, a workflow C created by copying a workflow B with an ID of "2." is assigned an ID of "2.1.", that is, an ID in which information "1." indicating that it is derived is added to the original ID "2.". When the workflow providing cloud service 103 detects that any of the registration key, edit key, and copy key on the workflow management screen 610 has been selected in response to a request from a client, the workflow editing screen 620 is displayed.

[0029] The workflow editing screen 620 corresponds to an example of a screen for receiving instructions from a user regarding editing of a workflow. The execution process setting area 621 is an input area for receiving from a user an instruction for adding, inserting, and deleting a process to be executed by the target workflow. The shared setting area 622 is an input area for receiving from a user, who is an operator, an instruction for setting one or more of the users and user groups who are permitted to use the target workflow. The users to be processed correspond to user accounts registered in the workflow providing cloud service 103 based on instructions received via the user management screen described with reference to FIG. 5. The user groups to be processed correspond to user groups registered in the workflow providing cloud service 103 based on instructions received via the user group management screen described with reference to FIG. 13. The last updated date and time display area 623 displays information indicating the date and time when the target workflow was last newly created or updated. When the workflow providing cloud service 103 detects that the Apply key has been selected, it updates the information displayed in the last updated date and time display area 623 to the current date and time. Then, the workflow providing cloud service 103 stores the content input via the workflow editing screen 620 in a predetermined storage area (for example, HDD 304) and displays the workflow management screen 610. Furthermore, when the workflow providing cloud service 103 detects that the Cancel key has been selected, it displays the workflow management screen 610 without storing the content input via the workflow editing screen 620 in a predetermined storage area.

[0030] Next, a workflow update notification function of the workflow providing cloud service 103 in this embodiment will be described with reference to Fig. 7, Fig. 8, and Fig. 9. The workflow update notification function is a function in which the workflow providing cloud service 103 notifies the user, after the login process is completed, of information on workflows that have been added or updated since the previous (for example, most recent) use of the service.

[0031] Fig. 7 shows an example of a setting screen for the workflow update notification function that the workflow providing cloud service 103 presents to a user via a client upon receiving a request from the client. The settings made via the setting screen shown in Fig. 7 are stored in a predetermined storage area (for example, HDD 304) by the workflow providing cloud service 103, and are referred to as appropriate when the workflow providing cloud service 103 performs various controls. 7, the workflow update notification function is enabled, and the notification target is set to "matching condition." In addition, with regard to the conditions for the notification target, condition 711 indicated as "workflow that has been used" and condition 712 indicated as "derived from a workflow that has been used" are enabled.

[0032] The notification target condition designation area 710 is an input area for accepting designation of conditions from the logged-in user for narrowing down the workflows for which the logged-in user is to be notified of updates from among the workflows that have been added or updated since the logged-in user last used the service. A check box is associated with each of the series of conditions shown as conditions 711 to 718, and selecting at least some of the check boxes enables the conditions associated with the check boxes.

[0033] Each of the series of conditions 711 to 718 presented in the notification target condition designation area 710 will be described below. In the following description, the term "matches a process" or "includes a process" refers to, for example, a match or inclusion of a type of process, such as email transmission or translation. However, in the present disclosure, when the term "matches a process" or "includes a process" is used, in addition to a match or inclusion of the type of process, it may be determined that the process matches or is included when various parameters given to the process match. Matching parameters may refer to, for example, a situation in which the destination email address matches in an email transmission process.

[0034] The condition 711 indicated as "workflow that has been used" refers to a workflow whose executing user matches the login user in the workflow execution history stored in a predetermined storage area (e.g., HDD 304) of the workflow providing cloud service 103. Details of the workflow execution history will be described separately later with reference to FIG.

[0035] Condition 712 indicated as "derived from a workflow that has been used" indicates a workflow that satisfies condition 711, that is, a workflow that has been duplicated based on a "workflow that has been used." Specifically, a workflow that is created by accepting an operation of the duplicate key on the workflow management screen 610 and that is assigned an ID derived from the original workflow satisfies condition 712. As a more specific example, on the workflow management screen 610 shown in FIG. 6, workflows derived from workflow B with an ID of "2." are workflow C with an ID of "2.1." and workflow D with an ID of "2.1.1." In other words, if workflow B satisfies the "workflow that has been used" indicated as condition 711, workflows C and D satisfy the condition of "derived from a workflow that has been used" indicated as condition 712.

[0036] Condition 713 indicated as "The first process matches a workflow that has been used before" refers to a workflow whose first process matches a workflow that satisfies condition 711. For example, since the first processes of workflows A to G on the workflow management screen 610 are scans, the first processes of these workflows match. Therefore, if workflow A satisfies the "workflow that has been used before" indicated as condition 711, workflows B to G satisfies the condition of "The first process matches a workflow that has been used before" indicated as condition 713.

[0037] Condition 714 indicated as "The end process matches a workflow that has been used before" refers to a workflow whose end process matches a workflow that satisfies condition 711. For example, on the workflow management screen 610, the end processes of workflows B and F are summaries, so the end processes of these workflows match. Therefore, if workflow B satisfies the condition of "workflow that has been used before" indicated as condition 711, workflow F satisfies the condition of "The end process matches a workflow that has been used before" indicated as condition 714.

[0038] Condition 715 indicated as "the beginning and end processes match those of a workflow that has been used before" refers to a workflow whose beginning and end processes match those of a workflow that satisfies condition 711. For example, on the workflow management screen 610, workflows B and F have a beginning process of scanning and an end process of summarizing, so the beginning and end processes match between these workflows. Therefore, if workflow B satisfies the condition of "workflow that has been used before" indicated as condition 711, workflow F satisfies the condition of "the beginning and end processes match those of a workflow that has been used before" indicated as condition 715.

[0039] Condition 716 indicated as "includes a workflow that has been used" refers to a workflow that includes a series of processes of a workflow that corresponds to condition 711. For example, on the workflow management screen 610, the series of processes of workflow D (scanning, translating, summarizing, redaction, and printing) includes the series of processes of workflow C (scanning, translating, summarizing, and redaction). Therefore, if workflow C corresponds to the "workflow that has been used" indicated as condition 711, workflow D corresponds to the condition of "includes a workflow that has been used" indicated as condition 716.

[0040] Condition 717, indicated as "the 'any user-specified value' % at the beginning matches a workflow that has been used," refers to a workflow in which, starting from the beginning, a percentage of the series of processes in the workflow matches that specified by the user. Specifically, the target workflow is one in which a series of processes starting from the beginning of the workflow, the total number of processes multiplied by the user-specified percentage (here referred to as the target number of processes), matches a series of processes starting from the beginning of the workflow that satisfies condition 711. For example, when 60 is set as the arbitrary user-specified value in the condition 717, the condition 717 becomes "the first 60% matches a workflow that has been used before." In this case, an example of a determination as to whether or not the workflow D shown on the workflow management screen 610 satisfies the condition "the first 60% matches a workflow that has been used before" will be described below. Since the total number of processes in workflow D is 5, the target process number is 3, which is 60% of the total number of processes. In this situation, it is assumed that a workflow that satisfies condition 711 includes a workflow such as workflow C whose first three processes (scan, translate, summarize) match the first three processes (scan, translate, summarize) in workflow D. In this case, workflow D satisfies the condition "first 60% match a workflow that has been used before."

[0041] Condition 718, indicated as "Workflows that have been used and the 'any user-specified value' % at the end match" refers to a workflow in which, among the series of processes in the workflow, the series of processes at the end match the percentage of processes specified by the user, starting from the end. Specifically, the workflow is targeted if the number of processes at the end of the series of processes in the workflow (here referred to as the target number of processes) multiplied by the user-specified percentage times the total number of processes matches the series of processes at the end of the workflow that satisfies condition 711. For example, if 50 is set as the arbitrary user-specified value in condition 718, then condition 717 becomes "50% of the end matches a workflow that has been used before." In this case, an example of determining whether or not workflow G shown on the workflow management screen 610 satisfies the condition "50% of the end matches a workflow that has been used before" will be described below. Since the total number of processes in workflow G is 4, the number of target processes is 2, which is 50% of the total number of processes. Under such circumstances, it is assumed that a workflow that satisfies condition 711 has a series of two processes (redaction, printing) at the end that match the series of two processes (redaction, printing) at the end of workflow G. In such a case, another workflow that has a series of two processes (redaction, printing) at the end that match workflow G corresponds to "50% of the end matches a workflow that you have used." Note that in the example shown in FIG. 6, since there is no other workflow that has a series of two processes (redaction, printing) at the end that match workflow G, a workflow that satisfies condition 718 is not detected.

[0042] In this embodiment, the calculation result of the target process count is rounded up to the nearest integer, but control may be applied to round down or round down to the nearest integer. In addition, when determining whether a workflow including branches or parallel processing satisfies the conditions specified via the notification target condition specification area 710, it is determined whether any of the paths of a series of processes that can be executed in the workflow satisfies the notification target condition.

[0043] 8 shows an example of a workflow execution history managed by the workflow providing cloud service 103. The workflow providing cloud service 103 manages the date and time the workflow was executed, the workflow ID, the workflow name, the executing user account, and the group to which the executing user belongs by associating them and storing them in a predetermined storage area (for example, HDD 304). In other words, the workflow providing cloud service 103 records and manages the execution results of the workflow by each user in the workflow execution history. Furthermore, the workflow execution history stored in the above storage area is referred to as appropriate when the workflow providing cloud service 103 performs various controls.

[0044] With reference to FIG. 9, an example of a method in which the workflow providing cloud service 103 notifies a user of information on a workflow that has been added or updated since the user last used the service, using the workflow update notification function, will be described. When the workflow providing cloud service 103 receives a login request from a client, it executes login processing 900 for logging the user in to the workflow providing cloud service 103. Then, when the login processing 900 is completed, the workflow providing cloud service 103 presents an operation screen for the user who is the target of the login processing 900 to the user via the client. For example, in the example described with reference to Fig. 5, a notification screen 910 shows an example of an operation screen presented via the client when Alice, a user to be managed, logs in. Similarly, a notification screen 930 shows an example of an operation screen presented via the client when Bob, a user to be managed, logs in.

[0045] As described above, each of the notification screens 910 and 930 is an example of a screen that notifies the target user of a workflow that has been added or updated since the target user last used the service. The workflow notified via these notification screens is a workflow that satisfies the conditions specified via the notification target condition specification area 710 of the screen described with reference to FIG. As a specific example, a notification screen 910 shows an example of a screen presented when Alice logs in to the workflow providing cloud service 103 in a situation where the setting contents exemplified in Figures 6 and 7 are applied and the execution history exemplified in Figure 8 is managed. The notification screen 910 presents workflow B, workflow C, and workflow D as workflows that have been added or updated since the previous use of the service. When Alice logs in, the workflow providing cloud service 103 evaluates whether or not each of the workflows that have been added or updated since Alice last used it meets the notification target conditions exemplified in FIG. 7. Workflow B meets the condition of "workflows that have been used" shown as condition 711, because it has been executed by Alice in the workflow execution history (FIG. 8). Furthermore, workflows C and D shown as examples on the workflow management screen 610 are workflows derived from workflow B, and therefore meet the condition of "derived from a workflow that has been used" shown as condition 712. Therefore, on the notification screen 910, workflows B, C, and D are presented as workflows that have been added or updated since the last time the service was used.

[0046] When the workflow providing cloud service 103 detects that the close key has been selected on each notification screen shown in FIG. 9, it presents a workflow list screen to the user via the client. Screen 920 shows an example of a workflow list screen when the logged-in user is Alice. That is, the workflows available to Alice are displayed on screen 920. Screen 940 shows an example of a workflow list screen when the logged-in user is Bob. That is, the workflows available to Bob are displayed on screen 940. The logged-in user can select a workflow to be executed via the presented workflow list screen. When the workflow providing cloud service 103 detects that an execution key has been selected after a workflow has been selected, the workflow providing cloud service 103 executes a series of processes in sequence based on the selected workflow.

[0047] (Information Processing System) An example of the processing of the information processing system according to this embodiment will be described with reference to Fig. 10, focusing particularly on the processing related to the control of the workflow providing cloud service 103. The series of processing shown in Fig. 10 is realized by the CPU 301 of the information processing device that provides the workflow providing cloud service 103 executing a control program stored in the ROM 302 or the HDD 304. It is also assumed that the series of processing shown in Fig. 10 is started after the workflow providing cloud service 103 receives a login request from a client and executes login processing.

[0048] In S1001, the workflow management unit 423 determines whether or not the workflow notification setting is valid. As a specific example, the workflow management unit 423 determines whether or not the workflow notification setting is valid by referring to the setting value of the workflow update notification illustrated in FIG. If the workflow management unit 423 determines in S1001 that the workflow notification setting is valid (if the setting value is ON), the process proceeds to S1002. On the other hand, if the workflow management unit 423 determines in S1001 that the workflow notification setting is not valid (if the setting value is OFF), the process proceeds to S1010.

[0049] In S1002, the workflow management unit 423 acquires one workflow to be evaluated from the workflow group managed by the workflow providing cloud service 103 illustrated in FIG. In S1003, the workflow management unit 423 determines whether the workflow to be evaluated has been added or updated since the date and time of the last use by the logged-in user. As a specific example, the workflow management unit 423 refers to the workflow management information illustrated in Fig. 6 and determines whether the date and time displayed in the last update date and time display area 623 is after the date and time of the last use by the logged-in user. If the workflow management unit 423 determines in S1003 that the workflow to be evaluated has been added or updated since the date and time of the previous use by the logged-in user, the process proceeds to S1004. On the other hand, if the workflow management unit 423 determines in S1003 that the workflow to be evaluated has not been added or updated since the date and time of the previous use by the logged-in user, the process proceeds to S1007.

[0050] In S1004, the workflow management unit 423 determines whether or not the logged-in user is allowed to use the workflow to be evaluated. Specifically, the workflow management unit 423 refers to the setting information of the workflow to be evaluated that is registered in the workflow providing cloud service 103 by an operation via the workflow management screen exemplified in Fig. 6. Then, the workflow management unit 423 checks whether or not the shared setting of the workflow to be evaluated (setting value specified via the shared setting area 622) includes the logged-in user or a user group to which the logged-in user belongs. If the workflow management unit 423 determines in S1004 that the login user is allowed to use the workflow to be evaluated, the process proceeds to S1005. On the other hand, if the workflow management unit 423 determines in S1004 that the login user cannot use the workflow to be evaluated, the process proceeds to S1007.

[0051] In S1005, the workflow management unit 423 judges whether the workflow to be evaluated matches the information notification condition. Specifically, the workflow management unit 423 judges whether the workflow to be evaluated corresponds to the setting contents specified via the notification target condition specification area 710 of the screen illustrated in FIG. If the workflow management unit 423 determines in S1005 that the workflow to be evaluated matches the condition for information notification, the process proceeds to S1006. On the other hand, if the workflow management unit 423 determines in S1005 that the workflow to be evaluated does not match the condition for information notification, the process proceeds to S1007. In S1006, the workflow management unit 423 adds the workflow to be evaluated to the list of information to be notified to the user.

[0052] In S1007, the workflow management unit 423 determines whether or not the series of evaluations shown as the processes from S1003 to S1006 has been performed for all workflow groups managed by the workflow providing cloud service 103. If the workflow management unit 423 determines in S1007 that a series of evaluations has been completed for all of the workflow groups managed by the workflow providing cloud service 103, the process proceeds to S1008. On the other hand, if the workflow management unit 423 determines in S1007 that a series of evaluations has not been completed for all of the workflow groups managed by the workflow providing cloud service 103, the process proceeds to S1002. In this case, the processes from S1002 onwards are executed again for the workflows that have not yet been evaluated.

[0053] In S1008, the workflow management unit 423 determines whether or not one or more workflows are included in the target of information notification to the user. If the workflow management unit 423 determines in S1008 that one or more workflows are included in the targets of the information notification to the user, the process proceeds to S1009. On the other hand, if the workflow management unit 423 determines in S1008 that one or more workflows are not included in the targets of the information notification to the user, the process proceeds to S1010.

[0054] In 1009, the display control unit 422 presents a notification screen, on which information related to the workflow determined to be included in the target of information notification to the user in S1008, to the logged-in user via the client. For example, each of the notification screens 910 and 930 illustrated in Fig. 9 corresponds to an example of the screen presented to the logged-in user in S1009.

[0055] In S1010, the display control unit 422 presents a workflow list screen corresponding to the login user to the login user via the client. For example, each of the screens 920 and 940 illustrated in Fig. 9 corresponds to an example of the screen presented to the login user in S1010.

[0056] In this embodiment, the series of processes shown in Fig. 10 are executed after the workflow providing cloud service 103 receives a login request from a client and executes login processing, but this does not necessarily limit the trigger for executing the series of processes. As a specific example, the workflow providing cloud service 103 may display an update information key (not shown) on the workflow list screen, and execute the series of processes shown in Fig. 10 when it is detected that the update information key is pressed. In this case, when the workflow management unit 423 determines in S1008 that one or more workflows are not included in the targets of information notification to the user, the display control unit 422 may display a screen (not shown) indicating that there is no update information.

[0057] <Second embodiment> As a second embodiment of the present disclosure, in addition to the first embodiment, an example of a mechanism for presenting a workflow that is likely to be useful to a user who has not executed a workflow in the workflow providing cloud service 103 will be described. The hardware configuration of each device in the second embodiment is the same as that in the first embodiment. In the following, the present embodiment will be described focusing on the parts that are particularly different from the first embodiment, and detailed description of the parts that are substantially the same as the first embodiment will be omitted.

[0058] An example of processing added to the first embodiment in order to realize this embodiment will be described with reference to Fig. 11. A series of processing shown in Fig. 11 is realized by the CPU 301 of the information processing device that provides the workflow providing cloud service 103 executing a control program stored in the ROM 302 or HDD 304.

[0059] In this embodiment, when it is determined in the process of S1001 shown in Fig. 10 that the workflow notification setting is valid, the determination process shown as the process of S1101 in Fig. 11 is executed. Specifically, in S1101, the workflow management unit 423 refers to the workflow execution history exemplified in Fig. 8 and determines whether or not the logged-in user has executed a workflow. If the workflow management unit 423 determines in S1101 that the logged-in user has executed a workflow before, the process proceeds to S1002 shown in FIG. On the other hand, if the workflow management unit 423 determines in S1101 that the login user has never executed the workflow, the process proceeds to S1102.

[0060] In S1102, the workflow management unit 423 refers to the workflow execution history exemplified in FIG. 8, and calculates the number of times each workflow has been executed by a user who belongs to the same group as the logged-in user. In S1103, the workflow management unit 423 adds the workflow group with the highest number of executions by users in the same group as the logged-in user (for example, the top N workflows in terms of execution count) to the list of workflows to be notified to the user, and proceeds to S1009 shown in FIG. The number of executions may be calculated as the total number of executions of the target workflow, or may be calculated by regarding multiple executions of the workflow by the same user as one execution. The number of executions may also be calculated based on the entire execution history, or based on a day, week, month, year, or any fixed period set on a setting screen (not shown).

[0061] An example of a screen that the workflow providing cloud service 103 in this embodiment presents to a user via a client after receiving a login request from the client and executing login processing will be described with reference to Fig. 12. Note that in the example shown in Fig. 12, it is assumed that a user account called Carol is registered in addition to Alice and Bob described in the first embodiment. Also, it is assumed that Carol has a user account in the workflow providing cloud service 103 but has never executed a workflow using the workflow providing cloud service 103. In this embodiment, when Carol, who has never executed a workflow, logs in via a client, the workflow providing cloud service 103 displays a notification screen 1201 that presents workflows that are frequently used in the group to which Carol belongs. On the other hand, when a user who has executed a workflow, such as Alice, logs in via a client, the workflow providing cloud service 103 displays a workflow update notification screen, as in the first embodiment. Through the above-described control, workflows that are frequently used in the group to which the user belongs are presented, making it possible for a user who has never executed a workflow to become aware of information about workflows that may be useful to the user.

[0062] In this embodiment, an example of a case where workflows that are frequently used within a group to which the user belongs are displayed has been described, but workflows that are frequently used across the entire service may be displayed without limiting the group. In addition, the example shown in Fig. 12 illustrates a screen that presents the top three workflows that have been used the most, but the number of workflows to be displayed may be specified on a setting screen (not shown). In addition, in the present embodiment, an example of a case where a workflow is presented to a user who has never executed a workflow has been described, but similar information may also be presented to a user who has executed a workflow under a predetermined condition. As a specific example, a workflow that is frequently used in a group to which the user belongs may be presented periodically at predetermined intervals to a user who has executed a workflow. In this case, the frequency of the periodic information presentation may be, for example, daily, weekly, monthly, or annually, or at any fixed interval set by a setting screen (not shown).

[0063] <Other embodiments> The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions. Furthermore, the present invention includes systems and their functions that are configured by appropriately combining the above-mentioned embodiments.

[0064] The disclosure of the present embodiment also includes the following configurations, methods, and programs. (Configuration 1) An information processing device characterized by having a management means for managing a workflow, in which a series of multiple processes for target data are defined, in association with multiple users or user groups to which the workflow is to be shared, and a notification means for, when access is received from a user, notifying the user of information regarding a workflow, from the series of workflows managed by the management means, that has been registered or updated after the date and time when access was previously received from the user, and that is associated with the user or a user group to which the user belongs as a sharing target. (Configuration 2) An information processing device as described in configuration 1, further comprising a setting means for setting conditions for workflows to be the subject of information notification, wherein the notification means, when receiving access from a user, notifies the user of information regarding a workflow that, among a series of workflows managed by the management means, has been registered or updated after the date and time when access was previously received from the user and that satisfies the conditions set by the setting means. (Configuration 3) The information processing device according to configuration 2, characterized in that candidates for the conditions of the workflow to be set by the setting means include at least any of the following: a workflow that has been executed by a target user; a workflow that is derived from a workflow that has been executed by the user; a workflow whose initial process matches that of a workflow that has been executed by the user; a workflow whose final process matches that of a workflow that has been executed by the user; a workflow whose initial and final processes match that of a workflow that has been executed by the user; a workflow that includes a series of processes of a workflow that has been executed by the user; a workflow whose series of processes from the beginning, a proportion specified by the user, matches a series of processes from the beginning of a workflow that has been executed by the user; and a workflow whose series of processes from the end, a proportion specified by the user, matches a series of processes from the end of a workflow that has been executed by the user. (Configuration 4) The information processing device according to any one of configurations 1 to 3, wherein when the notification means receives access from a user who has no history of executing a workflow, the notification means notifies the user who has received the access of at least one of information about each of a predetermined number of workflows that have been executed more frequently by other users other than the user who has received the access, among the series of workflows managed by the management means, and information about each of a predetermined number of workflows that have been executed more frequently by other users who belong to a user group to which the user who has received the access belongs. (Configuration 5) The information processing device according to any one of configurations 1 to 3, wherein the notification means notifies the user who has accepted the access of at least one of information on each of a predetermined number of workflows that have been executed more frequently by other users other than the user who has accepted the access, and information on each of a predetermined number of workflows that have been executed more frequently by other users who belong to a user group to which the user who has accepted the access belongs, periodically at predetermined intervals. (Method 1) A control method of an information processing device, comprising: a management step of managing a workflow, in which a series of multiple processes for target data are defined, in association with multiple users or user groups to which the workflow is to be shared; and a notification step of, when access is received from a user, notifying the user of information regarding a workflow, from the series of workflows managed by the management means, that has been registered or updated since the date and time when access was previously received from the user, and that is associated with the user or a user group to which the user belongs as a sharing target. (Program 1) A program for causing a computer to function as an information processing device, characterized by having a management means for managing a workflow, in which a series of multiple processes for target data are defined, in association with multiple users or user groups with whom the workflow is to be shared, and a notification means for, when access is received from a user, notifying the user of information regarding a workflow, from the series of workflows managed by the management means, that has been registered or updated since the date and time that access was previously received from the user, and that is associated with the user or a user group to which the user belongs as a sharing target. [Explanation of symbols]

[0065] 103 Workflow provision cloud service 422 Display control unit 423 Workflow Management Department

Claims

1. a management means for managing a workflow, in which a series of multiple processes for target data is defined, in association with multiple users or user groups with whom the workflow is to be shared; a notification means for notifying a user, when access is received from the user, of a series of workflows managed by the management means, of workflows that have been registered or updated since the date and time of previous access reception from the user, and to which the user or a user group to which the user belongs is associated as a sharing target; An information processing device comprising:

2. A setting unit is provided for setting a condition of a workflow to be notified of information, When the notification means receives an access from a user, the notification means notifies the user of information regarding a workflow that has been registered or updated since the date and time when the access from the user was previously received, among a series of workflows managed by the management means, and that satisfies the condition set by the setting means.

2. The information processing device according to claim 1.

3. The workflow condition candidates to be set by the setting means include: The workflow must have been executed by the target user. The workflow is derived from a workflow that has been executed by the user. The workflow has a beginning process that matches a workflow that has been executed by the user, and The workflow has a final process that matches that of a workflow that has been executed by the user, The process at the beginning and end of the workflow is the same as that of a workflow that has been executed by the user; and The workflow includes a series of workflow processes that have been executed by the user. A series of processes from the beginning of a workflow at a ratio specified by the user matches a series of processes from the beginning of a workflow that has been executed by the user; and A series of processes from the end of a workflow, the proportion of which is specified by the user, matches a series of processes from the end of a workflow that has been executed by the user; and At least one of the following is included: The information processing device according to claim 2 .

4. The notification means, when receiving an access from a user who has not executed a workflow, notifies the user of a series of workflows managed by the management means, Information about each of a predetermined number of workflows that have been executed more frequently by users other than the user who has accepted the access; and Information about each of a predetermined number of workflows that have been executed more frequently by other users who belong to a user group to which the user who has accepted the access belongs; and notify the user who has accepted the access of at least one of the following:

4. The information processing device according to claim 1, wherein the information processing device further comprises:

5. The notification means periodically, at predetermined intervals, Information regarding each of a predetermined number of workflows that have been executed more frequently by other users than the user who received the access; and Information about each of a predetermined number of workflows that have been executed more frequently by other users who belong to a user group to which the user who has accepted the access belongs; and notify the user who has accepted the access of at least one of the following:

4. The information processing device according to claim 1, wherein the information processing device further comprises:

6. A method for controlling an information processing device, comprising: a management step of managing a workflow, in which a series of multiple processes for target data is defined, in association with multiple users or user groups with whom the workflow is to be shared; a notification step of, when an access from a user is accepted, notifying the user of information regarding a workflow that has been registered or updated since the date and time when the access from the user was accepted and that is associated with the user or a user group to which the user belongs as a sharing target, among a series of workflows managed in the management step; 2. A method for controlling an information processing device, comprising:

7. Computer, a management means for managing a workflow, in which a series of multiple processes for target data is defined, in association with multiple users or user groups with whom the workflow is to be shared; a notification means for notifying a user, when access is received from the user, of a series of workflows managed by the management means, of workflows that have been registered or updated since the date and time of previous access reception from the user, and to which the user or a user group to which the user belongs is associated as a sharing target; A program for causing an information processing device to function, comprising:

Images