Construction method and device of internal plug-in of mechanism, program product and electronic equipment

Abstract

The invention discloses a construction method and device of an internal plug-in of an institution, a program product and electronic equipment, and relates to the field of financial science and technology or other related fields, the construction method comprises the following steps: receiving an internal plug-in adding request, generating a plug-in record based on plug-in information, adding the plug-in record into a preset plug-in data table, and adding the plug-in record into the preset plug-in data table; the method comprises the steps of scanning a preset plug-in data table based on a first preset interval time, detecting a plug-in resource packet corresponding to a plug-in record under the condition that the plug-in record of which the storage state is not stored is scanned to obtain a detection result, and updating the storage state of the plug-in record to be stored under the condition that the detection result indicates that the plug-in resource packet passes detection. And completing the construction of the internal plug-in corresponding to the plug-in record. According to the method and the device, the technical problem of relatively low development efficiency caused by incapability of effectively managing plug-ins in an institution in related technologies is solved.

Description

Technical Field

[0001] The present invention relates to the field of financial technology, and in particular to a method for constructing an internal plug-in of an institution, a device thereof, a program product, and an electronic device. Background Art

[0002] As the development model of front-end and back-end separation gradually matures, developers need more professional supporting tools to improve efficiency in the field of front-end R&D. In the financial industry, although many plug-ins and tools have emerged to meet this demand, these tools are often unable to effectively connect with external plug-in management systems due to the separation of internal and external networks. This leads to a lack of effective management of plug-in tools in the intranet, which makes some tools unable to be fully reused and even has problems with functional duplication. In addition, due to the separation of internal and external networks, it is also impossible to obtain external high-quality plug-in resources in real time, so that developers cannot get enough help in tool support, which affects development efficiency and quality.

[0003] Therefore, there is an urgent need for a method for constructing an internal plug-in so that the internal plug-in can be effectively managed.

[0004] To the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiment of the present invention provides a method for constructing an internal plug-in of an organization and its device, program product, and electronic device, so as to at least solve the technical problem in the related art that the internal plug-in of the organization cannot be effectively managed, resulting in low development efficiency.

[0006] According to one aspect of an embodiment of the present invention, a method for constructing an internal plug-in of an organization is provided, comprising: receiving a request for adding an internal plug-in, wherein the request for adding an internal plug-in carries at least: plug-in information, a plug-in resource package; generating a plug-in record based on the plug-in information, and adding the plug-in record to a preset plug-in data table, wherein the plug-in record includes: a storage status; scanning the preset plug-in data table based on a first preset interval time, and in the case of scanning a plug-in record whose storage status is not stored in the storage, detecting the plug-in resource package corresponding to the plug-in record to obtain a detection result; in the case where the detection result indicates that the plug-in resource package has passed the detection, updating the storage status of the plug-in record to stored in the storage, and completing the construction of the internal plug-in corresponding to the plug-in record.

[0007] In one embodiment of the present application, before receiving a request to add an internal plug-in, it also includes: determining a plug-in data table structure, wherein the plug-in data table structure includes at least: a publisher identification field, a plug-in version field, a plug-in type field, an entry status field, and an entry time field; based on the plug-in data table structure, constructing a preset plug-in data table at a preset plug-in service address.

[0008] In one embodiment of the present application, before receiving a request to add an internal plug-in, it also includes: building a front-end page and embedding the front-end page into a preset development tool, wherein the preset development tool is used to generate a plug-in resource package; replacing the resource address in the preset development tool with the preset plug-in service address where the preset plug-in data table is located.

[0009] In one embodiment of the present application, a preset development tool receives a plug-in request through a front-end page, and upon receiving the plug-in request, calls a preset plug-in data table based on a preset plug-in service address, and completes processing of the plug-in request based on the preset plug-in data table, wherein the plug-in request includes at least one of the following: an internal plug-in addition request, an internal plug-in update request, and an external plug-in synchronization request.

[0010] In one embodiment of the present application, based on a preset plug-in data table, a step of completing processing of a plug-in request includes: when the plug-in request is an internal plug-in addition request, adding the plug-in information and the plug-in resource package carried by the internal plug-in addition request to the preset plug-in data table; when the plug-in request is an internal plug-in update request, based on the plug-in identifier carried by the internal plug-in update request, querying the preset plug-in data table for a target plug-in record corresponding to the plug-in identifier, inserting the latest plug-in record associated with the target plug-in record into the preset plug-in data table, and uploading the latest plug-in resource package associated with the latest plug-in record; when the plug-in request is an external plug-in synchronization request, based on the external plug-in synchronization information carried by the external plug-in synchronization request, adding the external plug-in indicated by the external plug-in identifier carried by the external plug-in synchronization request to the preset plug-in data table.

[0011] In one embodiment of the present application, based on the external plug-in synchronization information carried by the external plug-in synchronization request, the step of adding the external plug-in indicated by the external plug-in identifier carried by the external plug-in synchronization request to the preset plug-in data table includes: based on the external plug-in identifier, determining the external plug-in address of the external plug-in, and splicing the external plug-in address with the external plug-in synchronization information to obtain the external plug-in information; based on the external plug-in information, pulling the external plug-in from the external plug-in address to a preset folder; based on a second preset interval time, detecting each external plug-in in the preset folder, and if the external plug-in detection passes, marking the external plug-in with a label indicating that the detection passes; and adding the external plug-in marked with the label indicating that the detection passes to the preset plug-in data table.

[0012] In one embodiment of the present application, after detecting the plug-in resource package corresponding to the plug-in record and obtaining the detection result, it also includes: when the detection result indicates that the plug-in resource package detection fails, determining the detection information and calling the mail system; sending the detection information to the publisher terminal indicated by the publisher identifier corresponding to the plug-in resource package through the mail system.

[0013] According to another aspect of an embodiment of the present invention, there is also provided a device for constructing an internal plug-in of an organization, comprising: a receiving unit, for receiving a request for adding an internal plug-in, wherein the request for adding an internal plug-in carries at least: plug-in information, a plug-in resource package; a generating unit, for generating a plug-in record based on the plug-in information, and adding the plug-in record to a preset plug-in data table, wherein the plug-in record comprises: a storage status; a scanning unit, for scanning the preset plug-in data table based on a first preset interval time, and when a plug-in record with a storage status of not being stored is scanned, detecting the plug-in resource package corresponding to the plug-in record, and obtaining a detection result; an updating unit, for updating the storage status of the plug-in record to stored, when the detection result indicates that the plug-in resource package has passed the detection, to complete the construction of the internal plug-in corresponding to the plug-in record.

[0014] In one embodiment of the present application, the construction device also includes: a first determination module, used to determine the plug-in data table structure before receiving an internal plug-in addition request, wherein the plug-in data table structure includes at least: a publisher identification field, a plug-in version field, a plug-in type field, an entry status field, and an entry time field; a first construction module, used to construct a preset plug-in data table at a preset plug-in service address based on the plug-in data table structure.

[0015] In one embodiment of the present application, the construction device also includes: a second construction module, which is used to build a front-end page before receiving a request to add an internal plug-in, and embed the front-end page into a preset development tool, wherein the preset development tool is used to generate a plug-in resource package; a first replacement module, which is used to replace the resource address in the preset development tool with the preset plug-in service address where the preset plug-in data table is located.

[0016] In one embodiment of the present application, a preset development tool receives a plug-in request through a front-end page, and upon receiving the plug-in request, calls a preset plug-in data table based on a preset plug-in service address, and completes processing of the plug-in request based on the preset plug-in data table, wherein the plug-in request includes at least one of the following: an internal plug-in addition request, an internal plug-in update request, and an external plug-in synchronization request.

[0017] In one embodiment of the present application, the construction device also includes: a processing unit, the processing unit including: a first adding module, which is used to add the plug-in information and plug-in resource package carried by the internal plug-in addition request to the preset plug-in data table when the plug-in request is an internal plug-in addition request; a first query module, which is used to query the target plug-in record corresponding to the plug-in identifier from the preset plug-in data table based on the plug-in identifier carried by the internal plug-in update request when the plug-in request is an internal plug-in update request, and insert the latest plug-in record associated with the target plug-in record into the preset plug-in data table, and upload the latest plug-in resource package associated with the latest plug-in record; a second adding module, which is used to add the external plug-in indicated by the external plug-in identifier carried by the external plug-in synchronization request to the preset plug-in data table based on the external plug-in synchronization information carried by the external plug-in synchronization request when the plug-in request is an external plug-in synchronization request.

[0018] In one embodiment of the present application, the second adding module includes: a first determining submodule, used to determine the external plug-in address of the external plug-in based on the external plug-in identifier, and splice the external plug-in address with the external plug-in synchronization information to obtain the external plug-in information; a first pulling submodule, used to pull the external plug-in from the external plug-in address to a preset folder based on the external plug-in information; a first detecting submodule, used to detect each external plug-in in the preset folder based on a second preset interval time, and if the external plug-in passes the detection, mark the external plug-in with a label indicating that the detection passed; the first adding submodule, used to add the external plug-in marked with the label indicating that the detection passed to the preset plug-in data table.

[0019] In one embodiment of the present application, the construction device also includes: a second determination module, which is used to determine the detection information and call the mail system after detecting the plug-in resource package corresponding to the plug-in record and obtaining the detection result, if the detection result indicates that the plug-in resource package fails the detection; a first sending module, which is used to send the detection information to the publisher terminal indicated by the publisher identifier corresponding to the plug-in resource package through the mail system.

[0020] According to another aspect of an embodiment of the present invention, there is also provided a computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the computer program implements any of the above-mentioned methods for constructing an internal plug-in of an institution.

[0021] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any one of the above-mentioned methods for constructing an internal plug-in of an organization.

[0022] In the present invention, by receiving a request for adding an internal plug-in, a plug-in record is generated based on the plug-in information, and the plug-in record is added to a preset plug-in data table. Based on a first preset interval time, the preset plug-in data table is scanned, and when a plug-in record with a storage status of not being stored is scanned, the plug-in resource package corresponding to the plug-in record is detected to obtain a detection result. When the detection result indicates that the plug-in resource package has passed the detection, the storage status of the plug-in record is updated to being stored, and the construction of the internal plug-in corresponding to the plug-in record is completed, thereby solving the technical problem in the related art that the plug-ins within the organization cannot be effectively managed, resulting in low development efficiency.

[0023] In the present invention, the construction process of the internal plug-in is managed by presetting the plug-in data table, including: building a new internal plug-in and detecting the plug-in resource package of the internal plug-in, thereby realizing the automatic detection and warehousing of the internal plug-in, improving the efficiency and accuracy of the internal plug-in construction, and achieving the technical effect of effectively managing the internal plug-in. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0025] Figure 1 A hardware structure block diagram of a computer terminal (or mobile device) for implementing a method for building an internal plug-in of an organization is shown;

[0026] Figure 2 is a flowchart of a method for constructing an internal plug-in of an organization according to Example 1 of the present application;

[0027] Figure 3 This is a schematic diagram of the front-end web page function display according to Example 1 of the present application;

[0028] Figure 4 is a schematic diagram showing the external resource synchronization service function according to Example 1 of the present application;

[0029] Figure 5 It is a schematic diagram of the system structure of the method for constructing the internal plug-in of the actuator according to Example 1 of the present application;

[0030] Figure 6 It is a schematic diagram of the resource storage operation process according to Example 1 of the present application;

[0031] Figure 7 is a schematic diagram of an optional device for constructing an internal plug-in of a mechanism according to an embodiment of the present application;

[0032] Figure 8 It is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0034] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0035] It should be noted that the method for constructing an internal plug-in and the device thereof in the present invention can be used in financial technology when constructing an internal plug-in, and can also be used in any field other than financial technology when constructing an internal plug-in. The present invention does not limit the application field of the method for constructing an internal plug-in and the device thereof.

[0036] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) collected and involved in the present invention are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data are in compliance with the relevant laws, regulations and standards of the relevant regions, necessary confidentiality measures are taken, and public order and good customs are not violated, and corresponding operation entrances are provided for users to choose to authorize or refuse. For example, an interface is set between the system and the relevant users or organizations. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0037] In the present invention, a front-end plug-in management method applied in financial scenarios is proposed. By building a unified plug-in management platform, plug-in assets are uniformly managed, released and promoted, and internal plug-ins are uniformly managed to improve asset reuse and development efficiency. In addition, through the external resource synchronization service, external high-quality plug-in resources can be obtained regularly, existing resource versions can be updated, and synchronized to the internal management platform, which is convenient for front-end personnel to obtain tools and install and use tools in a timely manner to improve development efficiency.

[0038] The present invention is described in detail below in conjunction with various embodiments.

[0039] Example 1

[0040] According to an embodiment of the present application, an embodiment of a method for constructing an internal plug-in of an organization is also provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0041] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal (or mobile device) for implementing a method for building an internal plug-in of an organization is shown. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more ( Figure 1 102a, 102b, ..., 102n are used to illustrate) processor 102 (processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, a keyboard, a cursor control device, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera, wherein the network interface may be connected to a wired and / or wireless network. A person of ordinary skill in the art will understand that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.

[0042] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0043] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the method for constructing the internal plug-in of the mechanism in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the method for constructing the internal plug-in of the mechanism is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0044] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0045] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0046] Under the above operating environment, this application provides Figure 2 The method for building an internal plug-in is shown. Figure 2 is a flowchart of a method for constructing an internal plug-in according to Example 1 of the present application, such as Figure 2 As shown, the method comprises the following steps:

[0047] Step S201: receiving an internal plug-in adding request, wherein the internal plug-in adding request carries at least plug-in information and a plug-in resource package.

[0048] In an embodiment of the present invention, the construction of internal plug-ins of an organization can be applied to a plug-in management system. Developers can enter the plug-in publishing page through the terminal on the front-end web (application) page or the development tool entrance (i.e., the front-end web page embedded in the development tool) to enter the plug-in information, upload the plug-in resource package, and generate an internal plug-in addition request. Afterwards, the plug-in management system can build the corresponding internal plug-in according to the received internal plug-in addition request, and realize the management of the built internal plug-in.

[0049] In the embodiment of the present invention, the plug-in information includes but is not limited to: publisher, plug-in version, plug-in type (internal build or external synchronization), etc.

[0050] Step S202: Generate a plug-in record based on the plug-in information, and add the plug-in record to a preset plug-in data table, wherein the plug-in record includes: storage status.

[0051] In an embodiment of the present invention, a corresponding plug-in record can be generated according to the plug-in information input by the terminal, and the plug-in record includes fields such as plug-in publisher, plug-in version, plug-in type, etc. The field value of each field is determined according to the plug-in information, and the field value corresponding to the storage status in the plug-in record is initialized to not stored. Then, the plug-in record is added to the preset plug-in data table to realize the management of internal plug-ins through the preset plug-in data table.

[0052] In an embodiment of the present invention, the data structure of the preset plug-in data table can be designed based on the data structure required by the development tool for developing the internal plug-in. For example, the data structure of the preset plug-in data table may include fields such as plug-in publisher, plug-in version, plug-in type, storage status, storage time, etc.

[0053] Step S203, based on the first preset interval time, scan the preset plug-in data table, and when a plug-in record with a storage status of not being stored is scanned, detect the plug-in resource package corresponding to the plug-in record to obtain a detection result.

[0054] In an embodiment of the present invention, the plug-in administrator can periodically scan the preset plug-in data table through the front-end web page (i.e., scan the preset plug-in data table once at a first preset interval (e.g., one week). If a plug-in record whose storage status is not stored is scanned, it is necessary to detect the plug-in resource package corresponding to the plug-in record, for example, to perform plug-in vulnerability scanning, internal plug-in function testing, etc., to obtain the detection result.

[0055] In this embodiment, if the detection is passed, the internal plug-in is put into storage, otherwise it is returned to storage.

[0056] Step S204: when the detection result indicates that the plug-in resource package has passed the detection, the storage status of the plug-in record is updated to storage, and the construction of the internal plug-in corresponding to the plug-in record is completed.

[0057] In an embodiment of the present invention, if the detection result indicates that the plug-in resource package has passed the detection, it means that the current internal plug-in can be used normally, and the storage status of the corresponding plug-in record can be updated to storage, so as to indicate to the user who is going to use the internal plug-in that the internal plug-in can be used normally.

[0058] In this embodiment, the front-end web page can display all plug-ins in the preset plug-in data table to the user. The user can click the required plug-in to enter the details page, click the install button, execute the installation instructions inside the development tool, and complete the installation.

[0059] In summary, by receiving a request for adding an internal plug-in, a plug-in record is generated based on the plug-in information, and the plug-in record is added to the preset plug-in data table. Based on the first preset interval time, the preset plug-in data table is scanned, and when a plug-in record with a storage status of not being stored is scanned, the plug-in resource package corresponding to the plug-in record is detected to obtain a detection result. When the detection result indicates that the plug-in resource package detection has passed, the storage status of the plug-in record is updated to stored, and the construction of the internal plug-in corresponding to the plug-in record is completed, thereby realizing automatic detection and storage of internal plug-ins, improving the efficiency and accuracy of internal plug-in construction, and achieving the technical effect of effectively managing internal plug-ins, thereby solving the technical problem that the related technology cannot effectively manage the plug-ins within the organization, resulting in low development efficiency.

[0060] In order to effectively manage internal plug-ins, it is necessary to construct a preset plug-in data table. In the method for constructing an internal plug-in of an organization provided in Example 1 of the present application, before receiving a request to add an internal plug-in, the plug-in data table structure is determined, wherein the plug-in data table structure includes at least: a publisher identification field, a plug-in version field, a plug-in type field, an entry status field, and an entry time field; based on the plug-in data table structure, a preset plug-in data table is constructed at the preset plug-in service address.

[0061] In an embodiment of the present invention, the plug-in data table structure can be determined according to the data structure required by the development tool for developing the internal plug-in. For example, the data table structure is designed according to the information required by the development tool for developing the internal plug-in (such as the plug-in publisher, plug-in version, plug-in type, storage status, storage time, etc.).

[0062] In this embodiment, the data table structure includes at least the following fields: a publisher identification field, which is used to record the information of the creator or contributor of the plug-in, which can be an employee ID, name or team name, to facilitate subsequent traceability and management; a plug-in version field, which is used to record the version number of the plug-in, which helps to manage and update the plug-in to ensure that the latest or most stable version is used; a plug-in type field: used to distinguish the source of the plug-in, whether it is internally developed or from an external open source community, which affects the use rights and security assessment of the plug-in; an entry status field: used to mark whether the plug-in has been officially included in the plug-in library, as well as its review status, such as "under review", "included", "failed", etc.; an entry time field: records the specific time when the plug-in is officially included in the plug-in library, which helps to statistically analyze the update frequency and usage trends of the plug-in.

[0063] In this embodiment, after the structure of the plug-in data table is clarified, the plug-in data table can be constructed on the preset plug-in service address. The preset plug-in service address refers to the server address of the plug-in management platform, and the construction of the plug-in data table here means creating a specific table in the database of the server for storing and managing the information of all plug-ins.

[0064] In this embodiment, by constructing a plug-in data table with the above fields, effective management and optimization of plug-in assets can be achieved, improving the efficiency and security of front-end development in financial scenarios. At the same time, it also facilitates the continuous iteration of plug-ins and collaboration between developers.

[0065] In order to effectively manage internal plug-ins, it is necessary to change the resource address within the preset development tool. In the method for constructing an internal plug-in of an organization provided in Example 1 of the present application, before receiving a request to add a new internal plug-in, a front-end page is constructed and embedded in the preset development tool, wherein the preset development tool is used to generate a plug-in resource package; the resource address within the preset development tool is replaced with the preset plug-in service address where the preset plug-in data table is located.

[0066] In the embodiment of the present invention, a user interface (i.e., a front-end page, such as a front-end web page) is designed and developed, which allows developers to publish and update plug-ins and register external resources. This front-end page needs to have a good user experience and provide clear forms and interactive options to facilitate developers to fill in necessary information, such as plug-in name, version number, publisher, etc., and upload plug-in resource packages.

[0067] In the embodiment of the present invention, in order to seamlessly integrate the front-end page into the daily work of developers, this page can be embedded into a preset development tool (i.e., a tool for generating a plug-in resource package), for example, the front-end page can be embedded into the development tool through WebView (web page view) technology. In this way, developers can directly access and operate the front-end page in the development tool without leaving the development environment or switching to a different browser, thereby improving the efficiency and convenience of use.

[0068] In the embodiment of the present invention, in order to enable the development tool to access and use the internally built plug-in service, the resource address preset in the development tool (usually the address pointing to the external plug-in library) can be replaced with the plug-in service address pointing to the preset plug-in data table. In this way, when searching and installing plug-ins, the development tool will directly obtain resources from the internal plug-in service, thereby realizing the internal management of plug-ins.

[0069] In this embodiment, the front-end page is embedded into the preset development tool and the resource address in the preset development tool is replaced, which can realize internal management and convenient access of plug-in resources, thereby improving development efficiency, enhancing security, optimizing resource management, promoting internal sharing, improving the convenience of plug-in acquisition and improving developer experience in front-end development in financial scenarios.

[0070] Figure 3 is a schematic diagram of the front-end web page function display according to Example 1 of the present application, such as Figure 3 As shown, the three main functional areas of the front-end web page are displayed, including: the area for developers to publish plug-ins, the area for auditors to enter the library, and the area for external resource registration.

[0071] The developer plugin publishing area provides the operation interface required by front-end developers to publish plugins. Developers can fill in the plugin details in this interface, such as plugin name, version number, publisher information, etc., and upload the plugin resource package. Developers can choose to add new plugins or update existing plugin versions, and submit the plugins to the plugin service for subsequent review and storage by filling in the corresponding form and uploading resources.

[0072] Auditors' storage area: Auditors or plug-in administrators use this area to perform plug-in storage audit operations, view plug-in information and resource packages submitted by developers, and perform security vulnerability scans and functional tests. If the plug-in passes all tests, the auditor can mark the plug-in information and resource package as "approved" and perform formal storage operations. If there are any problems with the plug-in, it can be delisted and the developer will be notified to make modifications.

[0073] External resource registration area: allows developers to register external plug-in resources, including information such as the publishing author, plug-in name and version number. This information will be submitted to the external resource synchronization service, which will regularly pull plug-in resources from the external resource library based on the registered information, perform security scanning and testing, and resources that pass the test will be synchronized to the internal plug-in management platform for use by intranet developers.

[0074] In order to improve the accuracy of processing plug-in requests, in the method for constructing an internal plug-in of an organization provided in Example 1 of the present application, a preset development tool receives a plug-in request through a front-end page, and upon receiving the plug-in request, calls a preset plug-in data table based on a preset plug-in service address, and completes the processing of the plug-in request based on the preset plug-in data table, wherein the plug-in request includes at least one of the following: an internal plug-in addition request, an internal plug-in update request, and an external plug-in synchronization request.

[0075] In an embodiment of the present invention, a front-end page embedded in a preset development tool can become an entry for receiving plug-in requests. When a developer submits a request through the front-end page, the page will send the request information (such as plug-in name, version number, publisher ID, etc.) to the development tool. The development tool can send a request to the plug-in service according to the preset plug-in service address. After receiving the request, the plug-in service will query the preset plug-in data table and perform corresponding operations according to the request type to complete the processing of the plug-in request. For example, an internal plug-in addition request will trigger an insert operation of the plug-in data table, an update request will trigger an update operation, and an external plug-in synchronization request will trigger a query of data in the table and a synchronization operation of external resources.

[0076] Here, the plug-in request may be a request for adding or updating an internal plug-in (ie, an internal plug-in adding request, an internal plug-in updating request), or may be a request for synchronizing external plug-in resources (ie, an external plug-in synchronization request).

[0077] In this embodiment, the plug-in service can process the request based on the query results and predefined business logic. For example, for a new or updated request, the server will perform a security scan and functional test, and after passing the test, update the plug-in data table and notify the requester; for an external plug-in synchronization request, the server will pull external resources, scan and store them, and update the plug-in data table at the same time.

[0078] In this embodiment, the combination of the preset development tools and the front-end page, as well as the interaction with the preset plug-in service address, not only simplifies the plug-in management process and improves operational efficiency, but also promotes internal and external linkage of plug-in resources while ensuring security, optimizes the developer experience, and enhances team collaboration and code reuse capabilities.

[0079] In order to further improve the accuracy of processing plug-in requests, in the method for constructing an internal plug-in of an organization provided in Example 1 of the present application, when the plug-in request is an internal plug-in addition request, the plug-in information and the plug-in resource package carried by the internal plug-in addition request are added to the preset plug-in data table; when the plug-in request is an internal plug-in update request, based on the plug-in identifier carried by the internal plug-in update request, the target plug-in record corresponding to the plug-in identifier is queried from the preset plug-in data table, and the latest plug-in record associated with the target plug-in record is inserted into the preset plug-in data table, and the latest plug-in resource package associated with the latest plug-in record is uploaded; when the plug-in request is an external plug-in synchronization request, based on the external plug-in synchronization information carried by the external plug-in synchronization request, the external plug-in indicated by the external plug-in identifier carried by the external plug-in synchronization request is added to the preset plug-in data table.

[0080] In an embodiment of the present invention, when the plug-in request is for the addition of an internal plug-in, the preset development tool receives the plug-in request (including plug-in information (such as plug-in name, version number, publisher identifier, etc.) and plug-in resource package) through the front-end page. Then, the plug-in information and plug-in resource package are submitted to the plug-in service. Afterwards, the plug-in service can add these plug-in information and plug-in resource packages to the preset plug-in data table for storage. In this way, it is ensured that the detailed information of each newly added plug-in is accurately recorded for subsequent retrieval, management and use.

[0081] In an embodiment of the present invention, if the plug-in request is an update of an internal plug-in, the plug-in identifier (i.e., a unique identifier of the plug-in, such as a combination of the plug-in name and the version number) can be obtained from the internal plug-in update request. Then, the record of the target plug-in (i.e., the target plug-in record) can be queried from the preset plug-in data table according to the plug-in identifier. Once the target plug-in record is found, a new record (i.e., the latest plug-in record) can be created to represent the updated plug-in status, and this record can be associated with the original target plug-in record. At the same time, the latest plug-in resource package is uploaded. In this way, the plug-in data table records the update history of the plug-in, which is convenient for tracing and management.

[0082] In an embodiment of the present invention, if the plug-in request is an external plug-in synchronization request, a specific plug-in (i.e., the external plug-in indicated by the external plug-in identifier carried by the external plug-in synchronization request) can be obtained from an external resource according to the external plug-in synchronization information (including the external plug-in identifier, such as the plug-in name and version number) carried in the request. After obtaining these external plug-ins, they can be added to the preset plug-in data table to implement internal management of external resources. In this way, not only can external high-quality resources be introduced, but also it can be ensured that these resources can be used only after meeting internal security standards.

[0083] In order to synchronize external high-quality plug-ins, in the method for constructing internal plug-ins of an organization provided in Example 1 of the present application, based on the external plug-in identifier, the external plug-in address of the external plug-in is determined, and the external plug-in address is spliced ​​with the external plug-in synchronization information to obtain the external plug-in information; based on the external plug-in information, the external plug-in is pulled from the external plug-in address to a preset folder; based on a second preset interval time, each external plug-in in the preset folder is tested, and if the external plug-in passes the test, a label indicating that the test has passed is marked on the external plug-in; the external plug-in marked with a label indicating that the test has passed is added to the preset plug-in data table.

[0084] In the embodiment of the present invention, when an external plug-in synchronization request is received, the external address of the plug-in can be determined according to the external plug-in identifier (usually the name and version number of the plug-in) carried in the request. For example, by splicing the plug-in identifier with the URL (Uniform Resource Locator) template of the known external plug-in resource library, a URL that accurately points to the required plug-in can be obtained to facilitate subsequent resource retrieval.

[0085] Then, the external plug-in address can be spliced ​​with other synchronization information carried in the request (such as publisher, plug-in type, etc.) to form complete external plug-in information. In this way, all necessary metadata can be carried when pulling plug-in resources, which is helpful for subsequent management and use. Afterwards, according to the spliced ​​external plug-in information, plug-in resources can be pulled from the external plug-in address and saved to a pre-set internal folder (i.e., preset folder). In this way, external plug-in resources can be imported into the intranet environment in the financial field, providing internal developers with a way to access and use them.

[0086] In an embodiment of the present invention, each external plug-in in a preset folder can be subjected to regular security inspection and functional testing based on a second preset interval (such as daily frequency) to ensure that these plug-ins do not introduce security vulnerabilities or incompatibility issues, and only those external plug-ins that pass the inspection will be labeled with a "passed inspection" label, indicating that it has been safety verified and can be used safely. Then, the external plug-in information marked with the passed inspection label can be added to the preset plug-in data table (for example, traversing all the tagged external plug-in resources, performing batch uploads, to complete the warehousing), realizing the internal management of external plug-in resources. In this way, the internal development team can easily search and use these verified external plug-in resources just like using internal plug-ins.

[0087] Figure 4 is a schematic diagram showing the external resource synchronization service function according to Example 1 of the present application, such as Figure 4As shown, the relevant service functions of the external resource synchronization service are displayed, including: resource pulling service, resource batch uploading service, and vulnerability scanning service.

[0088] Among them, the resource pulling service is responsible for pulling plug-in resources from the external resource library. When the developer registers a new external plug-in resource (including the publishing author, plug-in name and version number) on the front-end web page, the resource pulling service will splice this information with the URL template of the known external plug-in resource library to form an accurate plug-in resource address. Then, according to these addresses, the external plug-in resources are automatically pulled into the preset internal folder. This process can be performed regularly, such as pulling new resources on a daily or weekly basis to ensure that the resources on the financial plug-in management platform are up to date.

[0089] Vulnerability scanning service: After the resource pulling service pulls external plug-in resources into the internal folder, the vulnerability scanning service will periodically perform security checks on these resources. Through the internal vulnerability scanning tool, each external plug-in in the folder is batch scanned to check whether there are security vulnerabilities. For plug-ins that pass the security check, the vulnerability scanning service will mark a "Passed" label, indicating that no security issues were found in the plug-in and it is suitable for use in the internal environment.

[0090] Resource batch upload service: After the vulnerability scanning service completes the detection and marks the detection pass label, the resource batch upload service will traverse all external plug-in resources with the detection pass label in the folder and perform batch upload operations. These resources will be uploaded to the database of the plug-in management platform and become part of the internal plug-in library. After the upload is completed, internal developers can access and use these security-verified external plug-in resources through development tools or web pages.

[0091] In order to improve the storage rate of constructed internal plug-ins, in the method for constructing internal plug-ins of an organization provided in Example 1 of the present application, after detecting the plug-in resource package corresponding to the plug-in record and obtaining the detection result, if the detection result indicates that the plug-in resource package fails the detection, the detection information is determined and the mail system is called; the detection information is sent through the mail system to the publisher terminal indicated by the publisher identifier corresponding to the plug-in resource package.

[0092] In an embodiment of the present invention, during the detection process of the plug-in resource package, if any problem of not meeting the safety standard, having loopholes or incomplete functions is found, detailed detection information can be generated, including: the specific problems detected, potential security risks, and necessary modification suggestions, so that the plug-in publisher can clearly understand the reasons for the failure of the plug-in. In addition, in order to promptly notify the plug-in publisher that its plug-in detection has not passed, the plug-in service will call the integrated mail system, which can be realized through API (Application Programming Interface, i.e., application programming interface), ensuring that the detection information can be quickly and accurately transmitted. The detection information is then sent to the publisher terminal corresponding to the plug-in resource package publisher identification through the mail system.

[0093] Here, the publisher ID is the unique ID of the plugin publisher in the system, which can be associated with the email address provided when registering. By sending emails, the system can directly notify the plugin publisher of the status of its plugin and provide a detailed detection report so that the publisher can make subsequent modifications and resubmit.

[0094] In this embodiment, through automated detection and notification processes, not only the security and efficiency of front-end plug-in management in financial scenarios are enhanced, but also the continuous improvement of plug-in quality is promoted, the internal communication and collaboration processes are optimized, and clear feedback is provided to plug-in publishers, thereby improving the operating efficiency and asset quality of the entire plug-in management system.

[0095] Figure 5 is a schematic diagram of the system structure of the method for constructing the internal plug-in of the actuator according to Example 1 of the present application, such as Figure 5 As shown, it includes: user layer, service layer, and data layer. Among them, the user layer includes: development tools, front-end web pages, and mail system; the service layer includes: plug-in services and external resource synchronization services; the data layer includes: database.

[0096] exist Figure 5 The database is the core data storage part of the entire system, which is used to save all the information of the plug-in, including but not limited to: plug-in name, version number, publisher, plug-in type, storage status, storage time, and plug-in resource package, etc.

[0097] The plug-in service is a backend service for receiving, processing and managing plug-ins. It is responsible for receiving plug-in information and resource packages submitted by front-end web pages and development tools, performing preliminary format and integrity checks, and then storing the plug-in information in the database for subsequent review and release processes. The plug-in service also provides plug-in query, download and version management functions, allowing developers to easily find and use the required plug-ins.

[0098] The external resource synchronization service is used to regularly pull plug-in resources from the external resource library, perform security scanning and testing, and store the resources that pass the test into the internal plug-in management platform. Through the external resource information registered by the developer (such as the publisher, plug-in name and version number), it communicates with the interface of the external resource library, automatically obtains resources, and then executes the internal security detection process to ensure the security of the resources. Through this service, the internal plug-in library can be synchronized with the latest external plug-in resources, providing developers with the latest tools and functions.

[0099] The front-end web page is part of the user interface, providing an intuitive interface for the plug-in management platform, allowing users to access it through a browser. The front-end web page integrates functions such as plug-in publishing, auditor storage operations, and external resource registration, allowing developers and auditors to operate on a unified platform, improving the efficiency of plug-in management.

[0100] The development tool is the environment where front-end developers actually code and build applications. By embedding the web page of the plug-in management platform into the development tool, developers can publish, query, and install plug-ins without leaving their work environment. The development tool is also responsible for executing the automatic installation and automatic update functions of plug-ins, as well as communicating with the plug-in service to obtain plug-in lists and resources.

[0101] The mail system is responsible for sending notifications of audit information, plugin status changes, etc. to relevant personnel, such as plugin publishers or reviewers. Through the mail system, the timeliness and reliability of information transmission can be ensured, and the transparency of plugin management and review processes can be enhanced.

[0102] Figure 6 is a schematic diagram of the resource storage operation process according to Example 1 of the present application, such as Figure 6 As shown, you can first determine whether it is a new plug-in or an updated plug-in. If it is a new plug-in, fill in the information: publisher, version, plug-in type, etc.; if it is an updated plug-in, enter the plug-in name to find the original version and fill in the version number. Then, upload the resource package. After that, the plug-in administrator performs the inventory review. You can first perform a vulnerability scan. If the vulnerability scan passes, continue to perform the internal plug-in function test. If the test is successful, the uploader is notified by email and the database is updated. If the vulnerability scan does not pass or the test fails, modify the resource package according to the audit information, and re-determine whether it is a new plug-in or an updated plug-in, and enter the subsequent process until the vulnerability scan passes and the internal plug-in function test succeeds.

[0103] The method for constructing an internal plug-in of an organization provided in an embodiment of the present application receives a request for adding an internal plug-in, generates a plug-in record based on plug-in information, and adds the plug-in record to a preset plug-in data table. Based on a first preset interval, the preset plug-in data table is scanned, and when a plug-in record with a storage status of not being stored is scanned, the plug-in resource package corresponding to the plug-in record is detected to obtain a detection result. When the detection result indicates that the plug-in resource package has passed the detection, the storage status of the plug-in record is updated to being stored, and the construction of the internal plug-in corresponding to the plug-in record is completed, thereby realizing automatic detection and storage of internal plug-ins, improving the efficiency and accuracy of internal plug-in construction, and achieving the technical effect of effectively managing internal plug-ins, thereby solving the technical problem in the related art that plug-ins within the organization cannot be effectively managed, resulting in low development efficiency.

[0104] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0105] Example 2

[0106] The embodiment of the present application also provides a device for constructing an internal plug-in of an organization. It should be noted that the device for constructing an internal plug-in of the embodiment of the present application can be used to execute the method for constructing an internal plug-in of an organization provided in the embodiment of the present application. The device for constructing an internal plug-in of an organization provided in the embodiment of the present application is introduced below.

[0107] According to an embodiment of the present application, a device for implementing the method for constructing the above-mentioned internal plug-in of the organization is also provided. Figure 7 is a schematic diagram of an optional construction device for an internal plug-in of an organization according to an embodiment of the present application, such as Figure 7 As shown, the construction device may include: a receiving unit 70, a generating unit 71, a scanning unit 72, and an updating unit 73.

[0108] The receiving unit 70 is used to receive an internal plug-in adding request, wherein the internal plug-in adding request carries at least: plug-in information and plug-in resource package;

[0109] The generating unit 71 is used to generate a plug-in record based on the plug-in information, and add the plug-in record to the preset plug-in data table, wherein the plug-in record includes: storage status;

[0110] The scanning unit 72 is used to scan the preset plug-in data table based on the first preset interval time, and when a plug-in record with a storage status of not being stored is scanned, detect the plug-in resource package corresponding to the plug-in record to obtain a detection result;

[0111] The updating unit 73 is used to update the storage status of the plug-in record to storage when the detection result indicates that the plug-in resource package has passed the detection, and complete the construction of the internal plug-in corresponding to the plug-in record.

[0112] The device for constructing an internal plug-in of an organization provided in an embodiment of the present application receives a request for adding an internal plug-in through a receiving unit 70, generates a plug-in record based on the plug-in information through a generating unit 71, and adds the plug-in record to a preset plug-in data table, scans the preset plug-in data table based on a first preset interval time through a scanning unit 72, and in the case of scanning a plug-in record with a storage status of not being stored in the storage, detects the plug-in resource package corresponding to the plug-in record to obtain a detection result, and in the case of an update unit 73 indicating that the detection of the plug-in resource package has passed, updates the storage status of the plug-in record to stored in the storage, completes the construction of the internal plug-in corresponding to the plug-in record, realizes automatic detection and storage of internal plug-ins, improves the efficiency and accuracy of internal plug-in construction, and achieves the technical effect of effectively managing internal plug-ins, thereby solving the technical problem that the plug-ins within the organization cannot be effectively managed in the related technology, resulting in low development efficiency.

[0113] Optionally, the construction device also includes: a first determination module, used to determine the plug-in data table structure before receiving an internal plug-in addition request, wherein the plug-in data table structure includes at least: a publisher identification field, a plug-in version field, a plug-in type field, an entry status field, and an entry time field; a first construction module, used to construct a preset plug-in data table at a preset plug-in service address based on the plug-in data table structure.

[0114] Optionally, the construction device also includes: a second construction module, used to build a front-end page before receiving a request to add an internal plug-in, and embed the front-end page into a preset development tool, wherein the preset development tool is used to generate a plug-in resource package; a first replacement module, used to replace the resource address in the preset development tool with a preset plug-in service address where the preset plug-in data table is located.

[0115] Optionally, the preset development tool receives a plug-in request through a front-end page, and upon receiving the plug-in request, calls a preset plug-in data table based on a preset plug-in service address, and completes processing of the plug-in request based on the preset plug-in data table, wherein the plug-in request includes at least one of the following: an internal plug-in addition request, an internal plug-in update request, and an external plug-in synchronization request.

[0116] Optionally, the construction device also includes: a processing unit, the processing unit includes: a first adding module, which is used to add the plug-in information and the plug-in resource package carried by the internal plug-in addition request to the preset plug-in data table when the plug-in request is an internal plug-in addition request; a first query module, which is used to query the target plug-in record corresponding to the plug-in identifier from the preset plug-in data table based on the plug-in identifier carried by the internal plug-in update request when the plug-in request is an internal plug-in update request, and insert the latest plug-in record associated with the target plug-in record into the preset plug-in data table, and upload the latest plug-in resource package associated with the latest plug-in record; a second adding module, which is used to add the external plug-in indicated by the external plug-in identifier carried by the external plug-in synchronization request to the preset plug-in data table based on the external plug-in synchronization information carried by the external plug-in synchronization request when the plug-in request is an external plug-in synchronization request.

[0117] Optionally, the second adding module includes: a first determination submodule, used to determine the external plug-in address of the external plug-in based on the external plug-in identifier, and splice the external plug-in address with the external plug-in synchronization information to obtain the external plug-in information; a first pulling submodule, used to pull the external plug-in from the external plug-in address to a preset folder based on the external plug-in information; a first detection submodule, used to detect each external plug-in in the preset folder based on a second preset interval time, and if the external plug-in passes the detection, mark the external plug-in with a label of passed detection; the first adding submodule, used to add the external plug-in marked with a label of passed detection to the preset plug-in data table.

[0118] Optionally, the construction device also includes: a second determination module, which is used to determine the detection information and call the mail system after obtaining the detection result of the plug-in resource package corresponding to the detection plug-in record, if the detection result indicates that the plug-in resource package fails the detection; a first sending module, which is used to send the detection information to the publisher terminal indicated by the publisher identifier corresponding to the plug-in resource package through the mail system.

[0119] The above-mentioned construction device may also include a processor and a memory. The above-mentioned receiving unit 70, generating unit 71, scanning unit 72, updating unit 73, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0120] The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and when the detection result indicates that the detection of the plug-in resource package has passed, the storage status of the plug-in record is updated to storage by adjusting the kernel parameters, and the construction of the internal plug-in corresponding to the plug-in record is completed.

[0121] The above-mentioned memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash memory (fl ash RAM), and the memory includes at least one storage chip.

[0122] It should be noted that the receiving unit 70, generating unit 71, scanning unit 72, and updating unit 73 correspond to steps S201 to S204 in Embodiment 1, and the examples and application scenarios implemented by the above units and the corresponding steps are the same, but are not limited to the contents disclosed in the above Embodiment 1. It should be noted that the above units can be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n), and the above units can also be run in the computer terminal 10 provided in Embodiment 1 as part of the device.

[0123] Example 3

[0124] An embodiment of the present application may provide an electronic device, Figure 8 is a structural block diagram of an electronic device according to an embodiment of the present application. Figure 8 As shown, the electronic device may include: one or more ( Figure 8 (only one is shown) processor 802, memory 804, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0125] Wherein, the memory can be used to store software programs and modules, such as the method for constructing the internal plug-in of the mechanism in the embodiment of the present application and the program instructions / modules corresponding to the device, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the method for constructing the internal plug-in of the mechanism. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0126] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: receiving an internal plug-in addition request, wherein the internal plug-in addition request carries at least: plug-in information, plug-in resource package; generating a plug-in record based on the plug-in information, and adding the plug-in record to a preset plug-in data table, wherein the plug-in record includes: storage status; based on a first preset interval time, scanning the preset plug-in data table, and in the case of scanning a plug-in record with a storage status of not being stored in the storage, detecting the plug-in resource package corresponding to the plug-in record to obtain a detection result; in the case where the detection result indicates that the plug-in resource package has passed the detection, updating the storage status of the plug-in record to storage, and completing the construction of the internal plug-in corresponding to the plug-in record.

[0127] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: determine the plug-in data table structure, wherein the plug-in data table structure includes at least: a publisher identification field, a plug-in version field, a plug-in type field, an entry status field, and an entry time field; based on the plug-in data table structure, construct a preset plug-in data table at the preset plug-in service address.

[0128] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: build a front-end page and embed the front-end page into a preset development tool, wherein the preset development tool is used to generate a plug-in resource package; replace the resource address in the preset development tool with the preset plug-in service address where the preset plug-in data table is located.

[0129] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: the preset development tool receives the plug-in request through the front-end page, and when the plug-in request is received, calls the preset plug-in data table based on the preset plug-in service address, and completes the processing of the plug-in request based on the preset plug-in data table, wherein the plug-in request includes at least one of the following: an internal plug-in addition request, an internal plug-in update request, and an external plug-in synchronization request.

[0130] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: when the plug-in request is an internal plug-in addition request, the plug-in information and plug-in resource package carried by the internal plug-in addition request are added to the preset plug-in data table; when the plug-in request is an internal plug-in update request, based on the plug-in identifier carried by the internal plug-in update request, the target plug-in record corresponding to the plug-in identifier is queried from the preset plug-in data table, and the latest plug-in record associated with the target plug-in record is inserted into the preset plug-in data table, and the latest plug-in resource package associated with the latest plug-in record is uploaded; when the plug-in request is an external plug-in synchronization request, based on the external plug-in synchronization information carried by the external plug-in synchronization request, the external plug-in indicated by the external plug-in identifier carried by the external plug-in synchronization request is added to the preset plug-in data table.

[0131] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: based on the external plug-in identifier, determine the external plug-in address of the external plug-in, and splice the external plug-in address with the external plug-in synchronization information to obtain the external plug-in information; based on the external plug-in information, pull the external plug-in from the external plug-in address to a preset folder; based on the second preset interval time, detect each external plug-in in the preset folder, and if the external plug-in passes the detection, mark the external plug-in with a label of passing the detection; add the external plug-in marked with the label of passing the detection to the preset plug-in data table.

[0132] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: when the detection result indicates that the plug-in resource package detection fails, determine the detection information and call the mail system; send the detection information to the publisher terminal indicated by the publisher identifier corresponding to the plug-in resource package through the mail system.

[0133] By adopting the embodiment of the present application, a scheme for constructing an internal plug-in of an organization is provided. By receiving a request for adding an internal plug-in, a plug-in record is generated based on the plug-in information, and the plug-in record is added to a preset plug-in data table. Based on a first preset interval time, the preset plug-in data table is scanned, and when a plug-in record with a storage status of not being stored is scanned, the plug-in resource package corresponding to the plug-in record is detected to obtain a detection result. When the detection result indicates that the plug-in resource package has passed the detection, the storage status of the plug-in record is updated to being stored, and the construction of the internal plug-in corresponding to the plug-in record is completed, the automatic detection and storage of the internal plug-in is realized, the efficiency and accuracy of the internal plug-in construction are improved, and the technical effect of effectively managing the internal plug-in is achieved, thereby solving the technical problem that the plug-in within the organization cannot be effectively managed in the related technology, resulting in low development efficiency.

[0134] It can be understood by those skilled in the art that Figure 8 The structure shown is for illustration only, and the electronic device may also be a terminal device such as a smart phone, a tablet computer, a PDA, and a Mobile Internet Device (MID). Figure 8 The structure of the electronic device is not limited. Figure 8 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 8 Different configurations shown.

[0135] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0136] Example 4

[0137] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the method for constructing the internal plug-in of the organization provided in the first embodiment.

[0138] Optionally, in this embodiment, the above storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0139] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing the steps of the method for constructing an internal plug-in of an execution organization.

[0140] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0141] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0142] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0143] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0144] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0145] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or CD-ROM and other media that can store program codes.

[0146] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for constructing an internal plug-in of an organization, characterized in that: include: Receive an internal plug-in adding request, wherein the internal plug-in adding request carries at least: plug-in information and a plug-in resource package; Based on the plug-in information, a plug-in record is generated, and the plug-in record is added to a preset plug-in data table, wherein the plug-in record includes: storage status; Based on a first preset interval time, scanning the preset plug-in data table, and in the case where the plug-in record whose storage status is not stored is scanned, detecting the plug-in resource package corresponding to the plug-in record to obtain a detection result; When the detection result indicates that the plug-in resource package has passed the detection, the storage status of the plug-in record is updated to storage, and the construction of the internal plug-in corresponding to the plug-in record is completed.

2. The construction method according to claim 1, characterized in that: Before accepting the request for adding internal plugins, it also includes: Determine a plug-in data table structure, wherein the plug-in data table structure at least includes: a publisher identification field, a plug-in version field, a plug-in type field, a storage status field, and a storage time field; Based on the plug-in data table structure, the preset plug-in data table is constructed at the preset plug-in service address.

3. The construction method according to claim 1, characterized in that: Before accepting the request for adding internal plugins, it also includes: Constructing a front-end page, and embedding the front-end page into a preset development tool, wherein the preset development tool is used to generate the plug-in resource package; The resource address in the preset development tool is replaced with the preset plug-in service address where the preset plug-in data table is located.

4. The construction method according to claim 3, characterized in that: The preset development tool receives a plug-in request through the front-end page, and upon receiving the plug-in request, calls the preset plug-in data table based on the preset plug-in service address, and completes processing of the plug-in request based on the preset plug-in data table, wherein the plug-in request includes at least one of the following: the internal plug-in addition request, the internal plug-in update request, and the external plug-in synchronization request.

5. The construction method according to claim 4, characterized in that: The step of completing the processing of the plug-in request based on the preset plug-in data table includes: In the case where the plug-in request is the internal plug-in adding request, adding the plug-in information and the plug-in resource package carried by the internal plug-in adding request to the preset plug-in data table; In the case where the plug-in request is the internal plug-in update request, based on the plug-in identifier carried in the internal plug-in update request, querying the target plug-in record corresponding to the plug-in identifier from the preset plug-in data table, inserting the latest plug-in record associated with the target plug-in record into the preset plug-in data table, and uploading the latest plug-in resource package associated with the latest plug-in record; In the case that the plug-in request is the external plug-in synchronization request, based on the external plug-in synchronization information carried by the external plug-in synchronization request, the external plug-in indicated by the external plug-in identifier carried by the external plug-in synchronization request is added to the preset plug-in data table.

6. The construction method according to claim 5, characterized in that: The step of adding the external plug-in indicated by the external plug-in identifier carried by the external plug-in synchronization request to the preset plug-in data table based on the external plug-in synchronization information carried by the external plug-in synchronization request includes: Based on the external plug-in identifier, determine the external plug-in address of the external plug-in, and concatenate the external plug-in address with the external plug-in synchronization information to obtain external plug-in information; Based on the external plug-in information, pull the external plug-in from the external plug-in address to a preset folder; Based on a second preset interval, each of the external plug-ins in the preset folder is detected, and if the external plug-in passes the detection, a label indicating that the detection has passed is marked on the external plug-in; The external plug-in marked with the label indicating that the detection has passed is added to the preset plug-in data table.

7. The construction method according to claim 1, characterized in that: After detecting the plug-in resource package corresponding to the plug-in record and obtaining the detection result, the method further includes: When the detection result indicates that the plug-in resource package fails the detection, determining the detection information and calling the mail system; The detection information is sent to the publisher terminal indicated by the publisher identifier corresponding to the plug-in resource package through the mail system.

8. A device for constructing a plug-in inside an organization, characterized in that: include: A receiving unit, configured to receive an internal plug-in adding request, wherein the internal plug-in adding request carries at least: plug-in information and a plug-in resource package; A generating unit is used to generate a plug-in record based on the plug-in information, and add the plug-in record to a preset plug-in data table, wherein the plug-in record includes: storage status; A scanning unit, configured to scan the preset plug-in data table based on a first preset interval time, and when scanning the plug-in record whose storage status is not stored in the storage, detect the plug-in resource package corresponding to the plug-in record to obtain a detection result; The updating unit is used to update the storage status of the plug-in record to storage if the detection result indicates that the plug-in resource package has passed the detection, and complete the construction of the internal plug-in corresponding to the plug-in record.

9. A computer program product, characterized in that It comprises a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for constructing an internal plug-in of an institution as described in any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for constructing an internal plug-in of an institution as described in any one of claims 1 to 7.

Images