A client collaborative management method and device
Through the client collaborative management method, the front-end engineering framework is traversed to obtain and fill the parameter list, and a multi-level editing interface is generated, which solves the information asymmetry caused by untimely update of client products, and realizes the team members' quick grasp of product functions and Efficient maintenance.
Patent Information
- Application Number
- CN202210667439.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-06-14
- Publication Date
- 2024-11-22
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Client products are updated and modified from time to time, resulting in the panoramic view and interface documents that are not enough to allow team members to quickly and comprehensively grasp the functions of client products, especially when personnel changes and manual updates are not timely.
Provide a collaborative management method for clients, obtain parameter lists by traversing the front-end engineering framework, fill in interface annotation information and store them into the database, generate a multi-level editing interface, allowing personnel from each role to position and modify parameters through the interface to achieve unified management of parameters and updated.
It improves the upgrade and maintenance efficiency of client products, avoids the problems of information asymmetry and incomplete mastery, and ensures team members' quick understanding and accurate management of product functions.
Smart Images

Figure CN114997831B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of client management, and more particularly to a method and device for collaborative management of clients. Background Art
[0002] In a mature client (website or APP) product, the server provides customers with a wealth of customer functions or internal employee management functions. In order to facilitate the inheritance and traceability of client products, product managers will maintain the client product panoramic view, developers will maintain interface documents, and when connecting with external products, they will also provide externally released interface documents. During the testing process, testers rely more on experience to analyze the test scope.
[0003] However, considering the increasing size of client products, irregular personnel changes, and untimely manual updates, if the client product panoramic view and interface documentation are not updated in a timely manner, it will not be enough for team members (product managers, developers, testers, etc.) to quickly and comprehensively grasp the client product functions. Summary of the invention
[0004] This article is used to solve the problem in the existing technology that the client product is not updated and modified regularly, and the client product panoramic view and interface documentation are not enough for team members to quickly and comprehensively grasp the client product functions.
[0005] In order to solve the above technical problems, this article provides a client collaborative management method, including:
[0006] Traverse the client's front-end engineering framework to obtain a parameter list, which includes the following parameters in descending order: functional module, page, and interface;
[0007] Analyze the backend engineering framework to complete the annotation information, sending message body and receiving message body of each interface in the parameter list;
[0008] Store the completed parameter list into the database;
[0009] A multi-level editing interface is generated according to the database, so that each role personnel can locate the parameter editing sub-interface of the client through the multi-level editing interface and modify the corresponding parameters through the parameter editing sub-interface of the client.
[0010] As a further embodiment of this invention, a quick link is provided in the interface editing sub-interface, through which the user can jump to the code block of the interface.
[0011] As a further embodiment of this invention, the collaborative management method of the client further includes:
[0012] Receive modification requests generated by various role personnel through the multi-level editing interface, and modify the data in the database according to the modification requests.
[0013] As a further embodiment of the present invention, traversing the front-end engineering framework of the client to obtain the parameter list includes: traversing the front-end engineering framework of the client using a pull script to read variable path information from an information pull configuration file;
[0014] Access the parameter information under the variable path information;
[0015] Identify the read parameter information and the relationship between the parameters to obtain a parameter list.
[0016] As a further embodiment of this invention, before storing the completed parameter list into the database, the following is further included:
[0017] comparing the parameter list with the manually maintained panoramic view, and marking the unique parameters in the parameter list and the panoramic view;
[0018] Receive analysis results of the marked parameters, and update the parameter list and the panoramic view according to the analysis results of the marked parameters.
[0019] As a further embodiment of the present invention, the client collaborative management method further includes: re-traversing the front-end engineering framework of the client according to a preset plan to obtain the latest parameter list;
[0020] Compare the latest parameter list with the historical parameter list to obtain the newly added parameter list and the deleted parameter list;
[0021] Storing the newly added parameter list in a database;
[0022] Confirmation information is generated according to the deletion parameter list and sent to relevant maintenance personnel for confirmation, and the database is modified according to the confirmation result of the maintenance personnel.
[0023] This article also provides a client collaborative management device, including:
[0024] The front-end traversal unit is used to traverse the front-end engineering framework of the client to obtain a parameter list, which includes the following parameters in descending order: function module, page and interface;
[0025] A back-end completion unit, used to complete the annotation information, the sending message body and the receiving message body of each interface in the parameter list;
[0026] The storage unit is used to store the completed parameter list into the database;
[0027] The editing unit is used to generate a multi-level editing interface according to the database, so that each role personnel can locate the parameter editing sub-interface of the client through the multi-level editing interface and modify the corresponding parameters through the parameter editing sub-interface of the client.
[0028] This document also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in any of the aforementioned embodiments when executing the computer program.
[0029] This document also provides a computer storage medium having a computer program stored thereon. When the computer program is executed by a processor of a computer device, the method described in any of the aforementioned embodiments is executed.
[0030] This document also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the method described in any of the above embodiments is implemented.
[0031] The client collaborative management method and device provided in this article can obtain the parameter list by traversing the client's front-end engineering framework, and can comprehensively obtain the client-related functional modules, pages and interface information as well as the association relationship between the functional modules, pages and interfaces; complete the annotation information, sending message body and receiving message body of each interface in the parameter list, which can improve the readability of the interface; store the parameter list in a database, and generate a multi-level editing interface based on the database, so that each role personnel can locate the client's parameter editing sub-interface through the multi-level editing interface, and modify the corresponding parameters through the client's parameter editing sub-interface, which can provide unified management for each role personnel, avoid the problem of asymmetric and incomplete grasp of client-related information by each role personnel, and improve the efficiency of client upgrade and maintenance.
[0032] In order to make the above and other purposes, features and advantages of this article more obvious and easy to understand, the following specifically cites preferred embodiments and describes them in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] In order to more clearly illustrate the technical solutions in the embodiments of this article or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of this article. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0034] Figure 1 A first flow chart of the system management method of the client of the embodiment of this document is shown;
[0035] Figure 2A second flow chart of the system management method of the client of the embodiment of this document is shown;
[0036] Figure 3A A schematic diagram of deleting an editing sub-interface in an embodiment of this invention is shown;
[0037] Figure 3B A schematic diagram of modifying and editing the sub-interface of the embodiment of this article is shown;
[0038] Figure 3C A schematic diagram of the editing sub-interface newly added in the embodiment of this article is shown;
[0039] Figure 4 A flowchart of a process for determining a pull script according to an embodiment of the present invention is shown;
[0040] Figure 5 A third flow chart of the collaborative management method of the client of the embodiment of this document is shown;
[0041] Figure 6 A fourth flow chart of the collaborative management method of the client of the embodiment of this document is shown;
[0042] Figure 7 A device diagram showing a collaborative management device of a client in an embodiment of this invention;
[0043] Figure 8 A structural diagram of a collaborative management device of a client in an embodiment of this invention is shown.
[0044] Description of the accompanying symbols:
[0045] 701, front-end traversal unit;
[0046] 702, back-end completion unit;
[0047] 703, storage unit;
[0048] 704, editing unit;
[0049] 802. Collaborative management device;
[0050] 804, processor;
[0051] 806. Memory;
[0052] 808, driving mechanism;
[0053] 810, input / output module;
[0054] 812. Input device;
[0055] 814. Output device;
[0056] 816. Presentation equipment;
[0057] 818. Graphical user interface;
[0058] 820, network interface;
[0059] 822, communication link;
[0060] 824. Communication bus. DETAILED DESCRIPTION
[0061] The following will be combined with the drawings in the embodiments of this article to clearly and completely describe the technical solutions in the embodiments of this article. Obviously, the described embodiments are only part of the embodiments of this article, not all of the embodiments. Based on the embodiments of this article, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this article.
[0062] It should be noted that the terms "including" and "having" and any variations thereof in the specification and claims of this document and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, apparatus, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or are inherent to these processes, methods, products or equipment.
[0063] This specification provides method operation steps as described in the embodiments or flow charts, but more or fewer operation steps may be included based on routine or non-creative work. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the system or device product is executed in practice, it can be executed in the order of the method shown in the embodiments or the drawings or in parallel.
[0064] It should be noted that the collaborative management method and device of the client in this article can be used for clients in the financial field, such as cross-border matching system clients, and can also be used for clients in any field other than the financial field. The application field of the collaborative management method and device of the client in this article is not limited.
[0065] In one embodiment of the present invention, a client collaborative management method is provided to solve the problem in the prior art that client products are not updated and modified regularly, and the client product panoramic view and interface documents are not enough for client team members to quickly and comprehensively grasp the product functions. Figure 1 As shown, the system management method of the client includes:
[0066] Step 101, traverse the front-end engineering framework of the client to obtain a parameter list, which includes the following parameters in descending order: function module, page and interface.
[0067] Step 102, complete the comment information, the sending message body and the receiving message body of each interface in the parameter list.
[0068] Step 103, storing the completed parameter list into a database.
[0069] Step 104, generating a multi-level editing interface according to the database, so that each role personnel can locate the parameter editing sub-interface of the client through the multi-level editing interface, and modify the corresponding parameters through the parameter editing sub-interface of the client.
[0070] The client mentioned in this article refers to a website or APP. The client's front-end engineering framework can be implemented by React, Vue, Angular, etc.
[0071] In some implementations, the front-end engineering framework of the client traversed in step 101 refers to a stable client, such as a client with an error rate less than a predetermined value. This article uses the parameter list analyzed from the stable client as a baseline to ensure the accuracy of the data in the database.
[0072] Each functional module described in this article is used to implement a type of function, such as login, registration, etc. Functional modules, pages, and interfaces are in a downward inclusion relationship, that is, a functional module includes multiple pages, and each page may include multiple interfaces. The page corresponding to the functional module implements the function of the functional module, and the interface is the interface in the page that can interact with the server, such as various query interfaces.
[0073] The relationship between the parameters in the parameter list is shown in Table 1.
[0074] Table 1
[0075]
[0076]
[0077] Table 1 is for example only. The content of functional modules, pages and interfaces depends on the specific client.
[0078] In step 102, the annotation information, the sending message body and the receiving message body of each interface are supplemented by analyzing the client backend engineering framework. The client backend engineering framework is, for example, SpringBoot, which specifies the annotation information, the sending message body and the receiving message body of the interface.
[0079] This step can make the interface in the editing interface more readable, so that relevant personnel can clearly determine the existing annotation information, sending message body and receiving message body of the interface.
[0080] Storing the completed parameter list in the database in step 103 can facilitate querying the function module, page and interface information through the editing interface.
[0081] In step 104, the multi-level editing interface has a function of jumping between upper and lower sub-interfaces. Specifically, the modify button (modification includes deletion and adjustment) in the function module editing sub-interface can jump to the page editing sub-interface, and the modify button in the page editing sub-interface can jump to the interface editing sub-interface. The function module editing sub-interface, the page editing sub-interface, and the interface editing sub-interface are also provided with a new button to add a new function module, page, and interface.
[0082] In specific implementation, a query function is also provided in the multi-level editing interface. The function modules, pages and interfaces queried out are provided for reference by various roles, such as new members familiarizing themselves with the product, or optimizing the original functions to assist in analyzing the impact scope. Product managers and testers can query function modules to facilitate the sorting of requirements or test scopes, and developers can query interfaces to facilitate reuse or sorting of impact scopes. The query results can draw business process links by function or output a list of query results.
[0083] In this embodiment, the function module editing sub-interface and the page editing sub-interface are applicable to all roles (including business personnel, product managers, testers, and developers, etc.), and the interface editing sub-interface is used by developers. Through the implementation of steps 101 to 104, the function module, page and interface management are integrated, so that each role personnel can maintain the client product parameter information, provide intuitive and comprehensive management for each role personnel, avoid the problem of asymmetric client-related information and incomplete grasp of each role personnel, and improve the efficiency of client upgrade and maintenance.
[0084] In a further embodiment of the present invention, a quick link is also provided in the interface editing sub-interface, and the user can jump to the code block of the interface through the quick link to view or modify the interface code.
[0085] In one embodiment of this invention, Figure 2 As shown, it also includes:
[0086] Step 105, receiving modification requests generated by personnel of various roles through the multi-level editing interface, and modifying the data in the database according to the modification requests.
[0087] The modification request includes a delete modification request, a modify modification request, and a new modification request. Taking the interface editing sub-interface as an example, the user deletes, modifies, and adds the editing sub-interfaces as shown below: Figure 3A , Figure 3B and Figure 3C shown.
[0088] During the specific implementation, in order to avoid accidental deletion of information, designated personnel must review the deletion and modification requests. After the review is passed, the corresponding data in the database will be deleted.
[0089] In one embodiment of the present invention, the above step 101 traverses the front-end engineering framework of the client to obtain a parameter list, including using a pull script to traverse the front-end engineering framework of the client, reading variable path information from an information pull configuration file; accessing parameter information under the variable path information; identifying the read parameter information and the relationship between the parameters to obtain a parameter list.
[0090] In specific implementation, the pull script is run through a continuous integration tool (such as Jenkins), which calls the pull script to perform the pull operation. The information pull configuration file is compatible with the existing mainstream framework and supports customization. Different engineering frameworks can customize the public variables in the configuration file (that is, replace the public variables with the storage path of the variables in this system). In addition, custom scan items can be added in appropriate locations.
[0091] like Figure 4 As shown, the process of determining a customized configuration file includes:
[0092] Step 401, compare various plug-ins, program implementation methods and scripting languages to obtain common variables. Among them, various plug-ins, program implementation methods and scripting languages are obtained by analyzing existing mainstream frameworks.
[0093] Step 402: Generate a configuration file based on the common variables.
[0094] Step 403, receiving the variables configured by the user through the configuration file, and obtaining a customized configuration file.
[0095] In one embodiment of this invention, Figure 5 As shown, the client collaborative management method includes:
[0096] Step 501, traverse the front-end engineering framework of the client to obtain a parameter list.
[0097] Step 502, complete the annotation information, the sending message body and the receiving message body of each interface in the parameter list.
[0098] Step 503 , comparing the parameter list and the manually maintained panoramic view, and marking the unique functions in the parameter list and the panoramic view.
[0099] In detail, the panoramic view maintained by humans (product managers) includes information about the functional modules, pages, and interfaces of the client product. The panoramic view is determined by parameters accumulated in the form of mind maps or tables during the client construction process.
[0100] When this step is implemented, the parameters that belong to the parameter list but do not belong to the panoramic view are set to mark 1, and the parameters that do not belong to the parameter list but belong to the panoramic view are set to mark 2.
[0101] Step 504, receiving the analysis results of the marked parameters, and updating the parameter list or the panoramic view according to the analysis results of the marked parameters. For the parameter marked 1, it may be an obsolete parameter in the client. At this time, if the analysis result indicates that it is an obsolete parameter, the parameter is deleted from the parameter list. For the parameter corresponding to mark 2, it may be a parameter that is manually omitted or stopped from being updated. At this time, if the analysis result indicates that it is a parameter that is omitted or stopped from being updated, the parameter is added to the panoramic view.
[0102] Step 505: store the updated parameter list into the database.
[0103] Step 506, generating a multi-level editing interface according to the database, so that each role personnel can locate the parameter editing sub-interface of the client through the multi-level editing interface, and modify the corresponding parameters through the parameter editing sub-interface of the client.
[0104] In one embodiment of the present invention, it is considered that due to human factors, it is impossible to ensure that the parameter information of the client product in the database is the same as that of the running client. Figure 6 As shown, the client collaborative management method also includes:
[0105] Step 601, re-traverse the front-end engineering framework of the client according to the preset plan to obtain the latest parameter list. In this step, the preset plan is a configurable item, and the specific plan time can be manually configured, such as every 12 hours, every day, every week, etc.
[0106] Step 602, respectively compare the latest parameter list and the historical parameter list to obtain a newly added parameter list and a deleted parameter list.
[0107] Step 603: store the newly added parameter list into the database.
[0108] Step 604: Generate confirmation information based on the deletion parameter list and send it to the relevant maintenance personnel for confirmation, and modify the database according to the confirmation result of the maintenance personnel. Specifically, if the maintenance personnel confirms that the deletion is approved, the parameters in the deletion parameter list are deleted from the database. If the maintenance personnel confirms that the deletion is not approved, there is no need to process the database.
[0109] This embodiment can ensure the timeliness of the client parameter database and avoid errors caused by human factors.
[0110] Based on the same inventive concept, this article also provides a client collaborative management device, as described in the following embodiments. Since the principle of solving the problem by the client collaborative management device is similar to that of the client collaborative management method, the implementation of the client collaborative management device can refer to the client collaborative management method, and the repeated parts will not be repeated.
[0111] Specifically, Figure 7 As shown, the collaborative management device of the client includes:
[0112] The front-end traversal unit 701 is used to traverse the front-end engineering framework of the client to obtain a parameter list, which includes the following parameters in descending order: function module, page and interface.
[0113] The back-end completion unit 702 is used to complete the annotation information, the sending message body and the receiving message body of each interface in the parameter list.
[0114] The storage unit 703 is used to store the completed parameter list into the database.
[0115] The editing unit 704 is used to generate a multi-level editing interface according to the database, so that each role personnel can locate the parameter editing sub-interface of the client through the multi-level editing interface and modify the corresponding parameters through the parameter editing sub-interface of the client.
[0116] This embodiment can provide unified management for personnel of different roles, avoid problems such as asymmetric client-related information and incomplete knowledge of the personnel of different roles, and improve the efficiency of client upgrade and maintenance.
[0117] In one embodiment of the present invention, a client collaborative management device 802 is also provided, such as Figure 8 As shown, it includes: a memory 806, a processor 804, and a computer program stored in the memory 806 and executable on the processor, and the processor implements the method described in any of the aforementioned embodiments when executing the computer program. Specifically, the processor 804 is such as one or more central processing units (CPUs), and each processing unit can implement one or more hardware threads. The memory 806 can include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory can use any technology to store information. Further, any memory can provide volatile or non-volatile retention of information. Further, any memory can represent a fixed or removable component of the collaborative management device 802. In one case, when the processor 804 executes an associated instruction stored in any memory or a combination of memories, the collaborative management device 802 can perform any operation of the associated instruction. The collaborative management device 802 also includes one or more drive mechanisms 808 for interacting with any memory, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.
[0118] The collaborative management device 802 may also include an input / output module 810 (I / O) for receiving various inputs (via input device 812) and for providing various outputs (via output device 814). A specific output mechanism may include a presentation device 816 and an associated graphical user interface 818 (GUI). In other embodiments, the input / output module 810 (I / O), input device 812, and output device 814 may not be included, and the collaborative management device 802 may only be a computer device in the network. The collaborative management device 802 may also include one or more network interfaces 820 for exchanging data with other devices via one or more communication links 822. One or more communication buses 824 couple the components described above together.
[0119] The communication link 822 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 822 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.
[0120] Corresponds to Figure 1 , Figure 2 , Figures 4 to 6 The method in this article also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are executed.
[0121] The embodiment of the present invention also provides a computer readable instruction, wherein when the processor executes the instruction, the program therein causes the processor to execute the following Figure 1 , Figure 2 , Figures 4 to 6 The method shown.
[0122] It should be understood that in the various embodiments of this document, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this document.
[0123] It should also be understood that in the embodiments of this article, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0124] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this article.
[0125] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0126] In the several embodiments provided herein, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.
[0127] 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 embodiments of this article.
[0128] In addition, each functional unit in each embodiment of this invention 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 integrated unit may be implemented in the form of hardware or in the form of software functional unit.
[0129] 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 this article 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, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of this article. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.
[0130] Specific embodiments are used in this article to illustrate the principles and implementation methods of this article. The description of the above embodiments is only used to help understand the methods and core ideas of this article. At the same time, for general technicians in this field, according to the ideas of this article, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on this article.
Claims
1. A client collaborative management method, characterized in that: include: Traverse the client's front-end engineering framework to obtain a parameter list, which includes the following parameters in descending order: functional module, page, and interface; Analyze the backend engineering framework to complete the annotation information, sending message body and receiving message body of each interface in the parameter list; Store the completed parameter list into the database; Generate a multi-level editing interface according to the database, so that each role personnel can locate the parameter editing sub-interface of the client through the multi-level editing interface and modify the corresponding parameters through the parameter editing sub-interface of the client; Among them, the multi-level editing interface has the function of jumping between upper and lower sub-interfaces. The parameter editing sub-interface includes the function module editing sub-interface, the page editing sub-interface and the interface editing sub-interface. The function module editing sub-interface and the page editing sub-interface are applicable to all roles, and the interface editing sub-interface is used by developers. The Modify button in the function module editing sub-interface can jump to the page editing sub-interface, and the Modify button in the page editing sub-interface can jump to the interface editing sub-interface; the function module editing sub-interface, page editing sub-interface and interface editing sub-interface also have Add buttons to add new function modules, pages and interfaces.
2. The method according to claim 1, characterized in that A quick link is set in the interface editing sub-interface, through which you can jump to the code block of the interface.
3. The method according to claim 1, characterized in that Also includes: Receive modification requests generated by personnel of various roles through the multi-level editing interface, and modify the data in the database according to the modification requests.
4. The method according to claim 1, characterized in that Traversing the front-end engineering framework of the client to obtain the parameter list includes: using the pull script to traverse the front-end engineering framework of the client and reading variable path information from the information pull configuration file; Access the parameter information under the variable path information; Identify the read parameter information and the relationship between the parameters to obtain a parameter list.
5. The method according to claim 1, characterized in that Before storing the completed parameter list in the database, it also includes: comparing the parameter list with the manually maintained panoramic view, and marking the unique parameters in the parameter list and the panoramic view; Receive analysis results of the marked parameters, and update the parameter list and the panoramic view according to the analysis results of the marked parameters.
6. The method according to claim 1, characterized in that Also includes: Re-traverse the front-end engineering framework of the client according to the preset plan to obtain the latest parameter list; Compare the latest parameter list with the historical parameter list to obtain the newly added parameter list and the deleted parameter list; Storing the newly added parameter list in a database; Confirmation information is generated according to the deletion parameter list and sent to relevant maintenance personnel for confirmation, and the database is modified according to the confirmation result of the maintenance personnel.
7. A collaborative management device for a client, characterized in that: include: The front-end traversal unit is used to traverse the front-end engineering framework of the client to obtain a parameter list, which includes the following parameters in descending order: function module, page and interface; A back-end completion unit, used to complete the annotation information, the sending message body and the receiving message body of each interface in the parameter list; The storage unit is used to store the completed parameter list into the database; An editing unit, used to generate a multi-level editing interface according to the database, so that each role personnel can locate the parameter editing sub-interface of the client through the multi-level editing interface and modify the corresponding parameters through the parameter editing sub-interface of the client; Among them, the multi-level editing interface has the function of jumping between upper and lower sub-interfaces. The parameter editing sub-interface includes the function module editing sub-interface, the page editing sub-interface and the interface editing sub-interface. The function module editing sub-interface and the page editing sub-interface are applicable to all roles, and the interface editing sub-interface is used by developers. The Modify button in the function module editing sub-interface can jump to the page editing sub-interface, and the Modify button in the page editing sub-interface can jump to the interface editing sub-interface; the function module editing sub-interface, page editing sub-interface and interface editing sub-interface also have Add buttons to add new function modules, pages and interfaces.
8. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 6 is implemented.
9. A computer storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor of a computer device, the computer program executes the instructions of the method according to any one of claims 1 to 6.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.
Citation Information
Patent Citations
Emulated data visualized and cooperated sharing method
CN101216846A
Website management system and method
CN104268156A
Website content updating method and device, terminal and storage medium
CN111191176A
Data co-processing method, device and system
CN111553132A
Collaborative configuration service method and related components
CN113067833A
