Data processing method and related device

Abstract

The present disclosure provides a data processing method and a related device. The method comprises: in response to a plug-in invocation request for a target plug-in, acquiring plug-in configuration data of the target plug-in, wherein the target plug-in is used for generating a target field in a table; generating a configuration form on the basis of description data in the plug-in configuration data; in response to receiving form data of the configuration form, generating field configuration data of the target field on the basis of the form data and template data in the plug-in configuration data; and generating target field content of the target field on the basis of the field configuration data.

Description

Data processing method and related device

[0001] Cross-reference to related applications

[0002] The present application claims priority to the Chinese Patent Application No. 202410796350.7, filed on June 19, 2024, and entitled "A data processing method and related device", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present disclosure relates to the technical field of computer, and particularly relates to a data processing method and related device. BACKGROUND

[0004] Tables often need to process and analyze data content in the tables. SUMMARY

[0005] In a first aspect, the present disclosure provides a data processing method, comprising:

[0006] In response to a plug-in call request for a target plug-in, obtaining plug-in configuration data of the target plug-in; the target plug-in is used to generate a target field in a table;

[0007] Generating a configuration form based on description data in the plug-in configuration data;

[0008] In response to receiving form data of the configuration form, generating field configuration data of the target field based on the form data and template data in the plug-in configuration data;

[0009] Generating target field content of the target field based on the field configuration data.

[0010] In a second aspect, the present disclosure provides a data processing method, comprising:

[0011] In response to receiving a plug-in debugging request for a target plug-in, creating a debugging plug-in of the target plug-in; the target plug-in is used to generate a target field in a table;

[0012] In response to a debugging call request for the debugging plug-in, obtaining debugging configuration data of the debugging plug-in;

[0013] Generating a debugging configuration form based on description data in the debugging configuration data;

[0014] In response to receiving debugging data of the debugging configuration form, generating a test result of the target plug-in.

[0015] In a third aspect, the present disclosure provides a data processing device, comprising:

[0016] The first obtaining module is configured to obtain plug-in configuration data of a target plug-in in response to a plug-in calling request for the target plug-in, wherein the target plug-in is configured to generate a target field in a table.

[0017] The first configuration module is configured to generate a configuration form based on description data in the plug-in configuration data.

[0018] The target field module is configured to generate field configuration data of the target field based on template data in the plug-in configuration data and form data of the configuration form in response to receiving the form data of the configuration form.

[0019] The field content module is configured to generate target field content of the target field based on the field configuration data.

[0020] The fourth aspect of the present disclosure provides a data processing apparatus, comprising:

[0021] The creation module is configured to create a debugging plug-in of a target plug-in in response to receiving a plug-in debugging request for the target plug-in, wherein the target plug-in is configured to generate a target field in a table.

[0022] The second obtaining module is configured to obtain debugging configuration data of the debugging plug-in in response to a debugging calling request for the debugging plug-in.

[0023] The second configuration module is configured to generate a debugging configuration form based on description data in the debugging configuration data.

[0024] The debugging module is configured to generate a test result of the target plug-in in response to receiving debugging data of the debugging configuration form.

[0025] The fifth aspect of the present disclosure provides an electronic device, comprising one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and executed by the one or more processors, and the programs comprise instructions for executing the method according to the first aspect or the second aspect.

[0026] The sixth aspect of the present disclosure provides a non-volatile computer readable storage medium containing a computer program, which, when executed by one or more processors, causes the processors to execute the method according to the first aspect or the second aspect.

[0027] The fifth aspect of the present disclosure provides a computer program product comprising computer program instructions, which, when executed on a computer, cause the computer to execute the method according to the first aspect. BRIEF DESCRIPTION OF DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the present disclosure or the related art, the drawings needed to be used in the embodiments or the related description will be briefly introduced. Obviously, the drawings in the following description are only embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without any creative effort based on these drawings.

[0029] FIG. 1 is a schematic diagram of a data processing architecture according to an embodiment of the present disclosure.

[0030] FIG. 2 is a schematic diagram of a hardware structure of an exemplary electronic device according to an embodiment of the present disclosure.

[0031] FIG. 3 is a schematic flowchart of a data processing method according to an embodiment of the present disclosure.

[0032] FIG. 4 is a schematic diagram of a search target plug-in according to an embodiment of the present disclosure.

[0033] FIG. 5 is a schematic diagram of obtaining specified version data of a target plug-in according to an embodiment of the present disclosure.

[0034] FIG. 6 is a schematic diagram of an application principle of a target plug-in according to an embodiment of the present disclosure.

[0035] FIG. 7 is a schematic flowchart of a data processing method according to an embodiment of the present disclosure. FIG. 8 is a schematic diagram of a development principle of a target plug-in according to an embodiment of the present disclosure.

[0036] FIG. 9 is a schematic diagram of an auditing and deployment principle of a target plug-in according to an embodiment of the present disclosure.

[0037] FIG. 10 is a schematic diagram of a data processing apparatus according to an embodiment of the present disclosure.

[0038] FIG. 11 is a schematic diagram of a data processing apparatus according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solutions and advantages of the present disclosure clearer, the present disclosure will be further described in detail below with reference to specific embodiments and drawings.

[0040] It should be noted that, unless otherwise defined, technical terms or scientific terms used in the embodiments of the present disclosure shall have the common meaning understood by one of ordinary skill in the art to which the present disclosure pertains. The terms “first”, “second”, and similar terms used in the embodiments of the present disclosure do not denote any order, quantity, or importance, but are merely used to distinguish different components. The terms “include”, “contain”, and similar terms mean that the elements or objects before the terms encompass the elements or objects listed after the terms and their equivalents, and do not exclude other elements or objects. The terms “connect” or “connected” or similar terms do not limit to physical or mechanical connections, but can include electrical connections, whether direct or indirect. The terms “upper”, “lower”, “left”, “right”, and the like are merely used to indicate relative positional relationships, and when the absolute positions of the described objects are changed, the relative positional relationships can also be changed accordingly.

[0041] It can be understood that, before using the technical solutions disclosed in the embodiments of the present disclosure, the type of personal information involved in the present disclosure, the use range, the use scenario, and the like should be informed to the user and the authorization of the user should be obtained in a proper manner according to relevant laws and regulations.

[0042] For example, in response to receiving the active request of the user, prompt information is sent to the user to explicitly prompt the user that the operation requested to be performed will require obtaining and using the personal information of the user. Thus, the user can autonomously select whether to provide the personal information to the software or hardware such as an electronic device, an application program, a server, or a storage medium, etc. that performs the operation of the technical solutions of the present disclosure according to the prompt information.

[0043] As an optional but non-limiting implementation manner, in response to receiving the active request of the user, the manner of sending the prompt information to the user may, for example, be a pop-up window manner, and the prompt information may, for example, be presented in the form of text in the pop-up window. In addition, the pop-up window may, for example, also carry a selection control for the user to select “agree” or “disagree” to provide the personal information to the electronic device.

[0044] It can be understood that the above notification and obtaining of the authorization of the user are merely illustrative, and do not limit the implementation manners of the present disclosure, and other manners that meet the relevant laws and regulations can also be applied to the implementation manners of the present disclosure.

[0045] FIG. 1 shows a schematic diagram of a data processing architecture according to an embodiment of the present disclosure. Referring to FIG. 1, the data processing architecture 100 can include a server 110, a terminal 120, and a network 130 providing a communication link. The server 110 and the terminal 120 can be connected through the network 130 in a wired or wireless manner. The server 110 can be a standalone physical server, a server cluster or a distributed system composed of multiple physical servers, a cloud server providing cloud services, cloud database, cloud computing, cloud function, cloud storage, network service, cloud communication, middleware service, security service, CDN, and other basic cloud computing services.

[0046] The terminal 120 can be implemented in hardware or software. For example, when the terminal 120 is implemented in hardware, it can be various electronic devices with a display screen and supporting page display, including but not limited to a smart phone, a tablet computer, an electronic book reader, a laptop computer, and a desktop computer, etc. When the terminal 120 is implemented in software, it can be installed in the above-mentioned electronic devices; it can be implemented as multiple software or software modules (for example, software or software modules for providing distributed services), or as a single software or software module, which is not specifically limited herein.

[0047] It should be noted that the data processing method provided by the embodiments of the present disclosure can be executed by the terminal 120 or the server 110. It should be understood that the number of terminals, networks, and servers in FIG. 1 is only illustrative and is not intended to be limiting. According to the implementation needs, there can be any number of terminals, networks, and servers.

[0048] FIG. 2 shows a schematic diagram of a hardware structure of an exemplary electronic device 200 according to an embodiment of the present disclosure. As shown in FIG. 2, the electronic device 200 can include a processor 202, a memory 204, a network module 206, a peripheral interface 208, and a bus 210. The processor 202, the memory 204, the network module 206, and the peripheral interface 208 are connected to each other through the bus 210 for internal communication within the electronic device 200.

[0049] The processor 202 can be a central processing unit (CPU), a data processor, a neural processing unit (NPU), a microcontroller (MCU), a programmable logic device, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or one or more integrated circuits. The processor 202 can be configured to perform functions related to the techniques described in the present disclosure. In some embodiments, the processor 202 can also include multiple processors integrated as a single logical component. For example, as shown in FIG. 2, the processor 202 can include multiple processors 202a, 202b, and 202c.

[0050] The memory 204 can be configured to store data (e.g., instructions, computer code, etc.). As shown in FIG. 2, the memory 204 can store data including program instructions (e.g., program instructions for implementing the data processing method of embodiments of the present disclosure) and data to be processed (e.g., the memory can store configuration files of other modules, etc.). The processor 202 can also access the program instructions and data stored in the memory 204, and execute the program instructions to operate on the data to be processed. The memory 204 can include volatile storage or non-volatile storage. In some embodiments, the memory 204 can include random access memory (RAM), read only memory (ROM), optical disk, magnetic disk, hard disk, solid state disk (SSD), flash memory, memory stick, etc.

[0051] The network module 206 can be configured to provide communication between the electronic device 200 and other external devices via a network. The network can be any wired or wireless network capable of transmitting and receiving data. For example, the network can be a wired network, a local wireless network (e.g., Bluetooth, WiFi, near field communication (NFC), etc.), a cellular network, the Internet, or a combination thereof. It can be understood that the type of network is not limited to the specific examples described above. In some embodiments, the network module 306 can include any combination of any number of network interface controllers (NICs), radio frequency modules, transceivers, modems, routers, gateways, adapters, cellular network chips, etc.

[0052] The peripheral interface 208 can be configured to connect the electronic device 200 with one or more peripheral devices to enable information input and output. For example, the peripheral devices can include input devices such as keyboards, mice, touchpads, touchscreens, microphones, various sensors, etc., and output devices such as displays, speakers, vibrators, indicator lights, etc.

[0053] The bus 210 can be configured to transmit information between various components of the electronic device 200 (e.g., the processor 202, the memory 204, the network module 206, and the peripheral interface 208), such as an internal bus (e.g., a processor-memory bus), an external bus (a USB port, a PCI-E bus), and the like.

[0054] It should be noted that although the architecture of the electronic device 200 described above only shows the processor 202, the memory 204, the network module 206, the peripheral interface 208, and the bus 210, in the specific implementation process, the architecture of the electronic device 200 can also include other components necessary for normal execution. In addition, those skilled in the art can understand that the architecture of the electronic device 200 described above can also only contain components necessary for the implementation of the embodiments of the present disclosure, and does not necessarily contain all the components shown in the figure.

[0055] Table data often needs to process and analyze the data content, but the existing table data processing method is not efficient and flexible. Therefore, how to improve the processing efficiency and flexibility of table data has become a technical problem to be solved.

[0056] In view of this, the embodiments of the present disclosure provide a data processing method and related equipment. The configuration form of the description data of the plug-in configuration data of the target plug-in is generated; and based on the form data of the configuration form set by the user and the template data of the plug-in configuration data, the field configuration data of the target field is generated, so as to generate the corresponding target field content. The custom processing of the table data can be realized by calling the target plug-in, and the corresponding target field is obtained, which improves the efficiency and flexibility of data processing. In addition, the developer can test, create, and update the target plug-in, which realizes a more open and flexible data processing method.

[0057] Referring to FIG. 3, FIG. 3 shows a schematic flowchart of a data processing method according to an embodiment of the present disclosure. The data processing method according to the embodiments of the present disclosure can be deployed on a terminal or a server side, for example, an application program platform. In FIG. 3, the data processing method 300 can further include the following steps.

[0058] In step S310, in response to a plug-in calling request for a target plug-in, plug-in configuration data of the target plug-in is obtained; the target plug-in is used to generate a target field in a table.

[0059] Among them, the plug-in can refer to a functional component with business custom logic on the application program platform. The plug-in calling request is used to call the target plug-in. The plug-in configuration data can refer to a series of parameters and setting information set by the plug-in to enable normal work or function customization according to specific needs.

[0060] In some embodiments, the plug-in configuration data can include description data and template data. The description data can refer to DSL description data of field components in the plug-in, and the description data can be used to render a configuration form to visually provide the plug-in configuration data to the user for setting. The template data can refer to a preset structured content model, and the template data can be customized. Different template data can correspond to plug-ins with different functions, for example, for a plug-in that implements formula processing, the template data can include a preset formula model; for a plug-in that implements content expansion, the template data can include a preset prompt word model.

[0061] In some embodiments, before the plug-in invocation request for the target plug-in, the method further includes:

[0062] In response to receiving the plug-in query request containing the keyword, determining a target data set based on a query plug-in type in the plug-in query request;

[0063] Searching the target data set based on the keyword; wherein the preset data set includes meta information of a plurality of plug-ins;

[0064] Determining, as a search result, a plug-in corresponding to the meta information matched with the keyword, to obtain a search result list;

[0065] Determining, as the target plug-in, a plug-in selected by the user in the search result list.

[0066] Referring to FIG. 4, FIG. 4 shows a schematic diagram of searching for a target plug-in according to an embodiment of the present disclosure. In FIG. E, a user sends a plug-in query request for a target plug-in to a front end FE, for example, the user can input a search keyword in an input area of a real interface and trigger a search button in a display interface to generate a plug-in query request including the keyword. The front end FE sends the plug-in query request to a back end Pack, in response to the plug-in query request, the back end Pack queries a meta information document from meta information sdk and checks the reading permission of the meta information document; if the reading permission of the meta information document is checked, the keyword is checked (the keyword cannot be empty). The back end Pack can query the brand to which the meta information document belongs in the global meta information (for example, query the field brand in the meta information). If the meta information document is a non-preset unit (for example, cn unit), the preset unit is queried for data. Based on the search request, it is determined whether the queried plug-in is a field type plug-in, in response to the search request querying the plug-in, the back end Pack searches based on the keyword in the corresponding specified data set (such as a first search data set), and obtains a search result. The back end Pack can obtain the basic information of the search result plug-in from the database, check the user visibility of the basic information, and if the user visibility is checked, the operation classification of the search result can be obtained from the database. The back end Pack can return the search result to the front end FE in the form of a list to show the plug-in list of the search result to the user.

[0067] In some embodiments, determining a target data set based on a query plug-in type in the plug-in query request comprises:

[0068] In response to the query plug-in type being a preset type plug-in, determining that a first search data set is the target data set;

[0069] In response to the query plug-in type being a non-preset type plug-in, determining that a second search data set is the target data set, the second search data set being independent of the first search data set.

[0070] In some embodiments, the preset type plug-in can refer to a field type plug-in for generating a custom field, for example, a formula type plug-in, an AI extension type plug-in. The first search data set can be a search data set corresponding to the preset type plug-in, and the second search data set can correspond to the non-preset type plug-in.

[0071] In some embodiments, in response to a plug-in call request for a target plug-in, obtaining plug-in configuration data of the target plug-in comprises:

[0072] In response to the plug-in call request including a specified version, obtaining plug-in configuration data corresponding to the specified version and specified version data;

[0073] In response to the plug-in calling request not including a specified version, the latest version corresponding plug-in configuration data and the latest version data are obtained.

[0074] Referring to FIG. 5, FIG. 5 shows a schematic diagram of obtaining specified version data of a target plug-in according to an embodiment of the present disclosure. In FIG. 5, a user sends a plug-in calling request to the front end FE, and the plug-in calling request includes a query for specified version data. The front end FE sends the plug-in calling request to the back end Pack, the back end Pack queries the plug-in configuration data corresponding to the target plug-in from the database, and checks the user visibility. If the user visibility check passes, the operation classification of the target plug-in is obtained from the database. In response to determining that the plug-in configuration data includes multi-version data, it is determined whether a specified version number exists in the parameters of the plug-in calling request; in response to the specified version number existing in the parameters, the plug-in configuration data corresponding to the specified version is queried from the database; in response to the specified version number not existing in the parameters, the plug-in configuration data corresponding to the latest version is queried from the database. The plug-in configuration data obtained by querying is assembled with the corresponding version data, and is sent to the front end FE via the back end Pack to be displayed to the user.

[0075] In step S320, a configuration form is generated based on the description data in the plug-in configuration data.

[0076] The configuration form can refer to dynamically constructing a user interface according to the plug-in configuration metadata (such as field name, type, default value, description, etc.) provided by the target plug-in, so that the user can customize or modify the configuration of the plug-in through the form.

[0077] In step S330, in response to receiving form data of the configuration form, field configuration data of the target field is generated based on the form data and the template data in the plug-in configuration data.

[0078] When the user submits specific configuration information through the configuration form, the field configuration data of the target field can be generated or updated according to the form data and the template data predefined by the plug-in.

[0079] In step S340, target field content of the target field is generated based on the field configuration data.

[0080] In some embodiments, the template data includes formula template data, and the target field includes a formula field.

[0081] Then, generating the field configuration data of the target field based on the form data and the template data in the plug-in configuration data includes: generating a corresponding formula based on the form data and the formula template data, and obtaining the field configuration data of the target field based on the formula.

[0082] generating target field content of the target field based on the field configuration data, including: bringing field content corresponding to the field configuration data in the table data into the formula to obtain the target field content.

[0083] In some embodiments, the template data includes prompt word template data, and the target field includes a prompt word field.

[0084] Then, generating field configuration data of the target field based on the form data and the template data in the plug-in configuration data, includes:

[0085] generating corresponding prompt words based on the form data and the prompt word template data, and obtaining the field configuration data of the target field based on the prompt words;

[0086] generating target field content of the target field based on the field configuration data, including: automatically generating the target field content based on the prompt words.

[0087] Referring to FIG. 6, FIG. 6 shows an application principle schematic diagram of a target plug-in according to an embodiment of the present disclosure. In FIG. 6, a user can call a plug-in for a current data object to implement the function of the target plug-in on the current data object. The target plug-in can be used to generate an open field of the current data object, which can refer to a custom field created by a developer on an open slot. For example, calling the target plug-in on the basis of the current data object can perform formula operation on at least part of the data fields in the current data object to obtain an open formula field, or can perform AI expansion on at least part of the data fields in the current data object to obtain an AI expansion field.

[0088] The user can send a plug-in information request for obtaining target plug-in information to the front end FE, and the front end FE responds to the plug-in information request to obtain plug-in information under each operation category from the back end Pack, and displays each target plug-in in a corresponding interface. Specifically, the target plug-in can be an open field plug-in, and the user can perform a trigger operation of adding a field in the display interface, for example, clicking an add field button in the display interface to display a field panel in the associated area of the add field button. The field panel can display one or more field buttons, and each field button can be used to generate different fields. The field panel can also display a field center button, and the user can trigger the field center button to display a corresponding field center interface. The field center interface can include one or more field buttons. Because the field panel can carry a limited number of field plug-ins due to area restrictions, all field plug-ins can be carried in the field center.

[0089] The field center interface can also display a search component for searching the plug-in, which can include an input area and a corresponding search trigger component. The input area can be used to input search information, such as keyword input; the search trigger component can be used to send a plug-in search request to the FE, which can include the search information input in the input area.

[0090] The FE sends the plug-in search request to the Pack, and the Pack sends the search information to the search platform; the search platform searches all index information of the plug-ins based on the search information, and returns the plug-in search result in the form of a plug-in list to the Pack. The Pack returns the plug-in list of the plug-in search result to the FE for display, for example, the plug-in list can be displayed in the form of a list or view in the field center interface.

[0091] The user can select the plug-in search result displayed by the FE and trigger the selected target plug-in, for example, click the target plug-in in the plug-in search result to generate a target plug-in call request. The FE responds to the target plug-in call request, obtains the corresponding plug-in configuration data from the Pack, and renders the configuration form based on the form rendering data in the plug-in configuration data. The FE displays the configuration form to the user, the user sets the configuration data in the configuration form, and sends the set configuration form to the FE. The FE maintains the settings of the configuration form, obtains the configuration data and its settings therefrom, generates a target field for the current data object, and displays it to the user. The current data object can be a data table, which can include a initial field, and after calling the target plug-in, the data table table increases the target field, at this time, the data table table includes a initial field and 1 target field.

[0092] In some embodiments, the method 300 further includes: in response to the user's upgrade request for the target plug-in, upgrading the target plug-in based on the upgrade data in the upgrade request.

[0093] The user can manually upgrade the target plug-in. Specifically, the user triggers an upgrade request, which usually contains the current version information of the target plug-in and the new version information to which the user wants to upgrade, and sometimes includes some additional upgrade parameters or configuration upgrade data.

[0094] Referring to FIG. 7, FIG. 7 shows a schematic flowchart of a data processing method according to embodiments of the present disclosure. The data processing method according to embodiments of the present disclosure can be deployed on a terminal or a server side, for example, an application program platform. In FIG. 7, the data processing method 700 can further include the following steps.

[0095] At step S710, in response to receiving the plug-in debugging request for the target plug-in, a debugging plug-in of the target plug-in is created; the target plug-in is used to generate a target field in a table.

[0096] The developer can debug the target plug-in through a test environment provided by the application program platform, and determine whether the target plug-in can achieve the expected function through the debugging result. Referring to FIG. 8, FIG. 8 shows a development principle diagram of a target plug-in according to an embodiment of the present disclosure. In FIG. 8,

[0097] The developer can send a first plug-in test request to the front end FE; the front end FE responds to the first plug-in test request, and newly creates a debugging plug-in for debugging the target plug-in and generates corresponding plug-in protocol data. Specifically, a corresponding interface display toolbar can be provided, and the developer fills in the setting data of the plug-in protocol data through the toolbar and generates the plug-in protocol data about the target plug-in. The plug-in protocol data can be plug-in configuration data provided by the developer based on supported languages (such as programming languages), has a structured information format, and can define the communication and configuration between the application program (such as the platform or the framework) and the plug-in. The plug-in protocol data can include at least one of the following: form rendering data, template data, and other necessary data (such as plug-in meta information, function description, dependency relationship, etc.). In multiple aspects, it is ensured that the plug-in can be recognized, loaded and correctly executed by the host application. The developer can perform a trigger operation (such as clicking a corresponding test button, etc.) of the plug-in test request, send the first plug-in test request to the front end FE, and submit the plug-in protocol data to the front end FE in the form of a file. The front end FE creates plug-in configuration data of the target plug-in based on the received plug-in protocol data, and transmits it to the back end Pack for storage.

[0098] In some embodiments, the method 700 further includes: in response to receiving an update request for the debugging plug-in, updating the debugging plug-in based on update data in the update request. Where the target plug-in can be multi-versioned, the plug-in protocol data can be corresponding multi-versioned data. The developer can send a second plug-in test request to the front end FE; the front end FE loads the existing debugging plug-in for updating in response to the second plug-in test request. At this time, the existing debugging plug-in can be a first version, and the corresponding plug-in protocol data thereof is also a first version. The developer can submit the new version of the plug-in protocol data to the front end FE in the form of a file, for example, the new version can refer to a second version. The front end FE updates the plug-in configuration data of the first version of the debugging plug-in based on the received plug-in protocol data of the second version to obtain the plug-in configuration data of the second version. And the updated plug-in configuration data of the second version is transmitted to the back end Pack for storage, thereby completing the updating of the existing debugging plug-in. In step S720, in response to a debugging call request for the debugging plug-in, the debugging configuration data of the debugging plug-in is obtained.

[0099] Specifically, the developer can trigger the call of the debugging plug-in (for example, the developer can select the debugging plug-in on the corresponding interface and click the button to add the debugging plug-in) to send a debugging plug-in call request to the front end FE.

[0100] In step S730, a debugging configuration form is generated based on the description data in the debugging configuration data.

[0101] Specifically, the front end FE pulls the configuration data of the target plug-in from the back end Pack in response to the debugging plug-in call request; and renders the form component according to the form rendering data in the configuration data to display the configuration form of the debugging plug-in on the corresponding interface.

[0102] In step S740, in response to receiving the debugging data of the debugging configuration form, a test result of the target plug-in is generated.

[0103] Specifically, the developer can fill in the corresponding form items in the configuration form, and the front end FE obtains the corresponding data values from the form items to process the configuration data of the debugging plug-in to generate the target field. The target field can be saved and displayed on the corresponding interface to check whether the content of the target field meets the expectation.

[0104] In some embodiments, the method 700 further includes:

[0105] When the test result meets the expectation, a plug-in creation request for creating the target plug-in is received;

[0106] In response to receiving the plugin creation request, plugin protocol data of the target plugin is obtained from an attachment field in the plugin creation request; wherein the plugin protocol data is generated based on protocol setting data input by a user.

[0107] Referring to FIG. 9, FIG. 9 shows a schematic diagram of the principle of auditing and deploying a target plugin according to an embodiment of the present disclosure. In FIG. 9, an auditor can audit a target plugin based on an audit request proposed by a developer. If the auditor determines that the audit result of the target plugin is passed, the target plugin can be deployed on an application platform for users to share and use.

[0108] The developer can send a plugin audit request to the front end FE, and the plugin audit request is used to request an auditor to audit an unpublished target plugin or to audit an updated version of a published target plugin. Specifically, the developer can submit a plugin audit request to the front end FE by filling in an audit form. When the plugin audit request is detected, the automation test program Automation in the application platform can automatically send a notification to the auditor to prompt the auditor to review the information of the target plugin. After the auditor determines that the audit is passed, the auditor sends the related information of the target plugin to the front end FE, so that the front end FE adds or updates the related information of the target plugin in the plugin management table. These related information can include at least one of the following: plugin name, plugin description, plugin type, plugin version, plugin ID, operation options (for example, operation buttons or links of functions such as editing, deleting, enabling / disabling, etc., providing an interface for an administrator to manage the plugin), plugin developer, plugin release date: displaying the release or update time of the plugin, dependency relationship, etc.

[0109] In some embodiments, the method 700 further includes:

[0110] When the test result is as expected, receiving a plugin creation request for creating the target plugin;

[0111] In response to receiving the plugin creation request, plugin protocol data of the target plugin is obtained from an attachment field in the plugin creation request; wherein the plugin protocol data is generated based on protocol setting data input by a user.

[0112] Specifically, when the test result is as expected, the auditor determines that the target plug-in passes the audit. The auditor can trigger an automation test procedure Automation to generate a plug-in creation request (e.g., an HTTP action) by clicking an automation button; or the user can generate the plug-in creation request, for example, by triggering a button for creating a plug-in. The plug-in creation request can be used to request a call to the corresponding target plug-in interface from the backend Pack to submit plug-in configuration data of the target plug-in, so as to deploy the target plug-in on the application platform, for example, to create or update the target plug-in. The plug-in deployment request can include a record identifier recordID used to indicate the plug-in configuration data of the target plug-in, where the plug-in configuration data of the target plug-in can be stored in the form of table data in the core domain of the application platform. For example, the plug-in configuration data can be row record data record having the corresponding record identifier recordID and including a plurality of record fields, each record field can be a plug-in configuration parameter of the plug-in configuration data, and the value of each record field can be the value of the plug-in configuration parameter. The backend Pack responds to the plug-in deployment request, obtains the corresponding row record data according to the record identifier (e.g., recordID), and can obtain the plug-in configuration data of the target plug-in according to the row record data.

[0113] The backend Pack can verify the legality and access authority of the row record data, and can obtain valid data of the row record data record after the verification is passed. Wherein, the backend identifier (e.g., PackID) and the plug-in identifier (e.g., extensionID) are generated when the target plug-in is added, the backend identifier can be used to indicate the corresponding backend Pack of the target plug-in, and the plug-in identifier can be used to indicate the target plug-in.

[0114] The backend Pack can parse the row record data record to obtain the plug-in name (which can be an internationalized plug-in name) extension_name of the target plug-in and the description language (e.g., a dsl (Domain Specific Language, domain specific language) description language) of the target plug-in.

[0115] The backend Pack can parse the plugin type of the target plugin based on the row record data record, which can include a first type or a second type. For example, the first type can be a static field class, indicating that the target plugin depends on a static template in the configuration data to generate a target field. The second type can be a FaaS (Functions as a Service) field class, indicating that the target plugin can support FaaS to generate a target field. Specifically, the backend Pack can extract a field extension_type representing the plugin type from the parsed data structure. For example, extension_type = field_static can indicate that the plugin type is a static field class, and extension_type = field_FaaS can indicate that the plugin type is a FaaS field class. When all field-related field plugins need to be obtained, non-accurate matching can be performed based on the plugin type as a query condition. For example, the query condition can be where extension_type in (field_static) to query target plugins whose plugin type extension_type includes field_static. For another example, the query condition can be where extension_type in (field_) to query target plugins whose plugin type extension_type includes field, i.e., to find plugins related to the field field. It should be understood that the above-mentioned plugin types are only illustrative and are not intended to limit the plugin types. The plugin type can be set as needed, and the number of categories of the plugin type can be one or more, which is not limited here.

[0116] In some embodiments, the plugin protocol data of the target plugin is obtained from an attachment field in the plugin creation request, including:

[0117] Obtaining a token of the attachment field, and obtaining a download link of the attachment field based on the token;

[0118] Obtaining content data of the attachment field based on the download link, to obtain the plugin protocol data.

[0119] Specifically, the backend Pack can obtain the token of the attachment field in the row record data record. The backend Pack obtains the attachment download link according to the token of the attachment field, and obtains the attachment data content of the attachment field based on the download link. The attachment data content can be the plugin protocol data of the target plugin, provided in the form of a file in the attachment field.

[0120] The backend Pack can set the visibility range of the target plug-in. In order to avoid the conflict between the field editing permission and the plug-in permission, the target plug-in can be set as visible to all. The backend Pack can parse the operation category of the target plug-in based on the row record data record. The operation category can be a classification according to the function or application scenario of the target plug-in. For example, the operation category can include customer service category, data analysis category, system tool category, security maintenance category, etc. The backend Pack can parse the plug-in configuration data of the target plug-in to obtain version data and store it.

[0121] As can be seen, the backend Pack can parse the newly added field or the updated field based on the row record data record, for example, the backend identification PackID, the plug-in identification extensionID, the plug-in type extension_type, the operation category operation_type, etc. The backend Pack can store the newly added field or the updated field to the meta information of the target plug-in, and store it together with the plug-in configuration data of the target plug-in to the database.

[0122] In some embodiments, the method 700 further includes:

[0123] generating a version number of the target plug-in, and storing the version number in the version data corresponding to the target plug-in.

[0124] Specifically, the backend Pack can lock the multi-version data of the target plug-in, for example, implement locking based on the Redis database, to prevent conflict between different versions of data. The backend Pack can generate the current version number version of the target plug-in, write the basic data, version data, etc. of the target plug-in in the database, add or update the Replit plug-in data, etc.

[0125] The backend Pack can store multi-version data of the target plug-in in the form of a data table. Specifically, a data table can be created to store information about different versions of the plug-in, including its type extension_type, primary key identification id, primary key PRIMARY KEY (defined on the primary key identification id to ensure the uniqueness of each data table record), unique key UNIQUE KEY uniq_pack_version_id (which can ensure that the combination of pack_id and version is unique, preventing duplicate version numbers for the same target plug-in), plug-in identification pack_id, version data version_data (which can store detailed information related to the version, possibly in JSON or other structured text data), storage type storage_type (which is used to indicate whether the version data version_data is direct data storage or a reference to data storage), version number version (which is different from the update version number), protocol version protocol_version (the base version number on which the target plug-in depends or is compatible), plug-in version status status (for example, 1 for enabled and 2 for disabled), and creation time create_time and update time update_time, among other detailed information.

[0126] In some embodiments, the method 700 further includes:

[0127] In response to determining that the target plug-in is a preset class plug-in, updating the independent first search data set corresponding to the preset class plug-in based on the meta information of the target plug-in.

[0128] In some embodiments, the method 700 further includes:

[0129] Specifically, the backend Pack can determine a corresponding search data set based on the plug-in category of the target plug-in, which can be a set of index information of all plug-ins. If the target plug-in is a field-type plug-in (a plug-in for generating a field), a search can be performed in a first search data set, which can be a set of index information of all field-type plug-ins. If the target plug-in is a non-field-type plug-in, a search can be performed in a second search data set, which can be a set of index information of all non-field-type plug-ins. The first search data set and the second search data set can be independent of each other. The backend Pack can update the search data of the search center in the application program platform based on the meta information of the newly added or updated target plug-in. For example, for field-type plug-ins, the first search data set can be updated based on the newly added or updated meta information.

[0130] The backend Pack can encapsulate the above processing result and return the encapsulation result to the front end FE via the automation test program Automation. In this way, the deployment of the target plug-in in the application program platform is completed, and the user can call the target plug-in to realize the corresponding function by triggering the operation.

[0131] In some embodiments, the method 700 further includes:

[0132] In response to receiving an update request for the target plug-in, updating the target plug-in based on update data in the update request.

[0133] Specifically, the developer can also submit update data to the front end FE, and the front end FE sends the update data to the backend Pack, which updates the target plug-in based on the update data.

[0134] It can be seen that according to the method of the embodiments of the present disclosure, the application program platform provides a more open and flexible data processing method for the developer, and the developer can test, create and update the target plug-in in the application program platform, thereby realizing the customized data processing function. The user can also be provided with the function of the target plug-in, and the user can realize efficient and flexible data processing by calling the target plug-in.

[0135] It should be noted that the method of the embodiments of the present disclosure can be executed by a single device, such as a computer or a server. The method of the present embodiment can also be applied to a distributed scenario, and can be completed by multiple devices cooperating with each other. In this distributed scenario, one of the multiple devices can only execute one or more steps in the method of the embodiments of the present disclosure, and the multiple devices can interact with each other to complete the method.

[0136] It is to be understood that the foregoing description is directed to some embodiments of the disclosure. Other embodiments fall within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order and still achieve desirable results. Additionally, the processes depicted in the accompanying figures do not necessarily require the particular order shown or sequential order to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.

[0137] According to the same technical concept, the disclosure also provides a data processing apparatus corresponding to any of the above-mentioned embodiment methods, as shown in FIG. 10, the data processing apparatus comprises:

[0138] A first obtaining module is configured to obtain plug-in configuration data of a target plug-in in response to a plug-in call request for the target plug-in, wherein the target plug-in is configured to generate a target field in a table;

[0139] A first configuration module is configured to generate a configuration form based on description data in the plug-in configuration data;

[0140] A target field module is configured to generate field configuration data of the target field based on form data of the configuration form and template data in the plug-in configuration data in response to receiving the form data of the configuration form;

[0141] A field content module is configured to generate target field content of the target field based on the field configuration data.

[0142] In some embodiments, the data processing apparatus further comprises:

[0143] A plug-in query module is configured to determine a target data set based on a query plug-in type in a plug-in query request containing a keyword in response to receiving the plug-in query request;

[0144] A search module is configured to search in the target data set based on the keyword, wherein the preset data set comprises meta-information of a plurality of plug-ins;

[0145] A result list module is configured to determine a plug-in corresponding to the meta-information matching the keyword as a search result to obtain a search result list;

[0146] A plug-in selection module is configured to determine a plug-in selected by a user in the search result list as the target plug-in.

[0147] In some embodiments, the data processing apparatus further comprises:

[0148] An additional information module is configured to generate additional information data based on the attribute of the target field and store the additional information data into the meta information of the target plug-in.

[0149] In some embodiments, the meta information of the target plug-in includes a version data table, and the version data table includes at least one record, and each record stores plug-in configuration data of a different version.

[0150] In some embodiments, the data processing apparatus further includes:

[0151] A plug-in upgrade module is configured to upgrade the target plug-in based on upgrade data in a user request for upgrading the target plug-in.

[0152] Based on the same technical concept, the disclosure also provides a data processing apparatus corresponding to the method of any of the above embodiments, as shown in FIG. 11, the data processing apparatus includes:

[0153] A creation module is configured to create a debugging plug-in of a target plug-in in response to receiving a plug-in debugging request for the target plug-in, and the target plug-in is configured to generate a target field in a table.

[0154] A second acquisition module is configured to acquire debugging configuration data of the debugging plug-in in response to a debugging call request for the debugging plug-in.

[0155] A second configuration module is configured to generate a debugging configuration form based on description data in the debugging configuration data.

[0156] A debugging module is configured to generate a test result of the target plug-in in response to receiving debugging data of the debugging configuration form.

[0157] In some embodiments, the data processing apparatus further includes:

[0158] A debugging update module is configured to update the debugging plug-in based on update data in an update request for the debugging plug-in in response to receiving the update request.

[0159] In some embodiments, the data processing apparatus further includes:

[0160] A receiving module is configured to receive a plug-in creation request for creating the target plug-in when the test result meets an expectation.

[0161] A plug-in creation module is configured to acquire plug-in protocol data of the target plug-in from an attachment field in the plug-in creation request in response to receiving the plug-in creation request, and the plug-in protocol data is generated based on protocol setting data input by a user.

[0162] In some embodiments, the data processing apparatus further comprises:

[0163] an attachment obtaining module, configured to obtain a mark of the attachment field, and obtain a download link of the attachment field based on the mark; and

[0164] obtain content data of the attachment field based on the download link, to obtain the plug-in protocol data.

[0165] In some embodiments, the data processing apparatus further comprises:

[0166] a version data module, configured to generate a version number of the target plug-in, and store the version number into version data corresponding to the target plug-in.

[0167] In some embodiments, the data processing apparatus further comprises:

[0168] a search updating module, configured to, in response to determining that the target plug-in is a preset type plug-in, update an independent first search data set corresponding to the preset type plug-in based on meta information of the target plug-in.

[0169] In some embodiments, the data processing apparatus further comprises:

[0170] a plug-in updating module, configured to, in response to receiving an updating request for the target plug-in, update the target plug-in based on updating data in the updating request.

[0171] For the convenience of description, the above apparatus is described in various modules respectively based on functions. Of course, the functions of the modules can be implemented in one or more software and / or hardware in the implementation of the present disclosure. The apparatus of the above embodiments is used to implement the corresponding data processing method in any of the preceding embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be described here.

[0172] Based on the same technical concept, corresponding to any of the above method embodiments, the present disclosure further provides a non-transitory computer readable storage medium, which stores computer instructions for causing the computer to execute the data processing method according to any of the above embodiments.

[0173] The computer readable media of the embodiments can include permanent and non-permanent, removable and non-removable media, which can be implemented by any method or technology to store information. The information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device, or any other non-transmission medium that can be used to store information accessible by a computing device.

[0174] The storage medium of the above embodiments stores computer instructions for causing the computer to execute the data processing method as described in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described here.

[0175] Those skilled in the art should understand that the discussion of any of the above embodiments is only exemplary and is not intended to imply that the scope of the present disclosure (including claims) is limited to these examples; under the idea of the present disclosure, the above embodiments or technical features between different embodiments can also be combined, the steps can be implemented in any order, and there are many other changes of different aspects of the embodiments of the present disclosure as described above. In order to be brief, they are not provided in detail.

[0176] In addition, in order to simplify the description and discussion, and so as not to make the embodiments of the present disclosure difficult to understand, the well-known power / ground connections of integrated circuit (IC) chips and other components can or can not be shown in the provided drawings. In addition, the devices can be shown in the form of block diagrams in order to avoid making the embodiments of the present disclosure difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform to be implemented the embodiments of the present disclosure (i.e. these details should be fully within the understanding of those skilled in the art). Where specific details (e.g. circuits) are set forth in order to describe an exemplary embodiment of the present disclosure, it will be apparent to those skilled in the art that the embodiments of the present disclosure can be implemented without these specific details or with variations on these specific details. Therefore, these descriptions should be considered illustrative rather than limiting.

[0177] While the present disclosure has been described in connection with certain embodiments thereof, many modifications, substitutions, and variations will be apparent to those of ordinary skill in the art from the foregoing description. For instance, other memory architectures (e.g., dynamic RAM (DRAM)) can use the embodiments discussed.

[0178] Embodiments of the disclosure are intended to cover all such alternatives, modifications, and variations as falling within the broad scope of the appended claims. Accordingly, any one or more of the above-described embodiments can be combined with any one or more of the above-described embodiments in any manner within the scope of the disclosure.

Claims

1. A data processing method, comprising: in response to a plug-in call request for a target plug-in, obtaining plug-in configuration data of the target plug-in; the target plug-in is used to generate a target field in a table; generating a configuration form based on description data in the plug-in configuration data; in response to receiving form data of the configuration form, generating field configuration data of the target field based on the form data and template data in the plug-in configuration data; generating target field content of the target field based on the field configuration data.

2. The method according to claim 1, wherein, Before the step of in response to a plug-in call request for a target plug-in, the method further comprises: in response to receiving a plug-in query request containing a keyword, determining a target data set based on a query plug-in type in the plug-in query request; searching in the target data set based on the keyword; wherein the preset data set comprises meta information of a plurality of plug-ins; determining a plug-in corresponding to the meta information matching the keyword as a search result to obtain a search result list; determining a plug-in selected by a user in the search result list as the target plug-in.

3. The method according to claim 2, wherein, The step of determining a target data set based on a query plug-in type in the plug-in query request comprises: in response to the query plug-in type being a preset type plug-in, determining a first search data set as the target data set; in response to the query plug-in type being a non-pre-set type plug-in, determining a second search data set as the target data set, the second search data set being independent of the first search data set.

4. The method according to claim 1, wherein, The step of in response to a plug-in call request for a target plug-in, obtaining plug-in configuration data of the target plug-in, comprises: in response to the plug-in call request including a specified version, obtaining plug-in configuration data corresponding to the specified version and specified version data; in response to the plug-in call request not including a specified version, obtaining plug-in configuration data corresponding to the latest version and latest version data. 5.The method of claim 1, further comprising: generating additional information data based on attributes of the target field, and storing the additional information data into meta information of the target plug-in.

6. The method according to claim 5, wherein, The meta information of the target plug-in comprises a version data table, and the version data table comprises at least one record, each record storing plug-in configuration data of a different version.

7. The method according to claim 1, wherein, The template data comprises formula template data, and the target field comprises a formula field; then the step of generating field configuration data of the target field based on the form data and the template data in the plug-in configuration data comprises: generating a corresponding formula based on the form data and the formula template data, and obtaining the field configuration data of the target field based on the formula; the step of generating target field content of the target field based on the field configuration data comprises: bringing field content corresponding to the field configuration data in the table into the formula to obtain the target field content; or, the template data comprises prompt word template data, and the target field comprises a prompt word field; generating field configuration data of the target field based on the form data and template data in the plug-in configuration data, including: generating corresponding prompt words based on the form data and the prompt word template data, and obtaining the field configuration data of the target field based on the prompt words; generating target field content of the target field based on the field configuration data, including: automatically generating the target field content based on the prompt words.

8. The method of claim 1, further comprising: in response to a user request for upgrading the target plug-in, upgrading the target plug-in based on upgrade data in the request.

9. A data processing method, comprising: in response to receiving a plug-in debugging request for a target plug-in, creating a debugging plug-in of the target plug-in; the target plug-in is configured to generate a target field in a form; in response to a debugging call request for the debugging plug-in, obtaining debugging configuration data of the debugging plug-in; generating a debugging configuration form based on description data in the debugging configuration data; in response to receiving debugging data of the debugging configuration form, generating a test result of the target plug-in.

10. The method of claim 9, further comprising: in response to receiving an update request for the debugging plug-in, updating the debugging plug-in based on update data in the update request.

11. The method of claim 9, further comprising: when the test result meets expectations, receiving a plug-in creation request for creating the target plug-in; in response to receiving the plug-in creation request, obtaining plug-in protocol data of the target plug-in from an attachment field in the plug-in creation request; wherein the plug-in protocol data is generated based on protocol setting data input by a user.

12. The method of claim 11, obtaining the plug-in protocol data of the target plug-in from the attachment field in the plug-in creation request, comprising: obtaining a tag of the attachment field, and obtaining a download link of the attachment field based on the tag; obtaining content data of the attachment field based on the download link to obtain the plug-in protocol data.

13. The method of claim 11, further comprising at least one of: generating a version number of the target plug-in, and storing the version number into version data corresponding to the target plug-in; or, in response to determining that the target plug-in is a preset type plug-in, updating independent first search data sets corresponding to the preset type plug-in based on meta information of the target plug-in; or, in response to receiving an update request for the target plug-in, updating the target plug-in based on update data in the update request.

14. A data processing apparatus, comprising: a first obtaining module configured to obtain plug-in configuration data of a target plug-in in response to a plug-in call request for the target plug-in; the target plug-in is configured to generate a target field in a form; a first configuration module configured to generate a configuration form based on description data in the plug-in configuration data; a target field module, configured to generate, in response to receiving form data of the configuration form, field configuration data of the target field based on the form data and template data in the plug-in configuration data; a field content module, configured to generate target field content of the target field based on the field configuration data.

15. A data processing apparatus, comprising: a creating module, configured to create, in response to receiving a plug-in debugging request for a target plug-in, a debugging plug-in of the target plug-in; the target plug-in is configured to generate a target field in a form; a second obtaining module, configured to obtain, in response to a debugging call request for the debugging plug-in, debugging configuration data of the debugging plug-in; a second configuration module, configured to generate, based on description data in the debugging configuration data, a debugging configuration form; a debugging module, configured to generate, in response to receiving debugging data of the debugging configuration form, a test result of the target plug-in.

16. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 13 when executing the program.

17. A non-transitory computer readable storage medium, storing computer instructions for causing a computer to execute the method of any one of claims 1 to 13.

Images