Method for automatically extracting data value label of low-code platform

Abstract

The invention provides a method for automatically extracting a data value label of a low-code platform, and the method comprises the following steps: S1, configuring a label to be extracted through a configuration center, and storing the configured label in a label system warehouse; s2, when the function of the low-code platform is triggered and responded, matching source data provided by an external system according to a label in a label system warehouse, finding corresponding data content, storing the label and the data content in a label data warehouse before calculation, generating a unique identifier of label data, and storing the unique identifier of the label data in the label system warehouse; then generating a label calculation task by using the unique identifier, the label and the data content, and handing over the label calculation task to a label calculation unit for calculation; s3, the label calculation unit returns a calculation result to the low-code platform; and S4, the low-code platform receives a calculation task result fed back by the label calculation unit, and updates the label data content in the label data warehouse according to the unique label data identifier to form effective label data.

Description

Technical Field

[0001] The present invention relates to a data extraction method, and in particular to a method for automatically extracting data value labels on a low-code platform. Background Art

[0002] In the software development field, low-code platform development is a visual application development approach that delivers applications faster with less code. Low-code development platforms are a set of digital technology tool platforms that enable rapid construction of required business platforms through more efficient methods like graphical drag-and-drop and parameterized configuration. They enable innovative scenarios and applications in digital transformation with little or no code.

[0003] Extracting data value refers to the process of extracting the required information from the original data for further storage, conversion, and analysis based on a certain purpose. On this basis, relevant tags can be defined for the extracted data value content. In the existing technology, there are systems that support tags (markers and descriptions added to the data. It is a kind of labeling, annotation, and understanding of the data by humans or systems), but more of them are label definitions of data value, lacking records of dynamic label operations. How to realize the dynamic recording of tags in the process of extracting data value is lacking in the current existing technology.

[0004] Furthermore, most current systems complete the label definition for specified data through custom development, or they can create configuration files for the labels that include variables, conditions, and codes. However, the interface is not easy to operate and is not scalable. In addition to developers, other people who do not understand code will need to spend a lot of energy and time if they want to use labels to increase the content of extracted data or change the logic of extracted data. Summary of the Invention

[0005] The present invention provides a method for automatically extracting data value tags on a low-code platform. This method solves the problem of dynamically recording data based on tag management during the data value extraction process, thereby enabling the addition of extracted data content or modification of extracted data logic on the low-code platform. The technical solution is as follows:

[0006] A method for automatically extracting data value labels on a low-code platform includes the following steps:

[0007] Step S1: The operator of the low-code platform configures the tags to be extracted through the pre-written configuration file provided by the configuration center or the drag-and-drop method, and saves the configured tags to the tag system warehouse to form tags in the tag system warehouse. The tags provide a basis for the next step of refining the tag content;

[0008] Step S2: When the function of the low-code platform is triggered to respond, the source data provided by the external system is matched according to the label in the label system warehouse, and the data content corresponding to the label in the source data provided by the external system is found. Then, the label and data content are saved in the label data warehouse before calculation, and a unique identifier of the label data is generated. Then, the unique identifier, label and data content are used together to generate a label calculation task, and the label calculation task is handed over to the label calculation unit to calculate the label value;

[0009] Step S3: After receiving the label calculation task, the label calculation unit starts to perform label value distribution calculation. The label calculation unit generates label data based on the assigned label calculation task and returns the label data to the low-code platform;

[0010] Step S4: The low-code platform receives the feedback from the label calculation unit: the calculation task results and the unique identifier of the label data, updates the label data content in the label data warehouse, and forms valid label data.

[0011] Furthermore, step S1 includes the following steps:

[0012] S11: The low-code platform operator configures the value labels to be extracted from the source data and the rules for value labels based on business needs through the configuration center;

[0013] S12: The low-code platform operator configures the tag group to be extracted from the source data through the configuration center based on business needs. The tag group includes several value tags and at least one core tag. The operator also determines the value selection rules for all value tags and core tags included in the tag group. The rules for dynamic tags inherit the rules for value tags.

[0014] S13: Low-code platform operators configure the associated tags to be extracted from the source data through the configuration center based on business needs. Associated tags represent the data association relationship between multiple tag groups.

[0015] S14: The low-code platform operator configures the object tags to be extracted from the source data through the configuration center based on business needs. The object tags represent the relationship between the objects and the source data.

[0016] S15: The operator of the low-code platform configures the calculation formula and calculation method for the tags to be calculated.

[0017] Furthermore, step S2 includes the following steps:

[0018] S21: Low-code platform: The function is triggered by the source data of the external system. The triggering methods include the external system providing new data to the low-code platform, the external system updating old data to the low-code platform, and the change of external system data causing the tag listener or trigger to respond.

[0019] S22: Match the source data provided by the external system with the tags in the tag system warehouse, find the data content corresponding to the tags in the source data provided by the external system, and update the data tag warehouse based on the tags and data content of the triggered response, and obtain the unique identifier after the data is saved;

[0020] S23: The low-code platform uses the unique identifier, label, and data content of the data label warehouse to generate one or more label calculation tasks, and saves them in its own task queue, waiting for the label calculation unit to execute this task;

[0021] S24: After the low-code platform obtains the result of the label calculation unit, it updates the calculation result to the data label warehouse according to the unique identifier of the data label warehouse in the result to form a valid label data.

[0022] Furthermore, step S3 includes the following steps:

[0023] S31: The tag computing unit requests tasks from the low-code platform in a polling manner;

[0024] S32: When one of the tag calculation units receives a calculation task, it first obtains the tag configuration content from the tag system warehouse based on the tag information in the task content. The task content should include but is not limited to: calculation formula, calculation parameters, and calculation parameter acquisition interface;

[0025] S33: First, obtain all parameters involved in the calculation formula according to the calculation parameters and parameter acquisition interface, and then execute the calculation formula to obtain the label calculation result;

[0026] S34: If any of the above steps S31-S33 fails, the error cause is directly returned to the low-code platform;

[0027] S35: If the task is successfully executed, the calculation result is returned to the low-code platform;

[0028] S36: After the task is completed, the label calculation unit requests the task from the low-code platform again.

[0029] Furthermore, step S4 includes the following steps:

[0030] S41: After the low-code platform obtains the task result, it determines the correctness of the result execution. If the calculation fails, it can determine whether the task can be re-executed or not executed based on the tag configuration;

[0031] S42: The low-code platform determines that the task result calculation is successful, and then determines whether the tag attribute needs to perform derivative calculations on the calculation result based on the tag configuration, and generates subsequent new tag calculation tasks;

[0032] S43: The low-code platform determines whether this is a label calculation based on the label task and is broken down into multiple tasks for execution. If it is multiple tasks, the calculation results need to be temporarily stored. When all calculation tasks return and succeed, the multiple calculation results are merged according to the label configuration. The merged calculation can generate a new calculation task or be completed by the low-code platform itself.

[0033] S44: When all the above steps are completed and the process is correct, the final calculation result is updated to the label data warehouse according to the unique identifier of the label data warehouse.

[0034] The method for automatically extracting data value labels of the low-code platform is provided with a data extraction platform, which includes a low-code platform, a configuration center, a label system warehouse, a label calculation unit and a label data warehouse. The low-code platform is connected to the configuration center, the label calculation unit and the label data warehouse, and the configuration center is connected to the low-code platform through the label system warehouse; the low-code platform is responsible for the management of the label system warehouse, and realizes the creation of label calculation tasks, and schedules the label calculation unit to execute label calculation tasks.

[0035] The configuration center creates the label system by dragging components or writing configuration files, and defines the label calculation method, calculation form and algorithm, and the association relationship information between labels, thereby forming value labels, label groups, label dynamic association rules, and label dynamic calculation rules.

[0036] The value tag is one of the data that the business system needs to pay attention to; the tag group consists of several value tags and at least one core tag that represents the characteristics of the tag group; the tag dynamic association rule is that the value tag content that constitutes the tag group can adopt different value rules according to the definition of the tag group to implement dynamic value rules; the tag dynamic calculation rule means that the data obtained after calculation according to the dynamic value rule configured by the tag group is a dynamic tag. In principle, the rules of dynamic tags should inherit the rules of value tags.

[0037] The tag system warehouse is used to store the tag system configured by the configuration center, including value tags, tag groups, tag dynamic association rules and tag dynamic calculation rules.

[0038] The label calculation unit is an independent functional module used to calculate label content according to the label calculation formula and source data, and is used to perform label calculation tasks. Each label calculation unit only calculates one label or one label group at the same time.

[0039] The method for automatically extracting data value tags on the low-code platform has the following characteristics:

[0040] (1) Regarding the construction of data tags, existing products are more focused on defining tags for specific data. Compared with the tag group proposed in the present invention, they lack the ability to record information about the dynamic operation process of tags. They also fail to keep records and provide reminders for error messages reported during the operation of tags. This places a lot of workload on developers, thereby increasing work costs. The tag group proposed in the present invention avoids the above-mentioned defects, thereby reducing costs.

[0041] (2) Based on business application requirements and data display scenarios, various types of raw data in the low-code platform are aggregated according to the objects or calculation rules and forms to form multiple data sets. Then, the data under the same data set are batch preprocessed according to the set rules, and the calculation results are quickly converted into new data assets. The purpose is to reduce the volume of data supply and improve the overall efficiency of data use when applying and sharing data in the future.

[0042] The data processing interface of the present invention is simple and easy to operate, easy to use, reduces man-hour costs, and improves work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 This is a data extraction system architecture diagram of the method for automatically extracting data value labels of the low-code platform;

[0044] Figure 2 is a schematic diagram of the execution logic of step S2;

[0045] Figure 3 It is a logical diagram for judging the execution results. DETAILED DESCRIPTION

[0046] like Figure 1 As shown, the method for automatically extracting data value labels of the low-code platform is provided with a data extraction platform, which includes a low-code platform 1, a configuration center 2, a label system warehouse 3, a label calculation unit 4 and a label data warehouse 5. The low-code platform 1 is connected to the configuration center 2, the label calculation unit 4 and the label data warehouse 5 as the core of the business system. The configuration center 2 is connected to the low-code platform 1 through the label system warehouse 3. On the user side, the low-code platform 1 is used to introduce data provided by external systems, and then on the service side, the data value is extracted from the data provided by the external system according to the labels of the label system warehouse 3, and the results are managed.

[0047] in:

[0048] The low-code platform 1, as the core of the business system, is responsible for the management of the label system warehouse 3, and realizes the creation of label calculation tasks, and schedules the label calculation unit 4 to perform label calculation tasks.

[0049] The configuration center 2 is the embodiment of the low-code capability of the entire platform for extracting data value. It realizes the creation of label systems by dragging components or writing configuration files, as well as the definition of label calculation methods, calculation forms and algorithms, and the relationship between labels, and then forms value labels, label groups, label dynamic association rules and label dynamic calculation rules. The purpose is to use less code and faster speed to quickly complete the required business functions, deliver applications, and realize scenario application innovation in digital transformation with little code or no code.

[0050] The label system warehouse 3 is used to store the label system configured by the configuration center 2, including value labels, label groups, label dynamic association rules and label dynamic calculation rules; the value label is one of the data that the business system needs to pay attention to; the label group is a collection of multiple value labels, which includes at least one core label that represents the information of the label group characteristics; the label dynamic association rule is that the value label content that constitutes the label group can adopt different value rules according to the definition of the label group to realize the dynamic value rule; the label dynamic calculation rule means that the data obtained after calculation according to the dynamic value rule configured by the label group is a dynamic label. In principle, the rule of the dynamic label should inherit the rule of the value label.

[0051] For example, a piece of data describes an event that occurred in a certain place. The business system needs to dispatch this event to a certain unit for processing. The dispatch operation may have two possible results: one is that the dispatched unit completes the event processing as required and provides the processing results; the other is that the dispatched unit cannot complete the event processing and provides the reason for the inability to process. In this case, the business system may continue to dispatch this event to another unit or dispatch it to the same unit again for further processing. This is a simple dispatch process, and the data that the business system needs to pay attention to during this process includes but is not limited to the following:

[0052] What happened (unique identifier of the event);

[0053] Who (sending person)

[0054] What time (dispatch time);

[0055] What action (dispatch or feedback);

[0056] Number of times (the number of dispatches);

[0057] Target (the dispatched unit, or the people in the unit).

[0058] Each of these items can be extracted into a value tag, each of which can be configured with its own value rules. For example, the value of the "Who" (dispatcher) value tag is derived from the dispatcherUserId field in the dispatch data, while the value of the "When" (dispatching time) value tag is derived from the dispatcherTime field in the dispatch data. Value tags and their value rules can be configured in the configuration center 2 and stored in the tag system repository 3.

[0059] Through the above examples, it can be seen that a set of value tags generated for each dispatch can also create a tag group according to the configured logical rules. The tag group consists of several value tags and at least one core tag that represents the characteristics of the tag group. The value tag content that makes up the tag group can adopt different value rules according to the definition of the tag group to implement dynamic value rules. The data obtained after calculation according to the dynamic value rules configured by the tag group is a dynamic tag. In principle, the rules of dynamic tags should inherit the rules of value tags. According to the above example, for each dispatch, the value tag at the time of dispatch plus the number of dispatches can be extracted as the core tag, and the tag group rules provided by the configuration center 2 are combined into a tag group generation rule and value rule, and saved in the tag system warehouse 3.

[0060] Each data operation of the business system may generate dynamic tags containing multiple tag groups, and dynamic logical relationships with other tag groups can also be configured. For example, a dispatch can define a dispatch tag group and a dispatch count tag group; a feedback can define a feedback tag group. If the feedback result is that the processing is completed, the dynamic tag of the tag group of the corresponding dispatch count can be updated to valid dispatch, and the valid number of dispatches recorded by the dynamic tag is increased by one; if the feedback result is that the processing cannot be completed, the dynamic tag of the tag group of the corresponding dispatch count can be updated to invalid dispatch, and the invalid number of dispatches recorded by the dynamic tag is increased by one; the dynamic association information, dynamic association judgment logic, and dynamic association operation logic between the above-mentioned tag groups are also configured through the configuration center and saved in the tag system warehouse.

[0061] Furthermore, the information contained in each data record or each data operation can be used to extract data objects, such as people (the person who reported the incident, the people involved in the incident), places (the address where the incident occurred), things (the type of incident), objects (the objects involved in the incident), organizations (the departments and units involved in the incident), etc., and can also be configured for associated extraction. For example: Zhang San complained that the heating in a certain community where he lived was not hot enough, and the corresponding data objects that can be extracted are: Zhang San made one complaint, the object of the complaint was a certain community, and the complaint issue was a heating problem, etc.

[0062] The label calculation unit 4 is an independent functional module used to calculate the label content according to the label calculation formula and source data, and is used to perform label calculation tasks; each label calculation unit 4 only calculates one label or one label group at the same time; when there are too many label calculation tasks generated on the low-code platform 1, the ability of multi-task parallel calculation can be achieved by running multiple label calculation units 4, thereby alleviating the task pressure of the low-code platform 1.

[0063] The tag data warehouse 5 is used to store data of value tags, dynamic tags, and object tags. These data are regarded as the results of extracting data value, and the results of extracting data value can be provided to external systems through interfaces or other forms.

[0064] The present invention comprises the following steps:

[0065] Step S1: The low-code platform operator configures the tags to be extracted using a pre-written configuration file or drag-and-drop tag configuration provided by the configuration center 2. The configured tags are saved to the tag system warehouse 3, forming tags in the tag system warehouse 3. These tags provide the basis for the next step of refining the tag content.

[0066] Furthermore, step S1 includes the following sub-steps:

[0067] S11: The operator of the low-code platform configures the value labels and value label rules to be extracted from the source data through the configuration center 2 according to business needs.

[0068] S12: The operator of the low-code platform configures the label group to be extracted from the source data through the configuration center 2 according to business needs. The content of the label group includes several value labels and at least one core label, and determines the value selection rules of all value labels and core labels contained in the label group. The rules of dynamic labels inherit the rules of value labels.

[0069] S13: The operator of the low-code platform configures the associated tags to be extracted from the source data through the configuration center 2 according to business needs. The associated tags represent the data association relationship between multiple tag groups.

[0070] S14: The operator of the low-code platform configures the object labels to be extracted from the source data through the configuration center 2 according to business needs. The object labels represent the relationship between the objects and the source data.

[0071] S15: The operator of the low-code platform configures the calculation formula and calculation method for the tags to be calculated.

[0072] Calculation formula example: The data content value is greater than or equal to the label threshold, and the data content value is between label threshold 1 and label threshold 2. Calculation method example: Streaming calculation, batch calculation, etc. Configure a listener or timer to calculate label content to specify the timing of label calculation tasks.

[0073] Step S2: When the function of the low-code platform 1 is triggered to respond, the source data provided by the external system is first matched according to the label in the label system warehouse 3, and the data content corresponding to the label in the source data provided by the external system is found. Then, the label and data content are saved in the label data warehouse 5 before calculation, and a unique identifier of the label data is generated. Then, the unique identifier, label and data content are used together to generate a label calculation task, and the label calculation task is handed over to the label calculation unit 4 to calculate the label value.

[0074] Furthermore, step S2 includes the following sub-steps:

[0075] S21: If Figure 2 As shown, the function of low-code platform 1 is triggered by the source data of the external system. The triggering methods include the external system providing new data to low-code platform 1, the external system updating old data to the low-code platform, and the change of external system data causing the tag listener or trigger to respond.

[0076] S22: Match the source data provided by the external system according to the tags in the tag system warehouse 3, find the data content corresponding to the tags in the source data provided by the external system, and update the low-code platform to the data tag warehouse 5 according to the tags and data content of the trigger response, and obtain the unique identifier after the data is saved;

[0077] S23: The low-code platform 1 uses the unique identifier, label and data content of the data label warehouse 5 to generate one or more label calculation tasks, and saves them in its own task queue, waiting for the label calculation unit 4 to execute this task.

[0078] S24: After the low-code platform obtains the result of the label calculation unit, it updates the calculation result to the data label warehouse according to the unique identifier of the data label warehouse in the result to form a valid label data.

[0079] Step S3: After the label calculation unit 4 receives the label calculation task, it starts to perform label value distribution calculation, assigns label calculation tasks to different label calculation units 4, generates label data, and returns the label data to the low-code platform 1;

[0080] Furthermore, step S3 includes the following sub-steps:

[0081] S31: The label calculation unit 4 requests a task from the low-code platform 1 in a polling manner;

[0082] S32: When one of the tag calculation units 4 receives a calculation task, it first obtains the tag configuration content from the tag system warehouse 3 based on the tag information in the task content. The task content should include but is not limited to: calculation formula, calculation parameters, calculation parameter acquisition interface, etc.

[0083] S33: First, obtain all parameters involved in the calculation formula according to the calculation parameters and parameter acquisition interface, and then execute the calculation formula to obtain the label calculation result;

[0084] S34: If any of the above steps S31-S33 fails, the error cause is directly returned to the low-code platform 1;

[0085] S35: If the task is successfully executed, the calculation result is returned to the low-code platform 1;

[0086] S36: After the task is executed, the label calculation unit 4 requests the task from the low-code platform 1 again.

[0087] Step S4: The low-code platform receives the calculation task results and the unique identifier of the label data fed back by the label calculation unit 4, updates the label data content in the label data warehouse 5, and forms valid label data.

[0088] Further, if Figure 3 As shown, step S4 includes the following sub-steps:

[0089] S41: After the low-code platform 1 obtains the task result, it determines the correctness of the result execution. If the calculation fails, it can determine whether the task can be re-executed or not executed based on the label configuration.

[0090] S42: The low-code platform 1 determines that the task result calculation is successful, and then determines whether the tag attribute needs to perform derivative calculations on the calculation results based on the tag configuration, and generates subsequent new tag calculation tasks.

[0091] S43: The low-code platform determines whether this is a label calculation based on the label task and is broken down into multiple tasks for execution. If it is multiple tasks, the calculation results need to be temporarily stored. When all calculation tasks return and succeed, the multiple calculation results are merged according to the label configuration. The merged calculation can generate a new calculation task or be completed by the low-code platform itself.

[0092] S44: When all the above steps are completed and the process is correct, the final calculation result is updated to the label data warehouse according to the unique identifier of the label data warehouse.

[0093] This invention implements data classification and extraction through a configurable interface or parameters, reducing development costs. Furthermore, the extraction process, extraction format, and extraction algorithm for each type of tag in the system can be customized, making the system more widely applicable and practical. The data processing interface of this invention is simple and easy to use, reducing labor costs and improving work efficiency.

Claims

1. A method for automatically extracting data value labels on a low-code platform, comprising the following steps: Step S1: The operator of the low-code platform configures the tags to be extracted through the pre-written configuration file provided by the configuration center or the drag-and-drop method, and saves the configured tags to the tag system warehouse to form tags in the tag system warehouse. The tags provide a basis for the next step of refining the tag content; Step S2: When the function of the low-code platform is triggered to respond, the source data provided by the external system is matched according to the label in the label system warehouse, and the data content corresponding to the label in the source data provided by the external system is found. Then, the label and data content are saved in the label data warehouse before calculation, and a unique identifier of the label data is generated. Then, the unique identifier, label and data content are used together to generate a label calculation task, and the label calculation task is handed over to the label calculation unit to calculate the label value; Step S3: After receiving the label calculation task, the label calculation unit starts to perform label value distribution calculation. The label calculation unit generates label data based on the assigned label calculation task and returns the label data to the low-code platform; Step S4: The low-code platform receives the feedback from the label calculation unit: the calculation task results and the unique identifier of the label data, updates the label data content in the label data warehouse, and forms valid label data.

2. The method for automatically extracting data value tags on a low-code platform according to claim 1 is characterized by: Step S1 includes the following steps: S11: The low-code platform operator configures the value labels to be extracted from the source data and the rules for value labels based on business needs through the configuration center; S12: The low-code platform operator configures the tag group to be extracted from the source data through the configuration center based on business needs. The tag group includes several value tags and at least one core tag. The operator also determines the value selection rules for all value tags and core tags included in the tag group. The rules for dynamic tags inherit the rules for value tags. S13: Low-code platform operators configure the associated tags to be extracted from the source data through the configuration center based on business needs. Associated tags represent the data association relationship between multiple tag groups. S14: The low-code platform operator configures the object tags to be extracted from the source data through the configuration center based on business needs. The object tags represent the relationship between the objects and the source data. S15: The operator of the low-code platform configures the calculation formula and calculation method for the tags to be calculated.

3. The method for automatically extracting data value tags on a low-code platform according to claim 1 is characterized by: Step S2 includes the following steps: S21: Low-code platform: The function is triggered by the source data of the external system. The triggering methods include the external system providing new data to the low-code platform, the external system updating old data to the low-code platform, and the change of external system data causing the tag listener or trigger to respond. S22: Match the source data provided by the external system with the tags in the tag system warehouse, find the data content corresponding to the tags in the source data provided by the external system, and update the data tag warehouse based on the tags and data content of the triggered response, and obtain the unique identifier after the data is saved; S23: The low-code platform uses the unique identifier, label, and data content of the data label warehouse to generate one or more label calculation tasks, and saves them in its own task queue, waiting for the label calculation unit to execute this task; S24: After the low-code platform obtains the result of the label calculation unit, it updates the calculation result to the data label warehouse according to the unique identifier of the data label warehouse in the result to form a valid label data.

4. The method for automatically extracting data value tags on a low-code platform according to claim 1 is characterized by: Step S3 includes the following steps: S31: The tag computing unit requests tasks from the low-code platform in a polling manner; S32: When one of the tag calculation units receives a calculation task, it first obtains the tag configuration content from the tag system warehouse based on the tag information in the task content. The task content should include but is not limited to: calculation formula, calculation parameters, and calculation parameter acquisition interface; S33: First, obtain all parameters involved in the calculation formula according to the calculation parameters and parameter acquisition interface, and then execute the calculation formula to obtain the label calculation result; S34: If any of the above steps S31-S33 fails, the error cause is directly returned to the low-code platform; S35: If the task is successfully executed, the calculation result is returned to the low-code platform; S36: After the task is completed, the label calculation unit requests the task from the low-code platform again.

5. The method for automatically extracting data value tags on a low-code platform according to claim 1 is characterized by: Step S4 includes the following steps: S41: After the low-code platform obtains the task result, it determines the correctness of the result execution. If the calculation fails, it can determine whether the task can be re-executed or not executed based on the tag configuration; S42: The low-code platform determines that the task result calculation is successful, and then determines whether the tag attribute needs to perform derivative calculations on the calculation result based on the tag configuration, and generates subsequent new tag calculation tasks; S43: The low-code platform determines whether this is a label calculation based on the label task and is broken down into multiple tasks for execution. If it is multiple tasks, the calculation results need to be temporarily stored. When all calculation tasks return and succeed, the multiple calculation results are merged according to the label configuration. The merged calculation can generate a new calculation task or be completed by the low-code platform itself. S44: When all the above steps are completed and the process is correct, the final calculation result is updated to the label data warehouse according to the unique identifier of the label data warehouse.

6. The method for automatically extracting data value tags on a low-code platform according to claim 1 is characterized by: The method for automatically extracting data value tags of the low-code platform is provided with a data extraction platform, which includes a low-code platform, a configuration center, a tag system warehouse, a tag calculation unit and a tag data warehouse. The low-code platform is connected to the configuration center, the tag calculation unit and the tag data warehouse, and the configuration center is connected to the low-code platform through the tag system warehouse; The low-code platform is responsible for the management of the label system warehouse, the creation of label calculation tasks, and the scheduling of label calculation units to execute label calculation tasks.

7. The method for automatically extracting data value tags on a low-code platform according to claim 6 is characterized by: The configuration center creates the label system by dragging components or writing configuration files, and defines the label calculation method, calculation form and algorithm, and the association relationship information between labels, thereby forming value labels, label groups, label dynamic association rules, and label dynamic calculation rules.

8. The method for automatically extracting data value tags on a low-code platform according to claim 7, characterized in that: The value tag is one of the data that the business system needs to pay attention to; the tag group consists of several value tags and at least one core tag that represents the characteristics of the tag group; the tag dynamic association rule is that the value tag content that constitutes the tag group can adopt different value rules according to the definition of the tag group to implement dynamic value rules; the tag dynamic calculation rule means that the data obtained after calculation according to the dynamic value rule configured by the tag group is a dynamic tag. In principle, the rules of dynamic tags should inherit the rules of value tags.

9. The method for automatically extracting data value tags on a low-code platform according to claim 7, characterized in that: The tag system warehouse is used to store the tag system configured by the configuration center, including value tags, tag groups, tag dynamic association rules and tag dynamic calculation rules.

10. The method for automatically extracting data value tags on a low-code platform according to claim 6, characterized in that: The label calculation unit is an independent functional module used to calculate label content according to the label calculation formula and source data, and is used to perform label calculation tasks. Each label calculation unit only calculates one label or one label group at the same time.

Images