A method, device and medium for development and implementation of a business entity model

Abstract

The application provides a development implementation method, device and medium for a business entity model, the method acquires a basic model from at least one first developer terminal; wherein the basic model comprises a plurality of attribute fields of the business entity model. The attribute fields comprise one or more of the following: function module data structure, configuration file, front-end page structure, business logic. Based on a customized development instruction corresponding to at least one second developer terminal, a copy model of the basic model is established. And the terminal identifier of the corresponding second developer terminal is recorded to the development interface list of the copy model. Based on the customized development operation of the second developer terminal on the copy model, the corresponding customized development copy model is sent to the user terminal. And in the case of receiving a synchronous development instruction, the model update information of the basic model is synchronously updated to the copy model.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a method, device and medium for developing and implementing business entity models. Background Technology

[0002] In recent years, with the development of enterprise informatization, more and more enterprises have developed a demand for customized enterprise-specific information systems. However, a problem with customized business entity models is that as customization deepens, the final delivered product differs more and more from the software vendor's standard product. This difference includes both customer needs and gaps caused by customization and modification.

[0003] The aforementioned issues make subsequent version updates difficult, easily resulting in enterprise-specific versions that cannot be fully upgraded. Upgrades either only allow for the modification of less customized content or require complete customization based on the new version. This leads to high upgrade difficulty and a large workload. Summary of the Invention

[0004] This application provides a method, device, and medium for developing and implementing business entity models, which addresses the difficulty and workload of subsequent comprehensive upgrades when a business entity model is customized for a specific enterprise.

[0005] On one hand, embodiments of this application provide a method for developing and implementing a business entity model, the method comprising:

[0006] Obtain a basic model from at least one first developer terminal; wherein the basic model includes several attribute fields of a business entity model; the attribute fields include one or more of the following: functional module data structure, configuration file, front-end page structure, and business logic;

[0007] Based on the customized development instructions corresponding to at least one second developer terminal, a replica model of the basic model is established; and the terminal identifier of the corresponding second developer terminal is recorded in the development interface list of the replica model.

[0008] Based on the customized development operations performed by the second developer terminal on the replica model, the corresponding customized development replica model is sent to the user terminal; and

[0009] Upon receiving a synchronous development instruction, the model update information of the base model is synchronously updated to the copy model.

[0010] In one implementation of this application, a replica model of the basic model is established based on custom development instructions corresponding to at least one second developer terminal, specifically including:

[0011] Based on the customized development instructions, the control permissions of each replica model in the preset control permission set are determined; wherein, the control permissions are the development permissions of the second developer terminal for each attribute field in the corresponding replica model;

[0012] Based on the control permissions and the corresponding distribution of the second developer terminals, a replica model corresponding to the basic model is established; the distribution includes at least a quantity distribution and a preset partitioning rule grouping distribution.

[0013] In one implementation of this application, a replica model corresponding to the basic model is established based on the control permissions and the corresponding distribution of the second developer terminals, specifically including:

[0014] Obtain a pre-stored permission allocation list; the permission allocation list is pre-stored in a preset database;

[0015] Based on the permission allocation list, match each control permission with each second developer terminal;

[0016] Based on the control permissions matched by each of the second developer terminals, a corresponding copy model is established.

[0017] In one implementation of this application, upon receiving a synchronous development instruction, the model update information of the base model is synchronously updated to the copy model, specifically including:

[0018] Based on the synchronous development instructions, the base model and each of the replica models are determined;

[0019] According to the preset synchronization rules, the attribute fields of the base model are compared with the attribute fields of each of the replica models to determine the model update information of the base model, so as to synchronize the model update information of the base model to the replica models.

[0020] In one implementation of this application, according to a preset synchronization rule, the attribute fields of the base model are compared with the attribute fields of each of the replica models to determine the model update information of the base model, specifically including:

[0021] Determine the control permissions for each attribute field in each of the base models and each of the replica models;

[0022] And generate a permission change list corresponding to each of the control permissions; wherein, the permission change list includes permission change information for each of the attribute fields and update permissions for the control permissions of each of the attribute fields; the update permission indicates whether the control permission can be updated after the control permission is changed;

[0023] Based on the permission change list, the attribute fields of the base model are compared with the attribute fields of each of the replica models to determine the model update information.

[0024] In one implementation of this application, the method further includes:

[0025] Based on the model accumulation module, the model characteristic information of the copy model from the user terminal and / or the second developer terminal is determined; the model characteristic information includes attribute fields in the copy model that are different from the base model;

[0026] The model characteristic information is sent to the corresponding first developer terminal, so that the model characteristic information is updated to the base model based on the operation of the first developer terminal.

[0027] In one implementation of this application, before synchronously updating the model update information of the base model to the copy model upon receiving a synchronous development instruction, the method further includes:

[0028] Determine the terminal identifiers of the first developer terminal and the second developer terminal;

[0029] Each terminal identifier is matched with an identity authentication list to determine whether the terminal identifier has a preset identity authentication interface, so as to obtain the corresponding synchronous development instructions.

[0030] In one implementation of this application, the base model and the copy model are generated based on a low-code platform.

[0031] On the other hand, embodiments of this application also provide a development and implementation device for a business entity model, the device comprising:

[0032] At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0033] Obtain a basic model from at least one first developer terminal; wherein the basic model includes several attribute fields of a business entity model; the attribute fields include one or more of the following: functional module data structure, configuration file, front-end page structure, and business logic;

[0034] Based on the customized development instructions corresponding to at least one second developer terminal, a replica model of the basic model is established; and the terminal identifier of the corresponding second developer terminal is recorded in the development interface list of the replica model.

[0035] Based on the customized development operations performed by the second developer terminal on the replica model, the corresponding customized development replica model is sent to the user terminal; and

[0036] Upon receiving a synchronous development instruction, the model update information of the base model is synchronously updated to the copy model.

[0037] Furthermore, embodiments of this application also provide a non-volatile computer storage medium for developing and implementing business entity models, storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0038] Obtain a basic model from at least one first developer terminal; wherein the basic model includes several attribute fields of a business entity model; the attribute fields include one or more of the following: functional module data structure, configuration file, front-end page structure, and business logic;

[0039] Based on the customized development instructions corresponding to at least one second developer terminal, a replica model of the basic model is established; and the terminal identifier of the corresponding second developer terminal is recorded in the development interface list of the replica model.

[0040] Based on the customized development operations performed by the second developer terminal on the replica model, the corresponding customized development replica model is sent to the user terminal; and

[0041] Upon receiving a synchronous development instruction, the model update information of the base model is synchronously updated to the copy model.

[0042] Through the aforementioned technical solution, this application, via a first developer terminal and a second developer terminal, completes the replication of the business entity model from the basic model to obtain a copy model, further expands the model, completes the customized development of the business entity model, and facilitates the convenient upgrade of the business entity model on the user product side. This solves the technical problem of the difficulty and large workload of subsequent comprehensive upgrades when an enterprise's business entity model is customized. Attached Figure Description

[0043] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0044] Figure 1 This is a flowchart illustrating a method for developing and implementing a business entity model according to an embodiment of this application.

[0045] Figure 2 This is a schematic diagram of the structure of a development and implementation device for a business entity model according to an embodiment of this application. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0047] In recent years, with the development of enterprise informatization, more and more companies have developed a demand for customized enterprise-specific information systems. However, a problem with enterprise-specific customization is that as customization deepens, the final delivered product differs more and more from the software vendor's standard product. This difference includes aspects that meet customer needs, as well as gaps created by customization and modifications. This makes subsequent version updates difficult, easily resulting in enterprise-specific versions that cannot be fully upgraded. Upgrades either only allow for the modification of less customized content or require complete customization based on a new version. Upgrades are difficult and involve a large workload.

[0048] Based on the above issues, a new development and implementation method for business entity models is proposed. This significantly improves the degree of customization for enterprise-specific projects, enabling finer-grained upgrades and allowing customized products to continuously receive the latest features of standardized products. Furthermore, modifications to commonalities discovered during customized development can be preserved and reused, facilitating customization for other enterprises. This greatly reduces customization costs and extends the product lifecycle for customized enterprises, improving the cost-effectiveness of purchased products for buyers. It represents a modern software industrial development and delivery methodology.

[0049] Based on this, embodiments of this application provide a method, device, and medium for developing and implementing business entity models, which addresses the difficulty and workload of subsequent comprehensive upgrades when a company customizes its business entity model.

[0050] The various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0051] This application provides a method for developing and implementing a business entity model, such as... Figure 1 As shown, the method may include steps S101-S104:

[0052] S101, the server obtains the base model from at least one first developer terminal.

[0053] The basic model includes several attribute fields of the business entity model. These attribute fields include one or more of the following: functional module data structure, configuration file, front-end page structure, and business logic.

[0054] It should be noted that the server, as the execution entity for the development and implementation method of the business entity model, exists only as an example, and the execution entity is not limited to the server. This application does not make any specific limitation in this regard.

[0055] In the fields of enterprise software and SaaS, this application provides a development method that, while allowing for customized development based on customer needs, also maintains a consistent and continuous product update and release mechanism, based on the business entity model upon which the software relies. It primarily achieves multi-party collaborative development capabilities through a replicable, scalable, and sustainably modifiable entity model, a synchronization system, and a control system. Based on this capability, this application addresses the long-standing problem of unproductization in customized development, providing a development implementation method that enables the integration of productized development results with customized development results.

[0056] The first developer terminal can be a computer, server, or other similar device; this application does not specify a particular type. In actual use, there can be multiple first developer terminals, meaning that the development of the basic model can be performed by multiple terminals, as long as they are based on the same business entity model. The basic model can be understood as a model with basic functionalities within a system, upon which the second developer terminal or user can perform secondary development.

[0057] In practical use, a basic model developed by one or more first developer terminals is sent to the server, which then further develops and implements the business entity model. In this embodiment, the basic model and the copy model obtained by copying the basic model are generated based on a low-code platform.

[0058] The basic model has multiple parameters, the parameter codes are as follows:

[0059] {

[0060] ButtonConfig: null, / / Button configuration

[0061] LayoutConfig: null, / / Layout configuration

[0062] ColumnConfig: null, / / Regional configuration

[0063] ControlConfig: null, / / Control configuration

[0064] BasicConfig: null, / / Basic configuration

[0065] PageConfig: null, / / Page configuration

[0066] ScriptInfo: null, / / Script configuration

[0067] ... / / Including but not limited to the above configurations

[0068] }

[0069] S102, the server establishes a replica model of the basic model based on the customized development instructions corresponding to at least one second developer terminal. The server also records the terminal identifier of the corresponding second developer terminal in the development interface list of the replica model.

[0070] In this embodiment, the second developer terminal can actively send customized development instructions to the server, or the first developer terminal can grant customized development instructions to the second developer terminal through the server, thereby giving the second developer terminal the permission to develop a copy of the basic model.

[0071] The second developer terminal can be understood as the terminal that the first developer terminal publishes tasks for personalized development, such as the computer or laptop of a developer in a software outsourcing company. The second developer terminal can obtain a copy model sent by the server through customized development instructions. There can be multiple second developer terminals, that is, multiple second developer terminals can develop in the same or different directions (such as the development direction for the payment function module) based on the same copy model, or multiple second developer terminals can develop based on different copy models.

[0072] Developing based on the same replica model allows software developers to customize the base model if needed, enabling a second developer terminal to tailor the development to meet those customization requirements. Conversely, developing based on different replica models allows for the creation of different functional modules for different users.

[0073] For example, in a business entity model to be developed, the first user needs a payment interface, a purchase interface, etc., and each interface has different customization requirements. The second developer terminal can develop a copy model to meet these different requirements. Specifically, some second developer terminals can develop the payment interface, and some can develop the purchase interface. If the second user also needs a payment interface, a purchase interface, and a sharing interface, the first developer terminal can select at least one second developer terminal to fulfill the second user's customization needs.

[0074] In this embodiment of the application, a copy model of the basic model is established based on customized development instructions corresponding to at least one second developer terminal, specifically including:

[0075] Based on the customized development instructions, the server determines the control permissions for each replica model in the preset control permission set. These control permissions refer to the development permissions of the second developer terminal for each attribute field in the corresponding replica model. Subsequently, the server establishes the corresponding replica models for the base model based on the control permissions and the distribution of the corresponding second developer terminals. This distribution includes at least a quantity distribution and a grouping distribution based on preset partitioning rules.

[0076] In other words, based on customized development instructions from the first or second developer terminal, the server retrieves the control permissions of the second developer terminal for each replica model. These control permissions are pre-stored in a control permission set, which can be pre-stored in a database connected to the server. In actual use, there can be multiple second developer terminals; the replica models can be distributed according to preset partitioning rules, and these partitions correspond to the distribution of the second developer terminals. For example, partitioning by product can create multiple groups of second developer terminals, each developing different products, with different terminal groups having different numbers of terminals.

[0077] For the distribution of different control permissions and corresponding second developer terminals, at least one replica model can be established to enable the second developer terminals to perform extended development. In actual use, second developer terminals with different control permissions may be in the same partition group or may not be in the same partition group. That is to say, multiple second developer terminals with different control permissions can develop a replica model simultaneously. The specific settings are based on the actual use of this application, and this application does not impose specific limitations on this.

[0078] In this embodiment of the application, a copy model of the basic model is established according to the control permissions and the distribution of the corresponding second developer terminals, specifically including:

[0079] The server retrieves a pre-stored permission assignment list. This list is pre-stored in a default database. Then, based on the permission assignment list, it matches each control permission with each secondary developer terminal. Finally, based on the control permissions matched to each secondary developer terminal, it establishes a corresponding replica model.

[0080] In other words, the database connected to the server pre-stores a permission allocation list, which contains the correspondence between the second developer's terminal and the control permissions. After obtaining the terminal identifier of the second developer's terminal, the server matches the control permissions corresponding to that terminal identifier using the permission allocation list, thereby establishing a replica model with the corresponding control permissions on the second developer's terminal.

[0081] The above solution enables customized development to become product updates, allowing multiple developers to develop the same model without conflict and to combine them correctly, thereby enabling business entity models to be shared and developed collaboratively.

[0082] S103, the server sends the corresponding customized replica model to the user terminal based on the customized development operation of the replica model on the second developer terminal.

[0083] In this embodiment, the second developer terminal performs customized development operations on the replica model, thereby expanding the attribute fields and functions of the replica model to meet the user's customization needs. The second developer terminal can provide the developed replica model to the user terminal. In actual use, the user terminal can use the replica model or further develop it.

[0084] S104: Upon receiving a synchronous development instruction, the server synchronously updates the model update information of the base model to the replica model.

[0085] In this embodiment of the application, upon receiving a synchronous development instruction, the model update information of the base model is synchronously updated to the copy model, specifically including:

[0086] First, the server determines the base model and each replica model based on the synchronous development instructions. Then, according to preset synchronization rules, it compares the attribute fields of the base model with the attribute fields of each replica model to determine the model update information for the base model, and then synchronizes this update information to the replica models.

[0087] Synchronous development commands can be sent from the first developer terminal to the server to synchronize the update information of the basic model to the copy model of the second developer terminal; alternatively, the second developer terminal can actively send the commands to the server, which will then obtain the basic model generated by the first developer terminal and synchronize the model update information to the copy model.

[0088] The server can determine the synchronization rules for updating the base model to the replica model, specifically:

[0089] The server determines the control permissions for each attribute field in each base model and each replica model. It then generates a permission change list for each control permission. This permission change list includes permission change information for each attribute field and update permissions for each attribute field's control permissions. Update permissions indicate whether an attribute can be updated after a control permission change. Based on the permission change list, the attribute fields of the base models are compared with the attribute fields of each replica model to determine model update information.

[0090] In other words, the server can determine the control permissions of attribute fields and establish a list of permission changes. This list contains information about permission changes to attribute fields, i.e., information about attribute fields being modified by the second developer's terminal. It also includes preset update permissions for the attribute fields, i.e., permissions that allow updates to be made even after modifications by the second developer's terminal. Based on the permission change list, the server can compare the attribute fields sequentially to determine the update content of the base model compared to the unupdated replica model, and whether the replica model can be updated by the base model, thus obtaining model update information.

[0091] In this embodiment of the application, during the basic model development of the business entity model, in order to better meet user customization needs, this application can also:

[0092] The server, based on the model accumulation module, determines the model characteristic information of the replica model from the user terminal and / or the second developer terminal. This model characteristic information includes attribute fields in the replica model that differ from the base model. Then, the server sends this model characteristic information to the corresponding first developer terminal, so that, based on the operations performed by the first developer terminal, the model characteristic information is updated in the base model.

[0093] In other words, the server in this application can obtain model characteristic information from a replica model that has been customized by a second developer terminal or user terminal through model sedimentation, and then send the model characteristic information to the first developer terminal so that the first developer terminal can update the base model according to the customized model characteristic information. Subsequently, during model synchronization, the base model carries the model characteristic information to update more replica models.

[0094] In this embodiment of the application, before synchronously updating the model update information of the base model to the copy model upon receiving a synchronous development instruction, the method further includes:

[0095] The server determines the terminal identifiers of the first and second developer terminals. It then matches each terminal identifier against an authentication list to determine if a preset authentication interface exists for that terminal, in order to obtain the corresponding synchronous development instructions.

[0096] This application can enable the synchronization module system to have an authentication interface, such as an authorization authentication token, through the following code.

[0097] The `SyncModel` class, defined as `string basicId, string extendId`, is used to call the synchronization system's interface. In other words, the server can establish an authentication list based on terminal identifiers to restrict the permissions of each terminal to issue synchronous development commands. Specifically, in practical use, if there are multiple sets of primary or secondary developer terminals, one terminal can be selected to issue synchronous development commands, allowing the synchronization system to overwrite parts of the basic model onto the extended model, thus completing the attribute synchronization of the extended model.

[0098] This application provides a product-based update solution for customized development through the aforementioned approach. Multiple developers can work on the same model without conflict and can combine them correctly. The development process includes control rules and synchronization rules, making it easier to complete the development of business entity models. It also allows for the accumulation of model features to meet subsequent user customization needs. This simplifies and reduces costs by enabling product-based, shared, and collaborative development of business entity models, resolving the technical challenges and workload associated with comprehensive upgrades after customizing a company's business entity model.

[0099] Figure 2 This application provides an embodiment of a development and implementation device for a business entity model, the device comprising:

[0100] At least one processor. And a memory communicatively connected to the at least one processor. The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0101] Obtain the base model from at least one primary developer terminal. The base model includes several attribute fields of the business entity model. These attribute fields include one or more of the following: functional module data structure, configuration file, front-end page structure, and business logic.

[0102] Based on the customized development instructions corresponding to at least one second developer terminal, a replica model of the basic model is established. The terminal identifier of the corresponding second developer terminal is then recorded in the development interface list of the replica model.

[0103] Based on the customized development operations of the replica model on the second developer terminal, the corresponding customized replica model is sent to the user terminal.

[0104] Upon receiving a synchronous development instruction, the model update information of the base model will be synchronously updated to the copy model.

[0105] This application embodiment also provides a non-volatile computer storage medium for developing and implementing business entity models, storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0106] Obtain the base model from at least one primary developer terminal. The base model includes several attribute fields of the business entity model. These attribute fields include one or more of the following: functional module data structure, configuration file, front-end page structure, and business logic.

[0107] Based on the customized development instructions corresponding to at least one second developer terminal, a replica model of the basic model is established. The terminal identifier of the corresponding second developer terminal is then recorded in the development interface list of the replica model.

[0108] Based on the customized development operations of the replica model on the second developer terminal, the corresponding customized replica model is sent to the user terminal.

[0109] Upon receiving a synchronous development instruction, the model update information of the base model will be synchronously updated to the copy model.

[0110] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the embodiments of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0111] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0112] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0113] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0114] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0115] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0116] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0117] It should also be noted that 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 limitation, 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.

[0118] This specification can be described in the general context of computer-executable instructions that are executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This specification can also be practiced in distributed computing environments, where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0119] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments for devices and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0120] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0121] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. A development and implementation method for a business entity model, characterized in that, The method includes: Obtain a basic model from at least one first developer terminal; wherein the basic model includes several attribute fields of a business entity model; the attribute fields include one or more of the following: functional module data structure, configuration file, front-end page structure, and business logic; Based on the customized development instructions corresponding to at least one second developer terminal, a replica model of the basic model is established; and the terminal identifier of the corresponding second developer terminal is recorded in the development interface list of the replica model. Based on the customized development operations performed by the second developer terminal on the replica model, the corresponding customized development replica model is sent to the user terminal; and Upon receiving a synchronous development instruction, the model update information of the base model is synchronously updated to the copy model.

2. The method according to claim 1, characterized in that, Based on customized development instructions corresponding to at least one second developer terminal, a replica model of the basic model is established, specifically including: Based on the customized development instructions, the control permissions of each replica model in the preset control permission set are determined; wherein, the control permissions are the development permissions of the second developer terminal for each attribute field in the corresponding replica model; Based on the control permissions and the corresponding distribution of the second developer terminals, a replica model corresponding to the basic model is established; the distribution includes at least a quantity distribution and a preset partitioning rule grouping distribution.

3. The method according to claim 2, characterized in that, Based on the control permissions and the corresponding distribution of the second developer terminals, establish a replica model corresponding to the basic model, specifically including: Obtain a pre-stored permission allocation list; the permission allocation list is pre-stored in a preset database; Based on the permission allocation list, match each control permission with each second developer terminal; Based on the control permissions matched by each of the second developer terminals, a corresponding copy model is established.

4. The method according to claim 1, characterized in that, Upon receiving a synchronous development instruction, the model update information of the base model is synchronously updated to the copy model, specifically including: Based on the synchronous development instructions, the base model and each of the replica models are determined; According to the preset synchronization rules, the attribute fields of the base model are compared with the attribute fields of each of the replica models to determine the model update information of the base model, so as to synchronize the model update information of the base model to the replica models.

5. The method according to claim 4, characterized in that, According to preset synchronization rules, the attribute fields of the base model are compared with the attribute fields of each replica model to determine the model update information of the base model, specifically including: Determine the control permissions for each attribute field in each of the base models and each of the replica models; And generate a permission change list corresponding to each of the control permissions; wherein, the permission change list includes permission change information for each of the attribute fields and update permissions for the control permissions of each of the attribute fields; the update permission indicates whether the control permission can be updated after the control permission is changed; Based on the permission change list, the attribute fields of the base model are compared with the attribute fields of each of the replica models to determine the model update information.

6. The method according to claim 1, characterized in that, The method further includes: Based on the model accumulation module, the model characteristic information of the copy model from the user terminal and / or the second developer terminal is determined; the model characteristic information includes attribute fields in the copy model that are different from the base model; The model characteristic information is sent to the corresponding first developer terminal, so that the model characteristic information is updated to the base model based on the operation of the first developer terminal.

7. The method according to claim 1, characterized in that, Upon receiving a synchronous development instruction, before synchronously updating the model update information of the base model to the copy model, the method further includes: Determine the terminal identifiers of the first developer terminal and the second developer terminal; Each terminal identifier is matched with an identity authentication list to determine whether the terminal identifier has a preset identity authentication interface, so as to obtain the corresponding synchronous development instructions.

8. The method according to claim 1, characterized in that, The base model and the copy model are generated based on a low-code platform.

9. A development and implementation device for business entity models, characterized in that, The device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Obtain a basic model from at least one first developer terminal; wherein the basic model includes several attribute fields of a business entity model; the attribute fields include one or more of the following: functional module data structure, configuration file, front-end page structure, and business logic; Based on the customized development instructions corresponding to at least one second developer terminal, a replica model of the basic model is established; and the terminal identifier of the corresponding second developer terminal is recorded in the development interface list of the replica model. Based on the customized development operations performed by the second developer terminal on the replica model, the corresponding customized development replica model is sent to the user terminal; and Upon receiving a synchronous development instruction, the model update information of the base model is synchronously updated to the copy model.

10. A non-volatile computer storage medium for developing and implementing business entity models, storing computer-executable instructions, characterized in that, The computer-executable instructions are set as follows: Obtain a basic model from at least one first developer terminal; wherein the basic model includes several attribute fields of a business entity model; the attribute fields include one or more of the following: functional module data structure, configuration file, front-end page structure, and business logic; Based on the customized development instructions corresponding to at least one second developer terminal, a replica model of the basic model is established; and the terminal identifier of the corresponding second developer terminal is recorded in the development interface list of the replica model. Based on the customized development operations performed by the second developer terminal on the replica model, the corresponding customized development replica model is sent to the user terminal; and Upon receiving a synchronous development instruction, the model update information of the base model is synchronously updated to the copy model.

Images