A visual data display system based on a low-code platform

Abstract

The present invention relates to a visual data display system based on a low-code platform, which belongs to the field of application software development technology and solves the problem that the low-code platform in the prior art does not support customized development and has poor cross-application and cross-business data interaction capabilities. The visual data display system includes: a data layer module, an application layer module, and a display layer module. The application layer module obtains data from the data layer module, processes the data using a codeless development method or a mixed development method, and visualizes the processing results in the display layer module, thereby realizing customized development of the low-code platform and data interaction between different applications or businesses.

Description

Technical Field

[0001] The present invention relates to the technical field of application software development, and in particular to a visual data display system based on a low-code platform. Background Art

[0002] The low development efficiency, high technical threshold, and complex maintenance and iteration of traditional application software development platforms have led more and more developers to choose low-code platforms for software development. As an emerging software development method, it provides a visual development environment and prefabricated component libraries, allowing developers to quickly build applications through simple drag and drop, configuration, and other operations, greatly simplifying the development process and improving development efficiency. Especially for rapid prototyping and the development of simple applications, it not only enables professional developers to complete tasks more efficiently, but also allows non-professional developers to participate in the development process, further lowering the technical threshold.

[0003] However, existing low-code development platforms have the following shortcomings: (1) For complex or specific field application development, low-code platforms may not be able to achieve deep customization and high-performance optimization; (2) Existing low-code platforms do not support customized development, and users can only use the components provided by the current platform. In addition, the cost of secondary development is high and cannot meet users' personalized needs for specific application scenarios; (3) Existing low-code platforms have poor data interaction capabilities across applications and businesses. Summary of the invention

[0004] In view of the above analysis, an embodiment of the present invention aims to provide a visual data display system based on a low-code platform to solve the problem that the existing low-code platform does not support customized development and has poor cross-application and cross-business data interaction capabilities.

[0005] The embodiment of the present invention provides a visual data display system based on a low-code platform, the visual data display system comprising: a data layer module, an application layer module, and a display layer module; the data layer module comprises: a database, a cache, a file system, and a third-party data interface; the application layer module comprises: a report engine, a form engine, a process engine, and a portal engine; the application layer module obtains data from the data layer module, processes the data using a codeless development method or a mixed development method, and visually displays the processing results in the display layer module;

[0006] The mixed development method includes: the report engine filters data based on custom rules and generates reports based on the filtered data; the report engine generates customized reports based on third-party interface data; the form engine sets the form display format and execution logic based on custom code; the form engine implements customized component display or third-party form display based on code blocks; the form engine implements customized display or batch operation of form data based on custom buttons; the process engine determines the approver information based on the third-party interface; the portal engine integrates the report engine to implement page custom configuration.

[0007] Based on the further improvement of the above method, the report engine includes a mixed development module and a filter component, and the mixed development module includes a dynamic component and a third-party service, wherein the dynamic component is used to configure visualization resources according to different business needs to generate reports that meet specific business needs, and the third-party service refers to the customized display of third-party data based on the report engine, and the filter component is used to filter data according to user preset conditions to realize customized report display.

[0008] Based on the further improvement of the above method, the form engine includes a mixed development module, which includes a code block, an embedded script and a custom button. The code block refers to a code fragment used to perform specific functions. The specific functions include form data calculation and processing, form data format verification, customized component display or third-party form display. The embedded script is used for display control and execution logic control of the form, and the custom button is used for customized operations on form data.

[0009] Based on the further improvement of the above method, the process engine includes multiple functional nodes, including initiation, end, approver, copy recipient and conditional branch; the portal engine includes multiple basic components, including common functional components, notification and announcement components, to-do components, report and chart components, and report filtering components.

[0010] Based on the further improvement of the above method, the report engine also includes a chart component, the chart component includes a chart type component and a chart style component, the chart type component includes a detailed table, a cross table, a line chart, a pie chart, and a water conservancy professional chart, and the chart style component includes a data style, a chart style, a numerical format, a time format, and a data conversion; the report engine filters data based on custom rules, and generates a report based on the filtered data, including: (1) selecting a report engine, the presentation layer module displays a report management menu, and the content displayed in the report management menu includes a chart component, a mixed development module, and a filter component; (2) adding a chart component to the presentation layer according to target requirements layer module to create reports; (3) adding dynamic components to the display layer module, and judging whether to introduce internal resources or external links based on business needs. The internal resource introduction requires filling in the file introduction path, and the file introduction path stores the dynamic component code with predefined structure, style and behavior. The external link introduction requires filling in the domain name starting with HTTP or HTTPS, and the domain name stores external API interfaces that perform specific functions or third-party resources that store pictures and fonts; (4) configuring the parameters of each component, including: adding the filter component to the display layer module, setting the filtering conditions according to the target requirements, and sending the filtered data to the specified component.

[0011] Based on the further improvement of the above method, the report engine generates customized reports based on third-party interface data, including: (1) selecting a third-party service in the report management menu, and obtaining target report data based on the third-party data interface; (2) after filling in the server address and interface name, the low-code platform performs a connection test. If the connection is successful, the display layer module displays the currently obtained target report data; (3) selecting a chart component from the chart type component according to business needs, and setting the chart style based on the chart style component. The chart style includes the table font color, alignment, column width and header format; (4) judging whether to add a filter component according to business needs. If added, add the filter component to the display layer module, display the report data field in the filter component, and drag the report data field to the filter field bar of the filter component to complete the filter condition setting; if the filter component is not added, the adjusted report is displayed in the display layer module; if the filter component is added, the report corresponding to the adjustment and filter conditions is displayed.

[0012] Based on the further improvement of the above method, the form engine also includes form controls and form rules, wherein the form controls include form type controls and form style controls, the form type controls include single-line text, multi-line text, single choice, multiple choice, picture, attachment, the form style controls include form style, format verification, field permissions, default value settings, the form rules include field display and hide rules and attribute rules, the field display and hide rules are used to control the display or hiding of the current field according to business needs, and the attribute rules are used to set the read-only, edit, required and error prompt of the field according to business needs; the form engine sets the table based on custom code The single display format and execution logic include: (1) selecting a form engine, the display layer module displays a form management menu, and the content displayed in the form management menu includes form controls, form rules, and mixed development modules; (2) dragging form type controls to the display layer module according to target requirements to create a form, and selecting an embedded script in the form properties, the embedded script includes a front-end Js code and a back-end Java code, the front-end Js code is used for display control and logic judgment control of the front-end form controls, and the back-end Java code is used to implement data calculation logic control between the form controls and the data layer module; (3) realizing form visualization display according to the form embedded script.

[0013] Based on the further improvement of the above method, the form engine realizes customized component display or third-party form display based on code blocks, including: dragging the code block to the display layer module, inserting the code snippet that meets the business needs, the code snippet includes a progress bar that matches the current form display or inserting a third-party tree-style subtable, and setting the display properties of the code block according to business needs to realize customized form display.

[0014] Based on the further improvement of the above method, the form engine realizes customized display or batch operation of form data based on custom buttons, including: the custom buttons include a list operation button and a list top button, the list operation button is used for customized display of field data in the form, and the list top button is used for batch operation of form data; the list operation button is used for customized display of field data in the form, including: filling in the internal resource link in the properties of the list operation button according to business needs, adding a data unique identifier as a parameter, the data unique identifier is used to distinguish different form records, after the configuration is completed, clicking the list operation button can view the record details corresponding to the data unique identifier; the list top button is used for batch operation of form data, including: setting the name of the list top button, selecting batch operation, filling in prompt text, field value, interface value and user-defined logic, the field value is the field in the form targeted by the batch operation, the interface value is the external interface address targeted by the batch operation, selecting the key field in the current form as the interface value according to business needs, and performing batch operation on the checked form records according to the user-defined logic.

[0015] Based on the further improvement of the above method, the process engine obtains the approver information based on the third-party interface, including: the process engine obtains the approver information based on the third-party interface, including: (1) selecting the process engine, determining the form that needs to initiate the process, adding the approver node to the presentation layer module to create the approver node, setting the data source of the approver node to the third-party data interface, and setting the service name, interface name, and custom parameters of the third-party interface, the custom parameters are the input parameters specified by the interface, the input parameters include the node type, role code, organization code, and the fields in the form of the initiated process; (2) the user obtains the approver information based on the custom parameters of the third-party interface, including: filtering and processing the approver information returned by the third-party interface according to the custom parameters.

[0016] Compared with the prior art, the present invention can achieve at least one of the following beneficial effects:

[0017] 1. The present invention proposes a visual data display system based on a low-code platform, which uses a mixed development method based on the low-code platform to expand the functions of the report engine, form engine, process engine and portal engine, including dynamic components and third-party services in the report engine, code blocks and embedded scripts in the form engine, so that the low-code development platform supports user secondary development, can quickly build functions based on business needs, and also realizes user customized development of low-code platform functions, filling the gap between market growth and enterprise IT delivery capabilities, and achieving efficiency improvement and cost reduction through low-code technology while ensuring quality.

[0018] 2. The present invention proposes a visual data display system based on a low-code platform, which can introduce third-party service interfaces through the data layer by expanding the functions of the report engine and the form engine, thereby improving the data interaction capabilities of the low-code platform across applications and businesses.

[0019] 3. The present invention proposes a visual data display system based on a low-code platform, which can shorten the software trial and error time and the overall development time through the low-code platform, and reduce the software development cost.

[0020] In the present invention, the above-mentioned technical solutions can also be combined with each other to achieve more preferred combination solutions. Other features and advantages of the present invention will be described in the subsequent description, and some advantages can become obvious from the description, or can be understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained through the contents particularly pointed out in the description and the drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings are only used for the purpose of illustrating specific embodiments and are not to be considered as limiting the present invention. In the entire drawings, the same reference symbols represent the same components;

[0022] Figure 1 It is a schematic diagram of a visual data display system of a low-code platform in an embodiment;

[0023] Figure 2 It is a schematic diagram of a report engine in an embodiment;

[0024] Figure 3 Schematic diagram of a form engine in an embodiment;

[0025] Figure 4 It is a schematic diagram of a process engine in an embodiment;

[0026] Figure 5 Schematic diagram of the portal engine in the embodiment. DETAILED DESCRIPTION

[0027] The preferred embodiments of the present invention are described in detail below in conjunction with the accompanying drawings, wherein the accompanying drawings constitute a part of this application and are used together with the embodiments of the present invention to illustrate the principles of the present invention, but are not used to limit the scope of the present invention.

[0028] A specific embodiment of the present invention discloses a visual data display system based on a low-code platform, wherein the visual data display system includes: a data layer module, an application layer module, and a display layer module; the data layer module includes: a database, a cache, a file system, and a third-party data interface; the application layer module includes: a report engine, a form engine, a process engine, and a portal engine; the application layer module obtains data from the data layer module, processes the data using a codeless development method or a mixed development method, and visually displays the processing results in the display layer module; the mixed development method includes: the report engine filters data based on custom rules and generates reports based on the filtered data; the report engine generates customized reports based on third-party interface data; the form engine sets the form display format and execution logic based on custom code; the form engine implements customized component display or third-party form display based on code blocks; the form engine implements customized display or batch operation of form data based on custom buttons; the process engine determines the approver information based on the third-party interface; and the portal engine integrates the report engine to implement page custom configuration.

[0029] Specifically, see Figure 1 , which gives a schematic diagram of the visual data display system of the low-code platform, which is implemented based on the microservice architecture. The visual data display system includes: data layer module, application layer module, support service module, platform service module, gateway service module, and load balancing module; the application layer module includes: login service, message notification service, and file service; the support service module includes: configuration center, registration center, circuit breaker and current limit, log, and monitoring alarm; the platform service module includes: distributed task scheduling center, service orchestration, message queue, and heterogeneous database synchronization; the gateway service module includes: using SpringCloudAliba.ba-Gateway as the access point for all API interface service requests; the load balancing module includes: using Nginx for load balancing and reverse proxy.

[0030] The report engine includes a chart component, a mixed development module and a filter component, such as Figure 2As shown, the chart component includes a chart type component and a chart style component, and the chart type component includes a detailed table, a cross table, a line chart, a pie chart, and a water conservancy professional chart; the chart style component includes a data style, a chart style, a numerical format, a time format, and a data conversion; the mixed development module includes a dynamic component and a third-party service, wherein the dynamic component is used to configure visualization resources according to different business needs to generate reports that meet specific business needs, and the third-party service refers to the customized display of third-party data based on the report engine, and the filter component is used to filter data according to user preset conditions to realize customized report display. Preferably, the report engine can realize data query, data aggregation, data statistics, data formatting module, data conversion, data encapsulation and data export; the report engine supports water conservancy scene chart configuration and water conservancy process line configuration, including: water level flow process line, water level storage capacity relationship curve, rain and flood map, real-time forecast superimposed rainfall process map, etc.

[0031] The form engine includes form controls, form rule controls and mixed development modules, such as Figure 3 As shown. The form control includes a form type control and a form style control. The form type control includes the form control including single-line text, multi-line files, numbers, text descriptions, dates, date ranges, single choices, multiple choices, dictionaries, pictures, attachments, automatic numbering, text combinations, regions, political regions, rich text, calculation formulas, ext fields, dividing lines, organizations, users, subtables, and associated fields. The form style control includes form style, format verification, field permissions, and default value settings. The form rules include field display and hide rules and attribute rules. The field display and hide rules are used to control the display or hiding of the current field according to business requirements. The attribute rules are used to set the field to read-only, edit, required, and error prompts according to business requirements. The mixed development module includes code blocks, embedded scripts, and custom buttons. The code blocks refer to code snippets used to perform specific functions. The specific functions include form data calculation processing, form data format verification, customized component display, or third-party form display. The embedded scripts are used for form display control and execution logic control. The custom buttons are used for customized operations on form data. Preferably, the form engine can realize data entry, form verification, associated data, associated forms, back-end verification, rule verification, custom buttons, front-end scripts, back-end scripts, and mounting processes; the form engine supports creation from blank or based on existing database tables, can customize personalized pages, supports custom button function configuration, including list operations, top button operations, details page operations, and supports standard form operations, including adding, editing, and deleting.

[0032] For form controls, single-line text controls allow users to enter a line of text; multi-line text controls allow users to enter multiple lines of text; number controls allow users to enter numbers, such as quantity, water level, water storage capacity, etc., and can set decimal place limits, display formats, unit suffixes, etc.; text description controls refer to notes inserted into the form; date controls are used to fill in dates and times, and date range controls are used to display a period of time; radio controls are used to set option content to single selection, and multi-select controls are used to set option content to multiple selections, and multiple options can be set as default values; dictionary controls are used to obtain dictionary content stored in the data layer; picture controls are used to upload pictures, preview pictures, and other content in forms; attachment controls are used to upload files, videos, and other content; automatic numbering controls are used to automatically generate numbers for forms, which can be customized The text combination control allows the user to combine multiple types of text and display it as a combination of multiple text fields. The region control is used to display the region content in the form, and the style of the region display content can be set. The political region control is used to fill in the political region information in the form. The rich text control is used to fill in graphics and text in the form. The calculation formula control is used for numerical calculations in the form. The Ext field control is used in scenarios where some fields do not need to be stored in the database but need to be displayed on the form. The dividing line control divides the page display content to make the page content display clear. The organization control is used to select and fill in the organization information. The user control is used to set the user information. The subtable control is to add an area in the add and edit pages to display the content of the specified field. The associated field control is used to associate with fields in other forms.

[0033] For form-style controls, format validation includes field value uniqueness validation (i.e., the field value cannot be repeated), joint uniqueness validation (i.e., all fields in the form that have been selected for uniqueness validation cannot be repeated), word limit validation, and required field validation; field permissions include visible and editable, which can be set according to business needs; default value settings are used for form linkage, which means that when a form is associated with the content in another published form, the field value in the published form is associated with the current control field value to use it as the default value of the current form control.

[0034] For the form rule control, for example, when filling in project information, different content needs to be displayed according to different project types. For example, when the project type is a public project, information such as the estimated start time, business responsible unit, and delivery responsible unit will not be displayed.

[0035] The form engine implements customized display or batch operation of form data based on custom buttons, including: the custom buttons include a list operation button and a list top button, the list operation button is used for customized display of field data in the form, and the list top button is used for batch operation of form data; the list operation button is used for customized display of field data in the form, including: filling in internal resource links in the properties of the list operation button according to business needs, adding a data unique identifier as a parameter, the data unique identifier is used to distinguish different form records, and after configuration is completed, clicking the list operation button can view the record details corresponding to the data unique identifier; the list top button is used for batch operation of form data, including: setting the name of the list top button, selecting batch operation, filling in prompt text, field value, interface value and user-defined logic, the field value is the field in the form targeted by the batch operation, the interface value is the external interface address targeted by the batch operation, selecting the key field in the current form as the interface value according to business needs, and performing batch operation on the checked form records according to the user-defined logic.

[0036] The process engine includes multiple functional nodes, including initiation, end, approver, copy recipient, and conditional branch, such as Figure 4 As shown, the process engine can realize summary field setting, button authority allocation, automatic approval setting, message queue MQ (Message Queue) information sending, and conditional rule setting. The initiation methods of the process engine include form engine initiation and business function initiation. The process engine is implemented based on the Flowable framework, and can independently configure the release process approval node. By dragging and checking the settings, it can generate workflows that users can use, so as to achieve the purpose of rapid online and process adjustment. Schematically, select the process engine, the display layer module displays the process management menu, and the content displayed in the process management menu includes various functional nodes; establish a process logic structure according to business needs, the logical structure includes an initiator node, an approver node, a cc node, a conditional branch, and an end node, drag the various functional nodes of the process engine to the display layer module according to the logical structure to establish a business process, and configure the parameters of each process node, and deploy the configured business process to achieve online.

[0037] The portal engine includes multiple basic components, including common function components, notification and announcement components, to-do component, report chart component, report filtering component, such as Figure 5As shown, it can be set as a system portal or a personal portal according to actual needs. The portal engine integrates system functions and report components, and provides a system home page page section custom configuration function to meet the user's business processing habits and methods. Position layout can be performed by dragging and dropping. Users can also set the display and hiding of the sections they need or don't need on the front desk, so that the home page can present different faces to different people.

[0038] Exemplarily, the report engine can exchange data with the database, cache, and file system in the data layer module by establishing a data connection, realize data interaction with the external interface by establishing a third-party data interface, and support data cleaning and persistence of external data to the database. The third-party data interface is implemented based on Apache Camel, and data can be docked without hard coding. The data can be directly referenced in the report or saved in the platform database, supporting the cleaning of request results and matching to the field storage in the database to avoid the dilemma of data islands. The form engine can exchange data with the database, cache, and file system in the data layer module by establishing a data connection.

[0039] The codeless development method includes: dragging components in each engine in the application layer module to the presentation layer module, and parameterizing and configuring each component to meet user needs.

[0040] Exemplarily, the report engine filters data based on custom rules, and generates a report based on the filtered data, including: (1) selecting a report engine, the presentation layer module displays a report management menu, and the contents displayed in the report management menu include chart components, mixed development modules, and filter components; (2) adding chart components to the presentation layer module according to target requirements to create a report; (3) adding dynamic components to the presentation layer module, and judging whether to introduce internal resources or external links according to business requirements. The internal resource introduction requires filling in a file introduction path, and the file introduction path stores dynamic component codes with predefined structures, styles, and behaviors. The external link introduction requires filling in a domain name starting with HTTP or HTTPS, and the domain name stores external API interfaces that perform specific functions or third-party resources that store images and fonts; (4) configuring the parameters of each component, including: adding the filter component to the presentation layer module, setting filtering conditions according to target requirements, and sending the filtered data to the specified component.

[0041] If the components in the selected report engine do not require custom rules to filter data, you can set the component values ​​to fixed values ​​based on business needs.

[0042] The report engine generates customized reports based on third-party interface data, including: (1) selecting a third-party service in the report management menu, and obtaining target report data based on the third-party data interface; (2) after filling in the server address and interface name, the low-code platform performs a connection test. If the connection is successful, the display layer module displays the currently obtained target report data; (3) selecting a chart component from the chart type component based on business needs, and setting the chart style based on the chart style component. The chart style includes the table font color, alignment, column width and header format; (4) determining whether to add a filter component based on business needs. If added, add the filter component to the display layer module, display the report data field in the filter component, and drag the report data field to the filter field bar of the filter component to complete the filter condition setting; if the filter component is not added, the adjusted report is displayed in the display layer module; if the filter component is added, the report corresponding to the adjustment and filter conditions is displayed.

[0043] The form engine sets the form display format and execution logic based on the custom code, including: (1) selecting the form engine, the presentation layer module displays the form management menu, and the content displayed in the form management menu includes form controls, form rules and mixed development modules; (2) dragging the form type control to the presentation layer module according to the target requirements to create a form, and selecting the embedded script in the form properties, the embedded script includes the front-end Js code and the back-end Java code, the front-end Js code is used for the display control and logic judgment control of the front-end form control, and the back-end Java code is used to realize the data calculation logic control between the form control and the data layer module; (3) realizing the visual display of the form according to the form embedded script.

[0044] The form engine implements customized component display or third-party form display based on code blocks, including: dragging code blocks to the display layer module, inserting code snippets that meet business needs, the code snippets include a progress bar that matches the current form display or inserting a third-party tree-style subtable, and setting the display properties of the code block according to business needs to achieve customized form display.

[0045] The custom buttons include a list operation button, a new / edit page button, and a list top button. The functions of the list operation button include specifying fields, secondary confirmation, and popping up a custom interface. Exemplarily, the specified field is that after clicking the current list operation button, the current form only displays the content of the user-specified field. The user can achieve this by setting the "specified field" attribute of the list operation button. For complex forms, the specified field allows the user to display the content of each specified field in the current form without dragging the form slider, and quickly complete the filling of the specified field data in the form. Preferably, the user wants to fill in the data in the remark field in the current form, and the current form has a total of 40 fields, and the remark field is located in the last row. Each time the user fills in the remark data, he needs to drag the slider to the end to locate the remark field. Therefore, the process of filling in multiple form data is too cumbersome. In this case, the user can set the "specified field" attribute of the list operation button to remark, and after clicking the specified button, he can quickly locate the remark field.

[0046] The secondary confirmation is that after the user clicks the list operation button, a pop-up window appears in the current form interface, and the displayed content includes the content filled in by the system designer in the "prompt text" attribute of the list operation button and the confirmation and cancel buttons. The user can implement the predefined execution logic by clicking the confirmation and cancel buttons. Preferably, the content filled in by the system designer in the "prompt text" attribute of the list operation button is "Are you sure you want to deactivate the current plan? After deactivation, unstarted tasks will no longer be executed", and after the user selects the confirmation button, the system deactivates the current plan according to the predefined logic.

[0047] The pop-up custom interface is suitable for situations where the form content layout and style are relatively complex and require secondary development. The form content page is customized and developed. Users can fill in internal resource links, external resource links, and form links in the properties of the list operation button to enable the user to display the referenced resources after clicking the custom button. For example, the list operation button pops up a custom page to select internal resources, write the resource path, and add a data unique identifier as a parameter. The data unique identifier is used to distinguish different form records, so that the data details can be viewed by clicking the view button of the data.

[0048] The Add / Edit Page button is executed by the system user through the logic defined by the system user to realize the interface display of the business requirements. For example, when the user completes the adjustment of the text and image style of the announcement and wants to preview the edited content, the system user uses the Add / Edit Page button to set a preview button on the announcement adding and editing page based on this business requirement. When the user clicks the preview button, the system can display the adjusted announcement content on the current interface.

[0049] For the button at the top of the list, batch operation of form data and pop-up custom interface can be realized. Specifically, for batch operation, the user can set the name, "prompt text" attribute and execution logic of the button at the top of the list. The name can reflect the function of the button at the top of the list. The execution logic is based on the confirmation and cancel buttons. The execution logic can be realized by setting field values ​​and setting interface values ​​in combination with the user's custom logic. The field value can be all the field names of the current form. The interface value can be filled in the external interface link and the field name in the form corresponding to the external interface link as needed. Exemplarily, the current form is a user water supply form, and the fields included in the form include area, household name, household number, water meter type, water meter number, charging mode, amount, arrears, arrears days, etc. The current business demand is to stop the water supply for households with arrears of more than 30 days. In this case, based on the setting field value of the button at the top of the list, the field name "arrears days" is passed to the button at the top of the list, and the logic code of "stopping the water supply for households with arrears of more than 30 days" is written. When the user clicks the confirmation button, the corresponding water supply operation can be realized. In the water meter valve control form, add a button at the top of the list, set its name attribute to "Batch Valve Opening", select batch operation, set the prompt text attribute, set its field value to: Update the value of the valve status field in the form to open, set the interface value to the batch valve opening interface url, and use the primary key recorded in the water meter valve control form as the parameter of the incoming interface. In the water meter valve control function, you can check the list data and click the batch valve opening button to realize batch valve opening of IoT water meters. The way to realize the pop-up custom interface of the top button of the list is the same as the pop-up custom interface of the list operation button.

[0050] The process engine obtains the approver information based on the third-party interface, including: the process engine obtains the approver information based on the third-party interface, including: (1) selecting the process engine, determining the form that needs to initiate the process, adding the approver node to the presentation layer module to create the approver node, setting the data source of the approver node to the third-party data interface, and setting the service name, interface name, and custom parameters of the third-party interface, the custom parameters are the input parameters specified by the interface, the input parameters include the node type, role code, organization code, and fields in the form for initiating the process; (2) the user obtains the approver information based on the custom parameters of the third-party interface, including: filtering and processing the approver information returned by the third-party interface according to the custom parameters.

[0051] The node types include approver node types and copy recipient node types; the role code is a code corresponding to the role name, for example, the role code of the inspection staff is inspectionUser, and the role code of the maintenance staff is repairUser. The role code and organization code can be set according to business needs.

[0052] The portal engine integrates the report engine to implement page customization configuration, including: selecting a system portal or a personal portal according to business requirements, then dragging portal engine components according to requirements, setting properties for each component, and formatting to obtain a portal interface.

[0053] Compared with the prior art, the present embodiment provides a visual data display system based on a low-code platform, which adopts a mixed development approach to expand the functions of the report engine and form engine, including dynamic components and third-party services in the report engine, code blocks and embedded scripts in the form engine, so that the low-code development platform supports user secondary development, can quickly build functions based on business needs, and realizes customized development of low-code platform functions by users, filling the gap between market growth and enterprise IT delivery capabilities, and achieving efficiency improvement and cost reduction through low-code technology while ensuring quality. By expanding the functions of the report engine and form engine, the two can introduce third-party service interfaces through the data layer, improving the data interaction capabilities of the low-code platform across applications and businesses, and ultimately shortening the software trial and error time and overall development time through the low-code platform, reducing software development costs.

[0054] Those skilled in the art will appreciate that all or part of the processes of the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, wherein the computer-readable storage medium is a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0055] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by any technician familiar with the technical field within the technical scope disclosed by the present invention should be covered within the protection scope of the present invention.

Claims

1. A visual data display system based on a low-code platform, characterized in that: The visual data display system includes: a data layer module, an application layer module, and a display layer module; the data layer module includes: a database, a cache, a file system, and a third-party data interface; the application layer module includes: a report engine, a form engine, a process engine, and a portal engine; the application layer module obtains data from the data layer module, processes the data using a codeless development method or a mixed development method, and visualizes the processing results in the display layer module; The mixed development method includes: the report engine filters data based on custom rules and generates reports based on the filtered data; the report engine generates customized reports based on third-party interface data; the form engine sets the form display format and execution logic based on custom code; the form engine implements customized component display or third-party form display based on code blocks; the form engine implements customized display or batch operation of form data based on custom buttons; the process engine determines approver information based on a third-party interface; the portal engine integrates the report engine to implement page custom configuration; The report engine includes a mixed development module and a filter component. The mixed development module includes a dynamic component and a third-party service. The dynamic component is used to configure visualization resources according to different business needs to generate reports that meet specific business needs. The third-party service refers to the customized display of third-party data based on the report engine. The filter component is used to filter data according to user preset conditions to realize customized display of reports. The form engine includes a mixed development module, which includes code blocks, embedded scripts and custom buttons. The code blocks refer to code snippets used to perform specific functions, and the specific functions include form data calculation and processing, form data format verification, customized component display or third-party form display. The embedded scripts are used for form display control and execution logic control, and the custom buttons are used for customized operations on form data.

2. According to claim 1, a visual data display system based on a low-code platform is characterized in that: The process engine includes multiple functional nodes, including initiation, end, approver, copy recipient and conditional branch; the portal engine includes multiple basic components, including common function components, notification and announcement components, to-do components, report chart components and report filtering components.

3. According to claim 2, a visual data display system based on a low-code platform is characterized in that: The report engine also includes a chart component, which includes a chart type component and a chart style component. The chart type component includes a detailed table, a cross table, a line chart, a pie chart, and a water conservancy professional chart. The chart style component includes a data style, a chart style, a numerical format, a time format, and a data conversion. The report engine filters data based on custom rules, and generates reports based on the filtered data, including: (1) selecting a report engine, the presentation layer module displays a report management menu, and the contents displayed in the report management menu include chart components, mixed development modules, and filter components; (2) adding chart components to the presentation layer module according to target requirements to create reports; (3) adding dynamic components to the presentation layer module, and judging whether to introduce internal resources or external links according to business requirements. The internal resource introduction requires filling in a file introduction path, and the file introduction path stores dynamic component codes with predefined structures, styles, and behaviors. The external link introduction requires filling in a domain name starting with HTTP or HTTPS, and the domain name stores external API interfaces that perform specific functions or third-party resources that store images and fonts; (4) configuring parameters of each component, including: adding the filter component to the presentation layer module, setting filtering conditions according to target requirements, and sending the filtered data to the specified component.

4. According to claim 3, a visual data display system based on a low-code platform is characterized in that: The report engine generates customized reports based on third-party interface data, including: (1) selecting a third-party service in the report management menu, and obtaining target report data based on the third-party data interface; (2) after filling in the server address and interface name, the low-code platform performs a connection test. If the connection is successful, the display layer module displays the currently obtained target report data; (3) selecting a chart component from the chart type component based on business needs, and setting the chart style based on the chart style component. The chart style includes the table font color, alignment, column width and header format; (4) determining whether to add a filter component based on business needs. If added, add the filter component to the display layer module, display the report data field in the filter component, and drag the report data field to the filter field bar of the filter component to complete the filter condition setting; if the filter component is not added, the adjusted report is displayed in the display layer module; if the filter component is added, the report corresponding to the adjustment and filter conditions is displayed.

5. A visual data display system based on a low-code platform according to claim 4, characterized in that: The form engine also includes form controls and form rules, wherein the form controls include form type controls and form style controls, the form type controls include single-line text, multi-line text, single choice, multi-choice, picture, and attachment, the form style controls include form style, format verification, field permissions, and default value settings, the form rules include field display and hide rules and attribute rules, the field display and hide rules are used to control the display or hiding of the current field according to business requirements, and the attribute rules are used to set the read-only, edit, required, and error prompt of the field according to business requirements; The form engine sets the form display format and execution logic based on the custom code, including: (1) selecting the form engine, the presentation layer module displays the form management menu, and the content displayed in the form management menu includes form controls, form rules and mixed development modules; (2) dragging the form type control to the presentation layer module according to the target requirements to create a form, and selecting the embedded script in the form properties, the embedded script includes the front-end Js code and the back-end Java code, the front-end Js code is used for the display control and logic judgment control of the front-end form control, and the back-end Java code is used to realize the data calculation logic control between the form control and the data layer module; (3) realizing the visual display of the form according to the form embedded script.

6. A visual data display system based on a low-code platform according to claim 5, characterized in that: The form engine implements customized component display or third-party form display based on code blocks, including: dragging code blocks to the display layer module, inserting code snippets that meet business needs, the code snippets include a progress bar that matches the current form display or inserting a third-party tree-style subtable, and setting the display properties of the code block according to business needs to achieve customized form display.

7. A visual data display system based on a low-code platform according to claim 6, characterized in that: The form engine implements customized display or batch operation of form data based on custom buttons, including: the custom buttons include a list operation button and a list top button, the list operation button is used for customized display of field data in the form, and the list top button is used for batch operation of form data; The list operation button is used for customized display of field data in the form, including: filling in the internal resource link in the properties of the list operation button according to business needs, adding the data unique identifier as a parameter, the data unique identifier is used to distinguish different form records, and after the configuration is completed, clicking the list operation button can view the record details corresponding to the data unique identifier; The button at the top of the list is used for batch operations on form data, including: setting the name of the button at the top of the list, selecting batch operations, filling in prompt text, field values, interface values ​​and user-defined logic, the field values ​​are the fields in the form targeted by the batch operations, the interface values ​​are the external interface addresses targeted by the batch operations, and the key fields in the current form are selected as interface values ​​according to business requirements, and batch operations are performed on the selected form records according to the user-defined logic.

8. A visual data display system based on a low-code platform according to claim 7, characterized in that: The process engine obtains the approver information based on the third-party interface, including: (1) selecting the process engine, determining the form that needs to initiate the process, adding the approver node to the presentation layer module to create the approver node, setting the data source of the approver node to the third-party data interface, and setting the service name, interface name, and custom parameters of the third-party interface. The custom parameters are input parameters specified by the interface, and the input parameters include node type, role code, organization code, and fields in the form for initiating the process; (2) the user obtains the approver information based on the custom parameters of the third-party interface, including: filtering and processing the approver information returned by the third-party interface according to the custom parameters.

Images