Workflow sharing system, workflow sharing method, and program

Abstract

To automatically delete or hold setting values set for each of setting items of tasks included in a workflow when the workflow is distributed, while reducing operation load of a user.SOLUTION: A workflow sharing system 1 includes: a workflow generation unit 20 which sets setting values for each of setting items of tasks when the workflow is generated to execute the tasks in the order designated in advance; a flag addition unit 21 which adds a deletion flag or a hold flag to each of the setting values set for each of the setting items of the tasks; and a setting value deletion unit 25 which determines, when the workflow is distributed to another user, whether each of the setting values set for each of the setting items of the tasks has a deletion flag added thereto, and deletes the setting value with the deletion flag added thereto.SELECTED DRAWING: Figure 4

Description

Technical Field

[0005] , , ,

[0001] The present invention relates to a workflow sharing system, a workflow sharing method, and a program.

Background Art

[0002] By utilizing a workflow that executes a plurality of tasks in a preset order, it is possible to improve the efficiency of operations. In order to cause a computer to execute a workflow, it is necessary to input preset values in advance for the setting items of each task included in the workflow. The computer can automatically execute each task by using the preset values input in advance. For example, for routine work and the like, the work efficiency can be significantly improved by utilizing a workflow.

[0003] Incidentally, a workflow as described above may be shared by a plurality of users. Conventionally, a workflow sharing system that shares a workflow among a plurality of users has been proposed (for example, Patent Document 1). In this prior art, when the set value set for the setting item of the task included in the workflow is a non-shared parameter including personal information, it is disclosed that by replacing the non-shared parameter with a substitute parameter, leakage of personal information during workflow sharing can be prevented.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

[0006] When a user who created a workflow distributes and shares it with other users, they may be in the same group but belong to different teams. In this case, group information can be left in the workflow when distributing it, but personal and team information must be removed. If personal and team information is left in the workflow when distributing it, it will not function as intended by the other user, leading to malfunctions. There is also the problem of information within the team being leaked to users in other teams.

[0007] One way to prevent such problems is to replace personal information with alternative information, as in the conventional technology mentioned above. However, the settings set in a workflow include settings that can be shared with other users and settings that cannot be shared with other users, and information that cannot be shared with other users is not necessarily limited to personal information. Therefore, if settings that can be shared with users to whom the workflow is distributed are replaced with alternative parameters, the users who receive the workflow will have to reconfigure the settings again when they use the workflow, which reduces usability.

[0008] On the other hand, when a user who created a workflow distributes it, they might consider manually deleting settings that cannot be shared, taking into account the characteristics of the recipient users. However, this is not foolproof, as users might forget to perform such deletions when distributing the workflow. Furthermore, if users have to manually delete settings when distributing a workflow, it increases their workload and lacks convenience.

[0009] The present invention was made to solve the above problems, and aims to provide a workflow sharing system, workflow sharing method, and program that reduce the operational burden on the user while automatically deleting or retaining the setting values ​​set for each setting item of each task included in the workflow when the workflow is distributed. [Means for solving the problem]

[0010] To achieve the above objective, the invention according to claim 1 is a workflow sharing system comprising: a workflow creation unit that sets setting values ​​for each setting item of each task when creating a workflow that executes multiple tasks in a predetermined order; a flag setting unit that individually assigns a delete flag or a retain flag to the setting values ​​set for each setting item of each task; and a setting value deletion unit that, when the workflow is distributed to other users, determines whether the delete flag has been assigned to the setting values ​​set for each setting item of each task and deletes the setting values ​​to which the delete flag has been assigned. A history management unit records and manages the setting value for each setting item of each task and the deletion flag or retention flag attached to that setting value in the history information, Equipped with When a new workflow is created by the workflow creation unit, if a task recorded in the history information is selected, the flag assignment unit automatically assigns the delete flag or the retain flag to the setting value for each setting item of the task based on the history information. This configuration is characterized by the following features. The invention according to claim 2 is a workflow sharing system comprising: a workflow creation unit that sets setting values ​​for each setting item of each task when creating a workflow that executes multiple tasks in a predetermined order; a flag assignment unit that individually assigns a delete flag or a retain flag to the setting values ​​set for each setting item of each task; a setting value deletion unit that, when the workflow is distributed to other users, determines whether the delete flag has been assigned to the setting value set for each setting item of each task and deletes the setting value to which the delete flag has been assigned; and a history management unit that records and manages the setting values ​​for each setting item of each task and the delete flag or retain flag assigned to the setting value in association with history information, wherein the flag assignment unit is configured such that, when a new workflow is created by the workflow creation unit, a task recorded in the history information is selected and the same setting value as the setting value recorded in the history information is set, the flag assignment unit automatically assigns the delete flag or the retain flag to the setting value based on the history information.

[0011] Claim 3 The invention relating to this is as described in claim 1 or 2 In the workflow sharing system, the setting value deletion unit is configured to retain the setting values ​​to which the retention flag has been set, without deleting them, when the workflow is distributed to other users.

[0013] The invention according to claim 4 is, or 2 In the workflow sharing system, the setting value deletion unit is configured to delete the setting value to which the deletion flag is attached when the attributes of the user who created the workflow and the attributes of the user designated as the recipient of the workflow are different from each other.

[0014] The invention according to claim 5 is, 4 In this workflow sharing system, the user attributes are characterized by including the groups to which the user belongs.

[0015] The invention according to claim 6 is, or 2 In this workflow sharing system, the workflow creation unit is characterized by setting user-specified setting values ​​for each task's setting items.

[0020] Claim 7 The invention relating to this claim is 1 or 2 In this workflow sharing system, the history management unit is configured to manage the history information for each user who creates a workflow.

[0023] Claim 8 The invention relating to this is , wa Workflow sharing system The workflow includes: a workflow creation unit that sets setting values ​​for each setting item of each task when creating a workflow that executes multiple tasks in a predetermined order; a flag assignment unit that individually assigns a delete flag or a retain flag to the setting values ​​set for each setting item of each task; a setting value deletion unit that, when the workflow is distributed to other users, determines whether the delete flag has been assigned to the setting values ​​set for each setting item of each task and deletes the setting values ​​to which the delete flag has been assigned; and a flag management unit that manages flag registration information in which the delete flag or the retain flag has been assigned to each setting item of each task in advance, wherein the flag assignment unit automatically assigns the delete flag or the retain flag to the setting values ​​set for each setting item of each task included in the workflow based on the flag registration information. The aforementioned flag management unit, The aforementioned flag registration information is managed for each user. The configuration is characterized in that if the number of times a flag different from the deletion flag or the retention flag set in the flag registration information is selected by the same user reaches a predetermined number of times, the deletion flag or the retention flag set in the flag registration information is changed.

[0024] Claim 9The invention relates to a workflow sharing method for sharing a workflow that executes a plurality of tasks in a preset order among a plurality of users. When creating the workflow, there is a workflow creation step of setting a setting value for each setting item of each task included in the workflow, a flag assignment step of individually assigning a deletion flag or a retention flag to the setting value set for each setting item of each task included in the workflow, and when the workflow is distributed to other users, a setting value deletion step of determining whether the deletion flag is assigned to the setting value set for each setting item of each task included in the workflow and deleting the setting value to which the deletion flag is assigned. A history management step that records and manages the setting value for each setting item of each task and the deletion flag or retention flag attached to that setting value in the history information, having Furthermore, the flag assignment step, when a new workflow is created by the workflow creation step, and a task recorded in the history information is selected, automatically assigns the delete flag or the retain flag to the setting value for each setting item of the task based on the history information. a configuration characterized by this. The invention according to claim 10 is a workflow sharing method for sharing a workflow in which multiple tasks are executed in a predetermined order among multiple users, comprising: a workflow creation step in which a setting value is set for each setting item of each task included in the workflow when the workflow is created; a flag assignment step in which a delete flag or a retain flag is individually assigned to the setting value set for each setting item of each task included in the workflow; a setting value deletion step in which, when the workflow is distributed to other users, the method determines whether the delete flag has been assigned to the setting value set for each setting item of each task included in the workflow and deletes the setting value to which the delete flag has been assigned; and a history management step in which the setting value for each setting item of each task and the delete flag or the retain flag assigned to that setting value are recorded in history information and managed in association, wherein the flag assignment step is configured to automatically assign the delete flag or the retain flag to the setting value based on the history information when a new workflow is created by the workflow creation step, a task recorded in the history information is selected, and the same setting value as the setting value recorded in the history information is set. The invention according to claim 11 is a workflow sharing method for sharing a workflow in which multiple tasks are executed in a predetermined order among multiple users, comprising: a workflow creation step in which a setting value is set for each setting item of each task included in the workflow when the workflow is created; a flag assignment step in which a delete flag or a retain flag is individually assigned to the setting value set for each setting item of each task included in the workflow; a setting value deletion step in which, when the workflow is distributed to other users, the system determines whether the delete flag has been assigned to the setting value set for each setting item of each task included in the workflow and deletes the setting value to which the delete flag has been assigned; and a flag management step in which flag registration information in which the delete flag or the retain flag has been set in advance for each setting item of each task, wherein the flag assignment step automatically assigns the delete flag or the retain flag to the setting value set for each setting item of each task included in the workflow based on the flag registration information, and the flag management step manages the flag registration information for each user, and when the number of times a flag different from the delete flag or the retain flag set in the flag registration information is selected by the same user reaches a predetermined number of times, the system changes the delete flag or the retain flag set in the flag registration information.

[0025] Claim 12 The invention according to claim is a program that causes a computer to perform a workflow creation step of setting a setting value for each setting item of each task included in a workflow that executes a plurality of tasks in a preset order, a flag assignment step of individually assigning a deletion flag or a retention flag to the setting value set for each setting item of each task included in the workflow, and when the workflow is distributed to other users, a setting value deletion step of determining whether the deletion flag is assigned to the setting value set for each setting item of each task included in the workflow and deleting the setting value to which the deletion flag is assigned. A history management step that records and manages the setting value for each setting item of each task and the deletion flag or retention flag attached to that setting value in the history information, to execute The flag assignment step, when a new workflow is created by the workflow creation step, and a task recorded in the history information is selected, automatically assigns the delete flag or the retain flag to the setting value for each setting item of the task based on the history information. a configuration characterized by this. The invention according to claim 13 is a program that causes a computer to execute a workflow in which a plurality of tasks are executed in a predetermined order, comprising: a workflow creation step of setting a setting value for each setting item of each task included in the workflow; a flag assignment step of individually assigning a delete flag or a retain flag to the setting value set for each setting item of each task included in the workflow; a setting value deletion step of determining whether the delete flag has been assigned to the setting value set for each setting item of each task included in the workflow when the workflow is distributed to other users, and deleting the setting value to which the delete flag has been assigned; and a history management step of recording and managing the setting value for each setting item of each task and the delete flag or the retain flag assigned to that setting value in the history information, wherein the flag assignment step is configured to automatically assign the delete flag or the retain flag to the setting value based on the history information when a new workflow is created by the workflow creation step, and a task recorded in the history information is selected and the same setting value as the setting value recorded in the history information is set. The invention according to claim 14 is a program that causes a computer to execute a workflow in which a plurality of tasks are executed in a predetermined order, comprising: a workflow creation step of setting a setting value for each setting item of each task included in the workflow; a flag assignment step of individually assigning a delete flag or a retain flag to the setting value set for each setting item of each task included in the workflow; a setting value deletion step of determining whether the delete flag has been assigned to the setting value set for each setting item of each task included in the workflow when the workflow is distributed to other users, and deleting the setting value to which the delete flag has been assigned; and a flag management step of managing flag registration information in which the delete flag or the retain flag has been assigned in advance for each setting item of each task, wherein the flag assignment step automatically assigns the delete flag or the retain flag to the setting value set for each setting item of each task included in the workflow based on the flag registration information, and the flag management step manages the flag registration information for each user, and when the number of times a flag different from the delete flag or the retain flag set in the flag registration information is selected by the same user reaches a predetermined number of times, the delete flag or the retain flag set in the flag registration information is changed.

Effect of the Invention

[0027] [Figure 1] This figure shows an example configuration of a workflow sharing system. [Figure 2] This figure shows an example of the hardware configuration of a workflow sharing device. [Figure 3] This figure shows an example of user information. [Figure 4] This figure shows an example of the functional configuration of a workflow sharing device. [Figure 5] This figure shows an example of a workflow creation screen provided by the Workflow Creation Department. [Figure 6] This figure shows an example of the editing screen for the workflow settings table. [Figure 7] This figure shows an example of workflow configuration data created by the workflow creation unit. [Figure 8] This figure shows an example of workflow configuration data when some configuration items are not flagged. [Figure 9] This figure shows an example of flag registration information. [Figure 10] This figure shows an example of an operation screen for users to perform flag setting operations. [Figure 11] This figure shows an example of an editing screen displayed when either the delete flag or the keep flag is tentatively selected. [Figure 12] This figure shows an example of workflow configuration data generated when user A distributes a workflow created by user B or E to other users. [Figure 13] This flowchart shows an example of a basic processing procedure using a workflow sharing device. [Figure 14] A flowchart illustrating a detailed example of the workflow creation process. [Figure 15] This flowchart shows an example of a detailed processing procedure for flag setting. [Figure 16] This flowchart shows an example of a detailed processing procedure for workflow distribution. [Modes for carrying out the invention]

[0028] Preferred embodiments of the present invention will be described in detail below with reference to the drawings. In the embodiments described below, elements common to all are denoted by the same reference numerals, and redundant explanations of these elements will be omitted.

[0029] Figure 1 shows an example configuration of a workflow sharing system 1 in one embodiment of the present invention. The workflow sharing system 1 is configured such that a workflow sharing device 2, a plurality of image processing devices 3, and a plurality of information processing terminals 4 are connected to a network 5 such as a LAN (Local Area Network) and can communicate with each other. The workflow sharing device 2 is configured, for example, as a server device. The workflow sharing device 2 may be installed in an intranet environment such as a company network, or it may be installed in a cloud environment on the internet. The plurality of image processing devices 3 include image processing devices 3a and 3b. For example, the image processing devices 3a and 3b are configured as multifunction devices such as MFPs (multifunction peripherals) and are equipped with scanning, printing, copying, and faxing functions. The plurality of information processing terminals 4 are devices used by each of the plurality of users A to H, and are composed of, for example, personal computers (PCs) or tablet terminals.

[0030] For example, as shown in Figure 1, multiple users A through H belong to an organization within a certain company. Users A and B belong to team TA of group GA within the company organization. Users C and D belong to team TB of group GA. Users E, F, G, and H belong to a different group GB than users A, B, C, and D.

[0031] Workflow Sharing Device 2 is a device that aims to improve the efficiency of business operations within a company organization by creating workflows that execute multiple tasks in a predetermined order based on instructions from a user, and by distributing and sharing workflows created by one user with other users. Furthermore, Workflow Sharing Device 2 can also manage workflows created by users and execute the multiple tasks defined in those workflows in a predetermined order.

[0032] Workflow sharing device 2 can be used by multiple users A through H. Each user A through H can access workflow sharing device 2 using their own information processing terminal 4 to edit and create workflows, and distribute workflows to other users. In the following, we will mainly describe an example in which user A accesses workflow sharing device 2 to create a workflow and distributes the created workflow to other users.

[0033] Figure 2 shows an example of the hardware configuration of the workflow sharing device 2. The workflow sharing device 2 comprises a processor 10, a storage unit 11, and a communication interface 12. The processor 10 comprises a CPU 10a and a memory 10b. The CPU 10a reads and executes the program 13 stored in the storage unit 11. The memory 10b is a volatile storage device that stores temporary data generated when the CPU 10a executes the program 13. The storage unit 11 is a non-volatile storage device composed of a hard disk drive (HDD) or a solid-state drive (SSD). In addition to the program 13, the storage unit 11 stores user information 14, a workflow database 15, history information 16, and flag registration information 17.

[0034] Figure 3 shows an example of user information 14. User information is information that registers information about users who use the workflow sharing device 2. In other words, user information 14 is information that associates the usernames and user attributes of users A to H who use the workflow sharing device 2. User attributes are information that registers the organizations (teams or groups) to which each user A to H belongs. By referring to user information 14, the workflow sharing device 2 can recognize the teams and groups to which each user A to H belongs.

[0035] Figure 4 shows an example of the functional configuration of the workflow sharing device 2. When the CPU 10a of the processor 10 executes program 13, the processor 10 functions as a workflow creation unit 20, a flag assignment unit 21, a history management unit 22, a flag management unit 23, and a distribution unit 24. The distribution unit 24 also includes a setting value deletion unit 25.

[0036] The workflow creation unit 20 is a processing unit that creates a workflow in which multiple tasks are executed in a predetermined order based on user instructions and operations. The workflow creation unit 20 has functions such as a web server, and when it detects access from the information processing terminal 4 operated by each user, it performs user authentication. If user authentication is successful and the user can be identified, the workflow creation unit 20 provides the information processing terminal 4 operated by the user with a workflow creation screen for creating a workflow, and creates the workflow based on the operation information received from the information processing terminal 4.

[0037] Figure 5 shows an example of a workflow creation screen 30 provided by the workflow creation unit 20. The workflow creation screen 30 displays a task list 31, a workflow creation field 32, and a settings table editing button 33. The task list 31 displays a list of multiple tasks that can be incorporated into a workflow. In the example screen in Figure 5, multiple task icons 31a to 31g are displayed in the task list 31. The user can create a workflow in the workflow creation field 32 by repeatedly dragging the desired task icon from the multiple task icons 31a to 31g displayed in the task list 31 and dropping it into the workflow creation field 32. In other words, the workflow creation unit 20 constructs a workflow that executes multiple tasks sequentially according to the order in which the task icons are dropped into the workflow creation field 32 by the user.

[0038] Figure 5 shows an example where a user first drops the "Receive Fax" task icon 31d, then the "Save to Storage" task icon 31e, and finally the "Send Email" task icon 31f into the workflow creation field 32, thereby creating a workflow in which three tasks are automatically executed in the order of "Receive Fax" → "Save to Storage" → "Send Email".

[0039] Tasks incorporated into a workflow have pre-configured settings. Therefore, by clicking on task icons 31d, 31e, and 31f, which are dropped into the workflow creation area 32, the user can transition the workflow creation screen 30 to a settings input screen where they can set the desired settings for each task's settings. By performing operations on this settings input screen, the user can set the desired settings for each operation item. Alternatively, by using the settings table edit button 33 displayed on the workflow creation screen 30, the user can display the settings table editing screen on the workflow creation screen 30 and input the desired settings by performing operations on that editing screen.

[0040] Figure 6 shows an example of the workflow settings table editing screen 35. In the workflow settings table editing screen 35, multiple tasks are listed in the order they were dropped into the workflow creation field 32. In this editing screen 35, the user can enter desired settings for each task's settings. For example, the task "FAX Reception" has a setting item called "Receiving Device," and the user can set the IP address of the receiving device in the setting value field. Also, the task "Storage Save" has three setting items: "Destination URL," "ID," and "PW," and the user can set desired settings for these items. The setting item "Destination URL" is necessary to access the storage where the data will be saved. The user sets the URL of the desired storage as the setting value for the setting item "Destination URL." The setting items "ID" and "PW" are information for automatically logging into the storage at the URL set by the user. The user sets their own user ID and password as the setting values ​​for the setting items "ID" and "PW." Furthermore, the task "Send Email" has a setting item called "Recipient Address," and the user enters the address to which the email will be sent in the setting value field.

[0041] For example, the workflow shown in editing screen 35 in Figure 6 is a workflow created by user A, and it defines a series of processes in which, when the image processing device 3a receives image data by fax, it saves the image data to storage managed by Team TA, and then attaches the image data to an email address shared by Team TA and sends it. Therefore, in editing screen 35 shown in Figure 6, the IP address of the image processing device 3a is set as the value of the "receiving device" setting item for task "fax reception", the URL for accessing the storage managed by Team TA is set as the value of the "save destination URL" setting item for task "storage save", the user ID and password of user A are set as the values ​​of the "ID" and "PW" setting items, and the email address shared by Team TA is set as the value of the "recipient address" setting item for task "email sending".

[0042] The workflow creation unit 20 creates a workflow that executes multiple tasks in an order specified by the user, based on the user's configuration operations, and sets the user-specified setting values ​​for the setting items of each task.

[0043] The flag assignment unit 21 is a processing unit that individually assigns a delete flag or a retain flag to the setting value set for each setting item of each task included in the workflow. As shown in Figure 6, the editing screen 35 of the workflow setting table is provided with a flag setting field. This flag setting field has three setting fields: same team, same group, and outside the group. Each of these three setting fields displays a delete button 36 for setting a delete flag and a retain button 37 for setting a retain flag.

[0044] The delete flag and retain flag determine whether to delete or retain the settings for each task's configuration item when a workflow is distributed to a user different from the creator, based on the attributes of the user designated as the recipient. The delete flag specifies that the settings should be deleted when the workflow is distributed. The retain flag specifies that the settings should be retained when the workflow is distributed. In the settings fields for the same team, the same group, and outside the group, users can choose either the delete button 36 or the retain button 37, and only one of the delete flag or retain flag can be set.

[0045] The delete flag set for "Same Team" specifies that if a user designated as a recipient of the workflow is on the same team as the user who created the workflow, the setting value will be deleted. For example, if the setting values ​​for the "ID" and "PW" fields of the task "Storage Save" are the user ID and password of the user who created the workflow, it is advisable to set the delete flag to prevent other users from using that user ID and password. When the delete flag is set for "Same Team," the setting value of the relevant field is automatically deleted when the workflow is distributed to another user who is on the same team as the user who created the workflow. Therefore, the user who created the workflow does not need to manually delete the setting value when distributing the workflow to another user, resulting in improved usability.

[0046] The "Retain same team" flag specifies that if the user designated as the recipient of the workflow is on the same team as the user who created the workflow, the settings will be retained. For example, the "Receiving device" setting for the task "FAX reception" and the "Save destination URL" setting for the task "Storage save" are information that can be shared within the same team, so it is preferable to set the "Retain same team" flag. When the "Retain same team" flag is set, and the workflow is distributed to another user who is on the same team as the user who created the workflow, the settings for those items will not be automatically deleted but will be retained. Therefore, users who receive the workflow do not need to set the settings themselves and can reuse the settings set by the user who created the workflow, thus improving convenience.

[0047] The delete flag set for the same group specifies that the settings will be deleted if the user designated as the recipient of the workflow belongs to the same group as the user who created the workflow. For example, if the settings for "ID" and "PW" in the task "Storage Save" are the user ID and password of the user who created the workflow, it is preferable to set the delete flag to prevent other users from using the user ID and password. When the delete flag is set for the same group, the settings for those settings will be automatically deleted when the workflow is distributed to another user who belongs to the same group as the user who created the workflow. Therefore, the user who created the workflow does not need to manually delete the settings when distributing the workflow to another user, resulting in improved usability. Furthermore, if the delete flag is set for the same team, it is preferable to automatically set the delete flag for the same group as well.

[0048] The "Retain" flag set for the same group specifies that if the user designated as the recipient of the workflow belongs to the same group as the user who created the workflow, the settings will be retained. For example, the "Receiving Device" setting for the task "FAX Reception" and the "Destination URL" setting for the task "Storage Save" are information that can be shared within the same group, so it is preferable to set the "Retain" flag for them. When the "Retain" flag is set for the same group, if the workflow is distributed to another user who belongs to the same group as the user who created the workflow, the settings for those settings will not be automatically deleted but will be retained. Therefore, users who receive the workflow do not need to set the settings themselves and can reuse the settings set by the user who created the workflow, thus improving convenience.

[0049] The delete flag set outside the group specifies that if the user designated as the recipient of the workflow belongs to a different group than the user who created the workflow, the setting value should be deleted. It is preferable to set the retain flag if the setting item "Receiving device" for the task "FAX reception" or the setting item "Save destination URL" for the task "Storage save" is information that can only be shared within the same group. When the delete flag outside the group is set, the setting value of the relevant setting item is automatically deleted when the workflow is distributed to another user belonging to a different group than the user who created the workflow. Therefore, the user who created the workflow does not need to manually delete the setting value when distributing the workflow to another user, resulting in improved usability.

[0050] The "Retain outside group" flag, set to "Outside group," specifies that if the user designated as the recipient of the workflow belongs to a different group than the user who created the workflow, the setting value should be retained. When the "Retain outside group" flag is set, and the workflow is distributed to another user belonging to a different group than the user who created the workflow, the setting value for that item is not automatically deleted but is retained. Therefore, users receiving the workflow do not need to set the setting value themselves and can reuse the setting value set by the user who created the workflow, thus improving convenience.

[0051] The flagging unit 21 sets either a delete flag or a save flag based on the user's button operations on the editing screen 35 of the workflow settings table for each setting field within the same team, the same group, and outside the group. When the user finishes setting flags and operates the edit completion button 38, the flagging unit 21 finishes setting flags. When the user operates the edit completion button 38, the workflow creation unit 20 creates workflow setting data based on the user's editing operations and registers and manages that workflow setting data in the workflow database 15.

[0052] Figure 7 shows an example of workflow setting data 41 created by the workflow creation unit 20. The workflow setting data 41 shown in Figure 7 is data that executes multiple tasks specified by the user in the order specified by the user. Specifically, when a fax is received by the receiving device (image processing device 3a) specified by the user, the received image data is saved to the storage specified by the storage destination URL, and then the image data is sent by email to the destination specified by the recipient address. This workflow setting data 41 includes setting values ​​for the setting items of each task. Therefore, the workflow sharing device 2 can automatically execute each task based on the setting values ​​set for each setting item when the workflow is executed.

[0053] Furthermore, the workflow setting data 41 includes flags assigned by the flag assignment unit 21. In the example in Figure 7, the setting item "Receiving device" for the task "Receiving fax" has a retain flag set for the same team, a retain flag set for the same group, and a delete flag set for outside the group. The same flag settings are also applied to the setting item "Destination URL" for the task "Storage save". On the other hand, the setting items "ID" and "PW" for the task "Storage save" have delete flags set for the same team, the same group, and outside the group. The same flag settings are also applied to the setting item "Recipient address" for the task "Sending email".

[0054] Furthermore, the workflow configuration data 41 includes creator information 42 to identify the user who created the workflow. Creator information 42 may be a username, or it may be any other information that can identify the user. In Figure 7, it is recorded that the workflow configuration data 41 was created by user A.

[0055] In the example in Figure 7, either a delete flag or a keep flag is recorded for all setting items of each task included in the workflow. However, when a user performs operations on the editing screen 35, they may forget to flag all setting items. Figure 8 shows an example of workflow setting data 41 when some setting items are not flagged. In the example in Figure 8, user A does not flag the setting item "Recipient Address" for the task "Send Email".

[0056] If the user creating the workflow does not set flags for all setting items, the flagging unit 21 can activate the history management unit 22 or the flag management unit 23 to automatically set a delete flag or a retain flag for the setting values ​​of the setting items that have not been flagged.

[0057] The history management unit 22 records and manages the setting values ​​for each setting item of each task included in the workflow, along with the deletion flag or retention flag assigned to that setting value, in the history information 16 each time a workflow is created by a user. The history information 16 is information that has been accumulated and recorded for each setting item of each task and the flags assigned to that setting value in workflows previously created by each user. The history management unit 22 manages such history information 16 for each user who creates a workflow. Therefore, if the user has not set a flag for some of the setting items of the setting items of each task included in the workflow, the flag assignment unit 21 can automatically assign a deletion flag or retention flag by referring to the history information 16. For example, when a new workflow is created by the workflow creation unit 20, the flag assignment unit 21 identifies the setting items and setting values ​​of tasks for which the user has not set a flag. The flag assignment unit 21 then reads the history information 16 managed by the history management unit 22 and determines whether the same task as the task for which the flag was not set is recorded in the history information 16. If the same task is recorded in the history information 16, the flag assignment unit 21 identifies whether the flag set in the setting value of the setting item in the history information 16 is a delete flag or a retain flag, and automatically assigns the identified flag to the setting value of the setting item.

[0058] In this case, the flag assignment unit 21 may determine whether the setting item has the same setting value as the one previously set by the user, and may automatically assign the same flag as the one previously set by the user, provided that the same setting value is set in the current workflow as well. For example, if the user has set their personal email address as the recipient address for emails in a previous workflow, and has set their personal email address in the current workflow as well, the flag assignment unit 21 will automatically assign the flag by adopting the same flag as the one recorded in the history information 16. On the other hand, if the user has set their personal email address as the recipient address for emails in a previous workflow, but has set an email address shared by the team TA instead of their personal email address in the current workflow, the flag assignment unit 21 will not automatically assign the same flag as the one recorded in the history information 16.

[0059] As described above, the flagging unit 21 can update the workflow setting data 41 shown in Figure 8 to the workflow setting data 41 shown in Figure 7 by automatically assigning flags based on the history information 16 managed by the history management unit 22. In other words, the flagging unit 21 can automatically assign a delete flag or a retain flag to the setting items and setting values ​​of tasks for which the user has not set a flag.

[0060] The flag management unit 23 manages flag registration information 17 that is pre-set by the user. Figure 9 shows an example of flag registration information 17. Flag registration information 17 is information that is pre-set, including tasks that can be incorporated into a workflow, task settings, and default flags to be set for the same team, the same group, and outside the group for each of the task settings. For example, this information is created for each user. Therefore, if the user has not set a flag for some of the settings of the settings of the tasks included in the workflow, the flag assignment unit 21 can automatically assign a delete flag or a retain flag by referring to the flag registration information 17. For example, when a new workflow is created by the workflow creation unit 20, the flag assignment unit 21 identifies the settings and settings of tasks for which the user has not set a flag. The flag assignment unit 21 then reads the flag registration information 17 managed by the flag management unit 23 and automatically assigns the default flags registered in the flag registration information 17 as flags for the identified settings. In this way, the flag assignment unit 21 can update the workflow setting data 41 shown in Figure 8 to the workflow setting data 41 shown in Figure 7 by automatically assigning flags based on the flag registration information 17 managed by the flag management unit 23. In other words, the flag assignment unit 21 can automatically assign a delete flag or a retain flag to the setting items and setting values ​​of tasks for which the user has not set a flag.

[0061] Furthermore, if the user fails to flag some of the setting values ​​for certain tasks included in the workflow, the flagging unit 21 may display an operation screen where the user can set a delete flag or a retain flag, allowing the user to set the flag again. Figure 10 shows an example of an operation screen 39 for the user to set a flag. The operation screen 39 shown in Figure 10 is displayed, for example, as a warning screen when the user fails to flag some of the setting values ​​for certain setting items. As a result, the user becomes aware that some setting values ​​for certain setting items have been flagged. The user can then perform an operation on the operation screen 39 to set either a delete flag or a retain flag for the same team, the same group, and outside the group, respectively. Based on the user's operation on the operation screen 39, the flagging unit 21 can flag the setting values ​​of the setting items that have not been flagged.

[0062] Furthermore, when the workflow sharing device 2 displays the editing screen 35 of the workflow setting table, it may display it with either the delete flag or the retain flag temporarily selected based on the history information 16 or the flag registration information 17. Figure 11 shows an example of the editing screen 35 displayed with either the delete flag or the retain flag temporarily selected. For example, in the editing screen 35 shown in Figure 11, the workflow sharing device 2, based on the history information 16 or the flag registration information 17, displays the delete button 36 and grays out the retain button 37 when displaying the setting value of a setting item of a task incorporated into the workflow with the delete flag temporarily selected. Conversely, when displaying the setting value of a setting item of a task incorporated into the workflow with the retain flag temporarily selected, it displays the retain button 37 and grays out the delete button 36. This allows the user to understand whether the delete flag or the retain flag is temporarily selected by looking at the editing screen 35. If the user needs to change the flag setting of the temporarily selected state, they can change the flag setting by operating either the delete button 36 or the retain button 37. Furthermore, if the user does not need to change the flag setting of the temporarily selected flag, they do not need to operate the delete button 36 or the keep button 37. Therefore, by displaying the editing screen 35 with the flag temporarily selected based on the history information 16 or flag registration information 17 when the editing screen 35 is displayed, it is possible to reduce the operational burden on the user when setting flags. As a result, when the user operates the edit end button 38, the workflow creation unit 20 can generate workflow setting data 41 as shown in Figure 7, and there will be no omissions in the user's flag setting. The workflow creation unit 20 can then register the workflow setting data 41, which has no omissions in the flag setting, in the workflow database 15.

[0063] Furthermore, the flag management unit 23 may change the default flag in the flag registration information 17 if the number of times a flag other than the delete flag or retain flag set as the default flag in the flag registration information 17 is selected by the same user reaches a predetermined number of times. For example, if the delete flag is set as the default flag in the flag registration information 17, and the number of times the user selects the retain flag by performing operations on the editing screen 35 reaches a predetermined number of times, the flag management unit 23 will change the default flag in the flag registration information 17 from the delete flag to the retain flag. Such processing is performed individually for each flag within the same team, the same group, and outside the group. Therefore, the user does not need to perform operations to change the default flag registered in the flag registration information 17, and the operational burden is reduced. Note that the predetermined number of times in this case may be one or two or more times.

[0064] Once the workflow is registered in the workflow database 15 as described above, the workflow sharing device 2 becomes capable of executing multiple tasks incorporated into the workflow. For example, when the workflow configuration data 41 shown in Figure 7 is registered in the workflow database 15, the workflow sharing device 2 begins to constantly monitor the fax reception status of the image processing device 3a. Subsequently, as the image processing device 3a receives a fax, the workflow sharing device 2 executes processing based on the workflow. That is, the workflow sharing device 2 acquires the image data received from the image processing device 3a, automatically logs into the storage configured in the workflow to save the image data, and then sends an email with the image data attached to the recipient address configured in the workflow.

[0065] Furthermore, workflows registered in the workflow database 15 can only be accessed by the user who created them, and the workflows can be re-edited. However, if a workflow is distributed to another user by the user who created it, a copy of the workflow setting data 41 is created, and the copied data is registered and saved in the workflow database 15. At this time, the copied data can only be accessed by the user designated as the recipient. The user designated as the recipient of the workflow can then edit the distributed workflow by accessing the workflow sharing device 2 using their own information processing terminal 4. At this time, the user can use each task incorporated into the workflow as is.

[0066] Next, the distribution unit 24 functions when the user who created the workflow instructs that the workflow be distributed to another user. The distribution unit 24 copies the workflow configuration data 41 specified by the user who created the workflow to generate distribution data and registers and saves it in the workflow database 15.

[0067] The distribution unit 24 includes a setting value deletion unit 25. When a workflow is distributed to other users, the setting value deletion unit 25 determines whether a deletion flag has been assigned to the setting values ​​set for each task, and deletes the setting values ​​with the deletion flag from the workflow setting data 41. The setting value deletion unit 25 does not delete setting values ​​with the retention flag assigned from the workflow setting data 41. Therefore, when the distribution unit 24 copies the workflow setting data 41 to generate data for distribution, it can generate data in which the setting values ​​assigned to each task have the deletion flag removed.

[0068] Furthermore, when a workflow is distributed to other users, the setting value deletion unit 25 reads the user information 14, compares the attributes of the user designated as the recipient with the attributes of the user who created the workflow, and determines whether the relationship between the workflow creator and the recipient user is that of the same team, the same group, or outside the group. Based on the determination result, the setting value deletion unit 25 deletes the setting values. For example, if the workflow creator and the recipient user are on the same team, the setting value deletion unit 25 refers to the same team flag setting and deletes the setting values ​​that have the delete flag set, while retaining the setting values ​​that have the retain flag set. Also, if the workflow creator and the recipient user are not on the same team but are in the same group, the setting value deletion unit 25 refers to the same group flag setting and deletes the setting values ​​that have the delete flag set, while retaining the setting values ​​that have the retain flag set. Furthermore, if the workflow creator and the recipient user are not in the same group, the setting value deletion unit 25 refers to the outside-group flag setting and deletes the setting values ​​that have the delete flag set, while retaining the setting values ​​that have the retain flag set. Therefore, when a workflow is distributed, the user who created the workflow does not need to manually delete settings that cannot be shared with the recipient users, thus reducing the user's workload.

[0069] Figure 12 shows an example of workflow configuration data 41 generated when user A distributes a workflow created by user A to other users B or E. For example, if user A designates user B, who belongs to the same team, as the recipient user, the setting value deletion unit 25 deletes all setting values ​​that have a deletion flag set in the same team column. In this case, when the workflow is distributed, workflow configuration data 41 as shown in Figure 12(a) is automatically generated from the workflow configuration data 41 shown in Figure 7, for example. Also, if user A designates user E, who is outside the group, as the recipient user, the setting value deletion unit 25 deletes all setting values ​​that have a deletion flag set in the outside group column. In this case, when the workflow is distributed, workflow configuration data 41 as shown in Figure 12(b) is automatically generated from the workflow configuration data 41 shown in Figure 7, for example.

[0070] The distribution unit 24 then generates distribution data based on the workflow setting data 41 shown in Figures 12(a) and (b), and registers and saves it in an area of ​​the workflow database 15 that is accessible to the recipient user. This prevents the settings set by the workflow creator from being used by another user, and also solves the problem of information being leaked to users in other groups.

[0071] Next, an example of a processing procedure by the workflow sharing device 2 described above will be explained. Figures 13 to 16 are flowcharts showing an example of a basic processing procedure by the workflow sharing device 2. This processing procedure is carried out sequentially by the CPU 10a of the processor 10 in the workflow sharing device 2 executing program 13.

[0072] First, as shown in Figure 13, the workflow sharing device 2 performs user authentication (step S1). If the user can be identified during user authentication, the workflow sharing device 2 performs the workflow creation process (step S2). The workflow creation process performed by the workflow sharing device 2 allows the user to create a new workflow. Next, the workflow sharing device 2 performs the workflow distribution process (step S3). The workflow distribution process performed by the workflow sharing device 2 allows the user to distribute and share the created workflow with other users.

[0073] Figure 14 is a flowchart showing an example of a detailed processing procedure for the workflow creation process (step S2). When the workflow sharing device 2 starts the workflow creation process, it accepts the user's task placement operation on the workflow creation screen (step S10) and places multiple tasks based on the user's task placement operation (step S11). Subsequently, the workflow sharing device 2 accepts the user's setting value input operation (step S12) and sets the entered setting values ​​in the setting items of each task (step S13). After that, the workflow sharing device 2 performs a flag setting process (step S14). The flag setting process is the process of setting a delete flag or a retain flag in the setting values ​​set in the setting items of each task included in the workflow. When the workflow sharing device 2 finishes the flag setting process, it registers and saves the workflow in the workflow database 15 (step S15). This completes the workflow creation process.

[0074] Figure 15 is a flowchart showing an example of a detailed processing procedure for the flag setting process (step S14). When the workflow sharing device 2 starts the flag setting process, it uses the history information 16 to determine whether or not to set the delete flag or the retain flag to a provisional selection state (step S20). For example, if the user has selected provisional selection mode, the workflow sharing device 2 decides to use the history information 16. Conversely, if the user has not selected provisional selection mode, the workflow sharing device 2 decides not to use the history information 16. If the history information 16 is to be used (YES in step S20), the workflow sharing device 2 reads the information of the workflow creation user from the history information 16 stored in the storage unit 11 (step S21) and determines whether or not there is a usage history for the same task as the task incorporated into the workflow in the workflow creation process (step S2) (step S22). As a result, if there is a usage history for the same task (YES in step S22), the workflow sharing device 2 automatically sets the delete flag or the retain flag to a provisional selection state for the setting value of the setting item of the task incorporated into the workflow (step S23). If history information is not used (NO in step S20), or if there is no usage history for the same task (NO in step S22), the process in step S23 is skipped.

[0075] Next, the workflow sharing device 2 determines whether or not it has detected a flag setting operation by the user (step S24). If a flag setting operation is detected (YES in step S24), the workflow sharing device 2 determines whether or not the flag specified by the user is a delete flag (step S25). If it is a delete flag (YES in step S25), the workflow sharing device 2 assigns the delete flag to the setting value of the setting item specified by the user (step S26). On the other hand, if it is not a delete flag (NO in step S25), the workflow sharing device 2 assigns the retain flag to the setting value of the setting item specified by the user (step S27). The workflow sharing device 2 then records the flag set by the user in the history information 16 along with the setting item and setting value for each task (step S28). Finally, the workflow sharing device 2 determines whether or not the user's flag setting operation has finished (step S29). For example, if the user operates the edit end button 38 on the editing screen 35 in Figure 6, the workflow sharing device 2 determines that the user's flag setting operation has finished. If the user has not finished setting the flag (NO in step S29), the workflow sharing device 2 returns to step S24, and the process described above is repeated. As the processes in steps S24 to S28 are repeated, a delete flag or a retain flag is assigned to the setting value of the setting item for each task included in the workflow, based on the user's instructions.

[0076] If the user has finished setting the flag (YES in step S29), the workflow sharing device 2 determines whether there are any settings that have not been flagged (step S30). If there are settings that have not been flagged (YES in step S30), the workflow sharing device 2 refers to the flag registration information 17 (step S31) and automatically sets the delete flag or retain flag, which are registered as default flags in the flag registration information 17, to the settings that have not been flagged (step S32). If there are no settings that have not been flagged (NO in step S30), the processes in steps S31 and S32 are not performed. This completes the flag setting process.

[0077] Next, Figure 16 is a flowchart showing an example of a detailed processing procedure for the workflow distribution process (step S3). When the workflow sharing device 2 starts the workflow distribution process, it reads the workflow specified by the user (step S40) and determines whether there are any settings items in each task included in that workflow that are not flagged (step S41). If there are settings items that are not flagged (YES in step S41), the workflow sharing device 2 performs the flag setting process (step S42). The details of this flag setting process are the same as the flowchart shown in Figure 15. If there are no settings items that are not flagged (NO in step S41), the process in step S42 is skipped.

[0078] The workflow sharing device 2 identifies the distribution destination user specified by the user (step S43) and reads the user information 14 (step S44). Based on the user information 14, the workflow sharing device 2 detects the attributes of the distribution destination user (step S45). This determines whether the distribution destination user is on the same team or in the same group as the user who created the workflow. Then, based on the flag settings in the workflow setting data 41, the workflow sharing device 2 deletes the setting values ​​set for each task setting item included in the workflow (step S46). For example, if the distribution destination user is on the same team as the workflow creator, the workflow sharing device 2 deletes the setting value of the setting item that has the delete flag set as a flag setting for being on the same team. Also, if the distribution destination user is not on the same team as the workflow creator but is in the same group, the workflow sharing device 2 deletes the setting value of the setting item that has the delete flag set as a flag setting for being in the same group. Furthermore, if the distribution destination user is neither on the same team nor in the same group as the workflow creator, the workflow sharing device 2 deletes the setting value of the setting item that has the delete flag set as a flag setting for being outside the group.

[0079] Subsequently, the workflow sharing device 2 packages the workflow with the settings removed to generate distribution data (step S47), and distributes the workflow by saving it to a storage area accessible to the recipient user (step S48). This completes the workflow distribution process.

[0080] As described above, the workflow sharing system 1 of this embodiment comprises a workflow creation unit 20 that sets setting values ​​for each setting item of each task when creating a workflow that executes multiple tasks in a predetermined order, a flag setting unit 21 that individually assigns a delete flag or a retain flag to the setting values ​​set for each setting item of each task, and a setting value deletion unit 25 that, when the workflow is distributed to other users, determines whether a delete flag has been assigned to the setting values ​​set for each setting item of each task and deletes the setting values ​​that have the delete flag assigned. With this configuration, when the user who created the workflow distributes and shares it with other users, the user does not need to manually delete the setting values. Therefore, the operational burden on the user can be reduced when distributing the workflow.

[0081] Furthermore, in the workflow sharing system 1 described above, the flagging unit 21 is configured to assign a delete flag or a retain flag to the setting value set for each setting item of each task, based on the attributes of the user to whom the workflow is distributed. The setting value deletion unit 25 is configured to determine whether a delete flag has been assigned to the setting value set for each setting item of each task, based on the attributes of the user designated as the destination of the workflow. With this configuration, it is possible to decide whether or not to delete the setting value based on the attributes of the user designated as the destination when distributing the workflow.

[0082] Preferred embodiments of the present invention have been described above. However, the present invention is not limited to those described in the above embodiments, and various modifications are applicable.

[0083] For example, the above embodiment illustrates a case where the above-described process is executed in a workflow sharing device 2 configured as a server device. However, it is not limited to this. For example, the information processing terminal 4 used by users A to H may be configured to execute the above-described process by installing an application that executes the process described in the above embodiment on the information processing terminal 4. In this case, program 13 is installed on the information processing terminal 4, and the information processing terminal 4 executes the above-described process by running program 13.

[0084] Furthermore, Program 13 is not limited to being pre-installed on the workflow sharing device 2 or the information processing terminal 4. In other words, Program 13 may be the subject of a transaction on its own. In this case, Program 13 may be provided in a form that can be downloaded via a network 5 such as the Internet, or it may be provided recorded on a computer-readable recording medium such as a CD-ROM.

[0085] Furthermore, in the above embodiment, when setting flags on the setting values ​​of the setting items of each task included in the workflow, an example was described in which a delete flag or a retain flag is set for each of the multiple flag setting fields such as same team, same group, and outside the group. However, it is not limited to this. For example, each task's setting item may have only one of either a delete flag or a retain flag set. In this case, the setting value deletion unit 25 should be configured to determine whether the attributes of the user designated as the destination of the workflow are different from the attributes of the workflow creator, and if they are different, delete the setting value to which the delete flag has been set. [Explanation of Symbols]

[0086] 1. Workflow Sharing System 2. Workflow Sharing Device 3(3a,3b) Image processing device 4. Information Processing Terminals 10 Processors 13 Programs 16. History Information 17 Flag Registration Information 20 Workflow Creation Department 21 Flag assignment section 22 History Management Department 23 Flag Management Department 24 Distribution Department 25 Setting value deletion section

Claims

1. When creating a workflow that executes multiple tasks in a predetermined order, the workflow creation unit sets the setting values ​​for each setting item of each task, A flagging unit that individually assigns a delete flag or a retain flag to the setting value set for each setting item of each task, When the aforementioned workflow is distributed to other users, a setting value deletion unit determines whether the deletion flag has been assigned to the setting value set for each task setting item, and deletes the setting value to which the deletion flag has been assigned. A history management unit records and manages the setting value for each setting item of each task and the deletion flag or retention flag attached to that setting value in the history information, Equipped with, The workflow sharing system is characterized in that, when a new workflow is created by the workflow creation unit, and a task recorded in the history information is selected, the flag assignment unit automatically assigns the delete flag or the retain flag to the setting value for each setting item of the task based on the history information.

2. When creating a workflow that executes multiple tasks in a predetermined order, the workflow creation unit sets the setting values ​​for each setting item of each task, A flagging unit that individually assigns a delete flag or a retain flag to the setting value set for each setting item of each task, When the aforementioned workflow is distributed to other users, a setting value deletion unit determines whether the deletion flag has been assigned to the setting value set for each task setting item, and deletes the setting value to which the deletion flag has been assigned. A history management unit records and manages the setting value for each setting item of each task and the deletion flag or retention flag attached to that setting value in the history information, Equipped with, The workflow sharing system is characterized in that, when a new workflow is created by the workflow creation unit, a task recorded in the history information is selected and the same setting value as the setting value recorded in the history information is set, the flag assignment unit automatically assigns the delete flag or the retain flag to the setting value based on the history information.

3. The workflow sharing system according to claim 1 or 2, characterized in that the setting value deletion unit retains the setting values ​​to which the retention flag is assigned without deleting them when the workflow is distributed to other users.

4. The workflow sharing system according to claim 1 or 2, characterized in that the setting value deletion unit deletes the setting value to which the deletion flag has been assigned when the attributes of the user who created the workflow and the attributes of the user designated as the recipient of the workflow are different from each other.

5. The workflow sharing system according to claim 4, characterized in that the user's attributes include the group to which the user belongs.

6. The workflow creation unit is characterized by setting user-specified setting values ​​for each task's setting items, as described in claim 1 or 2 of the workflow sharing system.

7. The workflow sharing system according to claim 1 or 2, characterized in that the history management unit manages the history information for each user who creates a workflow.

8. When creating a workflow that executes multiple tasks in a predetermined order, the workflow creation unit sets the setting values ​​for each setting item of each task, A flagging unit that individually assigns a delete flag or a retain flag to the setting value set for each setting item of each task, When the aforementioned workflow is distributed to other users, a setting value deletion unit determines whether the deletion flag has been assigned to the setting value set for each task setting item, and deletes the setting value to which the deletion flag has been assigned. A flag management unit manages flag registration information for which the deletion flag or the retention flag has been set in advance for each task's setting item, Equipped with, The flag assignment unit automatically assigns the delete flag or the retain flag to the setting value set for each setting item of each task included in the workflow, based on the flag registration information. The workflow sharing system is characterized in that the flag management unit manages the flag registration information for each user, and when the number of times a flag other than the delete flag or the retain flag set in the flag registration information is selected by the same user reaches a predetermined number of times, the delete flag or the retain flag set in the flag registration information is changed.

9. A workflow sharing method for sharing a workflow that executes multiple tasks in a predetermined order among multiple users, When creating the aforementioned workflow, a workflow creation step is performed in which setting values ​​are set for each setting item of the tasks included in the workflow, A flagging step which involves individually assigning a delete flag or a retain flag to the setting value set for each setting item of the workflow included in the aforementioned workflow, When the workflow is distributed to other users, the workflow includes a step to delete settings, which determines whether the deletion flag has been assigned to the setting value set for each setting item of the workflow, and deletes the setting value to which the deletion flag has been assigned. A history management step that records and manages the setting value for each setting item of each task and the deletion flag or retention flag attached to that setting value in the history information, It has, The workflow sharing method is characterized in that, when a new workflow is created by the workflow creation step, and a task recorded in the history information is selected, the delete flag or the retain flag is automatically assigned to the setting value for each setting item of the task based on the history information.

10. A workflow sharing method for sharing a workflow that executes multiple tasks in a predetermined order among multiple users, When creating the aforementioned workflow, a workflow creation step is performed in which setting values ​​are set for each setting item of the tasks included in the workflow, A flagging step which involves individually assigning a delete flag or a retain flag to the setting value set for each setting item of the workflow included in the aforementioned workflow, When the workflow is distributed to other users, the workflow includes a step to delete settings, which determines whether the deletion flag has been assigned to the setting value set for each setting item of the workflow, and deletes the setting value to which the deletion flag has been assigned. A history management step that records and manages the setting value for each setting item of each task and the deletion flag or retention flag attached to that setting value in the history information, It has, The workflow sharing method is characterized in that, when a new workflow is created by the workflow creation step, a task recorded in the history information is selected and the same setting value as the setting value recorded in the history information is set, the delete flag or the retain flag is automatically assigned to the setting value based on the history information.

11. A workflow sharing method for sharing a workflow that executes multiple tasks in a predetermined order among multiple users, When creating the aforementioned workflow, a workflow creation step is performed in which setting values ​​are set for each setting item of the tasks included in the workflow, A flagging step which involves individually assigning a delete flag or a retain flag to the setting value set for each setting item of the workflow included in the aforementioned workflow, When the workflow is distributed to other users, the workflow includes a step to delete settings, which determines whether the deletion flag has been assigned to the setting value set for each setting item of the workflow, and deletes the setting value to which the deletion flag has been assigned. A flag management step that manages flag registration information for which the deletion flag or the retention flag has been set in advance for each task setting item, It has, The flag assignment step automatically assigns the delete flag or the retain flag to the setting value set for each setting item of each task included in the workflow, based on the flag registration information. The aforementioned flag management step is characterized by managing the flag registration information for each user, and if the number of times a flag different from the delete flag or the retain flag set in the flag registration information is selected by the same user reaches a predetermined number of times, the delete flag or the retain flag set in the flag registration information is changed.

12. On the computer, When creating a workflow that executes multiple tasks in a predetermined order, the workflow creation step involves setting setting values ​​for each setting item of the tasks included in the workflow, A flagging step which involves individually assigning a delete flag or a retain flag to the setting value set for each setting item of the workflow included in the aforementioned workflow, When the workflow is distributed to other users, the workflow includes a step to delete settings, which determines whether the deletion flag has been assigned to the setting value set for each setting item of the workflow, and deletes the setting value to which the deletion flag has been assigned. A history management step that records and manages the setting value for each setting item of each task and the deletion flag or retention flag attached to that setting value in the history information, Make it run, The flag assignment step is a program characterized in that, when a new workflow is created by the workflow creation step, and a task recorded in the history information is selected, the program automatically assigns the delete flag or the retain flag to the setting value for each setting item of the task based on the history information.

13. On the computer, When creating a workflow that executes multiple tasks in a predetermined order, the workflow creation step involves setting setting values ​​for each setting item of the tasks included in the workflow, A flagging step which involves individually assigning a delete flag or a retain flag to the setting value set for each setting item of the workflow included in the aforementioned workflow, When the workflow is distributed to other users, the workflow includes a step to delete settings, which determines whether the deletion flag has been assigned to the setting value set for each setting item of the workflow, and deletes the setting value to which the deletion flag has been assigned. A history management step that records and manages the setting value for each setting item of each task and the deletion flag or retention flag attached to that setting value in the history information, Make it run, The flag assignment step is a program characterized in that, when a new workflow is created by the workflow creation step, a task recorded in the history information is selected and the same setting value as the setting value recorded in the history information is set, the program automatically assigns the delete flag or the retain flag to the setting value based on the history information.

14. On the computer, When creating a workflow that executes multiple tasks in a predetermined order, the workflow creation step involves setting setting values ​​for each setting item of the tasks included in the workflow, A flagging step which involves individually assigning a delete flag or a retain flag to the setting value set for each setting item of the workflow included in the aforementioned workflow, When the workflow is distributed to other users, the workflow includes a step to delete settings, which determines whether the deletion flag has been assigned to the setting value set for each setting item of the workflow, and deletes the setting value to which the deletion flag has been assigned. A flag management step that manages flag registration information for which the deletion flag or the retention flag has been set in advance for each task setting item, Make it run, The flag assignment step automatically assigns the delete flag or the retain flag to the setting value set for each setting item of each task included in the workflow, based on the flag registration information. The flag management step is a program that manages the flag registration information for each user, and when the number of times a flag other than the delete flag or the retain flag set in the flag registration information is selected by the same user reaches a predetermined number of times, the program changes the delete flag or the retain flag set in the flag registration information.

Images