Data processing method and device, electronic equipment, storage medium and product

Abstract

The invention discloses a data processing method and device, electronic equipment, a storage medium and a product. The invention relates to the technical field of big data. The method comprises the following steps: in response to a trigger operation on at least one form event, loading at least one pre-configured target processing method corresponding to a target event and corresponding to-be-used data; executing a data processing operation corresponding to the target event based on the target processing method and the corresponding to-be-used data to obtain a to-be-verified processing result; if the to-be-verified processing result meets the preset condition, continuing to execute the data processing operation corresponding to the target event based on the next target processing method and the corresponding to-be-processed data; and rendering target display information corresponding to the target event based on the target processing result corresponding to the at least last target processing method. According to the technical scheme, the design cost of the form is reduced, and the code reuse rate of the form event processing method is improved.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of big data technology, and in particular, to a data processing method, device, electronic device, storage medium and product. Background Art

[0002] As an important tool for filling in data in Internet applications, forms play a vital role. With the continuous development of the Internet, the needs of business scenarios have diversified, and forms have become more complicated.

[0003] At present, for form design scenarios with complex execution logic, developers are required to write a large number of front-end scripts to meet business needs, which leads to the problem of high technical cost of form design work; further, these front-end scripts are encapsulated in their respective form events, but some form event calling logics are basically similar. The above method requires designing a set of execution logic in each form event, which leads to the problem of low code reuse rate of form event processing methods. Summary of the invention

[0004] The embodiments of the present invention provide a data processing method, device, electronic device, storage medium and product to reduce the design cost of a form and improve the code reuse rate of a form event processing method.

[0005] In a first aspect, an embodiment of the present invention provides a data processing method, the method comprising:

[0006] In response to a trigger operation on at least one form event, loading at least one pre-configured target processing method corresponding to the target event and data to be used corresponding to the at least one target processing method; wherein the target event corresponds to the trigger operation;

[0007] Based on the target processing method and the corresponding data to be used, a data processing operation corresponding to the target event is performed to obtain a processing result to be verified that is compatible with the target processing method;

[0008] If the processing result to be verified meets the preset condition, then based on the next target processing method of the target processing method and the corresponding data to be processed, continue to execute the data processing operation corresponding to the target event;

[0009] Rendering target display information corresponding to the target event based on a target processing result corresponding to at least a last target processing method in at least one target processing method.

[0010] In a second aspect, an embodiment of the present invention further provides a data processing device, the device comprising:

[0011] An event triggering module, configured to load, in response to a triggering operation on at least one form event, at least one pre-configured target processing method corresponding to the target event and data to be used corresponding to the at least one target processing method; wherein the target event corresponds to the triggering operation;

[0012] A processing result determination module, used to perform a data processing operation corresponding to the target event based on the target processing method and the corresponding data to be used, and obtain a processing result to be verified that is compatible with the target processing method;

[0013] A method continuing execution module, used for continuing to execute the data processing operation corresponding to the target event based on the next target processing method of the target processing method and the corresponding data to be processed if the processing result to be verified meets the preset condition;

[0014] The display information determination module is used to render target display information corresponding to the target event based on a target processing result corresponding to at least the last target processing method in at least one target processing method.

[0015] In a third aspect, an embodiment of the present invention further provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the data processing method as described in any one of the embodiments of the present invention is implemented.

[0016] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a data processing method as described in any one of the embodiments of the present invention.

[0017] In a fifth aspect, an embodiment of the present invention further provides a computer program product, including a computer program, which, when executed by a processor, implements a data processing method as described in any one of the embodiments of the present invention.

[0018] In an embodiment of the present invention, when designing a form, at least one processing method corresponding to each form event and corresponding data to be processed are pre-configured. When the form is applied, by responding to a trigger operation on at least one form event, at least one pre-configured target processing method corresponding to the target event and data to be used corresponding to at least one target processing method are loaded, and a data processing operation corresponding to the target event is performed based on the target processing method and the corresponding data to be used, and a processing result to be verified that is compatible with the target processing method is obtained. Furthermore, if the processing result to be verified meets a preset condition, the data processing operation corresponding to the target event is continued to be executed based on the next target processing method of the target processing method and the corresponding data to be processed. Subsequently, the target display information corresponding to the target event can be rendered based on the target processing result corresponding to at least the last target processing method in at least one target processing method. The technical solution of the present invention splits the complex execution logic of a form event into multiple processing methods, and configures at least one corresponding processing method and corresponding data to be processed for each form event. Since the split processing method part is a common processing logic and can be reused, the user only needs to develop the running scripts of some processing methods, which reduces the design cost of forms with complex execution logic. Furthermore, in this embodiment, the corresponding target processing method and data to be processed are loaded when the target event is triggered. The same processing method can be repeatedly called by multiple different form events, thereby improving the code reuse rate of the corresponding processing method of the form event. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0020] Figure 1 is a flow chart of a data processing method provided according to an embodiment of the present invention;

[0021] Figure 2 is a schematic diagram of a data processing method provided according to an embodiment of the present invention;

[0022] Figure 3 It is a schematic diagram of a global calling method and / or a local calling method configuration operation method according to an embodiment of the present invention;

[0023] Figure 4 is a schematic diagram of a data processing method provided according to an embodiment of the present invention;

[0024] Figure 5is a schematic diagram of a specific implementation process of a data processing method provided according to an embodiment of the present invention;

[0025] Figure 6 is a structural schematic diagram of a data processing device provided according to an embodiment of the present invention;

[0026] Figure 7 The present invention is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0027] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0028] It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. At the same time, in the description of the present invention, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance. The acquisition, storage, use, and processing of data in the technical solution of this application comply with the relevant provisions of national laws and regulations.

[0029] Figure 1 1 is a flow chart of a data processing method provided according to an embodiment of the present invention. This embodiment is applicable to the design of a form with complex execution logic and the data processing of form events in the form. The method can be executed by a data processing device, which can be implemented in the form of hardware and / or software. Figure 1 As shown, the method includes:

[0030] S110: In response to a triggering operation on at least one form event, load at least one pre-configured target processing method corresponding to the target event and to-be-used data corresponding to the at least one target processing method.

[0031] Among them, a form is a user interface for collecting and submitting data, and a form has the function of information flow. A form is composed of form elements, which can be understood as different types of input elements, radio buttons, and submit buttons. Form events are a series of events triggered when a user interacts with a form element in a form, including but not limited to clicks, input changes, gaining or losing focus, submission, etc. These events allow the server to respond to user operations, such as validating input, processing data, or executing specific business logic.

[0032] Here are some common form events and their descriptions. Value change event: Triggered when the value of a form element changes, such as when a user completes input (without keeping focus) after typing in an input box or selecting a drop-down list; this event is often used to trigger data validation or submission operations after the user has completed all necessary input. Get and lose focus events: Triggered when a form element gains or loses focus. For example, when a user clicks an input box to start typing, a get focus event is triggered; when a user clicks outside the input box or presses the tab key (i.e., Tab key) to leave the input box, a lose focus event is triggered. Input event: Triggered in real time as the user types in a form element. This event allows the server to respond immediately during the user's input process, such as providing real-time feedback or validation. Submit event: Triggered when a user attempts to submit a form. This is usually triggered by clicking a submit button or pressing the return key (i.e., Enter key); the server can listen to this event to handle the sending of form data or perform pre-submission validation. Invalid event: Triggered when the value of a form element does not meet the validation conditions; this event allows developers to capture invalid input and handle it before the user submits the form.

[0033] Among them, the target event corresponds to the triggering operation. It can be understood that the form includes at least one form element, each form element corresponds to at least one pre-defined form event, and when the form event corresponding to a form element is triggered, this form event is the target event. The target processing method is the business execution logic that the form needs to execute when the target event is triggered. For example, the target processing method may include calling an interface method, running a script method, or a method for interacting with a form (for example, a custom verification method, form pop-up box nesting), etc. The data to be used is the data content required to run the target processing method. In this embodiment, the target event corresponds to one or more target processing methods.

[0034] Specifically, during the form design phase, each form element in the form may correspond to one or more form events, and at least one corresponding processing method may be configured in advance for different form events, and a binding relationship between the form event and the processing method may be established, and each binding point relationship may be stored in a target storage unit. When a user triggers a form event corresponding to any form element in the form, the triggered form event is the target event, and at this time, the target processing method corresponding to the target event and the data to be used required to execute the target processing method may be loaded from each binding relationship in the target storage unit.

[0035] In the first example, during the form design phase, a click form event is configured for form element A, and the target processing method corresponding to the click trigger event is a data storage method that stores all current values ​​in the form in a preset storage unit. Then, a binding relationship between form element A, click form event, and data storage method can be pre-established. During the form application phase, when the user clicks on form element A, the click form event of form element A is the target event, and the pre-configured data storage method (i.e., the target processing method) can be loaded according to the pre-configured binding relationship, and all current values ​​in the form are data to be used.

[0036] In the second example, during the form design phase, a click form event is configured for form element A, and the target processing method corresponding to the click trigger event includes: a target running script that implements a specific operation process, which is the first target processing method, and a second target processing method that further processes the output result of the first target processing method. The data to be used corresponding to the first target processing method are the current element values ​​of form element B and form element C, and the data to be used corresponding to the second target processing method are the output result of the first target processing method, the element values ​​of form element D and form element E. Then, a binding relationship between form element A, the click form event, the first target processing method, the second target processing method, form element B, form element C, form element D, and form element E can be established in advance, and this binding relationship can be stored. In the form application stage, when the user clicks on form element A, the click form event of form element A is the target event. According to the pre-configured binding relationship, the first target processing method and the second target processing method corresponding to the target event can be loaded. According to the binding relationship, the current element values ​​of form element B and form element C can be obtained, which are the data to be used corresponding to the first target processing method, and the element values ​​of form element D and form element F can be obtained, which are part of the data to be used corresponding to the second target processing method.

[0037] S120: Execute a data processing operation corresponding to the target event based on the target processing method and the corresponding data to be used, and obtain a processing result to be verified that is compatible with the target processing method.

[0038] The processing result to be verified is a result used to characterize whether the target processing method is successfully executed. The execution status of the target processing method can be verified by the processing result to be verified. The processing result to be verified may include the target processing result. It should be noted that the target processing method in this step is the first method of at least one target processing method.

[0039] Specifically, on the basis of obtaining the target processing method and the corresponding data to be used, the data to be used is processed and analyzed by the target processing method to obtain the processing results to be verified that are compatible with the target processing method.

[0040] On the basis of the first example above, all current values ​​in the form can be stored in a designated storage unit based on the data storage method, and a "successfully saved" result to be verified can be obtained.

[0041] Based on the above second example, the current element values ​​of form element B and form element C can be used as input parameters of the target running script. After the target running script operates on these two current element values, the output result after the operation is obtained to be verified.

[0042] S130: If the processing result to be verified meets the preset condition, then based on the next target processing method of the target processing method and the corresponding data to be processed, continue to execute the data processing operation corresponding to the target event.

[0043] The preset condition is a pre-set execution rule for determining whether to continue to execute the data processing operation corresponding to the target event. In this embodiment, the preset condition may include: the processing result to be verified includes execution success identification information, or the processing result to be verified includes execution failure identification information.

[0044] In this embodiment, in the case where the number of target processing methods corresponding to the target event is one, after executing the target processing method, the processing result to be verified is obtained. If the processing result to be verified includes success identification information, it indicates that the current target event has been completed (if the target processing result needs to be rendered into the form, the target processing result in the processing result to be verified can be rendered at this time). Based on the above first example, after all current values ​​in the form are successfully stored in the specified storage unit according to the data storage method, the processing result to be verified with the execution success identification information is obtained, indicating that the current target event has been completed.

[0045] In the case where there are multiple target processing methods corresponding to the target event, after executing the target processing method to obtain the processing result to be verified, the next target processing method of the target processing method can be determined based on the binding relationship between the multiple target processing methods. If the processing result to be verified includes success identification information, the target processing result in the processing result to be verified and the data to be processed corresponding to the next target processing method can be used as input parameters so that the next target processing method continues to execute the data processing operation corresponding to the target event based on the input parameters; if the processing result to be verified is failure identification information, the next target processing method can be used to process the data to be processed corresponding to the next target processing method to continue to execute the data processing operation corresponding to the target event.

[0046] On the basis of the above second exemplary embodiment, after executing the first target processing method, a first processing result to be verified including the first target processing result is obtained. If the first processing result to be verified includes success identification information, the first target processing result and the data to be processed corresponding to the second target processing method can be used as input parameters, so that the second target processing method continues to perform the data processing operation corresponding to the target event according to the input parameters; if the first processing result to be verified includes failure identification information, the second target processing method performs the data processing operation according to the corresponding data to be processed.

[0047] S140: Render target display information corresponding to the target event based on the target processing result corresponding to at least the last target processing method among the at least one target processing method.

[0048] The target processing result is the output result obtained after executing the target processing method, for example, the target processing result includes but is not limited to: text string, numerical value, graph, image, etc. The target display information is the display content of the target processing result in the form.

[0049] In this embodiment, the rendering type corresponding to the target event can be pre-configured. For example, the rendering type can include but is not limited to interface return data, prompt interface call information, interactive form (control visibility, cascade, required, check, open, close pop-up window), etc. For each target processing method corresponding to the target event, after the current target processing method is executed and the current target processing result is obtained, the current target processing result can be rendered in the form according to the rendering type corresponding to the target event; it can also be that after all target processing methods are executed, the final target processing result is rendered in the form according to the rendering type corresponding to the target event, that is, the target display information corresponding to the target event is rendered.

[0050] The technical solution provided in this embodiment is that, when designing a form, at least one processing method corresponding to each form event and the corresponding data to be processed are pre-configured. When the form is applied, by responding to the trigger operation of at least one form event, at least one pre-configured target processing method corresponding to the target event and the data to be used corresponding to the at least one target processing method are loaded, and the data processing operation corresponding to the target event is performed based on the target processing method and the corresponding data to be used, and the processing result to be verified that is adapted to the target processing method is obtained. Furthermore, if the processing result to be verified meets the preset conditions, the data processing operation corresponding to the target event is continued to be executed based on the next target processing method of the target processing method and the corresponding data to be processed. Subsequently, the target display information corresponding to the target event can be rendered based on the target processing result corresponding to at least the last target processing method in the at least one target processing method. The technical solution of the present invention splits the complex execution logic of a form event into multiple processing methods, and configures at least one corresponding processing method and corresponding data to be processed for each form event. Since part of the split processing methods are common processing logics and can be reused, users only need to develop running scripts for some processing methods, thereby reducing the design cost of forms with complex execution logic. Furthermore, in this embodiment, the corresponding target processing method and data to be processed are loaded only when the target event is triggered. The same processing method can be repeatedly called by multiple different form events, thereby improving the code reuse rate of the corresponding processing methods of the form events.

[0051] On the basis of the above embodiments, global calling methods and local calling methods may be pre-configured, and at least one global calling method and / or at least one local calling method may be configured for each form event, and a mapping relationship between the form event, all calling identifiers and / or local calling identifiers may be established, so that when a triggering operation on the form event is detected, at least one target processing method may be determined based on the target event corresponding to the triggering operation and the mapping relationship. Accordingly, the present invention proposes the following embodiments: Figure 2 1 is a flow chart of a data processing method provided according to an embodiment of the present invention. Figure 2 As shown, the data processing method comprises the following steps:

[0052] 210. Determine at least one global calling method based on the interface calling information, the running script information and / or the interaction information between the form events, and record the global calling identifier of the global calling method.

[0053] The interface call information is an executable Uniform Resource Locator (URL) used to identify the address of the resource. The running script information is a computer program consisting of a series of instructions and commands, which are used to implement the functions of the data model to be fused. The running script can exist in the form of a text file. Alternatively, the running script information can also be the interface information for calling the execution script. The interaction information between form events is the execution logic required to implement form interaction.

[0054] Among them, the global call method is relative to the local call method. The following will explain in detail what is a global call method and what is a local call method. For a form containing a large number of form events, the execution methods corresponding to some form events are consistent, that is, there are multiple form events corresponding to the same execution method. This execution method can be used as a global call method. Some form events have personalized execution methods. For example, the execution method of some form events is to perform a specific data processing process before executing a certain method. This execution method with personalized execution logic can be used as a local call method. That is, it can be understood that for a form, the global call method is for all form events in the form, and the local call method is for certain specific form events in the form. The global call identifier is the unique identification information corresponding to a global call method.

[0055] In this embodiment, the global call method may include at least three categories, namely: an interface call global method determined according to the interface call information; a script global method determined according to the running script information; and an interactive global method determined according to the interactive information. Since the interface call information may be included in a variety of different interfaces, the running script information may include a variety of different script contents, and the interactive information between form events may include a variety of different interactive logics, based on this, multiple global call methods may be determined, and the corresponding unique identification information may be determined for each global call method as a global call identification.

[0056] Specifically, determining the specific implementation method of at least one global calling method based on the interface calling information, the running script information and / or the interaction information between the form events may include: determining the method name of the global calling method, the uniform resource locator corresponding to the interface calling information, the execution status feedback information, the input parameter description and / or the output parameter description based on the interface calling information; and / or determining the method name, the script running type, the input parameters, the input parameter description and / or the output parameter description of the global calling method based on the running script information; determining the event calling parameters in the global calling method based on the interaction information between the form events.

[0057] Among them, the execution status feedback information is used to indicate in what form the execution status of a certain global call method is fed back after the execution of the method, that is, it can be understood as being used to characterize whether the global call method is successfully executed. For example, the execution status feedback information can be a request status code or an execution flag, etc. Input parameters refer to the data that the global call method needs to receive, and these data are used to affect the behavior or output results of the global call method. Input parameters can be of various types, including but not limited to numerical values, strings, file paths, etc., which are passed according to requirements to start or affect certain functions of the global call method. Input parameter description is the characteristic description information of the input parameters, which is used to explain the input parameters. Output parameters are data that can be obtained after running the global call method. Output parameter description is the characteristic description information of the output parameters, which is used to explain the output parameters. Script running types include running scripts or script calling interfaces. The input parameters are input parameters. Event call parameters refer to additional information passed to the global call method when an event is triggered, which can help the global call method understand the context of the event or perform some additional operations.

[0058] In this embodiment, when defining a global call method, it is necessary to make the global call method contain specific content information so that the content information can be used when calling the global method. Specifically, when determining the interface call global method, the interface call information to be called can be determined according to the actual business needs, so that the method name, uniform resource locator, execution status feedback information, input parameter description and / or output parameter description corresponding to the interface call global method can be defined according to the interface call information. Based on the same way, multiple different interface call global methods can be defined according to actual business needs. When determining the script global method, the running script information to be executed can also be determined according to the actual business needs. Thus, the method name, input parameter, input parameter description and / or output parameter description corresponding to the script global method can be defined according to the running script information. In addition, if the script running type is the running script, the specific code program of the running script needs to be configured. If the script running type is the script calling interface, the script calling interface uniform resource locator needs to be configured. Based on the same way, multiple different script global methods can be defined according to actual business needs. When determining the interactive global method, the interactive logic that needs to be executed can also be determined according to actual business needs, that is, the interactive information between form events. Therefore, the event call parameters can be configured according to the interactive information between the form events. Optionally, the method name, execution status feedback information, input parameter description and / or output parameter description of the interactive global method can also be defined. Based on the same method, multiple different interactive global methods can be defined according to actual business needs.

[0059] It is understandable that in actual applications, commonly used interface call global methods, script global methods and interactive global methods can be pre-defined and stored. When designing a specific form, if some pre-defined global call methods are needed, there is no need to repeatedly reconfigure the global call methods, and you can select from the pre-defined multiple commonly used global methods.

[0060] In this embodiment, through pre-set rules, the global calling method of the interface calling class, the global calling method of the running script class and / or the global calling method of the interaction class between form events can be configured. Since a variety of different types of global calling methods can be configured, the flexibility of configuring the global method is improved and the scope of application of the global calling method is expanded.

[0061] 220. Configure at least one local call method based on the local configuration component, and determine a local call identifier of the local call method.

[0062] In this embodiment, the local configuration component is a processing unit for configuring a local call method. For a form containing a large number of form events, some form events have personalized execution methods. Such execution methods with personalized execution logic can be used as a local call method, that is, the local call method is for certain specific form events in the form. The local call identifier is the unique identification information corresponding to the local call method.

[0063] Specifically, in the case where a personalized execution method needs to be configured, one or more local call methods can be defined in the local configuration component, and a local call identifier can be defined for each local call method. For example, the local call method can include: local method name, local parameter name, local parameter value, and setting information of whether the local parameter value covers the preset binding value, etc.

[0064] 230. Configure at least one global calling method and / or at least one local calling method for each form event, and establish a mapping relationship between the form event, the global calling identifier and / or the local calling identifier, so that when a triggering operation on the form event is detected, at least one target processing method is determined based on the target event corresponding to the triggering operation and the mapping relationship.

[0065] In this embodiment, any form event is taken as an example for explanation. If the current form event does not require a personalized execution process, a global call method can be configured for it according to the business needs of the current form event. On this basis, if a global call method can meet the business function of the current form event, a corresponding global call method is configured for the current form event; if a global call method cannot meet the business function of the current form event, multiple global call methods can be configured for the current form event, and the nested relationship between the multiple global call methods is determined. If the current form event requires a personalized execution process, then on the basis of configuring a global call method for it according to the business needs of the current form event, one or more local call methods are further configured for it. After completing the method configuration of the current form event, a mapping relationship between the current form event, the global call identifier of at least one global call method corresponding thereto, and / or the local call identifier of at least one local call method corresponding thereto can be established, and the method configuration of each form event is performed based on the same configuration method. Therefore, when a form event is triggered, the pre-stored mapping relationship is queried according to the triggered target event to determine at least one global calling method and / or at least one local calling method corresponding to the target event, that is, to obtain at least one target processing method.

[0066] In this embodiment, since each global calling method and each local calling method are independent and callable methods, by configuring a corresponding global calling method and / or local calling method for each form event, it is possible to flexibly configure implementation methods for form events with complex execution processes. Moreover, the same processing method can be repeatedly called by multiple different form events, thereby improving the reuse rate of global calling methods and local calling methods.

[0067] On the basis of the above technical solution, after configuring at least one global calling method and / or at least one local calling method for each form event, the method also includes: configuring an operation method for the global calling method and / or the local calling method to call the corresponding global calling method or local calling method based on the operation method to process the corresponding data to be used.

[0068] The operation method may be understood as the calling logic between the global calling method and / or the local calling method corresponding to a form event during the specific execution process.

[0069] In this embodiment, for certain form events with complex execution logic, since such form events correspond to multiple global calling methods and multiple local point-use methods, it is necessary to configure operation methods for the global calling methods and / or local calling methods so that each calling method can be smoothly executed during the specific execution process, thereby improving the response speed of the form event.

[0070] For example, a form event corresponds to three global call methods, namely the first global method, the second global method, and the third global method. The form event also corresponds to two local call methods, namely the first local method and the second local method. For example, see the diagram of the operation methods configured for these methods. Figure 3 ,like Figure 3 As shown, the operation method is: trigger form event -> first local method -> first global method -> if the first global method is executed successfully -> second global method -> end; and, trigger form event -> first local method -> first global method -> if the first global method fails to execute -> third global method -> second local method -> end. It can be seen that for such a form event with complex execution logic (i.e., a form including multiple global call methods and multiple local point-use methods), by configuring the operation method for the global call method and / or the local call method, each call method can be efficiently executed in the specific execution process, thereby improving the response speed of the form event.

[0071] 240. In response to a triggering operation on at least one form event, load at least one pre-configured target processing method corresponding to the target event and to-be-used data corresponding to the at least one target processing method.

[0072] Among them, the target event corresponds to the triggering operation.

[0073] 250. Perform a data processing operation corresponding to the target event based on the target processing method and the corresponding data to be used, and obtain a processing result to be verified that is compatible with the target processing method.

[0074] 260. If the processing result to be verified meets the preset condition, then based on the next target processing method of the target processing method and the corresponding data to be processed, continue to execute the data processing operation corresponding to the target event.

[0075] 270. Render target display information corresponding to the target event based on the target processing result corresponding to at least the last target processing method among the at least one target processing method.

[0076] The technical solution provided in this embodiment pre-configures global calling methods and local calling methods, configures at least one global calling method and / or at least one local calling method for each form event, and establishes a mapping relationship between form events, all calling identifiers and / or local calling identifiers. Since each global calling method and each local calling method are independent and callable methods, by configuring a corresponding global calling method and / or local calling method for each form event, it is possible to flexibly configure implementation methods for form events with complex execution processes, thereby improving the reuse rate of form event processing methods.

[0077] On the basis of the above embodiments, when it is detected that the form rendering condition is met, the configuration method of the target form can be loaded into the target memory; further, in response to the triggering operation of at least one form event, at least one target processing method of the target event corresponding to the triggering operation and the to-be-used data corresponding to the target processing method are determined from the memory; in addition, according to the target rendering type corresponding to the target event, the to-be-verified processing result corresponding to the at least one target processing method can be obtained, and the form corresponding to the target event can be rendered according to the to-be-verified processing result to obtain the target display information. Accordingly, the present invention proposes the following embodiments: Figure 4 1 is a flow chart of a data processing method provided according to an embodiment of the present invention. Figure 4 As shown, the data processing method comprises the following steps:

[0078] 310. When it is detected that the form rendering condition is met, a global calling method and / or a local calling method associated with at least one form event in the target form is loaded into a target memory corresponding to the target form, so as to obtain a target processing method corresponding to the target event from the memory.

[0079] The form rendering condition is a pre-set rule used to determine whether the target form needs to be rendered. For example, the form rendering condition may be detecting a trigger operation on the "Start" control of the target form, detecting a trigger operation on a link corresponding to the target form, etc. The target form is the form to be rendered and its form events are monitored. The target memory is a storage container for temporarily storing global call methods and / or local call methods.

[0080] In this embodiment, when a user triggers a "start" control corresponding to a form on a terminal device or clicks a link corresponding to a form, the form is the target form. Since the configuration information of the target form (i.e., the global call method and / or the local call method) is configured in the form design stage, these configuration information can be pre-stored on the server side. Based on this, the configuration information corresponding to the target form can be loaded from the server side into the specific storage space (i.e., the target memory) of the terminal device, and the homepage of the target form can be rendered on the display page of the terminal device. The purpose of this setting is to load the global call method and / or the local call method corresponding to the target form from the server side into the local memory of the user's terminal device, so that when these methods are called later, the calling time can be shortened and the efficiency of determining the output result of the target form can be improved.

[0081] 320. In response to a trigger operation on at least one form event, determine from a memory at least one target processing method of a target event corresponding to the trigger operation and data to be used corresponding to the target processing method.

[0082] The target processing method is a method in the global calling method and / or the local calling method. The memory can be a memory unit of the server or a local memory of the user terminal device.

[0083] In this embodiment, on the basis of rendering the target form on the display page of the user terminal device, when the user triggers the form event of any form element in the target form, if the configuration information corresponding to the target form has been loaded into the local memory of the user terminal device, at least one target processing method of the target event and the data to be used corresponding to the target processing method can be obtained from the local memory according to the identification information of the form event. In particular, if the configuration information corresponding to the target form has not been loaded into the local memory of the user terminal device, the configuration information corresponding to the target event can be obtained from the memory unit of the server according to the identification information of the form event. The advantage of such a setting is that the target processing methods of each form event corresponding to the target form are stored in the memory. When a form event is triggered, the target processing method corresponding to the target event is determined from the memory, and the target processing method and the data to be processed corresponding to the target event can be accurately matched.

[0084] 330. Perform a data processing operation corresponding to the target event based on the target processing method and the corresponding data to be used, and obtain a processing result to be verified that is compatible with the target processing method.

[0085] 340. If the processing result to be verified is in a preset state and there is a next target processing method associated with the target processing method, the data to be used and the processing result to be verified corresponding to the next target processing method are obtained as input parameters of the target processing method.

[0086] The preset state is the pre-set state information of the processing result to be verified. In this embodiment, the preset state is that the processing result to be verified includes the execution success state. In this embodiment, the data to be used includes the binding method parameters corresponding to the global call method and / or the distinguishing parameters corresponding to the local call method.

[0087] In this embodiment, when there are multiple target processing methods corresponding to the target event, after executing the target processing method to obtain the target output result and the processing result to be verified, the next target processing method associated with the target processing method can be determined according to the binding relationship between the multiple target processing methods. If the processing result to be verified includes the execution success status, the target output result and the data to be processed corresponding to the next target processing method can be used as input parameters. The purpose of this setting is to verify the processing result to be verified and determine the input parameters of the next target processing method according to the verification result. Since different verification results can correspond to different processing methods, the corresponding input parameters are determined for different processing methods, thereby ensuring the consistency when executing each target processing method.

[0088] 350. After processing the input parameters according to the input parameter description information corresponding to the next target processing method, the input parameters are input to the next target processing method to continue to execute the data processing operation corresponding to the target event.

[0089] The input parameter description information is the description information of the input parameters required to execute the next target processing method.

[0090] In this embodiment, the input parameter description information may include at least one of: a binding method parameter corresponding to a global calling method, a distinguishing parameter corresponding to a local calling method, and a current value of a table element specified by a next target processing method.

[0091] In this embodiment, the data content required to execute the next target processing method can be determined based on the input parameter description information, so that the required data content (including input parameters, and / or the current value of the table element specified by the next target processing method) can be spliced ​​according to the input parameter description information to obtain all the input parameters required to execute the next target processing method, and then all the input parameters are input into the next target processing method to continue to execute the data processing operation corresponding to the target event.

[0092] 360. According to the target rendering type corresponding to the target event, obtain a processing result to be verified corresponding to at least one target processing method, and render the form corresponding to the target event according to the processing result to be verified to obtain target display information.

[0093] The processing results to be verified include at least the target processing results output by the last target processing method. The target rendering type is the output result rendering method pre-configured for the target event. The rendering type can include: echo interface return data, prompt interface call information, interactive form (control visibility, cascade, required, check, open, close pop-up window), etc.

[0094] In this embodiment, the target rendering type corresponding to the target event is pre-configured. For the situation where there are multiple target processing methods, if the corresponding target rendering type is configured in advance for each target processing method, then each time a target processing method is executed, the target output result in the to-be-verified processing result obtained by the current method can be rendered according to the corresponding target rendering type to obtain one of the target display information of the target event; if the target rendering type is only configured in advance for the last one of the multiple target processing methods, then after all the target processing methods are executed, the form can be rendered according to the target processing result and target rendering type output by at least the last target processing method to obtain the final target display information. The advantage of such a setting is that by pre-configuring the corresponding target rendering type for the form event, the effect of personalized rendering of the form can be achieved, which improves the richness of the form display content.

[0095] Based on the above embodiment, the method further includes: when the processing result to be verified corresponding to at least one target processing method is display information of other form events, rendering the result to be verified onto other form events and displaying it.

[0096] In this embodiment, if there is a target processing method whose to-be-verified processing result is the display information of other form events, in this case, after the target processing method is executed and the to-be-verified processing result is obtained, the to-be-verified processing result is rendered to the corresponding other form event and displayed on the form display page. The purpose of this setting is to accurately render the target processing result at the specified form position, further improving the richness of the form display.

[0097] Exemplarily, the first processing result to be verified corresponding to the first target processing method corresponding to form event A is pre-defined as the display information of form event B. When form event A is triggered and the first target processing method is executed to obtain the first processing result to be verified, the target processing result in the first processing result to be verified can be rendered on the form element corresponding to form event B.

[0098] Next, the data processing method of this embodiment is described with a specific example. Figure 5 .

[0099] like Figure 5 As shown, in the target form design stage, configuration information corresponding to each form event is predetermined, wherein the configuration information includes at least one target processing method, each target processing room includes a global calling method and / or a local calling method, and the configuration information includes the data to be processed corresponding to the target processing method.

[0100] In the target form application stage, when the user clicks the "Start" control of the target form on the terminal device, the homepage of the target form can be rendered on the display page of the terminal device, and the configuration information corresponding to the target form can be loaded into the local memory of the terminal device. Subsequently, the trigger event of at least one table element in the target form is monitored. When a table event is triggered, this table event is the target event. Further, the target processing method and the data to be processed corresponding to the target event can be determined from the local memory according to the identification information corresponding to the target event, which can specifically include: first, determining at least one target processing method corresponding to the target event through the identification information corresponding to the target event, then, by parsing the configured target processing method (for example, traversing the global method configuration tree, finding the leaf node with the binding field identification), obtaining the input and output parameters, and the event identification information of other form events bound to the corresponding parameters, after obtaining the event identification information, the current display value can be obtained according to the event identification information (the target form provides a method that can obtain its current display value according to the event identification information), and these parameters are collectively referred to as global binding parameters; finally, if the target processing method includes a local call method, the custom parameters configured in the local call method can be obtained from the local memory, and the custom parameters and the global binding parameters are spliced ​​(the parameter splicing logic is also configured in the custom method configuration content), and the data to be processed that needs to be passed to the target processing method is obtained. Further, the target processing method executes the corresponding processing logic according to the received data to be processed to obtain the processing result to be verified. At this time, regardless of whether the target processing method is successfully executed, the target processing result in the processing result to be verified can be rendered in the target form. Then, determine whether there is a next target processing method associated with the current target processing method. If not, it indicates that the execution process corresponding to the target event has ended. If it exists and the current target processing method is successfully executed, call the next target execution method from the local memory, and use the target processing result after the current target processing method is executed as one of the input parameters of the next target processing method, and obtain the data to be processed corresponding to the next target processing method from the local memory, and then execute the next target processing method; if it exists and the current target processing method fails to execute, call the next target execution method and the corresponding data to be processed from the local memory, and then execute the next target processing method. Until all target processing methods are executed.

[0101] The technical solution provided in this embodiment is to load the global call method and / or local call method corresponding to the target form from the server to the local memory of the user terminal device, so that when these methods are called later, the call time can be shortened and the efficiency of determining the output result of the target form can be improved; further, in response to the triggering operation of at least one form event, at least one target processing method of the target event corresponding to the triggering operation and the data to be used corresponding to the target processing method are determined from the memory, and the target processing methods of each form event corresponding to the target form are stored in the memory. When a form event is triggered, the target processing method corresponding to the target event is determined from the memory, and the target processing method and the data to be processed corresponding to the target event can be accurately matched. In addition, according to the target rendering type corresponding to the target event, the to-be-verified processing result corresponding to at least one target processing method can be obtained, and the form corresponding to the target event can be rendered according to the to-be-verified processing result to obtain the target display information. By pre-configuring the corresponding target rendering type for the form event, the effect of personalized form rendering can be efficiently achieved, and the richness of the form display content can be improved.

[0102] Figure 6 Schematic diagram of a data processing device according to an embodiment of the present invention. Figure 6 As shown, the device includes: an event triggering module 410, a processing result determining module 420, a method continuing execution module 430 and a display information determining module 440.

[0103] The event triggering module 410 is used to load at least one pre-configured target processing method corresponding to the target event and the to-be-used data corresponding to the at least one target processing method in response to a triggering operation on at least one form event; wherein the target event corresponds to the triggering operation;

[0104] A processing result determination module 420 is used to perform a data processing operation corresponding to the target event based on the target processing method and the corresponding data to be used, and obtain a processing result to be verified that is compatible with the target processing method;

[0105] A method continuing execution module 430, configured to continue executing the data processing operation corresponding to the target event based on the next target processing method of the target processing method and the corresponding data to be processed if the processing result to be verified meets a preset condition;

[0106] The display information determination module 440 is configured to render target display information corresponding to the target event based on a target processing result corresponding to at least the last target processing method in at least one target processing method.

[0107] The technical solution of this embodiment is that in the embodiment of the present invention, when designing a form, at least one processing method corresponding to each form event and the corresponding data to be processed are pre-configured. When the form is applied, by responding to the trigger operation of at least one form event, at least one pre-configured target processing method corresponding to the target event and the data to be used corresponding to the at least one target processing method are loaded, and the data processing operation corresponding to the target event is performed based on the target processing method and the corresponding data to be used, and the processing result to be verified that is adapted to the target processing method is obtained. Then, if the processing result to be verified meets the preset conditions, the data processing operation corresponding to the target event is continued to be executed based on the next target processing method of the target processing method and the corresponding data to be processed. Subsequently, the target display information corresponding to the target event can be rendered based on the target processing result corresponding to at least the last target processing method in the at least one target processing method. The technical solution of the present invention splits the complex execution logic of a form event into multiple processing methods, and configures at least one corresponding processing method and corresponding data to be processed for each form event. Since part of the split processing methods are common processing logics and can be reused, users only need to develop running scripts for some processing methods, thereby reducing the design cost of forms with complex execution logic. Furthermore, in this embodiment, the corresponding target processing method and data to be processed are loaded only when the target event is triggered. The same processing method can be repeatedly called by multiple different form events, thereby improving the code reuse rate of the corresponding processing methods of the form events.

[0108] Based on the above device, optionally, the device further includes: a data configuration module. The data configuration module includes:

[0109] A global method determination unit, used to determine at least one global calling method according to the interface calling information, the running script information and / or the interaction information between the form events, and record the global calling identifier of the global calling method;

[0110] A local method determination unit, configured to configure at least one local call method based on the local configuration component, and determine a local call identifier of the local call method;

[0111] A method mapping unit is used to configure at least one global call method and / or at least one local call method for each form event, and to establish a mapping relationship between the form event, the global call identifier and / or the local call identifier, so as to determine at least one target processing method based on the target event corresponding to the trigger operation and the mapping relationship when a trigger operation on the form event is detected.

[0112] Based on the above device, optionally, the global method determination unit includes:

[0113] Specifically used to determine the method name of the global calling method, the uniform resource locator corresponding to the interface calling information, the execution status feedback information, the input parameter description and / or the output parameter description based on the interface calling information; and / or, the global method determination unit is used to determine the method name, the script running type, the input parameters, the input parameter description and / or the output parameter description of the global calling method based on the running script information, wherein the script running type includes running the script or the script calling interface; and determine the event calling parameters in the global calling method based on the interaction information between the form events.

[0114] Based on the above device, optionally, the data configuration module further includes:

[0115] The method configuration unit is used to configure an operation method for the global calling method and / or the local calling method, so as to call the corresponding global calling method or the local calling method based on the operation method to process the corresponding data to be used.

[0116] Based on the above device, optionally, the device further includes: a data loading module. The data loading module is used to load the global calling method and / or local calling method associated with at least one form event in the target form into the target memory corresponding to the target form when detecting that the form rendering condition is met, so as to obtain the target processing method corresponding to the target event from the memory.

[0117] Based on the above-mentioned device, optionally, the event trigger module 410 is specifically used to determine from the memory at least one target processing method of the target event corresponding to the trigger operation and the data to be used corresponding to the target processing method in response to the trigger operation of at least one form event; wherein the target processing method is a method in the global call method and / or the local call method.

[0118] Based on the above device, optionally, the method continues to execute module 430, including:

[0119] An input parameter determination unit, configured to obtain the to-be-used data and the to-be-verified processing result corresponding to the next target processing method as input parameters of the target processing method if the to-be-verified processing result is in a preset state and there is a next target processing method associated with the target processing method;

[0120] The method continuation execution unit is used to process the input parameters according to the input parameter description information corresponding to the next target processing method, and then input them into the next target processing method to continue to execute the data processing operation corresponding to the target event.

[0121] On the basis of the above-mentioned device, optionally, the display information determination module 440 is specifically used to obtain the processing result to be verified corresponding to at least one target processing method according to the target rendering type corresponding to the target event, and render the form corresponding to the target event according to the processing result to be verified to obtain the target display information; wherein the processing result to be verified includes at least the target processing result output by the last target processing method.

[0122] Based on the above device, optionally, the device further comprises: a result rendering module. The result rendering module is used to render and display the result to be verified on other form events when the result to be verified corresponding to at least one target processing method is display information of other form events.

[0123] The data processing device provided in the embodiment of the present invention can execute the data processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0124] Figure 7 The present invention is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Figure 7 A block diagram of an exemplary electronic device 50 suitable for implementing exemplary embodiments of the present invention is shown. Figure 7 The electronic device 50 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0125] like Figure 7 As shown, the electronic device 50 is in the form of a general computing device. The components of the electronic device 50 may include but are not limited to: one or more processors or processing units 501, a system memory 502, and a bus 503 connecting different system components (including the system memory 502 and the processing unit 501).

[0126] Bus 503 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0127] The electronic device 50 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 50, including volatile and non-volatile media, removable and non-removable media.

[0128] System memory 502 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 504 and / or cache memory 505. Electronic device 50 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 506 may be used to read and write non-removable, non-volatile magnetic media ( Figure 7 not shown, usually called a "hard drive"). Although Figure 7 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 503 via one or more data medium interfaces. The memory 502 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the embodiments of the present invention.

[0129] A program / utility 508 having a set (at least one) of program modules 507 may be stored, for example, in the memory 502, such program modules 507 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 507 generally perform the functions and / or methods of the embodiments described herein.

[0130] The electronic device 50 may also communicate with one or more external devices 509 (e.g., keyboards, pointing devices, displays 510, etc.), may communicate with one or more devices that enable a user to interact with the electronic device 50, and / or communicate with any device that enables the electronic device 50 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). Such communication may be performed through an input / output (I / O) interface 511. Furthermore, the electronic device 50 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 512. As shown, the network adapter 512 communicates with other modules of the electronic device 50 through the bus 503. It should be understood that although Figure 7 Not shown, other hardware and / or software modules may be used in conjunction with the electronic device 50, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0131] The processing unit 501 executes various functional applications and data processing based on streaming processing by running the programs stored in the system memory 502, for example, implementing the data processing method provided in the embodiment of the present invention.

[0132] An embodiment of the present invention further provides a storage medium containing computer executable instructions, and when the computer executable instructions are executed by a computer processor, they are used to perform a data processing method, the method comprising:

[0133] In response to a trigger operation on at least one form event, loading at least one pre-configured target processing method corresponding to the target event and data to be used corresponding to the at least one target processing method; wherein the target event corresponds to the trigger operation;

[0134] Based on the target processing method and the corresponding data to be used, a data processing operation corresponding to the target event is performed to obtain a processing result to be verified that is compatible with the target processing method;

[0135] If the processing result to be verified meets the preset condition, then based on the next target processing method of the target processing method and the corresponding data to be processed, continue to execute the data processing operation corresponding to the target event;

[0136] Rendering target display information corresponding to the target event based on a target processing result corresponding to at least a last target processing method in at least one target processing method.

[0137] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0138] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0139] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0140] Computer program code for performing the operation of embodiments of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0141] An embodiment of the present invention further provides a computer program product, including a computer program, which, when executed by a processor, implements the data processing method provided in any embodiment of the present application.

[0142] In the process of implementation, the computer program product can be written in one or more programming languages ​​or a combination thereof to perform the computer program code of the present invention, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).

[0143] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A data processing method, characterized in that: include: In response to a trigger operation on at least one form event, loading at least one pre-configured target processing method corresponding to the target event and data to be used corresponding to the at least one target processing method; wherein the target event corresponds to the trigger operation; Based on the target processing method and the corresponding data to be used, a data processing operation corresponding to the target event is performed to obtain a processing result to be verified that is compatible with the target processing method; If the processing result to be verified meets the preset condition, then based on the next target processing method of the target processing method and the corresponding data to be processed, continue to execute the data processing operation corresponding to the target event; Rendering target display information corresponding to the target event based on a target processing result corresponding to at least a last target processing method in at least one target processing method.

2. The method according to claim 1, characterized in that The method further comprises: Determine at least one global calling method according to the interface calling information, the running script information and / or the interaction information between the form events, and record the global calling identifier of the global calling method; Configure at least one local call method based on the local configuration component, and determine a local call identifier of the local call method; At least one global calling method and / or at least one local calling method is configured for each form event, and a mapping relationship between the form event, the global calling identifier and / or the local calling identifier is established, so that when a triggering operation on the form event is detected, the at least one target processing method is determined based on the target event corresponding to the triggering operation and the mapping relationship.

3. The method according to claim 2, characterized in that Determining at least one global calling method based on the interface calling information, the running script information and / or the interactive information between the form events includes: Determine, based on the interface call information, the method name of the global call method, the uniform resource locator corresponding to the interface call information, the execution status feedback information, the input parameter description and / or the output parameter description; and / or, Determine the method name, script running type, input parameter, input parameter description and / or output parameter description of the global calling method according to the running script information, wherein the script running type includes running script or script calling interface; The event calling parameters in the global calling method are determined according to the interactive information between the form events.

4. The method according to claim 2 or 3, characterized in that: After configuring at least one global calling method and / or at least one local calling method for each form event, the method further includes: An operation method is configured for the global calling method and / or the local calling method, so as to call the corresponding global calling method or the local calling method based on the operation method to process the corresponding data to be used.

5. The method according to claim 1, characterized in that The method further comprises: When it is detected that the form rendering condition is met, a global calling method and / or a local calling method associated with at least one form event in a target form is loaded into a target memory corresponding to the target form, so as to obtain a target processing method corresponding to the target event from the memory.

6. The method according to claim 1, characterized in that The step of loading, in response to a triggering operation on at least one form event, at least one pre-configured target processing method corresponding to the target event and data to be used corresponding to the at least one target processing method comprises: In response to a trigger operation on at least one form event, determining from a memory at least one target processing method of a target event corresponding to the trigger operation and data to be used corresponding to the target processing method; The target processing method is a method in a global calling method and / or a local calling method.

7. The method according to claim 1, characterized in that If the processing result to be verified meets the preset condition, then based on the next target processing method of the target processing method and the corresponding data to be processed, continue to perform the data processing operation corresponding to the target event, including: If the processing result to be verified is in a preset state and there is a next target processing method associated with the target processing method, then obtaining the to-be-used data corresponding to the next target processing method and the processing result to be verified as input parameters of the target processing method; After the input parameters are processed according to the input parameter description information corresponding to the next target processing method, they are input into the next target processing method to continue to execute the data processing operation corresponding to the target event.

8. The method according to claim 1, characterized in that The rendering of target display information corresponding to the target event based on the target processing result corresponding to at least the last target processing method in at least one target processing method includes: According to the target rendering type corresponding to the target event, obtaining a to-be-verified processing result corresponding to at least one target processing method, and rendering the form corresponding to the target event according to the to-be-verified processing result to obtain target display information; The processing results to be verified include at least the target processing result output by the last target processing method.

9. The method according to claim 1 or 8, characterized in that: The method further comprises: When the processing result to be verified corresponding to at least one target processing method is display information of other form events, the result to be verified is rendered on the other form events and displayed.

10. A data processing device, characterized in that: include: An event triggering module, configured to load, in response to a triggering operation on at least one form event, at least one pre-configured target processing method corresponding to the target event and data to be used corresponding to the at least one target processing method; wherein the target event corresponds to the triggering operation; A processing result determination module, used to perform a data processing operation corresponding to the target event based on the target processing method and the corresponding data to be used, and obtain a processing result to be verified that is compatible with the target processing method; A method continuing execution module, used for continuing to execute the data processing operation corresponding to the target event based on the next target processing method of the target processing method and the corresponding data to be processed if the processing result to be verified meets the preset condition; The display information determination module is used to render target display information corresponding to the target event based on a target processing result corresponding to at least the last target processing method in at least one target processing method.

11. The device according to claim 10, characterized in that The device further comprises: a data configuration module; the data configuration module comprises: A global method determination unit, used to determine at least one global calling method according to the interface calling information, the running script information and / or the interaction information between the form events, and record the global calling identifier of the global calling method; A local method determination unit, configured to configure at least one local call method based on the local configuration component, and determine a local call identifier of the local call method; A method mapping unit is used to configure at least one global calling method and / or at least one local calling method for each form event, and to establish a mapping relationship between the form event, the global calling identifier and / or the local calling identifier, so as to determine the at least one target processing method based on the target event corresponding to the triggering operation and the mapping relationship when a triggering operation on the form event is detected.

12. The device according to claim 11, characterized in that The data configuration module further includes: a method configuration unit; The method configuration unit is used to configure an operation method for the global calling method and / or the local calling method, so as to call the corresponding global calling method or the local calling method based on the operation method to process the corresponding data to be used.

13. An electronic device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the data processing method according to any one of claims 1 to 9 when executing the computer program.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the data processing method as described in any one of claims 1 to 9 is implemented.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the data processing method according to any one of claims 1 to 9.

Images