Implementation method, system and electronic device for multi-version application

Abstract

The present invention discloses a method, system and electronic device for implementing multi-version applications. The method includes: obtaining application metadata and page metadata of different versions; combining the application metadata and page metadata according to a preset rule, and performing data processing on the combined data to generate the current application version; obtaining a preset version number, and obtaining corresponding target application version data according to the preset version number; parsing the target application version data to determine target application metadata and target page metadata, so as to realize the update of the application version. By creating application version management, the present invention stores and records each application function released by the low-code platform, and can quickly return to the application function version that needs to be rolled back according to requirements, improving the security and traceability of developing applications on the low-code platform, increasing the robustness and fault tolerance of the low-code platform, and enabling the low-code platform to better serve the digital transformation of enterprises.

Description

Technical Field

[0001] The present invention relates to the technical field of application management of low-code platforms, and in particular, to a method, a system, and an electronic device for implementing multi-version applications. Background Art

[0002] The Low-Code Development Platform (LCDP) is fully known as Low-Code Development Platform in English. It usually refers to an APaaS product. By providing a visual application development environment for developers, it reduces or eliminates the need for native code writing in application development, and thus realizes a solution for conveniently constructing application programs. Low-code has evolved gradually from traditional software development methods and has the characteristics of being fast, flexible, and low-cost.

[0003] The current low-code platform generates forms based on visual drag-and-drop technology to complete the development of application functions. Users complete the development and configuration of the application function pages by dragging and configuring these components, and provide an operation to click and publish the application function through the page. However, the existing low-code platform application management lacks version management and records. When incorrect application functions are released due to operators or when business requirements are iteratively changed, it is impossible to quickly roll back to the previous application version, which greatly increases the workload of technical personnel and may also cause the enterprise's online application system to be temporarily unavailable and business stagnation, bringing immeasurable economic losses to the enterprise's operation. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a method, a system, and an electronic device for implementing multi-version applications, which solve the problem that the workload of technical personnel increases due to the lack of version management in the prior art.

[0005] According to a first aspect, an embodiment of the present invention provides a method for implementing multi-version applications, including:

[0006] Obtaining application metadata and page metadata of different versions;

[0007] Combining the application metadata and the page metadata according to a preset rule, and performing data processing on the combined data to generate the current application version;

[0008] Obtaining a preset version number, and obtaining the corresponding target application version data according to the preset version number;

[0009] Parsing the target application version data to determine target application metadata and target page metadata, so as to implement the update of the application version.

[0010] The implementation method of the multi-version application provided by the embodiments of the present invention solves the problem that the low-code platform cannot quickly roll back to the previous application version when an incorrect application is released due to human operation errors or when business requirements iterate and change. By creating application version management, each application function stored and recorded by the low-code platform can be quickly returned to the required application function version according to needs, improving the security and traceability of application development on the low-code platform, increasing the robustness and fault tolerance of the low-code platform, and enabling the low-code platform to better serve the digital transformation of enterprises.

[0011] Combined with the first aspect, in the first implementation manner of the first aspect, the obtaining of the application metadata and page metadata of different versions includes:

[0012] Obtain application identification information, page component attributes, and page layout data;

[0013] Determine application metadata according to the application identification information;

[0014] Use the page component attributes and the page layout data to determine page metadata.

[0015] Combined with the first aspect, in the second implementation manner of the first aspect, the combining of the application metadata and page metadata according to a preset rule and the data processing of the combined data to generate the current application version includes:

[0016] Obtain the page metadata corresponding to the current application metadata;

[0017] Combine the page metadata to determine version metadata;

[0018] Perform data processing on the version metadata to generate the current application version.

[0019] Combined with the second implementation manner of the first aspect, in the third implementation manner of the first aspect, the performing of data processing on the version metadata to generate the current application version includes:

[0020] Obtain the current time, perform data processing on the current time using a preset algorithm to determine the application version identifier;

[0021] Concatenate the application version identifier according to preset data bits to generate the current application version.

[0022] Combined with the first aspect, in the fourth implementation manner of the first aspect, before obtaining the target application version data corresponding to the preset version number, the method further includes:

[0023] Add the current application version to the application metadata to generate basic data, which is used to store relevant data of each version of the application;

[0024] Compress the basic data to generate different application versions, and store each application version in the storage module.

[0025] Combined with the fourth embodiment of the first aspect, in the fifth embodiment of the first aspect, the obtaining the corresponding target application version data according to the preset version number includes:

[0026] Search for the corresponding target application version data in the storage module according to the preset version number;

[0027] When the corresponding target application version data does not exist in the storage module, search for the corresponding target application version data in the database.

[0028] Combined with the first aspect, in the sixth embodiment of the first aspect, the parsing the target application version data to determine the target application metadata and the target page metadata includes:

[0029] Use a preset parsing algorithm to parse the target application version data to determine the parsing result;

[0030] Perform dynamic rendering on the parsing result to generate the target application metadata and the target page metadata.

[0031] According to the second aspect, the implementation system of the multi-version application provided by the embodiments of the present invention includes:

[0032] The first processing module is used to obtain application metadata and page metadata of different versions;

[0033] The second processing module is used to combine the application metadata and the page metadata according to a preset rule, and perform data processing on the combined data to generate the current application version;

[0034] The third processing module is used to obtain a preset version number, and obtain the corresponding target application version data according to the preset version number;

[0035] The fourth processing module is used to parse the target application version data to determine the target application metadata and the target page metadata to implement the update of the application version.

[0036] The implementation system of multi-version applications provided by the embodiments of the present invention solves the problem that the low-code platform cannot quickly roll back to the previous application version when an incorrect application is released due to human operation errors or when business requirements iterate and change, by creating application version management. Each application function released by the low-code platform is stored and recorded, and it is possible to quickly return to the application function version that needs to be rolled back according to requirements, improving the security and traceability of developing applications on the low-code platform, increasing the robustness and fault tolerance of the low-code platform, and enabling the low-code platform to better serve the digital transformation of enterprises.

[0037] According to a third aspect, an embodiment of the present invention provides an electronic device, including: a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to execute the implementation method of the multi-version application described in the first aspect or any one of the embodiments of the first aspect.

[0038] According to a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium that stores computer instructions for causing the computer to execute the implementation method of the multi-version application described in the first aspect or any one of the embodiments of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings required for use in the description of the specific embodiments or the prior art. Obviously, the following drawings are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0040] Figure 1 is a flowchart of the implementation method of the multi-version application according to an embodiment of the present invention;

[0041] Figure 2 is a flowchart of the implementation method of the multi-version application according to a preferred embodiment of the present invention;

[0042] Figure 3 is a flowchart of the implementation method of the multi-version application according to another preferred embodiment of the present invention;

[0043] Figure 4 is a flowchart of another implementation method of the multi-version application according to a preferred embodiment of the present invention;

[0044] Figure 5 is a schematic diagram of the implementation system of the multi-version application according to an embodiment of the present invention;

[0045] Figure 6 It is a schematic diagram of the hardware structure of the electronic device provided by the embodiment of the present invention. Detailed implementation manners

[0046] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0047] The full English name of the Low-Code Development Platform (LCDP) is Low-Code Development Platform. It generally refers to an APaaS product, which provides developers with a visual application development environment, reduces or eliminates the need for native code writing in application development, and thus realizes a solution for conveniently building application programs. Therefore, the low-code platform is also often referred to as the APaaS platform. Broadly speaking, the low-code concept covers all applications and services that can complete code integration and reduce code development. Narrowly speaking, the low-code concept is more inclined to meet the application needs of the enterprise business side. It is an independent development platform that can build simple applications with a small amount of code or no code through a visual interface.

[0048] Low code has evolved gradually from traditional software development methods and has the characteristics of being fast, flexible and low-cost. Traditional software development requires multiple links such as requirement collection, prototype design, general design, detailed design, code development, functional testing, deployment and installation, and monitoring and operation and maintenance to complete the system construction, which not only has a long time cycle but also high costs. Through the drag-and-drop development method of low code, users can easily build their own application systems like building blocks. At the same time, the drag-and-drop method with what you see is what you get reduces the dependence on professional developers. Business department personnel can build application systems by themselves, reducing the need to repeatedly communicate requirements with the IT department, reducing time and labor costs, and shortening the project cycle. The core of the low-code platform is that it can quickly develop multiple application systems, and after development, they can be directly released for use. In terms of subsequent system operation and maintenance, compared with traditional development and operation and maintenance methods, the low-code platform has higher flexibility, can change at any time according to the adjustment of business requirements, and has higher agility and faster iteration speed.

[0049] Current low-code platforms generate forms based on visual drag-and-drop technology to complete the development of application functions. The drag-and-drop form designer provides basic components such as common text input, password input, radio and checkbox, dropdown selection, and date selection, as well as advanced components such as file upload and rich text. Users complete the development and configuration of the application function pages by dragging and configuring these components, and perform the operation of clicking to publish the application function through the page. This simple and convenient operation method meets the rapid development of business application functions, but also brings relatively large security risks. For example, if a manager makes a mistake and publishes an application with incorrect business logic, resulting in business personnel being unable to use the system to handle business normally, and wants to quickly return to the previous version of the application function that was working properly, but cannot quickly roll back. Also, as the customer's business changes, the application functions need to be iteratively updated according to the adjustment of business requirements. The current low-code platform edits the application function page again and then republishes the new application, and the old application version will disappear. However, after a period of time, the existing business model needs to change back to the original business model. Since the information of the original application version is not retained, we can only re-edit and publish the application function according to the latest business.

[0050] Therefore, in order to avoid the lack of version management and records in the application management of the current low-code platform, when the operator's carelessness causes the wrong release of the application function or the business requirements are iteratively changed, it is impossible to quickly roll back to the previous application version, and we can only re-develop and edit the application page again to achieve the purpose of returning to the function of the previous application version. This method is not only slow, but also greatly increases our workload, and will also cause the enterprise's online application system to be temporarily unavailable and business to stagnate, bringing immeasurable economic losses to the enterprise's operation.

[0051] In this embodiment, a method for implementing multi-version applications is provided, which can be used in electronic devices such as computers, mobile phones, and tablets. Figure 1 It is a flowchart of the method for implementing multi-version applications according to an embodiment of the present invention, as Figure 1 shown. The process includes the following steps:

[0052] S11, obtain application metadata and page metadata of different versions.

[0053] In this embodiment, application metadata and page metadata of multiple different versions are obtained. Among them, the application metadata is mainly used to describe the name of the application version, the name of the application icon, and the related functions of the application, etc.; the page metadata includes information about page components, page names, and description information about page-related functions, etc. It should be noted that this embodiment is only illustrated by the above information and is not limited thereto.

[0054] S12. Combine the application metadata and page metadata according to preset rules, and perform data processing on the combined data to generate the current application version.

[0055] In this embodiment, after determining the application metadata and page metadata, they are combined in a specific manner, and the combined data is processed to determine the current application version. It should be noted that the specific combination method and data processing process will be described in detail below.

[0056] S13. Obtain the preset version number, and obtain the corresponding target application version data according to the preset version number.

[0057] Among them, obtaining the preset version number is used to record the version number that the user needs to return, and find the corresponding target application version data according to the obtained preset version number, so as to ensure that the application version that the user needs to return is determined according to this target application version data.

[0058] S14. Parse the target application version data to determine the target application metadata and target page metadata to implement the update of the application version.

[0059] After obtaining the target application version data, it is necessary to parse this data, and then determine the final target application metadata and target page metadata to achieve the effect of modifying the application version. At the same time, the log data is retained, and a notification message indicating the completion of the application version update is sent.

[0060] The implementation method of the multi-version application provided in this embodiment solves the problem that when the low-code platform releases a wrong application due to human operation errors or the business requirements iterate and change, it is impossible to quickly roll back to the previous application version by creating application version management. Each application function released by the low-code platform is stored and recorded, and it can quickly return to the application function version that needs to be rolled back according to the requirements, improving the security and traceability of the application development on the low-code platform, increasing the robustness and fault tolerance of the low-code platform, and enabling the low-code platform to better serve the digital transformation of enterprises.

[0061] In another embodiment, an implementation method of a multi-version application is also provided. Figure 2 It is another flowchart of the implementation method of the multi-version application according to the embodiment of the present invention, as Figure 2 shown, and this process includes the following steps:

[0062] S21. Obtain the application metadata and page metadata of different versions.

[0063] In this embodiment, the above step S21 further includes the following steps:

[0064] S211, obtain the application identification information, page component attributes, and page layout data.

[0065] S212, determine the application metadata according to the application identification information.

[0066] S213, use the page component attributes and page layout data to determine the page metadata.

[0067] The application metadata JSON determined by the application name, application icon name, and application description (application identification information), and the page metadata JSON determined by the page component attributes and page layout style (page component attributes and page layout data), and then through the rule of splicing multiple page metadata under a single application metadata of a specific application, combine the JSON to generate the application version metadata.

[0068] S22, combine the application metadata and page metadata according to the preset rules, and perform data processing on the combined data to generate the current application version.

[0069] For details, please refer to step S12, which will not be elaborated in this embodiment.

[0070] Specifically, before step S23, this embodiment further includes the following steps:

[0071] S203, add the current application version to the application metadata to generate the basic data, which is used to store the relevant data of each version of the application.

[0072] S213, compress the basic data to generate different application versions, and store each application version in the storage module.

[0073] The application version number plus the application metadata JSON together form the application version definition basic JSON, which stores the relevant data of this version of the entire application. Considering that the basic JSON will occupy a relatively large space in the case of a large number of application function pages, the Deflater lossless data compression algorithm is adopted. Other compression algorithms such as HPack can also be used. Compress the generated JSON data to generate the application version. The defined application version stores the most likely to be restored previous application version in the memory processor cache through the application version storage module, which is convenient for the application version processor to quickly read and increases the system response speed. The application version storage memory expiration policy can customize the default retention days through the configuration file. At the same time, considering the system reliability, all application versions are persisted to the hard disk MySQL database to facilitate the later search for each different version.

[0074] S23, obtain the preset version number, and obtain the corresponding target application version data according to the preset version number.

[0075] For details, refer to step S13, which will not be elaborated in this embodiment.

[0076] S24. Parse the target application version data to determine the target application metadata and the target page metadata, so as to implement the update of the application version.

[0077] For details, refer to step S14, which will not be elaborated in this embodiment.

[0078] The implementation method of the multi-version application provided in this embodiment solves the problem that when the low-code platform releases an incorrect application due to human operation errors or when the business requirements iterate and change, it is impossible to quickly roll back to the previous application version by creating application version management. Each application function stored and recorded by the low-code platform can be quickly returned to the application function version that needs to be rolled back according to the requirements, improving the security and traceability of developing applications on the low-code platform, increasing the robustness and fault tolerance of the low-code platform, and enabling the low-code platform to better serve the digital transformation of enterprises.

[0079] In another embodiment, an implementation method of a multi-version application is further provided. Figure 3 It is another flowchart of the implementation method of the multi-version application according to the embodiment of the present invention, as Figure 3 shown, and this process includes the following steps:

[0080] S31. Obtain the application metadata and page metadata of different versions.

[0081] For details, refer to step S11, which will not be elaborated in this embodiment.

[0082] S32. Combine the application metadata and page metadata according to a preset rule, and perform data processing on the combined data to generate the current application version.

[0083] In this embodiment, the above step S32 further includes the following steps:

[0084] S321. Obtain the page metadata corresponding to the current application metadata.

[0085] S322. Combine the page metadata to determine the version metadata.

[0086] In this embodiment, the multiple page metadata under a single application metadata is spliced and combined, and JSON is combined to generate the version metadata of the application.

[0087] S323. Perform data processing on the version metadata to generate the current application version.

[0088] Specifically, the above step S323 further includes the following steps:

[0089] (1) Obtain the current time, perform data processing on the current time using a preset algorithm, and determine the application version identifier.

[0090] (2) Concatenate the application version identifier according to the preset data bits to generate the current application version.

[0091] Among them, the 14-bit time unit in the format of year, month, day, hour, minute, and second YYYYMMDDHHMMSS of the current system time is processed with the MD5 hash algorithm into a 16-bit unique string, and concatenated to form a 30-bit application version number with a unique identifier, and the current application version is generated. It should be noted that this embodiment only exemplifies the number of digits of the current time, the algorithm of the operation, and the number of digits of the final application version. In actual applications, it can be adjusted according to actual needs, and this embodiment is not limited thereto.

[0092] S33. Obtain the preset version number, and obtain the corresponding target application version data according to the preset version number.

[0093] For details, refer to step S13, which will not be elaborated in this embodiment.

[0094] S34. Parse the target application version data to determine the target application metadata and the target page metadata to implement the update of the application version.

[0095] For details, refer to step S14, which will not be elaborated in this embodiment.

[0096] The implementation method of the multi-version application provided in this embodiment solves the problem that the low-code platform cannot quickly roll back to the previous application version when an incorrect application is released due to human operation errors or when the business requirements are iteratively changed. By creating application version management, each application function stored and recorded by the low-code platform can be quickly returned to the application function version that needs to be rolled back according to the requirements, improving the security and traceability of the application development of the low-code platform, increasing the robustness and fault tolerance of the low-code platform, and enabling the low-code platform to better serve the digital transformation of enterprises.

[0097] In another embodiment, an implementation method of a multi-version application is also provided. Figure 4 It is another flowchart of the implementation method of the multi-version application according to the embodiment of the present invention. As Figure 4 shown, this process includes the following steps:

[0098] S41. Obtain the application metadata and page metadata of different versions.

[0099] For details, refer to step S11, which will not be elaborated in this embodiment.

[0100] S42. Combine the application metadata and the page metadata according to the preset rules, and process the combined data to generate the current application version.

[0101] For details, refer to step S12, which will not be elaborated in this embodiment.

[0102] S43. Obtain the preset version number, and obtain the corresponding target application version data according to the preset version number.

[0103] In this embodiment, the above step S43 further includes the following steps:

[0104] S431. Search for the corresponding target application version data in the storage module according to the preset version number.

[0105] S432. When the corresponding target application version data does not exist in the storage module, search for the corresponding target application version data in the database.

[0106] Retrieve according to any version number that the user needs to return, that is, the preset version number, from the version library storage module. The retrieval order is to first obtain from the memory processor. If it is not the previous application version, it will not exist in the memory. Then, obtain from the MySQL database. The MySQL database will always retain all application version data. After retrieving the corresponding application version definition data, hand it over to the application version executor.

[0107] S44. Parse the target application version data to determine the target application metadata and the target page metadata, so as to update the application version.

[0108] In this embodiment, the above step S44 further includes the following steps:

[0109] S441. Use the preset parsing algorithm to parse the target application version data to determine the parsing result.

[0110] S442. Dynamically render the parsing result to generate the target application metadata and the target page metadata.

[0111] The application version executor uses the Inflater lossless data decompression algorithm to dynamically parse the target application version. Other decompression algorithms such as UPack can also be used, which need to correspond to the compression algorithm. The parsed page metadata and application metadata are synchronized to the application unit and page unit of the low-code platform, and the existing target application metadata and target page metadata are dynamically rendered to achieve the effect of modifying the application version. At the same time, the log data is retained, and a notification message indicating the completion of the application version update is sent.

[0112] The implementation method of the multi-version application provided in this embodiment solves the problem that the low-code platform cannot quickly roll back to the previous application version when an incorrect application is released due to human operation errors or when business requirements iterate and change. By creating application version management, each application function released by the low-code platform is stored and recorded, and it can quickly return to the application function version that needs to be rolled back according to requirements, improving the security and traceability of developing applications on the low-code platform, increasing the robustness and fault tolerance of the low-code platform, and enabling the low-code platform to better serve the digital transformation of enterprises.

[0113] In this embodiment, a system for implementing a multi-version application is also provided. As used hereinafter, the term "module" may be a combination of software and / or hardware that can implement a predetermined function. Although the systems described in the following embodiments are preferably implemented in software, implementations in hardware, or combinations of software and hardware are also possible and contemplated.

[0114] The present invention discloses a system for implementing a multi-version application, as Figure 5 shown, including:

[0115] The first processing module 1 is used to obtain application metadata and page metadata of different versions;

[0116] The second processing module 2 is used to combine the application metadata and page metadata according to a preset rule, and perform data processing on the combined data to generate the current application version;

[0117] The third processing module 3 is used to obtain a preset version number and obtain the corresponding target application version data according to the preset version number;

[0118] The fourth processing module 4 is used to parse the target application version data to determine the target application metadata and target page metadata to implement the update of the application version.

[0119] The system for implementing a multi-version application provided in the embodiments of the present invention solves the problem that the low-code platform cannot quickly roll back to the previous application version when an incorrect application is released due to human operation errors or when business requirements iterate and change. By creating application version management, each application function released by the low-code platform is stored and recorded, and it can quickly return to the application function version that needs to be rolled back according to requirements, improving the security and traceability of developing applications on the low-code platform, increasing the robustness and fault tolerance of the low-code platform, and enabling the low-code platform to better serve the digital transformation of enterprises.

[0120] The embodiments of the present invention also provide an electronic device. Please refer to Figure 6 , Figure 6 which is a schematic structural diagram of an electronic device provided by an alternative embodiment of the present invention. As Figure 6As shown, the electronic device may include: at least one processor 601, such as a CPU (Central Processing Unit), at least one communication interface 603, a memory 604, and at least one communication bus 602. Among them, the communication bus 602 is used to realize the connection and communication between these components. Among them, the communication interface 603 may include a display screen (Display) and a keyboard (Keyboard). Optionally, the communication interface 603 may also include a standard wired interface and a wireless interface. The memory 604 may be a high-speed RAM memory (Random Access Memory, volatile random access memory), or a non-volatile memory, such as at least one disk memory. Optionally, the memory 604 may also be at least one storage device located far from the aforementioned processor 601. Among them, the processor 601 may be combined with Figure 5 the described system, the memory 604 stores application programs, and the processor 601 calls the program code stored in the memory 604 to execute any of the above method steps.

[0121] Among them, the communication bus 602 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The communication bus 602 can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity of representation, Figure 6 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0122] Among them, the memory 604 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory may also include a non-volatile memory (English: non-volatile memory), such as a flash memory (English: flash memory), a hard disk drive (English: hard disk drive, abbreviation: HDD) or a solid-state drive (English: solid-state drive, abbreviation: SSD); the memory 604 may also include a combination of the above types of memories.

[0123] Among them, the processor 601 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.

[0124] Among them, the processor 601 may further include a hardware chip. The above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0125] Optionally, the memory 604 is further configured to store program instructions. The processor 601 may call the program instructions to implement the implementation method of the multi-version application as shown in the figure embodiments of the present application.

[0126] The embodiment of the present invention further provides a non-transitory computer storage medium. The computer storage medium stores computer-executable instructions, and the computer-executable instructions can execute the implementation method of the multi-version application in any of the above method embodiments. Among them, the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk drive (HDD), or a solid-state drive (SSD), etc.; the storage medium may also include a combination of the above-mentioned types of memories.

[0127] Although the embodiments of the present invention are described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations fall within the scope defined by the appended claims.

Claims

1. A method for implementing multi-version applications, characterized in that, it includes: Obtain application metadata and page metadata of different versions, including: Obtain application identification information, page component attributes, and page layout data; Determine application metadata according to the application identification information; Use the page component attributes and the page layout data to determine page metadata; Combine the application metadata and page metadata according to a preset rule, and perform data processing on the combined data to generate the current application version, including: Obtain each page metadata corresponding to the current application metadata; Combine each page metadata to determine version metadata; Perform data processing on the version metadata to generate the current application version, including: Obtain the current time, perform data processing on the current time using a preset algorithm to determine the application version identifier; Concatenate the application version identifier according to a preset data bit to generate the current application version; Add the current application version to the application metadata to generate basic data, which is used to store relevant data of each version of the application; compress the basic data to generate different application versions, and store each application version in a storage module; Obtain a preset version number, and obtain the corresponding target application version data according to the preset version number, including: Search for the corresponding target application version data in the storage module according to the preset version number; When the corresponding target application version data does not exist in the storage module, search for the corresponding target application version data in the database; Parse the target application version data to determine the target application metadata and target page metadata to implement the update of the application version, including: Use a preset parsing algorithm to parse the target application version data to determine the parsing result; Perform dynamic rendering on the parsing result to generate the target application metadata and target page metadata.

2. A system for implementing multi-version applications, characterized in that, it includes: A first processing module for obtaining application metadata and page metadata of different versions, including: Obtain application identification information, page component attributes, and page layout data; Determine application metadata according to the application identification information; Use the page component attributes and the page layout data to determine page metadata; A second processing module for combining the application metadata and page metadata according to a preset rule, and performing data processing on the combined data to generate the current application version, including: Obtain each page metadata corresponding to the current application metadata; Combine each page metadata to determine version metadata; A third processing module for obtaining a preset version number, and obtaining the corresponding target application version data according to the preset version number, including: Search for the corresponding target application version data in the storage module according to the preset version number; When the corresponding target application version data does not exist in the storage module, search for the corresponding target application version data in the database; The fourth processing module is used to parse the target application version data to determine the target application metadata and the target page metadata, so as to implement the update of the application version, including: Parsing the target application version data by using a preset parsing algorithm to determine a parsing result; Performing dynamic rendering on the parsing result to generate the target application metadata and the target page metadata.

3. An electronic device Characterized in that It includes: A memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions to execute the implementation method of the multi-version application according to claim 1.

4. A computer-readable storage medium Characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to cause a computer to execute the implementation method of the multi-version application according to claim 1.

Images