Plug-in calling method and device, computer equipment and storage medium

Abstract

The invention relates to a plug-in calling method and device, computer equipment, a storage medium and a computer program product. The method comprises the steps of obtaining a data processing page identifier, a data processing template identifier, a data processing control identifier and a system identifier of a data processing page corresponding to a data processing event; based on the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier, obtaining a plurality of target plug-ins corresponding to the data processing event; based on the plug-in type corresponding to the target plug-in, determining a calling sequence of the target plug-in; and calling the target plug-ins based on the calling sequence of the target plug-ins. By adopting the method, the plug-in calling adaptability can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a plug-in calling method, apparatus, computer equipment, storage medium and computer program product. Background Art

[0002] With the development of computer technology, electronic management and processing of data have been realized. Enterprises can manage and process company operating data through software systems. Enterprises can import new data into the software system through import templates, and export data from the software system through export templates.

[0003] In traditional technology, developers add new plug-ins to the software system and change the operating logic of the software system to meet the company's personalized needs for the software system, which results in low flexibility in plug-in calling. Summary of the invention

[0004] Based on this, it is necessary to provide a plug-in calling method, apparatus, computer device, computer-readable storage medium and computer program product that can improve the adaptability of plug-in calling in response to the above technical problems.

[0005] In a first aspect, the present application provides a plug-in calling method. The method comprises:

[0006] Obtaining a data processing page identifier, a data processing template identifier, a data processing control identifier, and a system identifier of a data processing page corresponding to a data processing event;

[0007] Acquire multiple target plug-ins corresponding to the data processing event based on the data processing page identifier, the data processing template identifier, the data processing control identifier, and the system identifier;

[0008] Determining a calling order of the target plug-ins based on the plug-in types corresponding to the target plug-ins;

[0009] The target plug-ins are called based on the calling order of the target plug-ins.

[0010] In a second aspect, the present application also provides a plug-in calling device. The device includes:

[0011] A first acquisition module is used to acquire a data processing page identifier, a data processing template identifier, a data processing control identifier and a system identifier of a data processing page corresponding to a data processing event;

[0012] A second acquisition module, configured to acquire a plurality of target plug-ins corresponding to the data processing event based on the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier;

[0013] A determination module, configured to determine a calling order of the target plug-ins based on the plug-in type corresponding to the target plug-in;

[0014] The calling module is used to call the target plug-in based on the calling order of the target plug-in.

[0015] In a third aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of any one of the methods described in the first aspect when executing the computer program.

[0016] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of any one of the methods described in the first aspect.

[0017] In a fifth aspect, the present application further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the steps of any one of the methods described in the first aspect.

[0018] The plug-in calling method, apparatus, computer device, storage medium and computer program product obtain multiple target plug-ins corresponding to data processing events through data processing page identifiers, data processing template identifiers, data processing control identifiers and system identifiers, that is, data processing page identifiers, data processing template identifiers, data processing control identifiers and system identifiers can all have bound plug-ins, and the binding of plug-ins is not limited to software systems. Each identifier can be bound to one or more plug-ins according to actual needs, thereby improving the scalability of plug-in binding. Moreover, compared with realizing plug-in binding by modifying software system programs, it is easier to bind plug-ins to data processing page identifiers, data processing template identifiers, data processing control identifiers and system identifiers. The system identifier is used for binding, thereby improving the efficiency of plug-in binding; the target plug-in for processing the data processing event is obtained through the data processing page identifier, data processing template identifier, data processing control identifier and system identifier corresponding to the data processing event. Since the plug-ins bound to the data processing page identifier, data processing template identifier, data processing control identifier and system identifier are all set according to actual needs, the obtained target plug-in is adapted to the actual needs, and then the calling order of the target plug-in is determined according to the plug-in type of the target plug-in, and the target plug-in is called based on the calling order of the target plug-in. The preset arrangement order of the plug-in type is also set according to actual needs, thereby further improving the adaptability of plug-in calling. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG1 is an application environment diagram of a plug-in calling method in one embodiment;

[0020] FIG2 is a schematic diagram of a flow chart of a plug-in calling method in one embodiment;

[0021] FIG3 is a schematic diagram of an upload page in one embodiment;

[0022] FIG4 is a schematic diagram of a plug-in, a binding object, and a scope range in one embodiment;

[0023] FIG5 is a schematic diagram of a process of obtaining a target plug-in in one embodiment;

[0024] FIG6 is a schematic diagram of a list page in one embodiment;

[0025] FIG7 is a schematic diagram of importing a template page in one embodiment;

[0026] FIG8 is a schematic diagram of operating an editing page in one embodiment;

[0027] FIG9 is a schematic diagram of a parameter configuration page in one embodiment;

[0028] FIG10 is a schematic diagram of a template verification process in one embodiment;

[0029] FIG11 is a schematic diagram of a data import process in one embodiment;

[0030] FIG12 is a schematic diagram of a data export process in one embodiment;

[0031] FIG13 is a structural block diagram of a plug-in calling device in one embodiment;

[0032] FIG. 14 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0034] The plug-in calling method provided in the embodiment of the present application can be applied to the application environment shown in Figure 1. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. Both the terminal and the server can be used alone to execute the plug-in calling method provided in the embodiment of the present application. The terminal and the server can also be used in collaboration to execute the plug-in calling method provided in the embodiment of the present application. For example, the terminal obtains the data processing page identifier, data processing template identifier, data processing control identifier and system identifier of the data processing page corresponding to the data processing event; based on the data processing page identifier, data processing template identifier, data processing control identifier and system identifier, obtain multiple target plug-ins corresponding to the data processing event; based on the plug-in type corresponding to the target plug-in, determine the calling order of the target plug-in; based on the calling order of the target plug-in, call the target plug-in. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices, and the Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. The portable wearable device may be a smart watch, a smart bracelet, a head-mounted device, etc. The server 104 may be implemented as an independent server or a server cluster consisting of multiple servers.

[0035] In one embodiment, as shown in FIG. 2 , a plug-in calling method is provided. This embodiment is described by taking the method applied to a computer device as an example, and includes steps 202 to 208 .

[0036] Step 202: Obtain a data processing page identifier, a data processing template identifier, a data processing control identifier, and a system identifier of a data processing page corresponding to a data processing event.

[0037] Among them, data processing events refer to events that process data, and data processing events include but are not limited to data download events and data upload events. Data download events refer to events that download data in a list on a data processing page. Data upload events refer to events that upload data to be uploaded to a list on a data processing page. Data processing page identifiers refer to strings that represent lists in data processing. It can be understood that the data processing page identifier has a corresponding relationship with the list in the data processing page, and the data processing page identifier is the string of the list in the data processing page. The data processing page identifier can be composed of numbers, characters, symbols, etc. A data processing page refers to a page that presents a list. A data processing template identifier refers to a string that represents a data processing template, and data processing templates include but are not limited to data download templates and data upload templates. A data processing control identifier refers to a string that represents a data processing control, and data processing controls include but are not limited to data upload controls and data download controls.

[0038] The system identifier refers to a string that represents the software system. The system identifier corresponds to the software system and the user of the software system. The software system can manage the business data of the user and has the functions of data download and data upload. The user can be different enterprises. Even if different users use the same software system, the software system identifiers used by different users are different. For example, if software system S is used by enterprise A, the system identifier of the software system used by enterprise A is AS. If software system S is used by enterprise B, the system identifier of the software system used by enterprise B is BS. Although the software systems used by enterprises A and B are both S, due to different needs of enterprises A and B, the software system AS used by enterprise A is a system with a personalized plug-in bound to software system S, and the software system BS used by enterprise B is a system with a personalized plug-in bound to software system S. The personalized plug-ins bound by enterprises A and B may be different.

[0039] Exemplarily, the computer device obtains a data processing event, and then obtains a data processing page identifier, a data processing template identifier, a data processing control identifier, and a system identifier of a data processing page corresponding to the data to be processed event.

[0040] In one embodiment, the operator triggers the data processing control located in the data processing page, and the computer device responds to the trigger operation to obtain the data processing page identifier, data processing template identifier, data processing control identifier and system identifier of the data processing control of the data processing page. For example, the operator uploads the data import template through the upload page shown in FIG3 for the data processing page, and then triggers the data processing control located in the data processing page. The computer device responds to the trigger operation to obtain the data processing page identifier of the data processing page, the data processing template identifier corresponding to the data import template, the data processing control identifier and system identifier of the data processing control.

[0041] Step 204: Acquire multiple target plug-ins corresponding to the data processing event based on the data processing page identifier, the data processing template identifier, the data processing control identifier, and the system identifier.

[0042] The target plug-in refers to a plug-in used for data processing events, and the target plug-in includes at least one of a page plug-in, a template plug-in, a control plug-in, a global plug-in, and a dynamic plug-in. The target plug-in includes multiple methods, and it is understood that a target plug-in is a method set.

[0043] Exemplarily, when at least one of the data processing page identifier, the data processing template identifier, the data processing control identifier, and the system identifier has a corresponding binding plug-in, the computer device obtains the binding plug-in corresponding to at least one of the data processing page identifier, the data processing template identifier, the data processing control identifier, and the system identifier, and determines multiple target plug-ins corresponding to the data processing event based on the corresponding binding plug-ins. The binding plug-in corresponding to the data processing page identifier is a page plug-in, the binding plug-in corresponding to the data processing template identifier is a template plug-in, the binding plug-in corresponding to the data processing control identifier is a control plug-in, and the binding plug-in corresponding to the system identifier is a global plug-in.

[0044] In one embodiment, based on the corresponding binding plug-in, multiple target plug-ins corresponding to the data processing event are determined, including: if the corresponding binding plug-in does not have a corresponding dynamic plug-in, the corresponding binding plug-in is determined as the target plug-in corresponding to the data processing event; if at least one corresponding binding plug-in has a corresponding dynamic plug-in, the corresponding binding plug-in and the dynamic plug-in are determined as the target plug-ins corresponding to the data processing event.

[0045] Step 206: Determine the calling order of the target plug-ins based on the plug-in types corresponding to the target plug-ins.

[0046] Among them, the plug-in type refers to the type of the target plug-in, and the plug-in type includes but is not limited to page binding plug-ins, template binding plug-ins, control binding plug-ins, global binding plug-ins and dynamic binding plug-ins. A page binding plug-in refers to a plug-in bound to a list in a data processing page, and the scope of the page binding plug-in is the list in the data processing page. It can be understood that the page binding plug-in will be called when the data in the list in the data processing page is processed. A template binding plug-in refers to a plug-in bound to a data processing template, for example, the type of the plug-in bound to a data upload template is a template binding plug-in, or the type of the plug-in bound to a data download template is a template binding plug-in, and the scope of the template binding plug-in is the data processing template. A control binding plug-in refers to a plug-in bound to a data processing control, for example, the type of the plug-in bound to a data upload control is a control binding plug-in, or the type of the plug-in bound to a data download control is a control binding plug-in, and the scope of the control binding plug-in is the bound data processing control. A global binding plug-in refers to a plug-in bound to the system, and the scope of the global binding plug-in is the system. A dynamically bound plugin is a plugin that is bound to another plugin. The scope of a dynamically bound plugin is the bound plugin. For example, if plugin A is bound to plugin B, then plugin A is a dynamically bound plugin. If the bound plugin B is called, plugin A is also called. The calling order refers to the order in which the target plugins are called.

[0047] For example, in the schematic diagram of plug-ins, binding objects and scopes shown in Figure 4, the binding object of the page binding plug-in is a list, and the scope is to process the data in the list; the binding object of the template binding plug-in is the data processing template, and the scope is to use the data processing template to process data; the binding object of the control binding plug-in is the data processing control, and the scope is to use the data processing control to process data; the binding object of the global binding plug-in is the software system, and the scope is to process the data in the system, that is, the scope is global; the binding object of the dynamic binding plug-in is the plug-in, and the scope is to call the bound plug-in for data processing.

[0048] Exemplarily, when there is only one corresponding target plug-in for each plug-in type, the computer device obtains a preset arrangement order corresponding to the plug-in type, and determines a calling order of the target plug-in corresponding to the plug-in type based on the preset arrangement order corresponding to the plug-in type.

[0049] In one embodiment, when there are multiple target plug-ins corresponding to at least one plug-in type, for the target plug-ins corresponding to the same plug-in type, the target plug-ins are sorted based on the binding orders corresponding to the target plug-ins to obtain a target plug-in sequence corresponding to the plug-in type, and the calling order corresponding to each target plug-in is determined based on the preset arrangement order corresponding to the plug-in type and the target plug-in sequence.

[0050] Step 208: Call the target plug-in based on the calling order of the target plug-in.

[0051] Exemplarily, in the process of processing a data processing event, the computer device obtains a to-be-executed method identifier corresponding to the data processing event, and based on the calling order of the target plug-in, sequentially calls the to-be-executed methods corresponding to the to-be-executed method identifier from the target plug-in.

[0052] In the above plug-in calling method, multiple target plug-ins corresponding to the data processing event are obtained through the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier, that is, the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier can all have bound plug-ins, and the binding of plug-ins is not limited to the software system. Each identifier can be bound to one or more plug-ins according to actual needs, thereby improving the scalability of plug-in binding. Moreover, compared with realizing the binding of plug-ins by modifying the software system program, binding the plug-in with the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier improves Improves the efficiency of plug-in binding; obtains the target plug-in for processing the data processing event through the data processing page identifier, data processing template identifier, data processing control identifier and system identifier corresponding to the data processing event. Since the plug-ins bound to the data processing page identifier, data processing template identifier, data processing control identifier and system identifier are all set according to actual needs, the obtained target plug-in is adapted to the actual needs. Then, the calling order of the target plug-in is determined according to the plug-in type of the target plug-in, and the target plug-in is called based on the calling order of the target plug-in. The preset arrangement order of the plug-in type is also set according to actual needs. Therefore, the adaptability of the plug-in call is further improved.

[0053] In one embodiment, as shown in FIG. 5 , based on the data processing page identifier, the data processing template identifier, the data processing control identifier, and the system identifier, obtaining multiple target plug-ins corresponding to the data processing event includes:

[0054] Step 502: Based on the data processing page identifier, obtain the page plug-in corresponding to the data processing event.

[0055] Among them, the page plug-in refers to a plug-in that is saved in association with the data processing page identifier. The plug-in type of the page plug-in is a page binding plug-in, which can be understood as binding the page plug-in to the list in the data processing page corresponding to the data processing page identifier. After binding, the plug-in that is saved in association with the data processing page identifier, for example, the list page shown in Figure 6 includes list attributes. The selected plug-in can be bound to the list through the list plug-in in the list attributes. After clicking the save point, the computer device associates and saves the selected plug-in with the identifier of the page where the list is located, and obtains the associated saved relationship between the selected plug-in and the page identifier of the page where the list is located. If the list is bound to multiple plug-ins, the plug-in editor can also manage multiple plug-ins.

[0056] Exemplarily, when there is a plug-in stored in association with the data processing page identifier, the computer device obtains the plug-in stored in association with the data processing page identifier, and determines the plug-in stored in association with the data processing page identifier as the page plug-in corresponding to the data processing event.

[0057] Step 504: based on the data processing template identifier, obtain the template plug-in corresponding to the data processing event.

[0058] Among them, the template plug-in refers to a plug-in saved in association with the data processing template identifier. The plug-in type of the template plug-in is a template binding plug-in, which can be understood as the template plug-in is bound to the data processing template corresponding to the data processing template identifier. After binding, the plug-in saved in association with the data processing template identifier, for example, the import template page shown in Figure 7 includes a plug-in selection control 702. Through the plug-in selection control 702, the selected plug-in can be bound to the import template in the import template page. After clicking Save, the computer device associates and saves the selected plug-in with the import template identifier of the import template, and obtains the associated saved relationship between the selected plug-in and the import template identifier. The import template identifier can be the code or name of the import template, etc.

[0059] Exemplarily, when there is a plug-in stored in association with the data processing template identifier, the computer device obtains the plug-in stored in association with the data processing template identifier, and determines the plug-in stored in association with the data processing template identifier as the template plug-in corresponding to the data processing event.

[0060] Step 506: Based on the data processing control identifier, obtain the control plug-in corresponding to the data processing event.

[0061] Among them, the control plug-in refers to a plug-in saved in association with the data processing control identifier. The plug-in type of the control plug-in is a control binding plug-in, which can be understood as the control plug-in is bound to the data processing control corresponding to the data processing control identifier. After binding, the plug-in is saved in association with the data processing control identifier. For example, as shown in the operation editing page of Figure 8, the operation editing page includes an import plug-in control 802. By importing the plug-in control 802, the selected plug-in can be bound to the data processing control. After clicking Save, the computer device associates and saves the selected plug-in with the data processing control identifier of the data processing control, and obtains the associated saved relationship between the selected plug-in and the data processing control identifier.

[0062] Exemplarily, when there is a plug-in saved in association with the data processing control identifier, the computer device obtains the plug-in saved in association with the data processing control identifier, and determines the plug-in saved in association with the data processing control identifier as the control plug-in corresponding to the data processing event.

[0063] Step 508: Based on the system identifier, obtain the global plug-in corresponding to the data processing event.

[0064] Among them, a global plug-in refers to a plug-in saved in association with a system identifier. The plug-in type of a global plug-in is a global binding plug-in, which can be understood as a global plug-in bound to the system corresponding to the system identifier. After binding, the plug-in saved in association with the system identifier, for example, a parameter configuration page as shown in FIG9 , includes an extended capability configuration control 902. The extended capability configuration control 902 can be used to bind the selected plug-in to the software system. After clicking Save, the computer device associates and saves the selected plug-in with the system identifier of the software system, and obtains an associated saved relationship between the selected plug-in and the system identifier.

[0065] Exemplarily, when there is a plug-in saved in association with the system identifier, the computer device obtains the plug-in saved in association with the system identifier, and determines the plug-in saved in association with the system identifier as a global plug-in corresponding to the data processing event.

[0066] Step 510: Based on the page plug-in, the template plug-in, the control plug-in and the global plug-in, multiple target plug-ins corresponding to the data processing event are obtained.

[0067] Exemplarily, when there is no corresponding dynamic plug-in for the page plug-in, template plug-in, control plug-in and global plug-in, the page plug-in, template plug-in, control plug-in and global plug-in are determined as multiple target plug-ins corresponding to the data processing event.

[0068] In this embodiment, multiple target plug-ins corresponding to the data processing event are obtained through the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier, that is, the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier can all have bound plug-ins, and the binding of the plug-in is not limited to the software system, and can be flexibly bound to at least one of the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier according to actual needs, thereby improving the flexibility of plug-in binding, and obtaining the target plug-in for processing the data processing event through the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier corresponding to the data processing event, thereby improving the adaptability of target plug-in acquisition.

[0069] In one embodiment, based on the page plug-in, the template plug-in, the control plug-in and the global plug-in, multiple target plug-ins corresponding to the data processing event are obtained, including:

[0070] When at least one of the page plug-in, the template plug-in, the control plug-in and the global plug-in has a corresponding dynamic plug-in, the page plug-in, the template plug-in, the control plug-in, the global plug-in and the dynamic plug-in are determined as multiple target plug-ins corresponding to the data processing event.

[0071] Among them, a dynamic plug-in refers to a plug-in bound to a plug-in, and the plug-in type of a dynamic plug-in is a dynamically bound plug-in.

[0072] Exemplarily, when at least one of the page plug-in, template plug-in, control plug-in and global plug-in has a corresponding dynamic plug-in, the computer device obtains the dynamic plug-in and determines the page plug-in, template plug-in, control plug-in, global plug-in and dynamic plug-in as multiple target plug-ins corresponding to the data processing event.

[0073] In this embodiment, at least one of the page plug-in, template plug-in, control plug-in and global plug-in has a corresponding dynamic plug-in. It can be understood that the plug-in is bound to other plug-ins according to actual needs, thereby further improving the flexibility of plug-in binding, and obtaining the dynamic plug-in through the page plug-in, template plug-in, control plug-in and global plug-in. The page plug-in, template plug-in, control plug-in, global plug-in and dynamic plug-in are determined as multiple target plug-ins corresponding to the data processing event, thereby further improving the adaptability of target plug-in acquisition.

[0074] In one embodiment, based on the plug-in type corresponding to the target plug-in, determining the calling order of the target plug-in includes:

[0075] For target plug-ins corresponding to the same plug-in type, obtain the binding order corresponding to the target plug-in; based on the binding order corresponding to the target plug-in, sort the target plug-ins corresponding to the plug-in type to obtain the target plug-in sequence corresponding to the plug-in type; based on the preset arrangement order corresponding to each plug-in type, sort the target plug-in sequences corresponding to multiple plug-in types to obtain the calling order of each target plug-in.

[0076] The binding order refers to the calling order of the target plug-in among multiple target plug-ins corresponding to the same plug-in type. The binding order can be determined according to the time when the target plug-in is bound. For example, the data processing template is bound to five plug-ins A, B, C, D and E. The binding times of the five plug-ins A, B, C, D and E are T1, T2, T3, T4 and T5 respectively. The order of T1, T2, T3, T4 and T5 is T1, T2, T3, T4 and T5. Then the binding order of the five plug-ins A, B, C, D and E is 1, 2, 3, 4 and 5 respectively, that is, the calling order of A is the first one among A, B, C, D and E, the calling order of B is the second one among A, B, C, D and E, the calling order of C is the third one among A, B, C, D and E, the calling order of D is the fourth one among A, B, C, D and E, and the calling order of E is the fifth one among A, B, C, D and E. The binding order can also be the order set by the configuration personnel. The preset arrangement order refers to the calling order of the target plug-in sequence corresponding to the plug-in type.

[0077] The calling order of the target plug-in refers to the order in which the target plug-in is called among the multiple target plug-ins corresponding to the data processing event. For example, the preset arrangement order of the global binding plug-in is 1st, the preset arrangement order of the list binding plug-in is 2nd, the preset arrangement order of the template binding plug-in is 3rd, the preset arrangement order of the control binding plug-in is 4th, and the preset arrangement order of the dynamic binding plug-in is 5th. The target plug-in sequence corresponding to the global binding plug-in is {A1}, the target plug-in sequence corresponding to the list binding plug-in is {B1, B2}, there is no template binding plug-in, the target plug-in sequence corresponding to the control binding plug-in is {C1, C2, C3}, and the target plug-in sequence corresponding to the dynamic binding plug-in is {D1}. Then the calling orders of A1, B1, B2, C1, C2, C3, and D1 are 1, 2, 3, 4, 5, 6, and 7 respectively.

[0078] Exemplarily, for each plug-in type, the computer device obtains the binding order of the target plug-ins corresponding to the plug-in type, sorts the target plug-ins corresponding to the plug-in type according to the binding order corresponding to the target plug-ins, and obtains the target plug-in sequence corresponding to the plug-in type; then obtains the preset arrangement order corresponding to each plug-in type, sorts the target plug-in sequences corresponding to multiple plug-in types according to the preset arrangement orders corresponding to the multiple plug-in types, and obtains the calling order of each target plug-in.

[0079] In this embodiment, the target plug-ins corresponding to the same plug-in type are first sorted to obtain a target plug-in sequence corresponding to the plug-in type, and then multiple target plug-in sequences are sorted based on the preset arrangement order corresponding to each plug-in type to obtain a calling order for each target plug-in, thereby avoiding errors in calling the target plug-in, and the preset arrangement order of the plug-in type can be flexibly set according to actual needs, thereby further improving the adaptability of the plug-in call.

[0080] In one embodiment, based on the calling order of the target plug-in, calling the target plug-in includes:

[0081] Obtain a method identifier to be executed corresponding to the data processing event; determine a target plug-in including a method corresponding to the method identifier to be executed as the plug-in to be executed corresponding to the method identifier to be executed; and call the method corresponding to the method identifier to be executed from the plug-in to be executed based on the calling order of the plug-ins to be executed.

[0082] The method identifier to be executed refers to a string representing the method to be executed. The method identifier to be executed is located in the program code that implements the data processing event. The method identifier to be executed can be located in multiple processing links of the data processing event. The plug-in to be executed refers to a target plug-in that includes the method corresponding to the method identifier to be executed. The number of plug-ins to be executed is at least one.

[0083] Exemplarily, in the process of processing data processing events, the computer device obtains the method identification to be executed for each method identification to be executed, determines the target plug-in including the method corresponding to the method identification to be executed as the plug-in to be executed corresponding to the method identification to be executed, and calls the method corresponding to the method identification to be executed from the plug-in to be executed based on the calling order of the plug-ins to be executed.

[0084] In this embodiment, the target plug-in including the method corresponding to the method identifier to be executed is determined as the plug-in to be executed corresponding to the method identifier to be executed. The plug-in to be executed includes the method corresponding to the method identifier to be executed. The method corresponding to the method identifier to be executed is called from the plug-in to be executed in the calling order of the plug-ins to be executed, so that the superposition of the methods corresponding to the method identifier to be executed can be achieved, thereby further improving the flexibility of plug-in calling.

[0085] In one embodiment, obtaining the identifier of the method to be executed corresponding to the data processing event includes:

[0086] Obtain a processing flow corresponding to a data processing event; the processing flow includes multiple processing links; in the process of executing the processing link, obtain an identifier of a method to be executed corresponding to the data processing event.

[0087] The processing flow refers to the process of processing data processing events, and the processing flow includes multiple processing links. For example, a data import event includes a template verification process as shown in FIG10 and a data import process as shown in FIG11. The template verification process includes five processing links, namely, opening the start page, opening the template download page, downloading the template, uploading the file and template verification. Opening the start page corresponds to method identifier 1 and method identifier 2, opening the template download page corresponds to method identifier 3, uploading the file corresponds to method identifier 4 and method identifier 5, and template verification corresponds to method identifier 6. Method identifiers 1 to 6 can be identifiers representing different methods, and each method identifier represents a corresponding method. The method identifiers corresponding to each processing link can be set according to actual needs. For example, method identifier 1 is after Load Start Page, which represents the method after the import boot start page is loaded. Method identifier 2 represents before Show Template Select List, which represents the method before opening the template download list page. Method identifier 3 is before Create Header Column, which represents the method after the template column header is created. Method identifier 4 is after Up load File, which represents the method after uploading the imported file. Method identifier 5 is beforeTemplate Validate, which represents the method before the uploaded data template is verified. Method identifier 6 is after TemplateValidate, represents the method after the uploaded data template is verified; the data import process includes 7 processing links, namely starting the task, initializing the context, parsing the table, data verification, temporary storage, calling the operation and ending the task. The above 7 processing links include 17 method identifiers. Method identifier 1 to method identifier 17 can be identifiers representing different methods. Each method identifier represents a corresponding method. The method identifier corresponding to each processing link can be set according to actual needs. The data export event includes the data export process shown in Figure 12. The data export process includes 5 processing links, namely initializing the context, obtaining the data primary key combination, querying the data source, writing the table header and writing the table data. The above 5 processing links include 8 method identifiers. Method identifier 1 to method identifier 8 can be identifiers representing different methods. Each method identifier represents a corresponding method. The method identifier corresponding to each processing link can be set according to actual needs.

[0088] Exemplarily, the computer device obtains a processing flow corresponding to the data processing event, and for each processing link in the processing flow, obtains an identifier of a method to be executed corresponding to the data processing event during the process of executing the processing link.

[0089] In this embodiment, by executing the processing link in the processing flow corresponding to the data processing event, the method identifier to be executed corresponding to the data processing event is obtained during the execution of the processing link. The method corresponding to the method identifier to be executed is located in the target plug-in, providing basic data for calling the target plug-in.

[0090] In an exemplary embodiment, before delivering the software system to the enterprise, the configuration personnel need to customize it according to the actual needs of the enterprise. The configuration personnel bind the plug-in to the list through the list page shown in FIG6 to obtain the association and preservation relationship between the plug-in and the page identifier of the page where the list is located; bind the plug-in to the data processing template through the import template page shown in FIG7 to obtain the association and preservation relationship between the plug-in and the data processing template identifier; bind the plug-in to the data processing control through the operation editing page shown in FIG8 to obtain the association and preservation relationship between the plug-in and the data processing control identifier; bind the plug-in to the software system through the parameter configuration page shown in FIG9 to obtain the association and preservation relationship between the plug-in and the system identifier, and bind the plug-in to the plug-in to obtain the association and preservation relationship between the plug-in and the plug-in. After the binding is completed, the target software system and the system identifier corresponding to the target software system are obtained.

[0091] When the user uses the target software system to process data, the computer device obtains the data processing event, and then obtains the data processing page identifier, data processing template identifier, data processing control identifier and system identifier of the data processing page corresponding to the data to be processed event; in the case where there is a plug-in saved in association with the data processing page identifier, the computer device obtains the plug-in saved in association with the data processing page identifier, and determines the plug-in saved in association with the data processing page identifier as the page plug-in corresponding to the data processing event; in the case where there is a plug-in saved in association with the data processing template identifier, the computer device obtains the plug-in saved in association with the data processing template identifier, and determines the plug-in saved in association with the data processing template identifier as the template plug-in corresponding to the data processing event; In the case where there is a plug-in saved in association with the data processing control identifier, the computer device obtains the plug-in saved in association with the data processing control identifier, and determines the plug-in saved in association with the data processing control identifier as a control plug-in corresponding to the data processing event; in the case where there is a plug-in saved in association with the system identifier, the computer device obtains the plug-in saved in association with the system identifier, and determines the plug-in saved in association with the system identifier as a global plug-in corresponding to the data processing event; in the case where there is a corresponding dynamic plug-in among at least one of the page plug-in, template plug-in, control plug-in and global plug-in, the computer device obtains the dynamic plug-in, and then determines the page plug-in, template plug-in, control plug-in, global plug-in and dynamic plug-in as multiple target plug-ins corresponding to the data processing event.

[0092] The computer device obtains the plug-in type corresponding to the target plug-in, obtains the binding order of the target plug-in corresponding to each plug-in type, sorts the target plug-ins corresponding to the plug-in type according to the binding order corresponding to the target plug-in, and obtains the target plug-in sequence corresponding to the plug-in type; then obtains the preset arrangement order corresponding to each plug-in type, sorts the target plug-in sequences corresponding to the multiple plug-in types according to the preset arrangement orders corresponding to the multiple plug-in types, and obtains the calling order of each target plug-in.

[0093] The computer device obtains the processing flow corresponding to the data processing event, and for each processing link in the processing flow, obtains the method identifier to be executed corresponding to the data processing event during the execution of the processing link, determines the target plug-in including the method corresponding to the method identifier to be executed as the plug-in to be executed corresponding to the method identifier to be executed, and calls the method corresponding to the method identifier to be executed from the plug-in to be executed based on the calling order of the plug-in to be executed.

[0094] In the above plug-in calling method, multiple target plug-ins corresponding to the data processing event are obtained through the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier, that is, the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier can all have bound plug-ins, and the binding of plug-ins is not limited to the software system. Each identifier can be bound to one or more plug-ins according to actual needs, thereby improving the scalability of plug-in binding. Moreover, compared with realizing the binding of plug-ins by modifying the software system program, binding the plug-in with the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier improves Improves the efficiency of plug-in binding; obtains the target plug-in for processing the data processing event through the data processing page identifier, data processing template identifier, data processing control identifier and system identifier corresponding to the data processing event. Since the plug-ins bound to the data processing page identifier, data processing template identifier, data processing control identifier and system identifier are all set according to actual needs, the obtained target plug-in is adapted to the actual needs. Then, the calling order of the target plug-in is determined according to the plug-in type of the target plug-in, and the target plug-in is called based on the calling order of the target plug-in. The preset arrangement order of the plug-in type is also set according to actual needs. Therefore, the adaptability of the plug-in call is further improved.

[0095] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0096] Based on the same inventive concept, the embodiment of the present application also provides a plug-in calling device for implementing the plug-in calling method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more plug-in calling device embodiments provided below can refer to the limitations on the plug-in calling method above, and will not be repeated here.

[0097] In one embodiment, as shown in FIG. 13 , a plug-in calling device is provided, including: a first acquisition module 1302, a second acquisition module 1304, a determination module 1306 and a calling module 1308, wherein:

[0098] The first acquisition module 1302 is used to acquire a data processing page identifier, a data processing template identifier, a data processing control identifier and a system identifier of a data processing page corresponding to a data processing event;

[0099] The second acquisition module 1304 is used to acquire multiple target plug-ins corresponding to the data processing event based on the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier;

[0100] A determination module 1306, configured to determine a calling order of the target plug-ins based on the plug-in types corresponding to the target plug-ins;

[0101] The calling module 1308 is used to call the target plug-in based on the calling order of the target plug-in.

[0102] In one embodiment, the second acquisition module 1304 is also used to: acquire the page plug-in corresponding to the data processing event based on the data processing page identifier; acquire the template plug-in corresponding to the data processing event based on the data processing template identifier; acquire the control plug-in corresponding to the data processing event based on the data processing control identifier; acquire the global plug-in corresponding to the data processing event based on the system identifier; and obtain multiple target plug-ins corresponding to the data processing event based on the page plug-in, template plug-in, control plug-in and global plug-in.

[0103] In one embodiment, the second acquisition module 1304 is also used to: when at least one of the page plug-in, template plug-in, control plug-in and global plug-in has a corresponding dynamic plug-in, determine the page plug-in, template plug-in, control plug-in, global plug-in and dynamic plug-in as multiple target plug-ins corresponding to the data processing event.

[0104] In one embodiment, the determination module 1306 is also used to: obtain the binding order corresponding to the target plug-in corresponding to the same plug-in type; sort the target plug-ins corresponding to the plug-in type based on the binding order corresponding to the target plug-in to obtain the target plug-in sequence corresponding to the plug-in type; sort the target plug-in sequences corresponding to multiple plug-in types based on the preset arrangement order corresponding to each plug-in type to obtain the calling order of each target plug-in.

[0105] In one embodiment, the calling module 1308 is also used to: obtain the method identifier to be executed corresponding to the data processing event; determine the target plug-in including the method corresponding to the method identifier to be executed as the plug-in to be executed corresponding to the method identifier to be executed; and call the method corresponding to the method identifier to be executed from the plug-in to be executed based on the calling order of the plug-ins to be executed.

[0106] In one embodiment, the calling module 1306 is further used to: obtain a processing flow corresponding to a data processing event; the processing flow includes multiple processing links; and in the process of executing the processing link, obtain an identifier of a method to be executed corresponding to the data processing event.

[0107] Each module in the above-mentioned plug-in calling device can be implemented in whole or in part by software, hardware or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0108] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be shown in FIG14. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, the memory, and the input / output interface are connected via a system bus, and the communication interface, the display unit, and the input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner may be implemented through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a plug-in calling method is implemented. The display unit of the computer device is used to form a visually visible picture, which may be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0109] Those skilled in the art will understand that the structure shown in FIG. 14 is merely a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0110] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0111] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0112] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0113] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0114] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0115] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0116] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A plug-in calling method, characterized in that: The method comprises: Obtaining a data processing page identifier, a data processing template identifier, a data processing control identifier, and a system identifier of a data processing page corresponding to a data processing event; Acquire multiple target plug-ins corresponding to the data processing event based on the data processing page identifier, the data processing template identifier, the data processing control identifier, and the system identifier; Determining a calling order of the target plug-ins based on the plug-in types corresponding to the target plug-ins; The target plug-ins are called based on the calling order of the target plug-ins.

2. The method according to claim 1, characterized in that The acquiring, based on the data processing page identifier, the data processing template identifier, the data processing control identifier, and the system identifier, a plurality of target plug-ins corresponding to the data processing event comprises: Based on the data processing page identifier, obtaining a page plug-in corresponding to the data processing event; Based on the data processing template identifier, obtaining a template plug-in corresponding to the data processing event; Based on the data processing control identifier, obtaining a control plug-in corresponding to the data processing event; Based on the system identifier, obtaining a global plug-in corresponding to the data processing event; Based on the page plug-in, the template plug-in, the control plug-in and the global plug-in, a plurality of target plug-ins corresponding to the data processing event are obtained.

3. The method according to claim 2, characterized in that The obtaining of a plurality of target plug-ins corresponding to the data processing event based on the page plug-in, the template plug-in, the control plug-in and the global plug-in comprises: In the case that at least one of the page plug-in, the template plug-in, the control plug-in and the global plug-in has a corresponding dynamic plug-in, the page plug-in, the template plug-in, the control plug-in, the global plug-in and the dynamic plug-in are determined as multiple target plug-ins corresponding to the data processing event.

4. The method according to claim 1, characterized in that The determining the calling order of the target plug-ins based on the plug-in type corresponding to the target plug-in includes: For a target plug-in corresponding to the same plug-in type, obtaining a binding order corresponding to the target plug-in; Based on the binding order corresponding to the target plug-in, sort the target plug-in corresponding to the plug-in type to obtain a target plug-in sequence corresponding to the plug-in type; Based on the preset arrangement order corresponding to each of the plug-in types, target plug-in sequences corresponding to the multiple plug-in types are sorted to obtain a calling order of each of the target plug-ins.

5. The method according to claim 1, characterized in that The calling sequence based on the target plug-in includes: Obtaining an identifier of a method to be executed corresponding to the data processing event; Determine the target plug-in including the method corresponding to the method identifier to be executed as the plug-in to be executed corresponding to the method identifier to be executed; Based on the calling order of the to-be-executed plug-ins, the method corresponding to the to-be-executed method identifier is called from the to-be-executed plug-in.

6. The method according to claim 5, characterized in that The step of obtaining the identifier of the method to be executed corresponding to the data processing event includes: Obtaining a processing flow corresponding to the data processing event; the processing flow includes multiple processing links; In the process of executing the processing link, an identifier of a method to be executed corresponding to the data processing event is obtained.

7. A plug-in calling device, characterized in that: The device comprises: A first acquisition module is used to acquire a data processing page identifier, a data processing template identifier, a data processing control identifier and a system identifier of a data processing page corresponding to a data processing event; A second acquisition module, configured to acquire a plurality of target plug-ins corresponding to the data processing event based on the data processing page identifier, the data processing template identifier, the data processing control identifier and the system identifier; A determination module, configured to determine a calling order of the target plug-ins based on the plug-in type corresponding to the target plug-in; The calling module is used to call the target plug-in based on the calling order of the target plug-in.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images