EAI processing flow setting apparatus, EAI processing flow setting method, and EAI processing flow setting program

The EAI process flow setting device allows for independent control and efficient creation of templates and derived flows, enhancing productivity and reducing errors in EAI systems.

JP2025104937APending Publication Date: 2025-07-10OBIC CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2023223134
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-12-28
Publication Date
2025-07-10

AI Technical Summary

Technical Problem

Existing EAI process flow systems lack the ability to create templates and derived flows independently, leading to inefficiencies and errors in flow creation and modification.

Method used

An EAI process flow setting device and method that utilizes a non-programming tool to create templates and derived flows, allowing for independent control over parameters and flow modifications, and supports parameter transfer between templates and derived flows.

Benefits of technology

Improves productivity, reduces errors, and enables high-quality, rapid flow development with independent control over parameters, supporting efficient and error-free flow modifications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025104937000001_ABST
    Figure 2025104937000001_ABST
Patent Text Reader

Abstract

To provide an enterprise application integration (EAI) processing flow setting apparatus, an EAI processing flow setting method, and an EAI processing flow setting program for creating a template of an EAI processing flow using a non-programmable setting tool, to create a derivative flow which inherits and derives from the template.SOLUTION: When a template creator sets a common processing task and a placeholder in the order of processing, using a non-programmable setting tool, an enterprise application integration (EAI) processing flow setting apparatus creates a template flow which is a system integration process composed of the common processing task and the placeholder, and creates, when a flow creator sets a derivative task in the placeholder using the non-programmable setting tool, a derivative flow by embedding the derivative task in the template flow.SELECTED DRAWING: Figure 18
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to an EAI process flow setting device, an EAI process flow setting method, and an EAI process flow setting program.

Background Art

[0002] Patent Document 1 discloses a configuration for automatically generating a business processing program that detects an EAI process flow defined by a system developer using a non-programming tool and executes the detected process flow in parallel.

Prior Art Document

Patent Document

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the invention described in Patent Document 1, since a process flow parallel program is created only from the process flow defined by the system developer, it is not possible to create a template for an EAI (Enterprise Application Integration) process flow and create a derived flow that inherits and derives from the template. There is a problem that the template creator and the derived flow creator cannot perform independent control on the template and the derived flow.

[0005] The present invention has been made in view of the above problems, and an object of the present invention is to provide an EAI process flow setting device, an EAI process flow setting method, and an EAI process flow setting program that can create a template for an EAI process flow and create a derived flow that inherits and derives from the template by using a non-programming setting tool.

Means for Solving the Problem

[0006] In order to solve the above-described problems and achieve the object, the EAI processing flow setting device according to the present invention is an EAI processing flow setting device including a storage unit and a control unit, wherein the storage unit includes EAI processing storage means for storing a non-programming setting tool for an EAI processing flow, and the control unit, when a common processing task and a placeholder are set in accordance with a processing order by using the non-programming setting tool by a template creator, includes template flow creation means for creating a template flow which is a system cooperation process composed of the common processing task and the placeholder, and when a derived task is set in the placeholder by using the non-programming setting tool by a flow creator, includes derived flow creation means for creating a derived flow in which the derived task is incorporated into the template flow.

[0007] Further, in the EAI processing flow setting device according to the present invention, when a flow modification instruction for the template flow is set by using the non-programming setting tool by the template creator, the control unit further includes flow modification means for reflecting the flow modification instruction in each of the derived flows.

[0008] Further, in the EAI processing flow setting device according to the present invention, when a control variable which is a parameter whose value is statically determined by the flow creator is edited, the control unit further includes parameter transfer means for reflecting the control variable in the entire derived flow.

[0009] Further, in the EAI processing flow setting device according to the present invention, the parameter transfer means is characterized in that the control variable is set to be editable, and when the control variable is edited by the flow creator, the control variable is reflected in the entire derived flow.

[0010] Further, in the EAI processing flow setting device according to the present invention, the control unit executes the derived flow in response to a flow execution instruction by a flow executor, and when there is an acquisition of a return value variable which is a parameter whose value is dynamically determined, further includes parameter passing means for reflecting the return value variable in the entire derived flow.

[0011] Further, the EAI processing flow setting method according to the present invention is an EAI processing flow setting method for causing an EAI processing flow setting device including a storage unit and a control unit to execute. The storage unit includes EAI processing storage means for storing a non-programming setting tool for an EAI processing flow. When a common processing task and a placeholder are set in accordance with a processing order by using the non-programming setting tool by a template creator, which is executed in the control unit, a template flow creation step of creating a template flow which is a system cooperation process composed of the common processing task and the placeholder, and when a derived task is set in the placeholder by using the non-programming setting tool by a flow creator, a derived flow creation step of creating a derived flow in which the derived task is incorporated into the template flow.

[0012] Also, the EAI processing flow setting program according to the present invention is an EAI processing flow setting program for causing an EAI processing flow setting device including a storage unit and a control unit to execute. The storage unit includes an EAI processing storage means for storing a non-programming setting tool for the EAI processing flow. In the control unit, when a common processing task and a placeholder are set in accordance with the processing order by using the non-programming setting tool by a template creator, a template flow creation step of creating a template flow which is a system cooperation process composed of the common processing task and the placeholder, and when a derived task is set in the placeholder by using the non-programming setting tool by a flow creator, a derived flow creation step of creating a derived flow in which the derived task is incorporated into the template flow are executed.

Effect of the Invention

[0013] According to the present invention, it is possible to improve productivity and ensure quality in constructing an EAI processing flow. Further, according to the present invention, it is possible to improve the efficiency of the EAI processing flow modification work and suppress setting errors due to human error. Further, according to the present invention, each of the template creator (e.g., system introduction person, etc.) and the flow creator (e.g., system introduction person or customer enterprise, etc.) can perform independent control on the parameters passed between the template and the derived flow. Further, according to the present invention, it is possible to support high-quality and rapid flow development at the time of constructing cooperation. Further, according to the present invention, it is possible to achieve a speedy response and prevention of mistakes in response to changes in the flow at the time of development and introduction. Further, according to the present invention, the template function enables a high-quality flow to be provided at low cost. Further, according to the present invention, it is possible to realize a self-utilization operation in which the customer creates a derived flow by inheriting a template created by an SE. Further, according to the present invention, it is possible to execute the transfer control of parameters between the inherited template flow and the derived flow in the non-programming setting tool for the EAI processing flow.

Brief Description of Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

[0015] Embodiments of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to these embodiments.

[0016] [1. Summary] Referring to FIGS. 1 to 17, the summary of the present invention will be described. FIG. 1 is a diagram showing an example of an EAI processing flow. FIG. 2 is a diagram showing an example of a flow designer screen.

[0017] First, EAI (Enterprise Application Integration) is defined as an approach or technology for integrating different information systems or applications so that they can cooperate effectively. Here, as shown in FIG. 1, in general EAI, each process of the system is defined as a "task", and a series of system cooperation processes are defined as a "flow". In this way, in EAI, the steps of a series of cooperation processes are defined and executed as a flow in which a plurality of tasks are connected. Here, as "tasks", there are tasks for controlling the flow of the flow (for example, conditional branching, loop, etc.), tasks for performing file operations (for example, file movement, Excel (registered trademark) output, variable-length reading, etc.), tasks for performing database operations (for example, execution of update system stored procedures, table reading, transaction control, etc.), tasks for outputting logs (for example, event log output, EAI-specific log output, ERP log, text log output, etc.), and other tasks (for example, sub-flow call, application execution, mail sending, etc.).

[0018] Also, as shown in FIG. 2, the flow realizes system cooperation without programming by associating tasks on the flow designer screen through GUI operations by the flow creator. Here, the flow creator may be a system introduction person or a system administrator of the customer enterprise using the system.

[0019] Here, conventionally, in order to stably operate an EAI cooperation system, for complex flow control and processing in case of errors (for example, "a series of processes for applying a transaction during database update", "error processing", "log output processing", or "notification processing"), high-level knowledge is required even without coding, so a high education cost for flow creators has been required.

[0020] Also, conventionally, when creating a large number of similar flows, a solution has been devised in which a template incorporating the standard control that such a flow should have is provided as a "prototype template", and the template is diverted and replicated, and only the necessary parts are changed to define the actual flow. However, since it involves replication and change, there are problems: (1) at the time of replication, there is a risk of missing to change the parts that need to be changed, or changing the parts that should not be changed; and (2) when a common correction is required for multiple flows after creating them, there is a cost for correcting each flow individually.

[0021] Therefore, in this embodiment, a mechanism is provided to group a series of task processes as an "inheritance template" instead of a "prototype template". Here, in this embodiment, the "inheritance template" is referred to as a "template", and the flow created based on the "template" is referred to as a "derived flow". Here, the "derived flow" is not a copy of the "template", but is created by inheriting the functions of the "template" and adding flow-specific implementations to the "template". By modifying the "template", the "derived flow" is collectively reflected, thereby solving problems (1)-(2). Specifically, in this embodiment, solution (1) is to prepare placeholders in the "template", make only the placeholder part editable when creating a flow, and implement the common parts of complex flow control that can stably operate the EAI cooperation system, such as pre-processing, post-processing, and processing during errors, thereby realizing productivity improvement and quality assurance. Solution (2) is to reflect the modification in the "derived flow" by only modifying the "template". Since the "derived flow" is corrected without omission by the collective reflection of the flow, it is realized to prevent the mistake of forgetting to modify some of the multiple created flows.

[0022] Here, with reference to FIGS. 3 to 6, an example of the outline of solution (1) in this embodiment will be described. FIGS. 3 to 6 are diagrams showing an example of the outline of solution (1) in this embodiment.

[0023] In this embodiment, as shown in FIG. 3, when an inheritance relationship between a template flow and a derived flow is established, as shown in FIG. 4, it is desired to obtain a file and update the master based on the content of the obtained file. However, it is assumed that there are multiple masters for the update destination, and it is necessary to update each master with unique processing, and when it is necessary to create a flow for the number of update targets, the template creator creates a template flow. Here, as shown in FIG. 4, in this embodiment, common processing and error handling on the derived flow side are implemented and shared as pre-processing and common post-processing (1)-(2) for the template flow. The "file acquisition process" is implemented in the common pre-processing assuming that it is a common process regardless of the derived flow. Since the operations after file acquisition differ depending on the derived flow, it is implemented as a placeholder (1), and as error handling when an error occurs within the placeholder (1), "TRY·CATCH" is implemented before and after the placeholder (1). A placeholder (2) is implemented so that the processing after an error occurs can also be individually set depending on the derived flow, and the operation to be commonly performed in the processing after an error occurs: "mail sending" is implemented in the common post-processing (2).

[0024] Then, as shown in FIG. 5, in this embodiment, the derived flow creator creates a derived flow by making settings for the placeholders based on the template flow.

[0025] Then, as shown in FIG. 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 content of the placeholders set for the derived flow into the template of the derived flow inheritance source.

[0026] Also, with reference to FIGS. 7 and 8, an example of the outline of the solution (2) in this embodiment will be described. FIGS. 7 and 8 are diagrams showing an example of the outline of the solution (2) in this embodiment.

[0027] As shown in FIG. 7, in the present embodiment, it is necessary to correct the content that is completed within the common processing on the template flow side, and it is assumed that there is no need to change the derived flow. That is, it is assumed that after the derived flow is created, in the file acquisition process within the common processing, it is found that the subsequent tasks cannot run. When the number of file acquisitions is 0, the common processing of the template is corrected (changed) so that the template creator ends the process.

[0028] Then, as shown in FIG. 8, in the present embodiment, when the flow executor executes the derived flow, a flow in which the placeholder setting content of the derived flow is merged with the inheritance source template is executed at the time of executing the derived flow. By correcting the inheritance source template, when the derived flow is executed, the correction of adding the file acquisition number check to the common preprocessing of the template flow is collectively reflected.

[0029] Further, conventionally, by executing the solutions (1)-(2), new problems occur. When corrections to the "template" that has an impact relationship with the "derived flow" side occur, corrections to both the "template" and the "derived flow" are required. For example, when the email sending process is implemented in both the "template" and the "derived flow", if the email server used by the customer company changes, the problem cannot be solved only by correcting the "template" side, so problem (3) that cannot solve problems (1)-(2) has occurred.

[0030] Therefore, in this embodiment, a mechanism for passing parameters between a "template" and a "derived flow" is provided. Here, in this embodiment, regarding settings where modifications can occur, the "template" implements parameters associated with the "template", and the "derived flow" uses the parameters for setting, thereby solving problem (3) in the form of batch reflection of the "derived flow" by modifying the parameters. Note that in this embodiment, among the parameters to be passed, a parameter whose value is statically determined is defined as a "control variable", and a parameter whose value is dynamically determined is defined as a "return value variable". That is, in this embodiment, a function for creating a "parameter: control variable" with detailed control attributes such as being mandatory / optional for editing and being editable / locked for the setting content when creating a template flow in solution (3) is implemented. By using the control variable in the derived flow, the settings of the "template" and the "derived flow" can be batch-changed by modifying the parameters. By performing control of [mandatory / optional]·[editable / locked] on the control variable of the "template", it is prevented that the "derived flow" is created with unintended setting content. In solution (4), a function for passing the dynamically generated value to each of the template common process and the placeholder is implemented, and a "variable: return value variable" with attributes such as the data type associated with the template flow is implemented. Here, in this embodiment, among the parameters to be passed, a parameter whose value is statically determined is defined as a "control variable", and a parameter whose value is dynamically determined is defined as a "return value variable".

[0031] Here, with reference to FIGS. 9 to 14, an example of the outline of solution (3) in this embodiment will be described. FIGS. 9 to 14 are diagrams showing an example of the outline of solution (3) in this embodiment.

[0032] As shown in FIG. 9, in this embodiment, for control variables associated with a template that can be set separately at the time of template creation and at the time of derivative flow creation, the template creator sets, at the time of template creation, basic attributes such as the type and number of digits of the control variable, and settings for control regarding changes to the control variable at the time of derivative flow creation. At the time of derivative flow creation, the template creator sets what specific values the control variables will take and settings for control such as display / non-display and input required / optional for the flow executor. Here, as shown in FIG. 9, in this embodiment, the control variable (1) has its setting content changed by the derivative flow, and the imported file is different depending on the flow. Although it is unknown at the template creation stage, since it is to be used within the common process, it is made editable with input required on the derivative flow side. The control variable (2) has an invariant value that does not depend on the derivative flow. Since the customer company using it does not use an smtp server other than smtp.xxxx.com and it is common regardless of the derivative flow, it is made non-editable on the derivative flow side.

[0033] Then, as shown in FIG. 10, in this embodiment, the derivative flow creator sets the control variables. Here, as shown in FIG. 10, in this embodiment, in the derivative flow X-1, since it is assumed that the control variable (1) will be determined by user input at the time of execution, display and required settings are made at the time of flow execution. The control variable (2) cannot be changed on the derivative flow side because changes at the time of derivative flow creation by the template creator are set to be disabled. Also, as shown in FIG. 10, in this embodiment, control variables can also be used in placeholders.

[0034] Also, as shown in FIG. 11, in this embodiment, in the derivative flow X-2, since the file acquisition directory is assumed to be a fixed value regardless of the flow executor, it is set to be non-displayed and input is not required at the time of flow execution. Thus, as shown in FIG. 11, in this embodiment, the settings by the derivative flow creator are not reflected in other templates.

[0035] Then, as shown in FIG. 12, in this embodiment, when, during the execution of a flow, settings that are made public to the flow executor are set for a control variable in a derived flow, it becomes possible to set a value for the control variable. [1] Since the content set in the template is the value of the control variable, that is, because it inherits a common template and thus has the same value, [2] it is overwritten by the value set for the control variable on the derived flow side, and since the derived flow cannot be changed by the template creator, the value is directly assigned to the value of the control variable (2).

[0036] Then, as shown in FIG. 13, in this embodiment, [3] when the flow executor makes a setting input, it is overwritten by the set value. For the control variable (1) of the derived flow X-1, a setting is made to display the control variable to the flow executor and it is overwritten by the input value. For the control variable (1) of the derived flow X-2, since the derived flow creator makes it non-displayable during flow execution, the value is not changed. Here, in this embodiment, the state after the flow executor rewrites from "C:\xxxx\yyyy" to "C:\Users\TEMP" is shown.

[0037] Then, as shown in FIG. 14, in this embodiment, based on the determined value of the control variable, the derived flow is executed. Using the value of the control variable (1) as the read file directory, the file acquisition processing task operates. Using the value of the control variable (2) as the smtp server, the email sending task operates.

[0038] Also, with reference to FIGS. 15 to 17, an example of the outline of the solution (4) in this embodiment will be described. FIGS. 15 to 17 are diagrams showing an example of the outline of the solution (4) in this embodiment.

[0039] As shown in Fig. 15, in the present embodiment, when the template creator sets the return value on the return value variable setting screen assumed for the template creator associated with the template, a return value variable associated with the template is created. Here, as shown in Fig. 15, in the present embodiment, the screen after the template creator inputs each item is shown. Also, as shown in Fig. 15, in the present embodiment, the return value variable (1) is prepared as an arbitrarily set variable in the derived flow, and the return value variable (2) can be set on the derived flow side because it is assumed to be used within the common post-processing (2). Also, as shown in Fig. 15, in the present embodiment, since the return value variable (2) can be changed, the value is used assuming that the value is set on the derived flow side.

[0040] Then, as shown in Fig. 16, in the present embodiment, the derived flow creator is setting the return value on the return value variable setting screen. Here, as shown in Fig. 16, in the present embodiment, the screen after the derived flow creator inputs the input value of the return value variable (2) is shown. Also, as shown in Fig. 16, in the present embodiment, when the value can be changed in the derived flow, the value can be set on the derived flow side. For example, for the return value variable (2), "Table update. Exception content" is set on the derived flow side. Also, as shown in Fig. 16, in the present embodiment, when the setting on the derived flow side is possible, it is optional whether to use the return value variable in the derived flow. Also, as shown in Fig. 16, in the present embodiment, the setting screen of the "Loop" task shows the use of the return value variable on the derived flow side.

[0041] Then, as shown in FIG. 17, in the present embodiment, at the flow execution stage, the value of the return value variable is determined at the timing when the task is executed. Here, as shown in FIG. 17, in the present embodiment, the value dynamically set at the return value variable usage location is used, and the value is set in the return value variable at the timing when the task is executed. For example, when the number of acquired items is 10, the return value variable (1): 10 is set. Also, as shown in FIG. 17, in the present embodiment, the value is set in the return value variable at the timing when the task is executed. For example, when an exception of type error occurs, the return value variable (2): "The types do not match" is set.

[0042] [2. Configuration] An example of the configuration of the EAI processing flow setting device 100 according to the present embodiment will be described with reference to FIGS. 18 and 19. FIG. 18 is a block diagram showing an example of the configuration of the EAI processing flow setting device 100 in the present embodiment.

[0043] As shown in FIG. 18, the EAI processing flow setting device 100 is a commercially available desktop personal computer. Note that the EAI processing flow setting 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 Assistants), smartphone, or tablet personal computer.

[0044] The EAI processing flow setting device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the EAI processing flow setting device 100 is communicably connected via an arbitrary communication path.

[0045] The communication interface unit 104 communicably connects the EAI processing flow setting 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 a communication line. Here, the network 300 has a function of communicably connecting the EAI processing flow setting device 100 and the server 200 to each other, and is, for example, the Internet or a LAN (Local Area Network).

[0046] An input / output interface unit 108 has an input device 112 and an output device 114 connected thereto. As the output device 114, in addition to a monitor (including a touch panel), a speaker or a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. Hereinafter, the output device 114 may be described as the monitor 114 or the printer 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

[0047] The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records a computer program for giving commands to the CPU (Central Processing Unit) in cooperation with the OS (Operating System) to perform various processes. As the storage unit 106, 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, and an optical disk can be used. The storage unit 106 includes an EAI processing database 106a.

[0048] The EAI processing database 106a stores EAI processing data. Here, the EAI processing database 106a may store a non-programming setting tool for the EAI processing flow. Also, the EAI processing database 106a may store an EAI processing master to be referred to during the execution of the derived flow. Here, the EAI processing master may include a flow (without template) master, a template flow master, a derived flow (with template)_header master, a derived flow (with template)_detail master, a template control variable master, a derived flow control variable master, a template return value variable master, and a derived flow return value variable master.

[0049] Here, referring to FIG. 19, an example of the data structure related to the template function in the present embodiment will be described. FIG. 19 is a diagram showing an example of the master configuration in the present embodiment.

[0050] As shown in FIG. 19, in the present embodiment, during the execution of the derived flow, the flow data of the template flow associated with the template ID of the flow (with template)_header master and the detail flow data associated with the flow ID of the flow (with template)_header master are used to execute the flow. Here, as shown in FIG. 19, the detail flow ID is used to identify the placeholder. Also, as shown in FIG. 19, the primary key is indicated by diagonal lines.

[0051] Returning to FIG. 18, the control unit 102 is a CPU or the like that comprehensively controls the EAI processing flow setting device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program defining various processing procedures, and required data, and executes various information processes based on these stored programs. Conceptually in terms of functions, the control unit 102 includes a template flow creation unit 102a, a derived flow creation unit 102b, a flow modification unit 102c, a parameter transfer unit 102d, and a flow execution unit 102e.

[0052] The template flow creation unit 102a creates a template flow, which is a system cooperation process. Here, when the common processing tasks and placeholders are set in accordance with the processing order by using a non-programming setting tool by the template creator, the template flow creation unit 102a may create a template flow, which is a system cooperation process composed of the common processing tasks and placeholders. Also, the template flow creation unit 102a may register the template flow in the EAI processing master.

[0053] The derived flow creation unit 102b creates a derived flow in which the derived tasks are incorporated into the template flow. Here, when a derived task is set in the placeholder by using a non-programming setting tool by the flow creator, the derived flow creation unit 102b may create a derived flow in which the derived task is incorporated into the template flow. Also, the derived flow creation unit 102b may register the derived flow in the EAI processing master.

[0054] The flow modification unit 102c reflects a flow modification instruction for the template flow in the derived flow. Here, when a flow modification instruction for the template flow is set by using a non-programming setting tool by the template creator, the flow modification unit 102c may reflect the flow modification instruction in each derived flow.

[0055] The parameter passing unit 102d reflects a control variable, which is a parameter with a statically determined value, throughout the derived flow. Here, when the control variable, which is a parameter with a statically determined value, is edited by the flow creator, the parameter passing unit 102d may reflect the control variable throughout the derived flow. Also, when the control variable is set to be editable and the control variable is edited by the flow creator, the parameter passing unit 102d may reflect the control variable throughout the derived flow. Also, the parameter passing unit 102d may register the control variable in the EAI processing master.

[0056] The flow execution unit 102e executes the derived flow. Here, the flow execution unit 102e executes the derived flow in response to a flow execution instruction from a flow executor. When there is an acquisition of a return value variable, which is a parameter whose value is dynamically determined, the flow execution unit 102e may reflect the return value variable throughout the derived flow. Further, the flow execution unit 102e may register the return value variable in the EAI processing master.

[0057] [3. Specific Example] A specific example of the present embodiment will be described with reference to FIGS. 20 to 35.

[0058] [EAI Processing Flow Setting Process] Here, with reference to FIG. 20, an example of the EAI processing flow setting process in the present embodiment will be described. FIG. 20 is a flowchart showing an example of the processing of the EAI processing flow setting apparatus 100 in the present embodiment.

[0059] As shown in FIG. 20, when the template flow creation unit 102a sets common processing tasks and placeholders in accordance with the processing order via the input device 112 by using a non-programming setting tool by a template creator, the template flow creation unit 102a creates a template flow, which is a system cooperation process composed of the common processing tasks and the placeholders, and registers the template flow in the EAI processing master (step SA-1).

[0060] Then, when the derived flow creation unit 102b sets derived tasks in the placeholders via the input device 112 by using a non-programming setting tool by a flow creator, the derived flow creation unit 102b creates a derived flow in which the derived tasks are incorporated into the template flow, and registers the derived flow in the EAI processing master (step SA-2).

[0061] Then, the flow modification unit 102c determines whether a flow modification instruction for the template flow is set via the input device 112 by using a non-programming setting tool by a template creator (step SA-3).

[0062] And when the flow correction unit 102c determines that no flow correction instruction for the template flow is set (step SA-3: No), it causes the process to proceed to step SA-5.

[0063] On the other hand, when the flow correction unit 102c determines that a flow correction instruction for the template flow is set (step SA-3: Yes), it causes the process to proceed to step SA-4.

[0064] And the flow correction unit 102c reflects the flow correction instruction in each derived flow (step SA-4).

[0065] And the parameter transfer unit 102d determines whether a control variable, which is a parameter whose value is statically determined by the flow creator via the input device 112, has been edited (step SA-5).

[0066] And when the parameter transfer unit 102d determines that the control variable, which is a parameter whose value is statically determined, has not been edited (step SA-5: No), it causes the process to proceed to step SA-7.

[0067] On the other hand, when the parameter transfer unit 102d determines that the control variable, which is a parameter whose value is statically determined, has been edited (step SA-5: Yes), it causes the process to proceed to step SA-6.

[0068] And the parameter transfer unit 102d reflects the control variable in the entire derived flow and registers the control variable in the EAI process master (step SA-6).

[0069] And the flow execution unit 102e executes the derived flow in response to a flow execution instruction via the input device 112 by the flow executor (step SA-7).

[0070] And the flow execution unit 102e determines whether there is an acquisition of a return value variable, which is a parameter whose value is dynamically determined (step SA-8).

[0071] When there is no acquisition of a return value variable, which is a parameter whose value is determined dynamically, by the flow execution unit 102e (step SA-8: No), the derived flow is completed and the process ends.

[0072] On the other hand, when there is an acquisition of a return value variable, which is a parameter whose value is determined dynamically, by the flow execution unit 102e (step SA-8: Yes), the process is transferred to step SA-9.

[0073] Then, the flow execution unit 102e registers the return value variable in the EAI process master, reflects the return value variable throughout the derived flow, completes the derived flow (step SA-9), and ends the process.

[0074] Here, with reference to FIGS. 21 to 25, an example of the flow creation process in the present embodiment will be described. FIGS. 21 to 25 are diagrams showing an example of the flow creation process in the present embodiment.

[0075] As shown in FIG. 21, in the present embodiment, a new template is created, and a derived flow is created based on the created template. That is, as shown in FIG. 21, in the present embodiment, when it is necessary to create a plurality of flows for importing a file and updating the imported data to the master, the common process of each flow is created as a template, and the different parts of the flow are prepared as placeholders, so as to create a derived flow based on the created template.

[0076] First, as shown in FIG. 21, in this embodiment, [1] an operator (template creator) creates a new flow as a template. Here, as shown in FIG. 21, in this embodiment, a "data classification" that is used at the time of process branching and selects whether to execute csv reading or Excel reading depending on the value, a "directory path" and a "file name" for which a frame is prepared because the location and file name of the reading target are required in the reading task and are assumed to be specified at the time of execution, and an "smtp server" used in the mail sending task are assumed, and the flow is created. Also, in this embodiment, since there is no assumption of sending mails to domains other than smtp.xxxx.com, an initial value is entered to prevent errors due to changes in the smtp server name on the derived flow side so that it cannot be changed on the derived flow side.

[0077] Then, as shown in FIG. 22, in this embodiment, the master is updated. Here, as shown in FIG. 22, in this embodiment, the content (with numbers described) entered on each screen corresponds to the number of the master.

[0078] Then, as shown in FIG. 23, in this embodiment, [2] an operator (derived flow creator) creates a flow based on the template. Here, as shown in FIG. 23, in this embodiment, when the template to be used is selected, the screen transitions to the designer screen. Also, as shown in FIG. 23, in this embodiment, tasks that are not placeholders cannot be edited, but the setting contents of the tasks can be viewed. Also, as shown in FIG. 23, in this embodiment, when the derived flow creator clicks on the placeholder (1) of the template flow, the placeholder to be set can be changed on the editing screen in the center.

[0079] Then, as shown in FIG. 24, in this embodiment, when the derivative flow creator clicks on the placeholder (2) of the template flow, the placeholder to be set can be changed on the editing screen in the center. Here, as shown in FIG. 24, in this embodiment, for the derivative flow: tax classification master import, when using an extension other than csv and setting the value to 0, the "data classification" that is not publicly available to the flow executor, the "directory path" and "file name" which are assumed to be specified during execution and for which the input of the flow executor is made mandatory, and in the template control variable settings, items that cannot be changed are locked so that they cannot be changed, control variables are available in the placeholder, and since it is assumed to be used when checking the value, a "smtp server" that is not blank but is screen-locked is assumed, and the flow is created.

[0080] Then, as shown in FIG. 25, in this embodiment, master updates are performed, and the content (numbers are described) entered on each screen corresponds to the numbers in the master. And, as shown in FIG. 25, in this embodiment, [3] the operator (flow executor) opens the flow execution screen, and only the items where "whether to be publicly available to the flow executor" is True are displayed on the screen. An asterisk is added to the items that are set to be mandatory in the derivative flow control variable settings. The flow executor inputs values, and during flow execution, it is verified whether values are entered for the mandatory items, and verification of the type and number of digits of the input values is performed. If there are no problems, the flow is executed.

[0081] Also, with reference to FIGS. 26 to 35, an example of the derivative flow execution process inheriting the template in this embodiment will be described. FIGS. 26 to 35 are diagrams showing an example of the derivative flow execution process inheriting the template in this embodiment.

[0082] As shown in FIG. 26, in this embodiment, there is processing set for each task, and when the derived flow is executed, the tasks are interpreted and executed according to the flow. That is, as shown in FIG. 26, in this embodiment, [1] the flow executor is executing a derived flow that inherits a template. Here, as shown in FIG. 26, in this embodiment, it shows the state where the flow executor has input values from the initial screen.

[0083] And, as shown in FIG. 27, in this embodiment, the values of the control variables during flow execution are determined, and [1-1] the values of the template control variable master associated with the derived flow are acquired.

[0084] And, as shown in FIG. 28, in this embodiment, [1-2] values are acquired from the derived flow control variable master associated with [derived flow (with template)_header master] and [template control variable master], and overwritten. Here, as shown in FIG. 28, in this embodiment, items for which "cannot be changed on the derived flow side" is True are excluded from the overwrite target, so they are not acquired.

[0085] And, as shown in FIG. 29, in this embodiment, [1-3] it is overwritten with the values input by the flow executor.

[0086] And, as shown in FIG. 30, in this embodiment, [2] flow data is acquired from the "template flow master" associated with 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.

[0087] And, as shown in FIG. 31, in this embodiment, [3] the control variables determined in [1] are set in the flow created in [2], and the determined values are respectively substituted.

[0088] Then, as shown in FIGS. 32 to 35, in this embodiment, tasks are executed according to the [4] flow. When moving from the template common process to the placeholder task or from the placeholder to the template common process, the value of the return value variable is set. Here, as shown in FIG. 32, in this embodiment, a value is set in the return value variable in the common process, that is, the value is set when the task set by the return value variable is executed. Also, as shown in FIG. 33, in this embodiment, the return value variable is used in the common process, that is, the return value variable is dynamically set when the task is executed. Further, in this embodiment, as shown in FIG. 34, a value is set in the return value variable in the placeholder, and as shown in FIG. 35, the return value variable is used in the common process. Here, FIG. 34 shows the case where an error occurs during the execution of the update system stored procedure in the placeholder and branches to the CATCH process.

[0089] [4. Contribution to the United Nations Sustainable Development Goals (SDGs)] According to this embodiment, it is possible to contribute to improving business efficiency and making appropriate business decisions of enterprises, so it is possible to contribute to Goals 8 and 9 of the SDGs.

[0090] Also, according to this embodiment, it is possible to contribute to reducing waste loss and promoting paperless and digitalization, so it is possible to contribute to Goals 12, 13, and 15 of the SDGs.

[0091] Also, according to this embodiment, it is possible to contribute to strengthening control and governance, so it is possible to contribute to Goal 16 of the SDGs.

[0092] [5. Other Embodiments] The present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims, in addition to the above-described embodiments.

[0093] For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all or part of the processes described as being manually performed can be automatically performed by a known method.

[0094] In addition, regarding 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 the drawings, they can be arbitrarily changed unless otherwise specified.

[0095] Also, regarding the EAI processing flow setting device 100, each of the illustrated components is a functional concept and does not necessarily need to be physically configured as shown in the drawings.

[0096] For example, regarding the processing functions provided by the EAI processing flow setting device 100, particularly each processing function performed by the control unit 102, all or any part of them may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing an information processing device to execute the processes described in this embodiment, and is mechanically read by the EAI processing flow setting device 100 as needed. That is, in a storage unit such as a ROM or an HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS to perform various processes is recorded. This computer program is executed by being loaded into the RAM and constitutes the control unit in cooperation with the CPU.

[0097] Also, this computer program may be stored in an application program server connected to the EAI processing flow setting device 100 via an arbitrary network, and all or part of it can be downloaded as needed.

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

[0099] Also, the "program" is a data processing method described in any language or description method, and is not limited to a specific form such as source code or binary code. Note that the "program" is not necessarily limited to a single configuration, and also includes those that are distributed as a plurality of modules or libraries, or those that achieve their functions in cooperation with other separate programs represented by an OS. Note that for the specific configuration, reading procedure, and installation procedure after reading for reading the recording medium in each device shown in this embodiment, well-known configurations and procedures can be used.

[0100] The various databases and the like stored in the storage unit 106 are storage means such as a memory device such as a RAM or a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0101] Further, the EAI processing flow setting 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. Further, the EAI processing flow setting device 100 may be realized by installing software (including programs or data, etc.) for realizing the processing described in this embodiment in the device.

[0102] Furthermore, the specific form of the distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or according to the functional load. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Industrial Applicability

[0103] The present invention is useful in various industries where it is necessary to link a plurality of systems used in business within a company.

Explanation of Signs

[0104] 100 EAI processing flow setting device 102 Control unit 102a Template flow creation unit 102b Derived flow creation unit 102c Flow correction unit 102d Parameter transfer unit 102e Flow execution unit 104 Communication interface unit 106 Storage unit 106a EAI processing database 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims

1. An EAI processing flow setting device comprising a storage unit and a control unit, wherein the storage unit comprises EAI processing storage means for storing a non-programming setting tool for an EAI processing flow, and the control unit template flow creation means for creating a template flow, which is a system cooperation process composed of the common processing task and the placeholder, when the common processing task and the placeholder are set in accordance with the processing order by using the non-programming setting tool by a template creator; derived flow creation means for creating a derived flow in which the derived task is incorporated into the template flow when the derived task is set in the placeholder by using the non-programming setting tool by a flow creator, characterized in that the EAI processing flow setting device comprises the above.

2. The control unit further comprises flow modification means for reflecting the flow modification instruction in each derived flow when a flow modification instruction for the template flow is set by using the non-programming setting tool by the template creator. The EAI processing flow setting device according to claim 1, characterized in that it further comprises the above.

3. The control unit further comprises parameter transfer means for reflecting the control variable, which is a parameter whose value is statically determined by the flow creator, throughout the derived flow when the control variable is edited. The EAI processing flow setting device according to claim 1 or 2, characterized in that it further comprises the above.

4. The parameter transfer means is characterized in that the control variable is set to be editable, and when the control variable is edited by the flow creator, the control variable is reflected throughout the derived flow. The EAI processing flow setting device according to claim 3.

5. The control unit further comprises parameter transfer means for executing the derived flow in response to a flow execution instruction by a flow executor and reflecting the return value variable, which is a parameter whose value is dynamically determined, throughout the derived flow when there is an acquisition of the return value variable. The EAI processing flow setting device according to claim 1 or 2, characterized in that it further comprises the above.

6. An EAI processing flow setting method for causing an EAI processing flow setting device comprising a storage unit and a control unit to execute, wherein the storage unit comprises EAI processing storage means for storing a non-programming setting tool for an EAI processing flow, and When executed in the control unit, a template flow creation step of creating a template flow, which is a system cooperation process composed of the common processing tasks and the placeholders, in accordance with the processing order when the common processing tasks and the placeholders are set by a template creator using the non-programming setting tool; a derived flow creation step of creating a derived flow in which the derived task is incorporated into the template flow when the derived task is set for the placeholder by a flow creator using the non-programming setting tool; An EAI processing flow setting method characterized by including the above.

7. An EAI processing flow setting program for causing an EAI processing flow setting device including a storage unit and a control unit to execute, wherein the storage unit has an EAI processing storage means for storing a non-programming setting tool for the EAI processing flow; and in the control unit, a template flow creation step of creating a template flow, which is a system cooperation process composed of the common processing tasks and the placeholders, in accordance with the processing order when the common processing tasks and the placeholders are set by a template creator using the non-programming setting tool; a derived flow creation step of creating a derived flow in which the derived task is incorporated into the template flow when the derived task is set for the placeholder by a flow creator using the non-programming setting tool; An EAI processing flow setting program for causing the above to be executed.

Citation Information

Patent Citations

  • Information processing device, information processing program, and information processing method

    JP2022059478A

  • Program generation device and method

    JP2004178301A