Low-code platform message data processing system, method and device

Abstract

This specification relates to the technical field of low-code platforms, and specifically discloses a low-code platform message data processing system, method and device, wherein the system includes a message parser and a message adapter; the message parser is used to receive initial message data, and convert the received initial message data into corresponding target format message data; the initial message data includes message data in multiple formats; the message adapter is used to receive target format message data output by the message parser, and associate the target format message data according to preset business logic, and output the associated target format result message. Through the above scheme, it is possible to support multiple interfaces to be combined into one interface output, reduce the amount of code, and can be applied to complex business scenarios through configuration.

Description

Technical Field

[0001] This specification relates to the technical field of low-code platforms, and in particular to a low-code platform message data processing system, method and device. Background Art

[0002] At present, the interface interaction of low-code development platforms usually adopts the JSON message format. The low-code development platform may have message formats of protocols such as xml, txt, csv, etc., which need to be converted into JSON message format. In the prior art, there are technical solutions for format conversion, but they are limited to verification use and cannot be linked with the actual business system, which is relatively broken. Moreover, in the case of multiple interfaces, multiple JSON messages will be output. After the output, they need to be processed again for output, which has the problem of high code volume.

[0003] To address the above problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of this specification provide a low-code platform message data processing system, method and device to solve the problem in the prior art that low-code development platform message conversion cannot be linked with the actual business system.

[0005] The embodiments of this specification provide a low-code platform message data processing system, including a message parser and a message adapter;

[0006] The message parser is used to receive initial message data and convert the received initial message data into corresponding target format message data; the initial message data includes message data in multiple formats;

[0007] The message adapter is used to receive the target format message data output by the message parser, and to associate the target format message data according to a preset business logic, and output an associated target format result message.

[0008] In one embodiment, the message parser includes multiple interfaces, each of which is used to receive message data of an instruction type.

[0009] In one embodiment, the message adapter determines the correlation attribute according to a preset business logic, and performs correlation processing on the target format message data based on the correlation attribute.

[0010] In one embodiment, the message parser and the message adapter are debugged in a visual presentation form.

[0011] In one embodiment, the message parser can be configured in response to a drag and drop operation by a developer.

[0012] In one embodiment, the initial message data may include at least one of the following: an xml message, a txt message, and a csv message; and the target format message includes a JSON message.

[0013] In one embodiment, the device further comprises a message processor, which is used to receive the target format result message output by the message adapter and process the target format result message according to a preset business rule corresponding to the preset business logic.

[0014] The embodiment of this specification also provides a low-code platform message data processing method, including:

[0015] Receiving initial message data; the initial message data includes message data in multiple formats;

[0016] Convert the received initial message data into corresponding target format message data;

[0017] The target format message data is associated and processed according to the preset business logic, and the associated target format result message is output.

[0018] In one embodiment, the target format message data is associated and processed according to a preset business logic, and the associated target format result message is output, including:

[0019] Determine the associated attributes based on the preset business logic;

[0020] Based on the association attribute, the target format message data is associated and processed, and the associated target format result message is output.

[0021] In one embodiment, after outputting the associated target format result message, after outputting the associated target format result message, the method further includes:

[0022] Obtaining preset business rules corresponding to the preset business logic;

[0023] The associated target format result message is processed based on the preset business rule.

[0024] In one embodiment, the initial message data may include at least one of the following: an xml message, a txt message, and a csv message; and the target format message includes a JSON message.

[0025] The embodiment of this specification also provides a low-code platform message data processing device, including:

[0026] A receiving module, used for receiving initial message data; the initial message data includes message data in multiple formats;

[0027] A conversion module, used for converting the received initial message data into corresponding target format message data;

[0028] The association module is used to associate the target format message data according to the preset business logic and output the associated target format result message.

[0029] An embodiment of this specification also provides a computer device, including a processor and a memory for storing processor executable instructions, and when the processor executes the instructions, the steps of the low-code platform message data processing method described in any of the above embodiments are implemented.

[0030] An embodiment of this specification also provides a computer-readable storage medium on which computer instructions are stored. When the instructions are executed by a processor, the steps of the low-code platform message data processing method described in any of the above embodiments are implemented.

[0031] An embodiment of this specification also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the low-code platform message data processing method described in any of the above embodiments.

[0032] In an embodiment of the present specification, a low-code platform message data processing system is provided, including a message parser and a message adapter; the message parser is used to receive initial message data, and convert the received initial message data into corresponding target format message data; the initial message data includes message data in multiple formats; the message adapter is used to receive the target format message data output by the message parser, and associate the target format message data according to the preset business logic, and output the associated target format result message. In the above scheme, it can support multiple interfaces to be combined into one interface output, reduce the amount of code, and can be applied to complex business scenarios through configuration. The message adapter can be implemented in the low-code development platform, based on the online conversion function, multiple message formats can be adapted and converted into JSON, and multiple normalization and combined output can be achieved; the low-code development platform can make the message parser and message adapter appropriately encapsulated to achieve configurability, and has solved the difficulties such as performance and efficiency at the technical level, lowered the technical threshold at the usage level, and enabled developers to focus more on realizing business functions. The above solution solves the problem that the message conversion of the low-code development platform in the existing technology cannot be linked with the actual business system, and achieves the technical effect of effectively improving the message processing efficiency and reducing the amount of code. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The drawings described herein are used to provide a further understanding of this specification, constitute a part of this specification, and do not constitute a limitation of this specification. In the drawings:

[0034] Figure 1 A schematic diagram of the structure of a low-code platform message data processing system in one embodiment of this specification is shown;

[0035] Figure 2 A flowchart of a low-code platform message data processing method in an embodiment of this specification is shown;

[0036] Figure 3 An application flow chart of a low-code platform message data processing system in an embodiment of this specification is shown;

[0037] Figure 4 A processing flow chart of a low-code platform message data processing system in an embodiment of this specification is shown;

[0038] Figure 5 A schematic diagram of a low-code platform message data processing device in an embodiment of this specification is shown;

[0039] Figure 6 A schematic diagram of a computer device in an embodiment of the present specification is shown. DETAILED DESCRIPTION

[0040] The principles and spirit of this specification will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement this specification, and are not intended to limit the scope of this specification in any way. On the contrary, these embodiments are provided to make this specification more thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art.

[0041] Those skilled in the art will appreciate that the embodiments of this specification may be implemented as a system, device, method, or computer program product. Therefore, this specification may be implemented in the following forms: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0042] An embodiment of this specification provides a method for processing message data on a low-code platform. Figure 1 A schematic diagram of a low-code platform message data processing system in one embodiment of this specification is shown. Figure 1 As shown, the low-code platform message data processing system in this embodiment may include a message parser 101 and a message adapter 102.

[0043] The message parser 101 may be used to receive initial message data and convert the received initial message data into corresponding target format message data; the initial message data includes message data in multiple formats.

[0044] The message parser can parse the received initial message data and convert it into a target format message after parsing. The initial message data can include message data in multiple formats.

[0045] In some embodiments of the present specification, the initial message data may include at least one of the following: an xml message, a txt message, a csv message; and the target format message includes a JSON message.

[0046] In some embodiments of the present specification, the message parser may include multiple interfaces, each of the multiple interfaces is used to receive message data of an instruction type.

[0047] For example, in the scenario of querying student scores, the message parser may include two interfaces, one interface is used to receive student basic information in txt format, and the other interface is used to receive student score information in xml format.

[0048] For another example, in a risk prediction scenario, a message parser may include three interfaces, one for receiving basic customer information, one for receiving customer historical transaction data, and one for receiving customer credit data. The message data received by the three interfaces may be in the same format or in different formats.

[0049] The message adapter 102 may be used to receive the target format message data output by the message parser, and perform association processing on the target format message data according to a preset business logic, and output an associated target format result message.

[0050] The message adapter can receive multiple target format message data output by the message parser. The message adapter can be configured differently for different business scenarios. Accordingly, the message adapter can associate the target format message data according to the preset business logic to obtain a target format result message.

[0051] For example, in the score query scenario, the basic information and score information of the same student can be associated to generate a target format result message.

[0052] In the above embodiment, it is possible to support the combination of multiple interfaces into one interface output, reduce the amount of code, and apply it to complex business scenarios through configuration. A message adapter can be implemented in a low-code development platform, and based on the online conversion function, a variety of message formats can be adapted and converted into JSON, and multiple normalization and combined output can be achieved; the low-code development platform can make the message parser and message adapter appropriately encapsulated and configurable, and has solved the difficulties of performance and efficiency at the technical level, lowering the technical threshold at the usage level, allowing developers to focus more on realizing business functions. The above solution solves the problem that the message conversion of the low-code development platform in the prior art fails to be linked with the actual business system, and achieves the technical effect of effectively improving the efficiency of message processing and reducing the amount of code.

[0053] In some embodiments of the present specification, the message adapter determines the association attribute according to a preset business logic, and performs association processing on the target format message data based on the association attribute.

[0054] Specifically, the associated attribute information can be determined according to the business logic. For example, in the scenario of querying student scores, the student ID can be determined as the associated attribute. Then, the student basic information and the student scores are associated based on the student ID to generate the associated target format result message.

[0055] For another example, in the scenario of customer loan risk prediction, the customer account can be used as an associated attribute. Then, based on the user account, the customer basic information, customer historical transaction data and customer credit data are associated to generate an associated target format result message.

[0056] In some embodiments of the present specification, the message parser and the message adapter are debugged in a visual presentation form.

[0057] The message parser and message adapter can be debugged in a visual way on the low-code platform. By developing and debugging visualization, it is easier to analyze and find errors.

[0058] In some embodiments of the present specification, the message parser can be configured in response to the drag and drop operation of the developer. The configuration can be performed in a visual manner, which can reduce the development cycle and save labor costs.

[0059] In some embodiments of the present specification, the device further includes a message processor, which is used to receive a target format result message output by the message adapter and process the target format result message according to a preset business rule corresponding to the preset business logic.

[0060] After obtaining the target format result message, the target format result message can be processed according to the preset business rules corresponding to the preset business logic. For example, after querying and obtaining the student score message, it can be determined which interval the student's score is in. For another example, after obtaining customer risk-related data, the customer risk-related data can be analyzed and processed according to the risk judgment rules to determine the risk level of the customer.

[0061] Figure 2 A flow chart of a low-code platform message data processing method in an embodiment of this specification is shown. Although this specification provides method operation steps or device structures as shown in the following embodiments or drawings, more or fewer operation steps or module units may be included in the method or device based on routine or no creative labor. In the steps or structures where there is no necessary causal relationship logically, the execution order of these steps or the module structure of the device is not limited to the execution order or module structure described in the embodiments of this specification and shown in the drawings. When the method or module structure described is applied to an actual device or terminal product, it can be connected according to the method or module structure shown in the embodiments or drawings for sequential execution or parallel execution (for example, a parallel processor or a multi-threaded processing environment, or even a distributed processing environment).

[0062] Specifically, Figure 2 As shown, a low-code platform message data processing method provided by an embodiment of this specification may include the following steps:

[0063] Step S201, receiving initial message data; the initial message data includes message data in multiple formats.

[0064] The initial message data may be received by a message parser, and the initial message data may include message data in multiple formats.

[0065] In some embodiments of the present specification, the message parser may include multiple interfaces, each of the multiple interfaces is used to receive message data of an instruction type.

[0066] For example, in the scenario of querying student scores, the message parser may include two interfaces, one interface is used to receive student basic information in txt format, and the other interface is used to receive student score information in xml format.

[0067] For another example, in a risk prediction scenario, a message parser may include three interfaces, one for receiving basic customer information, one for receiving customer historical transaction data, and one for receiving customer credit data. The message data received by the three interfaces may be in the same format or in different formats.

[0068] Step S202: convert the received initial message data into corresponding target format message data.

[0069] The message parser can parse the received initial message data and convert it into a target format message after parsing. The initial message data can include message data in multiple formats.

[0070] In some embodiments of the present specification, the initial message data may include at least one of the following: an xml message, a txt message, a csv message; and the target format message includes a JSON message.

[0071] Step S203, performing association processing on the target format message data according to preset business logic, and outputting the associated target format result message.

[0072] The message adapter may receive the target format message data output by the message parser, and perform association processing on the target format message data according to a preset business logic, and output an associated target format result message.

[0073] The message adapter can receive multiple target format message data output by the message parser. The message adapter can be configured differently for different business scenarios. Accordingly, the message adapter can associate the target format message data according to the preset business logic to obtain a target format result message.

[0074] For example, in the score query scenario, the basic information and score information of the same student can be associated to generate a target format result message.

[0075] In the above embodiment, it is possible to support the combination of multiple interfaces into one interface output, reduce the amount of code, and apply it to complex business scenarios through configuration. A message adapter can be implemented in a low-code development platform, and based on the online conversion function, a variety of message formats can be adapted and converted into JSON, and multiple normalization and combined output can be achieved; the low-code development platform can make the message parser and message adapter appropriately encapsulated and configurable, and has solved the difficulties of performance and efficiency at the technical level, lowering the technical threshold at the usage level, allowing developers to focus more on realizing business functions. The above solution solves the problem that the message conversion of the low-code development platform in the prior art fails to be linked with the actual business system, and achieves the technical effect of effectively improving the efficiency of message processing and reducing the amount of code.

[0076] In some embodiments of the present specification, associating the target format message data according to preset business logic and outputting the associated target format result message may include: determining association attributes according to the preset business logic; and associating the target format message data based on the association attributes, and outputting the associated target format result message.

[0077] Specifically, the associated attribute information can be determined according to the business logic. For example, in the scenario of querying student scores, the student ID can be determined as the associated attribute. Then, the student basic information and the student scores are associated based on the student ID to generate the associated target format result message.

[0078] For another example, in the scenario of customer loan risk prediction, the customer account can be used as an associated attribute. Then, based on the user account, the customer basic information, customer historical transaction data and customer credit data are associated to generate an associated target format result message.

[0079] In some embodiments of the present specification, after outputting the associated target format result message, after outputting the associated target format result message, it may also include: obtaining the preset business rules corresponding to the preset business logic; and processing the associated target format result message based on the preset business rules.

[0080] After obtaining the target format result message, the target format result message can be processed according to the preset business rules corresponding to the preset business logic. For example, after querying and obtaining the student score message, it can be determined which interval the student's score is in. For another example, after obtaining customer risk-related data, the customer risk-related data can be analyzed and processed according to the risk judgment rules to determine the risk level of the customer.

[0081] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. For details, please refer to the description of the above-mentioned related processing related embodiments, and no further description is given here.

[0082] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0083] The above method is described below in conjunction with a specific embodiment. However, it should be noted that the specific embodiment is only for better illustrating the present specification and does not constitute an improper limitation on the present specification.

[0084] This specific embodiment provides a low-code platform message data processing method. The interface interaction in the current technical field is usually in JSON format, so the message format of xml, txt, csv and other protocols can be uniformly and visually converted to JSON format, and multiple interfaces can be combined into one interface output. Please refer to Figure 3 , shows an application flow chart for implementing the low-code platform message data processing method in this embodiment. Figure 3 As shown, the two interfaces of the message parser can receive txt messages and xml messages respectively, and parse the received messages to convert them into corresponding JSON messages. The message adapter can associate the received JSON messages according to the business logic configuration, output a JSON message, and then apply the JSON message to the business scenario corresponding to the business logic configuration. In this way, the amount of code can be reduced, the message adapter can be abstracted from the low-code development platform, and complex business scenarios can be implemented through configuration.

[0085] The core idea of ​​this specific embodiment is to implement a message adapter in a low-code development platform. Based on the online conversion function, a variety of message formats are adapted and converted into JSON, and the output can be normalized and combined in multiple ways, and debugged conveniently in a visual presentation form. In the design state, development and debugging can be carried out by setting sample data, and in the running state, the interface needs to be called in real time.

[0086] In a scenario instance of multi-factor normalization and combined output, such as credit risk control logic, multiple external data sources can be called, using a certain attribute of interface 1 and a certain attribute of interface 2. After the two attributes are obtained, the risk control rules are executed. In conventional development, it is necessary to call the parsed message separately and then repackage the required attributes into a new message for use. In this solution, the entire process is encapsulated as a low-code adapter to achieve multi-factor normalization, and a simple drag-and-drop configuration can realize this complex scenario.

[0087] The message parser can parse messages in various formats (xml, txt, csv).

[0088] The message adapter can adapt the parsed message to the configured JSON format.

[0089] Through Java, the parsing logic of messages in various formats can be encapsulated into components in the low-code development platform, supporting multi-threading and improving efficiency.

[0090] Please refer to Figure 4 , shows a processing flow chart of the low-code message data processing method in this embodiment applied to a specific business scenario of querying student scores. Figure 4 As shown, the following contents may be included.

[0091] The basic information interface of student Zhang San is a message provided in txt format, separated by |;.

[0092] The interface for student Zhang San's grade information is a message provided in XML format;

[0093] Through the designer provided by the low-code development platform, drag the txt message parser / xml message parser to the designer's canvas, configure the parsing steps, and output them as JSON messages respectively.

[0094] Through the message adapter, the JSON messages output by the two interfaces are associated through the relationship attribute, so that the data can be associated and combined into a new JSON to output the result. The relationship attribute here can be id, and in this embodiment, the value is 3.

[0095] In this specific embodiment, message parsing can be visually configured on the low-code development platform, and multiple types of messages can be combined into a standard RESTful interface protocol. In this solution, the low-code development platform has properly encapsulated the message parser and message adapter to make them configurable, and has solved the difficulties of performance and efficiency at the technical level, lowering the technical threshold at the usage level, allowing developers to focus more on realizing business functions; the visual configuration method reduces the development cycle and saves labor costs; the visualization of development and debugging makes it easier to analyze and discover errors.

[0096] Based on the same inventive concept, a low-code platform message data processing device is also provided in the embodiments of this specification, as described in the following embodiments. Since the principle of solving the problem by the low-code platform message data processing device is similar to that of the low-code platform message data processing method, the implementation of the low-code platform message data processing device can refer to the implementation of the low-code platform message data processing method, and the repeated parts will not be repeated. As used below, the terms "unit" or "module" can be a combination of software and / or hardware that implements predetermined functions. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived. Figure 5 It is a structural block diagram of a low-code platform message data processing device of an embodiment of this specification, such as Figure 5 As shown, it includes: a receiving module 501, a conversion module 502 and an association module 503, and the structure is described below.

[0097] The receiving module 501 is used to receive initial message data; the initial message data includes message data in multiple formats.

[0098] The conversion module 502 is used to convert the received initial message data into corresponding target format message data.

[0099] The association module 503 is used to perform association processing on the target format message data according to a preset business logic, and output the associated target format result message.

[0100] In some embodiments of this specification, the association module may be specifically used for:

[0101] Determine the associated attributes based on the preset business logic;

[0102] Based on the association attribute, the target format message data is associated and processed, and the associated target format result message is output.

[0103] In some embodiments of the present specification, the device may further include a determination module, and the determination module may be specifically used to:

[0104] Obtaining preset business rules corresponding to the preset business logic;

[0105] The associated target format result message is processed based on the preset business rule.

[0106] In some embodiments of the present specification, the initial message data may include at least one of the following: an xml message, a txt message, a csv message; and the target format message includes a JSON message.

[0107] From the above description, it can be seen that the embodiments of this specification achieve the following technical effects: a low-code platform message data processing system is provided, including a message parser and a message adapter; the message parser is used to receive initial message data and convert the received initial message data into corresponding target format message data; the initial message data includes message data in multiple formats; the message adapter is used to receive the target format message data output by the message parser, and associate the target format message data according to the preset business logic, and output the associated target format result message. In the above scheme, it can support multiple interfaces to be combined into one interface output, reduce the amount of code, and can be applied to complex business scenarios through configuration. The message adapter can be implemented in the low-code development platform, based on the online conversion function, multiple message formats can be adapted and converted into JSON, and multiple normalization and combined output can be achieved; the low-code development platform can make the message parser and message adapter appropriately encapsulated to achieve configurability, and has solved the difficulties such as performance and efficiency at the technical level, reducing the technical threshold at the usage level, so that developers can focus more on realizing business functions. The above solution solves the problem that the message conversion of the low-code development platform in the existing technology cannot be linked with the actual business system, and achieves the technical effect of effectively improving the message processing efficiency and reducing the amount of code.

[0108] This specification also provides a computer device, which can be found in Figure 6 The computer device composition structure diagram of the low-code platform message data processing method provided in the embodiment of this specification is shown, and the computer device may specifically include an input device 61, a processor 62, and a memory 63. Among them, the memory 63 is used to store processor executable instructions. When the processor 62 executes the instructions, the steps of the low-code platform message data processing method described in any of the above embodiments are implemented.

[0109] In this embodiment, the input device may specifically be one of the main devices for information exchange between the user and the computer system. The input device may include a keyboard, a mouse, a camera, a scanner, a light pen, a handwriting input board, a voice input device, etc.; the input device is used to input the original data and the program for processing these numbers into the computer. The input device can also obtain and receive data transmitted from other modules, units, and devices. The processor can be implemented in any appropriate manner. For example, the processor can take the form of a computer-readable medium, a logic gate, a switch, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a programmable logic controller, and an embedded microcontroller, etc., such as a microprocessor or a processor and a computer-readable program code (such as software or firmware) that can be executed by the (micro) processor. The memory may specifically be a memory device used to store information in modern information technology. The memory may include multiple levels. In a digital system, anything that can store binary data can be a memory; in an integrated circuit, a circuit with a storage function without a physical form is also called a memory, such as a RAM, a FIFO, etc.; in a system, a storage device with a physical form is also called a memory, such as a memory stick, a TF card, etc.

[0110] In this embodiment, the functions and effects specifically realized by the computer device can be explained in comparison with other embodiments and will not be described in detail here.

[0111] A computer storage medium based on a low-code platform message data processing method is also provided in the implementation manner of this specification, and the computer storage medium stores computer program instructions, which implement the steps of the low-code platform message data processing method described in any of the above embodiments when the computer program instructions are executed by the processor.

[0112] In this embodiment, the storage medium includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), a cache, a hard disk (HDD) or a memory card. The memory may be used to store computer program instructions. The network communication unit may be an interface for network connection communication set in accordance with the standard specified by the communication protocol.

[0113] In this embodiment, the functions and effects specifically implemented by the program instructions stored in the computer storage medium can be explained in comparison with other embodiments and will not be repeated here.

[0114] An embodiment of this specification also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the low-code platform-based method described in any of the above embodiments.

[0115] Obviously, those skilled in the art should understand that the modules or steps of the above-mentioned embodiments of this specification can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. In this way, the embodiments of this specification are not limited to any specific combination of hardware and software.

[0116] It should be understood that the above description is for illustration and not for limitation. Many embodiments and many applications beyond the examples provided will be apparent to those skilled in the art upon reading the above description. Therefore, the scope of this specification should not be determined with reference to the above description, but should be determined with reference to the preceding claims and the full scope of equivalents to which these claims belong.

[0117] The above description is only the preferred embodiment of this specification and is not intended to limit this specification. For those skilled in the art, the embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included in the protection scope of this specification.

Claims

1. A low-code platform message data processing system, characterized in that: Including message parser and message adapter; The message parser is used to receive initial message data and convert the received initial message data into corresponding target format message data; The initial message data includes message data in multiple formats; the message parser includes multiple interfaces, each of the multiple interfaces is used to receive message data of instruction type; The message adapter is used to receive the target format message data output by the message parser, determine the associated attributes according to the preset business logic, and perform associated processing on the target format message data based on the associated attributes, and output the associated target format result message.

2. The low-code platform message data processing system according to claim 1 is characterized in that: The message parser comprises a plurality of interfaces, each of which is used for receiving message data of an instruction type.

3. The low-code platform message data processing system according to claim 1 is characterized in that: The message parser and the message adapter can be debugged in a visual presentation form.

4. The low-code platform message data processing system according to claim 1 is characterized in that: The message parser can be configured in response to a drag and drop operation by a developer.

5. The low-code platform message data processing system according to claim 1 is characterized in that: The initial message data includes at least one of the following: an xml message, a txt message, and a csv message; the target format message includes a JSON message.

6. The low-code platform message data processing system according to claim 1 is characterized in that: It also includes a message processor, which is used to receive the target format result message output by the message adapter and process the target format result message according to the preset business rules corresponding to the preset business logic.

7. A low-code platform message data processing method, characterized in that: include: Receive initial message data; The initial message data includes message data in multiple formats; The initial message is received through multiple interfaces, each of the multiple interfaces is used to receive message data of the instruction type; Convert the received initial message data into corresponding target format message data; The associated attributes are determined according to the preset business logic, and the target format message data is associated based on the associated attributes, and the associated target format result message is output.

8. The low-code platform message data processing method according to claim 7 is characterized in that: After outputting the associated target format result message, it also includes: Obtaining preset business rules corresponding to the preset business logic; The associated target format result message is processed based on the preset business rule.

9. The low-code platform message data processing method according to claim 8 is characterized in that: The initial message data includes at least one of the following: an xml message, a txt message, and a csv message; the target format message includes a JSON message.

10. A low-code platform message data processing device, characterized in that: include: A receiving module, used for receiving initial message data; The initial message data includes message data in multiple formats; The initial message is received through multiple interfaces, each of the multiple interfaces is used to receive message data of the instruction type; A conversion module, used for converting the received initial message data into corresponding target format message data; The association module is used to determine the association attribute according to the preset business logic, and to perform association processing on the target format message data based on the association attribute, and output the associated target format result message.

11. A computer device, characterized in that: The method comprises a processor and a memory for storing processor-executable instructions, wherein the processor implements the steps of the method according to any one of claims 7 to 9 when executing the instructions.

12. A computer-readable storage medium having computer instructions stored thereon, characterized in that: When the instructions are executed by a processor, the steps of the method according to any one of claims 7 to 9 are implemented.

13. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the method according to any one of claims 7 to 9 are implemented.

Images