CN118819527A - Data processing method, device, electronic device and medium for zero-code development platform - Google Patents

Abstract

The present invention discloses a data processing method, device, electronic device and medium for a zero-code development platform, which are applied in the field of computer technology. The method includes generating respective index information when a form component and a process component are dragged, and storing the form setting data of a target form component associated with the process component into the process setting data. The process component is run, and the business data input by the user is filled into the corresponding position of the target form component, and the dynamic operation data of the process component is stored at the same time; when it is detected that the statistical chart component of the user interface is dragged, the statistical chart component is associated with the corresponding form component based on the dynamic operation data, and a statistical chart is generated according to the calculation result of the associated form component. The present invention can solve the problem that the related technology cannot realize the construction of a complete application by a zero-code development platform, and can associate the process engine data, the custom form data and the statistical chart data to build a complete business application.

Description

Data processing method, device, electronic device and medium for zero-code development platform

Technical Field

The present invention relates to the field of computer technology, and in particular to a data processing method, device, electronic device and non-volatile storage medium for a zero-code development platform.

Background Art

Low-code platforms support users to quickly build, deploy, run and manage applications in a low-code or zero-code manner. Low-code development platforms include narrow low-code development platforms and zero-code development platforms. Zero-code development platforms refer to development platforms that allow business personnel with zero development experience to quickly build business application systems based on business needs by dragging and dropping an intuitive interface without writing code.

The relevant technologies are all low-code platforms in a narrow sense. For inexperienced business personnel, it is impossible to build a complete business application system by simply dragging and dropping the design. Moreover, it can only display static data and cannot perform dynamic calculations and data updates based on business data.

In view of this, realizing the construction of a business application system based on a zero-code development platform is a technical problem that needs to be solved by technical personnel in this field.

It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present application, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field.

Summary of the invention

The present invention provides a data processing method, device, electronic device and non-volatile storage medium of a zero-code development platform, which realize the construction of a business application system based on the zero-code development platform.

In order to solve the above technical problems, the present invention provides the following technical solutions:

On one hand, the present invention provides a data processing method for a zero-code development platform, comprising:

When it is detected that a form component of the user interface is dragged, form index information is automatically generated for the form component, and form setting data is stored;

When it is detected that the process component of the user interface is dragged, process index information is automatically generated for the process component, and form setting data of the target form component associated with the process component is stored in the process setting data;

Run the process component, and fill the business data input by the user into the corresponding position of the target form component, and store the dynamic operation data during the operation of the process component;

When it is detected that the statistical chart component of the user interface is dragged, the statistical chart component is associated with the corresponding form component based on the dynamic operation data, and a statistical chart is generated according to the calculation result of the associated form component.

In a first exemplary implementation, the form component is a Vue front-end form component, and the automatically generating form index information for the form component and storing form setting data include:

When the drag component is called to complete the dragging of the form component, the unique serial number of the form component is obtained based on Vue's global unique identification number strategy;

According to the unique serial number of the form component, the generation of the form index number of the form component is triggered.

In a second exemplary implementation, the process of storing form setting data includes:

A form data storage structure is pre-built; the form data storage structure is represented as:

Component display name: business instance name, front-end component name: component type, form component icon attributes: preset attributes, value, value type: input data type, business information, form index number: unique serial number of the form component;

The business instance name data, component type data, form component icon attribute data, business attribute data and form index number are obtained from the form component, and the obtained data are filled into the corresponding position of the form data storage structure to obtain form setting data.

In a third exemplary implementation, storing the form setting data of the target form component associated with the process component into the process setting data includes:

A process setting data storage structure is constructed in advance in a nested manner of parent nodes and child nodes; the process setting data storage structure is expressed as:

Parent node: root node index number: unique serial number of process component, parent node name: null, node type of parent node: root node, node name of parent node: initiating node, parent node name: initiating node, description: description data, node attributes of root node; wherein, the node attributes of the root node include form management identifier: form index number of the first target form component: unique serial number of the form component, display name of the first target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type, form index number of the second target form component: unique serial number of the form component, display name of the second target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type;

Subnode: Subnode index number: unique serial number of process component, parent node name: parent node of subnode, node type of subnode: preset node type, node name of subnode: preset node name, name of subnode: preset node name, node attributes of subnode; wherein, the node attributes of subnode include form management identifier: form index number of third target form component: unique serial number of form component, display name of third target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type, custom attribute: attribute value; form index number of fourth target form component: unique serial number of form component, display name of fourth target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type;

When the end mark is detected, the sub-node data contained in the process setting data storage structure has been completely stored; the end mark at least includes an identifier type;

The name, node type, branch setting, sub-node setting and form setting data of each process node and the associated target form component are obtained from the process component, and the obtained data is filled into the corresponding position of the process setting data storage structure to obtain the process setting data.

In a fourth exemplary implementation, the process of acquiring the form setting data of the target form component includes:

Obtaining the form management identifier of the process component and the corresponding form component setting data;

The Vue component is called, each target form component is introduced through the import method, and the form setting data of the corresponding target form component is echoed according to the pre-set form management identification information referenced by the Vue component.

In a fifth exemplary implementation, the storing of dynamic operation data during the operation of the process component includes:

A dynamic operation data storage structure is pre-built based on the key-value format; the dynamic operation data storage structure is represented as:

The form index number of the first target form component: the display name of the first target form component, the form index number of the second target form component: the display name of the second target form component;

The dynamic operation data during the operation of the process component is filled into the corresponding position of the dynamic operation data storage structure to obtain the dynamic operation data.

In a sixth exemplary implementation, the step of associating the statistical chart component with a corresponding form component based on the dynamic operation data, and generating a statistical chart according to a calculation result of the associated form component, includes:

When it is detected that the statistical chart component is dragged, the statistical chart format selection page is displayed in the user interface;

When the statistical chart format is a line chart, the component display names corresponding to the horizontal and vertical axes of the statistical chart to be generated are constructed based on the current business needs;

Based on the component display names corresponding to the horizontal and vertical coordinates of the statistical chart, respectively obtaining the associated form index numbers corresponding to the number of statistical instances of the statistical chart from the process setting data;

Based on the index numbers of the associated forms and the current business requirements, a corresponding number of form data values are obtained from the dynamic operation data, and a statistical chart is generated according to the calculation results.

Another aspect of the present invention provides a data processing device for a zero-code development platform, comprising:

A form data storage module, used to automatically generate form index information for the form component and store form setting data when detecting that the form component of the user interface is dragged;

A process and form data association module, for automatically generating process index information for the process component when detecting that the process component of the user interface is dragged, and storing the form setting data of the target form component associated with the process component into the process setting data;

A dynamic data storage module, used to run the process component, fill the business data input by the user into the corresponding position of the target form component, and store the dynamic operation data during the operation of the process component;

A chart association module, configured to associate the statistical chart component with a corresponding form component based on the dynamic operation data when detecting that the statistical chart component of the user interface is dragged;

The chart generation module is used to generate statistical charts based on the calculation results of the associated form components.

The present invention also provides an electronic device, comprising a processor, wherein the processor is used to implement the steps of the data processing method of the zero-code development platform as described in any of the preceding items when executing a computer program stored in a memory.

Finally, the present invention also provides a non-volatile storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the data processing method of the zero-code development platform as described in any of the preceding items are implemented.

The advantage of the technical solution provided by the present invention is that, in the process of users customizing and building a business application system in a zero-code manner, index information is given to their customized form components and process components when they are created, and the form component settings are integrated into the process node settings, thereby realizing the design integration of forms and processes; the statistical chart component is associated with the corresponding form when it is created, and statistical charts are generated according to the data saved during the operation of the process node, which not only realizes the association of process engine data, custom form data and statistical analysis chart data to form a complete application, forming a basic zero-code application solution, effectively reducing the workload of software developers, but also being more conducive to the use of users with no code capabilities, thereby improving the flexibility and efficiency of building applications; it also realizes the function of dynamic calculation and data update based on business data, thereby further improving the flexibility and efficiency of users building applications and enhancing the user experience.

In addition, the present invention also provides corresponding implementation devices, electronic devices and non-volatile storage media for the data processing method of the zero-code development platform, further making the method more practical, and the devices, electronic devices and non-volatile storage media have corresponding advantages.

The technical features mentioned above, the technical features to be mentioned below, and the technical features shown separately in the drawings can be arbitrarily combined with each other, as long as the combined technical features are not contradictory. All feasible feature combinations are technical contents clearly recorded in this article. Any of the multiple sub-features contained in the same sentence can be applied independently, and does not have to be applied together with other sub-features. It should be understood that the above general description and the detailed description below are only exemplary and cannot limit the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions of the present invention or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

FIG1 is a schematic flow chart of a data processing method of a zero-code development platform provided by the present invention;

FIG2 is a flow chart of another data processing method of a zero-code development platform provided by the present invention;

FIG3 is an exemplary broken line statistical diagram provided by the present invention;

FIG4 is a structural diagram of a specific implementation of a data processing device for a zero-code development platform provided by the present invention;

FIG. 5 is a structural diagram of a specific implementation of an electronic device provided by the present invention.

DETAILED DESCRIPTION

In order to enable those skilled in the art to better understand the technical solution of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific embodiments. Among them, the terms "first", "second", "third", "fourth", etc. in the specification and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations of the two are intended to cover non-exclusive inclusions. The term "exemplary" means "used as an example, embodiment or illustrative". Any embodiment described here as "exemplary" is not necessarily interpreted as being superior or better than other embodiments.

The low-code platform is based on PaaS (Platform as a Service), supports the development, deployment and operation of applications in the cloud, and provides users with basic tools in software development, such as data objects, permission management, user interface, etc. Users can quickly complete the construction, deployment, operation and management of applications directly on the aPaaS (Application Platform as a Service) platform in a low-code or zero-code manner. Among them, low-code development platforms can include narrow low-code development platforms and zero-code development platforms. Narrow low-code development platforms can quickly generate applications with a small amount of code, while zero-code development platforms can quickly generate applications without code.

At present, all related technologies are aimed at the development of business application systems for narrow low-code platforms. For example, one related technology processes input data and obtains output data by obtaining the data processing instance corresponding to the execution node in the canvas. This method can automatically process input data according to the data processing instance corresponding to the execution node by setting the execution node in the canvas without switching the execution platform. Another related technology is a method for implementing a low-code BI (Business Intelligence) demonstration system based on Canvas, including: building a basic environment, starting a low-code BI demonstration system; obtaining BI large screen data and storing it in a database; logging in to the system, configuring the data source, obtaining database connection parameters to connect to the database, until the connection to the database is successfully verified; using the configured data source as the source data, starting to configure the data set, and selecting the corresponding table from all tables in the database as the data set; entering the data source page to configure the dashboard, first creating a new chart pop-up window, selecting the chart type after selecting the data set in the pop-up window, determining the dimensions and indicators of the data in the chart, and forming a complete chart; after completing and saving the dashboard, publishing the dashboard. The related technologies drag and drop the low-code process engine or use AIGC (Artificial Intelligence Generated Content) to automatically generate it, or drag and drop the user interface or drag and drop the layout and data rendering of the visual statistical chart. Since none of them design and display the data structure that associates the process engine data, custom form data, and statistical report data, the related technologies cannot form a complete business application system on the low-code development platform or zero-code development platform. In addition, the implementation method of the low-code BI demonstration system based on Canvas only uses static data display, and cannot perform dynamic calculations and data updates based on business data.

In view of this, the present invention associates the process nodes and form settings by setting index information, and links the zero-code development platform forms, processes, and statistical charts, providing a solution for the implementation of the basic functions of the zero-code development platform. Users can customize a business application system that includes processes, forms, and statistical analysis charts in a zero-code manner. After introducing the technical solution of the present invention, various non-limiting implementation methods of the present invention are described in detail below. In order to better illustrate the present invention, numerous specific details are given in the specific implementation methods below. Those skilled in the art should understand that the present invention can also be implemented without these specific details. In other examples, methods, means, components, and circuits well known to those skilled in the art are not described in detail in order to highlight the subject matter of the present invention.

First, please refer to Figure 1, which is a flow chart of a data processing method of a zero-code development platform provided by this embodiment. Business personnel, IT development and other non-code-based users can quickly build business application systems, which can be achieved through the zero-code development platform provided by the present invention. Users can complete the development, testing and deployment of the system within a few days or even a few hours, and can adjust or update at any time. The zero-code development platform of the present invention includes at least a front-end visual user interface and a back-end service. The back-end service includes a drag-and-drop component library, and provides automation functions, componentized design functions and data modeling functions. Among them, the drag-and-drop component library includes a large number of predefined form components, process components and statistical chart components, such as buttons, forms, images, navigation bars, etc. Automation functions include but are not limited to database integration, user management, and email notifications. Users only need to simply configure these functions, and the system will automatically handle all related operations, thereby greatly reducing the duplication of work and human resource investment in the development process. The componentized design function supports splitting the application into multiple independent and reusable components. Each component has specific functions and properties, and users can configure and customize these components according to their needs to meet their business needs. The data modeling function allows users to define and manage data in applications through a simple graphical interface. These data models can be directly used to generate application code and data structures. Users can intuitively see the various components and functions of the system through a visual user interface. They can directly drag and drop form components, process components, and statistical chart components from the drag-and-drop component library to the user page, and configure these components in combination with business needs and various functions to build the required business application system without writing any code. In the process of users building business application systems through the zero-code development platform, the data processing process of the zero-code development platform may include the following:

S101: When it is detected that a form component of a user interface is dragged, form index information is automatically generated for the form component, and form setting data is stored.

In this embodiment, the zero-code development platform provides a rich variety of input form components, such as text boxes, drop-down boxes, radio buttons, multiple-choice buttons, etc., and supports custom customization components. The form component is a form for users to customize the zero-code development platform form component according to business needs. Drag the form component on the user interface. The zero-code development platform will automatically create an index for each form component and save the form design data. The form design data includes but is not limited to the type, name, index number, and attribute information of the form component. In order to improve efficiency, the form design data can be temporarily saved in the front-end cache. For example, the front-end user interface is built based on a JavaScript framework such as Vue (programming technology), then the front-end form component dragging can be implemented using the draggable (component name) component function. The draggable component is used as a component encapsulation to realize the dragging component and check function. When the form component is dragged, the component index number is triggered to generate an event. Furthermore, in order to improve efficiency, the zero-code development platform can also verify user input data to ensure the accuracy and completeness of the submitted data; in order to improve user experience and practicality, it can also dynamically display or hide form fields according to user-set conditions, and support field-level calculations and logic.

S102: When it is detected that a process component of the user interface is dragged, process index information is automatically generated for the process component, and form setting data of a target form component associated with the process component is stored in the process setting data.

In this embodiment, the zero-code development platform provides a rich library of various input process components. The process component library contains various types of process nodes, such as start nodes, end nodes, decision nodes, task nodes, etc., and supports custom customization components, such as allowing users to set properties through the configuration panel, such as name, description, conditional expression, task assignment, etc. Users customize the process nodes through process components according to business needs, including task assignment, conditional judgment, parallel processing, and drag the process components on the user interface. The zero-code development platform will automatically create an index for each process node of each process component and save the process design data. The process design data includes but is not limited to the node index number, name, type, branch setting, subnode setting, and associated form component property setting. In order to improve efficiency, the process design data can be temporarily saved in the front-end cache. For example, if the front-end user interface is built based on a JavaScript framework such as Vue (programming technology), the front-end process component can also realize the drag function through the draggable (component name) component. When the process component is dragged, the process node index number generation event is triggered. Among them, the form index information and the process index information can adopt the same index generation method. For the convenience of description, the index generated for the form component is defined as the form index information, and the index generated for the process component is defined as the process index information. Furthermore, in order to improve efficiency, the zero-code development platform can also verify the user input data to ensure the accuracy and completeness of the submitted data. The execution and flow of process nodes can also be automatically triggered through predefined process rules and conditions. In order to improve practicality, the process engine of the zero-code development platform should be able to track and monitor the execution status of the workflow, provide operation logs and error handling mechanisms, and support users to modify the process online in real time during the operation stage of building a business application system, and have process version management functions.

S103: Run the process component, and fill the business data input by the user into the corresponding position of the target form component, and store the dynamic operation data during the operation of the process component.

After the above steps temporarily store the process design data and form design data in the cache, they can also be finally stored in the database, as shown in Figure 2. After being saved in the database, the process is run, and data is filled in the form contained in the process node, and the data during the process operation is saved for use in the statistical analysis chart in the next step. For the convenience of description, this step defines the form component contained in the currently running process component as the target form component, and the number of target form components is determined according to the actual business application. For the convenience of description, this step defines the running data of the stored process node as dynamic running data.

S104: When it is detected that the statistical chart component of the user interface is dragged, the statistical chart component is associated with the corresponding form component based on the dynamic operation data, and a statistical chart is generated according to the calculation result of the associated form component.

In this embodiment, the zero-code development platform provides a rich variety of statistical chart components and supports custom customization of statistical chart components. Users can customize visual elements such as chart colors, fonts, titles, legends, and axis labels. The statistical chart component provides a variety of chart types, including but not limited to bar charts, line charts, pie charts, scatter plots, and heat maps. Users can customize statistical analysis charts through statistical chart components according to business needs, drag statistical chart components on the user interface, set data sources for each statistical chart, and associate them with specific form fields. After saving the settings, the background of the zero-code development platform can be used to perform corresponding calculations on the set fields according to business needs, and the calculation results can be returned and displayed on the statistical chart.

In the technical solution provided in this embodiment, when users customize the business application system in a zero-code manner, index information is given to their customized form components and process components when they are created, and the form component settings are integrated into the process node settings, thereby realizing the design integration of forms and processes; the statistical chart component is associated with the corresponding form when it is created, and statistical charts are generated according to the data saved during the operation of the process node, which not only realizes the association of process engine data, custom form data and statistical analysis chart data to form a complete application, forming a basic zero-code application solution, effectively reducing the workload of software developers, but also being more conducive to the use of users with no code capabilities, and improving the flexibility and efficiency of building applications; it also realizes the function of dynamic calculation and data update based on business data, further improving the flexibility and efficiency of users building applications, and enhancing the user experience.

It should be noted that there is no strict order of execution between the steps in the present invention. As long as they comply with the logical order, these steps can be executed simultaneously or in a preset order. Figures 1 and 2 are only a schematic diagram and do not mean that this is the only execution order.

In the above embodiment, there is no limitation on how to generate the form component index number and store the form design data. Based on the above embodiment, the front-end user interface built based on Vue, that is, the form component is a Vue front-end form component. The present invention implements the custom design of the zero-code form by dragging the form component on the front-end user interface through the following contents, which may include the following contents:

When the drag component is called to complete the dragging of the form component, the unique serial number of the form component is obtained based on Vue's global unique identification number strategy; according to the unique serial number of the form component, the form index number of the form component is generated.

In this embodiment, after the form component is dragged, the index number of the form component can be generated using Vue's global unique id generation strategy: ${id}. Of course, the process index information of the process component in the above steps can also be generated using Vue's global unique id generation strategy: ${id}. The index number can be used to integrate the form component settings into the process node settings, thereby realizing the integration of the form and process design.

In order to realize the association between the form and the process, based on the above embodiment, the present invention further provides a form data storage structure for saving the settings of the custom process and the custom form, which may include the following contents:

Pre-build the form data storage structure; the form data storage structure can be expressed as: component display name: business instance name, front-end component name: component type, form component icon attributes: preset attributes, value, value type: input data type, business information, form index number: unique serial number of the form component; for example, in actual applications, the data structure can be expressed as:

{"Component display name": "Business instance name", "Front-end component name": "Component type", "Form component icon attribute": "Preset attribute", "Value": " ", "Value type": "Input data type", "Business information": { }, "Form index number": "The unique serial number of the form component"}.

Obtain business instance name data, component type data, form component icon attribute data, business attribute data and form index number from the form component, and fill the obtained data into the corresponding position of the form data storage structure to obtain form setting data.

In this embodiment, the component display name is represented as title, which is the instance name in the business application system. The front-end component name is represented as name, which is used to identify whether the component input is text data or numeric data. The form component icon attribute is represented as icon, which is used to indicate the permissions of the form component, such as read-only, hidden, or editable. The value is represented as value, the value type is represented as valueType, the business information is represented as props, and the component attributes can set fields according to actual business needs. The form index number is represented as id. Taking the construction of a sales performance record application as an example, the form component data finally stored based on the above form data storage structure can be represented as follows:

[{"title":"Employee Name","name":"TextInput","icon":"el-icon-edit","value":"","valueType":"String","props":{},"id":"field8651080140810"},

{"title":"Number of Sales","name":"NumberInput","icon":"el-icon-edit-outline","value":"","valueType":"Number","props":{},"id":"field1414113105871"}].

From the above, it can be seen that the present invention generates an index for the form component by using Vue's globally unique id generation strategy, and saves the setting data of the custom form through the data structure provided in this embodiment, which can be conducive to the subsequent integration of the form component settings into the process node settings, and the association of the process node and the form settings, thereby achieving the purpose of integrating the form and the process.

The above embodiment does not limit how to associate the form design data with the process design data. The present invention also provides a storage method for the process design data. By designing the storage structure of the process design data, the association between the process data and the form data is achieved, which may include the following contents:

Pre-build the process setting data storage structure; the process setting data storage structure is represented as:

A process setting data storage structure is constructed in advance in a nested manner of parent nodes and child nodes; the process setting data storage structure is expressed as:

Parent node: root node index number: unique serial number of process component, parent node name: null, node type of parent node: root node, node name of parent node: initiating node, parent node name: initiating node, description: description data, node attributes of root node; wherein, the node attributes of the root node include form management identifier: form index number of the first target form component: unique serial number of the form component, display name of the first target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type, form index number of the second target form component: unique serial number of the form component, display name of the second target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type;

Subnode: Subnode index number: unique serial number of process component, parent node name: parent node of subnode, node type of subnode: preset node type, node name of subnode: preset node name, name of subnode: preset node name, node attributes of subnode; wherein, the node attributes of subnode include form management identifier: form index number of third target form component: unique serial number of form component, display name of third target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type, custom attribute: attribute value; form index number of fourth target form component: unique serial number of form component, display name of fourth target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type.

When the end identifier is detected, the sub-node data contained in the process setting data storage structure has been completely stored; the end identifier at least includes an identifier type.

In practical applications, this data structure can be expressed as:

{"Root node index number": "Unique serial number of process component", "Parent node name": "null (empty)", "Node type": "Root node", "Node name": "Initiating node", "Name": "Initiating node", "Description": "Description data", "Node attributes": {"Form management identifier": [{"Form index number of the first target form component": "Unique serial number of form component", "Display name of the first target form component": "Business instance name", "Form data mandatory setting identifier": "Set value", "Form data permission setting identifier": "Permission", "Front-end component name": "Component type"}, {"Form index number of the second target form component": "Unique serial number of form component", "Display name of the second target form component": "Business instance name", "Form data mandatory setting identifier": "Set value", "Form data permission setting identifier": "Permission", "Front-end component name": "Component type"}……]},

"Subnode": {"Subnode index number": "Unique serial number of process component", "Parent node name": "Parent node of subnode", "Node type": "Preset node type", "Node name": "Preset node name", "Name": "Preset node name", "Node attributes": {"Form management identifier": [{"Form index number of third target form component": "Unique serial number of form component", "Display name of third target form component": "Business instance name", "Form data required setting identifier": "Set value", "Form data permission setting identifier": "Set value", " "Setting identifier": "Permission", "Front-end component name": "Component type", "Custom attributes": "Attribute value"}, {"Form index number of the fourth target form component": "Unique serial number of the form component", "Display name of the fourth target form component": "Business instance name", "Form data required setting identifier": "Set value", "Form data permission setting identifier": "Permission", "Front-end component name": "Component type"}, "End identifier": {"Identifier type": "Preset identifier", "Target": ""}}, "Child nodes": {}}.

Obtain the name, node type, branch settings, sub-node settings of each process node and the form setting data of the associated target form component from the process component, fill the obtained data into the corresponding position of the process setting data storage structure, and obtain the process setting data.

In this embodiment, the front end uses a custom flowchart node to design the process. After the form component and the process node are numbered by a globally unique id, the form component information associated with each node is saved in the process design data using the above data structure, and the final generated data can be saved, for example, using the XML design file of Activity. Since the process storage structure uses nested parent nodes and child nodes, when obtaining a certain node information based on the above saved data, a recursive method is used for matching. This embodiment uses the form management identification field to integrate the form data into the node data. The form management identification field can use the "formPerms" field, for example. Taking the above example, root represents the root node, parentId represents the parent node name, type represents the node type, nodeName represents the node name, name is the node name, and desc represents the description data, which is added according to the actual business application. Similarly, the node attribute props contains the form settings, and other attribute fields can be extended according to business requirements. id represents the root node index number, children represents the child node, and required represents the form data required setting identifier, for example, it can be required or optional, and perm represents permissions, such as read-only, hidden, and editable. The process design data finally generated can be:

{"id":"root","parentId":null,"type":"ROOT","nodeName":"Originating Node","name":"Originating Node","desc":"Anyone","props":{"formPerms":[{"id":"field8651080140810","title":"Employee Name","required":false,"perm":"E","nodetype":"TextInput"},{"id":"field1414113105871","title":"Number of Sales","required":false,"perm":"E","nodetype":"NumberInput"}]},

"children": {"id":"node_801519542445","parentId":"root","type":"INPUTCONTNODE","nodeName":"Fill in the node","name":"Fill in the node","props":{"formPerms":[{"id":"field8651080140810","title":"Employee Name","required":false,"perm" : "E", "nodetype": "TextInput", "iswatch": true}, {"id": "field1414113105871", "title": "Sales Number", "required": false, "perm": "E", "nodetype": "NumberInput"}], "refuse": {"type": "TO_END", "target": ""}}, "children": { }}}.

As can be seen from the above, this embodiment saves custom process settings by designing a targeted data structure and associates process nodes with form settings. The above process data storage structure is used to integrate form component settings into process node settings, realizes the design integration of forms and processes, and solves the problem of the process engine being able to associate and obtain form design data during design and operation.

The above embodiment does not limit how the front end performs automatic component matching and echoing. Based on the above embodiment, the present invention also provides an implementation method for the process node to echo and display the form, which may include the following contents:

Get the form management identifier of the process component and the corresponding form component setting data;

Call the Vue component, introduce each target form component through the import method, and echo the form setting data of the corresponding target form component according to the pre-set form management identification information referenced by the Vue component.

The front-end user interface designs the data structure according to the saved form. When the form is displayed at a certain process node, the setting of the form component in the formPerms field of the current node can be obtained. This embodiment adopts the component component of Vue, and introduces each form component through import. The dynamic component is matched and displayed according to the method of is=formPerms.name.

As can be seen from the above, this embodiment can dynamically and flexibly display form components when opening a form of a certain process node, solving the problem of displaying the form according to the form design data at the node in the process and the problem of saving the data format filled in the form.

The above embodiment does not limit how to store form data after the form managed by the process node is filled in during the process node operation. Based on the above embodiment, the present invention also provides an exemplary implementation method, which may include the following contents:

A dynamic operation data storage structure is pre-built based on the key-value format; the dynamic operation data storage structure is represented as:

The form index number of the first target form component: the display name of the first target form component, the form index number of the second target form component: the display name of the second target form component; in actual applications, the data structure can be expressed as:

{"form index number of the first target form component":"display name of the first target form component","form index number of the second target form component":"display name of the second target form component","……};

The dynamic operation data during the operation of the process component is filled into the corresponding position of the dynamic operation data storage structure to obtain the dynamic operation data.

In this embodiment, after filling in the form, the form data can be saved in the form of key-value, where the key is the component index number and the value is the filled value. Taking the above example as an example, the data instance corresponding to the dynamic running data is as follows:

{"field8651080140810":"张三","field1414113105871":"3"}.

The above embodiment does not limit how the statistical analysis chart calculates and displays the statistical chart according to the process and form values. Based on the above embodiment, the present invention also provides an exemplary implementation method for calculating and displaying the statistical chart according to the process and form values, which may include the following contents:

When it is detected that the statistical chart component is dragged, the statistical chart format selection page is displayed in the user interface; when the statistical chart format is a line chart, the component display names corresponding to the horizontal and vertical coordinates of the statistical chart to be generated are constructed based on the current business needs; based on the component display names corresponding to the horizontal and vertical coordinates of the statistical chart, the associated form index numbers corresponding to the number of statistical instances of the statistical chart are obtained from the process setting data respectively; based on each associated form index number and the current business needs, the corresponding number of form data values obtained from the dynamic running data are calculated, and the statistical chart is generated according to the calculation results.

In this embodiment, the statistical chart format selection page includes the formats of statistical charts, such as line charts and pie charts. The front end is designed based on the echarts (visual chart library) large screen design component. This embodiment uses a line chart and combines the above examples as an example to illustrate how to parse the process form data for calculation and return the display data:

The component display names in this embodiment are employee name and sales order number. Correspondingly, as shown in Figure 3, the horizontal axis of the line graph can be the employee name. When setting the horizontal axis of the line graph, the "employee name" form component should be selected; the vertical axis should select the "sales order number" component. The number of statistical instances is 10, which means that the form data of 10 process instances need to be integrated. The current business requirement is to count the total sales of each employee, so the non-repeating values of the "employee name" component are counted, and then the values of the "sales order number" component corresponding to each name are accumulated. First, parse out the id="field8651080140810" of title="employee name" and the id="field1414113105871" of title="sales order number" from formPerms. Then aggregate the results in the saved form data. Finally, with data={

"xData": "Zhang San, Li Si, Wang Wu",

"yData": "5, 3, 6"

} data format to render the echarts chart.

From the above, it can be seen that this embodiment provides a method for parsing and calculating form field values, which can summarize and visualize process information, and can solve the problem of obtaining process engine data and form data in statistical analysis charts. Since the data used is the data saved during the process operation, it can be updated in real time.

Based on the above embodiments, in order to improve the zero-code development platform provided by the present invention so that non-technical users can also easily create and manage complex business application systems, based on the above embodiments, the present invention may also include the following contents:

The zero-code development platform may also include a process logic editor, parallel processing components, sub-process calling components, process monitoring tools, version management systems, permission management systems, data filtering and processors, interactive design components and export components.

Among them, the process logic editor allows users to define the flow conditions and paths between process nodes, and supports the conditional judgment function to automatically determine the next step of the process according to the user-defined conditions. Parallel processing components allow multiple tasks or process branches to be executed simultaneously. Sub-process call components allow users to decompose complex processes into reusable sub-processes. Process monitoring tools can provide real-time views and log records of process execution. The version management system allows users to perform version control and historical tracking of process designs. The permission management system ensures that only authorized users can access and edit specific process components, form components, and statistical chart components, and ensures security when process components, form components, and statistical chart components are integrated with external systems and data sources, such as databases, APIs, Web services, etc. Data filtering and processors are used to support data filtering, sorting, and grouping, so that users can adjust the data displayed in the chart as needed. Interactive design components support various interactive functions, such as tooltips, data point highlighting, drilling, and zooming. The export component supports users to export designed charts as images, PDFs, or embed them into web pages, and supports sharing functions.

From the above, it can be seen that the zero-code development platform provided in this embodiment can significantly improve the efficiency of creating and maintaining business processes, can significantly lower the threshold for statistical chart design, lower the technical threshold, accelerate the iteration and optimization of business processes, improve the efficiency and effectiveness of data visualization, and meet the data display needs of different users.

The present invention also provides a corresponding device for the data processing method of the zero-code development platform, which further makes the method more practical. Among them, the device can be described from the perspective of functional modules and hardware. The data processing device of the zero-code development platform provided by the present invention is introduced below. The device is used to implement the data processing method of the zero-code development platform provided by the present invention. In this embodiment, the data processing device of the zero-code development platform may include or be divided into one or more program modules, and the one or more program modules are stored in a storage medium and executed by one or more processors to complete the data processing method of the zero-code development platform disclosed in Example 1. The program module referred to in this embodiment refers to a series of computer program instruction segments that can complete specific functions, which is more suitable for describing the execution process of the data processing device of the zero-code development platform in the storage medium than the program itself. The following description will specifically introduce the functions of each program module of this embodiment. The data processing device of the zero-code development platform described below and the data processing method of the zero-code development platform described above can be referred to each other.

From the perspective of functional modules, see FIG. 4 , which is a structural diagram of a data processing device of a zero-code development platform provided in this embodiment under a specific implementation mode, and the device may include:

The form data storage module 401 is used to automatically generate form index information for the form component and store form setting data when detecting that the form component of the user interface is dragged;

The process and form data association module 402 is used to automatically generate process index information for the process component when it is detected that the process component of the user interface is dragged, and store the form setting data of the target form component associated with the process component into the process setting data;

The dynamic data storage module 403 is used to run the process component and fill the business data input by the user into the corresponding position of the target form component, and store the dynamic operation data during the operation of the process component;

The chart association module 404 is used to associate the statistical chart component with the corresponding form component based on the dynamic operation data when it is detected that the statistical chart component of the user interface is dragged;

The chart generation module 405 is used to generate a statistical chart according to the calculation results of the associated form component.

Illustratively, in some implementations of this embodiment, the form data storage module 401 may also be used to:

The form component is a Vue front-end form component. When the drag component is called to complete the dragging of the form component, the unique serial number of the form component is obtained based on Vue's global unique identification number strategy;

According to the unique serial number of the form component, trigger the generation of the form index number of the form component.

Illustratively, in some other implementations of this embodiment, the form data storage module 401 may also be used for:

Pre-build the form data storage structure; the form data storage structure is represented as:

Component display name: business instance name, front-end component name: component type, form component icon attributes: preset attributes, value, value type: input data type, business information, form index number: unique serial number of the form component;

Obtain business instance name data, component type data, form component icon attribute data, business attribute data and form index number from the form component, and fill the obtained data into the corresponding position of the form data storage structure to obtain form setting data.

Illustratively, in some other implementations of this embodiment, the above process and form data association module 402 may also be used to:

A process setting data storage structure is constructed in advance in a nested manner of parent nodes and child nodes; the process setting data storage structure is expressed as:

Parent node: root node index number: unique serial number of process component, parent node name: null, node type of parent node: root node, node name of parent node: initiating node, parent node name: initiating node, description: description data, node attributes of root node; wherein, the node attributes of the root node include form management identifier: form index number of the first target form component: unique serial number of the form component, display name of the first target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type, form index number of the second target form component: unique serial number of the form component, display name of the second target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type;

Subnode: Subnode index number: unique serial number of process component, parent node name: parent node of subnode, node type of subnode: preset node type, node name of subnode: preset node name, name of subnode: preset node name, node attributes of subnode; wherein, the node attributes of subnode include form management identifier: form index number of third target form component: unique serial number of form component, display name of third target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type, custom attribute: attribute value; form index number of fourth target form component: unique serial number of form component, display name of fourth target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type;

When the end mark is detected, the sub-node data contained in the process setting data storage structure has been completely stored; the end mark at least includes an identifier type;

Obtain the name, node type, branch settings, sub-node settings of each process node and the form setting data of the associated target form component from the process component, fill the obtained data into the corresponding position of the process setting data storage structure, and obtain the process setting data.

Illustratively, in some other implementations of this embodiment, the above process and form data association module 402 may also be used to:

Get the form management identifier of the process component and the corresponding form component setting data;

Call the Vue component, introduce each target form component through the import method, and echo the form setting data of the corresponding target form component according to the pre-set form management identification information referenced by the Vue component.

For example, in some other implementations of this embodiment, the dynamic data storage module 403 may also be used for:

A dynamic operation data storage structure is pre-built based on the key-value format; the dynamic operation data storage structure is represented as:

The form index number of the first target form component: the display name of the first target form component, the form index number of the second target form component: the display name of the second target form component;

The dynamic operation data during the operation of the process component is filled into the corresponding position of the dynamic operation data storage structure to obtain the dynamic operation data.

For example, in some other implementations of this embodiment, the chart association module 404 may also be used to:

When it is detected that the statistical chart component is dragged, the statistical chart format selection page is displayed in the user interface;

When the statistical chart format is a line chart, the component display names corresponding to the horizontal and vertical axes of the statistical chart to be generated are constructed based on the current business needs;

Based on the component display names corresponding to the horizontal and vertical coordinates of the statistical chart, the associated form index numbers corresponding to the number of statistical instances of the statistical chart are obtained from the process setting data;

Based on the index numbers of each associated form and the current business needs, a corresponding number of form data values are obtained from the dynamic running data and calculated.

The functions of the various functional modules of the data processing device of the zero-code development platform described in this embodiment can be specifically implemented according to the method in the above method embodiment. The specific implementation process can refer to the relevant description of the above method embodiment, which will not be repeated here.

From the above, it can be seen that this embodiment can associate process engine data, custom form data and statistical analysis chart data to form a complete application, thereby realizing the construction of a business application system based on a zero-code development platform.

The data processing device of the zero-code development platform mentioned above is described from the perspective of functional modules. Furthermore, the present invention also provides an electronic device, which is described from the perspective of hardware. Figure 5 is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention under one implementation. As shown in Figure 5, the electronic device includes a memory 50 for storing a computer program; a processor 51 for implementing the steps of the data processing method of the zero-code development platform mentioned in any of the above embodiments when executing a computer program.

Among them, the processor 51 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the processor 51 may also be a controller, a microcontroller, a microprocessor or other data processing chip. The processor 51 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 51 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 51 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 51 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

The memory 50 may include one or more computer non-volatile storage media, which may be non-transitory. The memory 50 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices and flash memory storage devices. In some embodiments, the memory 50 may be an internal storage unit of an electronic device, such as a hard disk of a server. In other embodiments, the memory 50 may also be an external storage device of an electronic device, such as a plug-in hard disk equipped on a server, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Further, the memory 50 may also include both an internal storage unit and an external storage device of an electronic device. The memory 50 may not only be used to store application software and various types of data installed in the electronic device, such as: the code of the program in the process of executing the data processing method of the zero-code development platform, etc., but also be used to temporarily store data that has been output or is to be output. In this embodiment, the memory 50 is at least used to store the following computer program 501, wherein, after the computer program is loaded and executed by the processor 51, the relevant steps of the data processing method of the zero-code development platform disclosed in any of the aforementioned embodiments can be implemented. In addition, the resources stored in the memory 50 may also include an operating system 502 and data 503, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 502 may include Windows, Unix, Linux, etc. The data 503 may include but is not limited to data corresponding to the data processing results of the zero-code development platform, etc.

In some embodiments, the electronic device may further include a display screen 52, an input/output interface 53, a communication interface 54 or a network interface, a power supply 55 and a communication bus 56. Among them, the display screen 52 and the input/output interface 53, such as a keyboard, belong to a user interface, and an exemplary user interface may also include a standard wired interface, a wireless interface, etc. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an OLED (Organic Light-Emitting Diode) touch device, etc. The display may also be appropriately referred to as a display screen or a display unit, which is used to display information processed in the electronic device and to display a visual user interface. The communication interface 54 may exemplarily include a wired interface and/or a wireless interface, such as a WI-FI interface, a Bluetooth interface, etc., which is generally used to establish a communication connection between the electronic device and other electronic devices. The communication bus 56 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, FIG5 shows only one thick line, but this does not mean that there is only one bus or one type of bus.

Those skilled in the art will appreciate that the structure shown in FIG. 5 does not limit the electronic device and may include more or fewer components than shown in the figure, for example, may also include a sensor 57 for implementing various functions.

The functions of the functional modules of the electronic device described in this embodiment can be specifically implemented according to the method in the above method embodiment. The specific implementation process can refer to the relevant description of the above method embodiment, which will not be repeated here.

From the above, it can be seen that this embodiment can associate process engine data, custom form data and statistical analysis chart data to form a complete application, thereby realizing the construction of a business application system based on a zero-code development platform.

It is understandable that if the data processing method of the zero-code development platform in the above embodiment is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a non-volatile storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes but is not limited to: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), electrically erasable programmable ROM, register, hard disk, multimedia card, card-type memory (such as SD or DX memory, etc.), magnetic memory, removable disk, CD-ROM, magnetic disk or optical disk, etc. Various media that can store program codes. Based on this, the present invention also provides a non-volatile storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the data processing method of the zero-code development platform recorded in any of the above embodiments.

It is understandable that if the data processing method of the zero-code development platform in the above embodiment is implemented in the form of a software functional unit and sold or used as an independent product, the computer software product does not need to be stored in a physical storage medium. For example, it can be directly transmitted to a computer or other device with information processing capabilities through a wired network or a wireless network to perform all or part of the steps of the methods of each embodiment of the present invention. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product. Based on this, the present invention also provides a computer program product that stores a computer program. When the computer program is executed by a processor, it performs the steps of the data processing method of the zero-code development platform as described in any of the above embodiments.

In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the hardware disclosed in the embodiments, including devices, electronic devices, and non-volatile storage media, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method part description.

Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

The data processing method, device, electronic device and non-volatile storage medium of a zero-code development platform provided by the present invention are introduced in detail above. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. It should be pointed out that based on the embodiments of the present invention, for ordinary technicians in this technical field, all other embodiments obtained without creative work are within the scope of protection of the present invention. Without departing from the principles of the present invention, the present invention may also be improved and modified in a number of ways, and these improvements and modifications also fall within the scope of protection of the present invention.

Claims (10)

1. A data processing method for a zero-code development platform, comprising: When it is detected that a form component of the user interface is dragged, form index information is automatically generated for the form component, and form setting data is stored; When it is detected that the process component of the user interface is dragged, process index information is automatically generated for the process component, and form setting data of the target form component associated with the process component is stored in the process setting data; Run the process component, and fill the business data input by the user into the corresponding position of the target form component, and store the dynamic operation data during the operation of the process component; When it is detected that the statistical chart component of the user interface is dragged, the statistical chart component is associated with the corresponding form component based on the dynamic operation data, and a statistical chart is generated according to the calculation result of the associated form component. 2. The data processing method of the zero-code development platform according to claim 1, characterized in that the form component is a Vue front-end form component, and the automatic generation of form index information for the form component and the storage of form setting data include: When the drag component is called to complete the dragging of the form component, the unique serial number of the form component is obtained based on Vue's global unique identification number strategy; According to the unique serial number of the form component, the generation of the form index number of the form component is triggered. 3. The data processing method of the zero-code development platform according to claim 1, characterized in that the process of storing form setting data comprises: A form data storage structure is pre-built; the form data storage structure is represented as: Component display name: business instance name, front-end component name: component type, form component icon attributes: preset attributes, value, value type: input data type, business information, form index number: unique serial number of the form component; The business instance name data, component type data, form component icon attribute data, business attribute data and form index number are obtained from the form component, and the obtained data are filled into the corresponding position of the form data storage structure to obtain form setting data. 4. The data processing method of the zero-code development platform according to claim 1, characterized in that storing the form setting data of the target form component associated with the process component into the process setting data comprises: A process setting data storage structure is constructed in advance in a nested manner of parent nodes and child nodes; the process setting data storage structure is expressed as: Parent node: root node index number: unique serial number of process component, parent node name: null, node type of parent node: root node, node name of parent node: initiating node, parent node name: initiating node, description: description data, node attributes of root node; wherein, the node attributes of the root node include form management identifier: form index number of the first target form component: unique serial number of the form component, display name of the first target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type, form index number of the second target form component: unique serial number of the form component, display name of the second target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type; Subnode: Subnode index number: unique serial number of process component, parent node name: parent node of subnode, node type of subnode: preset node type, node name of subnode: preset node name, name of subnode: preset node name, node attributes of subnode; wherein, the node attributes of subnode include form management identifier: form index number of third target form component: unique serial number of form component, display name of third target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type, custom attribute: attribute value; form index number of fourth target form component: unique serial number of form component, display name of fourth target form component: business instance name, form data required setting identifier: setting value, form data permission setting identifier: permission, front-end component name: component type; When the end mark is detected, the sub-node data contained in the process setting data storage structure has been completely stored; the end mark at least includes an identifier type; The name, node type, branch setting, sub-node setting of each process node and the form setting data of the associated target form component are obtained from the process component, and the obtained data is filled into the corresponding position of the process setting data storage structure to obtain the process setting data. 5. The data processing method of the zero-code development platform according to claim 4, characterized in that the process of obtaining the form setting data of the target form component includes: Obtaining the form management identifier of the process component and the corresponding form component setting data; The Vue component is called, each target form component is introduced through the import method, and the form setting data of the corresponding target form component is echoed according to the pre-set form management identification information referenced by the Vue component. 6. The data processing method of the zero-code development platform according to claim 1, characterized in that the storing of dynamic operation data during the operation of the process component comprises: A dynamic operation data storage structure is pre-built based on the key-value format; the dynamic operation data storage structure is represented as: The form index number of the first target form component: the display name of the first target form component, the form index number of the second target form component: the display name of the second target form component; The dynamic operation data during the operation of the process component is filled into the corresponding position of the dynamic operation data storage structure to obtain the dynamic operation data. 7. The data processing method of the zero-code development platform according to any one of claims 1 to 6, characterized in that the statistical chart component is associated with the corresponding form component based on the dynamic operation data, and a statistical chart is generated according to the calculation result of the associated form component, comprising: When it is detected that the statistical chart component is dragged, the statistical chart format selection page is displayed in the user interface; When the statistical chart format is a line chart, the component display names corresponding to the horizontal and vertical axes of the statistical chart to be generated are constructed based on the current business needs; Based on the component display names corresponding to the horizontal and vertical coordinates of the statistical chart, respectively obtaining the associated form index numbers corresponding to the number of statistical instances of the statistical chart from the process setting data; Based on the index numbers of the associated forms and the current business requirements, a corresponding number of form data values are obtained from the dynamic operation data, and a statistical chart is generated according to the calculation results. 8. A data processing device for a zero-code development platform, comprising: A form data storage module, used to automatically generate form index information for the form component and store form setting data when detecting that the form component of the user interface is dragged; A process and form data association module, for automatically generating process index information for the process component when detecting that the process component of the user interface is dragged, and storing the form setting data of the target form component associated with the process component into the process setting data; A dynamic data storage module, used to run the process component, fill the business data input by the user into the corresponding position of the target form component, and store the dynamic operation data during the operation of the process component; A chart association module, configured to associate the statistical chart component with a corresponding form component based on the dynamic operation data when detecting that the statistical chart component of the user interface is dragged; The chart generation module is used to generate statistical charts based on the calculation results of the associated form components. 9. An electronic device, characterized in that it comprises a processor and a memory, wherein the processor is used to implement the steps of the data processing method of the zero-code development platform as claimed in any one of claims 1 to 7 when executing a computer program stored in the memory. 10. A non-volatile storage medium, characterized in that a computer program is stored on the non-volatile storage medium, and when the computer program is executed by a processor, the steps of the data processing method of the zero-code development platform as described in any one of claims 1 to 7 are implemented.