Visual construction method and device for multiple linkage based on low-code platform

Abstract

The embodiment of the invention relates to the field of application service development, in particular to a multi-linkage visual construction method and device based on a low-code platform. According to the scheme, the method comprises the following steps: receiving a construction instruction of a developer on data or a component in a visual interface of a low-code platform, then setting a trigger condition based on a service demand of the low-code platform, traversing association configuration of the data and the component, and judging whether the construction instruction or the linkage configuration triggers data or component linkage or not; if the linkage is triggered, the linkage is processed according to the initial configuration requirement; and then data modification is performed on the data linkage, and component modification is performed on the component linkage. Component linkage and data linkage of a complex form in a low-code platform are realized. And meanwhile, the low-code platform form can be suitable for complex form configuration rules and use scenes of large enterprises, the labor cost is greatly reduced, and the platform construction efficiency is improved.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of application service development, and in particular to a method and device for constructing a multiple-linked visualization based on a low-code platform. Background Art

[0002] At present, the component linkage of the low-code platform form designer mainly includes single selection, checkbox, drop-down single selection and drop-down checkbox, and mainly in the visual low-code designer, the display and hiding of the associated components are controlled according to the inherent option value of the selected component. Similarly, data linkage mainly includes single selection, drop-down single selection, multiple selection, drop-down multiple selection, single-line text, multi-line text, numerical value, date, and picture components. It is mainly in the visual low-code designer that the conditions of data association are set through the selected data association table, so as to affect the display value of a component in the data association table according to the data association rules. At present, component linkage and data linkage can be completed in the construction of the low-code platform. The main implementation method is to link other components or data already existing in the low-code platform itself through complex configuration methods in the low-code platform form designer. In the actual application process, it is suitable for relatively simple form linkage rules. When faced with complex form linkage rules, the current implementation method often leads to complex configuration items and insufficient flexibility. In addition, the maintainability and scalability of the configuration items are poor, which affects the development efficiency of low-code developers. However, in actual applications, the usage rules of forms are more complicated, which puts higher requirements on the flexibility, maintainability, and scalability of the configuration items of the form's component linkage and data linkage. The existing configuration methods are already difficult to adapt to the low-code R&D requirements of large-scale enterprise form component linkage and data linkage.

[0003] At present, there is an urgent need for a visual construction method of component linkage and data linkage based on a low-code platform, which can significantly improve the configuration flexibility, maintainability, and scalability of component linkage and data linkage of complex forms on the low-code platform, significantly improve the development efficiency of low-code developers, and make the low-code platform forms applicable to the complex form configuration rules and usage scenarios of large enterprises. Summary of the invention

[0004] In order to solve the problem that the configuration method in the existing technology is difficult to adapt to the low-code R&D requirements of large-scale enterprise form component linkage and data linkage, the embodiment of this specification provides a method and device for visual construction of multiple linkages based on a low-code platform, which can perform visual construction of component linkage and data linkage based on the low-code platform, and obtain the initial configuration requirements according to the business needs of the low-code platform to generate a linkage processing solution, perform linkage modification, and realize component linkage and data linkage of complex forms in the low-code platform. At the same time, the low-code platform form can be applied to the complex form configuration rules and usage scenarios of large enterprises, greatly reducing labor costs and improving platform construction efficiency. The specific technical solutions of the embodiments of this specification are as follows:

[0005] On the one hand, the embodiments of this specification provide a method for constructing multiple linkage visualizations based on a low-code platform, including:

[0006] Receive instructions from developers on building data or components in the visual interface of the low-code platform;

[0007] Acquire initial configuration requirements based on the business requirements of the low-code platform, and set trigger conditions according to the initial configuration requirements;

[0008] Traversing the associated configurations of data and components, and determining whether the build instruction or the linkage configuration triggers data or component linkage according to the trigger condition;

[0009] When the data or component triggers the linkage, the linkage is processed according to the initial configuration requirements:

[0010] If the type of linkage is data linkage, the target data of the data linkage requirement is obtained according to the initial configuration requirement, and the data of the low-code platform is modified according to the target data;

[0011] If the type of linkage is component linkage, the target component involved in the component linkage is obtained, configuration information is obtained according to the initial configuration requirements, and the low-code platform performs component modification according to the configuration information.

[0012] Furthermore, determining whether the construction instruction triggers data or component linkage further includes:

[0013] When the construction instruction involves data or components with associated configurations and satisfies the triggering condition, triggering the data or components to be linked; or,

[0014] When the associated configuration of the data and components triggers a logic conflict or backend data modification, the data or component linkage is triggered.

[0015] Further, judging whether the construction instruction or the linkage configuration triggers data or component linkage according to the trigger condition further includes:

[0016] If there is no linkage configuration that meets the trigger condition, the construction is terminated.

[0017] Furthermore, judging whether the construction instruction triggers data or component linkage according to the trigger condition and the associated configuration further includes:

[0018] If the trigger condition is an expression, the expression is sent to an expression parser for parsing to obtain a parsing result, and the parsing result is returned to the low-code platform, and it is determined whether the data or component triggers linkage based on the parsing result.

[0019] Furthermore, if the linkage type is component linkage, it further includes:

[0020] Determine the target component according to the associated configuration of the component and the initial configuration requirement;

[0021] Traverse and search for the target component in the component tree, and obtain the DOM node of the target component;

[0022] The component state of the target component is modified according to the DOM node of the target component and the configuration information.

[0023] Furthermore, modifying the component state of the target component further includes:

[0024] Obtain the data source configuration corresponding to the DOM node from the data source registration list of the data source center;

[0025] Parsing the expression involved in the data source configuration to obtain a parsing result, and generating a modification request according to the parsing result;

[0026] The configuration name in the configuration information is obtained, and the target component is modified according to the modification request and the configuration name.

[0027] Furthermore, the component linkage also includes:

[0028] Bidirectional component linkage, according to the associated configuration of the target component, the configuration information is updated based on the properties and status of the target component, and the low-code platform performs component modification according to the updated configuration information; or,

[0029] Multi-level component linkage. When the target component contains multiple multi-select and check-select components, the low-code platform modifies the components and then traverses the linkage configuration of the data and components again.

[0030] Further, processing the linkage according to the initial configuration requirement further includes:

[0031] Dynamic rule linkage: When there are multiple mixed conditions in the association configuration of data and components, the linkage rules are set through dynamic rule linkage.

[0032] On the other hand, the embodiment of this specification also provides a multiple linkage visualization construction device based on a low-code platform, the device comprising:

[0033] An instruction receiving unit, used to receive instructions for building data or components from developers in a visual interface of a low-code platform;

[0034] A trigger condition setting unit, used to obtain initial configuration requirements based on the business requirements of the low-code platform, and set trigger conditions according to the initial configuration requirements;

[0035] A linkage judgment unit, used for traversing the association configuration of data and components, and judging whether the construction instruction triggers data or component linkage according to the trigger condition and the association configuration;

[0036] A linkage processing unit, configured to process the linkage according to the initial configuration requirements after the data or component triggers the linkage:

[0037] A data linkage processing unit, configured to, when the linkage type is data linkage, obtain target data of the data linkage requirement according to the initial configuration requirement, and modify data of the low-code platform according to the target data;

[0038] The component linkage processing unit is used to obtain the target component involved in the component linkage when the linkage type is component linkage, obtain configuration information according to the initial configuration requirements, and modify the component on the low-code platform according to the configuration information.

[0039] On the other hand, an embodiment of the present specification further provides a computer device, including a memory, a processor, and a computer program stored in the memory, and the processor implements the above method when executing the computer program.

[0040] On the other hand, an embodiment of the present specification further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program implements the above method when executed by a processor.

[0041] Finally, the embodiments of this specification also provide a computer program product, wherein the computer program product includes a computer program, and the computer program implements the above method when executed by a processor.

[0042] By using the embodiment of this specification, the developer's construction instructions for data or components in the visual interface of the low-code platform are received, so as to obtain the developer's direct modification of the low-code platform; then, based on the requirements of different business scenarios in the low-code platform, the matching initial configuration requirements are obtained, and the trigger conditions under the business scenario are set according to the initial configuration requirements; then, the linkage configuration of data and components is traversed, and the construction instructions or linkage configuration are judged according to the trigger conditions whether to trigger the data or component linkage; when the data or component linkage is triggered, the configuration information is obtained according to the initial configuration requirements and the linkage is processed: if the triggered linkage type is data linkage, the target data of the data linkage requirement is obtained in the database according to the configuration information, and the data of the low-code platform is modified according to the target data; if the triggered linkage type is component linkage, the target component involved in the component linkage requirement component is obtained, and the data source configuration is obtained according to the configuration information to modify the component of the low-code platform. In this way, the visual component linkage and data linkage configuration are realized, the linkage rules and linkage logic are transformed into visual step configuration, and the trigger condition events, response events and linkage components, and response operations of linkage components are configured in sequence, and written into the linkage configuration attributes, which enhances the maintainability of the form linkage settings. At the same time, the low-code platform is automatically constructed according to linkage rules and linkage logic, which greatly reduces labor costs and improves platform construction efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0044] Figure 1 The figure shows a schematic diagram of an implementation system of a multiple linkage visualization construction method based on a low-code platform in an embodiment of this specification;

[0045] Figure 2 The figure is a flow chart of a method for constructing a visualization of multiple linkages based on a low-code platform in an embodiment of this specification;

[0046] Figure 3 It is a schematic diagram of the process of modifying components when the linkage type is component linkage in the embodiment of this specification;

[0047] Figure 4 It is a schematic diagram of bidirectional component linkage in the embodiment of this specification;

[0048] Figure 5 It is a schematic diagram of the linkage of multiple components in the embodiment of this specification;

[0049] Figure 6 Shown is a schematic diagram of dynamic rule linkage in an embodiment of this specification;

[0050] Figure 7 The figure shows a specific structural diagram of a multiple linkage visualization construction device based on a low-code platform in this embodiment;

[0051] Figure 8 The figure is a schematic diagram of the structure of a computer device in an embodiment of the present specification.

[0052]

Description of reference numerals

[0053] 101. Terminal;

[0054] 102. Platform side;

[0055] 701, instruction receiving unit;

[0056] 702. Trigger condition setting unit;

[0057] 703, linkage judgment unit;

[0058] 704, linkage processing module;

[0059] 7041, data linkage processing unit;

[0060] 7042, component linkage processing unit;

[0061] 802. Computer equipment;

[0062] 804. Processing equipment;

[0063] 806. Storage resources;

[0064] 808, drive system;

[0065] 810, input / output module;

[0066] 812. Input device;

[0067] 814. Output device;

[0068] 816. Presentation equipment;

[0069] 818. Graphical user interface;

[0070] 820, network interface;

[0071] 822, communication link;

[0072] 824. Communication bus. DETAILED DESCRIPTION

[0073] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on the embodiments in the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the embodiments of this specification.

[0074] It should be noted that the terms "first", "second", etc. in the description and claims of the embodiments of this specification and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the embodiments of this specification described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0075] It should be noted that the acquisition, storage, use, and processing of data in the technical solutions of the embodiments of this specification comply with the relevant provisions of national laws and regulations.

[0076] It should be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0077] like Figure 1The diagram shows a schematic diagram of the implementation system of a visual construction method for multiple linkages based on a low-code platform in an embodiment of the specification, including a terminal 101 and a platform end 102. The terminal 101 and the platform end 102 can communicate through a network, and the network may include a local area network (LAN), a wide area network (WAN), the Internet, or a combination thereof, and is connected to a website, a user device (such as a computing device), and a back-end system. Optionally, the platform end 102 may be a node of a cloud computing system, or each platform end may be a separate cloud computing system, including multiple computers interconnected by a network and working as a distributed processing system. The terminal 101 receives the developer's build instruction and sends it to the platform end 102. The platform end 102 determines whether the build instruction triggers data or component linkage based on the triggering condition, and then processes the linkage according to the business needs of the low-code platform, and finally visualizes the modifications to the low-code platform through the terminal 101.

[0078] In addition, it should be noted that Figure 1 What is shown is only one application environment provided by the embodiment of this specification. In actual application, other application environments may also be included, and this specification does not limit it.

[0079] In view of the problems existing in the prior art, the embodiments of this specification provide a method for visually constructing multiple linkages based on a low-code platform, which obtains the initial configuration requirements according to the business requirements of the low-code platform, generates a processing solution for linkage processing, and performs linkage modification to realize component linkage and data linkage of complex forms in the low-code platform. At the same time, the low-code platform forms can be applied to the complex form configuration rules and usage scenarios of large enterprises, greatly reducing labor costs and improving platform construction efficiency.

[0080] Figure 2 The figure shows a flowchart of a method for visual construction of multiple linkages based on a low-code platform in an embodiment of this specification. This figure describes the process of visual construction of linkages in a low-code platform. The order of steps listed in the embodiment is only one way of executing the steps among many, and does not represent the only order of execution. When the system or device product is executed in practice, it can be executed in sequence or in parallel according to the method shown in the embodiment or the accompanying drawings.

[0081] Specific as Figure 2 As shown, the method may include:

[0082] Step 201: receiving a developer's instruction to construct data or components in a visual interface of a low-code platform;

[0083] Step 202: Obtaining initial configuration requirements based on the business requirements of the low-code platform, and setting trigger conditions according to the initial configuration requirements;

[0084] Step 203: traverse the association configuration of data and components, and determine whether the construction instruction or the linkage configuration triggers data or component linkage according to the trigger condition;

[0085] Step 204: After the data or component triggers the linkage, the linkage is processed according to the initial configuration requirements:

[0086] Step 205: If the linkage type is data linkage, obtaining target data of the data linkage requirement according to the initial configuration requirement, and modifying data of the low-code platform according to the target data;

[0087] Step 206: If the type of linkage is component linkage, then the target component involved in the component linkage is obtained, configuration information is obtained according to the initial configuration requirements, and the low-code platform performs component modification according to the configuration information.

[0088] By using the embodiment of this specification, the developer's construction instructions for data or components in the visual interface of the low-code platform are received, so as to obtain the developer's direct modification of the low-code platform; then, based on the requirements of different business scenarios in the low-code platform, the matching initial configuration requirements are obtained, and the trigger conditions under the business scenario are set according to the initial configuration requirements; then, the linkage configuration of data and components is traversed, and the construction instructions or linkage configuration are judged according to the trigger conditions whether to trigger the data or component linkage; when the data or component linkage is triggered, the configuration information is obtained according to the initial configuration requirements and the linkage is processed: if the triggered linkage type is data linkage, the target data of the data linkage requirement is obtained in the database according to the configuration information, and the data of the low-code platform is modified according to the target data; if the triggered linkage type is component linkage, the target component involved in the component linkage requirement component is obtained, and the data source configuration is obtained according to the configuration information to modify the component of the low-code platform. In this way, the visual component linkage and data linkage configuration are realized, the linkage rules and linkage logic are transformed into visual step configuration, and the trigger condition events, response events and linkage components, and response operations of linkage components are configured in sequence, and written into the linkage configuration attributes, which enhances the maintainability of the form linkage settings. At the same time, the low-code platform is automatically constructed according to linkage rules and linkage logic, which greatly reduces labor costs and improves platform construction efficiency.

[0089] In the embodiments of this specification, the component linkage of the low-code platform form designer mainly includes single selection, multiple selection, drop-down single selection and drop-down multiple selection, etc., which mainly controls the visibility of associated components according to the inherent option value of the selected component in the visual low-code designer. Similarly, data linkage mainly includes single selection, drop-down single selection, multiple selection, drop-down multiple selection, single-line text, multi-line text, value, date, and picture components, which mainly controls the display value of a component in the data association table set according to the data association rules in the visual low-code designer.

[0090] According to an embodiment of the present specification, in order to confirm whether there is a trigger linkage between data and components, the trigger condition for determining whether the construction instruction or the linkage configuration triggers data or component linkage according to the trigger condition includes:

[0091] When the construction instruction involves data or components with associated configurations and satisfies the triggering condition, triggering the data or components to be linked; or,

[0092] When the associated configuration of the data and components triggers a logic conflict or backend data modification, the data or component linkage is triggered.

[0093] If there is no linkage configuration that meets the trigger condition, the construction is terminated.

[0094] According to one embodiment of the present specification, the associated configuration of the component data is checked and traversed. If there is no configuration, the process ends directly; if there is a configuration, the process proceeds to the next step: when the developer receives the build instruction for data or components in the visual interface of the low-code platform and the instruction involves data or components with associated configurations, and the trigger conditions are met at the same time, the data or components are judged to have triggered the data or component linkage; or, when the associated configuration of the data and components triggers a logical conflict or back-end data modification, the data or components can also be judged to have triggered the data or component linkage. At the same time, if there is no linkage configuration that meets the trigger conditions after traversing the linkage configuration of the data and components, the construction ends directly. For example, after the developer enters the build instruction in the low-code platform, the components involved in the build instruction do not involve components or data with associated configurations, and the construction is performed directly according to the build instruction.

[0095] Specifically, the low-code platform includes a monitoring component. Monitoring events are added in the monitoring component as trigger conditions for data linkage and component linkage. Among them, the trigger condition is when the component value changes, and the change of component value includes two situations. One is the direct modification of components or data by developers in the visual interface of the low-code platform; the other is the modification caused by triggering logical conflicts or back-end data modifications during the construction or operation of the low-code platform. Regardless of the modification method, a component value change event will be triggered. Therefore, all data and components need to be bound to the component value change event, so that when the component value is updated, the monitoring component can be triggered to monitor the change event in time.

[0096] According to an embodiment of the present specification, judging whether the construction instruction triggers data or component linkage according to the trigger condition and the associated configuration further includes:

[0097] If the trigger condition is an expression, the expression is sent to an expression parser for parsing to obtain a parsing result, and the parsing result is returned to the low-code platform, and it is determined whether the data or component triggers linkage based on the parsing result.

[0098] In the embodiment of the present specification, if the configured trigger condition is an expression, the expression needs to be parsed by an expression parser, and the expression parsing result is returned, and a judgment is made based on the parsing result to determine whether the data linkage or component linkage is triggered; at the same time, if the condition of the expression or value is met, the configuration information is passed to the message center, and the message notification component sends a message, which includes the name of the target component, the response operation of the target component and other related information; after the message notification center produces a new message, the monitoring component forwards it to the event processing center for processing.

[0099] According to one embodiment of the present specification, if the trigger condition is an expression, the expression is sent to an expression parser for parsing to obtain a parsing result, and the parsing result is returned to the low-code platform, and it is determined whether the data or component triggers linkage based on the parsing result.

[0100] According to one embodiment of this specification, Figure 3 As shown, if the type of linkage is component linkage, it further includes:

[0101] Step 301: Determine the target component according to the associated configuration of the component and the initial configuration requirement;

[0102] Step 302: traverse and search for the target component in the component tree, and obtain the DOM node of the target component;

[0103] Step 303: Modify the component state of the target component according to the DOM node of the target component and the configuration information.

[0104] Wherein, modifying the component state of the target component further includes:

[0105] Step 304: Obtain the data source configuration corresponding to the DOM node from the data source registration list of the data source center;

[0106] Step 305: parsing the expression involved in the data source configuration to obtain a parsing result, and generating a modification request according to the parsing result;

[0107] Step 306: Obtain the configuration name in the configuration information, and modify the target component according to the modification request and the configuration name.

[0108] In the embodiment of this specification, firstly, according to the associated configuration of the component in the processing request and the target component information carried by the initial configuration requirement, the component tree of the renderer is traversed and searched to obtain the DOM node of the target component. Secondly, the processing is performed according to the linkage type information carried in the processing request;

[0109] If the linkage type is data linkage, the target data of the data linkage requirement is obtained according to the initial configuration requirement, and the data of the low-code platform is modified according to the target data; the general execution action of data linkage is to modify component values, component drop-down lists and other related data operations. After obtaining the data returned by the data source center, the corresponding operation is performed according to the execution action information carried in the processing request to meet the execution effect.

[0110] If the linkage type is component linkage, the target component involved in the component linkage is obtained, the configuration information is obtained according to the initial configuration requirements, and the low-code platform modifies the component according to the configuration information. The general execution actions of component linkage are component visibility, required fields, read-only, etc., so after obtaining the DOM node of the target component, the status of the component is directly modified to meet the execution effect.

[0111] In another embodiment of the present specification, according to the data source configuration name carried in the processing request, the data source configuration of the corresponding name is obtained from the data source registration list of the data source center, and the request is assembled and sent according to the data source configuration. If the request parameter involves an expression, it needs to be parsed by the expression parser, and the result returned by the expression parser is used as the request parameter for assembly. Finally, the response body is processed and processed according to the data source configuration to generate the required data.

[0112] In the embodiments of this specification, in order to flexibly use this invention in large-scale enterprise-level applications, on the basis of the above technical solutions, two-way component linkage, multi-level data linkage and dynamic rule linkage are expanded to adapt to the enterprise-level form component scenario implementation. Specifically, the processing of the linkage also includes:

[0113] Bidirectional component linkage, according to the associated configuration of the target component, the configuration information is updated based on the properties and status of the target component, and the low-code platform performs component modification according to the updated configuration information; or,

[0114] Multi-level component linkage. When the target component contains multiple multi-select and check-select components, the low-code platform modifies the components and then traverses the linkage configuration of the data and components again.

[0115] Specifically, two-way component linkage is to flexibly configure two-way component linkage based on component attributes and states in the component linkage configuration of the form. Figure 4 As shown, you can configure component A to link component B, or you can configure component B to link component A in reverse, so that components A and B can be flexibly displayed, hidden, disabled, editable, or required in the same form according to the linkage rules. Multi-level data linkage is when a form contains multiple multiple-select, checkbox components, or multiple-select button groups. Through multi-level data linkage settings, multi-level data linkage between different components can be achieved. Figure 5 As shown, after configuring the data linkage of component A, the data values ​​of components B, C, and D can change accordingly. At the same time, the data values ​​of components B1, C1, C2, D1, and D2 will also change. By analogy, the values ​​of components Bn, C1n, C2n, D1n, and D2n will also change in linkage.

[0116] In another embodiment of the present specification, processing the linkage further includes:

[0117] Dynamic rule linkage: When there are multiple mixed conditions in the association configuration of data and components, the linkage rules are set through dynamic rule linkage.

[0118] Specifically, Figure 6 As shown, after setting various complex conditions of data source, component value, and function expression in the association configuration, after the linkage data and expressions set by the component and the target component are parsed, the linkage actions are distributed and executed to complete the linkage of dynamic rules.

[0119] A component linkage and data linkage construction scheme in this specification includes visual component linkage and data linkage configuration, bidirectional component linkage, multi-level data linkage, and dynamic rule linkage; the visual component linkage and data linkage configuration is realized, the linkage rules and linkage logic are transformed into visual step configuration, and the triggering conditions, response events, linkage components, and response operations of linkage components are configured in sequence, and written into the linkage configuration attributes. At the same time, the bidirectional component linkage realizes that the components in the form can be arbitrarily bidirectionally linked according to the linkage rules; the multi-level data linkage realizes the multi-level data linkage between components at different levels, meets the scenario of enterprise-level form data being displayed in association with each other, and improves the flexibility of form data display. The dynamic rule linkage realizes the linkage rule setting that uses a variety of association configuration conditions in a mixed manner, and improves the scalability of the linkage rule setting. In the embodiment of this specification, the linkage rules and linkage logic are also transformed into visual steps, and the component events are uniformly integrated through the event processing center, which enhances the maintainability of the form linkage setting. By configuring the linkage rules with the source component as the center, the configuration relationship of each linkage component can be more intuitively displayed, reducing the complexity of system operation.

[0120] As an example of this specification, please refer to Figure 7 FIG. 4 is a schematic diagram showing the specific structure of the salary calculation result verification device based on the clustering algorithm in this embodiment.

[0121] The instruction receiving unit 701 is used to receive the developer's instructions for building data or components in the visual interface of the low-code platform;

[0122] A trigger condition setting unit 702 is used to obtain initial configuration requirements based on the business requirements of the low-code platform and set trigger conditions according to the initial configuration requirements;

[0123] A linkage judgment unit 703 is used to traverse the association configuration of data and components, and judge whether the construction instruction triggers data or component linkage according to the trigger condition and the association configuration;

[0124] The linkage processing module 704 is used to process the linkage according to the initial configuration requirements after the data or component triggers the linkage:

[0125] The data linkage processing unit 7041 is used for obtaining the target data of the data linkage requirement according to the initial configuration requirement when the linkage type is data linkage, and modifying the data of the low-code platform according to the target data;

[0126] The component linkage processing unit 7042 is used to obtain the target component involved in the component linkage when the linkage type is component linkage, obtain configuration information according to the initial configuration requirements, and perform component modification on the low-code platform according to the configuration information.

[0127] Since the principle of solving the problem by the above device is similar to that of the above method, the implementation of the above system can refer to the implementation of the above method, and the repeated parts will not be repeated.

[0128] like Figure 8 The figure is a schematic diagram of the structure of a computer device according to an embodiment of the present specification. The computer device according to the embodiment of the present specification can run the method according to the embodiment of the present specification.

[0129] The computer device 802 may include one or more processing devices 804, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 802 may also include any storage resources 806 for storing any type of information such as code, settings, data, etc. Without limitation, for example, the storage resources 806 may include any one or more combinations of the following: any type of RAM, any type of ROM, a flash memory device, a hard disk, an optical disk, etc. More generally, any storage resource may use any technology to store information.

[0130] Further, any storage resource may provide volatile or non-volatile retention of information.

[0131] Further, any storage resource may represent a fixed or removable component of the computer device 802. In one case, when the processing device 804 executes the associated instructions stored in any storage resource or combination of storage resources, the computer device 802 may perform any operation of the associated instructions. The computer device 802 also includes one or more drive systems 808 for interacting with any storage resource, such as a hard disk drive system, an optical disk drive system, etc.

[0132] The computer device 802 may also include an input / output module 810 (I / O) for receiving various inputs (via input devices 812) and for providing various outputs (via output devices 814). A specific output mechanism may include a presentation device 816 and an associated graphical user interface 818 (GUI). In other embodiments, the input / output module 810 (I / O), input device 812, and output device 814 may not be included, and the computer device 802 may be used as a computer device in a network. The computer device 802 may also include one or more network interfaces 820 for exchanging data with other devices via one or more communication links 822. One or more communication buses 824 couple the components described above together.

[0133] The communication link 822 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 822 may include any combination of hardwired links, wireless links, routers, gateway functions, name platform terminals, etc., governed by any protocol or combination of protocols.

[0134] The embodiments of the present specification also provide a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program implements the above method when executed by a processor.

[0135] The embodiments of the present specification also provide a computer-readable instruction, wherein when a processor executes the instruction, the program therein causes the processor to execute the above method.

[0136] It should be understood that in the various embodiments of the present specification, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present specification.

[0137] It should also be understood that in the embodiments of this specification, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in the embodiments of this specification generally indicates that the associated objects before and after are in an "or" relationship.

[0138] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the embodiments of this specification can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of this specification.

[0139] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0140] In the several embodiments provided in the embodiments of this specification, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.

[0141] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of this specification.

[0142] In addition, each functional unit in each embodiment of the present specification can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0143] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of this specification is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a platform terminal, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the embodiment of this specification. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.

[0144] The embodiments of this specification use specific embodiments to illustrate the principles and implementation methods of the embodiments of this specification. The description of the above embodiments is only used to help understand the methods and core ideas of the embodiments of this specification. At the same time, for those skilled in the art, according to the ideas of the embodiments of this specification, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the embodiments of this specification.

Claims

1. A method for constructing multiple linkage visualizations based on a low-code platform, characterized in that: The method comprises, Receive instructions from developers on building data or components in the visual interface of the low-code platform; Acquire initial configuration requirements based on the business requirements of the low-code platform, and set trigger conditions according to the initial configuration requirements; Traversing the associated configurations of data and components, and determining whether the build instruction or the linkage configuration triggers data or component linkage according to the trigger condition; When the data or component triggers the linkage, the linkage is processed according to the initial configuration requirements: If the type of linkage is data linkage, the target data of the data linkage requirement is obtained according to the initial configuration requirement, and the data of the low-code platform is modified according to the target data; If the type of linkage is component linkage, the target component involved in the component linkage is obtained, configuration information is obtained according to the initial configuration requirements, and the low-code platform performs component modification according to the configuration information.

2. The method for constructing multiple linkage visualizations based on a low-code platform according to claim 1, characterized in that: Determining whether the construction instruction triggers data or component linkage further includes: When the construction instruction involves data or components with associated configurations and satisfies the triggering condition, triggering the data or components to be linked; or, When the associated configuration of the data and components triggers a logic conflict or backend data modification, the data or component linkage is triggered.

3. The method for constructing multiple linkage visualizations based on a low-code platform according to claim 1, characterized in that: Judging whether the construction instruction or the linkage configuration triggers data or component linkage according to the trigger condition further includes: If there is no linkage configuration that meets the trigger condition, the construction is terminated.

4. The method for constructing multiple linkage visualizations based on a low-code platform according to claim 1, characterized in that: Judging whether the construction instruction triggers data or component linkage according to the trigger condition and the associated configuration further includes: If the trigger condition is an expression, the expression is sent to an expression parser for parsing to obtain a parsing result, and the parsing result is returned to the low-code platform, and it is determined whether the data or component triggers linkage based on the parsing result.

5. The method for constructing multiple linkage visualizations based on a low-code platform according to claim 1, characterized in that: If the linkage type is component linkage, it further includes: Determine the target component according to the associated configuration of the component and the initial configuration requirement; Traverse and search for the target component in the component tree, and obtain the DOM node of the target component; The component state of the target component is modified according to the DOM node of the target component and the configuration information.

6. The method for constructing multiple linkage visualizations based on a low-code platform according to claim 5, characterized in that: Modifying the component state of the target component further comprises, Obtain the data source configuration corresponding to the DOM node from the data source registration list of the data source center; Parsing the expression involved in the data source configuration to obtain a parsing result, and generating a modification request according to the parsing result; The configuration name in the configuration information is obtained, and the target component is modified according to the modification request and the configuration name.

7. The method for constructing multiple linkage visualizations based on a low-code platform according to claim 1, characterized in that: The component linkage also includes: Bidirectional component linkage, according to the associated configuration of the target component, the configuration information is updated based on the properties and status of the target component, and the low-code platform performs component modification according to the updated configuration information; or, Multi-level component linkage. When the target component contains multiple multi-select and check-select components, the low-code platform modifies the components and then traverses the linkage configuration of the data and components again.

8. The method for constructing multiple linkage visualizations based on a low-code platform according to claim 1, characterized in that: Processing the linkage according to the initial configuration requirements further includes: Dynamic rule linkage: When there are multiple mixed conditions in the association configuration of data and components, the linkage rules are set through dynamic rule linkage.

9. A visual construction device for multiple linkages based on a low-code platform, characterized in that: The device comprises: An instruction receiving unit, used to receive instructions for building data or components from developers in a visual interface of a low-code platform; A trigger condition setting unit, used to obtain initial configuration requirements based on the business requirements of the low-code platform, and set trigger conditions according to the initial configuration requirements; A linkage judgment unit, used for traversing the association configuration of data and components, and judging whether the construction instruction triggers data or component linkage according to the trigger condition and the association configuration; A linkage processing module is used to process the linkage according to the initial configuration requirements after the data or component triggers the linkage: A data linkage processing unit, configured to, when the linkage type is data linkage, obtain target data of the data linkage requirement according to the initial configuration requirement, and modify data of the low-code platform according to the target data; The component linkage processing unit is used to obtain the target component involved in the component linkage when the linkage type is component linkage, obtain configuration information according to the initial configuration requirements, and modify the component on the low-code platform according to the configuration information.

10. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 8 is implemented.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

12. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images