CN112148353B - Data processing method and device - Google Patents
Data processing method and device Download PDFInfo
- Publication number
- CN112148353B CN112148353B CN202011003728.1A CN202011003728A CN112148353B CN 112148353 B CN112148353 B CN 112148353B CN 202011003728 A CN202011003728 A CN 202011003728A CN 112148353 B CN112148353 B CN 112148353B
- Authority
- CN
- China
- Prior art keywords
- node
- flow
- configuration file
- logic
- processed
- 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.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 28
- 238000000034 method Methods 0.000 claims abstract description 67
- 238000012986 modification Methods 0.000 claims abstract description 51
- 230000004048 modification Effects 0.000 claims abstract description 51
- 230000008569 process Effects 0.000 claims abstract description 48
- 238000012545 processing Methods 0.000 claims description 16
- 238000004891 communication Methods 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 5
- 230000009191 jumping Effects 0.000 claims description 3
- 238000005538 encapsulation Methods 0.000 abstract description 4
- 238000012423 maintenance Methods 0.000 abstract description 3
- 238000012800 visualization Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 238000003780 insertion Methods 0.000 description 4
- 230000037431 insertion Effects 0.000 description 4
- 230000002452 interceptive effect Effects 0.000 description 4
- 238000012546 transfer Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 235000008694 Humulus lupulus Nutrition 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a data processing method and a device, comprising the following steps: determining at least two process nodes included in a process to be processed; determining a logic relationship between the process nodes; generating a node configuration file corresponding to each flow node; and correlating the node configuration files according to the logic relationship to obtain a flow configuration file corresponding to the flow to be processed. By adopting the method in the embodiment, the process level encapsulation multiplexing can be realized by respectively obtaining the node configuration files corresponding to the process nodes and then correlating the node configuration files to obtain the process configuration files corresponding to the complete process, so that the modularized configuration of the whole process can be realized, the maintenance and modification of the configuration files of the whole process are facilitated, and the configuration efficiency is improved.
Description
Technical Field
The present application relates to the field of flow engine technologies, and in particular, to a data processing method and apparatus.
Background
The responsibility chain mode is a behavior mode commonly used in programming and is a representation of programming thought. The key point is that in the chain type processing, task nodes are reasonably divided, and the task nodes are serially combined in a chain mode in a certain way. The purpose of simplifying the complex problem is achieved by only one event per node. Meanwhile, as the nodes are associated through an external engine, the codes which are not directly called are not coupled. When the function of a certain node on the chain needs to be adjusted, only a single node needs to be replaced, and the whole set of logic does not need to be repeatedly written.
However, most of the responsibility chain modes in the prior art are made for adapting to specific application scenes, only the appointed functions can be realized, and the responsibility chain modes cannot be used in any logic implementation, only simple node encapsulation and chain type calling can be realized, node circulation judgment and circulation branching are not supported, and the multiplexing of the flow cannot be realized.
Aiming at a plurality of technical problems existing in the related art, no effective solution is provided at present.
Disclosure of Invention
In order to solve the above technical problems or at least partially solve the above technical problems, the present application provides a data processing method and apparatus.
In a first aspect, an embodiment of the present application provides a data processing method, including:
Determining at least two process nodes included in a process to be processed;
Determining a logic relationship between the process nodes;
generating a node configuration file corresponding to each flow node;
And correlating the node configuration files according to the logic relationship to obtain a flow configuration file corresponding to the flow to be processed.
Optionally, the generating a node configuration file corresponding to each flow node according to the foregoing data processing method includes:
Determining service logic corresponding to the flow node;
Determining the node type corresponding to the flow node according to the service logic;
determining calling sequence information corresponding to the flow node according to the logic relation;
and generating a node configuration file corresponding to the flow node according to the node type, the service logic and the calling sequence information.
Optionally, the data processing method as described above further includes:
Determining a target flow node for executing modification operation on the flow to be processed;
Determining a target node configuration file corresponding to the target flow node;
According to the modification operation, determining a modification strategy corresponding to the flow configuration file, and obtaining a modified flow configuration file;
And inserting the target node configuration file into the modified flow configuration file to obtain a target flow configuration file.
Optionally, in the foregoing data processing method, the determining, according to the modifying operation, a modifying policy corresponding to the flow configuration file, and obtaining a modified flow configuration file includes:
Determining a to-be-processed flow node on which the modification operation is executed and the target modification strategy corresponding to the to-be-processed flow node in the to-be-processed flow; the modification policy includes the target modification policy;
Positioning in the flow configuration file to obtain a node configuration file to be modified corresponding to the flow node to be processed;
And executing corresponding operation on the node configuration file to be modified according to the target modification strategy to obtain the modified flow configuration file.
Optionally, in the foregoing data processing method, the associating each node configuration file according to the logical relationship includes:
determining connection logic between the flow nodes according to the logic relationship;
obtaining corresponding logic nodes according to the connection logic matching, and obtaining the corresponding relation between the flow nodes and the logic nodes;
and according to the corresponding relation, the node configuration files are associated with each other through the logic nodes.
Optionally, the data processing method as described above further includes:
acquiring a call request for the flow to be processed;
Feeding back a flow engine inlet corresponding to the flow to be processed to a requester according to the call request;
receiving information to be processed corresponding to the node configuration file, which is sent by the requester through the flow engine inlet;
Processing the information to be processed through the node configuration file to obtain result information;
judging the result through a logic node corresponding to the node configuration file;
and when the result information meets the preset requirement, jumping to the next flow node.
Optionally, the data processing method, before the processing the information to be processed through the node configuration file, further includes:
Determining a preset data type corresponding to the node configuration file;
executing the next step when the data type of the information to be processed is consistent with the preset data type;
and generating reminding information when the data type of the information to be processed is inconsistent with the preset data type.
In a second aspect, an embodiment of the present application provides a data processing apparatus, including:
The first determining module is used for determining at least two flow nodes included in the flow to be processed;
a second determining module, configured to determine a logical relationship between the flow nodes;
the generation module is used for generating a node configuration file corresponding to each flow node;
And the association module is used for associating the node configuration files with each other according to the logic relationship to obtain a flow configuration file corresponding to the flow to be processed.
In a third aspect, an embodiment of the present application provides an electronic device, including: the device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
The memory is used for storing a computer program;
the processor is configured to implement a processing method according to any one of the preceding claims when executing the computer program.
In a fourth aspect, an embodiment of the present application provides a storage medium comprising a stored program, wherein the program when run performs the method steps of any one of the preceding claims.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages:
According to the method provided by the embodiment of the application, after the node configuration files corresponding to the flow nodes are respectively obtained, the flow configuration files corresponding to the complete flow are obtained through association, so that the flow level encapsulation multiplexing can be realized, the modularized configuration of the whole flow can be realized, the maintenance and modification of the configuration files of the whole flow are facilitated, and the configuration efficiency is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the invention or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, and it will be obvious to a person skilled in the art that other drawings can be obtained from these drawings without inventive effort.
FIG. 1 is a schematic flow chart of a data processing method according to an embodiment of the present application;
FIG. 2 is a flow chart of a data processing method according to another embodiment of the present application;
FIG. 3 is a flowchart illustrating a data processing method according to another embodiment of the present application;
FIG. 4 is a block diagram of a data processing apparatus according to an embodiment of the present application;
Fig. 5 is a schematic structural 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 below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Fig. 1 is a diagram of a data processing method according to an embodiment of the present application, including steps S1 to S4 as follows:
And S1, determining at least two flow nodes included in the flow to be processed.
Specifically, the process to be processed may be a process for realizing a certain business objective, which needs to generate a corresponding responsibility chain process.
For example: the to-be-processed process is that a bank needs to realize the transfer of money in a debit card row, and each process node can be obtained by splitting the framework as follows:
The method comprises the steps that 1, whether a payer account and a user name are accurate or not is checked;
A flow node 2, checking whether the balance of the account of the payer is sufficient;
A flow node 3, checking whether the account and the family name of the payee are accurate;
Process node 4. Subtracting the payment amount from the payer account balance;
flow node 5. Increase the payee account balance by the payee amount.
And S2, determining a logic relationship between the flow nodes.
Specifically, the logical relationship may be a relationship in which the transaction flow jumps between the flow nodes; taking the example that the bank in the previous embodiment is to realize the in-line transfer of a debit card; the split flow nodes comprise 5 flow nodes in total; because the other flow nodes except the node '1' need to jump to the node after the previous node meets the set requirement, and all the flow nodes are connected in a single chain; therefore, the logic relationship among the flow nodes is the relationship of single-chain connection.
Further, the logical relationship may record an ID corresponding to each flow node, so as to invoke different flow nodes according to the ID.
Since the decision logic on which the hops are based may vary from flow node to flow node, the following alternatives are optional: some may be implemented by "if" logic and some may be implemented by "for" logic. Therefore, the logic relationship can also record the judgment logic corresponding to each two flow nodes with connection relationship.
By way of example:
the flow node 1 is an If judging node, checks whether the account and the user name of the payer are accurate, returns a failure code after the check failure, ends the flow, and the check success flows to the next node.
And the flow node 2 is an If judging node, checks whether the balance of the account of the payer is larger than the payment amount, returns a failure code If the balance is smaller than the payment amount, ends the flow, and flows to the next node If the balance is larger than the payment amount.
And the flow node 3 is an If judging node, checks whether the account and the family name of the payee are accurate, returns a failure code after the check failure, ends the flow, and successfully flows to the next node.
The flow node 4 is an INode ordinary node, and performs an operation of subtracting the payment amount from the balance of the payer account.
The flow node 5 is an INode ordinary node, and performs an operation of adding the balance of the payee account to the amount of the money to be collected.
And S3, generating a node configuration file corresponding to each flow node.
Specifically, the node configuration file is an executable file or a part of executable files for enabling the corresponding flow node to realize a preset function.
Alternatively, each flow node may be associated with a specific Java class, and further, the node configuration file may be executable code of the corresponding Java class.
And S4, associating the node configuration files with each other according to the logic relationship to obtain a flow configuration file corresponding to the flow to be processed.
Specifically, after determining the node configuration files corresponding to the nodes in each node flow, each node configuration file may be associated according to the logical relationship.
One of the alternative implementation methods may be: the association of each node configuration file can be realized by calling the existing logic node for realizing logic association, for example, taking the process node 1 and the process node 2 in the previous steps as examples, because the process node 1 needs to determine whether to enter the process node 2 after performing if judgment, the process node 1 and the process node 2 need to be associated by the if logic node for realizing the if judgment method, so that a feature field or an interface for calling the if logic node can be written in the process node 1 according to a logic relationship, specifically, a feature field or an interface corresponding to the if logic node can be written in the node configuration file, so that when the process configuration file is executed, the if logic node can be called by itself or other calling modules, and the purpose of associating with the process node 2 according to the if judgment logic is achieved.
In summary, by adopting the method in this embodiment, after node configuration files corresponding to each flow node are obtained respectively, the flow configuration files corresponding to the complete flow are obtained by associating, so that the flow level encapsulation multiplexing can be implemented, and further, the modularized configuration of the whole flow can be implemented, the maintenance and modification of the configuration files of the whole flow are facilitated, and the configuration efficiency is improved.
As shown in fig. 2, in some embodiments, as the aforementioned data processing method, step S3 generates a node configuration file corresponding to each flow node, including steps S31 to S34 as follows:
s31, determining service logic corresponding to the flow node;
S32, determining the node type corresponding to the flow node according to the service logic;
S33, determining calling sequence information corresponding to the flow nodes according to the logic relation;
and S34, generating a node configuration file corresponding to the flow node according to the node type, the service logic and the calling sequence information.
Specifically, the service logic needs to include rules that should be possessed by a flow node to jump to another flow node. In addition, since the flow configuration file obtained in the present application is used to provide services to other entity units, the business logic can also be used to define the type of data and the data format and so on that each flow node needs to receive.
Since the service logic includes rules and flows, the node type may be a rule type corresponding to a flow node, that is, taking the example illustrated in the foregoing embodiment as an example: the node type may be if type, for type, etc. to characterize what the logic of the flow node needs to make a judgment, and in addition, the logic node that the flow node needs to call when making a logic judgment may be determined according to the type.
The determining the calling sequence information corresponding to the flow node according to the logic relation may be: determining a sequential relationship between the flow nodes, for example: when node A, B, C, D is present; and the calling sequence information corresponding to each flow node is respectively: 4. 1,2 and 3, and when the flow to be processed is executed, the calling sequence of the flow nodes is carried out according to the sequence of B, C, D and A.
Therefore, after the node type, the service logic and the calling sequence information are obtained, the node configuration file corresponding to each flow node is generated according to the node type, the service or the function which can be provided by each flow node can be determined, and when the final flow configuration file is generated, the calling sequence and the judging logic among the node configuration files can be determined.
In some embodiments, the data processing method as described above further includes steps S5 to S8 as follows:
S5, determining a target flow node for executing modification operation on the flow to be processed.
Specifically, the modification operation may be to replace an existing flow node with a target flow node, or insert the target flow node into a flow to be processed.
Optionally, a visual flow corresponding to the flow to be processed can be obtained at the interactive interface; the visualization process comprises first visualization nodes corresponding to the process nodes, and the first visualization nodes can be connected according to a logic relationship; in addition, a request for establishing the correspondence of the target flow node can be received through the interactive interface, and a second visualization node corresponding to the target flow node is obtained according to the request.
And, the modification operation may be obtained by inserting the second visualization node into the visualization flow, or replacing the first visualization node with the second visualization node.
S6, determining a target node configuration file corresponding to the target flow node.
Specifically, one of the alternative implementation manners may be: by inputting various configuration information (which may include node type, business logic and calling sequence information) corresponding to the target flow node in an input box in a preset interactive interface. Optionally, the call sequence information corresponding to the target flow node may be obtained according to an execution result of the modification operation, that is: and obtaining the calling sequence information according to the position of the target flow node in the flow to be processed obtained by the modification operation.
Then, the target node configuration file can be obtained by combining various configuration information and the like.
S7, according to the modification operation, determining a modification strategy corresponding to the flow configuration file, and obtaining the modified flow configuration file.
Specifically, the modification operation may include replacing an existing process node with a target process node in the process to be processed, or inserting the target process node into the process to be processed; the modification strategies corresponding to different modification operations are different, for example, when the modification operation is a replacement operation, only the replaced node configuration file in the flow configuration file needs to be replaced, and when the modification operation is an insertion operation, the node configuration file after the insertion position needs to be modified (for example, the calling sequence information is modified).
S8, inserting the target node configuration file into the modified flow configuration file to obtain a target flow configuration file.
Specifically, after determining the insertion position of the target node configuration file in the flow configuration file, the target node configuration file is inserted into the insertion position to obtain the target flow configuration file.
Optionally, when the modifying operation is a replacing operation; the optional implementation manner of steps S7 and S8 may be:
determining a flow node to be changed, which needs to be changed, according to the modification operation;
Acquiring calling sequence information in a node configuration file to be changed corresponding to a flow node to be changed;
generating a first target node configuration file corresponding to the target flow node according to the calling sequence information in the node configuration file to be changed and the business logic of the target flow node;
deleting the node configuration file to be changed from the flow configuration file to obtain a modified flow configuration file;
and replacing the first target node configuration file to obtain a first updated flow configuration file.
Optionally, when the modifying operation is an insert operation; the optional implementation manner of steps S7 and S8 may be:
acquiring a target flow node for adding the flow to be processed;
obtaining target calling sequence information of the target flow node added to the flow to be processed according to the modification operation;
According to the call sequence information of the target flow node added to the flow to be processed, determining updated call sequence information of the existing flow node in the flow to be processed;
Obtaining an updated flow configuration file according to the updated calling sequence information;
And obtaining a second updated flow configuration file according to the target node configuration file and the updated node configuration file.
As shown in fig. 3, in some embodiments, as in the foregoing data processing method, step S7 determines a modification policy corresponding to the flow configuration file according to the modification operation, and obtains a modified flow configuration file, including steps S71 to S73 as follows:
And S71, determining a to-be-processed flow node for executing the modification operation and a target modification strategy corresponding to the to-be-processed flow node in the to-be-processed flow.
Specifically, the target modification policy is a modification policy corresponding to the flow node to be processed; in the process to be processed, there may be multiple process nodes to be processed, and since the modification mode corresponding to each process node to be processed is not necessarily the same, the modification policy may include multiple target modification policies. Further, the node of the flow to be processed may be a node in the flow to be processed, or may be a node that needs to be newly added in the flow to be processed.
In an optional implementation manner of this step, the target modification policy may be operation information of the user to-be-processed flow node, which is obtained through identification of a man-machine interaction interface, specifically:
firstly, obtaining a visual flow corresponding to the flow to be processed through an interactive interface; the visualization process includes a first visualization node corresponding to each of the process nodes.
And then obtaining a second visualization node corresponding to the target flow node.
And finally, receiving a target visualization flow obtained by modifying the visualization flow after the second visualization node is operated. The second visualization node is a visualization node corresponding to the flow node to be processed.
And S72, positioning in the flow configuration file to obtain a node configuration file to be modified corresponding to the flow node to be processed.
Specifically, the node configuration file to be modified is obtained by positioning the nodes according to the flow to be processed; for example, each node configuration file may be provided with corresponding calling sequence information, and when the to-be-processed flow node is a replaced flow node or another node needs to be inserted before the to-be-processed flow node, the to-be-modified node configuration file may be directly located in the flow configuration file according to the calling sequence information of the to-be-processed flow node.
And S73, executing corresponding operation on the node configuration file to be modified according to the target modification strategy to obtain a modified flow configuration file.
Specifically, since the target modification policy may be:
1. Replacing the flow nodes to be processed with other flow nodes;
2. when another node is needed to be inserted before the flow node to be processed.
Corresponding to the target modification strategy 1, after the node configuration file to be modified is obtained, the node configuration file to be modified can be deleted, and the modified flow configuration file is obtained.
And the corresponding target modification strategy 2 can modify the calling sequence information corresponding to the node configuration file to be modified after the node configuration file to be modified is obtained, so that the condition that the calling sequence is repeated after other nodes are inserted is avoided, and further the modified flow configuration file is obtained.
Furthermore, by the method in the embodiment, the configuration file of the node to be modified, which needs to be modified, can be automatically positioned, and the modification efficiency can be effectively improved.
In some embodiments, as in the foregoing data processing method, the step S4 correlates the node configuration files according to a logical relationship, including steps S41 to S43 as follows:
s41, determining connection logic among all flow nodes according to the logic relationship;
s42, obtaining corresponding logic nodes according to the connection logic matching, and obtaining the corresponding relation between the flow nodes and the logic nodes;
And S43, associating the node configuration files with each other through the logic nodes according to the corresponding relation.
Specifically, the connection logic may be a decision logic that needs to be satisfied for a jump between every two flow nodes.
The logic node may be a node for implementing a certain connection logic, so as to obtain a corresponding relationship between the flow node and the logic node, so that the related judgment action can be completed by calling the logic node when the jump is performed between different flow nodes in the later stage.
The node configuration files are related through the logic nodes, and the node configuration files can be written into calling interfaces of the logic nodes.
For example, when the node configuration file a and the node configuration file B need to be associated through the logical node I, the interface calling mode of the logical node I may be written into the node configuration file a and the node configuration file B.
In some embodiments, the data processing method as described above further includes the following steps P1 to P5:
step P1, acquiring a call request of a flow to be processed;
Step P2, feeding back a flow engine inlet corresponding to the flow to be processed to a requester according to the call request;
Step P3, receiving information to be processed corresponding to the node configuration file, which is sent by a requester through a flow engine inlet;
step P4, processing the information to be processed through the node configuration file to obtain result information;
step P5., judging the result through a logic node corresponding to the node configuration file;
and step P6, when the result information meets the preset requirement, jumping to the next flow node.
Specifically, taking in-line transfer in the foregoing embodiment as an example: the call request may be that the user achieves the acquisition by triggering an operation control corresponding to "transfer".
After receiving the call request, feeding back a flow engine inlet corresponding to the flow to be processed to the requester, so that the requester can input the information to be processed to the flow to be processed through the flow engine inlet.
The processing of the information to be processed by the node configuration file can be the operation of inquiring or writing the information to be processed into a database according to the information to be processed, and the result information can be a corresponding inquiring result or writing result and the like.
Because the node configuration files are provided with the corresponding logic nodes, the result information can be sent to the logic nodes through the corresponding calling interfaces, so that whether to jump to the next flow node can be judged through the logic nodes according to the result information and preset requirements.
In some embodiments, the data processing method, before processing the information to be processed by the node configuration file, further includes steps Y1 to Y3 as follows:
Step Y1., determining a preset data type corresponding to the node configuration file;
step Y2., executing the next step when the data type of the information to be processed is consistent with the preset data type;
step Y3. generates reminding information when the data type of the information to be processed is inconsistent with the preset data type.
Specifically, the data types that can be processed by the node configuration file can be defined through the data types; when the data type of the information to be processed is consistent with the preset data type (for example, the information to be processed can comprise character type, character number, data format and the like), operations such as checking or writing can be performed on the information to be processed; when the data type of the information to be processed is inconsistent with the preset data type, generating reminding information so as to enable a user inputting the information to be processed to input data conforming to the preset data type again.
By the method in the embodiment, the information to be processed can be checked, so that useless information processing is avoided, and processing efficiency is improved.
As shown in fig. 4, according to an embodiment of another aspect of the present application, there is also provided a data processing apparatus including:
A first determining module 1, configured to determine at least two process nodes included in a to-be-processed process;
A second determining module 2, configured to determine a logical relationship between the flow nodes;
a generating module 3, configured to generate a node configuration file corresponding to each flow node;
and the association module 4 is used for associating the node configuration files with each other according to the logic relationship to obtain a flow configuration file corresponding to the flow to be processed.
In particular, the specific process of implementing the functions of each module in the apparatus of the embodiment of the present invention may be referred to the related description in the method embodiment, which is not repeated herein.
According to another embodiment of the present application, there is also provided an electronic apparatus including: as shown in fig. 5, the electronic device may include: the device comprises a processor 1501, a communication interface 1502, a memory 1503 and a communication bus 1504, wherein the processor 1501, the communication interface 1502 and the memory 1503 are in communication with each other through the communication bus 1504.
A memory 1503 for storing a computer program;
the processor 1501 is configured to execute the program stored in the memory 1503, thereby implementing the steps of the method embodiment described above.
The bus mentioned above for the electronic device may be a peripheral component interconnect standard (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.
The communication interface is used for communication between the electronic device and other devices.
The Memory may include random access Memory (Random Access Memory, RAM) or may include Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but may also be a Digital signal processor (Digital SignalProcessing, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components.
The embodiment of the application also provides a storage medium, which comprises a stored program, wherein the program executes the method steps of the method embodiment.
It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing is only a specific embodiment of the invention to enable those skilled in the art to understand or practice the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (9)
1. A method of data processing, comprising:
Determining at least two process nodes included in a process to be processed;
Determining a logic relationship between the process nodes;
generating a node configuration file corresponding to each flow node;
correlating each node configuration file according to the logical relationship, including: determining connection logic between the flow nodes according to the logic relationship; obtaining corresponding logic nodes according to the connection logic matching, and obtaining the corresponding relation between the flow nodes and the logic nodes; according to the correspondence, each node configuration file is associated with each other through the logic node to obtain a flow configuration file corresponding to the flow to be processed, wherein the associating each node configuration file with each other through the logic node includes: and writing calling interfaces of the logic nodes in the node configuration files to correlate the node configuration files.
2. The data processing method according to claim 1, wherein generating a node configuration file corresponding to each of the flow nodes comprises:
Determining service logic corresponding to the flow node;
Determining the node type corresponding to the flow node according to the service logic;
determining calling sequence information corresponding to the flow node according to the logic relation;
and generating a node configuration file corresponding to the flow node according to the node type, the service logic and the calling sequence information.
3. The data processing method according to claim 1, characterized by further comprising:
Determining a target flow node for executing modification operation on the flow to be processed;
Determining a target node configuration file corresponding to the target flow node;
According to the modification operation, determining a modification strategy corresponding to the flow configuration file, and obtaining a modified flow configuration file;
And inserting the target node configuration file into the modified flow configuration file to obtain a target flow configuration file.
4. A data processing method according to claim 3, wherein said determining a modification policy corresponding to the flow configuration file according to the modification operation, and obtaining a modified flow configuration file, includes:
determining a to-be-processed flow node on which the modification operation is executed and a target modification strategy corresponding to the to-be-processed flow node in the to-be-processed flow; the modification policy includes the target modification policy;
Positioning in the flow configuration file to obtain a node configuration file to be modified corresponding to the flow node to be processed;
And executing corresponding operation on the node configuration file to be modified according to the target modification strategy to obtain the modified flow configuration file.
5. The data processing method according to claim 1, characterized by further comprising:
acquiring a call request for the flow to be processed;
Feeding back a flow engine inlet corresponding to the flow to be processed to a requester according to the call request;
receiving information to be processed corresponding to the node configuration file, which is sent by the requester through the flow engine inlet;
Processing the information to be processed through the node configuration file to obtain result information;
judging the result through a logic node corresponding to the node configuration file;
and when the result information meets the preset requirement, jumping to the next flow node.
6. The data processing method according to claim 5, further comprising, before said processing of said information to be processed by said node profile:
Determining a preset data type corresponding to the node configuration file;
executing the next step when the data type of the information to be processed is consistent with the preset data type;
and generating reminding information when the data type of the information to be processed is inconsistent with the preset data type.
7. A data processing apparatus, comprising:
The first determining module is used for determining at least two flow nodes included in the flow to be processed;
a second determining module, configured to determine a logical relationship between the flow nodes;
the generation module is used for generating a node configuration file corresponding to each flow node;
The association module is configured to associate the node configuration files with each other according to the logical relationship, and includes: determining connection logic between the flow nodes according to the logic relationship; obtaining corresponding logic nodes according to the connection logic matching, and obtaining the corresponding relation between the flow nodes and the logic nodes; according to the correspondence, each node configuration file is associated with each other through the logic node to obtain a flow configuration file corresponding to the flow to be processed, wherein the associating each node configuration file with each other through the logic node includes: and writing calling interfaces of the logic nodes in the node configuration files to correlate the node configuration files.
8. An electronic device, comprising: the device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
The memory is used for storing a computer program;
The processor being adapted to carry out the method steps of any one of claims 1-6 when the computer program is executed.
9. A storage medium comprising a stored program, wherein the program when run performs the method steps of any of the preceding claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011003728.1A CN112148353B (en) | 2020-09-22 | 2020-09-22 | Data processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011003728.1A CN112148353B (en) | 2020-09-22 | 2020-09-22 | Data processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112148353A CN112148353A (en) | 2020-12-29 |
| CN112148353B true CN112148353B (en) | 2024-05-17 |
Family
ID=73896863
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011003728.1A Active CN112148353B (en) | 2020-09-22 | 2020-09-22 | Data processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112148353B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113467760B (en) * | 2021-07-26 | 2022-12-02 | 拉扎斯网络科技（上海）有限公司 | Method for creating order model the device storage medium and computer device |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102799962A (en) * | 2012-06-27 | 2012-11-28 | 南京合荣欣业信息技术有限公司 | Configuration type business flow system and realization method thereof |
| CN102810070A (en) * | 2012-07-16 | 2012-12-05 | 福建富士通信息软件有限公司 | High-performance professional ability packaging process engine and process control method thereof |
| CN103870260A (en) * | 2012-12-14 | 2014-06-18 | 腾讯科技（深圳）有限公司 | Method and system for service interface development |
| KR20170024998A (en) * | 2015-08-27 | 2017-03-08 | 박용규 | System for authoring and executing rule-based business application |
| CN106897806A (en) * | 2015-12-17 | 2017-06-27 | 北京奇虎科技有限公司 | Workflow creation method and system, operation system |
| CN106897809A (en) * | 2015-12-17 | 2017-06-27 | 北京奇虎科技有限公司 | Workflow creation method, workflow designer and workflow system |
| CN107577458A (en) * | 2017-08-18 | 2018-01-12 | 深圳怡化电脑股份有限公司 | A kind of finance self-help terminal traffic flow development approach and device |
| CN109636301A (en) * | 2018-10-16 | 2019-04-16 | 深圳壹账通智能科技有限公司 | Workflow configuration method, system, terminal and the readable storage medium storing program for executing of financial business |
| CN110007902A (en) * | 2019-03-12 | 2019-07-12 | 中国平安财产保险股份有限公司 | The method and device of business processing flow configuration |
| CN110297632A (en) * | 2019-06-12 | 2019-10-01 | 百度在线网络技术（北京）有限公司 | Code generating method and device |
| CN110310088A (en) * | 2019-06-14 | 2019-10-08 | 平安科技（深圳）有限公司 | Workflow configuration method and Related product |
| CN110321119A (en) * | 2018-03-30 | 2019-10-11 | 优酷网络技术（北京）有限公司 | The generation method of data processing module, server and client side |
| CN110377275A (en) * | 2019-07-18 | 2019-10-25 | 中汇信息技术（上海）有限公司 | Automatically create the method and storage medium of application program |
| CN110908644A (en) * | 2019-10-16 | 2020-03-24 | 浙江大搜车软件技术有限公司 | Configuration method and device of state node, computer equipment and storage medium |
| CN110928763A (en) * | 2019-09-29 | 2020-03-27 | 京东数字科技控股有限公司 | Test method, test device, storage medium and computer equipment |
| CN111124381A (en) * | 2019-12-13 | 2020-05-08 | 京东数字科技控股有限公司 | Flow creation method and device |
| CN111208992A (en) * | 2020-01-10 | 2020-05-29 | 深圳壹账通智能科技有限公司 | System scheduling workflow generation method and system |
| CN111369081A (en) * | 2018-12-06 | 2020-07-03 | 北京嘀嘀无限科技发展有限公司 | Flow configuration method and device, electronic equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3702916A1 (en) * | 2019-03-01 | 2020-09-02 | ABB Schweiz AG | Online reconfiguration of a node in a process control system |
-
2020
- 2020-09-22 CN CN202011003728.1A patent/CN112148353B/en active Active
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102799962A (en) * | 2012-06-27 | 2012-11-28 | 南京合荣欣业信息技术有限公司 | Configuration type business flow system and realization method thereof |
| CN102810070A (en) * | 2012-07-16 | 2012-12-05 | 福建富士通信息软件有限公司 | High-performance professional ability packaging process engine and process control method thereof |
| CN103870260A (en) * | 2012-12-14 | 2014-06-18 | 腾讯科技（深圳）有限公司 | Method and system for service interface development |
| KR20170024998A (en) * | 2015-08-27 | 2017-03-08 | 박용규 | System for authoring and executing rule-based business application |
| CN106897806A (en) * | 2015-12-17 | 2017-06-27 | 北京奇虎科技有限公司 | Workflow creation method and system, operation system |
| CN106897809A (en) * | 2015-12-17 | 2017-06-27 | 北京奇虎科技有限公司 | Workflow creation method, workflow designer and workflow system |
| CN107577458A (en) * | 2017-08-18 | 2018-01-12 | 深圳怡化电脑股份有限公司 | A kind of finance self-help terminal traffic flow development approach and device |
| CN110321119A (en) * | 2018-03-30 | 2019-10-11 | 优酷网络技术（北京）有限公司 | The generation method of data processing module, server and client side |
| CN109636301A (en) * | 2018-10-16 | 2019-04-16 | 深圳壹账通智能科技有限公司 | Workflow configuration method, system, terminal and the readable storage medium storing program for executing of financial business |
| CN111369081A (en) * | 2018-12-06 | 2020-07-03 | 北京嘀嘀无限科技发展有限公司 | Flow configuration method and device, electronic equipment and storage medium |
| CN110007902A (en) * | 2019-03-12 | 2019-07-12 | 中国平安财产保险股份有限公司 | The method and device of business processing flow configuration |
| CN110297632A (en) * | 2019-06-12 | 2019-10-01 | 百度在线网络技术（北京）有限公司 | Code generating method and device |
| CN110310088A (en) * | 2019-06-14 | 2019-10-08 | 平安科技（深圳）有限公司 | Workflow configuration method and Related product |
| CN110377275A (en) * | 2019-07-18 | 2019-10-25 | 中汇信息技术（上海）有限公司 | Automatically create the method and storage medium of application program |
| CN110928763A (en) * | 2019-09-29 | 2020-03-27 | 京东数字科技控股有限公司 | Test method, test device, storage medium and computer equipment |
| CN110908644A (en) * | 2019-10-16 | 2020-03-24 | 浙江大搜车软件技术有限公司 | Configuration method and device of state node, computer equipment and storage medium |
| CN111124381A (en) * | 2019-12-13 | 2020-05-08 | 京东数字科技控股有限公司 | Flow creation method and device |
| CN111208992A (en) * | 2020-01-10 | 2020-05-29 | 深圳壹账通智能科技有限公司 | System scheduling workflow generation method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112148353A (en) | 2020-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108846659B (en) | Block chain-based transfer method and device and storage medium | |
| CN107103462B (en) | Method and device for processing snapshot data of cross-border remittance of bank | |
| US11087371B2 (en) | Blockchain-based invoice creation method apparatus, and electronic device | |
| CN109993651B (en) | Data accounting service instruction set checking method, device, computer equipment and medium | |
| CN107993053A (en) | Data of settling a claim checking method, device, computer equipment and storage medium | |
| CN105321065A (en) | Multi-destination routing of transactions | |
| CN110619574A (en) | Remittance data processing method, remittance data processing apparatus, electronic device, and storage medium | |
| CN109361628A (en) | Message assemble method, device, computer equipment and storage medium | |
| CN112348326A (en) | Bank business processing method and system | |
| CN112148353B (en) | Data processing method and device | |
| CN114064112A (en) | Business process configuration method, device, equipment and storage medium | |
| CN114047928B (en) | Intelligent contract formal verification method and system suitable for combined transaction | |
| CN110009497B (en) | Block chain-based decision method and device and electronic equipment | |
| CN112015826B (en) | Intelligent contract security detection method based on block chain and related equipment | |
| WO2021129005A1 (en) | Blockchain state change-based transaction tracking method and device | |
| CN109785047A (en) | Order method for pushing, device, computer equipment and the storage medium of financial product | |
| CN111311395B (en) | Management system, method, equipment and storage medium for public accumulation fund-charging and repayment service | |
| CN107169767B (en) | Transaction processing method and system | |
| CN110336872B (en) | Method, device and system for acquiring third-party data | |
| CN109166042B (en) | Node device, real-time reconciliation method based on blockchain, and storage medium | |
| CN113255929B (en) | Method and device for acquiring interpretable reasons of abnormal user | |
| CN113822660B (en) | Data processing method, device, electronic equipment and medium | |
| CN111324645A (en) | Data processing method and device for block chain | |
| CN111429125B (en) | Account management method and device, storage medium and electronic equipment | |
| CN115018621A (en) | Contract changing method, device, equipment and 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: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176 Applicant after: Jingdong Technology Holding Co.,Ltd. Address before: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176 Applicant before: Jingdong Digital Technology Holding Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |