Application resource determination method and apparatus, server, and computer-readable storage medium

Abstract

Embodiments of the present application provide a kind of application resource determination method, device, server and computer readable storage medium, according to the instruction of creating customer version, corresponding customer version record is generated;Customer version record is one-to-one with customer version;According to the instruction of creating customer version resource, the customer version data of resource to be created is generated;According to the instruction of modifying standard version resource by customer version, the standard version data of resource to be modified is copied to generate target customer version data;According to the synchronization instruction of standard version upgrade, the resource from standard version to customer version is synchronized with the existence customer version data.This scheme supports customer version and standard version to share resource data, customer version copies the standard version data of resource to generate customer version data according to custom demand, and realizes the upgrade synchronization between customer version and standard version according to custom demand, effectively reduces data redundancy, reduces maintenance difficulty and cost, improves development efficiency and user experience.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of application development, in particular to an application resource determination method and device, a server and a computer readable storage medium. BACKGROUND

[0002] With the rapid development of enterprise digitization, more and more personalized applications need to be developed faster and more efficiently. Low-code development is a visual application development method that uses drag-and-drop components or model-driven methods to create web pages and applications.

[0003] Currently, when customizing a personalized version of a form or application, a copy is usually made based on an existing standard version or a template, and then personalized and customized development is performed on this basis. This will generate a large amount of redundant data, increasing maintenance costs, complicating upgrades, and making it prone to errors. SUMMARY

[0004] Therefore, the present application aims to provide an application resource determination method and device, a server and a computer readable storage medium, which can support sharing of resource data between customer versions and standard versions, and generate customer version data by copying standard version data of resources according to custom requirements, effectively reducing data redundancy, reducing maintenance difficulty and cost, and improving development efficiency and user experience.

[0005] To achieve the above-mentioned purpose, the technical solutions adopted by the embodiments of the present application are as follows:

[0006] In a first aspect, the present application provides an application resource determination method, which comprises:

[0007] According to the creation of a customer version instruction, a corresponding customer version record is generated; the customer version record corresponds one-to-one to the customer version;

[0008] According to the creation of a customer version resource instruction, customer version data of the resource to be created is generated;

[0009] According to the instruction for modifying the standard version resource of the customer version, the standard version data of the resource to be modified is copied to generate target customer version data; the standard version data is the resource data that already exists on the standard version for the resource to be modified; the target customer version data is the resource data generated on the customer version for the resource to be modified;

[0010] According to the synchronization instruction for the standard version upgrade, the resource existing in the customer version data is synchronized from the standard version to the customer version.

[0011] In an optional embodiment, the step of generating a corresponding customer version record according to the creation of a customer version instruction comprises:

[0012] receiving a create client version instruction; the create client version instruction comprising an application identifier;

[0013] allocating a client version identifier for the client version to be created;

[0014] generating a corresponding client version record according to the application identifier and the client version identifier.

[0015] In an optional embodiment, the step of generating client version data of the resource to be created according to the create client version resource instruction comprises:

[0016] receiving a create client version resource instruction; the create client version resource instruction comprising attribute information of the resource to be created and a client version identifier;

[0017] allocating a resource identifier for the resource to be created;

[0018] generating client version data of the resource to be created according to the resource identifier, the client version identifier and the attribute information.

[0019] In an optional embodiment, the step of copying standard version data of the resource to be modified to generate target client version data according to the instruction of modifying the standard version resource by the client version comprises:

[0020] when the resource to be modified is a standard version resource and no client version data exists, copying the standard version data to generate snapshot data;

[0021] generating the target client version data according to the modification data in the instruction of modifying the standard version resource by the client version and the snapshot data.

[0022] In an optional embodiment, the step of modifying the standard version resource by the client version further comprises:

[0023] when the resource to be modified is a standard version resource and client version data exists, obtaining snapshot data, client version data and latest standard version data;

[0024] generating the target client version data according to the modification data in the instruction of modifying the standard version resource by the client version, the snapshot data, the client version data and the latest standard version data.

[0025] In a second aspect, the present application provides an application resource determination device, which comprises:

[0026] The design module is configured to generate a corresponding customer version record according to a customer version creation instruction; the customer version record corresponds to the customer version; generate customer version data of a resource to be created according to a customer version resource creation instruction; and copy standard version data of a resource to be modified to generate target customer version data according to an instruction for modifying a standard version by a customer version; the standard version data is resource data of the resource to be modified that already exists on the standard version; and the target customer version data is resource data of the resource to be modified that is generated on the customer version.

[0027] The upgrade module is configured to synchronize a resource existing in the customer version data from the standard version to the customer version according to a synchronization instruction for standard version upgrade.

[0028] In an optional embodiment, the design module is specifically configured to:

[0029] receive a customer version creation instruction; the customer version creation instruction includes an application identifier; assign a customer version identifier to a customer version to be created; and generate a corresponding customer version record according to the application identifier and the customer version identifier.

[0030] In an optional embodiment, the design module is specifically configured to:

[0031] receive a customer version resource creation instruction; the customer version resource creation instruction includes attribute information and a customer version identifier of the resource to be created; assign a resource identifier to the resource to be created; and generate customer version data of the resource to be created according to the resource identifier, the customer version identifier and the attribute information.

[0032] In a third aspect, the present application provides a server, the server comprising a memory and a processor, the memory being configured to store a computer program, and the processor being configured to execute the application resource determination method according to any one of the preceding embodiments when the computer program is invoked.

[0033] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the application resource determination method according to any one of the preceding embodiments.

[0034] Compared with the prior art, the application embodiment provides an application resource determination method, device, server and computer readable storage medium, a corresponding customer version record is generated according to a customer version creation instruction; the customer version record corresponds to the customer version one by one; customer version data of a resource to be created is generated according to a customer version resource creation instruction; target customer version data is copied from standard version data of a resource to be modified to generate, according to an instruction for modifying a standard version resource by a customer version; the standard version data is resource data that already exists on the standard version of the resource to be modified; the target customer version data is resource data generated on the customer version of the resource to be modified; and the resource with the existing customer version data is synchronized from the standard version to the customer version according to a synchronization instruction for standard version upgrade. The scheme supports sharing of resource data between the customer version and the standard version, the customer version copies the standard version data of the resource to generate customer version data according to customization requirements, and upgrade synchronization between the customer version and the standard version is realized according to customization requirements, thereby effectively reducing data redundancy, reducing maintenance difficulty and cost, and improving development efficiency and user experience.

[0035] In order to make the above objectives, characteristics and advantages of the present application more apparent, comprehensible and easy to understand, the following preferred embodiments are specifically described below, and the accompanying drawings are referred to for detailed description. BRIEF DESCRIPTION OF DRAWINGS

[0036] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments. It should be understood that the following drawings only show some embodiments of the present application, and therefore should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can also be obtained without creative labor on the basis of these drawings.

[0037] Figure 1 A kind of application scenario schematic diagram provided by the embodiment of the present application is shown.

[0038] Figure 2 A kind of application resource determination method schematic diagram provided by the embodiment of the present application is shown.

[0039] Figure 3 A kind of application resource determination method schematic diagram provided by the embodiment of the present application is shown. Figure 2 A kind of sub-step flow schematic diagram in step S101 is shown.

[0040] Figure 4 A kind of sub-step flow schematic diagram in step S102 is shown. Figure 2 A kind of sub-step flow schematic diagram in step S103 is shown.

[0041] Figure 5 A kind of sub-step flow schematic diagram in step S103 is shown. Figure 2 A kind of sub-step flow schematic diagram in step S103 is shown.

[0042] Figure 6A flowchart of an application development is shown.

[0043] Figure 7 A schematic diagram of data merging is shown.

[0044] Figure 8 A block diagram of an application resource determination apparatus provided by an embodiment of the present application is shown.

[0045] Figure 9 A block diagram of a server provided by an embodiment of the present application is shown.

[0046] Icon: 10 - client; 20 - design end; 30 - running end; 100 - server; 110 - memory; 120 - processor; 130 - communication module; 200 - application resource determination apparatus; 201 - design module; 202 - upgrade module. DETAILED DESCRIPTION

[0047] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments. The components of the embodiments of the present application described and shown in the accompanying drawings can be arranged and designed in various different configurations.

[0048] Therefore, the detailed description of the embodiments of the present application provided in the accompanying drawings below is not intended to limit the scope of the claimed present application, but only represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0049] It should be noted that the relational terms such as "first" and "second" and the like are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that these entities or operations have any such actual relationship or order. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the processes, methods, articles or devices including a series of elements not only include those elements, but also include other elements not explicitly listed or inherent to such processes, methods, articles or devices. Without more limitations, the element defined by the statement "including a" does not exclude the presence of another identical element in the process, method, article or device including the element.

[0050] In the prior art, when developing an application and a form by using low code, all resources of a standard version are copied to generate a customized customer version, and then the customer version is modified based on the copied customer version. The customer version application generated in this way is independent, which is equivalent to a new application. The standard version mentioned herein refers to an initial version of an application or a form, and the resources refer to configuration data created in the low code development process, which can include models, fields, objects, menus, interfaces, forms, etc. The resources are usually divided into definition data and design data.

[0051] When a customer version application is newly created, all resource data of the standard version need to be copied. This will cause a large amount of redundant data because most of the uncustomized resources are also copied. When the standard version is upgraded to optimize functions or fix defects, the upgrade needs to be synchronized to the customer version, which will require repeated modification multiple times, and the upgrade will become more complex and more prone to errors.

[0052] Based on this, the embodiments of the present application provide an application resource determination method and device, a server and a computer readable storage medium. The customer version and the standard version share resource data, the customer version copies the standard version data of the resources to generate customer version data according to the customization requirements, and the upgrade synchronization between the customer version and the standard version is realized according to the customization requirements, which effectively reduces data redundancy, reduces maintenance difficulty and cost, and improves development efficiency and user experience.

[0053] Please refer to Figure 1 , Figure 1 An application scenario provided by the embodiments of the present application is shown. In Figure 1 , the design end 20 is in communication connection with the client end 10 and the running end 30 respectively. The client end 10 issues an operation instruction of an application or a form to the design end 20, and the operation instruction can include a customer version application creation instruction, a customer version resource creation instruction, a customer version modification standard version resource instruction, a customer version deletion standard version resource instruction, a standard version upgrade synchronization instruction, a standard version or customer version resource list pulling instruction, etc. After receiving the operation instruction of the client end, the design end 20 executes the steps of S101-S104 and the corresponding sub-steps in the following examples according to the specific requirements of the instruction, so as to realize the corresponding technical effects. After the design end 20 completes the design and development, the design data needs to be exported and loaded and run in the running end 30, so as to facilitate the display of the final design results.

[0054] According to the operation instruction, the design terminal 20 generates or updates the management data or resource data of the application or the table, which includes a customer information table for recording the customer version, a resource deletion record for recording the customer version deletion standard version resource, a user access list for recording the last access of the user to the customer version of the application, and resource data of the customer version and the standard version. The management data or resource data generated in the design and development process needs to be saved in the storage space.

[0055] Specifically, the storage space can be the storage space of the design terminal 20, such as a local database, a disk, etc. Alternatively, the storage space can be an independent database in communication connection with the design terminal 20, such as a remote database server. The design terminal 20 and the running terminal 30 can run on the same server or different servers. The present application is not limited in this regard.

[0056] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0057] Figure 2 Fig. 1 shows a schematic diagram of the application resource determination method provided by the embodiment of the present application. The execution subject of the method can be the design terminal as described above. As shown in Fig. 1, the method can include the following steps: Figure 2

[0058] In step S101, a corresponding customer version record is generated according to the creation of the customer version instruction.

[0059] The customer version record corresponds to the customer version one by one.

[0060] In the embodiment of the present application, it is assumed that the customer customizes and develops the application. According to the customer customization requirement, a corresponding customer version record is generated, and the newly generated customer version record is added to the customer information table. At the same time, the updated customer information table is saved, which can be saved locally or in a database server. The present application is not limited in this regard.

[0061] As an implementation manner, after the server saves the newly generated customer version record, the server notifies the client that the creation of the customer version is successful. Then, the client issues a refresh request for the customer version resource list, and the server sends the updated customer information table to the client according to the refresh request.

[0062] As another implementation manner, after the creation of the customer version is successful, the server sends the updated customer information table to the client, and notifies the client that the creation of the customer version is successful. The specific manner of notifying the client after the creation of the customer version is successful is not limited in the present application.

[0063] ​Specifically, after the customer version is created successfully, the administrator can configure the access right of the customer version for the related user, and the user with the configured access right can realize the customized development of the customer version.

[0064] In step S102, the customer version data of the resource to be created is generated according to the instruction of creating the customer version resource.

[0065] In the embodiment of the present application, it is assumed that the resource A does not exist in the standard version, and the user creates the resource A in the customer version, for example, the server generates the customer version data of the resource A according to the instruction of creating the customer version resource.

[0066] Specifically, when the resource list is displayed on the customer version, the newly created customer version resource needs to be displayed in addition to the resource of the standard version. Conversely, when the resource list is displayed on the standard version, only the resource of the standard version needs to be displayed, and the customer version resource does not need to be displayed. Thus, the customization difference of the resources between the standard version and the customer version is embodied.

[0067] In step S103, the target customer version data is generated by copying the standard version data of the resource to be modified according to the instruction of modifying the standard version resource of the customer version.

[0068] The standard version data is the resource data of the resource to be modified which already exists in the standard version, and the target customer version data is the resource data of the resource to be modified which is generated in the customer version.

[0069] In the embodiment of the present application, the customer version shares the standard version data with the standard version, and the customer version does not need to copy all the resource data of the standard version. When a resource or a form needs to be customized and designed, the standard version data of the resource to be modified is copied to generate the target customer version data. At this time, the target customer version data is the exclusive data of the customer version.

[0070] In step S104, the resource with the customer version data is synchronized from the standard version to the customer version according to the synchronization instruction of the standard version upgrade.

[0071] In the embodiment of the present application, the standard version realizes the function optimization and the defect repair through the upgrade. When the upgraded resource has the customer version data, the upgraded standard version data needs to be synchronized to the customer version, and the function optimization and the defect repair of the customer version are completed after the synchronization.

[0072] In summary, the application embodiment provides the application resource determination method, generates the corresponding customer version record according to the customer version creation instruction; the customer version record corresponds to the customer version one by one; generates the customer version data of the resource to be created according to the customer version resource creation instruction; according to the instruction of modifying the standard version resource by the customer version, the target customer version data is generated by copying the standard version data of the resource to be modified; the standard version data is the resource data of the resource to be modified on the standard version; the target customer version data is the resource data generated by the resource to be modified on the customer version; according to the synchronization instruction of the standard version upgrade, the resource existing in the customer version data is synchronized from the standard version to the customer version. The scheme supports the customer version and the standard version to share the resource data, the customer version copies the standard version data of the resource to generate the customer version data according to the customization requirement, and realizes the upgrade synchronization between the customer version and the standard version according to the customization requirement, effectively reduces the data redundancy, reduces the maintenance difficulty and cost, and improves the development efficiency and user experience.

[0073] Optionally, in actual application, according to different customization requirements, the same application or form can create multiple customer versions corresponding thereto. In order to facilitate the management of the customer version, the customer version is identified by the customer version identifier one by one. Figure 2 Based on the above, please refer to Figure 3 The substep of step S101 can include:

[0074] Step S1011 receives the customer version creation instruction.

[0075] The application identifier is included in the customer version creation instruction.

[0076] In the embodiment of the application, it is assumed that the customer version is created for the application, and the user needs to carry the application identifier when issuing the customer version creation instruction, and the application identifier indicates the application to which the customer version belongs. The application identifier is uniformly addressed, which can be an ID or an application name, and the application is not limited thereto.

[0077] Step S1012 allocates the customer version identifier for the customer version to be created.

[0078] In the embodiment of the application, the customer version identifier is uniformly addressed, and the customer version identifier can be an ID or a random number, and the application is not limited thereto.

[0079] Step S1013 generates the corresponding customer version record according to the application identifier and the customer version identifier.

[0080] In the embodiment of the application, for example, the customer information table is used to record the association relationship between the application and the customer version, and the customer information table can determine all customer versions of an application.

[0081] Specifically, when the client version is created, a new client version record is added to the client information table, and the client version record contains the application identifier and the client version identifier, and can also contain the client version name and the description information and other basic attribute information, so as to facilitate the user to browse and view. The specific content of the client version record can be set according to the actual application scene, and the application is not limited.

[0082] It should be noted that when the client version of the application is successfully created, the administrator can configure the access permission for the specified user through the interactive interface or the third party server, and the authorized user can access the client version through the client.

[0083] As an implementation manner, it is assumed that the user access list records the client version of the application last accessed by the user. When the user opens the design interface on the client, in order to facilitate the user to directly access the last client version, the client can query the client version of the application last accessed by the user.

[0084] Specifically, the server obtains the corresponding user use record in the user access list according to the user identifier in the query instruction. The user use record contains the user identifier, the application identifier and the client version identifier, and the user last accessed application client version can be determined according to the application identifier and the client version identifier. Each user is assigned a unique identifier, which is convenient for query and management.

[0085] When the user access record exists, the user access record is sent to the client, and the client can directly access the client version of the application according to the received application identifier and client version identifier. When the server receives the client version access request, the user access record is refreshed according to the user identifier, the application identifier and the client version identifier in the access request.

[0086] When the user use record does not exist, it means that the user is accessing for the first time, and the user can select the application to be accessed on the design interface, and then generate a new user access record according to the user identifier, the application identifier and the client version identifier in the access request, and add the newly generated user access record to the user access list. For the specific access method, the application is not limited.

[0087] After the user enters the client version of the application, the client sends a pull request of the resource list, the server obtains the resource list according to the application identifier and the client version identifier in the pull request, and sends the resource list to the client for display. The user can perform the creation, deletion and modification of the resource on the client.

[0088] As an implementation, assuming that the resource list is stored in a database server, the server sends a request for obtaining the resource list to the database server. The database server obtains the standard version data and the client version data according to the application identifier and the client version identifier, and sends the standard version data and the client version data to the server. When the standard version data and the client version data conflict, the server merges the resource data of the standard version and the client version according to the conflict policy, and sends the merged resource list to the client, and the client displays the latest client version data and the standard version data.

[0089] It should be noted that whether it is client version data is distinguished by the client version identifier, and the client version identifier is added in the client version data, and the standard version data does not add the client version identifier.

[0090] In the embodiment of the application, the conflict policy can be preset by an administrator or a user through a client, and a system default value can also be used. Assuming that the conflict policy can include the following three ways: first, the latest standard version data is used as a reference to cover the client version data; second, the client version data is used as a reference to cover the standard version data; and third, the difference conflict item is displayed, and the user selects which version data to use as a reference. The preset manner of the conflict policy and the manner of solving the conflict are not limited by the application.

[0091] Optionally, in actual application, when the standard version does not exist for a specified resource, the client version resource can be created according to the customization requirement of the client version. Figure 2 On the basis of Figure 4 , the sub-step of step S102 can include:

[0092] Step S1021, receiving a client version resource creation instruction.

[0093] The client version resource creation instruction includes attribute information of the resource to be created and a client version identifier.

[0094] In the embodiment of the application, assuming that a user creates a resource according to the customization requirement of a client, the user needs to carry attribute information of the resource and a client version identifier when issuing a client version resource creation instruction. The attribute information of the resource can include a resource name, description information, a location, a size, a color and the like, which can be selected according to an actual application scenario, and the application is not limited in this regard.

[0095] Step S1022, allocating a resource identifier to the resource to be created.

[0096] In the embodiment of the application, each resource has a corresponding resource identifier for uniquely identifying the resource for ease of management. When a new resource is created, a resource identifier needs to be allocated to the resource to be created, and the resource can be quickly found through the resource identifier subsequently.

[0097] Step S1023: Generate customer version data for the resource to be created based on the resource identifier, customer version identifier, and attribute information.

[0098] In this embodiment of the invention, the customer version identifier is used to distinguish whether a resource belongs to a standard version or a customer version. Standard version resources do not have a customer version identifier, while customer version resources have one. Customer version data for newly created resources is generated based on the resource identifier, customer version identifier, and attribute information.

[0099] Optionally, in practical applications, besides creating new resources on the customer version, more often than not, existing resources on the standard version are modified according to the customer's customized needs. Figure 2 Based on this, please refer to Figure 5 The sub-steps of step S103 may include:

[0100] Step S1031: When the resource to be modified is a standard version resource and there is no customer version data, copy the standard version data to generate snapshot data.

[0101] In this embodiment of the invention, when the resource does not have customer version data, it indicates that the customer version is modifying the resource for the first time, and the standard version data needs to be copied to the customer version to generate the customer version snapshot data.

[0102] Step S1032: Generate target customer version data based on the modification data and snapshot data in the instruction to modify the standard version resource of the customer version.

[0103] In this embodiment of the invention, customer version data is generated based on snapshot data. At this point, the customer version data and the snapshot data are identical. Then, the customer version data is modified according to the modification data in the instruction to obtain the target customer version data. Finally, the snapshot data and the target customer version data constitute a resource data record for the customer version, and the resource data record is saved, for example, by storing the resource data record on a database server.

[0104] As one implementation method, suppose a user needs to modify standard version resources in the client version. First, the design data of the resources is obtained. Then, the user enters the design interface and, according to customization requirements, such as adding or deleting components, or modifying component colors and fonts, the server modifies the resource data of the client version accordingly, ultimately generating the target client version data.

[0105] Optionally, in practical applications, scenarios where the same resource is modified multiple times are quite common. Figure 2 Based on this, please continue to refer to Figure 5 The sub-step of modifying the standard version resource in the customer version in step S103 may also include:

[0106] In step S1033, when the resource to be modified is a standard version resource and there is customer version data, snapshot data, customer version data and the latest standard version data are obtained.

[0107] In the embodiment of the present application, when there is customer version data for a standard version resource, it indicates that the customer has modified the resource. The modification needs to be performed again in combination with the difference between the customer version and the standard version, and therefore, the snapshot data, customer version data and the latest standard version data of the resource need to be obtained.

[0108] In step S1034, target customer version data is generated according to the modification data in the instruction for modifying the standard version resource, the snapshot data, customer version data and the latest standard version data.

[0109] In the embodiment of the present application, the snapshot data, customer version data and the latest standard version data are merged according to the conflict policy to obtain the resource data before modification. The modified resource data, that is, the target customer version data, is generated in combination with the modification data and the resource data.

[0110] It should be noted that when accessing the customer version, the operation of deleting the standard version resource is also included in the creating and modifying operation. Assuming that the user performs the operation of deleting the standard version resource in the customer version, the server generates a resource deletion record according to the resource identifier and customer version identifier included in the deletion instruction, the resource deletion record includes the resource identifier and customer version identifier, and is used to record in which customer versions the resource is deleted. When the customer version displays the resource list, the resources deleted by the customer version are not displayed, but the resources are not actually deleted, and when the resource list of the standard version is accessed, the resources deleted by the customer version are also displayed.

[0111] In the embodiment of the present application, when the user modifies or upgrades the standard version, the customer version and the standard version share the resource data, and therefore, most of the resource data does not need to be synchronized, and only the resource data modified by the customer version needs to be synchronized. During the synchronization process, if the standard version and the customer version conflict, the data is merged according to the conflict policy to obtain the final customer version data.

[0112] It can be seen that the present scheme can automatically merge the difference between the standard version and the customer version according to the customer version and in combination with the conflict policy, thereby completing the automatic upgrade of the standard version to the specified customer version, reducing the maintenance difficulty and cost, and improving the development efficiency.

[0113] In order to more clearly illustrate the application resource determination method provided in the embodiments of the present application, an exemplary description is given.

[0114] As an implementation manner, in the present application, Figure 6For example, the application development process mainly includes three processing stages of client, design end and running end. The client is mainly used for administrators or users to access the design interface for design and development; the design end is mainly used to implement the operation instructions sent by the client; and the running end is mainly used to display the final design results.

[0115] Specifically, the client issues a creation instruction of the application standard version, and the design end creates the application according to the instruction. The user develops and designs the application on the standard version, designs models, interfaces, forms and other resources according to requirements, and generates resource data. When the user completes the development and design on the standard version, the resource data of the application is packaged and exported, and the resource data package is sent to the running end for direct loading and running by the running end.

[0116] It is worth mentioning that when the form design is performed on the standard version, the component can be bound to call the interface, or it can be used as a node in the resource structure to manage the relationship between the form and the calling interface between different versions.

[0117] It should be noted that when the custom design is performed on the client version, the design and development of the client customization requirements can be based on the standard version. First, copy the standard version data to generate a snapshot data and a client version data, and modify the snapshot data and the client version data before the modification. When developing and designing, only the client version data is modified. Thus, the difference between the client version data and the snapshot data is the modified data of the client version customization requirements. Since there are shared resources and exclusive resources between the standard version and the client version, after the design is completed, the standard version data and the client version data need to be merged to obtain the final client version data, and then the final client version data is loaded and run.

[0118] Specifically, there are two ways to export and merge the client version data, one of which is to perform data merging on the design end, and the running end directly loads and runs; the other is to send the unmerged data to the running end by the design end, and the running end loads and merges when loading.

[0119] As an implementation, the application development process is as follows: Figure 7For example, assume that there are three pieces of data of a resource, which are standard version data, snapshot data and customer version data. When a standard version development performs a create, delete or modify operation on the resource, the standard version data of the resource is updated. When a customer version development customizes the resource, the customer version data of the resource is updated. When the customer version data of the resource is merged, the difference between the snapshot data and the customer version data is determined, and the difference is the operation of the customer version on the resource. According to a conflict policy, the difference and the latest standard version data are merged to generate final customer version data. For example, the snapshot data is bdata, the customer version data is cdata, and the latest standard version data is ndata. When the resource is designed for the first time in the customer version, the snapshot data bdata and the customer version data cdata of the current standard version are saved, and bdata and cdata are the same. When the resource is developed in the customer version, only cdata is updated. When the resource is developed in the standard version, only ndata is updated. When the customer version data is queried, the difference between bdata and cdata is determined, and the difference includes the create, modify and delete operations performed on the customer version. The difference is merged into ndata according to the operation type and the conflict policy, and then returned to the front end for rendering.

[0120] It can be seen that the scheme can quickly identify and mark the difference between the standard version and the customer version, render an effect diagram on the front end, and present the effect diagram to a user, thereby improving user experience.

[0121] Based on the same inventive concept, the embodiment of the application further provides an application resource determination device, which is described with reference to Figure 8 The application resource determination device 200 includes a design module 201 and an upgrade module 202.

[0122] The design module 201 is configured to generate a corresponding customer version record according to a create customer version instruction; the customer version record corresponds to the customer version in a one-to-one manner; generate customer version data of a resource to be created according to a create customer version resource instruction; copy standard version data of a resource to be modified to generate target customer version data according to an instruction for modifying the standard version resource by the customer version; the standard version data is resource data of the resource to be modified that already exists on the standard version; and the target customer version data is resource data of the resource to be modified that is generated on the customer version.

[0123] The upgrade module 202 is configured to synchronize a resource with existing customer version data from the standard version to the customer version according to a synchronization instruction for upgrading the standard version.

[0124] It can be seen that the application resource determination device provided by the embodiment of the application generates corresponding customer version records according to the customer version creation instruction; the customer version records correspond to the customer versions one by one; generates customer version data of the resource to be created according to the customer version resource creation instruction; copies standard version data of the resource to be modified to generate target customer version data according to the instruction for modifying the standard version resource by the customer version; the standard version data is resource data of the resource to be modified that already exists on the standard version; the target customer version data is resource data of the resource to be modified that is generated on the customer version; and the resource with the customer version data is synchronized from the standard version to the customer version according to the synchronization instruction for upgrading the standard version. The scheme supports sharing of resource data between the customer version and the standard version, the customer version copies the standard version data of the resource to generate customer version data according to the customization requirement, and the upgrade synchronization between the customer version and the standard version is realized according to the customization requirement, thereby effectively reducing data redundancy, reducing maintenance difficulty and cost, and improving development efficiency and user experience.

[0125] Optionally, the design module 201 is specifically configured to receive a customer version creation instruction; the customer version creation instruction includes an application identifier; a customer version identifier is allocated for the customer version to be created; and corresponding customer version records are generated according to the application identifier and the customer version identifier.

[0126] Optionally, the design module 201 is specifically configured to receive a customer version resource creation instruction; the customer version resource creation instruction includes attribute information of the resource to be created and a customer version identifier; a resource identifier is allocated for the resource to be created; and customer version data of the resource to be created is generated according to the resource identifier, the customer version identifier and the attribute information.

[0127] Optionally, the design module 201 is specifically configured to, when the resource to be modified is a standard version resource and no customer version data exists, copy the standard version data to generate snapshot data; and target customer version data is generated according to modification data in the instruction for modifying the standard version resource by the customer version and the snapshot data.

[0128] Optionally, the design module 201 is specifically configured to, when the resource to be modified is a standard version resource and customer version data exists, acquire snapshot data, customer version data and latest standard version data; and target customer version data is generated according to modification data in the instruction for modifying the standard version resource by the customer version, the snapshot data, the customer version data and the latest standard version data.

[0129] Please refer to Figure 9A block diagram of a server 100 is shown. The server 100 includes a memory 110, a processor 120 and a communication module 130. The memory 110, the processor 120 and the communication module 130 are electrically connected with each other directly or indirectly to realize data transmission or interaction. For example, the elements can be electrically connected with each other through one or more communication buses or signal lines.

[0130] The memory 110 is configured to store programs or data. The memory 110 can be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable read-only memory (EEPROM) and the like.

[0131] The processor 120 is configured to read / write the data or programs stored in the memory 110 and perform corresponding functions. For example, when the computer program stored in the memory 110 is executed by the processor 120, the application resource determination method disclosed in the above embodiments can be realized.

[0132] The communication module 130 is configured to establish a communication connection between the server 100 and other communication terminals through a network and to receive / transmit data through the network.

[0133] It should be understood that, Figure 9 The structure shown is only a structural schematic diagram of the server 100. The server 100 can further include more or less components than those shown in the above embodiments or have a different configuration from that shown in the above embodiments. Figure 9 The components shown in the above embodiments can be realized in hardware, software or a combination thereof. Figure 9 Figure 9 The computer program stored in the computer readable storage medium is executed by the processor 120 to realize the application resource determination method disclosed in the above embodiments.

[0134] The computer program stored in the computer readable storage medium is executed by the processor 120 to realize the application resource determination method disclosed in the above embodiments.

[0135] ​In summary, the application embodiment provides the application resource determination method, device, server and computer readable storage medium, the corresponding customer version record is generated according to the customer version creation instruction;Customer version record and customer version one-to-one;According to the customer version resource creation instruction, the customer version data of the resource to be created is generated;According to the instruction of modifying the standard version resource by the customer version, the target customer version data is copied by the standard version data of the resource to be modified;Standard version data is the resource data that already exists on the standard version of the resource to be modified;Target customer version data is the resource data generated on the customer version of the resource to be modified;According to the synchronization instruction of the standard version upgrade, the resource existing in the customer version data is synchronized from the standard version to the customer version.This scheme supports the sharing of resource data between customer version and standard version, and the customer version generates customer version data by copying the standard version data of the resource according to the customization requirements, and realizes the upgrade synchronization between customer version and standard version according to the customization requirements, effectively reduces the data redundancy, reduces the maintenance difficulty and cost, and improves the development efficiency and user experience.

[0136] In several embodiments provided in the present application, it should be understood that the disclosed apparatus and method can also be implemented by other manners. The apparatus embodiments described above are only schematic, for example, the flowcharts and block diagrams in the drawings show the possible implementation architectures, functions and operations of the apparatus, method and computer program product according to the embodiments of the present application. In this regard, each block in the flowcharts or block diagrams can represent a module, a program segment or a part of code, which contains one or more executable instructions for implementing the specified logic function. It should also be noted that, in some alternative implementation manners, the functions noted in the blocks can also occur in different order from that noted in the drawings. For example, two consecutive blocks can actually be executed substantially in parallel, and sometimes they can be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system for implementing the specified function or action, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0137] In addition, the function modules in each embodiment of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0138] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the parts of the technical solutions that essentially contribute to the prior art or the parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in the various embodiments of the present application. The aforementioned storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0139] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for determining application resources, characterized in that, The method comprises: According to the instruction of creating a customer version, a corresponding customer version record is generated; the customer version record corresponds to the customer version one by one; the customer version shares the resource data of the standard version; According to the instruction of creating a customer version resource, customer version data of the resource to be created is generated; When the resource to be modified is a standard version resource and there is no customer version data, according to the instruction of modifying the standard version resource by the customer version, the standard version data of the resource to be modified is copied to generate target customer version data; the standard version data is the resource data that has existed on the standard version of the resource to be modified; the target customer version data is the resource data generated on the customer version of the resource to be modified; When the resource to be modified is a standard version resource and there is customer version data, according to the modification data in the instruction of modifying the standard version resource by the customer version, the snapshot data corresponding to the resource to be modified, the customer version data and the latest standard version data are used to generate the target customer version data; According to the synchronization instruction of the standard version upgrade, the difference points of the customer version data and the corresponding snapshot data are determined, the difference points and the latest standard version data are merged to generate the final customer version data; the snapshot data is the standard version data copied when the resource is modified for the first time.

2. The application resource determination method of claim 1, wherein, The step of generating a corresponding customer version record according to the instruction of creating a customer version comprises: Receiving the instruction of creating a customer version; the instruction of creating a customer version comprises an application identifier; Allocating a customer version identifier for the customer version to be created; According to the application identifier and the customer version identifier, a corresponding customer version record is generated.

3. The method of claim 1, wherein, The step of generating customer version data of the resource to be created according to the instruction of creating a customer version resource comprises: Receiving the instruction of creating a customer version resource; the instruction of creating a customer version resource comprises attribute information and a customer version identifier of the resource to be created; Allocating a resource identifier for the resource to be created; According to the resource identifier, the customer version identifier and the attribute information, customer version data of the resource to be created is generated.

4. The method of claim 1, wherein, The step of copying the standard version data of the resource to be modified to generate target customer version data according to the instruction of modifying the standard version resource by the customer version comprises: Copying the standard version data to generate snapshot data; According to the modification data in the instruction of modifying the standard version resource by the customer version and the snapshot data, the target customer version data is generated.

5. An application resource determination apparatus characterized by comprising: The device comprises: The design module is configured to generate a corresponding customer version record according to a customer version creation instruction; the customer version record corresponds to the customer version; the customer version shares resource data of a standard version; generate customer version data of a to-be-created resource according to a customer version resource creation instruction; when the to-be-modified resource is a standard version resource and no customer version data exists, copy standard version data of the to-be-modified resource to generate target customer version data according to an instruction for modifying a standard version resource by a customer version; the standard version data is resource data that already exists for the to-be-modified resource on the standard version; the target customer version data is resource data generated for the to-be-modified resource on the customer version; when the to-be-modified resource is a standard version resource and customer version data exists, generate the target customer version data according to modification data in the instruction for modifying a standard version resource by a customer version, snapshot data corresponding to the to-be-modified resource, customer version data, and latest standard version data; The upgrade module is configured to determine difference points of the customer version data and corresponding snapshot data according to a synchronization instruction for standard version upgrade, and merge the difference points and latest standard version data to generate final customer version data; the snapshot data is standard version data copied when a resource is first modified.

6. The application resource determination apparatus of claim 5, wherein The design module is specifically configured to: receive a customer version creation instruction; the customer version creation instruction includes an application identifier; assign a customer version identifier to a to-be-created customer version; generate a corresponding customer version record according to the application identifier and the customer version identifier.

7. The application resource determination apparatus of claim 5, wherein The design module is specifically configured to: receive a customer version resource creation instruction; the customer version resource creation instruction includes attribute information and a customer version identifier of the to-be-created resource; assign a resource identifier to the to-be-created resource; generate customer version data of the to-be-created resource according to the resource identifier, the customer version identifier, and the attribute information.

8. A server, characterized by The server includes a memory and a processor; the memory is configured to store a computer program; the processor is configured to execute the application resource determination method of any one of claims 1-4 when the computer program is invoked.

9. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the application resource determination method of any one of claims 1-4.

Images