A service logic generation method, device and terminal

Abstract

The application discloses a kind of service logic generation method, device and terminal, the method includes: response is created in the event trigger logic node including service event identification in the first creation request on service flow editing interface;Response is obtained from the target basic node matched with target node type in the second creation request on service flow editing interface in basic node library;The target basic node includes node capability editing interface, and the node capability editing interface is configured with service capability information;Response is determined to the target service capability of target basic node by the selection instruction to the service capability information, and obtains service logic node;Response is determined logic node call relationship by the association instruction to event trigger logic node and service logic node;According to logic node call relationship, generates target service logic.The application enables non-programmer to edit and generate the required service logic in the way of flow chart, improves the generation efficiency of service logic.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a business logic generation method, apparatus, and terminal. Background Technology

[0002] In related technologies, when implementing business logic such as the logic of a game level or the logic of the entire game, a visual logic editor is usually provided, such as PlayMaker based on finite state machines and Blueprint based on function calls.

[0003] The basic principle of PlayMaker is a finite state machine. In PlayMaker, such as... Figure 1a As shown, developers define several operations and the possible states that each operation can produce. Users then connect the states of these operations with other operations to form a logical chain. The basic principle of Blueprints is to visualize function-level calls. In PlayMaker, for example... Figure 1b As shown, the developers implemented several functions, defined the parameters required by the functions and the return values. Users chain these functions together and connect the parameters of each function to corresponding variables. Mathematical or logical operations can be performed on the variables. If a logical branch is encountered, various branch controllers are also required.

[0004] However, the above-mentioned way of editing business logic is not user-friendly for business planners. The operations or logic that planners need to care about are too granular, and they need to have a certain programming foundation to edit business logic. Moreover, it is inconvenient to bring together operations or logic that are executed at the same time, making the connections in the logic flow redundant and complicated, which is not convenient for later maintenance and processing. Summary of the Invention

[0005] To address the problems of existing technologies, embodiments of the present invention provide a business logic generation method, apparatus, and terminal. The technical solution is as follows:

[0006] On the one hand, a business logic generation method is provided, the method comprising:

[0007] In response to the first creation request on the business process editing interface, an event triggering logic node is created; the event triggering logic node includes a business event identifier;

[0008] In response to a second creation request on the business process editing interface, a target basic node matching the target node type is obtained from the basic node library; the target basic node includes a node capability editing interface, which is configured with business capability information;

[0009] In response to the selection instruction for the business capability information, the target business capability of the target basic node is determined to obtain the business logic node;

[0010] In response to the association instruction between the event triggering logic node and the business logic node, the logic node invocation relationship is determined;

[0011] Based on the logical node call relationship, the target business logic is generated.

[0012] On the other hand, a business logic generation apparatus is provided, the apparatus comprising:

[0013] The first creation module is used to create an event triggering logic node in response to a first creation request on the business process editing interface; the event triggering logic node includes a business event identifier;

[0014] The second creation module is used to respond to the second creation request on the business process editing interface and obtain a target basic node that matches the target node type from the basic node library; the target basic node includes a node capability editing interface, which is configured with business capability information;

[0015] The node business capability determination module is used to determine the target business capability of the target basic node in response to the selection instruction for the business capability information, and obtain the business logic node.

[0016] The call relationship determination module is used to determine the call relationship of logical nodes in response to the association instruction between the event triggering logical node and the business logic node;

[0017] The business logic generation module is used to generate the target business logic based on the logic node call relationship.

[0018] As an optional implementation, if the target node type is a first node type and the target base node is a first base node, the business capability information of the first base node includes multiple business scripts;

[0019] Accordingly, the node service capability determination module includes:

[0020] The first determining module is configured to determine at least one target business script in response to the selection instruction for the plurality of business scripts;

[0021] The second determining module is used to determine the execution order of the at least one target business script in response to the position adjustment instruction of the at least one target business script;

[0022] The third determining module is used to determine the target business capabilities of the target basic node based on the execution order of the at least one target business script.

[0023] As an optional implementation, if the target node type is a second node type, the target base node includes an immediate condition sub-node and the first base node; the service capability information of the immediate condition sub-node includes immediate judgment conditions.

[0024] Accordingly, the node service capability determination module includes:

[0025] The instant condition determination module is used to determine the target instant judgment condition in response to the selection instruction for the instant judgment condition of the instant condition sub-node.

[0026] The first establishment module is used to establish a call to the first basic node when the determination result of the immediate judgment condition of the target is true;

[0027] The fourth determining module is used to determine at least one target business script in response to a selection instruction for multiple business scripts of the first basic node.

[0028] The fifth determining module is used to determine the execution order of the at least one target business script in response to the position adjustment instruction of the at least one target business script;

[0029] The sixth determining module is used to determine the target business capabilities of the target basic node based on the target judgment conditions and the execution order of the at least one target business script.

[0030] As an optional implementation, if the target node type is a third node type, the target base node includes a monitoring sub-node and the first base node; the service capability information of the monitoring sub-node includes monitoring triggering conditions;

[0031] Accordingly, the node service capability determination module includes:

[0032] The monitoring condition module is used to determine the target monitoring trigger condition in response to the selection instruction for the monitoring trigger condition of the monitoring sub-node;

[0033] The first calling module is used to call the first basic node when the target monitoring triggering condition is met;

[0034] The seventh determining module is used to determine at least one target business script in response to a selection instruction for multiple business scripts of the first basic node.

[0035] The eighth determining module is used to determine the execution order of the at least one target business script in response to the position adjustment instruction of the at least one target business script;

[0036] The ninth determining module is used to determine the target business capabilities of the target basic node based on the target monitoring triggering conditions and the execution order of the at least one target business script.

[0037] As an optional implementation, the at least one target business script includes a jump branch script; the call relationship determination module includes:

[0038] The first call relationship determination module is used to determine the first call relationship between the event triggering logic node and the first business logic node in response to the association instruction of the output port of the event triggering logic node and the input port of the first business logic node;

[0039] The second call relationship determination module is used to determine the second call relationship between the jump branch script and the second business logic node in response to the association instruction of the output port of the jump branch script and the input port of the second business logic node;

[0040] The business logic nodes include the first business logic node and the second business logic node; the logic node calling relationship includes the first calling relationship and the second calling relationship.

[0041] As an optional implementation, the at least one target service script includes a script awaiting execution; the node service capability determination module further includes:

[0042] The waiting time determination module is used to determine the waiting execution time in response to the setting instruction for the time parameter of the script to be executed.

[0043] Accordingly, when determining the target business capabilities of the target basic node, the node business capability determination module also determines the target business capabilities of the target basic node based on the waiting execution time.

[0044] As an optional implementation, the apparatus further includes:

[0045] An encapsulation module is used to encapsulate the target business logic in response to an encapsulation instruction for the target business logic to obtain a sub-process logic node;

[0046] The input / output node creation module is used to create input nodes and output nodes respectively in response to input / output creation requests for the sub-process logic nodes;

[0047] The tenth determining module is used to determine the input port and output port of the sub-process logic node in response to an association instruction that associates the input node and output node with the sub-process logic node respectively;

[0048] A storage module is used to store the sub-process logic nodes in response to a storage command.

[0049] As an optional implementation, the apparatus further includes:

[0050] The sub-process logic node invocation module is used to respond to sub-process logic node invocation requests on the business process editing interface and invoke the target sub-process logic node.

[0051] Accordingly, the calling relationship determination module is used to determine the calling relationship of logical nodes in response to the association instructions of the event triggering logical node, the business logical node and the target sub-process logical node.

[0052] On the other hand, a terminal is provided, including a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the above-mentioned business logic generation method.

[0053] On the other hand, a computer-readable storage medium is provided, wherein at least one instruction or at least one program is stored therein, the at least one instruction or the at least one program being loaded and executed by a processor to implement the business logic generation method described above.

[0054] On the other hand, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the business logic generation method provided in the various optional implementations described above.

[0055] This invention, in response to a first creation request on the business process editing interface, creates an event-triggered logic node containing a business event identifier. In response to a second creation request on the same interface, it retrieves a target basic node from a basic node library that matches the target node type. This target basic node includes a node capability editing interface configured with business capability information. Then, in response to a selection instruction on the business capability information of the node capability editing interface, it determines the target business capability of the target basic node to obtain a business logic node. Finally, in response to an association instruction between the event-triggered logic node and the business logic node, it determines the logic node call relationship, thereby generating the target business logic based on this logic node call relationship. In this technical solution, non-programmers can quickly edit and generate the required business logic using a flowchart, eliminating the need for planners to pay fine-grained attention to operations or logic. Furthermore, the relationships within the logic flow are concise and clear, facilitating later maintenance and processing, and improving the efficiency of business logic generation. Attached Figure Description

[0056] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0057] Figure 1a This is a schematic diagram illustrating the basic principles of PlayMaker in existing technologies;

[0058] Figure 1b This is a schematic diagram of the basic principle of Blueprint in existing technology;

[0059] Figure 2 This is a flowchart illustrating a business logic generation method provided in an embodiment of the present invention;

[0060] Figure 3a These are conceptual diagrams, structural block diagrams, and interface schematic diagrams of the event triggering logic nodes provided in embodiments of the present invention;

[0061] Figure 3b This is an example of parameter editing for a business script provided in an embodiment of the present invention;

[0062] Figure 3c These are conceptual diagrams, structural block diagrams, and interface schematic diagrams of ordinary business logic nodes provided in embodiments of the present invention;

[0063] Figure 3d These are conceptual diagrams, structural block diagrams, and interface schematics of the real-time conditional logic node provided in the embodiments of the present invention;

[0064] Figure 3e These are conceptual diagrams, structural block diagrams, and interface schematic diagrams of the trigger condition logic nodes provided in embodiments of the present invention;

[0065] Figure 4a This invention provides a conceptual diagram, structural block diagram, and interface schematic diagram of execution waiting between the internal logic of a common logic node.

[0066] Figure 4b This invention provides a conceptual diagram, structural block diagram, and interface diagram of the execution of internal logic branches between the internal logic of a common logic node.

[0067] Figure 4c This is a structural block diagram and interface diagram of the execution of custom flow scripts between the internal logic of ordinary logic nodes provided in the embodiments of the present invention;

[0068] Figure 5 These are conceptual diagrams, structural block diagrams, and interface schematic diagrams of the loop logic provided in embodiments of the present invention;

[0069] Figure 6a This is a schematic diagram of the interface for defining the input and output nodes of a sub-process logic node, provided in an embodiment of the present invention.

[0070] Figure 6b This is an example diagram of the calling sub-process logic node provided in an embodiment of the present invention;

[0071] Figure 7 This is a schematic diagram of the basic underlying framework provided in the embodiments of the present invention;

[0072] Figure 8 This is a schematic diagram of the data structure involved in the embodiments of the present invention;

[0073] Figure 9 This is a structural block diagram of the business logic generation device provided in an embodiment of the present invention;

[0074] Figure 10 This is a hardware structure block diagram of a terminal provided in an embodiment of the present invention. Detailed Implementation

[0075] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0076] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0077] This invention provides a business logic generation method, which can be applied to a business logic generation device that can be configured in electronic devices such as terminals. The terminal may include, but is not limited to, smartphones, desktop computers, tablet computers, laptops, digital assistants, etc.

[0078] Please see Figure 2 The diagram illustrates a flowchart of a business logic generation method according to an embodiment of the present invention. It should be noted that this specification provides the operational steps described in the embodiments or flowcharts, but based on conventional or non-inventive labor, more or fewer operational steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many steps and does not represent the only execution order. In actual system or product execution, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment). Specifically, as shown... Figure 2 As shown, the method may include:

[0079] S201, in response to the first creation request on the business process editing interface, creates an event triggering logic node.

[0080] The event triggering logic node includes a business event identifier, which is used to identify the event that triggers the business logic, such as the start event that triggers the logic execution. Figure 3a The diagram shown is a conceptual diagram, structural block diagram, and interface diagram of an event triggering logic node. This event triggering logic node also includes an output port, through which the event triggering logic node can establish a calling relationship with other logic nodes.

[0081] S203, in response to the second creation request on the business process editing interface, retrieves the target basic node that matches the target node type from the basic node library.

[0082] The second creation request may carry a target node type. The target base node includes a node capability editing interface, which is configured with business capability information. In specific implementation, the user can right-click on the business process editing interface to bring up a node type list. The user can select the target node type to be created from this list. Once the target node type is selected, the terminal can generate a second creation request based on that target node type and, in response to the second creation request, retrieve a target base node matching that target node type from the base node library.

[0083] In this embodiment of the invention, the node capabilities of the basic nodes in the basic node library can be configured by the user according to actual needs. Node capability refers to the logical function that the node can perform, and can be determined based on the user's selection of business capability information. The node types of the basic nodes included in the basic node library can include ordinary node types, immediate condition node types, trigger condition node types, and event node types. The business capability information corresponding to each basic node can correspond to its node type; the business capability information under different node types can be the same or different.

[0084] It should be noted that the basic node also includes an input port and an output port. The basic node can be associated through the input port and the output port, thereby establishing a call to the basic node.

[0085] S205, in response to the selection instruction for the business capability information, determine the target business capability of the target basic node to obtain the business logic node.

[0086] Specifically, users can access the business capability information corresponding to the node capability editing interface through the node capability editing interface of the target basic node, select the target business capability information from the business capability information, and thus, based on the selected target business capability information, the target basic node can have the target node capability required by the user, that is, obtain the corresponding business logic node.

[0087] As a possible implementation, if the target node type is the first node type, i.e., the aforementioned ordinary node type, then the target base node matching this target node type is the first base node, and the service capability information of the first base node may include multiple service scripts. Accordingly, step S205 above, in response to the selection instruction for the service capability information, determining the target service capability of the target base node may include the following steps:

[0088] (1) In response to the selection instruction for the plurality of business scripts, at least one target business script is determined.

[0089] Specifically, users can access the multiple business scripts through the node capability editing interface of the first basic node, and select one or more of the required business scripts. The selected one or more will then be the at least one target business script.

[0090] In practical applications, business parameters in the selected business script can also be set, such as... Figure 3b The example shown is a parameter editing feature of a business script. The business script provides a drop-down list for each business parameter, allowing users to select the parameter value as needed.

[0091] (2) In response to the position adjustment instruction of the at least one target business script, determine the execution order of the at least one target business script.

[0092] Specifically, users can adjust the positional relationship of at least one selected target business script according to the actual needs of the node's business capabilities, thereby determining the execution order of the at least one target business script.

[0093] (3) Determine the target business capabilities of the target basic node according to the execution order of the at least one target business script.

[0094] like Figure 3c The diagram shown is a conceptual diagram, structural block diagram, and interface diagram of a common business logic node. This common business logic node is the first basic node with the target business capability. The target business capability is determined by multiple selected scripts, such as script 1 and script 2, in the structural block diagram, as well as the positional relationship of each selected script.

[0095] As a possible implementation, if the target node type is the second node type, i.e., the aforementioned instantaneous condition node type, then the target base node matching this target node type includes an instantaneous condition sub-node and the aforementioned first base node. The service capability information of the instantaneous condition sub-node includes an instantaneous judgment condition. When the judgment result of the judgment condition is true, the first base node will be executed. Accordingly, step S205 above, in response to the selection instruction for the service capability information, determining the target service capability of the target base node may include the following steps:

[0096] (1) In response to the selection instruction for the instant judgment condition of the instant condition sub-node, determine the target instant judgment condition.

[0097] Specifically, the immediate condition sub-node is pre-configured with multiple immediate judgment conditions. These immediate judgment conditions are made on the spot, and users can select the target immediate judgment condition from among the multiple immediate judgment conditions as needed. Understandably, the parameter values ​​of the immediate condition parameters can be set for the selected target immediate judgment condition.

[0098] (2) When the judgment result of the immediate judgment condition of the target is true, a call to the first basic node is established.

[0099] In this embodiment of the invention, the base node of the instant condition node type combines the instant condition sub-node and the first base node in the same process node, and the first base node in the process node serves as the execution object when the instant condition sub-node's instant judgment condition is true. When editing the base node of the instant node type, the user only needs to select the instant judgment condition in the instant condition sub-node and the business capability information of the first base node in the process node.

[0100] (3) In response to the selection instruction for multiple business scripts of the first basic node, at least one target business script is determined.

[0101] (4) In response to the position adjustment instruction of the at least one target business script, determine the execution order of the at least one target business script.

[0102] (5) Determine the target business capabilities of the target basic node based on the target real-time judgment conditions and the execution order of the at least one target business script.

[0103] like Figure 3d The diagram shown is a conceptual diagram, structural block diagram, and interface diagram of an immediate conditional logic node. This immediate conditional logic node is the basic node of the immediate conditional node type with target business capabilities. The target business capabilities are determined by the immediate condition judgment in the structural block diagram, multiple selected scripts such as script 1 and script 2, and the positional relationship of each selected script.

[0104] As a possible implementation, if the target node type is the third node type, i.e., the aforementioned trigger condition node type, then the target basic nodes matching this target node type include the monitoring sub-node and the aforementioned first basic node. The business capability information of the monitoring sub-node includes the monitoring trigger condition. When the monitoring trigger condition is met, the first basic node will be executed. The monitoring trigger condition is not determined immediately, but rather delayed. For example, it monitors the occurrence of an event; when the event actually occurs, the monitoring trigger condition is met, and the first basic node is executed. Accordingly, step S205 above, in response to the selection instruction for the business capability information, determining the target business capability of the target basic node may include the following steps:

[0105] (1) In response to the selection instruction for the monitoring trigger condition of the monitoring sub-node, determine the target monitoring trigger condition.

[0106] Specifically, the monitoring sub-node is pre-configured with multiple monitoring trigger conditions. These trigger conditions are determined by a delay, and users can select a target monitoring trigger condition from among them as needed. Understandably, the parameter values ​​for the selected target monitoring trigger condition can be set.

[0107] (2) When the target monitoring triggering condition is met, the first basic node is invoked.

[0108] In this embodiment of the invention, the basic node of the trigger condition node type combines the monitoring sub-node and the first basic node in the same process node, and the first basic node in the process node is only executed when the monitoring condition sub-node is satisfied. When editing the basic node of the trigger condition type, the user only needs to select the monitoring trigger condition in the monitoring sub-node and the business capability information of the first basic node in the process node.

[0109] (3) In response to the selection instruction for multiple business scripts of the first basic node, at least one target business script is determined.

[0110] (4) In response to the position adjustment instruction of the at least one target business script, determine the execution order of the at least one target business script.

[0111] (5) Determine the target business capabilities of the target basic node based on the target monitoring trigger conditions and the execution order of the at least one target business script.

[0112] like Figure 3e The diagram shown is a conceptual diagram, structural block diagram, and interface diagram of the trigger condition logic node. This trigger condition logic node is the basic node of the trigger condition node type with target business capabilities. The target business capabilities are determined by the monitoring trigger conditions in this structural block diagram, multiple selected scripts such as script 1 and script 2, and the positional relationship of each selected script.

[0113] Based on the functions of process nodes in the flowchart, this invention configures the node types of basic nodes as the aforementioned ordinary node type, immediate condition node type, and trigger condition node type. This eliminates the need for users to focus on specific function information during the actual business logic editing process. This not only simplifies the subsequent associations between nodes but also greatly reduces the requirements for users and improves the editing efficiency and maintainability of business logic.

[0114] In practical applications, within the internal logic of a typical business logic node, it is sometimes necessary to wait for a certain amount of time or frames before executing subsequent logic. Therefore, as a possible implementation, the business capability information of the first basic node can also include a waiting execution script. This allows the selection of the waiting execution script when the internal logic of a typical business logic node needs to wait for a certain amount of time or frames before execution. In other words, the aforementioned at least one target business script can also include a waiting execution script. Correspondingly, after determining at least one target business script in response to the selection instruction for the plurality of business scripts, the method can further include: determining the waiting execution duration in response to the setting instruction for the time parameter of the waiting execution script. Figure 4a The diagrams shown depict the concept, structure, and interface of waiting within the internal logic of a regular logic node. By setting time parameters such as the number of frames for the waiting script, the waiting instructions within the business logic node can be implemented. Figure 4a In the conceptual diagram, "Logic 1" represents the logic composed of a portion of the target business scripts, and "Logic 2" represents the logic composed of another portion of the target business scripts. Therefore, in step S205, when determining the target business capabilities of the target basic node, the target business capabilities of the target basic node can also be determined based on the aforementioned waiting execution duration.

[0115] S207, in response to the association instruction between the event triggering logic node and the business logic node, determine the logic node calling relationship.

[0116] In the embodiments of the present invention, as described above Figures 3a to 3e Each of the basic nodes shown is configured with an input port and an output port. After obtaining the business logic nodes of various target business capabilities through step S205, the calling relationship between business logic nodes and between event triggering logic nodes and business logic nodes can be established by connecting the input ports and output ports of each business logic node.

[0117] As a possible implementation, to enable the execution of internal logic branches between the internal logic of ordinary logic nodes, the business capability information of the first basic node may further include a jump branch script. This allows the selection of the jump branch script when an internal logic branch is required; that is, at least one of the aforementioned target business scripts may also include a jump branch script. Correspondingly, determining the logic node calling relationship in response to the association instruction between the event-triggered logic node and the business logic node may include the following steps:

[0118] (1) In response to the association instruction of the output port of the event triggering logic node and the input port of the first business logic node, determine the first calling relationship of the event triggering logic node to the first business logic node.

[0119] In practice, users can draw a connection line between the output port of the event-triggered logic node and the input port of the first business logic node, establishing a first call relationship between the event-triggered logic node and the first business logic node. The first business logic node is a business logic node that needs to be executed after the event-triggered logic node is triggered.

[0120] (2) In response to the association instruction of the output port of the jump branch script and the input port of the second business logic node, determine the second call relationship of the jump branch script to the second business logic node.

[0121] In this embodiment of the invention, each business script in the business capability information of the basic node can also be configured with a corresponding output port. Through the output port of this business script, the calling relationship between the business script and other business logic nodes can be established. For example... Figure 4b The diagrams shown depict the concept, structure, and interface of executing internal logic branches between the internal logic of ordinary logic nodes. By connecting the output port of the jump branch script to the input port of the second business logic node, a second call relationship can be established between the jump branch script and the second business logic node. This allows the target node's capabilities to also include the capabilities of the second business logic node. Figure 4b In the conceptual diagram, "Logic 1" represents the logic composed of a portion of the target business scripts, and "Logic 2" represents the logic composed of another portion of the target business scripts. It is understood that the second business logic node can be any business logic node, and the logic node calling relationship in step S207 can include the aforementioned first and second calling relationships.

[0122] Understandably, the aforementioned Figure 4a and Figure 4b The waiting execution script and jump branch script shown are used to implement flow control over the internal logic flow of ordinary business logic nodes. To further improve the flexibility of business logic editing, the business capability information of the first basic node in this embodiment can also include a custom flow script. When the user needs to customize flow control instructions according to actual needs, the user can select the custom flow script, thereby extending any custom flow control script. For example... Figure 4c The diagram shown is a structural block diagram and interface illustration of executing custom flow scripts between the internal logic of ordinary logic nodes. Users can extend multiple flow branches according to actual needs.

[0123] As a possible implementation, when loop logic needs to be executed, it is only necessary to connect several business logic nodes in series with connecting lines, and connect the output port of the last business logic node to the input port of the first business logic node. However, to avoid infinite loops, the aforementioned business logic nodes used to form the loop logic cannot all be ordinary business logic nodes; there must be at least one immediate conditional logic node and / or a trigger conditional logic node. Taking a trigger conditional logic node as an example, such as... Figure 5 The conceptual diagram, structural block diagram, and interface diagram of the loop logic shown demonstrate how connecting an output port of a trigger condition logic node to its input port establishes a calling relationship between that output port and that input port, thus forming a calling relationship for the loop logic.

[0124] In practical applications, communication between different business logics is often involved. As a possible implementation method, this embodiment of the invention uses events to achieve communication between different business logics. Specifically, when editing different business logics, event-triggered logic nodes containing target communication events can be created for the two business logic processes that need to communicate. Connecting the output port of the event-triggered logic node of the information sender to the input port of the event-triggered logic node of the information receiver establishes communication between the two business logic processes. When the business logic of the information sender triggers the target communication event, the event-triggered logic node of the information sender sends the target communication event to the event-triggered logic node of the information receiver, thereby realizing communication between the two.

[0125] S209, Generate the target business logic based on the logical node call relationship.

[0126] In this embodiment of the invention, to improve the efficiency of business logic generation, a completed business logic can be encapsulated into a sub-business logic, which can then be invoked as a whole during the editing process of other business logics (which can be referred to as the parent business logic). Based on this, after generating the target business logic according to the logic node invocation relationship in step S209, the method may further include the following steps:

[0127] (1) In response to the encapsulation instruction for the target business logic, the target business logic is encapsulated to obtain a sub-process logic node.

[0128] (2) In response to the input / output creation request of the subprocess logic node, create the input node and the output node respectively.

[0129] To improve the flexibility of calling sub-process logic nodes, there can be multiple input nodes and multiple output nodes, and the specific number can be determined according to actual needs.

[0130] (3) In response to the association instruction that associates the input node and the output node with the sub-process logic node respectively, determine the input port and the output port of the sub-process logic node.

[0131] like Figure 6a The diagram shown illustrates the interface for defining the input and output nodes of a sub-process logic node. By creating input and output nodes and connecting them to the input and output ports of the sub-process logic node, the input and output nodes of the sub-process logic node can be defined.

[0132] Understandable, such as Figure 6b The example diagram shown illustrates the invocation of a sub-process logic node. A sub-process logic node can have multiple input nodes and output nodes. When the sub-process logic node is invoked by the parent business logic, the parent business logic can choose which input nodes and output nodes of the sub-process logic node to connect.

[0133] (4) In response to the storage instruction, store the sub-process logic node.

[0134] Based on this, the business logic generation method of this embodiment of the invention may further include the step of: invoking a target sub-process logic node in response to a sub-process logic node invocation request on the business process editing interface. Therefore, when determining the logic node invocation relationship in step S207 in response to the association instruction between the event-triggered logic node and the business logic node, the logic node invocation relationship can specifically be determined in response to the association instruction between the event-triggered logic node, the business logic node, and the target sub-process logic node. This simplifies the connection relationship between process nodes in the business logic, not only improving the editing efficiency of the business logic but also enhancing its maintainability in the later stages.

[0135] This invention uses a flowchart approach to create basic nodes for each node type. The basic underlying framework involved in this invention is as follows: Figure 7 As shown.

[0136] In this context, KFGraph corresponds to a flowchart. In a narrow sense, a flowchart is a logical flow initiated from a single start event. However, considering the management cost of flowcharts, some narrowly defined flowcharts are very simple and don't need to be made into a separate KFGraph. Therefore, the flowcharts corresponding to KFGraph are broadly defined, capable of having multiple start events and corresponding to multiple logical flows. The business process editor provides easy-to-use editor operations for these broadly defined flowcharts. In the editor, a start event can be selected to display only nodes directly or indirectly connected to that node, and grouping selected nodes in the flowchart is also supported. These ease-of-use features are part of the overall technical solution. KFGraph's main functional logic is to parse the flowchart configuration and construct a graph-like topology structure of various nodes based on the configuration.

[0137] KFGraphBlockBase is the base class for various nodes in a flowchart; KFGraphBlockEventPoint is used to implement event nodes for communication between flowcharts; KFGraphBlockExportPoint is used to implement input and output nodes in nested flowchart functions; KFGraphBlockNormal is used to implement ordinary logic nodes in a flowchart; KFGraphDecorator is used to implement condition-based logic nodes, such as immediate conditions and triggering conditions; KFGraphFrame is used to implement the specific logic in ordinary logic nodes; KFGraphScript is used to implement the scripts for the specific logic in ordinary logic nodes.

[0138] Figure 8 The diagram shows the data structure involved in an embodiment of the present invention. Based on this data structure, the main logical flow of the embodiment of the present invention includes the following:

[0139] (1) Start event node: First, the event triggering logic node will monitor the event corresponding to the node name, find the target node through the Outputs information of the node, and then execute the logic of the target node.

[0140] (2) Ordinary business logic nodes: First, the input port of the ordinary node type business logic node is called, and then the target scripts in the Frame script list are executed in sequence.

[0141] (3) Immediate conditional logic node: First, the input port of the immediate conditional child node is called, and then the conditional logic in the Decorator is executed. If the conditional logic is true, the target script in the Frame script list is executed in sequence according to (2) ordinary business logic node.

[0142] (4) Triggering condition logic node: First, monitor the Input port of the child node to be called, then activate the condition monitoring in the Decorator. If the monitoring is triggered, determine whether the condition logic is true. If it is true, execute the target script in the Frame script list in (2) ordinary business logic node in sequence.

[0143] (5) Loop: First, the Input port of the business logic node of the ordinary node type is called. Then, according to the actual situation, the steps (2), (3), or (4) are executed. Then, the target node is found through the Outputs port information of the node. The target node is the node itself. Then, the aforementioned steps of the Input port being called are executed, and the loop continues.

[0144] (6) Flowchart nesting: First, the input port of the business logic node of the ordinary node type is called. Then, if the Target specifies the module function and the module is a flowchart module, the instance of the flowchart module is found. If no instance is found, an instance is created according to the flowchart module type information. Finally, the specified node in the flowchart corresponding to the instance is executed.

[0145] (7) Communication between flowcharts: First, in flowchart instance 1, an event of the node name is emitted through the node of the event type. Then, in flowchart instance 2, the event of the node name is monitored through the node of the event type.

[0146] In this embodiment of the invention, non-programmers can quickly edit and generate the required business logic in the form of flowcharts, without requiring planners to pay attention to the fine-grained operation or logic. Moreover, the relationships in the logic flow are concise and clear, which facilitates later maintenance and processing and helps to improve the efficiency of business logic generation. It can be applied not only to the generation of game level flow logic, but also to the generation of the flow logic of the entire game.

[0147] Corresponding to the business logic generation methods provided in the above embodiments, this embodiment of the invention also provides a business logic generation device. Since the business logic generation device provided in this embodiment of the invention corresponds to the business logic generation methods provided in the above embodiments, the implementation methods of the aforementioned business logic generation methods are also applicable to the business logic generation device provided in this embodiment, and will not be described in detail in this embodiment.

[0148] Please see Figure 9 The diagram shows a structural schematic of a business logic generation device provided in an embodiment of the present invention. This device has the function of implementing the business logic generation method in the above-described method embodiments. This function can be implemented by hardware or by hardware executing corresponding software. Figure 9 As shown, the device may include:

[0149] The first creation module 910 is used to create an event triggering logic node in response to a first creation request on the business process editing interface; the event triggering logic node includes a business event identifier;

[0150] The second creation module 920 is used to respond to the second creation request on the business process editing interface and obtain a target basic node that matches the target node type from the basic node library; the target basic node includes a node capability editing interface, which is configured with business capability information;

[0151] The node business capability determination module 930 is used to determine the target business capability of the target basic node in response to the selection instruction for the business capability information, and obtain the business logic node.

[0152] The call relationship determination module 940 is used to determine the call relationship of logical nodes in response to the association instruction between the event triggering logical node and the business logic node;

[0153] The business logic generation module 950 is used to generate target business logic based on the logic node call relationship.

[0154] As an optional implementation, if the target node type is a first node type and the target base node is a first base node, the business capability information of the first base node includes multiple business scripts;

[0155] Accordingly, the node service capability determination module 930 includes:

[0156] The first determining module is configured to determine at least one target business script in response to the selection instruction for the plurality of business scripts;

[0157] The second determining module is used to determine the execution order of the at least one target business script in response to the position adjustment instruction of the at least one target business script;

[0158] The third determining module is used to determine the target business capabilities of the target basic node based on the execution order of the at least one target business script.

[0159] As an optional implementation, if the target node type is a second node type, the target base node includes an immediate condition sub-node and the first base node; the service capability information of the immediate condition sub-node includes immediate judgment conditions.

[0160] Accordingly, the node service capability determination module 930 includes:

[0161] The instant condition determination module is used to determine the target instant judgment condition in response to the selection instruction for the instant judgment condition of the instant condition sub-node.

[0162] The first establishment module is used to establish a call to the first basic node when the determination result of the immediate judgment condition of the target is true;

[0163] The fourth determining module is used to determine at least one target business script in response to a selection instruction for multiple business scripts of the first basic node.

[0164] The fifth determining module is used to determine the execution order of the at least one target business script in response to the position adjustment instruction of the at least one target business script;

[0165] The sixth determining module is used to determine the target business capabilities of the target basic node based on the target judgment conditions and the execution order of the at least one target business script.

[0166] As an optional implementation, if the target node type is a third node type, the target base node includes a monitoring sub-node and the first base node; the service capability information of the monitoring sub-node includes monitoring triggering conditions;

[0167] Accordingly, the node service capability determination module 930 includes:

[0168] The monitoring condition module is used to determine the target monitoring trigger condition in response to the selection instruction for the monitoring trigger condition of the monitoring sub-node;

[0169] The first calling module is used to call the first basic node when the target monitoring triggering condition is met;

[0170] The seventh determining module is used to determine at least one target business script in response to a selection instruction for multiple business scripts of the first basic node.

[0171] The eighth determining module is used to determine the execution order of the at least one target business script in response to the position adjustment instruction of the at least one target business script;

[0172] The ninth determining module is used to determine the target business capabilities of the target basic node based on the target monitoring triggering conditions and the execution order of the at least one target business script.

[0173] As an optional implementation, the at least one target business script includes a jump branch script; the call relationship determination module 940 includes:

[0174] The first call relationship determination module is used to determine the first call relationship between the event triggering logic node and the first business logic node in response to the association instruction of the output port of the event triggering logic node and the input port of the first business logic node;

[0175] The second call relationship determination module is used to determine the second call relationship between the jump branch script and the second business logic node in response to the association instruction of the output port of the jump branch script and the input port of the second business logic node;

[0176] The business logic nodes include the first business logic node and the second business logic node; the logic node calling relationship includes the first calling relationship and the second calling relationship.

[0177] As an optional implementation, the at least one target service script includes a script awaiting execution; the node service capability determination module 930 further includes:

[0178] The waiting time determination module is used to determine the waiting execution time in response to the setting instruction for the time parameter of the script to be executed.

[0179] Accordingly, when determining the target business capabilities of the target basic node, the node business capability determination module also determines the target business capabilities of the target basic node based on the waiting execution time.

[0180] As an optional implementation, the apparatus further includes:

[0181] An encapsulation module is used to encapsulate the target business logic in response to an encapsulation instruction for the target business logic to obtain a sub-process logic node;

[0182] The input / output node creation module is used to create input nodes and output nodes respectively in response to input / output creation requests for the sub-process logic nodes;

[0183] The tenth determining module is used to determine the input port and output port of the sub-process logic node in response to an association instruction that associates the input node and output node with the sub-process logic node respectively;

[0184] A storage module is used to store the sub-process logic nodes in response to a storage command.

[0185] As an optional implementation, the apparatus further includes:

[0186] The sub-process logic node invocation module is used to respond to sub-process logic node invocation requests on the business process editing interface and invoke the target sub-process logic node.

[0187] Accordingly, the calling relationship determination module 940 is specifically used to determine the calling relationship of logical nodes in response to the association instructions of the event triggering logical node, the business logical node and the target sub-process logical node.

[0188] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0189] This invention provides a terminal including a processor and a memory. The memory stores at least one instruction, at least one program, code set, or instruction set. The at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the business logic generation method provided in the above method embodiments.

[0190] Memory can be used to store software programs and modules. The processor executes various functional applications and generates business logic by running the software programs and modules stored in the memory. Memory can mainly include a program storage area and a data storage area. The program storage area can store the operating system, application programs required for functions, etc.; the data storage area can store data created based on the use of the device, etc. Furthermore, memory can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, memory can also include a memory controller to provide the processor with access to the memory.

[0191] The method embodiments provided in this invention can be executed on a computer terminal, server, or similar computing device. Taking running on a terminal as an example, Figure 10 This is a hardware structure block diagram of a terminal running a business logic generation method provided in an embodiment of the present invention. Specifically:

[0192] The terminal may include an RF (Radio Frequency) circuit 1010, a memory 1020 including one or more computer-readable storage media, an input unit 1030, a display unit 1040, a sensor 1050, an audio circuit 1060, a WiFi (Wireless Fidelity) module 1070, a processor 1080 including one or more processing cores, and a power supply 1090, etc. Those skilled in the art will understand that... Figure 10 The terminal structure shown does not constitute a limitation on the terminal and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0193] The RF circuit 1010 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and hands it over to one or more processors 1080 for processing; additionally, it transmits uplink data to the base station. Typically, the RF circuit 1010 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, an LNA (Low Noise Amplifier), a duplexer, etc. Furthermore, the RF circuit 1010 can also communicate wirelessly with networks and other terminals. The wireless communication can use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communication), GPRS (General Packet Radio Service), CDMA (Code Division Multiple Access), WCDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), email, SMS (Short Messaging Service), etc.

[0194] The memory 1020 can be used to store software programs and modules. The processor 1080 executes various functional applications and data processing by running the software programs and modules stored in the memory 1020. The memory 1020 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for the functions, etc.; the data storage area may store data created according to the use of the terminal, etc. In addition, the memory 1020 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 1020 may also include a memory controller to provide access to the memory 1020 for the processor 1080 and the input unit 1030.

[0195] The input unit 1030 can be used to receive input numerical or character information, and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control. Specifically, the input unit 1030 may include a touch-sensitive surface 1031 and other input devices 1032. The touch-sensitive surface 1031, also known as a touch display screen or touchpad, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch-sensitive surface 1031), and drive the corresponding connection device according to a pre-set program. Optionally, the touch-sensitive surface 1031 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to the processor 1080, and can receive and execute commands from the processor 1080. In addition, the touch-sensitive surface 1031 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. Besides the touch-sensitive surface 1031, the input unit 1030 may also include other input devices 1032. Specifically, other input devices 1032 may include, but are not limited to, one or more of the following: a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick.

[0196] The display unit 1040 can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces of the terminal. These graphical user interfaces can be composed of graphics, text, icons, videos, and any combination thereof. The display unit 1040 may include a display panel 1041, which may optionally be configured as an LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or similar display panel. Further, a touch-sensitive surface 1031 may cover the display panel 1041. When the touch-sensitive surface 1031 detects a touch operation on or near it, it transmits the information to the processor 1080 to determine the type of touch event. Subsequently, the processor 1080 provides corresponding visual output on the display panel 1041 according to the type of touch event. The touch-sensitive surface 1031 and the display panel 1041 can be two independent components to implement input and output functions. However, in some embodiments, the touch-sensitive surface 1031 and the display panel 1041 can be integrated to achieve both input and output functions.

[0197] The terminal may also include at least one sensor 1050, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 1041 according to the ambient light level, and the proximity sensor can turn off the display panel 1041 and / or backlight when the terminal is moved to the ear. As a type of motion sensor, a gravity acceleration sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used for applications that identify the terminal's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition-related functions (such as pedometer, tapping), etc. Other sensors that may be configured on the terminal, such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0198] Audio circuitry 1060, speaker 1061, and microphone 1062 provide an audio interface between the user and the terminal. Audio circuitry 1060 converts received audio data into electrical signals, which are then transmitted to speaker 1061, where they are converted into sound signals for output. Conversely, microphone 1062 converts collected sound signals into electrical signals, which are received by audio circuitry 1060, converted back into audio data, processed by processor 1080, and then transmitted via RF circuitry 1010 to, for example, another terminal, or output to memory 1020 for further processing. Audio circuitry 1060 may also include an earphone jack to facilitate communication between a peripheral headset and the terminal.

[0199] WiFi is a short-range wireless transmission technology. The terminal, through the WiFi module 1070, can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 10 WiFi module 1070 is shown, but it is understood that it is not a necessary component of the terminal and can be omitted as needed without changing the nature of the invention.

[0200] The processor 1080 is the control center of the terminal, connecting various parts of the terminal via various interfaces and lines. It executes software programs and / or modules stored in the memory 1020 and calls data stored in the memory 1020 to perform various functions and process data, thereby providing overall monitoring of the terminal. Optionally, the processor 1080 may include one or more processing cores; preferably, the processor 1080 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 1080.

[0201] The terminal also includes a power supply 1090 (such as a battery) to power various components. Preferably, the power supply can be logically connected to the processor 1080 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 1090 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0202] Although not shown, the terminal may also include a camera, Bluetooth module, etc., which will not be described in detail here. Specifically, in this embodiment, the terminal also includes a memory and one or more programs, wherein one or more programs are stored in the memory and configured to be executed by one or more processors. The aforementioned one or more programs contain instructions for executing the business logic generated by the above method embodiments.

[0203] Embodiments of the present invention also provide a computer-readable storage medium, which can be disposed in a terminal to store at least one instruction, at least one program, code set, or instruction set related to implementing a business logic generation method. The at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the business logic generation method provided in the above-described method embodiments.

[0204] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0205] It should be noted that the order of the above embodiments of the present invention is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, specific embodiments have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than that shown in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0206] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the apparatus embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0207] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0208] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for generating business logic, characterized in that, The method includes: In response to the first creation request on the business process editing interface, an event triggering logic node is created; the event triggering logic node includes a business event identifier; In response to a second creation request on the business process editing interface, a target base node matching the target node type is obtained from the base node library; the target base node includes a node capability editing interface. In response to the configuration instruction for business capability information received through the node capability editing interface, the target business capability of the target basic node is determined to obtain a business logic node; the business logic node internally encapsulates a logic block composed of at least one business script arranged in execution order; the at least one business script includes a jump branch script; In response to the association instruction between the event triggering logic node and the business logic node, the logic node calling relationship is determined; the logic node calling relationship includes a branch calling relationship, which is determined in response to the association instruction between the output port of the jump branch script and the input port of another business logic node; Based on the aforementioned logical node call relationships, the target business logic is generated; In response to the encapsulation instruction for the target business logic, the target business logic is encapsulated to obtain a sub-process logic node. The sub-process logic node has an input port and an output port. The parent business logic reuses and calls the sub-process logic node in other business processes by connecting the input port and the output port.

2. The business logic generation method according to claim 1, characterized in that, If the target node type is a first node type, the target base node is a first base node, and the business capability information of the first base node includes multiple business scripts; Accordingly, the configuration instructions for business capability information received through the node capability editing interface determine the target business capabilities of the target basic node, including: In response to a selection instruction for the plurality of business scripts received through the node capability editing interface, at least one target business script is determined; In response to a position adjustment instruction for the at least one target business script received through the node capability editing interface, the execution order of the at least one target business script is determined; The target business capabilities of the target basic node are determined based on the execution order of the at least one target business script.

3. The business logic generation method according to claim 2, characterized in that, If the target node type is the second node type, the target base node includes an immediate condition sub-node and the first base node; the business capability information of the immediate condition sub-node includes immediate judgment conditions; Accordingly, the determination of the target business capabilities of the target basic node in response to the configuration instruction for business capability information received through the node capability editing interface includes: In response to the selection instruction for the immediate judgment condition of the immediate conditional child node received through the node capability editing interface, the target immediate judgment condition is determined. When the result of the immediate judgment condition of the target is true, a call to the first basic node is established; In response to a selection instruction for multiple business scripts of the first basic node received through the node capability editing interface, at least one target business script is determined. In response to a position adjustment instruction for the at least one target business script received through the node capability editing interface, the execution order of the at least one target business script is determined; The target business capabilities of the target basic node are determined based on the target real-time judgment conditions and the execution order of the at least one target business script.

4. The business logic generation method according to claim 2, characterized in that, If the target node type is a third node type, the target base node includes a monitoring sub-node and the first base node; the service capability information of the monitoring sub-node includes monitoring trigger conditions; Accordingly, the step of determining the target service capabilities of the target basic node in response to the configuration instruction for the service capability information received through the node capability editing interface includes: In response to the selection instruction for the monitoring trigger condition of the monitoring sub-node received through the node capability editing interface, the target monitoring trigger condition is determined; When the target monitoring trigger condition is met, the first basic node is invoked; In response to a selection instruction for multiple business scripts of the first basic node received through the node capability editing interface, at least one target business script is determined. In response to a position adjustment instruction for the at least one target business script received through the node capability editing interface, the execution order of the at least one target business script is determined; The target business capabilities of the target basic node are determined based on the target monitoring trigger conditions and the execution order of the at least one target business script.

5. The business logic generation method according to any one of claims 2 to 4, characterized in that, The step of determining the logical node invocation relationship in response to the association instruction between the event-triggered logical node and the business logic node includes: In response to the association instruction between the output port of the event triggering logic node and the input port of the first business logic node, a first calling relationship between the event triggering logic node and the first business logic node is determined; In response to the association instruction of the output port of the jump branch script and the input port of the second business logic node, a second calling relationship of the jump branch script to the second business logic node is determined; The business logic nodes include the first business logic node and the second business logic node; the logic node calling relationship includes the first calling relationship and the second calling relationship.

6. The business logic generation method according to any one of claims 2 to 4, characterized in that, The at least one target business script includes a script awaiting execution; after determining at least one target business script in response to a selection instruction for the plurality of business scripts received through the node capability editing interface, the method further includes: In response to the instruction to set the time parameter of the script to be executed received through the node capability editing interface, the execution waiting time is determined; Accordingly, when determining the target business capabilities of the target basic node, the method further includes: The target business capabilities of the target basic node are determined based on the waiting execution duration.

7. The business logic generation method according to claim 1, characterized in that, After encapsulating the target business logic to obtain a sub-process logic node in response to the encapsulation instruction for the target business logic, the method further includes: In response to the input / output creation request for the sub-process logic node, an input node and an output node are created respectively; In response to an association instruction that associates the input node and the output node with the sub-process logic node respectively, the input port and the output port of the sub-process logic node are determined. In response to the storage instruction, the sub-process logic node is stored.

8. The business logic generation method according to claim 7, characterized in that, The method further includes: In response to a sub-process logic node call request on the business process editing interface, the target sub-process logic node is invoked. Accordingly, determining the logical node invocation relationship in response to the association instruction between the event triggering logical node and the business logic node includes: In response to the association instructions for the event triggering logic node, the business logic node, and the target sub-process logic node, the logic node calling relationship is determined.

9. A business logic generation device, characterized in that, The device includes: The first creation module is used to create an event triggering logic node in response to a first creation request on the business process editing interface; the event triggering logic node includes a business event identifier; The second creation module is used to respond to the second creation request on the business process editing interface and obtain a target basic node that matches the target node type from the basic node library; the target basic node includes a node capability editing interface; The node business capability determination module is used to determine the target business capability of the target basic node in response to the configuration instruction for business capability information received through the node capability editing interface, and obtain a business logic node; the business logic node internally encapsulates a logic block composed of at least one business script arranged in execution order; the at least one business script includes a jump branch script; The call relationship determination module is used to determine the call relationship of logical nodes in response to the association instruction between the event triggering logical node and the business logic node; the call relationship of logical nodes includes a branch call relationship, which is determined in response to the association instruction between the output port of the jump branch script and the input port of another business logic node; The business logic generation module is used to generate target business logic based on the logic node call relationship. An encapsulation module is used to encapsulate the target business logic in response to an encapsulation instruction to obtain a sub-process logic node. The sub-process logic node has an input port and an output port. The parent business logic reuses and calls the sub-process logic node in other business processes by connecting the input port and the output port of the sub-process logic node.

10. A terminal, characterized in that, It includes a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the business logic generation method as described in any one of claims 1 to 8.

Images