CN116931920A - Business logic object processing method and device, electronic equipment and storage medium - Google Patents
Business logic object processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN116931920A CN116931920A CN202310950133.4A CN202310950133A CN116931920A CN 116931920 A CN116931920 A CN 116931920A CN 202310950133 A CN202310950133 A CN 202310950133A CN 116931920 A CN116931920 A CN 116931920A
- Authority
- CN
- China
- Prior art keywords
- logic object
- node
- business logic
- functional
- function node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 26
- 238000000034 method Methods 0.000 claims abstract description 47
- 238000012545 processing Methods 0.000 claims abstract description 14
- 230000000007 visual effect Effects 0.000 claims abstract description 9
- 230000006870 function Effects 0.000 claims description 209
- 238000004590 computer program Methods 0.000 claims description 7
- 238000011161 development Methods 0.000 abstract description 10
- 238000010586 diagram Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 7
- 238000011423 initialization method Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 125000004122 cyclic group Chemical group 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 206010063385 Intellectualisation Diseases 0.000 description 2
- 230000006378 damage Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000001376 precipitating effect Effects 0.000 description 1
- 238000001556 precipitation Methods 0.000 description 1
- 230000002035 prolonged effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a business logic object processing method, a device, electronic equipment and a storage medium, wherein the method comprises the following steps: acquiring a call request input by a user and parameter entering information; searching a target business logic object in a business logic object library according to the identification of the target business logic object; and calling and executing the functional nodes of the target business logic object according to the parameter entering information and a preset scheduling algorithm to obtain an execution result of the target business logic object. The service logic can be arranged in a visual mode, the target service logic object can be directly searched in a pre-created service logic object library through the call request of a user and is called and executed, the created service logic object can be provided with reusability, the multiplexing of the service logic is realized, the development period is shortened, the repeated labor is avoided, and the service logic processing efficiency is improved.
Description
Technical Field
The present application relates to the field of software development, and in particular, to a method and apparatus for processing a service logic object, an electronic device, and a storage medium.
Background
The intelligent manufacturing is realized by utilizing advanced technology and system integration and through means of digitalization, networking and intellectualization, the automation, the high efficiency and the intellectualization of the production process are realized. The development of software is critical in an intelligent manufacturing environment.
In the prior art, the software development needs to cooperate with a front end and a rear end development team, the front end is responsible for user interface design and development, the rear end is responsible for data processing, business logic and system integration, the development mode needs to have professional programming skills for developers, and meanwhile, a large amount of time is also needed, and the problems of prolonged development period, resource waste, high maintenance cost and the like are caused by difficulty in precipitating templates and realizing business multiplexing.
Disclosure of Invention
The application aims to overcome the defects in the prior art and provide a business logic object processing method, a device, electronic equipment and a storage medium, which improve the efficiency of business logic object development.
In order to achieve the above purpose, the technical scheme adopted by the embodiment of the application is as follows:
in a first aspect, an embodiment of the present application provides a service logic object processing method, where the method includes:
acquiring a call request and parameter entering information input by a user, wherein the call request comprises an identification of a target business logic object to be called;
searching the target business logic object in a business logic object library according to the identification of the target business logic object, wherein the target business logic object comprises at least one functional node and a logic sequence among all functional nodes, and all the business logic objects in the business logic object library are obtained by arranging preset functional nodes in a visual mode in a graphical user interface in advance by a user;
and calling and executing the functional node of the target business logic object according to the parameter entering information and a preset scheduling algorithm to obtain an execution result of the target business logic object.
Optionally, before the step of obtaining the call request and the parameter entering information input by the user, the step of:
responding to the operation that a user selects at least one function node in a function node list of the graphical user interface, setting the parameter entering and exiting attribute of the function node and establishing the connection relation among the function nodes, determining each function node of the service logic object to be established, the parameter entering and exiting attribute of each function node and establishing the connection relation among the function nodes;
and generating the business logic object to be created based on each functional node of the business logic object to be created, the input-output parameter attribute of each functional node and the connection relation among the functional nodes.
Optionally, the generating the service logic object to be created based on each function node of the service logic object to be created, the parameter entering and exiting attribute of each function node, and the connection relationship between each function node is established includes:
generating each functional node of the service logic object to be created according to each functional node and the parameter entering and exiting attribute of each functional node;
and generating a logic sequence among the functional nodes according to the connection relation among the functional nodes to obtain the service logic object to be created.
Optionally, the method further comprises:
generating a functional node according to the historical programming information of the user;
and adding the generated function node to the function node list.
Optionally, after generating the service logic object to be created based on each function node of the service logic object to be created, the parameter entering and exiting attribute of each function node, and the connection relationship between each function node, the method further includes:
storing the obtained functional nodes in the service logic object and the position information of the functional nodes in the graphical user interface into a node set;
storing the connection relation among the functional nodes into a connection set;
and according to the node set and the connection set, canvas information of the service logic object is obtained, and the service logic object is displayed according to the canvas information.
Optionally, the calling and executing the functional node of the target service logic object according to the parameter entering information and a preset scheduling algorithm includes:
initializing the preset scheduling algorithm and the target business logic object;
and running the preset scheduling algorithm, and calling and executing the functional nodes of the target service logic object based on the parameter entering information and the logic sequence of each functional node in the target service logic object by the preset scheduling algorithm.
Optionally, the scheduling algorithm calls and executes the function node of the target service logic object based on the parameter entering information and the logic sequence of each function node in the target service logic, and the method includes:
generating a function node calling sequence based on the logic sequence of each function node in the target service logic by the scheduling algorithm;
traversing the function node calling sequence, and calling a function node which is the next function node of the current function node aiming at the called current function node based on the parameter entering information and/or the parameter exiting information of the current function node.
In a second aspect, an embodiment of the present application further provides a service logic object processing apparatus, where the apparatus includes:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a call request and parameter entering information input by a user, and the call request comprises an identification of a target business logic object to be called;
the searching module is used for searching the target business logic object in a business logic object library according to the identification of the target business logic object, wherein the target business logic object comprises at least one functional node and a logic sequence among the functional nodes, and each business logic object in the business logic object library is obtained by arranging preset functional nodes in a visual mode in a graphical user interface in advance by a user;
and the calling module is used for calling and executing the functional node of the target service logic object according to the parameter entering information and a preset scheduling algorithm to obtain an execution result of the target service logic object.
Optionally, the acquiring module is specifically configured to:
responding to the operation that a user selects at least one function node in a function node list of the graphical user interface, setting the parameter entering and exiting attribute of the function node and establishing the connection relation among the function nodes, determining each function node of the service logic object to be established, the parameter entering and exiting attribute of each function node and establishing the connection relation among the function nodes;
and generating the business logic object to be created based on each functional node of the business logic object to be created, the input-output parameter attribute of each functional node and the connection relation among the functional nodes.
Optionally, the acquiring module is specifically configured to:
generating each functional node of the service logic object to be created according to each functional node and the parameter entering and exiting attribute of each functional node;
and generating a logic sequence among the functional nodes according to the connection relation among the functional nodes to obtain the service logic object to be created.
Optionally, the acquiring module is specifically configured to:
generating a functional node according to the historical programming information of the user;
and adding the generated function node to the function node list.
Optionally, the acquiring module is specifically configured to:
storing the obtained functional nodes in the service logic object and the position information of the functional nodes in the graphical user interface into a node set;
storing the connection relation among the functional nodes into a connection set;
and according to the node set and the connection set, canvas information of the service logic object is obtained, and the service logic object is displayed according to the canvas information.
Optionally, the calling module is specifically configured to:
initializing the preset scheduling algorithm and the target business logic object;
and running the preset scheduling algorithm, and calling and executing the functional nodes of the target service logic object based on the parameter entering information and the logic sequence of each functional node in the target service logic object by the preset scheduling algorithm.
Optionally, the calling module is specifically configured to:
generating a function node calling sequence based on the logic sequence of each function node in the target service logic by the scheduling algorithm;
traversing the function node calling sequence, and calling a function node which is the next function node of the current function node aiming at the called current function node based on the parameter entering information and/or the parameter exiting information of the current function node.
In a third aspect, an embodiment of the present application further provides an electronic device, including: the system comprises a processor, a storage medium and a bus, wherein the storage medium stores program instructions executable by the processor, when an application program runs, the processor and the storage medium are communicated through the bus, and the processor executes the program instructions to execute the steps of the business logic object processing method in the first aspect.
In a fourth aspect, an embodiment of the present application further provides a computer readable storage medium, where a computer program is stored, where the computer program is read and executed to perform the steps of the business logic object processing method described in the first aspect.
The beneficial effects of the application are as follows:
the application provides a business logic object processing method, a device, electronic equipment and a storage medium, wherein a call request and parameter entering information input by a user are obtained; searching a target business logic object in a business logic object library according to the identification of the target business logic object; and calling and executing the functional nodes of the target business logic object according to the parameter entering information and a preset scheduling algorithm to obtain an execution result of the target business logic object. The service logic can be arranged in a visual mode, the target service logic object can be directly searched in a pre-created service logic object library through the call request of a user and is called and executed, the created service logic object can be provided with reusability, the multiplexing of the service logic is realized, the development period is shortened, the repeated labor is avoided, and the service logic processing efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of an overall architecture according to an embodiment of the present application;
FIG. 2 is a schematic flow chart of a business logic object processing method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a call service logic object according to an embodiment of the present application;
FIG. 4 is a schematic diagram of an encapsulated business logic object according to an embodiment of the present application;
FIG. 5 is a schematic diagram illustrating an example of a functional node according to an embodiment of the present application;
FIG. 6 is a flowchart illustrating another business logic object processing method according to an embodiment of the present application;
FIG. 7 is a flowchart of another business logic object processing method according to an embodiment of the present application;
FIG. 8 is a flowchart illustrating a business logic object processing method according to another embodiment of the present application;
FIG. 9 is a schematic flow chart of a method for calling a target business logic object according to an embodiment of the present application;
FIG. 10 is a schematic timing diagram of invoking a business logic object according to an embodiment of the present application;
FIG. 11 is a schematic diagram of a device for a method for processing a service logical object according to an embodiment of the present application;
fig. 12 is a block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described with reference to the accompanying drawings in the embodiments of the present application, and it should be understood that the drawings in the present application are for the purpose of illustration and description only and are not intended to limit the scope of the present application. In addition, it should be understood that the schematic drawings are not drawn to scale. A flowchart, as used in this disclosure, illustrates operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be implemented out of order and that steps without logical context may be performed in reverse order or concurrently. Moreover, one or more other operations may be added to or removed from the flow diagrams by those skilled in the art under the direction of the present disclosure.
In addition, the described embodiments are only some, but not all, embodiments of the application. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by a person skilled in the art without making any inventive effort, are intended to be within the scope of the present application.
It should be noted that the term "comprising" will be used in embodiments of the application to indicate the presence of the features stated hereafter, but not to exclude the addition of other features.
The method in the embodiment of the application is applied to electronic equipment, which can include, but is not limited to, a desktop computer, a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a smart phone, a smart television and other terminal equipment with a display screen, or can also be a server, wherein the server can be implemented on a cloud platform, and the cloud platform can include, by way of example only, a private cloud, a public cloud, a hybrid cloud, a community cloud (community cloud), a distributed cloud, a cross-cloud (inter-cloud), a multi-cloud (multi-cloud) and the like, or any combination thereof.
The method in the embodiment of the present application may include an editing state and an operating state, specifically, as shown in fig. 1, a schematic diagram of an overall architecture provided by the embodiment of the present application, where the editing state refers to a process of creating a business logic object in the state, and the editing state may include structures of a node component, a self-defined node, canvas rendering, multi-layer canvas management, a configuration component, a schema definition, a data structure, and an automatic formatting algorithm; the running state refers to a process of calling the edited business logic object in the state, and the running state can comprise a node library, a business logic library, a scheduling framework, context management, verification service, an expression engine, a data structure compiler, a third party jar Bao Jiazai device, timing task management, thread pool management, data source management, an external request cache pool, management end service, log monitoring and other structures.
Fig. 2 is a flow chart of a business logic object processing method according to an embodiment of the present application, where an execution body of the method is the aforementioned electronic device. As shown in fig. 2, the method includes:
s101, acquiring a call request input by a user and parameter entering information.
The call request may include an identifier of a target service logic object to be called, where the identifier of the target service logic object may refer to a unique ID number of the target service logic, or may refer to a name of the target service logic object, etc. The parameter entering information can refer to a data source which needs to be calculated by the target business logic object, and can be different types of data such as files, pictures, data tables and the like.
After the application inputs the call request and the parameter entering information at the front end of the external application, the call request and the parameter entering information input by the user are sent to the service logic object library through the external calling party.
S102, searching the target business logic object in the business logic object library according to the identification of the target business logic object.
Optionally, the target service logic object may include at least one function node and a logic sequence between the function nodes. Each business logic object in the business logic object library is obtained by arranging preset functional nodes in a visual mode in a graphical user interface in advance by a user. The function node may refer to a node that executes a certain service logic, such as a loop function node, a merge function node, a continue loop function node, a decision function node, an end function node, a sleep function node, and the like.
Optionally, the service logic object library may include at least one service logic object. The business logic object consistent with the identification of the target business logic object can be searched in the business logic object library according to the identification of the target business logic object.
S103, according to the parameter entering information and a preset scheduling algorithm, calling and executing the functional node of the target business logic object to obtain an execution result of the target business logic object.
Optionally, the parameter entering information can be uploaded to corresponding functional nodes in the target service logic object, each functional node in the target service logic object is scheduled and executed through a scheduling algorithm, and the output result of the last functional node after execution is used as the execution result of the target service object. And returning and displaying the execution result at the front end of the external application.
Specifically, fig. 3 is a schematic diagram of a service logic object calling provided in an embodiment of the present application, as shown in fig. 3 below, when an external request input by a user is received, a target service logic object is found in a service logic object library, and a function node in the target service logic object is called according to a preset scheduling algorithm. When the service logic object is called, the instantiated functional nodes are packaged together with a preset scheduling algorithm to obtain the packaged service logic object, so that each functional node in the service logic object is scheduled through the preset scheduling algorithm, specifically, as shown in fig. 4, fig. 4 is a schematic diagram of the packaged service logic object provided by the embodiment of the application, and the packaged service logic object has an executing method, an initializing method and a destroying method.
The functional node in the service logic object is an implementation class in the editing stage, and when the operation stage is instantiated as a functional node object, as shown in fig. 5, fig. 5 is a schematic diagram for instantiating the functional node according to the embodiment of the present application.
In this embodiment, the call request and the parameter entering information input by the user are obtained; searching a target business logic object in a business logic object library according to the identification of the target business logic object; and calling and executing the functional nodes of the target business logic object according to the parameter entering information and a preset scheduling algorithm to obtain an execution result of the target business logic object. The service logic can be arranged in a visual mode, the target service logic object can be directly searched in a pre-created service logic object library through the call request of a user and is called and executed, the created service logic object can be provided with reusability, the multiplexing of the service logic is realized, the development period is shortened, the repeated labor is avoided, and the service logic processing efficiency is improved.
Fig. 6 is a flow chart of another business logic object processing method according to an embodiment of the present application, as shown in fig. 6, before the call request and the parameter entering information input by the user are obtained in S101, the method may include:
s201, responding to the operation that a user selects at least one function node in a function node list of a graphical user interface, setting the parameter entering and exiting attribute of the function node and establishing the connection relation among the function nodes, determining each function node of the service logic object to be established, the parameter entering and exiting attribute of each function node and establishing the connection relation among the function nodes.
Optionally, the user may select at least one function node from the list of function nodes on the graphical user interface, where the function node may be used to calculate a service logic, and the function node includes logic code information that may be used to calculate the function node, for example, for a cyclic service logic, the logic code information of the cyclic service logic may be packaged as a cyclic function node; for start service logic, the start logic code may be encapsulated as a start function node; for ending business logic, the ending logic code may be packaged as an ending function node. For a business logic, it may be composed of multiple functional nodes.
The in-out parameter attribute may refer to a type of in-out parameter, such as a file type, a picture type, a table type, and the like.
Optionally, when the user selects at least one function node, the visualized function node may be dragged to an editing interface of the graphical user interface by a dragging mode, and the parameter entering and exiting attribute of the function node and the operation of establishing a connection relationship between the function nodes are set, and the back end responds to the user to select at least one function node in a function node list of the graphical user interface, and the operation of setting the parameter entering and exiting attribute of the function node and establishing the connection relationship between the function nodes, and determines each function node of the service logic object to be created, the parameter entering and exiting attribute of each function node and establishing the connection relationship between the function nodes.
S202, generating the business logic object to be created based on each function node of the business logic object to be created, the parameter entering and exiting attribute of each function node and the connection relation among the function nodes.
Optionally, when the back end determines each function node of the service logic object to be created, the parameter entering and exiting attribute of each function node, and establishes a connection relationship between each function node, and based on each function node of the service logic object to be created, the parameter entering and exiting attribute of each function node, and the connection relationship between each function node, the service logic object to be created is generated by using a preset method.
Fig. 7 is a flowchart of another service logic object processing method according to an embodiment of the present application, as shown in fig. 7, where in S202, a service logic object to be created is generated based on each function node of the service logic object to be created, a parameter entry and exit attribute of each function node, and a connection relationship between each function node, and may include:
s301, according to each functional node and the input-output parameter attribute of each functional node, each functional node of the service logic to be created is generated respectively.
Optionally, each functional node of the service logic to be created is generated according to each functional node and the parameter entering and exiting attribute of each functional node.
S302, generating a logic sequence among the functional nodes according to the connection relation among the functional nodes to obtain a service logic object to be created.
Optionally, generating a logic sequence among the functional nodes according to the connection relation among the functional nodes to obtain the service logic object to be created.
For example, for a judging service logic object, the judging service logic object may include a start function node, a judging function node, and an end function node, where the post-connection function node of the judging function node has two function nodes, for example, a function node a and a function node B, and then the judging function node may be connected to the function node a and the function node B respectively, and then the start function node, the judging function node, the function node a, or the function node B, and the end function node may be sequentially connected to obtain the judging service logic object.
In this embodiment, the service logic object is generated according to the function node in a pull-visual manner, and the general code function point is abstracted into a function node, so that the user can multiplex the function node and the service logic object conveniently, the work of repeated coding is reduced, and the development efficiency of the service logic object is improved.
Optionally, the method may further include:
optionally, according to the historical programming information of the user, generating the function node, and adding the generated function node into the function node list.
Optionally, in order to simplify the operation of the user, some common function points of the user can be determined according to the historical programming information of the user, and the function nodes are generated according to the code information of the common function points, so that the user can conveniently realize the function which can only be realized by a large string of codes through simple configuration. For example, the user may configure the ingress parameters of the functional node.
For example, for the operations of adding, deleting and modifying a service table in a database, in the coding process, data in a certain basic object needs to be inserted into the service table according to the connection and coding codes of the database, the inserted coding information can be generated into an inserted functional node, such as a submitting node, and the data insertion operation can be completed through the submitting node.
Fig. 8 is a flow chart of another business logic object processing method according to an embodiment of the present application, as shown in fig. 8, where the generating a business logic object to be created in S202 based on each function node of the business logic object to be created, the parameter entering and exiting attribute of each function node, and the connection relationship between each function node may include:
s401, storing the obtained functional nodes in the service logic object and the position information of the functional nodes in the graphical user interface into a node set.
Optionally, after the service logic object is created on the graphical user interface, the position information of each functional node in the service logic object on the graphical user interface and the configuration information of each functional node may be saved into the node set. The location information may refer to coordinate location information of each functional node on a graphical user interface.
S402, storing the connection relation among the functional nodes into a connection set.
Optionally, the connection relationship and the connection information between the functional nodes may be stored in the connection set, where the connection information between the functional nodes may refer to length information of the connection, start position information of the connection, end position information of the connection, and direction information of the connection.
S403, according to the node set and the connection set, canvas information of the service logic object is obtained, and the service logic object is displayed according to the canvas information.
Optionally, the node set and the connection set may be stored in a canvas information data structure library, and if a user needs to display a certain service logic object, the service logic object may be displayed through the node set and the connection set of each service logic object in the canvas information data structure library.
In this embodiment, the created business logic object can be conveniently displayed through the data structure library of the stored canvas information, so as to implement the precipitation of the business logic object.
Fig. 9 is a schematic flow chart of calling a target service logic object according to an embodiment of the present application, as shown in fig. 9, the step S103 of calling and executing a function node of the target service logic object according to the parameter information and a preset scheduling algorithm may include:
s501, initializing a preset scheduling algorithm and a target business logic object.
Optionally, when the user needs to call the target service logic object, the preset scheduling algorithm and each functional node in the target logic object are packaged together, so that the target logic object can be called through the preset calling algorithm.
Optionally, each functional node in the target service logic object may be used as an implementation class before the call operation, and each functional node refers to each functional node class, and after the call of the target logic object, each functional node class is instantiated in the operation process to obtain each functional node object. Node interfaces are realized for all functional node classes, and the node interfaces can realize an initialization method, a calling method and a destroying method. The initialization method is to check the correctness of the configuration information of the functional node in the process of the functional node in the instantiation process, and some self-defined initialization operations can be carried out; the calling method is a called method after the function node is selected by a calling algorithm and is used for executing the logic operation of the function node; the destruction method can be used for a method which can be scheduled by an upper control framework when the functional node does not need to be called, and is generally used for releasing some resources and other operations.
Optionally, the target business logic object also includes an initialization method, an execution method and a destruction method. The initialization method is mainly used for initializing all functional nodes included in the business logic object and initializing a preset scheduling algorithm for packaging the target business logic object together; the execution method refers to obtaining the parameter outputting data processed by a series of functional nodes according to the parameter inputting information and a preset scheduling algorithm; the destroying method is mainly used for enabling all the functional nodes included in the target business logic object to execute the destroying method of the primary functional node and the method for destroying the preset scheduling algorithm.
S502, running a preset scheduling algorithm, and calling and executing the functional nodes of the target service logic object based on the parameter entering information and the logic sequence of each functional node in the target service logic object by the preset scheduling algorithm.
Optionally, the step S502 of calling and executing the function node of the target service logic object based on the parameter entering information and the logic sequence of each function node in the target service logic object by a preset scheduling algorithm may include:
optionally, the scheduling algorithm generates a call sequence of each function node based on the logic sequence of each function node in the target service logic.
Specifically, if each functional node in the target service logical object is: the device comprises a function node A, a function node B, a function node C, a function node D and a function node E, wherein the function node C and the function node D are respectively connected with the function node B, and the function node C and the function node D are also respectively connected with the function node E. Then it can be generated that the call sequence of function node a is 1, the call sequence of function node B is 2, the call sequence of function node C is 3, the call sequence of function node D is 3, and the call sequence of function node E is 4.
Optionally, traversing the function node calling sequence, and calling a function node next to the current function node according to the parameter entering information and/or the parameter exiting information of the current function node aiming at the called current function node.
Optionally, if the called current node is a start function node, a function node next to the start function node can be called based on the parameter entering information; if the called function node is, for example, a judging function node, determining a function node subsequent to the current function node according to parameter outputting information of the judging function node, for example, the judging function node is like the function node B in the previous example, and parameter outputting information of the function node may be yes or no; if the output parameter is yes, judging the latter functional node of the functional nodes as a functional node C; if the parameter is "no", the function node next to the function node is the function node D, and the function node next to the current function node is called according to the parameter information of the current function node which has been called.
In this embodiment, according to the operation result of the front-end function node and the connection relationship of the function nodes, the called latter function node is determined.
Fig. 10 is a schematic timing diagram of calling a business logic object according to an embodiment of the present application, where the timing diagram is shown in fig. 10:
the user inputs a call request and a parameter entry through an external calling program; sending a call request and an entry into a service logic object library, searching a target service logic object, initializing the target service logic object and a preset scheduling algorithm, scheduling each functional node in the target service logic object through the preset scheduling algorithm, and finally returning the execution result of the target service logic object to an external calling program for display.
Fig. 11 is a schematic diagram of an apparatus for processing a service logic object according to an embodiment of the present application, where, as shown in fig. 11, the apparatus includes:
the acquiring module 601 is configured to acquire a call request and parameter entering information input by a user, where the call request includes an identifier of a target service logic object to be called;
the searching module 602 is configured to search the target service logic object in a service logic object library according to the identifier of the target service logic object, where the target service logic object includes at least one functional node and a logic sequence between the functional nodes, and each service logic object in the service logic object library is obtained by arranging preset functional nodes in a graphical user interface in a visual manner in advance by a user;
and the calling module 603 is configured to call and execute the functional node of the target service logic object according to the parameter entering information and a preset scheduling algorithm, so as to obtain an execution result of the target service logic object.
Optionally, the acquiring module 601 is specifically configured to:
responding to the operation that a user selects at least one function node in a function node list of the graphical user interface, setting the parameter entering and exiting attribute of the function node and establishing the connection relation among the function nodes, determining each function node of the service logic object to be established, the parameter entering and exiting attribute of each function node and establishing the connection relation among the function nodes;
and generating the business logic object to be created based on each functional node of the business logic object to be created, the input-output parameter attribute of each functional node and the connection relation among the functional nodes.
Optionally, the acquiring module 601 is specifically configured to:
generating each functional node of the service logic object to be created according to each functional node and the parameter entering and exiting attribute of each functional node;
and generating a logic sequence among the functional nodes according to the connection relation among the functional nodes to obtain the service logic object to be created.
Optionally, the acquiring module 601 is specifically configured to:
generating a functional node according to the historical programming information of the user;
and adding the generated function node to the function node list.
Optionally, the acquiring module 601 is specifically configured to:
storing the obtained functional nodes in the service logic object and the position information of the functional nodes in the graphical user interface into a node set;
storing the connection relation among the functional nodes into a connection set;
and according to the node set and the connection set, canvas information of the service logic object is obtained, and the service logic object is displayed according to the canvas information.
Optionally, the calling module 603 is specifically configured to:
initializing the preset scheduling algorithm and the target business logic object;
and running the preset scheduling algorithm, and calling and executing the functional nodes of the target service logic object based on the parameter entering information and the logic sequence of each functional node in the target service logic object by the preset scheduling algorithm.
Optionally, the calling module 603 is specifically configured to:
generating a function node calling sequence based on the logic sequence of each function node in the target service logic by the scheduling algorithm;
traversing the function node calling sequence, and calling a function node which is the next function node of the current function node aiming at the called current function node based on the parameter entering information and/or the parameter exiting information of the current function node.
Fig. 12 is a block diagram of an electronic device 700 according to an embodiment of the present application, where the electronic device may, for example, process a business logic object as described in the foregoing embodiments. As shown in fig. 12, the electronic device may include: a processor 701 and a memory 702.
Optionally, a bus 703 may be further included, where the memory 702 is configured to store machine readable instructions executable by the processor 701 (e.g., execution instructions corresponding to the acquisition module, the search module, the calling module in the apparatus in fig. 7, etc.), where when the electronic device 700 is running, the processor 701 communicates with the memory 702 through the bus 703, and where the machine readable instructions are executed by the processor 701 to perform the method steps in the method embodiments described above.
The embodiment of the application also provides a computer readable storage medium, and a computer program is stored on the computer readable storage medium, and when the computer program is executed by a processor, the method steps in the embodiment of the business logic object processing method are executed.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system and apparatus may refer to corresponding procedures in the method embodiments, and are not repeated in the present disclosure. In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, and the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, and for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, indirect coupling or communication connection of devices or modules, electrical, mechanical, or other form.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily appreciate variations or alternatives within the scope of the present application.
Claims (10)
1. A business logic object processing method, the method comprising:
acquiring a call request and parameter entering information input by a user, wherein the call request comprises an identification of a target business logic object to be called;
searching the target business logic object in a business logic object library according to the identification of the target business logic object, wherein the target business logic object comprises at least one functional node and a logic sequence among all functional nodes, and all the business logic objects in the business logic object library are obtained by arranging preset functional nodes in a visual mode in a graphical user interface in advance by a user;
and calling and executing the functional node of the target business logic object according to the parameter entering information and a preset scheduling algorithm to obtain an execution result of the target business logic object.
2. The business logic object processing method according to claim 1, wherein before obtaining the call request and the parameter entering information input by the user, the method comprises:
responding to the operation that a user selects at least one function node in a function node list of the graphical user interface, setting the parameter entering and exiting attribute of the function node and establishing the connection relation among the function nodes, determining each function node of the service logic object to be established, the parameter entering and exiting attribute of each function node and establishing the connection relation among the function nodes;
and generating the business logic object to be created based on each functional node of the business logic object to be created, the input-output parameter attribute of each functional node and the connection relation among the functional nodes.
3. The service logic object processing method according to claim 2, wherein the generating the service logic object to be created based on each functional node of the service logic object to be created, the parameter-in-parameter attribute of each functional node, and the connection relationship between each functional node is established, includes:
generating each functional node of the service logic object to be created according to each functional node and the parameter entering and exiting attribute of each functional node;
and generating a logic sequence among the functional nodes according to the connection relation among the functional nodes to obtain the service logic object to be created.
4. The business logic object processing method according to claim 2, further comprising:
generating a functional node according to the historical programming information of the user;
and adding the generated function node to the function node list.
5. The business logic object processing method according to claim 2, wherein after generating the business logic object to be created based on each function node of the business logic object to be created, the parameter entering and exiting attribute of each function node, and the connection relationship between each function node, further comprises:
storing the obtained functional nodes in the service logic object and the position information of the functional nodes in the graphical user interface into a node set;
storing the connection relation among the functional nodes into a connection set;
and according to the node set and the connection set, canvas information of the service logic object is obtained, and the service logic object is displayed according to the canvas information.
6. The business logic object processing method according to claim 1, wherein the calling and executing the functional node of the target business logic object according to the parameter information and a preset scheduling algorithm comprises:
initializing the preset scheduling algorithm and the target business logic object;
and running the preset scheduling algorithm, and calling and executing the functional nodes of the target service logic object based on the parameter entering information and the logic sequence of each functional node in the target service logic object by the preset scheduling algorithm.
7. The business logic object processing method according to claim 6, wherein the calling and executing the function node of the target business logic object by the scheduling algorithm based on the parameter entering information and the logic sequence of each function node in the target business logic comprises:
generating a function node calling sequence based on the logic sequence of each function node in the target service logic by the scheduling algorithm;
traversing the function node calling sequence, and calling a function node which is the next function node of the current function node aiming at the called current function node based on the parameter entering information and/or the parameter exiting information of the current function node.
8. A business logic object processing apparatus, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a call request and parameter entering information input by a user, and the call request comprises an identification of a target business logic object to be called;
the searching module is used for searching the target business logic object in a business logic object library according to the identification of the target business logic object, wherein the target business logic object comprises at least one functional node and a logic sequence among the functional nodes, and each business logic object in the business logic object library is obtained by arranging preset functional nodes in a visual mode in a graphical user interface in advance by a user;
and the calling module is used for calling and executing the functional node of the target service logic object according to the parameter entering information and a preset scheduling algorithm to obtain an execution result of the target service logic object.
9. An electronic device comprising a memory and a processor, the memory storing a computer program executable by the processor, the processor implementing the steps of the business logic object processing method of any of the preceding claims 1-7 when the computer program is executed.
10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, performs the steps of the business logic object processing method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310950133.4A CN116931920A (en) | 2023-07-28 | 2023-07-28 | Business logic object processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310950133.4A CN116931920A (en) | 2023-07-28 | 2023-07-28 | Business logic object processing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116931920A true CN116931920A (en) | 2023-10-24 |
Family
ID=88385994
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310950133.4A Pending CN116931920A (en) | 2023-07-28 | 2023-07-28 | Business logic object processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116931920A (en) |
-
2023
- 2023-07-28 CN CN202310950133.4A patent/CN116931920A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109684057B (en) | Task processing method and device and storage medium | |
| CN112433702B (en) | Lightweight process design system and method | |
| CN112130993A (en) | Power edge Internet of things agent edge calculation method and system based on graphical modeling | |
| CN110750315B (en) | Class loading method, device, equipment and storage medium in Android system | |
| CN115237295A (en) | Method, electronic equipment and medium for generating flow chart through visual dragging | |
| CN117873597A (en) | Method and system for realizing API arrangement through visual configuration mode | |
| CN117389647A (en) | Plug-in generation method, application development method, device, equipment and medium | |
| CN113094125A (en) | Business process processing method, device, server and storage medium | |
| CN112558968A (en) | Resource tree view generation method, device, equipment and storage medium | |
| CN110765610B (en) | PDM integration method, PDM integration device, computer equipment and storage medium | |
| CN114816170A (en) | Rule scheme generation method, device, medium and electronic equipment | |
| CN102486731B (en) | Strengthen the visualization method of the call stack of software of software, equipment and system | |
| CN116931920A (en) | Business logic object processing method and device, electronic equipment and storage medium | |
| CN114449063B (en) | Message processing method, device and equipment | |
| CN114895893A (en) | Multi-source data processing method, device, equipment and storage medium | |
| CN114490694A (en) | Business rule processing method and device, server and storage medium | |
| CN114493185A (en) | Approval processing method, device, system, electronic equipment, storage medium and product | |
| CN112527443A (en) | Prompt box display method and device, electronic equipment and computer readable storage medium | |
| CN112598323B (en) | Cross-business-domain process monitoring method and device, computer equipment and storage medium | |
| CN112748980B (en) | Message pushing method, device, equipment and computer readable storage medium | |
| CN113706209B (en) | Operation data processing method and related device | |
| CN117311668A (en) | Method, device, equipment and storage medium for generating technical requirements of intelligent instrument | |
| CN113687882B (en) | Activiti-based flow rollback method, activiti-based flow rollback device and storage medium | |
| US20240095633A1 (en) | Method for determining a project flow, electronic device, and storage medium | |
| CN114356574A (en) | Information technology operation and maintenance management platform, method and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: Floors 1-3, Building 10, Xuelang Town, No. 99 Qingshu Road, Wuxi Economic Development Zone, Wuxi City, Jiangsu Province, 214000 Applicant after: WUXI XUELANG SHUZHI TECHNOLOGY Co.,Ltd. Address before: 214000 floor 6, Changxing international finance building, No. 1, financial first street, economic development zone, Wuxi City, Jiangsu Province Applicant before: WUXI XUELANG SHUZHI TECHNOLOGY Co.,Ltd. |
|
| CB02 | Change of applicant information |