Zero-code report generation method and system based on low-code platform metadata driving

Abstract

The invention relates to a zero-code report generation method and system based on low-code platform metadata driving, and belongs to the technical field of low-code development. The system comprises a visual configuration module, a metadata driving engine, a report generation and execution module and a task scheduling and pushing module which are mutually connected and cooperated. The method comprises the following steps: loading platform metadata and an associated data model thereof, and customizing a report configuration scheme by a user; packaging the report configuration scheme into an independent and reusable service function component; configuring a trigger mode for the report; and the driving engine analyzes the configuration scheme, converts the rule into an executable data query statement, and generates a report file. According to the method, the dependence of report demands on development resources is reduced, and the data operation efficiency and service agility of organizations are greatly improved.

Description

TECHNICAL FIELD

[0001] The application relates to a low-code platform metadata-driven zero-code report generation method and system, and belongs to the technical field of low-code development. BACKGROUND

[0002] In the wave of enterprise digital transformation, the demand of business departments for real-time, diversity and flexibility of data reports shows explosive growth, and high-quality and efficient data supply capacity has become the core competitive advantage of software products. However, the traditional report development mode is still highly dependent on professional developers to manually write SQL queries, business logic and front-end rendering components. This development method has inherent structural defects, which not only cannot effectively respond to rapidly changing business needs, but also becomes a major bottleneck restricting the business agility of enterprises. In essence, the existing technical solutions cannot overcome the physical contradiction between the high adaptability of business environment and the efficiency of system development and change.

[0003] The existing technical solutions mainly exist in the following two forms and their disadvantages: First, the pure code development mode. In this mode, all report requirements need to go through the complete process of demand review, front-end and back-end development joint debugging, testing and online. This not only leads to low development efficiency and difficulty in responding to business changes, but also causes a large amount of development resources to be occupied by repetitive work, with high opportunity cost. In addition, the report logic is deeply coupled with the business system in the form of hard coding, and subtle changes may introduce system risks, making maintenance and iteration complex and lengthy.

[0004] Second, there are obvious limitations in integrating external report tools: this kind of solution reveals another deep-seated problem - system "coordination failure": open source solutions have poor expandability and insufficient support, and commercial products have high cost and still need to be coded and configured. This kind of tool is independent of the low-code platform and cannot effectively utilize its metadata and permission system, making it difficult for business users to operate with zero code. It is isolated from the main system in terms of security and experience, leading to a split between the main business system in terms of data consistency, security and experience, forming a new data island.

[0005] The skilled in the art has long been committed to solving the following core contradiction: how to ensure system stability, data security and development efficiency while giving business users high flexibility and autonomy, so that they can quickly generate and export their highly customized business report data in a zero-code way. SUMMARY

[0006] In order to solve the above problems, the application discloses a low-code platform metadata-driven zero-code report generation method and system, and the specific technical solutions are as follows: A zero-code report generation system based on low-code platform metadata driving, comprising: a visual configuration module: for providing a zero-code visual interface, receiving and persistently storing business user configured report rules; the report rules include business field selection of data objects and their associated objects, calculation field definition, data filtering conditions and output format style settings to form a report configuration scheme; a metadata driven engine: for receiving and parsing the report configuration scheme, generating data query and report generation executable instructions by calling the parsing metadata service and unified permission service provided by the low-code platform; a report generation execution module: for executing the executable instructions, querying data and filling the result data into a dynamic template according to the format style and display elements in the report configuration scheme to generate a final report file; a task scheduling and pushing module: for providing timing task configuration and email pushing management functions, and triggering the metadata driven engine to execute report file generation and distribution tasks based on timing task configuration.

[0007] Further, the visual configuration module, metadata driven engine, report generation execution module and task scheduling and pushing module are integrated with the metadata service, unified permission service, data source / database, timing task and email service of the low-code platform, and cooperate to complete the configuration, generation and distribution of the report, and the mutual connection relationship is as follows: the output end of the visual configuration module is connected with the input end of the metadata driven engine, for transmitting the report configuration scheme generated by the user to the metadata driven engine for parsing; the metadata driven engine is bidirectionally connected with the visual configuration module, the report generation execution module and the task scheduling and pushing module, for receiving instructions and issuing tasks, at the same time, the metadata driven engine interacts with the metadata service and unified permission service of the low-code platform by calling the standard service interface provided by the low-code platform to obtain metadata definition and execute data permission verification; the input end of the report generation execution module is controlled by the metadata driven engine, receiving the data query and report rendering instructions generated by the metadata driven engine; the output end of the report generation execution module is connected with the data source / database, executing query and obtaining data, and finally generating a report file; the output end of the task scheduling and pushing module is connected with the input end of the metadata driven engine, for automatically triggering the report generation process based on timing configuration; the function calling end of the task scheduling and pushing module is connected with the email service, for controlling the email service to push the generated report file to the specified mailbox list.

[0008] Further, the visualization configuration module is specifically configured to: generate a list of business fields available for user selection by dynamically loading metadata of the low-code platform and its associated data model; and receive a definition of a calculation field combined by an arithmetic operator or a predefined mathematical function based on selected fields from the user.

[0009] Further, the metadata-driven engine is configured to: parse data objects, associated objects, business fields, calculation field rules, and output format templates defined in the report configuration scheme; and dynamically generate executable data query instructions and report rendering instructions based on the parsing results and in combination with context parameters automatically captured from the business page.

[0010] A zero-code report generation method based on the above-mentioned zero-code report generation system driven by metadata of a low-code platform, comprising the following steps: Step 1: Configuration definition: business users select and define data objects and metadata of a low-code platform in a zero-code manner through a visualization configuration interface, configure data filtering rules, output format styles, and calculation fields, and form a report configuration scheme; Step 2: Component encapsulation, encapsulating the report configuration scheme into an independent and reusable business function component; Step 3: Business integration: integrating the business function component into a target business page through a drag-and-drop operation, and configuring the binding relationship between the business function component and the page context data; Step 4: Trigger execution: triggering the report generation process in response to user interaction operations on the business function component or scheduling operations of preset tasks; Step 5: Analysis and verification: the metadata-driven engine analyzes the report configuration scheme and automatically calls the unified permission service of the low-code platform to perform data access permission verification; Step 6: Generate query results: convert the verified configuration rules into executable query statements for the target database, execute the query, and fill the result data into the dynamic template to generate the final report file; Step 7: Output and distribution: providing online download of the final report file generated in step 6 through the front-end interface or automatically pushing it to the specified mailbox through the mail service.

[0011] Further, the business function component in step 2 can be dragged to any business page of the low-code platform; the data query range of the business function component is bound to the page context data through configuration, and the output format is associated with the pre-defined configuration template; the binding and association relationship serves as a dynamic property of the business function component, which is captured and parsed by the metadata-driven engine.

[0012] Further, the step 2 is followed by the step of: performing independent access permission control and operation authorization management on the encapsulated service function component, to control the access and operation permissions of different role users to the component.

[0013] Further, the scheduling operation of the preset time task in the step 4 specifically includes: receiving a scheduling period, a start time and a mail pushing list configured by a user, and automatically triggering a report generation and distribution process according to the plan.

[0014] Further, the data access permission verification in the step 5 specifically includes: calling a unified permission service API of the low-code platform, and dynamically applying row-level data permission rules and column-level data permission rules to the executable query statement based on identity information of a currently logged-in user, to realize data granularity security control.

[0015] Further, the dynamic template in the step 6 is a report template file supporting format, style and layout predefinition; and the generation of the final report file includes filling the result data into the template file and rendering into a file in a specified format. The specified format includes Excel, PDF and / or Word document formats. The format, style and layout of the dynamic template are consistent with the settings of the user in the report configuration scheme.

[0016] The working principle of the application is: From the perspective of the invention problem solving theory (TRIZ), the application is to solve the physical contradiction between “high adaptability requirement of business environment” and “system development and change efficiency”. Specifically, the system needs to have high flexibility and adaptability (TRIZ general engineering parameter #35, adaptability) to respond to the rapid change of business report requirements, and at the same time, it must maintain high development efficiency and low complexity (TRIZ general engineering parameters #39, production rate; #36, complexity of the system). The traditional technical solution cannot break this contradiction, and often loses one to gain the other.

[0017] The application successfully solves the above-mentioned contradiction by applying a plurality of TRIZ invention principles. Application of segmentation principle (#1): The complex report development process is divided into configuration, encapsulation, integration, execution and other independent modules.

[0018] Application of pre-action principle (#10): The pre-defined metadata model, association relationship and permission rule are prepared for the subsequent zero-code configuration.

[0019] Application of dynamic principle (#15): Through dynamic loading of metadata, dynamic binding of context parameters and dynamic generation of SQL instructions, the system can adapt to changes.

[0020] Apply self-service principle (#25): empower business users to complete the whole process of report development without the intervention of developers.

[0021] Apply composite material principle (#40): composite the native services (metadata, permissions) of the low-code platform with the innovative report generation engine into a collaborative whole system.

[0022] The beneficial effects of the present application are: 1. Zero-code self-service for business users: through the visual configuration interface and metadata-driven mechanism, business personnel can independently complete the whole process of report development from data selection, calculation, filtering to style design without writing any code, and can directly preview after configuration, improving user experience and configuration efficiency, completely liberating developers from tedious report requirements, and greatly improving the response speed to business data.

[0023] 2. Improve the efficiency of report development: change the development and change of report function from the "heavy" process of coding, testing and publishing to the "light" operation of visual configuration, respond to business needs in minutes, significantly shorten the development cycle and reduce the development cost.

[0024] 3. Ensure enterprise-level data security: through deep integration with the unified permission service system of the low-code platform, automatically perform data permission verification during report generation, ensure that business users can only access and operate data within their permission scope, effectively protect the security of core data assets.

[0025] 4. Provide flexible and diverse data service mode: support instant trigger generation and periodic automatic push, which can meet the user's temporary data export needs and provide periodic data report services for managers, enhancing the availability and timeliness of data.

[0026] 5. Eliminate information silos and achieve seamless integration: by encapsulating the report function as a drag-and-drop business component, it can be seamlessly integrated with other business functions in the platform, ensuring data consistency, security and user experience, and avoiding the ecological fragmentation problem caused by introducing external tools.

[0027] 6. Follow the law of evolution of technical system, indicate the evolution direction of the solution: The invention is fundamentally to evolve the report generation subsystem from a static module that needs external intervention into an intelligent unit with high dynamic and controllability. Through metadata driving, context awareness and component encapsulation, the system can self-configure and self-adapt to the changing business context, which conforms to the evolution trend of TRIZ technical system to "increase dynamic and controllability", and provides a universal design paradigm for solving such "flexibility-efficiency" contradiction.

[0028] In summary, the present invention does not sacrifice system stability, data security and development efficiency, breaks the absolute dependence of report development on professional developers, gives business users high flexibility and autonomy, enables them to create, integrate and distribute highly customized complex data business reports in a truly zero-code way, and fundamentally improves the data operation agility of enterprises. BRIEF DESCRIPTION OF DRAWINGS

[0029] Figure 1 is the schematic diagram of the system of the present invention; Figure 2 is the flow chart of the data generation method of the present invention; Figure 3 is the schematic diagram of the visual configuration interface of the present invention; Figure 4 is the schematic diagram of the integration effect of the business function component of the present invention in the business page. DETAILED DESCRIPTION

[0030] The present invention will be further illustrated below in conjunction with the drawings and specific embodiments. It should be understood that the following specific embodiments are only used to illustrate the present invention and not to limit the scope of the present invention.

[0031] In conjunction with the drawings Figure 1 It can be seen that the system of the present invention includes a visual configuration module, a metadata driving engine, a report generation and execution module, and a task scheduling and pushing module. The system is deeply integrated with the metadata service, unified permission service, data source / database, timing task and mail service of the low-code platform, and cooperates to complete the configuration, generation and distribution of the report. The system forms an automatic closed-loop process from configuration, analysis, execution to distribution through the following connection relationship. The modules of the system are connected as follows: Connection 1: The visual configuration module, as the user configuration entrance, is connected to the input end of the metadata driving engine through the output end, for transmitting the report configuration scheme generated by the user to the engine for analysis; Connection 2: The metadata-driven engine, as the control center and intelligent core of the system, is bidirectionally connected with the visualization configuration module, the report generation and execution module, and the task scheduling and pushing module, for receiving instructions and issuing tasks. Meanwhile, the engine interacts with the metadata service and unified permission service of the platform through the standard service interface provided by the low-code platform, to obtain metadata definition and perform data permission verification; Connection 3: The report generation and execution module, whose input end is controlled by the metadata-driven engine, receives data query and report rendering instructions generated by the engine; and its output end is connected with the data source / database, to execute query and obtain data, and finally generate a report file; Connection 4: The task scheduling and pushing module, whose output end is connected with the input end of the metadata-driven engine, is used to automatically trigger the report generation process based on timing configuration; and its function calling end is connected with the mail service, for controlling the mail service to push the generated report file to the specified mailbox list.

[0032] The following will be described in combination with the accompanying drawings Figure 2 The method for generating a report data is constructed, and the specific application implementation of a workshop material consumption report in the equipment operation and maintenance industry is taken as a case for description, and the specific process is as follows: Step 1.1: Configuration definition, the user performs the following zero-code configuration in the interface of the visualization configuration module: 1) Select the material receiving related data objects: sequentially select “material receiving single (MATR)”, “material receiving detail line (MATRLINE)”, “material account (ITEM)”, and “inventory transaction (INVTRANS)”. The association relationship among the above objects has been predefined in the platform data model, and the user does not need to manually configure, and the system automatically identifies.

[0033] 2) Select the business fields: select “work order number”, “demand department”, “material code”, “material name”, “material specification and model”, “actual receiving amount”, “unit price”, “amount”, and the like from the above objects.

[0034] 3) Define the calculation field: define a summary calculation field through the built-in formula editor and function list combination: period consumption summary amount = SUM(amount). This formula is used to calculate the total cost of all receiving materials in the selected period.

[0035] 4) Set the filter condition: set to “material receiving date = [system date-1]”, to accurately filter out all material receiving records of the previous day. This condition is transmitted as the default parameter value of the report, and modification is supported during preview, to meet the flexible use requirements of the user for the condition parameter value.

[0036] 5) Set condition output style: Configure condition format rule: When the "unit price" value is greater than 2000, the background color of the data row is automatically marked red, realizing visual warning of high-value materials.

[0037] Step 1.2: Component packaging, after configuration, the system automatically packages the report configuration scheme, calculation logic and output rules into an independent, reusable business function component, and publishes it to the component library of the platform. The business function component (such as named "Workshop Material Consumption Report") can be dragged and integrated into any business page.

[0038] Step 1.3: Business integration, users integrate the business function component packaged in step 1.2 into the specified target business page (such as "Material Consumption Dashboard" page, material requisition page) through drag-and-drop operation. The binding relationship between the configurable component and the page context data, such as the "demand department" drop-down list, is configured to realize dynamic filtering of data by department.

[0039] Step 1.4: Trigger execution, the generation of the report is triggered in the following ways: 1) Manual trigger: The user starts the process when clicking on the component on the business page.

[0040] 2) Automatic trigger: The task scheduling and pushing module automatically triggers the process according to the preset timing task (such as: every day 8:00).

[0041] Step 1.5: Analysis and verification, after the metadata-driven engine is triggered, the following sub-steps are executed: 1) Parse configuration: The engine reads and parses the report configuration scheme, identifies the need to query from "material requisition", "material requisition detail row", "material account", "inventory transaction" four tables, and understands the aggregation calculation logic and condition format rules of the period consumption summary amount.

[0042] 2) Permission verification: Call the unified permission service to dynamically impose the data access permissions of the current user (such as: only able to view the material requisition records of its own department and professional).

[0043] Step 1.6: Query generation, the metadata-driven engine converts the verified configuration rules into SQL query statements executable by the target database; the report generation execution module executes the query statement and fills the query and calculation results into the dynamic template, applies the condition format rules set in step 1.1 (such as: rendering the background color of the "unit price>2000" material row to red), and generates the final report file.

[0044] Step 1.7: Output distribution, the generated report file is provided for online download through the front-end interface or automatically pushed to the specified mailbox list through the mail service (such as: sent to the workshop supervisor, workshop planner).

[0045] Further, in step 1.3 (business integration), the configuration condition default values (such as time range) carried by the business function component can be reconfigured or bound with page dynamic parameters during integration to achieve more accurate context-related queries.

[0046] Further, in step 1.3 (output distribution), the system also provides an online preview mode. Users can adjust query parameters in the preview interface and trigger the system to re-execute steps 1.5 (parse verification) and 1.6 (query generation) to dynamically refresh the results; after confirming the preview results, users can choose to download the final report or push it to a specified mailbox.

[0047] The zero-code operation interface layout provided by the visualization configuration module can be referred to in Figure 3 . As shown in Figure 3 , the interface adopts a functional partition design, and report configuration is completed through a process-based guide, specifically including the following five core areas: Step 2.1 object model selection (basic information area). Users first select the main object (such as "material requisition (MATR)") from all available data objects provided by the platform metadata service in this area; the system automatically loads the sub-objects (such as "material ledger (ITEM)") that have a predefined association relationship with the main object, forming a complete object model tree.

[0048] Step 2.2 field configuration (field configuration area). Users click "Select Columns" to trigger the selection dialog box; the dialog box displays an object tree structure with the main object as the root node and the associated objects as the leaf nodes on the left side, and dynamically displays all available fields of the selected objects on the right side; users can complete the selection of business fields of the main object and associated objects through the check operation; users click "Calculate Fields" to define calculated fields (such as: define "period consumption summary amount = SUM(amount)") through the combination of built-in formula editor and function list; the system verifies the formula syntax in real time. The whole process does not require writing queries or associated codes.

[0049] Step 2.3 condition rule setting (condition rule area). Users select business fields to set data filtering conditions (such as: "material requisition date = [system date - 1]") in this area and complete parameter configuration through form selection and value filling; at the same time, sorting rules and data verification rules can be set.

[0050] Step 2.4: output style configuration (style configuration area). Users can personalize the report output style in this area, including: configuring header names, font styles, color schemes, and other basic styles; in particular, condition format rules can be set (such as: when "unit price">2000, automatically mark the data row background color red).

[0051] Furthermore, the interface toolbar provides a preview function button; after clicking, users can dynamically render and display the final report effect based on the current configuration, realizing a "what you see is what you get" configuration experience, significantly reducing the trial and error cost and understanding threshold of the configuration process.

[0052] The integration effect of the business function components and the business page can be seen in the following reference. Figure 4 ( Figure 4 ). like Figure 4 As shown in the diagram, this schematic diagram specifically illustrates the process of... Figure 3 How can the business function components, after being configured and encapsulated, be seamlessly integrated with other business functions of the low-code platform with zero code to achieve the desired application effect?

[0053] Step 3.1: Component Location and Presentation. The encapsulated business function component (e.g., "Workshop Material Consumption Report") is presented as an interactive UI element (e.g., a button or menu item). This component is added by the user from the platform component library and located on a target business page (e.g., "Material Requisition List Page") via drag-and-drop. After integration, its appearance and interactive behavior remain consistent with the page's native components.

[0054] Step 3.2: Context Parameter Binding. After integration, the dynamic binding relationship between the component and the page context data is configured through a visual properties panel. Users can map specific data or states on the page (such as the "department" filter value in the search area of ​​the list page) to dynamic filtering parameters of the report within the component. This process requires no scripting code.

[0055] Step 3.3: Dynamic Triggering and Execution. After configuration, when a user interacts on the business page (e.g., clicks a component), the report generation process will be triggered. The system will capture the context parameter values ​​of the current page and transmit them as input parameters to the metadata-driven engine. The engine will combine these dynamic parameters with the static configuration scheme encapsulated within the component to generate execution instructions and output a personalized report related to the current business context.

[0056] This integration mechanism eliminates the "data silos" between reporting functions and core business processes, enabling "immersive embedding" of analytical capabilities into business operation scenarios, and improving the immediacy of data extraction and the accuracy of decision-making. This fully demonstrates the beneficial effects of this invention in enhancing business agility and data self-service capabilities.

[0057] As will be understood by one of ordinary skill in the art upon reading the present disclosure, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It will also be understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0058] The above-described embodiments of the application are intended to be illustrative only. Changes can be made by those skilled in the art, without departing from the scope of the present application which is set out in the following claims. The technical scope of the present application is not limited to the contents described in the specification, and must be determined based on the scope of claims.

Claims

1. A zero code report generation system based on low code platform metadata drive, characterized in that, The application relates to a report generation method based on a low-code platform, and comprises the following steps: A visual configuration module is used to provide a zero-code visual interface, receive and persistently store a report rule configured by a business user; The report rule comprises the selection of business fields of a data object and an associated object, the definition of a calculation field, a data filtering condition and the setting of an output format style, so that a report configuration scheme is formed; A metadata-driven engine is used to receive and analyze the report configuration scheme, generate executable instructions for data query and report generation by calling a parsing metadata service and a unified permission service provided by the low-code platform; A report generation execution module is used to execute the executable instructions, query data and fill the result data into a dynamic template according to the format style and display elements in the report configuration scheme, so that a final report file is generated; A task scheduling and pushing module is used to provide a timing task configuration and a mail pushing management function, and trigger the metadata-driven engine to execute a report file generation and distribution task based on the timing task configuration.

2. The zero-code report generation system of claim 1, wherein, The visual configuration module, the metadata-driven engine, the report generation execution module and the task scheduling and pushing module are integrated with a metadata service, a unified permission service, a data source / database, a timing task and a mail service of the low-code platform, and cooperate to complete the configuration, generation and distribution of the report, and the mutual connection relationship is as follows: The output end of the visual configuration module is connected with the input end of the metadata-driven engine, and is used to transmit the report configuration scheme generated by the user to the metadata-driven engine for analysis; The metadata-driven engine is bidirectionally connected with the visual configuration module, the report generation execution module and the task scheduling and pushing module, is used to receive instructions and issue tasks, and interacts with the metadata service and the unified permission service of the low-code platform by calling a standard service interface provided by the low-code platform, so as to obtain metadata definition and execute data permission verification; The input end of the report generation execution module is controlled by the metadata-driven engine, and receives the data query and report rendering instructions generated by the metadata-driven engine; The output end of the report generation execution module is connected with the data source / database, executes query and obtains data, and finally generates a report file; The output end of the task scheduling and pushing module is connected with the input end of the metadata-driven engine, and is used to automatically trigger the report generation process based on timing configuration; The function calling end of the task scheduling and pushing module is connected with the mail service, and is used to control the mail service to push the generated report file to a specified mailbox list.

3. The zero-code report generation system of claim 1, wherein, The visual configuration module is specifically used for dynamically loading metadata and associated data models of the low-code platform, generating a list of business fields that can be selected by the user, and receiving the definition of a calculation field composed of selected fields by means of an arithmetic operator or a pre-defined mathematical function.

4. The zero-code report generation system of claim 1, wherein, The metadata-driven engine is configured to analyze the data object, the associated object, the business field, the calculation field rule and the output format template defined in the report configuration scheme; Based on the analysis result and in combination with context parameters automatically captured from a business page, executable data query instructions and report rendering instructions are dynamically generated.

5. A zero-code report generation method based on the zero-code report generation system based on the metadata of the low-code platform according to any one of claims 1-4, characterized in that, The application further discloses a report generation method based on a low-code platform, and comprises the following steps: Step 1: Configuration definition: business users select and define data objects and metadata of a low-code platform through a visual configuration interface in a zero-code manner, configure data filtering rules, output format styles, and calculation fields, and form a report configuration scheme; Step 2: Component packaging, packaging the report configuration scheme into an independent and reusable business function component; Step 3: Business integration: integrate the business function component into the target business page through drag-and-drop operation, and configure the binding relationship between the business function component and the page context data; Step 4: Trigger execution: in response to the user's interactive operation on the business function component or the scheduling operation of the preset time task, trigger the report generation process; Step 5: Analysis and verification: the metadata-driven engine analyzes the report configuration scheme and automatically calls the unified permission service of the low-code platform to perform data access permission verification; Step 6: Generate query results: convert the verified configuration rules into executable query statements for the target database, execute the query and fill the result data into the dynamic template to generate the final report file; Step 7: Output and distribution: the final report file generated in step 6 is provided for online download through the front-end interface or automatically pushed to the specified mailbox through the mail service.

6. The zero-code report generation method of claim 5, wherein, The business function component in step 2 can be dragged to any business page of the low-code platform; the data query range of the business function component is bound to the page context data through configuration, and the output format is associated with the pre-defined configuration template; the binding and association relationship is the dynamic property of the business function component, which is captured and analyzed by the metadata-driven engine.

7. The zero-code report generation method of claim 5, wherein, After step 2, it further includes the step of performing independent access permission control and operation authorization management on the packaged business function component to control the access and operation permissions of different role users to the component.

8. The zero-code report generation method of claim 5, wherein, The scheduling operation of the preset time task in step 4 specifically includes receiving user-configured scheduling period, start time, and mail push list, and automatically triggering the report generation and distribution process according to the plan.

9. The zero-code report generation method of claim 5, wherein, The data access permission verification in step 5 specifically includes calling the unified permission service API of the low-code platform, based on the identity information of the current logged-in user, dynamically applying row-level data permission rules and column-level data permission rules to the executable query statement to achieve data granularity security control.

10. The zero-code report generation method of claim 5, wherein, The dynamic template in step 6 is a report template file with predefined format, style, and layout; Generating the final report file includes filling the result data into the template file and rendering it into a file in a specified format; The specified format includes Excel, PDF, and / or Word document format; The format, style, and layout of the dynamic template are consistent with the user's settings in the report configuration scheme.

Images