EAI process flow management device, method for managing EAI process flow, and EAI process flow management program

Abstract

To provide an EAI process flow management device, a method for managing an EAI process flow, and an EAI process flow management program capable of managing versions of inheritance template flows and derived flows in a non-programming configuration tool for EAI process flows.SOLUTION: When a derived flow modification instruction for a derived task constituting a derived flow is set by a flow creator using a non-programming configuration tool, a derived-use flag of a record linked to the derived flow targeted by the modification instruction is set to be execution disabled. A record is then newly added to a derived flow master, the record being linked to the derived flow reflecting the modification instruction, a template version of a template flow constituting the derived flow, a new flow version number, and a derived-use flag set to be execution enabled.SELECTED DRAWING: Figure 16

Description

[Technical Field]

[0001] The present invention relates to an EAI processing flow management device, an EAI processing flow management method, and an EAI processing flow management program. [Background technology]

[0002] Patent Document 1 discloses a configuration for creating and modifying a program using a non-programming tool. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-188047 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the invention described in Patent Document 1 above has a problem in that it is not possible to manage versions of inheritance template flows in a non-programming setting tool for EAI (Enterprise Application Integration) process flows.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide an EAI processing flow management device, an EAI processing flow management method, and an EAI processing flow management program that can manage versions of inherited template flows and derived flows in a non-programming setting tool for EAI processing flows. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the EAI processing flow management device of the present invention is an EAI processing flow management device comprising a memory unit and a control unit, wherein the memory unit comprises an EAI processing storage means for storing a non-programming setting tool for an EAI processing flow, a template version which is a version of a template flow that is a system collaboration process composed of common processing tasks and placeholders whose processing order is linked, a derived flow in which a derived task is incorporated into the placeholder in the template flow, a flow version which is a version of the derived flow, and a derived flow master in which a record is set to which a derivative usage flag indicating whether the flow version can be executed is linked, and the control unit comprises flow modification means for, when a flow creator uses the non-programming setting tool to set a derived flow modification instruction for a derived task that constitutes the derived flow, setting the derivative usage flag of the record to which the derived flow that is the target of the derived flow modification instruction is linked to "not executable," and adding to the derived flow master a record linked to the derived flow that reflects the derived flow modification instruction, the template version of the template flow that constitutes the derived flow, a new flow version, and the derivative usage flag set to "executable."

[0007] Furthermore, in the EAI processing flow management device according to the present invention, when a template flow modification instruction is set for the template flow by a template creator using the non-programming setting tool, the flow modification means sets the derivative usage flag of the record in which the derived flow composed of the template flow that is the target of the template flow modification instruction is set to "unexecutable," and adds to the derived flow master a record linking the derived flow that reflects the template flow modification instruction, a new flow version, a new template version, and the derivative usage flag that is set to "executable."

[0008] In the EAI processing flow management device according to the present invention, the EAI processing storage means further stores a template flow master in which a record linking the template flow with the template version, which is a version of the template flow, is set, and the flow modification means further adds to and sets in the template flow master a record linking the template flow that reflects the template flow modification instruction with the new template version number.

[0009] Furthermore, in the EAI processing flow management device according to the present invention, when a derived flow version-up instruction is set by the flow creator using the non-programming setting tool for the derived task that constitutes the derived flow, the flow correction means sets the derived usage flag of the record in which the derived flow that is the target of the derived flow version-up instruction is set to "unexecutable," and adds to the derived flow master the record that links the derived flow that reflects the derived flow version-up instruction, the template version of the template flow that constitutes the derived flow, the new flow version number, and the derived usage flag that is "executable."

[0010] Furthermore, in the EAI processing flow management device according to the present invention, when a template flow version-up instruction for the template flow is set by the template creator using the non-programming setting tool, the flow correction means sets the derivative usage flag of the record to which the derived flow constituted by the template flow that is the target of the template flow version-up instruction to "not executable," and adds to and sets, in the derived flow master, the record to which the derived flow that reflects the template flow version-up instruction, the new flow version, the new template version, and the derivative usage flag that is "executable" are linked.

[0011] Furthermore, in the EAI processing flow management device according to the present invention, when a template flow version downgrade instruction is set for the template flow by the template creator using the non-programming setting tool, the flow modification means sets the derivative usage flag of the record in which the derived flow composed of the template flow that is the target of the template flow version downgrade instruction is set to "unexecutable," and adds to the derived flow master the record linking the derived flow of the template version that corresponds to the template flow version downgrade instruction, the flow version of the new version number, the template version, and the derivative usage flag that is "executable."

[0012] In addition, in the EAI processing flow management device of the present invention, the flow modification means is further characterized in that when a flag change instruction is set for the derived usage flag linked to the derived flow set in the derived flow master, the flow modification means changes and sets the execution feasibility of the derived usage flag based on the flag change instruction.

[0013] In addition, in the EAI processing flow management device of the present invention, the control unit is characterized in that it further comprises a flow execution means that, when the derived flow is selected on the execution instruction screen by the flow executor, displays the flow version of the derived flow linked to the executable derivative usage flag in a confirmable manner based on the derivative usage flag linked to the derived flow set in the derived flow master.

[0014] In addition, in the EAI processing flow management device according to the present invention, the template flow master is set with a record linking the template flow, the template version, and a template usage flag indicating whether the template can be used by a flow implementer, and the control unit further comprises flow execution means that, when the derived flow is selected by the flow implementer on the execution instruction screen, displays on the execution instruction screen whether the derived flow can be executed based on the template usage flag set in the template flow master to which the template version linked to the derived flow set in the derived flow master is linked.

[0015] Furthermore, an EAI processing flow management method according to the present invention is an EAI processing flow management method to be executed by an EAI processing flow management device having a memory unit and a control unit, wherein the memory unit comprises EAI processing storage means for storing a non-programming setting tool for an EAI processing flow, a template version which is a version of a template flow that is a system collaboration process composed of common processing tasks and placeholders to which a processing order is linked, a derived flow in which a derived task is incorporated into the placeholder in the template flow, a flow version which is a version of the derived flow, and a derived flow master in which a record is set to which a derivative usage flag indicating whether the flow version can be executed is linked, and the control unit includes a flow modification step executed by the control unit, when a derived flow creator uses the non-programming setting tool to set a derived flow modification instruction for a derived task that constitutes the derived flow, setting the derivative usage flag of the record to which the derived flow that is the target of the derived flow modification instruction is linked to "not executable," and adding to the derived flow master a record to which the derived flow that reflects the derived flow modification instruction, the template version of the template flow that constitutes the derived flow, a new flow version, and a derivative usage flag that indicates whether the executable is linked.

[0016] Furthermore, an EAI processing flow management program according to the present invention is an EAI processing flow management program to be executed by an EAI processing flow management device having a memory unit and a control unit, wherein the memory unit comprises EAI processing storage means for storing a non-programming setting tool for an EAI processing flow, a template version which is a version of a template flow that is a system collaboration process composed of common processing tasks and placeholders to which a processing order is linked, a derived flow in which a derived task is incorporated into the placeholder in the template flow, a flow version which is a version of the derived flow, and a derived flow master in which a record is set to which a derivative usage flag indicating whether the flow version can be executed is linked, and wherein, when a flow creator uses the non-programming setting tool to set a derived flow modification instruction for a derived task that constitutes the derived flow, the control unit executes a flow modification step of setting the derivative usage flag of the record to which the derived flow that is the target of the derived flow modification instruction is linked to "unexecutable", and adding to the derived flow master the derived flow that reflects the derived flow modification instruction, the template version of the template flow that constitutes the derived flow, a new flow version, and a record to which the derivative usage flag is linked to indicate whether the flow version is executable. [Effects of the Invention]

[0017] The present invention provides an advantage that when a change is made to a template, the change can be created as a new version. Furthermore, the present invention provides an advantage that template changes that may cause destructive changes to derived flows can be appropriately reflected, and if a defect occurs in the template, quick recovery can be achieved by reverting to the previous version, thereby improving flow maintainability. Furthermore, the present invention provides an advantage that high-quality flows can be provided as templates and fine-tuning can be made for each flow. Furthermore, the present invention provides an advantage that when a change is made to a template, the change is not immediately reflected in the derived flow, but rather a new version can be created. This allows the derived flow creator to decide whether to upgrade the template or continue to use the template before the change depending on the changes. Even if the modifications involve destructive changes, the flow user can execute the flow smoothly by adjusting the timing of the template upgrade. Furthermore, the present invention provides an advantage that a rollback function is provided to return the system to its previous state if a defect occurs in the template changes, thereby quickly restoring the system to its previous state if a problem occurs in the template flow or if there is a defect in the changes made to a single derived flow. Furthermore, according to the present invention, it is possible to make a certain version of a specific template unusable when creating a derived flow or when executing a flow, thereby preventing a new derived flow from being created using a problematic template version and preventing an inappropriate flow from being executed when the flow is executed.Furthermore, according to the present invention, it is possible to significantly improve the maintainability of flows. [Brief explanation of the drawings]

[0018] [Figure 1] FIG. 1 is a diagram illustrating an example of an EAI processing flow. [Figure 2] FIG. 2 is a diagram showing an example of a flow designer screen. [Figure 3] FIG. 3 is a diagram showing an example of an outline of a solution according to this embodiment. [Figure 4] FIG. 4 is a diagram showing an example of an outline of a solution according to this embodiment. [Figure 5] FIG. 5 is a diagram showing an example of an outline of a solution according to this embodiment. [Figure 6] FIG. 6 is a diagram showing an example of an outline of a solution according to this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of an outline of a solution according to this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of an outline of a solution according to this embodiment. [Figure 9] FIG. 9 is a diagram showing an example of an outline of a solution in this embodiment. [Figure 10] FIG. 10 is a diagram showing an example of an outline of a solution in this embodiment. [Figure 11] FIG. 11 is a diagram showing an example of an outline of a solution in this embodiment. [Figure 12] FIG. 12 is a diagram showing an example of an outline of a solution according to this embodiment. [Figure 13] FIG. 13 is a diagram showing an example of an outline of a solution in this embodiment. [Figure 14] FIG. 14 is a diagram showing an example of an outline of a solution in this embodiment. [Figure 15] FIG. 15 is a diagram showing an example of an outline of a solution in this embodiment. [Figure 16] FIG. 16 is a block diagram showing an example of the configuration of an EAI processing flow management device according to this embodiment. [Figure 17] FIG. 17 is a diagram showing an example of a master configuration in this embodiment. [Figure 18] FIG. 18 is a flowchart showing an example of processing by the EAI processing flow management device in this embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of the flow creation and execution process according to this embodiment. [Figure 20] FIG. 20 is a diagram showing an example of the flow creation and execution process in this embodiment. [Figure 21] FIG. 21 is a diagram showing an example of the flow creation and execution process in this embodiment. [Figure 22] FIG. 22 is a diagram showing an example of the flow creation and execution process in this embodiment. [Figure 23] FIG. 23 is a diagram showing an example of template creation and derived flow modification in this embodiment. [Figure 24] FIG. 24 is a diagram showing an example of template creation and derived flow modification in this embodiment. [Figure 25] FIG. 25 is a diagram showing an example of template creation and derived flow modification in this embodiment. [Figure 26] FIG. 26 is a diagram showing an example of template creation and derived flow modification in this embodiment. [Figure 27] FIG. 27 is a diagram showing an example of template creation and derived flow modification in this embodiment. [Figure 28] FIG. 28 is a diagram showing an example of execution of a derived flow that inherits a template flow that implements a version management function in this embodiment. [Figure 29] FIG. 29 is a diagram showing an example of execution of a derived flow that inherits a template flow that implements a version management function in this embodiment. [Figure 30] FIG. 30 is a diagram showing an example of modification of a derived flow when a template with a defect is prohibited from use in this embodiment. [Figure 31] FIG. 31 is a diagram showing an example of modification of a derived flow when a template with a defect is prohibited from use in this embodiment. [Figure 32] FIG. 32 is a diagram showing an example of modification of a derived flow when a template with a defect is prohibited from use in this embodiment. [Figure 33] FIG. 33 is a diagram showing an example of modification of a derived flow when a template with a defect is prohibited from use in this embodiment. [Figure 34]FIG. 34 is a diagram showing an example of template flow correction and derived flow correction when a problem occurs in changing a template in this embodiment. [Figure 35] FIG. 35 is a diagram showing an example of template flow correction and derived flow correction when a problem occurs in changing a template in this embodiment. [Figure 36] FIG. 36 is a diagram showing an example of template flow correction and derived flow correction when a problem occurs in changing a template in this embodiment. [Figure 37] FIG. 37 is a diagram showing an example of template flow correction and derived flow correction when a problem occurs in changing a template in this embodiment. [Figure 38] FIG. 38 is a diagram showing an example of template flow correction and derived flow correction when a problem occurs in changing a template in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0019] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

[0020] [1. Overview] An overview of the present invention will be described with reference to Figures 1 to 17. Figure 1 is a diagram showing an example of an EAI processing flow. Figure 2 is a diagram showing an example of a flow designer screen.

[0021] First, Enterprise Application Integration (EAI) is defined as an approach or technology for integrating different information systems or applications and enabling them to work together effectively. As shown in Figure 1, in a typical EAI system, each system process is defined as a "task," and a series of system integration processes is defined as a "flow." In this way, in EAI, the steps of a series of integration processes are defined and executed as a flow consisting of multiple linked tasks. Here, "tasks" include tasks that control the flow (e.g., conditional branching or loops), tasks that perform file operations (e.g., file transfer, Excel® output, variable-length read, etc.), tasks that perform database operations (e.g., execution of update-related stored procedures, table reads, transaction control, etc.), tasks that output logs (e.g., event log output, EAI-specific log output, ERP log, text log output, etc.), and other tasks (e.g., child flow invocation, application execution, email transmission, etc.).

[0022] As shown in Figure 2, a flow creator can link tasks on the flow designer screen using a GUI (Graphical User Interface), realizing system integration without programming. Here, the flow creator may be a system implementer or a system administrator at a client company.

[0023] In the past, when creating a large number of similar flows in an EAI integration system, a template incorporating the standard controls that such flows should have was provided as a "template." However, when using a "template," there were two issues: (1) when duplicating, mistakes were made in which parts that should be changed were forgotten, or parts that should not be changed were changed; and (2) after creating a large number of flows, if a common correction was required for the flows, the cost of correcting each flow individually was incurred.

[0024] In addition, in the past, when creating EAI processing flows, there was a problem in that common modifications were not efficient when creating a large number of similar flows.To address this problem, derived flows that inherited template flows were created.However, since changes made to the template flow were automatically reflected in the derived flows all at once, if there was a problem with the changes to the template flow, the derived flow could operate incorrectly, and if the changes to the template flow involved destructive changes to the derived flow, there was a risk that the derived flow would become inexecutable.

[0025] Therefore, in this embodiment, a mechanism is provided for consolidating a series of task processes into an "inheritance template" rather than a "template template." In this embodiment, an "inheritance template" is referred to as a "template," and a flow created based on a "template" is referred to as a "derived flow." Here, a "derived flow" is not a copy of a "template," but is created by inheriting the functions of the "template" and adding flow-specific implementation to the "template." Therefore, by modifying the "template," the "derived flows" can be reflected all at once, thereby solving problems (1) and (2).

[0026] An example of an outline of the solution in this embodiment will now be described with reference to Figures 3 to 6. Figures 3 to 6 are diagrams showing an example of an outline of the solution in this embodiment.

[0027] In this embodiment, when an inheritance relationship between a template flow and a derived flow is established as shown in Fig. 3, the template creator creates a template flow when it is desired to retrieve a file and update a master based on the contents of the retrieved file, but it is assumed that there are multiple masters to be updated, and each master needs to be updated using its own process, and it is necessary to create as many flows as there are to be updated. Here, as shown in Fig. 4, in this embodiment, common processing and error handling on the derived flow side are implemented in the template flow as common pre-processing and common post-processing (1)-(2) to make them common. The "file retrieval processing" is assumed to be common processing regardless of the derived flow and is implemented in the common pre-processing. Since the operation after file retrieval differs depending on the derived flow, it is implemented as placeholder (1). To handle an error in the case where an error occurs in placeholder (1), "TRY·CATCH" is implemented before and after placeholder (1). Placeholder (2) is implemented so that the processing after an error can also be individually set for each derived flow. The operation to be performed commonly in the processing after an error occurs, "send email," is implemented in common post-processing (2).

[0028] As shown in FIG. 5, in this embodiment, the creator of a derived flow sets placeholders based on a template flow to create a derived flow.

[0029] As shown in Figure 6, in this embodiment, the flow executor executes the derived flow A-1, and at the time of execution, executes the execution flow created by inserting the setting contents of the placeholder set in the derived flow into the template from which the derived flow is inherited.

[0030] An example of an outline of the solution in this embodiment will be described with reference to Figures 7 and 8. Figures 7 and 8 are diagrams showing an example of an outline of the solution in this embodiment.

[0031] As shown in FIG. 7, in this embodiment, it is assumed that after creating a derived flow, it is discovered that a subsequent task will not run in the file retrieval process within the common process, and if the number of file retrievals is 0, the template creator modifies (changes) the common process of the template so that the process will end.

[0032] As shown in FIG. 8, in this embodiment, when a flow executor executes a derived flow, a flow is executed in which the placeholder setting contents of the derived flow are merged with the inheritance template when the derived flow is executed, and the inheritance template is modified so that the modification of adding a file acquisition count check to the common pre-processing of the template flow is reflected all at once when the derived flow is executed.

[0033] However, as shown in FIG. 7, in this embodiment, adding a new process causes a new problem in that changes are reflected in the derived flow all at once even if there is a problem with the added process. For example, as shown in FIG. 7, in this embodiment, if the branching process after the check process for [whether the number of acquired files is 0] is incorrectly configured to end the process if the number of acquired files is not 0 and proceed to the placeholder section if the number is 0, a new problem occurs when the derived flow is executed, such as problems such as the derived flow not running or errors occurring. Furthermore, as shown in FIG. 8, in this embodiment, a new check process for the number of acquired files is added to the template, but a new problem occurs in that changes are reflected in the derived flow all at once even if there is a problem with the check process for the number of acquired files.

[0034] Furthermore, in the past, when implementing a system whereby changes to a template are immediately and collectively reflected in derived flows, if there was a problem with the template changes, the derived flows could stop working. For example, if a defect occurred due to a template change, the template flow had to be modified. Therefore, if the changes to the template content were immediately reflected in the derived flows, a new issue arose in which the flows would behave incorrectly when executed until the template flow was modified. Furthermore, in the past, when implementing a system whereby changes to a template are immediately and collectively reflected in derived flows, even if there was no problem with the template changes, the derived flows could stop working. For example, if a new element that must be set in the derived flow is added to the template, causing the derived flows to stop working due to changes in the template flow, the derived flows would have to be modified. Therefore, if a destructive change to the template (i.e., a change to the template that requires modification on the derived flow side) was immediately reflected in the derived flows, a new issue arose in which flow executors could not execute the flows until the derived flows were modified.

[0035] Therefore, in this embodiment, a function for managing the version of a template, a function for managing the version of a derived flow, and a function for prohibiting the use of a specific template version are implemented.

[0036] An example of an outline of the solution in this embodiment will now be described with reference to Figures 9 to 15. Figures 9 to 15 are diagrams showing an example of an outline of the solution in this embodiment.

[0037] 9 to 15 show the procedure by which the master is updated by screen operations in this embodiment, with the primary key of the master data being represented by the shaded area.

[0038] As shown in Fig. 9, a derived flow in this embodiment contains information on "which template flow it was created based on" and "which template flow version it uses," and therefore, it is possible to create multiple derived flows from a single combination of template ID and template version by linking them to a combination of template flow type and version. For example, Fig. 9 shows the data structure when derived flows A-1 and A-2 are created from template version 1 of template flow A.

[0039] Furthermore, in this embodiment, when a template flow is changed, the data is managed as a template flow of a different template version, although it is the same template flow. For example, as shown in Fig. 9, in this embodiment, the master state when template flow A is modified is shown, and it shows that when only template version 1 was available, the template was changed and version 2 (data in a bold frame) was added.

[0040] Furthermore, in this embodiment, when a derived flow is executed, the template version and derived flow version linked to the record where the Use FLG of the Derived Flow (with template)_Header Master is TRUE are executed. If the derived flow is executed without any modifications, the derived flow with the Use FLG set to TRUE and the linked template version remain 1, so the template version 1 is inherited and executed. Furthermore, in this embodiment, in order to reflect changes to the template, it is necessary to modify the derived flow and change the version. Furthermore, this embodiment can solve the problem of the derived flow being automatically affected and no longer working when a defect is corrected in the template.

[0041] Furthermore, as shown in FIGS. 10 to 15, in this embodiment, when a derived flow is modified, the data is managed as a derived flow of the same derived flow but of a different derived flow version.

[0042] 10 shows a modification of a derived flow without changing the template flow version, for example, showing the master state when a modification of derived flow A-1 is performed. As shown in FIG. 10, when a modification is performed, a template of template version 1 is merged with a derived flow of flow version 2 and executed. When a derived flow is modified, the use flag for the latest derived flow version is set to TRUE, and other versions are set to FALSE. In other words, as shown in FIG. 10, in this embodiment, a modification of a derived flow without upgrading the template version increments the derived flow version by one, and data is added without changing the template flow version.

[0043] FIG. 11 also illustrates a modification of a derived flow that involves a template version upgrade, as an example of a modification of a derived flow that involves a template version change. For example, the master state is shown when a derived flow A-1 (the latest flow version is 2) created based on "template flow A and template version 1" is modified to use template flow version 2. As shown in FIG. 11 , during execution, a "derived flow with flow version 3" is merged with a "template with template version 2." In this embodiment, upgrading a template used in a derived flow has the advantage of reflecting the functionality of the new template version, as well as the disadvantage (1) that problems may occur during use if the template change has a defect, and the disadvantage (2) that problems may occur during use if the template change includes a destructive change. That is, as shown in FIG. 11 , in this embodiment, a modification of a derived flow that involves a template version upgrade results in an upgrade of the derived flow, and data is added when the template flow version is upgraded.

[0044] FIG. 12 also illustrates a modification of a derived flow that involves a template flow version change, such as a modification of a derived flow due to a template downgrade. For example, the example illustrates a case in which a derived flow A-1 (the latest flow version is 3) created based on "template flow A and template version 2" is modified to use template flow version 1. As shown in FIG. 12 , during execution, a "template with template version 1" is merged with a "derived flow with flow version 4." In this embodiment, downgrading the template used in the derived flow has the advantage that, if the disadvantages (1) and (2) in FIG. 11 occur, the derived flow can be reverted to the previous template before the template defect and modified to work. That is, as shown in FIG. 12 , in this embodiment, when modifying a derived flow that involves a version downgrade, data is added while the derived flow version is upgraded and the template flow version is downgraded.

[0045] 13 also shows that it is possible to change a derived flow across template versions as a modification of the derived flow that accompanies a version change of the template flow. For example, it shows the state when derived flow A-1 (latest flow version is 1) created based on "template flow A and template version 1" is modified to use template flow version 4. Here, the process shown in FIG. 13 does not require upgrading to template changes (2 to 3). If the previous template version has been used stably for a while and template version 4 contains changes that you want to reflect in the derived flow, there is an advantage in that you can update the template version to the latest without having to modify each derived flow that requires a template version upgrade.

[0046] 14 also shows that it is possible to change a derived flow across template versions when modifying a derived flow that involves changing the template flow version, and for example shows the state when derived flow A-1 (latest flow version is 1) created based on "template flow A and template version 3" is modified to use template flow version 1. Here, the process shown in Fig. 14 has the advantage that even if there is a problem with the changes to the template added from template version 2 and the problem is discovered after several version changes have been made since then, it can be quickly reverted to a template flow version without the problem.

[0047] 15 also shows that a modification of a derived flow without changing the template flow version involves changing the usage flag (FLG) and using an older version of the derived flow. As shown in FIG. 15, in this embodiment, by changing the usage FLG of the derived flow, the version of the derived flow used by the flow implementer can be changed. For example, if there is a problem with the changes made to the derived flow itself without changing the template version, this has the advantage of making it possible to restore the derived flow to the state it was in previously. Furthermore, in this embodiment, when a derived flow is modified to create a new derived flow version, or when the usage FLG of the derived flow is changed as shown in FIG. 15, control is performed so that there is only one item with the same header ID and usage FLG set to True.

[0048] [2. Configuration] An example of the configuration of the EAI processing flow management device 100 according to this embodiment will be described with reference to Fig. 16 and Fig. 17. Fig. 16 is a block diagram showing an example of the configuration of the EAI processing flow management device 100 according to this embodiment.

[0049] 16, EAI processing flow management device 100 is a commercially available desktop personal computer. Note that EAI processing flow management device 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0050] EAI processing flow management device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units comprised in EAI processing flow management device 100 are connected to each other so that they can communicate with each other via any communication path.

[0051] The communication interface unit 104 communicatively connects the EAI processing flow management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the EAI processing flow management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0052] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0053] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 includes an EAI processing database 106a.

[0054] The EAI process database 106a stores EAI process data. The EAI process database 106a may also store a non-programming configuration tool for EAI process flows. The EAI process database 106a may also store EAI process masters referenced when a derived flow is executed. The EAI process masters may include a flow (without template) master, a template flow master, a derived flow (with template) header master, and / or a derived flow (with template) detail master. The EAI process database 106a may also store template versions, which are versions of template flows that are system collaboration processes composed of common processing tasks and placeholders linked to a processing order; derived flows in which derived tasks are incorporated into placeholders in a template flow; flow versions, which are versions of derived flows; and / or derived flow masters in which records are set with a derivation usage flag indicating whether a flow version can be executed. The EAI process database 106a may also store template flow masters in which records are set with a template flow and a template version, which are versions of the template flow, linked to each other. Here, the template flow master may have a record set that links together the template flow, the template version, and a template usage flag that indicates whether the template can be used by the flow executor.

[0055] An example of a data structure related to the template function in this embodiment will now be described with reference to Fig. 17. Fig. 17 is a diagram showing an example of a master configuration in this embodiment.

[0056] As shown in Figure 17, in this embodiment, when a derived flow is executed, the flow is executed using the flow data of the template flow linked to the template ID of the flow (with template)_header master, and the detail flow data linked to the flow ID of the flow (with template)_header master. Here, as shown in Figure 17, the primary key is indicated by diagonal lines.

[0057] 16, the control unit 102 is a CPU or the like that performs overall control of the EAI processing flow management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs. Functionally, the control unit 102 conceptually comprises a flow correction unit 102a and a flow execution unit 102b.

[0058] The flow modification unit 102a reflects the derived flow modification instruction in the derived flow. Alternatively, the flow modification unit 102a may reflect the template flow modification instruction in the derived flow. Alternatively, the flow modification unit 102a may reflect the template flow modification instruction in the template flow. Here, when a flow creator uses a non-programming setting tool to set a derived flow modification instruction for a derived task that constitutes a derived flow, the flow modification unit 102a may set the derivative usage flag of the record to which the derived flow that is the target of the derived flow modification instruction is linked to "unexecutable," and may additionally set, to the derived flow master, a record that links the derived flow that reflects the derived flow modification instruction, the template version of the template flow that constitutes the derived flow, the new flow version, and the derivative usage flag to "executable." Furthermore, when a template creator uses a non-programming setting tool to set a template flow modification instruction for a template flow, the flow modification unit 102a may set the derivative usage flag of a record in which a derived flow consisting of the template flow that is the target of the template flow modification instruction is set to not executable, and may add to the derived flow master a record that links the derived flow that reflects the template flow modification instruction, the new flow version, the new template version, and the executable derivative usage flag.

[0059] Furthermore, the flow modification unit 102a may add to the template flow master a record linking the template flow that reflects the template flow modification instruction and the new template version. Furthermore, when a derived flow creator sets a derived flow version upgrade instruction for a derived task that constitutes a derived flow using a non-programming setting tool, the flow modification unit 102a may set the derivative usage flag of the record in which the derived flow that is the target of the derived flow version upgrade instruction is set to "unexecutable," and add to the derived flow master a record linking the derived flow that reflects the derived flow version upgrade instruction, the template version of the template flow that constitutes the derived flow, the new flow version, and the derivative usage flag to "executable."

[0060] Furthermore, when a template creator uses a non-programming setting tool to set a template flow upgrade instruction for a template flow, the flow modification unit 102a may set the derivative use flag of a record associated with a derived flow composed of the template flow targeted by the template flow upgrade instruction to "unexecutable," and add a record associated with the derived flow reflecting the template flow upgrade instruction, the new flow version, the new template version, and an executable derivative use flag to the derived flow master. Furthermore, when a template creator uses a non-programming setting tool to set a template flow downgrade instruction for a template flow, the flow modification unit 102a may set the derivative use flag of a record associated with a derived flow composed of the template flow targeted by the template flow downgrade instruction to "unexecutable," and add a record associated with the derived flow of the template version corresponding to the template flow downgrade instruction, the new flow version, the template version, and an executable derivative use flag to the derived flow master. Furthermore, when a flag change instruction is set for a derivative use flag associated with a derived flow set in a derived flow master, the flow modification unit 102a may change the executable / unexecutable setting of the derivative use flag based on the flag change instruction. Furthermore, when a flow modification instruction for a template flow is set by the template creator using a non-programming setting tool, the flow modification unit 102a may reflect the flow modification instruction in each derived flow.

[0061] The flow execution unit 102b executes a derived flow. Here, the flow execution unit 102b may execute the derived flow in response to a flow execution instruction from a flow executer. Furthermore, when a derived flow is selected by a flow executer on the execution instruction screen, the flow execution unit 102b may display, in a confirmable manner, the flow version of the derived flow associated with an executable derivative usage flag based on a derivative usage flag associated with the derived flow set in the derived flow master. Furthermore, when a derived flow is selected by a flow executer on the execution instruction screen, the flow execution unit 102b may display, in a confirmable manner, whether the derived flow is executable based on a template usage flag set in a template flow master associated with a template version associated with the derived flow set in the derived flow master.

[0062] [3. Specific Examples] A specific example of this embodiment will be described with reference to FIGS.

[0063] [EAI processing flow management processing] An example of EAI processing flow management processing in this embodiment will now be described with reference to Fig. 18. Fig. 18 is a flowchart showing an example of processing by the EAI processing flow management device 100 in this embodiment.

[0064] As shown in FIG. 18, the flow executing unit 102b starts executing a derived flow in response to a flow execution instruction from a flow executing person (step SA-1).

[0065] Then, when an error occurs in the derived flow being executed, if an error notification instruction is set by the flow executer, the flow executing unit 102b sends an error notification to the flow creator (step SA-2).

[0066] The flow creator then determines whether or not there is a problem with the template flow that constitutes the derived flow (step SA-3).

[0067] If it is determined that there is no problem with the template flow that constitutes the derived flow (step SA-3: No), the control unit 102 moves the process to step SA-4.

[0068] When the flow creator sets a derived flow modification instruction for a derived task that constitutes a derived flow using a non-programming setting tool via the input device 112, the flow modification unit 102a sets the derived usage flag of the record linked to the derived flow that is the target of the derived flow modification instruction to "not executable," and adds to the derived flow master a record linked to the derived flow that reflects the derived flow modification instruction, the template version of the template flow that constitutes the derived flow, the new flow version number, and the derived usage flag that is "executable" (step SA-4), and then terminates the processing.

[0069] On the other hand, if the control unit 102 determines that there is a problem with the template flow that constitutes the derived flow (step SA-3: Yes), it sends a template correction instruction set by the flow creator to the template creator and transitions the processing to step SA-5.

[0070] Then, when the template creator sets a template flow modification instruction for the template flow using a non-programming setting tool via the input device 112, and the flow creator, who has been notified by the template creator, sets an instruction to change the derivative usage flag, the flow modification unit 102a sets the derivative usage flag of the record in which the derivative flow consisting of the template flow that is the target of the template flow modification instruction is set to not executable, and adds to the derived flow master a record linked to the derived flow that reflects the template flow modification instruction, the new flow version, the new template version, and the executable derivative usage flag (step SA-5), and terminates the processing.

[0071] An example of the flow creation and execution process in this embodiment will now be described with reference to Fig. 19 to Fig. 22. Fig. 19 to Fig. 22 are diagrams showing an example of the flow creation and execution process in this embodiment.

[0072] As shown in Fig. 19, in this embodiment, a new template is created, and a derived flow is created based on the created template. That is, as shown in Fig. 19, in this embodiment, when it is necessary to create multiple flows that import files and update the imported data into a master, the common processing of each flow is created as a template, and the parts that differ depending on the flow are prepared as placeholders, and the derived flow is created based on the created template. Here, as shown in Fig. 19, in this embodiment, in a state where [1] no template exists in the master (no template has been created) (a state where no data is present and therefore nothing is displayed on the template list screen), a new flow is created as a template by the worker (template creator), and the master is updated by associating the content entered on each screen (numbers are entered) with the master number.

[0073] 20 and 21, in this embodiment, from a state in which there is no data and nothing is displayed on the flow list screen, the worker (derived flow creator) selects a template to use on the template selection screen, transitions to the designer screen, and the derived flow creator creates a flow based on the template. The contents entered on each screen (numbers are entered) are associated with the master number, and the master is updated. Here, as shown in FIGS. 20 and 21, in this embodiment, tasks that are not placeholders cannot be edited, but the task settings can be viewed. Also, as shown in FIGS. 20 and 21, in this embodiment, the derived flow creator can change the target placeholder on the central editing screen by clicking on a placeholder in the template flow.

[0074] As shown in Figure 22, in this embodiment, [1] the derived flow that inherits the template is executed by the flow executor, and [2] flow data is obtained from the "template flow master" linked to the derived flow to be executed, and placeholders are merged from the "derived flow (with template)_detail master" to create the flow to be actually executed.

[0075] Next, an example of modifying a template flow and a derived flow using the version management function of this embodiment will be described with reference to Figures 23 to 29. Figures 23 to 27 are diagrams showing an example of creating a template and modifying a derived flow in this embodiment. Figures 28 and 29 are diagrams showing an example of executing a derived flow that inherits a template flow that implements the version management function of this embodiment.

[0076] In this embodiment, changes are made to an existing template to create a new version of the template, and the derived flow is changed in conjunction with the change in template version.As a change to the derived flow detail data, a placeholder is provided only when an error occurs in the processing, but a placeholder is also provided when the processing terminates normally.

[0077] 23, in this embodiment, [1-1] template creator A modifies an existing template, and the master is updated by associating the content entered on each screen (numbers are entered) with the master number. Note that in this embodiment, in places where the data structure of the master, etc. is expressed, the data is sorted in ascending order of version, and the data on the UI (User Interface) is sorted in descending order of version.

[0078] As shown in FIGS. 24 to 26, in this embodiment, [1-2] derived flow creator B changes the version of the existing derived flow, and the derived flow data is modified accordingly. The master is updated by associating the contents entered on each screen (including numbers) with the master number. Here, as shown in FIG. 25, in this embodiment, when the "Change Template Version" button is pressed in the Derived Flow Creation_Designer Screen_Modification, the screen transitions to the Template Version Change screen. Also, as shown in FIG. 25, in this embodiment, when the current label version is selected on the Template Version Change screen, the "Apply" button is locked so that it cannot be pressed. Also, as shown in FIG. 26, in this embodiment, in the Derived Flow Creation_Designer Screen_Modification, the screen is launched with the existing placeholder settings inherited, and the derived flow creator adds placeholder (3), which is the template change section. As shown in FIGS. 25 and 26, the parts added due to the template version change are indicated by bold frames. Also, as shown in Figure 26, the flow version is created by adding 1 to the largest number of the flow version with the same header ID of "Derived Flow (with template)_Header Master", and when a newly added derived flow version record is added, the usage flag of the latest version record is set to True, and the usage flag of the previous version record is set to False.

[0079] In this embodiment, [1-3] the flow execution screen displayed when the flow is executed by the flow executor C displays the derived flow data associated with the version for which the usage flag of the "derived flow (with template)_header master" is True, and as shown in Figure 27, a function is implemented to check the version of the derived flow being used by the flow executor C (for example, the person who set the derived flow can check whether the settings have actually been reflected, and the flow user can use this when inquiring about the setter (such as sharing information in the event of an error)).

[0080] 28, in this embodiment, the flow is executed by [2-1] flow executer C. Here, as shown in Fig. 28, the version of the derived flow displayed on the screen is the version where the derived flow (with template)_Header Master Use FLG is True, and there is only one record in the same header ID where the derived flow (with template)_Header Master Use FLG is True, so the version of the flow to be executed is narrowed down to one.

[0081] As shown in Figure 29, in this embodiment, [2-2] flow data is obtained from the "template flow master" linked to the derived flow to be executed, and placeholders are merged from the "derived flow (with template)_detail master" to create the flow to actually be executed. Here, as shown in Figure 29, the version of the derived flow to be executed is the version of the record whose Use FLG of the header ID of the selected derived flow is True.

[0082] 30 to 33, an example of modifying a template and a derived flow when a change to a template in this embodiment results in a defect will be described. Figures 30 to 33 are diagrams showing an example of modifying a derived flow when a template with a defect in this embodiment is to be prohibited from use.

[0083] Figures 30 to 33 show the operations on the template creation side when a certain version has a problem, and the rollback operations on the derived flow side, that is, the operations when a problem occurs in "Version 2" of "Template Flow: File Import Template" and some of the derived flows have already upgraded the file import template from "Version 1" to "Version 2."

[0084] 30, in this embodiment, [3-1] the worker (template creator A) sets existing templates to be unusable, and sets templates with template versions that have defects in derived flows to be unusable, and the master is updated by pressing the "Register button." Here, in this embodiment, by setting "make unusable in derived flows," a warning is displayed on the derived flow list screen for derived flows that were created with templates with unusable template versions, and unusable versions cannot be selected on the template switching screen for derived flows, and derived flows linked to unusable template versions cannot be executed.

[0085] As shown in FIG. 31, in this embodiment, the problematic derived flow is identified by the [3-2] worker (derived flow creator B), who then rolls back the derived flow or modifies the derived flow by changing the template version. A warning is then displayed on the flow list screen for template versions with the prohibition flag set to TRUE and for affected derived flows, thereby informing the derived flow creator of the derived flows that need to be modified. Specifically, as shown in FIG. 31, in this embodiment, a warning is displayed when the prohibition flag set to TRUE is set for a record in the [Template Flow Master] linked to a record in which the use flag set to TRUE is set for the [Derived Flow (with template)_Header Master]. Here, as shown in FIG. 31, in this embodiment, when the cursor is placed over the warning icon, a message is displayed in tooltip format.

[0086] As shown in FIG. 32, in this embodiment, the method for correcting the derived flow for which a warning is displayed is to perform [3-2-a] rollback of the derived flow, which is effective when a version of the derived flow exists that is linked to a template version that is not defective. As shown in FIG. 32, in this embodiment, pressing the "Register button" updates the master, and the master update only changes the usage flag to True / False; no records are deleted or added. As shown in FIG. 32, in this embodiment, by reopening the flow list screen, it is possible to confirm that the version of the derived flow has changed (returning to the version of the derived flow created based on template version 1).

[0087] As shown in FIG. 33, in this embodiment, the method for correcting a derived flow that displays a warning involves modifying the derived flow by changing the template version (see [3-2-b]). This method is effective when there is no derived flow version associated with a template version that is free of defects. As shown in FIG. 33, in this embodiment, assuming the state of the template flow master and derived flow (with template)_header master, the header ID is imported by flow executor C into the business establishment master, and there is no rollback destination. Therefore, method [3-2-a] cannot resolve the issue. However, the template version is downgraded to the file import template of template version 1, in which the prohibition flag is False. As shown in FIG. 33, in this embodiment, a derived flow using a template version in which the prohibition flag is True displays an error message on the screen to the worker (flow executor C) and locks the execution button. Here, as shown in FIG. 33, in this embodiment, the records added by modifying the derived flow are indicated within a bold frame.

[0088] Next, an example of how to modify a template and a derived flow when a change to a template in this embodiment results in a malfunction will be described with reference to Figures 34 to 38. Figures 34 to 38 are diagrams showing an example of how to modify a template flow and a derived flow when a change to a template in this embodiment results in a malfunction.

[0089] In the case where derived flows A, B, and C are created based on template X (template version 2), as shown in Figure 34, [4-1] the flow executor notices that there is a problem with derived flow A, and as shown in Figure 35, [4-2] the executor escalates and informs each person in charge that an error has occurred in the flow execution.

[0090] In this embodiment, [4-3] the template creator sets the template version in which the error occurred so that it cannot be used by derived flow creators and flow executors, and a warning is displayed on the screen to each person in charge not only for derived flow A in which the error was discovered, but also for all derived flows linked to the template version with the defect, as shown in Fig. 36. Here, as shown in Fig. 36, the template flow change history shows the screen after template version 2 has been set to be unusable, and the areas within the bold frame are editable.

[0091] As shown in FIG. 37, in this embodiment, by correcting the derived flow with a high priority [4-4], the template of template version 2, which has a defect, is no longer used, and only derived flow A is made available.

[0092] Then, as shown in FIG. 38, in this embodiment, the defect in the [4-5] template is repaired, and the derived flow is updated to the version of the repaired template to restore the system.

[0093] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0094] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0095] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0096] 5. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0097] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0098] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0099] Furthermore, with regard to the EAI processing flow management device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0100] For example, all or any part of the processing functions of EAI processing flow management device 100, particularly the processing functions performed by control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by EAI processing flow management device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM and cooperates with the CPU to form a control unit.

[0101] In addition, this computer program may be stored in an application program server connected to the EAI processing flow management device 100 via any network, and all or part of it may be downloaded as needed.

[0102] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0103] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0104] The various databases stored in the memory unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0105] Furthermore, EAI processing flow management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. Furthermore, EAI processing flow management device 100 may be realized by installing software (including programs, data, etc.) that causes the device to realize the processing described in this embodiment.

[0106] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0107] The present invention is useful in various industries that build systems using a large number of services. [Explanation of symbols]

[0108] 100 EAI processing flow management device 102 Control section 102a Flow Correction Unit 102b Flow execution unit 104 Communication interface unit 106 Storage section 106a EAI Processing Database 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. An EAI processing flow management device including a storage unit and a control unit, The storage unit an EAI processing storage means for storing a non-programming setting tool for an EAI processing flow, a template version which is a version of a template flow that is a system cooperation processing composed of common processing tasks and placeholders to which a processing order is linked, a derived flow in which a derived task is incorporated into the placeholder in the template flow, a flow version which is a version of the derived flow, and a derived flow master in which a record linked with a derived use flag indicating whether the flow version can be executed is set; Equipped with The control unit a flow modification means for, when a derived flow creator uses the non-programming setting tool to set a derived flow modification instruction for the derived task that constitutes the derived flow, setting the derivation usage flag of the record linked to the derived flow that is the target of the derived flow modification instruction to "unexecutable," and additionally setting, to the derived flow master, a record linked to the derived flow that reflects the derived flow modification instruction, the template version of the template flow that constitutes the derived flow, a new flow version number, and the derivation usage flag that is "executable"; An EAI processing flow management device comprising:

2. The flow correcting means is 2. The EAI processing flow management device according to claim 1, further comprising: when a template creator uses the non-programming setting tool to set a template flow modification instruction for the template flow, the device sets the derived usage flag of the record in which the derived flow composed of the template flow that is the target of the template flow modification instruction is set to "unexecutable," and adds to the derived flow master a record linking the derived flow that reflects the template flow modification instruction, a new flow version, a new template version, and the derived usage flag that is set to "executable."

3. The EAI processing storage means Furthermore, a template flow master is stored in which a record linking the template flow and the template version, which is a version of the template flow, is set, and The flow correcting means is 3. The EAI process flow management device according to claim 2, further comprising: adding to the template flow master a record linking the template flow reflecting the template flow correction instruction and the new template version number.

4. The flow correcting means is 2. The EAI processing flow management device according to claim 1, wherein, when a derived flow version-up instruction is set by the flow creator using the non-programming setting tool for the derived task that constitutes the derived flow, the device sets the derived usage flag of the record in which the derived flow that is the target of the derived flow version-up instruction is set to "unexecutable," and adds and sets to the derived flow master the record that links the derived flow that reflects the derived flow version-up instruction, the template version of the template flow that constitutes the derived flow, the flow version of the new version number, and the derivative usage flag that is set to "executable."

5. The flow correcting means is 3. The EAI processing flow management device according to claim 2, wherein, when a template flow version-up instruction for the template flow is set by the template creator using the non-programming setting tool, the device sets the derived usage flag of the record to which the derived flow constituted by the template flow that is the target of the template flow version-up instruction is linked to the not executable flag, and additionally sets the record to which the derived flow that reflects the template flow version-up instruction, the new flow version, the new template version, and the executable derived usage flag are linked to the derived flow master.

6. The flow correcting means is 3. The EAI processing flow management device according to claim 2, wherein, when a template flow version downgrade instruction for the template flow is set by the template creator using the non-programming setting tool, the device sets the derivative usage flag of the record in which the derived flow composed of the template flow that is the target of the template flow version downgrade instruction is set to ``unexecutable,'' and adds to the derived flow master the record in which the derived flow of the template version corresponding to the template flow version downgrade instruction, the flow version of the new version number, the template version, and the derivative usage flag set to ``executable.''

7. The flow correcting means is Furthermore, when a flag change instruction is set for the derived usage flag linked to the derived flow set in the derived flow master, the EAI processing flow management device described in claim 1 changes and sets the execution feasibility of the derived usage flag based on the flag change instruction.

8. The control unit a flow execution means for, when a flow executer selects the derived flow on an execution instruction screen, displaying the flow version of the derived flow associated with the executable derivative usage flag in a confirmable manner based on the derivative usage flag associated with the derived flow set in the derived flow master; 7. The EAI processing flow management device according to claim 1, further comprising:

9. The template flow master includes: A record is set that links the template flow, the template version, and a template usage flag that indicates whether the template flow can be used by the flow executor; The control unit a flow execution means for, when the derived flow is selected on an execution instruction screen by the flow executer, displaying on the execution instruction screen whether the derived flow is executable or not based on the template usage flag set in the template flow master to which the template version set in the derived flow master is linked; 4. The EAI process flow management device according to claim 3, further comprising:

10. An EAI processing flow management method to be executed by an EAI processing flow management device having a storage unit and a control unit, The storage unit an EAI processing storage means for storing a non-programming setting tool for an EAI processing flow, a template version which is a version of a template flow that is a system cooperation processing composed of common processing tasks and placeholders to which a processing order is linked, a derived flow in which a derived task is incorporated into the placeholder in the template flow, a flow version which is a version of the derived flow, and a derived flow master in which a record linked with a derived use flag indicating whether the flow version can be executed is set; Equipped with Executed in the control unit: a flow modification step of setting the derivation usage flag of the record linked to the derived flow that is the target of the derivation flow modification instruction to "unexecutable" when the flow creator uses the non-programming setting tool to set a derivation flow modification instruction for the derived task that constitutes the derived flow, and additionally setting, to the derived flow master, a record linked to the derived flow that reflects the derivation flow modification instruction, the template version of the template flow that constitutes the derived flow, a new flow version number, and the derivation usage flag that is set to "executable"; 1. An EAI process flow management method comprising:

11. An EAI processing flow management program to be executed by an EAI processing flow management device having a storage unit and a control unit, The storage unit an EAI processing storage means for storing a non-programming setting tool for an EAI processing flow, a template version which is a version of a template flow that is a system cooperation processing composed of common processing tasks and placeholders to which a processing order is linked, a derived flow in which a derived task is incorporated into the placeholder in the template flow, a flow version which is a version of the derived flow, and a derived flow master in which a record linked with a derived use flag indicating whether the flow version can be executed is set; Equipped with In the control unit, a flow modification step of setting the derivation usage flag of the record linked to the derived flow that is the target of the derivation flow modification instruction to "unexecutable" when the flow creator uses the non-programming setting tool to set a derivation flow modification instruction for the derived task that constitutes the derived flow, and additionally setting, to the derived flow master, a record linked to the derived flow that reflects the derivation flow modification instruction, the template version of the template flow that constitutes the derived flow, a new flow version number, and the derivation usage flag that is set to "executable"; An EAI process flow management program for executing the above.

Images