Plug-in management method, device, equipment and medium

Abstract

This disclosure relates to a plugin management method, apparatus, device, and medium. The method is applied to a business system, which connects to a plugin system. The plugin system includes various functional plugins. The method includes: in response to a user initiating a business process in the business system, determining a target business scenario; determining a target functional plugin matching the target business scenario from the plugin system; and rendering the target functional plugin on the business system's display page. This disclosure improves the flexibility of the business system in calling functional plugins and enhances functional scalability.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a plug-in management method, apparatus, device and medium. Background Technology

[0002] In the digital age, many enterprises or organizations use business systems with multiple functions to carry out their daily business operations.

[0003] As the complexity and diversity of business operations continue to increase, the functional requirements for business systems are also constantly changing. However, current business systems are generally tightly coupled with business scenarios, resulting in problems such as fixed functions and poor functional scalability, which makes them unable to meet the rapidly changing needs of the business.

[0004] For example, some related technologies primarily involve establishing a virtual environment, generating virtual environment plugins based on virtual environment commands, and integrating these plugins into the development application so that the application can call them. Then, the application's business execution module is integrated into the virtual environment. In this approach, the virtual environment plugins are tightly coupled with the development application to integrate the business logic of the virtual and local environments. However, once the virtual environment is established, the generated plugins are fixed and cannot dynamically provide differentiated functionalities. Furthermore, the static integration of virtual environment plugins into the development application limits the flexibility of adding, updating, or removing them.

[0005] Therefore, there is an urgent need for a more flexible and scalable business system to meet the rapidly changing needs of business operations. Summary of the Invention

[0006] To address the aforementioned technical problems, this disclosure provides a plug-in management method, apparatus, device, and medium.

[0007] According to one aspect of this disclosure, a plug-in management method is provided, the method being applied to a business system, the business system connecting to a plug-in system, the plug-in system including various functional plug-ins; the method includes: In response to a user initiating a business process in the business system, the target business scenario is determined; From the plugin system, identify the target functional plugin that matches the target business scenario; The target function plugin is rendered on the display page of the business system.

[0008] According to another aspect of this disclosure, a plug-in management device is also provided. The device is applied to a business system, which connects to a plug-in system, the plug-in system including various functional plug-ins; the device includes: The scenario determination module is used to determine the target business scenario in response to a user initiating a business process in the business system. The plugin determination module is used to determine the target functional plugins that match the target business scenario from the plugin system. The plugin rendering module is used to render the target function plugin on the display page of the business system.

[0009] According to another aspect of this disclosure, an electronic device is also provided, the electronic device comprising: processor; Memory used to store the processor's executable instructions; The processor is configured to read the executable instructions from the memory and execute the instructions to implement the above-described plug-in management method.

[0010] According to another aspect of this disclosure, a computer-readable storage medium is also provided, the storage medium storing a computer program for executing the above-described plug-in management method.

[0011] The technical solution provided in this disclosure has the following advantages compared with the prior art: The plugin management method disclosed herein is applied to a business system. The business system connects to a plugin system, which includes various functional plugins. This allows the plugin system to function as an independent structure outside the business system, decoupling the business system from the functional plugins and reducing the coupling strength between the business system and the business scenario. This facilitates the expansion of the business system with richer functional plugins. Based on this, the method includes: First, in response to a user initiating a business process in the business system, determining the target business scenario; then, identifying the target functional plugins matching the target business scenario from the plugin system. Based on this, after initiating the business process, this solution, by determining the target business scenario, can identify and load only the target functional plugins required by the target business scenario, improving the flexibility of functional plugin invocation and meeting the execution requirements of the target business scenario. Then, the target functional plugins are rendered on the first business's display page, intuitively guiding the user to view and use them. Therefore, this technical solution can improve the flexibility of the business system in invoking functional plugins, enhance functional extensibility, and facilitate guiding users to quickly implement business using target functional plugins. Attached Figure Description

[0012] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0013] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a flowchart of the plug-in management method described in the embodiments of this disclosure; Figure 2 This is a schematic diagram of the structure of the business system and plug-in system described in the embodiments of this disclosure; Figure 3 This is a schematic diagram of the plug-in management device shown in the embodiments of this disclosure; Figure 4 This is a schematic diagram of the structure of the electronic device described in an embodiment of this disclosure. Detailed Implementation

[0015] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0016] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.

[0017] Current business systems generally suffer from problems such as fixed functions and poor scalability. For example, some related technologies mainly involve establishing a virtual environment, generating virtual environment plugins based on virtual environment commands, and integrating these plugins into the development application so that the application can call them; then, the application's business execution module is integrated into the virtual environment.

[0018] In this solution, the virtual environment plugin is strongly coupled with the development application to integrate the business of the virtual environment with the local environment; after the virtual environment is established, the virtual environment plugin generated based on the virtual environment is fixed and cannot dynamically provide differentiated functions; and the virtual environment plugin is statically integrated into the development application, which limits the flexibility of adding, updating or removing the virtual environment plugin.

[0019] In addition, the inventors also considered other related technologies and found that the problems with the current business system are mainly reflected in the following aspects.

[0020] (1) The business system is tightly coupled with the business scenario, and its business functions are fixed for different users, making it impossible to dynamically provide differentiated business functions for users with different roles. It is understandable that users with different roles have different actual business scenarios and require different business functions. However, since each user faces the same full range of business functions, there will be redundant business functions that the current user does not need, resulting in unnecessary redundancy. In addition, redundant business functions may also increase the user's cognitive load and learning cost.

[0021] (2) When expanding new business functions or modifying existing business functions, it is necessary to wait for the overall version update of the business system. This periodic iteration results in a long business function launch cycle. Even minor function adjustments require a complete version update process, which cannot meet the needs of rapid business changes. In particular, there may be some urgent functional requirements in actual business, but this long periodic iteration cannot respond to rapidly changing business needs.

[0022] (3) A complete business process often spans multiple departments and requires collaboration between multiple independent business systems. The business process operation is significantly discrete, and users need to switch repeatedly between different business systems, resulting in problems such as repeated logins, data entry, and complex operation paths. This discrete operation not only forces the workflow to be interrupted, leading to low work efficiency, but also easily causes problems such as data inconsistency, duplicate entry errors, and information lag.

[0023] (4) Many business systems allow implementation through plugins, but the development of different business plugins or personalized functions in the operating system lacks a unified standardized interface. In addition, these business plugins are often developed by different teams at different times, which may lead to conflicts or compatibility issues between business plugins. Furthermore, as the business system expands, the plugins become increasingly complex, making the business system bloated and difficult to maintain during expansion.

[0024] (5) Business plugins are typically loaded statically when the business system starts up, and cannot be dynamically added, updated, or removed while the business system is running. To add a new business plugin, update an existing business plugin, or move a faulty business plugin, the business system must be restarted. This not only limits the flexibility of the business system, but may also require a restart due to plugin updates or failures, affecting stability and availability. For critical business systems that need to provide uninterrupted service (such as financial transactions), any planned or unplanned restart is unacceptable.

[0025] To address at least one of the above-mentioned problems, embodiments of this disclosure provide a plug-in management method, apparatus, device, and medium. For ease of understanding, embodiments of this disclosure are described below.

[0026] Figure 1 This flowchart illustrates a plug-in management method provided in an embodiment of the present disclosure. This method is applicable to many fields, including real estate, and enables business operations through a business system. For example, in the real estate transaction business, it describes a scenario where a business system is used for customer management.

[0027] The plug-in management method provided in this embodiment can be applied to business systems, which can be installed on electronic devices such as tablets, desktop computers, laptops, and smartphones. In this embodiment, the business system accesses a plug-in system, which includes various functional plug-ins; the plug-in system provides the business system with a rich set of usable functional plug-ins. For example... Figure 1 As shown, the plugin management method may include the following steps.

[0028] S102, in response to the user initiating a business process in the business system, determines the target business scenario.

[0029] In this embodiment, the business system can be understood as a complete set of business scenarios. In the business system, when a user triggers entry into a business process, the target business scenario of the currently initiated business can be captured through the operation event bus.

[0030] S104, Identify the target functional plugin that matches the target business scenario from the plugin system.

[0031] In this embodiment, each functional plugin in the plugin system is pre-configured with various plugin attribute information during development, such as scene identifier, role identifier, and mounting location. Therefore, based on the preset scene identifiers of each functional plugin in the plugin system, a target functional plugin matching the target business scenario can be determined from the plugin system. The determined target functional plugin can thus meet the usage requirements for implementing the target business scenario.

[0032] S106 renders the target function plugin on the business system's display page.

[0033] In this embodiment, after the business system determines the target functional plugin that needs to be called in the plugin system, it can dynamically load the target functional plugin and its corresponding plugin resource package from the CDN (Content Delivery Network). The target functional plugin and its plugin resource package are then placed in a sandbox environment to ensure security. Subsequently, according to the preset mounting location of the target functional plugin, the target functional plugin is rendered on the business system's display page, mounting the target functional plugin to the designated functional area of ​​the business system.

[0034] Furthermore, when users actually use the business system, they can operate the target function plugin on the display page and perform data processing tasks based on the target function plugin for the target business scenario.

[0035] The plugin management method disclosed herein is applied to a business system. The business system connects to a plugin system, which includes various functional plugins. This plugin system, as an independent structure outside the business system, decouples the business system from the functional plugins, reducing the coupling strength between the business system and the business scenario, and facilitating the expansion of the business system with richer functional plugins. Based on this, the method includes: First, in response to a user initiating a business process in the business system, determining the target business scenario; then, identifying the target functional plugins matching the target business scenario from the plugin system. Based on this, after initiating the business process, this solution, by determining the target business scenario, can identify and load only the target functional plugins required by the target business scenario, improving the flexibility of dynamically calling functional plugins and meeting the execution requirements of the target business scenario. Then, the target functional plugins are rendered on the first business display page, intuitively guiding users to view and use them. Furthermore, the above solution only identifies and renders the target functional plugins, rather than loading and rendering all functional plugins at once, thus reducing plugin loading and rendering time and improving the performance of the business system. Therefore, this technical solution can improve the flexibility of the business system in calling functional plugins, enhance functional extensibility, and facilitate guiding users to quickly implement business using target functional plugins.

[0036] To better understand the plugin management method provided in this embodiment, the plugin system accessed by the business system is introduced here, referring to the following embodiment.

[0037] Reference Figure 2 In this embodiment, the plugin system may include the following three-layer architecture: a business interface layer, a plugin container layer, and a core service layer. Decoupling between the plugin system and the business system is achieved through a standardized SDK (Software Development Kit).

[0038] Based on the above architecture of the plug-in system, this embodiment may include: a business system accessing the plug-in system dynamically and pluggably through a business interface layer; and the business system calling functional plug-ins in the plug-in container layer through the business interface layer. When executing business logic within the business system, the functional plug-in uses services provided by the core service layer.

[0039] In this embodiment, the business interface layer is a standardized interface system used to define unified data exchange specifications, such as customer data models and construction site project metadata standards; it is also used to create a general API mesh to provide basic services such as identity authentication, data encryption, and traffic control.

[0040] In this embodiment, the core service layer is mainly used to provide some basic logic for the plug-in container layer, such as business scenario awareness and user role recognition algorithms. Some core logic applications of the plug-in container layer are integrated into the core service layer, and all functional plug-ins may use the logical capabilities of the core service layer.

[0041] The ability to perceive the aforementioned business scenarios can be achieved through an intelligent business perception engine. This engine incorporates a business process state machine and uses an operation flow analysis module to identify the business scenarios currently triggered by the user in real time. The aforementioned user role recognition algorithm is used to identify the user's role profile (such as job title, permissions, and operating habits) and recommend matching functional plugins based on this profile.

[0042] In this embodiment, the plugin container layer includes functional plugins for implementing various business functions. Specifically, functional plugins can be independently developed, compiled, and deployed using micro-frontend technology. Each functional plugin supports a hot-swappable mechanism, which allows functional plugins to be flexibly integrated into the business system.

[0043] In this embodiment, a plugin container layer can be deployed in the plugin system kernel. The plugin container layer integrates the WebComponent framework. Based on this framework, micro-frontend technology is used, and different components in the component framework are used to encapsulate various functional plugins corresponding to different business scenarios.

[0044] In a pre-developed plugin registry, plugin attribute information for functional plugins is defined through metadata description files. Plugin attribute information includes, but is not limited to: the business systems the functional plugin can access, the plugin version, scenario identifier, and role identifier; the scenario identifier indicates the business scenarios the functional plugin supports; and the role identifier indicates the user roles to which the functional plugin is applicable.

[0045] Taking the real estate sector as an example, functional plugins developed according to this embodiment include functional plugins for sales business scenarios and functional plugins for delivery business scenarios.

[0046] Among them, the functional plugins corresponding to the sales business scenario may include: a customer management plugin, which integrates an OCR recognition interface to achieve automatic document backfilling; a contract generator plugin, which calls an intelligent template engine to generate standard contract documents; and a data dashboard plugin, which connects to a BI system to display the customer conversion funnel in real time.

[0047] Specific functional plugins for delivery business scenarios may include: a construction site 3D modeling plugin for integrating a lightweight BIM (Building Information Modeling) engine; a process acceptance plugin for embedding AR remote acceptance functionality; and a materials management plugin for connecting to IoT devices to achieve automatic inventory counting.

[0048] This embodiment may also include: establishing a dependency graph of functional plugins that matches the business processes of the business system, based on the complete business processes implemented by the business system.

[0049] In one possible implementation, one or more functional plugins can be configured for each business scenario in the complete business process implemented by the business system, and at least one component that the functional plugin depends on can also be configured. A second dependency relationship is established between the functional plugin and its dependent components.

[0050] Furthermore, each business scenario, as a node in the complete business process, has dependencies on other business scenarios. For example, the customer management scenario depends on the customer profiling scenario; the data analysis scenario depends on the database scenario. Based on this, according to the dependencies between business scenarios, the first dependency relationship is established for the corresponding functional plugins. Accordingly, the first dependency relationship is as follows: the customer management plugin depends on the customer profiling plugin, and the data analysis plugin depends on the database plugin.

[0051] Then, a directed graph can be used to record the first dependency relationships between different functional plugins and the second dependency relationships between functional plugins and components, forming a dependency graph.

[0052] This embodiment establishes a dependency graph for functional plugins based on the complete business process implemented by the business system, matching the business process. This dependency graph clearly maps the business process, reducing the maintenance costs of functional plugins and components. Functional plugins and components are loaded in the order of the business flow, avoiding functional gaps or logical conflicts. Furthermore, the dependency graph is easy to modify; by adjusting the dependencies recorded in the graph, it can flexibly adapt to different business scenarios and processes.

[0053] Based on the plug-in system provided in the above embodiments, the business system connects to the plug-in system in a dynamic and pluggable manner through the business interface layer; during operation, the business system calls functional plug-ins in the plug-in container layer through the business interface layer. The following embodiments provide a plug-in management method for the operation process of the business system, as shown below.

[0054] In one embodiment, in step S102, in response to the user initiating a business process in the business system, the plug-in management method may first include: In response to a user's login action in the business system, the system identifies the original functional plugin that matches the user from the plugin system.

[0055] In this embodiment, the user role can be determined in response to the user's login operation in the business system; and the original functional plugin that matches the user role can be determined according to the role identifier pre-configured for each functional plugin.

[0056] Specifically, the plugin attributes include role identifiers, which allow plugins to support different user lists configured based on user roles. Therefore, when a user logs into the business system, the initial plugins available to that user can be initialized according to their role. Different plugins are available to different users, dynamically providing differentiated plugins for users with different roles, avoiding providing unnecessary plugins.

[0057] Next, in response to the user initiating a business process in the business system, the target business scenario is determined. Accordingly, the target functional plugins matching the target business scenario are determined from the plugin system. This may include: determining the target functional plugins matching the target business scenario from the original functional plugins.

[0058] In one embodiment, determining the target functional plugin that matches the target business scenario from the plugin system may include: Step 1: Based on the scenario identifiers pre-configured for each functional plugin in the plugin system, determine the first functional plugin that matches the target business scenario from the plugin system.

[0059] Specifically, based on the scenario identifiers pre-configured for each functional plugin, the first functional plugin that matches the target business scenario is determined from the original functional plugins available to the user.

[0060] When registering plugin attribute information, functional plugins register a scenario identifier to represent the corresponding business scenario. The business system can run a plugin loader to dynamically determine and load the first functional plugin that matches the target business scenario from multiple original functional plugins based on the scenario identifier. By progressively loading the first functional plugin according to the target business scenario, on-demand dynamic plugin loading can be achieved, reducing redundant loading and improving runtime performance.

[0061] Step 2: Based on the preset dependency graph, determine the second functional plugins that the first functional plugin depends on from the plugin system; wherein, the dependency graph includes: the first dependency relationships between different functional plugins.

[0062] In this embodiment, the business system can pass the dependency graph to the business interface layer, which then passes the dependency graph to the plugin container layer. The plugin container layer then uses the dependency graph to import functional plugins and load the components that the functional plugins depend on on demand.

[0063] First, this embodiment determines the second functional plugin that the first functional plugin depends on based on the first dependency relationship between different functional plugins. For example, if functional plugin A depends on functional plugins B and C, then after obtaining functional plugin A, functional plugins B and C are obtained simultaneously according to the first dependency relationship.

[0064] In addition, based on the primary dependencies between different functional plugins, the business scenario of the user's next operation can be predicted, and functional plugin D, which depends on functional plugin A, can be preloaded.

[0065] Secondly, this embodiment also includes: determining multiple components that the first functional plugin depends on based on the second dependency relationship between the functional plugin and the component; and determining a first component that matches the target business scenario from among the multiple components that the first functional plugin depends on.

[0066] Functional plugins form a top-level structure, with components as their sub-structures. Multiple components together constitute a functional plugin. During use, a functional plugin may only require a subset of its components. As an example, the payment service plugin depends on the following components: payment button (A1), risk control verification (A2), and discount calculation (A3). In a typical payment scenario, only the payment button (A1) and risk control verification (A2) components need to be loaded; in a promotional payment scenario, only the payment button (A1) and discount calculation (A3) components need to be loaded.

[0067] Therefore, the functional plugins and their dependent components are dynamically changing, and the first matching component can be loaded on demand according to the target business scenario.

[0068] Based on the dependency graph, this embodiment determines the second functional component that the first functional plugin depends on, and also determines the component that the first functional plugin depends on, and loads the first component that matches the target business scenario as needed. This can better meet the usage requirements of the target business scenario and improve business execution efficiency.

[0069] Step 3: Determine the target functional plugin based on the first functional plugin and the second functional plugin.

[0070] In practical applications, there may be multiple different functional plugins corresponding to the same business scenario and implementing the same function. Alternatively, different loading methods (such as scripts or data packages) may be used to load overlapping functional plugins multiple times.

[0071] To address this issue, this embodiment allows for the selection of the optimal functional plugin for both the first and second functional plugins. Therefore, determining the target functional plugin based on the first and second functional plugins can include: The first and second functional plugins are filtered according to preset filtering parameters to obtain the third and fourth functional plugins respectively; wherein the filtering parameters include at least one of the following: plugin resource consumption, plugin version, number of plugin calls in the historical time period and plugin runtime. The third and fourth function plugins are identified as target function plugins.

[0072] This embodiment filters the first and second functional plugins according to the filtering parameters, which can filter out the target functional plugins with better performance and improve the execution efficiency of the business system in terms of performance.

[0073] After determining the target function plugin according to the above embodiments, the target function plugin is rendered on the display page of the first business; so that when the actual application business system is used, the target function plugin can be operated on the display page to perform data processing on the target business scenario based on the target function plugin.

[0074] In addition, the plug-in management method provided in this embodiment may also include: using a differential synchronization algorithm to synchronize the execution status of functional plug-ins in the business system to the plug-in system, thereby realizing the state synchronization of functional plug-ins; the execution status of functional plug-ins includes, for example, being occupied or unloaded.

[0075] It may also include: establishing an operation log traceability system to support plugin version rollback.

[0076] It may also include: establishing a conflict detection module and applying OT algorithms to resolve data concurrency conflicts.

[0077] In addition, for personalized or newly added services in the business system, if the existing functional plugins in the plugin system do not meet the actual operational requirements of the above services, this embodiment can provide the following plugin management method.

[0078] Submit a third functional plugin to the plugin system so that the plugin system can load the third functional plugin; wherein, the third functional plugin is generated by assembling functional plugins and / or components for the target business based on the visual configuration system; the target business is the business that existing functional plugins cannot meet the actual operational needs.

[0079] Once the plugin system returns the loaded third-party plugin, the loaded third-party plugin is rendered on the target business's display page.

[0080] In addition to the business system and the plugin system, this embodiment may also include a visual configuration system. The visual configuration system is configured with a drag-and-drop plugin orchestration interface and a plugin marketplace module. The plugin orchestration interface supports the custom assembly of functional plugins based on business processes; the plugin marketplace module integrates version management, access control, and usage analysis functions for functional plugins.

[0081] A visual configuration system can be a standalone system, facilitating reuse across multiple business systems. Alternatively, it can be part of a plug-in system, ensuring consistency among functional plug-ins. Or, it can be part of a business system, serving only the current business system, with highly customized configuration logic.

[0082] The visual configuration system allows you to configure the first dependencies between functional plugins and the second dependencies between functional plugins and components. The visual configuration system allows for the custom assembly of business processes when existing functional plugins do not meet actual operational needs. This includes custom assembly of functional plugins and custom assembly of components at the next level of functional plugins, thereby creating a third functional plugin.

[0083] The third-party function plugin is submitted to the plugin system for loading. Specifically, the plugin system's loading process includes, but is not limited to, the following: Perform integrity checks on the digital signatures, file structures, and dependencies of third-party plugins.

[0084] Prepare the environment for the third-function plugin, such as creating an independent sandbox environment and allocating resource quotas (such as CPU / memory limits).

[0085] Configuration for dynamically loading third-party plugins includes: registering custom WebComponent elements, establishing dependencies, and executing initialization scripts.

[0086] After the plugin system completes the loading process of the third-party function plugin, it returns the loaded third-party function plugin to the business system and then renders the loaded third-party function plugin on the target business's display page.

[0087] Corresponding to the plug-in management method provided in the foregoing embodiments, refer to Figure 3 As shown in the figure, this disclosure provides a plug-in management device. This plug-in management device is applied to a business system, which accesses a plug-in system, which includes various functional plug-ins; the device includes: The scenario determination module 310 is used to determine the target business scenario in response to the user starting a business process in the business system. The plugin determination module 320 is used to determine the target functional plugin that matches the target business scenario from the plugin system. The plugin rendering module 330 is used to render the target function plugin on the display page of the business system.

[0088] The device provided in this embodiment has the same implementation principle and technical effect as the aforementioned method embodiment. For the sake of brevity, any parts not mentioned in the device embodiment can be referred to the corresponding content in the aforementioned method embodiment.

[0089] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Figure 4 As shown, the electronic device 400 includes one or more processors 401 and memory 402.

[0090] The processor 401 may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 400 to perform desired functions.

[0091] The memory 402 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 401 may execute the program instructions to implement the plug-in management method of the embodiments of this disclosure described above and / or other desired functions. Various contents such as input signals, signal components, and noise components may also be stored in the computer-readable storage medium.

[0092] In one example, the electronic device 400 may also include an input device 403 and an output device 404, which are interconnected via a bus system and / or other forms of connection mechanism (not shown).

[0093] In addition, the input device 403 may also include, for example, a keyboard, a mouse, etc.

[0094] The output device 404 can output various information to the outside, including determined distance information, direction information, etc. The output device 404 may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

[0095] Of course, for the sake of simplicity, Figure 4Only some of the components of the electronic device 400 relevant to this disclosure are shown, omitting components such as buses, input / output interfaces, etc. In addition, the electronic device 400 may include any other suitable components depending on the specific application.

[0096] Furthermore, this embodiment also provides a computer-readable storage medium storing a computer program for executing the above-described plug-in management method.

[0097] The present disclosure provides a plug-in management method, apparatus, electronic device, and medium computer program product, including a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods described in the preceding method embodiments. For specific implementation details, please refer to the method embodiments, which will not be repeated here.

[0098] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0099] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A plug-in management method, characterized in that, The method is applied to a business system, which is connected to a plugin system, and the plugin system includes various functional plugins; the method includes: In response to a user initiating a business process in the business system, the target business scenario is determined; From the plugin system, identify the target functional plugin that matches the target business scenario; The target function plugin is rendered on the display page of the business system.

2. The method according to claim 1, characterized in that, Before the user initiates a business process in the business system in response to the user, the method further includes: In response to a user's login operation in the business system, the original functional plugin matching the user is determined from the plugin system; The step of determining the target functional plugin that matches the target business scenario from the plugin system includes: Identify the target functional plugin that matches the target business scenario from the original functional plugins.

3. The method according to claim 1, characterized in that, The step of determining the target functional plugin that matches the target business scenario from the plugin system includes: Based on the scenario identifiers pre-configured for each functional plugin in the plugin system, a first functional plugin matching the target business scenario is determined from the plugin system. Based on a preset dependency graph, a second functional plugin that the first functional plugin depends on is determined from the plugin system; wherein, the dependency graph includes: a first dependency relationship between different functional plugins; The target functional plugin is determined based on the first functional plugin and the second functional plugin.

4. The method according to claim 3, characterized in that, The dependency graph includes: a second dependency relationship between functional plugins and components; after determining the first functional plugin matching the target business scenario from the plugin system, the method further includes: Based on the second dependency relationship between the functional plugin and the component, determine the multiple components that the first functional plugin depends on; From the multiple components that the first functional plugin depends on, determine the first component that matches the target business scenario.

5. The method according to claim 3, characterized in that, The step of determining the target functional plugin based on the first functional plugin and the second functional plugin includes: The first functional plugin and the second functional plugin are filtered according to preset filtering parameters to obtain the third functional plugin and the fourth functional plugin respectively; wherein, the filtering parameters include at least one of the following: plugin resource consumption, plugin version, number of plugin calls in a historical time period and plugin runtime; The third and fourth functional plugins are identified as target functional plugins.

6. The method according to claim 1, characterized in that, The method further includes: A third functional plugin is submitted to the plugin system so that the plugin system can load the third functional plugin; wherein, the third functional plugin is generated based on the assembly of functional plugins and / or components of the target business by the visual configuration system; When the plugin system returns the loaded third function plugin, the loaded third function plugin is rendered on the display page of the target business.

7. The method according to claim 1, characterized in that, The plugin system includes at least: a business interface layer and a plugin container layer; the method further includes: The business system is connected to the plug-in system in a dynamic and pluggable manner through the business interface layer; The business system calls the functional plugins in the plugin container layer through the business interface layer.

8. A plug-in management device, characterized in that, The device is applied to a business system, which is connected to a plug-in system, which includes various functional plug-ins; the device includes: The scenario determination module is used to determine the target business scenario in response to a user initiating a business process in the business system. The plugin determination module is used to determine the target functional plugins that match the target business scenario from the plugin system. The plugin rendering module is used to render the target function plugin on the display page of the business system.

9. An electronic device, characterized in that, The electronic device includes: processor; Memory used to store the processor's executable instructions; The processor is configured to read the executable instructions from the memory and execute the instructions to implement the method described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a terminal device, cause the terminal device to perform the method as described in any one of claims 1-7.

Images