A low-code platform form migration method, device, equipment and storage medium

Abstract

The application discloses a low-code platform form migration method and device, equipment and storage medium, and relates to the technical field of low-code platforms. The method comprises the following steps: obtaining a configuration field of a form model to be migrated; the configuration field is a configuration field after a target field is annotated in advance according to an annotation rule; when file export is performed, a to-be-processed symbol is determined from the configuration field according to the annotation, the to-be-processed symbol is replaced with an occupant capable of representing a path position, then a symbol mapping table is created based on the to-be-processed symbol and the occupant, and a configuration file is exported; when file import is performed, a new symbol corresponding to the to-be-processed symbol is generated according to the annotation corresponding to the to-be-processed symbol, and the new symbol is used to replace the occupant corresponding to the to-be-processed symbol in the configuration file according to the mapping table until all the occupants in the configuration file are replaced. The method realizes the rapid migration of forms in a low-code platform.

Description

Technical Field

[0001] This invention relates to the field of low-code platform technology, and in particular to a low-code platform form migration method, apparatus, device, and storage medium. Background Technology

[0002] Low-code platforms have rapidly developed into a fast enterprise application solution in recent years, characterized by rapid delivery and high customization. They are typically provided to users as SaaS (Software-as-a-Service) or PaaS (Platform-as-a-Service). However, designing a fully functional application requires a high degree of familiarity with the low-code platform and a thorough understanding of business requirements, which many users lack. Therefore, it is often necessary to migrate existing, designed application forms. Forms are a logical concept in low-code platforms, serving as the carrier of business data and the foundation of data management. Their main functions include a UI for direct user interaction, a middleware service processing layer, and persistent data tables. From a UI perspective, this mainly includes layout components and functional components. An application is a service entity organically combined from multiple forms. The data between forms typically has significant interoperability, working together to complete the designed functionality. Migration refers to moving an existing entity (i.e., an application or form) from one environment to another, or creating a copy of the entity within the same environment, on an application or form basis. Migration generally has two modes: overwrite and copy-install. Overwrite updates and upgrades an existing entity, while copy-install creates a new entity, and the original entity and the migrated entity do not interfere with each other.

[0003] Platforms typically create application or form templates from common business types, frequently used functional components, and their own platform's key features. These pre-built templates are then uploaded, allowing users to quickly install a complete application – one application migration scenario. Another scenario involves users exporting their own applications or forms as templates. These templates are usually serialized application or form configuration data, which is then imported into the system for rapid reuse or design restoration.

[0004] The current approach involves serializing and exporting an existing application or form model into a configuration file, modifying the configuration file through string replacement, and then importing the configuration file into the system. This configuration file contains numerous symbols, such as data IDs, form component keys, table names, field names, table creation SQL statements, application initialization data, form-specific report configurations, and their mapping relationships. Migration issues are not significant in the overwrite mode; however, in the copy-installation migration mode, to ensure that the old and new applications do not interfere with each other, different symbols in the configuration file must be processed differently, such as randomly generating new symbols, leaving them unchanged, or modifying symbol prefixes. The current approach involves deserializing the configuration file during installation, extracting the symbols to be replaced using hard-coded code, generating new symbols using rules, saving the mapping relationship between the old and new symbols, performing a brute-force search and replacement on the entire configuration file, and finally importing the processed configuration file into the system to generate a new application or form. However, this method is logically complex and prone to errors, making troubleshooting and modification very difficult, and the brute-force symbol replacement is time-consuming, reducing migration efficiency. Summary of the Invention

[0005] In view of this, the purpose of this invention is to provide a method, apparatus, device, and medium for form migration on a low-code platform, which can improve migration efficiency. The specific solution is as follows:

[0006] Firstly, this application discloses a low-code platform form migration method, including:

[0007] Obtain the configuration fields of the form model to be migrated; the configuration fields are the target fields that have been annotated in advance according to the annotation rules.

[0008] When exporting the file, the symbol to be processed is determined from the configuration field according to the annotation, and the symbol to be processed is replaced with a occupant character that can represent the path location. Then, a symbol mapping table is created based on the symbol to be processed and the occupant character, and the configuration file is exported.

[0009] When importing a file, a new symbol corresponding to the symbol to be processed is generated based on the annotation corresponding to the symbol to be processed, and the new symbol is used to replace the corresponding occupant in the configuration file according to the mapping table, until all occupants in the configuration file have been replaced.

[0010] Optionally, determining the symbol to be processed from the configuration field based on the annotation includes:

[0011] Iterate through each field of the configuration fields and determine whether the current field contains a symbolic annotation;

[0012] If a symbol type annotation exists, the symbol in the current field will be used as the symbol to be processed.

[0013] Optionally, the step of replacing the symbol to be processed with an occupant that can represent the path location, and then creating a symbol mapping table based on the symbol to be processed and the occupant, includes:

[0014] Determine the symbol processing behavior in the annotation corresponding to the field containing the symbol to be processed;

[0015] The symbol to be processed is replaced with an occupant that can represent the path location according to the symbol processing behavior, and a symbol mapping table is created based on the symbol to be processed and the occupant.

[0016] Optionally, the step of replacing the symbol to be processed with a occupant that can represent the path location according to the symbol processing behavior, and creating a symbol mapping table based on the symbol to be processed and the occupant, includes:

[0017] If the symbol processing behavior is a symbol generation behavior, then the symbol to be processed is directly replaced with an occupant that can represent the path location, and a symbol mapping table is created based on the symbol to be processed and the occupant.

[0018] If the symbol processing behavior is a symbol container or symbol reference behavior, a callback function is created so that after all the symbols to be processed in the configuration field have been traversed, the symbols to be processed are replaced with the corresponding occupants according to the symbol mapping table.

[0019] Optionally, generating a new symbol corresponding to the symbol to be processed based on the annotation corresponding to the symbol to be processed includes:

[0020] The method for generating new symbols is determined based on the symbol type in the annotation;

[0021] Based on the symbol to be processed, the method for generating the new symbol, and the symbol scope in the annotation, a new symbol corresponding to the symbol to be processed is generated.

[0022] Optionally, after creating the symbol mapping table based on the symbol to be processed and the occupant, the method further includes:

[0023] Based on the length of each symbol to be processed in the mapping table, the mapping table is sorted in descending order of the length of the symbols to be processed;

[0024] Accordingly, generating a new symbol corresponding to the symbol to be processed based on the annotation corresponding to the symbol to be processed includes:

[0025] According to the order of the symbols to be processed in the mapping table, a new symbol corresponding to each symbol to be processed is generated based on the annotation corresponding to each symbol to be processed.

[0026] Optionally, creating a symbol mapping table based on the symbol to be processed and the occupant includes:

[0027] Based on the symbol to be processed and the occupant, a positive symbol mapping table is generated from the symbol to be processed to the occupant;

[0028] After generating the new symbol corresponding to the symbol to be processed based on the annotation corresponding to the symbol to be processed, the process further includes:

[0029] Based on the new symbol and the occupant, a reverse symbol mapping table is generated from the forward symbol mapping table, pointing from the occupant to the new symbol, so that the new symbol can be used to replace the corresponding occupant in the configuration file by querying the reverse symbol mapping table.

[0030] Secondly, this application discloses a low-code platform form migration device, comprising:

[0031] The configuration field acquisition module is used to acquire the configuration fields of the form model; the configuration fields are the target fields that have been annotated in advance according to the annotation rules.

[0032] The pending symbol replacement module is used to determine the pending symbols from the configuration fields according to the annotations after the file is exported, replace the pending symbols with occupants that can represent the path location, create a symbol mapping table based on the pending symbols and the occupants, and export the configuration file.

[0033] The occupant replacement module is used to generate a new symbol corresponding to the symbol to be processed based on the annotation corresponding to the symbol to be processed after the file is imported, and replace the corresponding occupant in the configuration file with the new symbol according to the mapping table, until all occupants in the configuration file have been replaced.

[0034] Thirdly, this application discloses an electronic device, including:

[0035] Memory, used to store computer programs;

[0036] A processor is used to execute the computer program to implement the aforementioned low-code platform form migration method.

[0037] Fourthly, this application discloses a computer-readable storage medium for storing a computer program; wherein the computer program, when executed by a processor, implements the aforementioned low-code platform form migration method.

[0038] In this application, the configuration fields of the form model to be migrated are obtained. These configuration fields are pre-annotated according to annotation rules for the target fields. During file export, the symbols to be processed are determined from the configuration fields based on the annotations, and these symbols are replaced with placeholders that represent path locations. Then, a symbol mapping table is created based on the symbols to be processed and the placeholders, and the configuration file is exported. During file import, a new symbol corresponding to the symbol to be processed is generated based on the annotations corresponding to the symbol to be processed. The new symbol is then used to replace the corresponding placeholder in the configuration file according to the mapping table, until all placeholders in the configuration file have been replaced. Therefore, by adding annotations to the configuration fields of the form model, determining the symbols to be processed based on the annotations, and then replacing the symbols to be processed with placeholders that represent path information, the new symbols are used to replace the corresponding placeholders after generating the new symbols corresponding to the symbols to be processed. This replaces brute-force string searches with placeholders and table lookups, enabling rapid installation of applications and forms on low-code platforms and improving migration speed. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0040] Figure 1 A flowchart of a low-code platform form migration method provided in this application;

[0041] Figure 2 A flowchart illustrating a specific low-code platform form export method provided in this application;

[0042] Figure 3 A flowchart illustrating a specific low-code platform form import method provided in this application;

[0043] Figure 4 A schematic diagram of a low-code platform form migration device is provided for this application;

[0044] Figure 5 This application provides a structural diagram of an electronic device. Detailed Implementation

[0045] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0046] In existing technologies, the configuration file is deserialized during installation, then the symbols to be replaced are extracted using hard code, new symbols are generated using rules, the mapping relationship between the old and new symbols is saved, and then a brute-force search and replacement is performed on the entire configuration file. Finally, the processed configuration file is imported into the system to generate a new application or form. However, this method has complex logic, is prone to errors, and is very difficult to troubleshoot or modify. Furthermore, the brute-force replacement of symbols is time-consuming, reducing migration efficiency. To overcome the above technical problems, this application proposes a low-code platform form migration method that can improve migration efficiency.

[0047] This application discloses a low-code platform form migration method. See also Figure 1 As shown, the method may include the following steps:

[0048] Step S11: Obtain the configuration fields of the form model to be migrated; the configuration fields are the configuration fields after adding annotations to the target fields in advance according to the annotation rules.

[0049] In this embodiment, the configuration fields of the form model to be migrated are first obtained, i.e., the form's configuration information. These configuration fields are annotated fields, specifically, they can be target fields in the configuration file that have been annotated in advance according to annotation rules. These annotation rules are based on symbol type, symbol processing behavior, and symbol scope. Furthermore, the migration and application of forms are similar; in this embodiment, the form model to be migrated can also be the application model to be migrated.

[0050] It is understandable that configuration fields contain a large number of symbols, such as data IDs, form component keys, table names, and field names. In this embodiment, annotations are added to each field based on its content. Annotations for configuring symbol types, based on the symbol's function, include, but are not limited to, application IDs, form IDs, field names, and table names. Annotations for configuring symbol processing behavior, based on the symbol's behavior in the configuration field, include, but are not limited to, symbol generation, symbol reference, and symbol container. Furthermore, corresponding symbol scopes are added based on the symbol's scope. Thus, custom annotations are created to mark symbol types, symbol processing behaviors, and symbol scopes on the configuration fields of the corresponding form model, facilitating the rapid identification of symbols in the configuration fields.

[0051] Step S12: When exporting the file, determine the symbol to be processed from the configuration field according to the annotation, replace the symbol to be processed with a occupant that can represent the path location, then create a symbol mapping table based on the symbol to be processed and the occupant, and export the configuration file.

[0052] In this embodiment, the migration is divided into two stages: export and import. In the export stage, reflection technology is used to process the configuration fields of the form model differently according to different annotations. All the symbols to be replaced are first replaced with occupants that can represent the path location, and a symbol mapping table is established. Then, the serialized configuration file is exported. The specific content of the occupants is not limited, as long as they can represent the path location and are unique.

[0053] In this embodiment, determining the symbol to be processed from the configuration field based on the annotation may include: traversing each field of the configuration field and determining whether the current field contains an annotation of the symbol type; if an annotation of the symbol type exists, then the symbol in the current field is taken as the symbol to be processed. That is, the target field containing the symbol type annotation is selected from the configuration fields, and then the symbol in that field is taken as the symbol to be processed.

[0054] In this embodiment, replacing the symbol to be processed with an occupant character that can represent the path location, and then creating a symbol mapping table based on the symbol to be processed and the occupant character, may include: determining the symbol processing behavior in the annotation corresponding to the field where the symbol to be processed is located; replacing the symbol to be processed with an occupant character that can represent the path location according to the symbol processing behavior; and creating a symbol mapping table based on the symbol to be processed and the occupant character. That is, since the symbol processing behaviors corresponding to the symbols to be processed are different, the specific operations when performing symbol replacement also differ. Therefore, the symbol to be processed is replaced with an occupant character that can represent the path location specifically according to the corresponding symbol processing behavior. The symbol mapping table, in addition to including the correspondence between the symbol to be processed and the occupant character, may also include information such as the field value corresponding to the symbol to be processed, the symbol type, the symbol processing behavior, and the symbol scope, so that the symbol mapping table can be directly queried when generating a new symbol.

[0055] In this embodiment, the step of replacing the symbol to be processed with a occupant character that can represent the path location according to the symbol processing behavior, and creating a symbol mapping table based on the symbol to be processed and the occupant character, may include: if the symbol processing behavior is a symbol generation behavior, then directly replacing the symbol to be processed with a occupant character that can represent the path location, and creating a symbol mapping table based on the symbol to be processed and the occupant character; if the symbol processing behavior is a symbol container or symbol reference behavior, then creating a callback function so that after traversing all the symbols to be processed in the configuration field, the symbol to be processed is replaced with the corresponding occupant character according to the symbol mapping table. It can be understood that symbol generation behavior refers to generating a symbol mapping table based on field values. Symbol reference and symbol container refer to the fact that this field may be a string or object that references a symbol; it does not generate a symbol, therefore replacement processing is required after the symbol mapping table is established.

[0056] For example Figure 2 As shown, after obtaining the configuration fields marked with annotations, all fields are traversed. When the current field is encountered and a corresponding annotation exists, the symbol processing behavior is further used to determine whether a symbol is generated. If it is a symbol generation behavior, the symbol to be processed is directly replaced with a placeholder character that can represent the path location, and a symbol mapping table is created based on the symbol to be processed and the placeholder character, thus saving the mapping relationship between the symbol to be processed and the placeholder character. If the symbol processing behavior is a symbol container or symbol reference behavior, it can be determined that the current field only references characters. To ensure the consistency of the replacement, all fields referencing characters are uniformly replaced according to the generated symbol mapping table after the actual symbol generation field has undergone symbol replacement. Specifically, delayed replacement is performed by creating callback functions. That is, when a field marked with symbol generation behavior is encountered, it is added to the symbol mapping table and the symbol to be processed in this field is replaced with a path placeholder character. When a field marked with a symbol container is encountered, a callback function is created and added to the delayed callback set. The function's role is to search the entire forward mapping table and replace the symbol with a path placeholder character. These callback functions are triggered uniformly after the entire symbol mapping table is established, with the aim of ensuring that all symbols referenced in this field are correctly replaced.

[0057] Step S13: When importing the file, a new symbol corresponding to the symbol to be processed is generated according to the annotation corresponding to the symbol to be processed, and the new symbol is used to replace the corresponding occupant in the configuration file according to the mapping table, until all occupants in the configuration file are replaced.

[0058] In this embodiment, since the exported file is usually serialized data, when the file is imported, i.e. during installation, deserialization is performed first. Then, a new symbol corresponding to the symbol to be processed is generated according to the annotation corresponding to the symbol to be processed. Then, the occupant corresponding to the new symbol is determined by querying the mapping table. The occupant is determined by traversing the deserialized data and the occupant is replaced with the corresponding new symbol, so as to achieve accurate and fast symbol replacement.

[0059] Therefore, symbols in application and form configuration data are categorized by type and scope. Combined with the language's annotation reflection technology, the original process of extracting symbols, establishing mappings, generating symbols, and brute-force search and replacement is transformed into two stages: export and import. In the export stage, symbols are extracted, a two-way mapping table is established, and existing symbols are replaced with path placeholders. In the import stage, new symbols are generated based on the symbol mapping table, and a fast table lookup and replacement are performed. This phased processing improves logical clarity, code readability, and maintainability, reduces the coupling dependencies between modules, and, because the import stage has fewer steps and uses placeholders and table lookups instead of brute-force string searches, the installation speed of applications and forms is sometimes noticeably improved. Since importing applications or forms is a much more frequent operation than exporting, phased processing can significantly speed up user operation response and improve the user experience. Furthermore, annotations and symbol mapping tables can be used for troubleshooting, and modifications can be made after expanding functionality, reducing the complexity of the installation logic and the maintenance difficulty after system expansion.

[0060] In this embodiment, generating a new symbol corresponding to the symbol to be processed based on the annotation corresponding to the symbol to be processed may include: determining a new symbol generation method based on the symbol type in the annotation; and generating a new symbol corresponding to the symbol to be processed based on the symbol to be processed, the new symbol generation method, and the symbol scope in the annotation. It is understood that the new symbol generation method can differ depending on the symbol type, for example, it may be randomly generated or a suffix may be added, and then a new symbol is generated based on the symbol to be processed, the new symbol generation method, and the symbol scope in the annotation.

[0061] In this embodiment, after creating a symbol mapping table based on the symbols to be processed and the occupants, the process may further include: sorting the mapping table according to the length of each symbol to be processed in descending order of length; correspondingly, generating a new symbol corresponding to each symbol to be processed based on the annotation corresponding to the symbol to be processed may include: generating a new symbol corresponding to each symbol to be processed based on the annotation corresponding to each symbol to be processed, according to the order of the symbols to be processed in the mapping table. By rearranging the symbols to place longer symbols before shorter symbols so that they can be processed first, it ensures that even in scenarios where some symbols can contain each other, they can still be processed correctly.

[0062] In this embodiment, creating a symbol mapping table based on the symbol to be processed and the occupant may include: generating a forward symbol mapping table pointing from the symbol to be processed to the occupant based on the symbol to be processed and the occupant; after generating a new symbol corresponding to the symbol to be processed according to the annotation corresponding to the symbol to be processed, it may further include: generating a reverse symbol mapping table pointing from the occupant to the new symbol based on the new symbol and the occupant, so as to replace the corresponding occupant in the configuration file with the new symbol by querying the reverse symbol mapping table. That is, the symbol mapping table may specifically include a forward symbol mapping table pointing from the symbol to be processed to the occupant, and a reverse symbol mapping table pointing from the occupant to the new symbol. It can be seen that in the import stage, for example... Figure 3 As shown, the configuration file is first deserialized to obtain the model object and the reverse mapping table. Then, by querying the reverse mapping table, new symbols are generated based on the symbol type, original symbol value, and scope, and a reverse symbol mapping table is created. Finally, the occupier is replaced with the new symbol according to the reverse symbol mapping table, and a new form is generated after the replacement.

[0063] As can be seen from the above, this embodiment obtains the configuration fields of the form model to be migrated; the configuration fields are configuration fields after adding annotations to the target fields according to annotation rules; when exporting the file, the symbols to be processed are determined from the configuration fields according to the annotations, and the symbols to be processed are replaced with placeholders that can represent path positions. Then, a symbol mapping table is created based on the symbols to be processed and the placeholders, and the configuration file is exported; when importing the file, a new symbol corresponding to the symbols to be processed is generated according to the annotations corresponding to the symbols to be processed, and the new symbol is used to replace the corresponding placeholders in the configuration file according to the mapping table, until all placeholders in the configuration file are replaced. It can be seen that by adding annotations to the configuration fields of the form model, determining the symbols to be processed according to the annotations, and then replacing the symbols to be processed with placeholders that can represent path information, so that after generating the new symbols corresponding to the symbols to be processed, the new symbol is used to replace the corresponding placeholders according to the path information and the symbol mapping table, thus replacing brute-force string search with placeholders, table lookup, etc., the rapid installation of applications and forms in the low-code platform is realized, and the migration speed is improved.

[0064] Accordingly, this application also discloses a low-code platform form migration device, see [link to relevant documentation]. Figure 4 As shown, the device includes:

[0065] The configuration field acquisition module 11 is used to acquire the configuration fields of the form model; the configuration fields are configuration fields after annotations have been added to the target fields in advance according to the annotation rules;

[0066] The pending symbol replacement module 12 is used to determine the pending symbol from the configuration field according to the annotation after the file is exported, replace the pending symbol with a occupant character that can represent the path position, then create a symbol mapping table based on the pending symbol and the occupant character, and export the configuration file.

[0067] The occupant replacement module 13 is used to generate a new symbol corresponding to the symbol to be processed based on the annotation corresponding to the symbol to be processed after the file is imported, and replace the corresponding occupant in the configuration file with the new symbol according to the mapping table, until all occupants in the configuration file are replaced.

[0068] As can be seen from the above, this embodiment obtains the configuration fields of the form model to be migrated; the configuration fields are configuration fields after adding annotations to the target fields according to annotation rules; when exporting the file, the symbols to be processed are determined from the configuration fields according to the annotations, and the symbols to be processed are replaced with placeholders that can represent the path position. Then, a symbol mapping table is created based on the symbols to be processed and the placeholders, and the configuration file is exported; when importing the file, a new symbol corresponding to the symbols to be processed is generated according to the annotations corresponding to the symbols to be processed, and the new symbol is used to replace the corresponding placeholders in the configuration file according to the mapping table, until all placeholders in the configuration file are replaced. It can be seen that by adding annotations to the configuration fields of the form model, determining the symbols to be processed according to the annotations, and then replacing the symbols to be processed with placeholders that can represent path information, so that after generating the new symbols corresponding to the symbols to be processed, the new symbols are used to replace the corresponding placeholders according to the path information and the symbol mapping table, thus replacing brute-force string search with placeholders, table lookup, etc., the rapid installation of applications and forms in the low-code platform is realized, and the migration speed is improved.

[0069] In some specific embodiments, the symbol replacement module 12 may specifically include:

[0070] The field traversal unit is used to traverse each field of the configuration fields and determine whether the current field has a symbolic annotation.

[0071] The symbol determination unit is used to determine the symbol in the current field as the symbol to be processed if there is an annotation of the symbol type.

[0072] In some specific embodiments, the symbol replacement module 12 may specifically include:

[0073] The behavior determination unit is used to determine the symbol processing behavior in the annotation corresponding to the field where the symbol to be processed is located;

[0074] The symbol replacement unit is used to replace the symbol to be processed with an occupant that can represent the path location according to the symbol processing behavior, and to create a symbol mapping table based on the symbol to be processed and the occupant.

[0075] In some specific embodiments, the symbol replacement unit to be processed may specifically include:

[0076] The first replacement unit is configured to directly replace the symbol to be processed with an occupant that can represent the path location if the symbol processing behavior is a symbol generation behavior, and create a symbol mapping table based on the symbol to be processed and the occupant.

[0077] The second replacement unit is used to create a callback function if the symbol processing behavior is a symbol container or symbol reference behavior, so that after all the symbols to be processed in the configuration field have been traversed, the symbols to be processed are replaced with the corresponding occupants according to the symbol mapping table.

[0078] In some specific embodiments, the occupant replacement module 13 may specifically include:

[0079] A generation method determination unit is used to determine the new symbol generation method based on the symbol type in the annotation;

[0080] The new symbol generation unit is used to generate a new symbol corresponding to the symbol to be processed based on the symbol to be processed, the new symbol generation method, and the symbol scope in the annotation.

[0081] In some specific embodiments, the low-code platform form migration device may specifically include:

[0082] The sorting unit is used to sort the mapping table according to the length of each symbol to be processed in the mapping table, in descending order of the length of the symbols to be processed.

[0083] Correspondingly, the occupant replacement module 13 is also used to generate a new symbol corresponding to each of the symbols to be processed according to the order of the symbols to be processed in the mapping table and the annotation corresponding to each symbol to be processed.

[0084] In some specific embodiments, the symbol replacement module 12 may specifically include:

[0085] A forward symbol mapping table generation unit is used to generate a forward symbol mapping table pointing from the symbol to be processed to the occupant based on the symbol to be processed and the occupant;

[0086] Accordingly, the low-code platform form migration device may specifically include:

[0087] The reverse symbol mapping table generation unit is used to generate a reverse symbol mapping table based on the new symbol and the occupant, according to the forward symbol mapping table, in order to replace the corresponding occupant in the configuration file with the new symbol by querying the reverse symbol mapping table.

[0088] Furthermore, this application also discloses an electronic device, see [link to relevant documentation]. Figure 5 As shown, the content in the figure should not be considered as any limitation on the scope of use of this application.

[0089] Figure 5This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the low-code platform form migration method disclosed in any of the foregoing embodiments.

[0090] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0091] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored thereon include operating system 221, computer program 222 and data 223 including configuration fields, etc., and the storage method can be temporary storage or permanent storage.

[0092] The operating system 221 manages and controls the various hardware devices on the electronic device 20 and the computer program 222 to enable the processor 21 to perform calculations and processing on the massive amounts of data 223 in the memory 22. The operating system 221 can be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the low-code platform form migration method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs capable of performing other specific tasks.

[0093] Furthermore, this application also discloses a computer storage medium storing computer-executable instructions. When the computer-executable instructions are loaded and executed by a processor, they implement the steps of the low-code platform form migration method disclosed in any of the foregoing embodiments.

[0094] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0095] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0096] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only 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.

[0097] The above provides a detailed description of a low-code platform form migration method, apparatus, device, and medium provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A method for migrating forms to a low-code platform, characterized in that, include: Retrieve the configuration fields of the form model to be migrated; The configuration field is a configuration field in which annotations have been added to the target field in advance according to the annotation rules; When exporting the file, the symbol to be processed is determined from the configuration field according to the annotation, and the symbol to be processed is replaced with a occupant character that can represent the path location. Then, a symbol mapping table is created based on the symbol to be processed and the occupant character, and the configuration file is exported. When importing the file, a new symbol corresponding to the symbol to be processed is generated based on the annotation corresponding to the symbol to be processed, and the new symbol is used to replace the corresponding occupant in the configuration file according to the mapping table, until all occupants in the configuration file are replaced; The step of replacing the symbol to be processed with an occupant character that can represent the path location, and then creating a symbol mapping table based on the symbol to be processed and the occupant character, includes: Determine the symbol processing behavior in the annotation corresponding to the field containing the symbol to be processed; The symbol to be processed is replaced with an occupant that can represent the path location according to the symbol processing behavior, and a symbol mapping table is created based on the symbol to be processed and the occupant. The step of replacing the symbol to be processed with a occupant that can represent the path location according to the symbol processing behavior, and creating a symbol mapping table based on the symbol to be processed and the occupant, includes: If the symbol processing behavior is a symbol generation behavior, then the symbol to be processed is directly replaced with an occupant that can represent the path location, and a symbol mapping table is created based on the symbol to be processed and the occupant. If the symbol processing behavior is a symbol container or symbol reference behavior, a callback function is created so that after all the symbols to be processed in the configuration field have been traversed, the symbols to be processed are replaced with the corresponding occupants according to the symbol mapping table.

2. The low-code platform form migration method according to claim 1, characterized in that, The step of determining the symbol to be processed from the configuration field based on the annotation includes: Iterate through each field of the configuration fields and determine whether the current field contains a symbolic annotation; If a symbol type annotation exists, the symbol in the current field will be used as the symbol to be processed.

3. The low-code platform form migration method according to claim 1, characterized in that, The step of generating a new symbol corresponding to the symbol to be processed based on the annotation corresponding to the symbol to be processed includes: The method for generating new symbols is determined based on the symbol type in the annotation; Based on the symbol to be processed, the method for generating the new symbol, and the symbol scope in the annotation, a new symbol corresponding to the symbol to be processed is generated.

4. The low-code platform form migration method according to claim 1, characterized in that, After creating the symbol mapping table based on the symbol to be processed and the occupant, the method further includes: Based on the length of each symbol to be processed in the mapping table, the mapping table is sorted in descending order of the length of the symbols to be processed; Accordingly, generating a new symbol corresponding to the symbol to be processed based on the annotation corresponding to the symbol to be processed includes: According to the order of the symbols to be processed in the mapping table, a new symbol corresponding to each symbol to be processed is generated based on the annotation corresponding to each symbol to be processed.

5. The low-code platform form migration method according to claim 1, characterized in that, The step of creating a symbol mapping table based on the symbol to be processed and the occupant includes: Based on the symbol to be processed and the occupant, a positive symbol mapping table is generated from the symbol to be processed to the occupant; After generating the new symbol corresponding to the symbol to be processed based on the annotation corresponding to the symbol to be processed, the process further includes: Based on the new symbol and the occupant, a reverse symbol mapping table is generated from the forward symbol mapping table, pointing from the occupant to the new symbol, so that the new symbol can be used to replace the corresponding occupant in the configuration file by querying the reverse symbol mapping table.

6. A form migration device for a low-code platform, characterized in that, include: The configuration field retrieval module is used to retrieve the configuration fields of the form model; The configuration field is a configuration field in which annotations have been added to the target field in advance according to the annotation rules; The pending symbol replacement module is used to determine the pending symbols from the configuration fields according to the annotation after the file is exported, replace the pending symbols with occupants that can represent the path location, create a symbol mapping table based on the pending symbols and the occupants, and export the configuration file. The occupant replacement module is used to generate a new symbol corresponding to the symbol to be processed based on the annotation corresponding to the symbol to be processed after the file is imported, and replace the corresponding occupant in the configuration file with the new symbol according to the mapping table, until all occupants in the configuration file are replaced. The symbol replacement module includes: The behavior determination unit is used to determine the symbol processing behavior in the annotation corresponding to the field where the symbol to be processed is located; The symbol replacement unit is used to replace the symbol to be processed with an occupant that can represent the path location according to the symbol processing behavior, and to create a symbol mapping table based on the symbol to be processed and the occupant. The symbol replacement unit is configured to, if the symbol processing behavior is a symbol generation behavior, directly replace the symbol to be processed with an occupant character that can represent the path location, and create a symbol mapping table based on the symbol to be processed and the occupant character; if the symbol processing behavior is a symbol container or symbol reference behavior, create a callback function so that after all the symbols to be processed in the configuration field have been traversed, the symbol to be processed is replaced with the corresponding occupant character according to the symbol mapping table.

7. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the low-code platform form migration method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, Used to store computer programs; wherein the computer programs, when executed by a processor, implement the low-code platform form migration method as described in any one of claims 1 to 5.

Images