Application program updating method and device applied to low-code platform, readable storage medium and program product

Abstract

The embodiment of the invention provides an application program updating method and device applied to a low-code platform, a readable storage medium and a program product, and the method comprises the steps that in response to a received application program updating instruction, a first dependency object of first metadata is determined according to the to-be-updated first metadata selected by a user; obtaining a second metadata set corresponding to the released version of the application program; the second metadata set comprises a plurality of second metadata; combining the first metadata, the first dependent object and the second metadata set to obtain a third metadata set; and updating the application program based on the third metadata set. A scheme for updating the application program by combining the partial updating metadata with the full metadata of the released version of the application program is provided, and the updating efficiency of the application program is improved.

Description

TECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to the technical field of computer, and particularly, to an application program updating method applied to a low-code platform, a device, a readable storage medium and a program product. BACKGROUND

[0002] An application platform as a service (aPaaS) platform provides a good environment for users to develop applications. In the platform, users can develop applications by using a low-code or no-code development method.

[0003] The application programs developed in the aPaaS platform can be maintained, and the application programs are iteratively updated. For example, the metadata of the application programs can be modified or new metadata can be added to the application programs.

[0004] Generally, when the application programs are iteratively updated, a user can edit a new version of the application program in a development environment, and then publish the full data of the new version to the online to complete the update of the application program.

[0005] The inventors find that the existing application program maintenance method cannot perform partial update, which results in low efficiency of the application program update. SUMMARY

[0006] Embodiments of the present disclosure provide an application program updating method applied to a low-code platform, a device, a readable storage medium and a program product.

[0007] In a first aspect, an application program updating method applied to a low-code platform is provided, including: in response to receiving an application program updating instruction, determining a first dependent object of a first metadata to be updated according to a user selection; obtaining a second metadata set corresponding to a published version of the application program; the second metadata set includes a plurality of second metadata; merging the first metadata, the first dependent object and the second metadata set to obtain a third metadata set; and updating the application program based on the third metadata set.

[0008] In a second aspect, the embodiments of the present disclosure provide an application program updating device applied to a low-code platform, comprising: a first determination unit configured to, in response to receiving an application program updating instruction, determine a first dependent object of first metadata to be updated according to user selection; an acquisition unit configured to acquire a second metadata set corresponding to a published version of the application program; the second metadata set comprises a plurality of second metadata; a merging unit configured to merge the first metadata, the first dependent object and the second metadata set to obtain a third metadata set; and an updating unit configured to update the application program based on the third metadata set.

[0009] In a third aspect, the embodiments of the present disclosure provide an electronic device, comprising: a processor and a memory.

[0010] The memory stores computer execution instructions.

[0011] The processor executes the computer execution instructions stored in the memory, so that the at least one processor executes the application program updating method applied to the low-code platform as described in the first aspect and various possible designs of the first aspect.

[0012] In a fourth aspect, the embodiments of the present disclosure provide a computer readable storage medium, wherein the computer readable storage medium stores computer execution instructions, and when a processor executes the computer execution instructions, the application program updating method applied to the low-code platform as described in the first aspect and various possible designs of the first aspect is implemented.

[0013] In a fifth aspect, the embodiments of the present disclosure provide a computer program product, comprising a computer program, and when a processor executes the computer program, the application program updating method as described in the first aspect and various possible designs of the first aspect is implemented.

[0014] The application program updating method, device, readable storage medium and program product applied to the low-code platform provided by the embodiments of the present disclosure, the method comprises: in response to receiving an application program updating instruction, determining a first dependent object of first metadata to be updated according to user selection; acquiring a second metadata set corresponding to a published version of the application program; the second metadata set comprises a plurality of second metadata; merging the first metadata, the first dependent object and the second metadata set to obtain a third metadata set; and updating the application program based on the third metadata set, thereby providing a scheme of updating the application program using part of the metadata combined with the full metadata of the published version of the application program. In the scheme, the application program can run without defects when the application program is updated using local metadata, and the application program updating efficiency is improved. BRIEF DESCRIPTION OF DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present disclosure, and other drawings can be obtained by those of ordinary skill in the art without creative labor under the premise of the drawings.

[0016] Figure 1 The application program updating method flowchart applied to the low-code platform provided by the embodiments of the present disclosure Figure 1 ;

[0017] Figure 2 The application program updating method flowchart applied to the low-code platform provided by the embodiments of the present disclosure Figure 2 ;

[0018] Figure 3 The application program updating method flowchart applied to the low-code platform provided by the embodiments of the present disclosure

[0019] Figure 4 The application program updating method flowchart applied to the low-code platform provided by the embodiments of the present disclosure Figure 3 ;

[0020] Figure 5 The structural block diagram of the application program updating device applied to the low-code platform provided by the embodiments of the present disclosure

[0021] Figure 6 The hardware structure schematic diagram of the electronic device provided by the embodiments of the present disclosure. DETAILED DESCRIPTION

[0022] In order to make the objects, technical solutions and advantages of the embodiments of the present disclosure clearer, the following will combine the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are some of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those of ordinary skill in the art without creative labor fall within the scope of protection of the present disclosure.

[0023] The version update of the application program is usually the whole content of the new update packaged for release. When the application program is large, it needs to be collaboratively developed and maintained by multiple users, that is, different users maintain part of the content of the application program respectively. When different users update different parts of the application program respectively, the application program needs to be released after the parts of other users are all updated and integrated into the whole. In this way, the efficiency of the application program update is low. Therefore, there is a demand for partial update of the application program to improve the efficiency of the application program update. The scheme provided by the present disclosure provides that the application program is updated using partial update metadata combined with the full amount of metadata of the released version of the application program, so that the application program can run without defects when the partial update metadata updates the application program, and the efficiency of the application program update is improved.

[0024] Please refer to Figure 1 , Figure 1 The flowchart of the application program update method applied to the low-code platform provided by the present disclosure is shown in Figure 1 As shown in Figure 1 , the method comprises the following steps:

[0025] S101: In response to receiving an application program update instruction, determining a first dependent object of the first metadata according to the first metadata selected by the user to be updated.

[0026] The execution subject of the application program update method provided by the present embodiment can be a client or a server capable of running the development environment provided by the low-code platform.

[0027] In the low-code platform, the metadata (Metadata) of the application program is data describing how the application program runs, including key data of the structure and behavior of the application program, defining the constituent elements, configuration rules and logical relationships of the application program. The low-code platform usually includes the following metadata: data model, definition of entity (table) and field (name, type, relationship, constraint, etc.), user interface (including page layout, form control, list view, button position, etc.), business logic (workflow, rule, etc.), permission and role including (user role, data access permission (permission control of adding, deleting, modifying and querying), page permission, etc.), and integration configuration, etc.

[0028] The user here can be a developer. In the present embodiment, there can be multiple developers collaboratively maintaining and updating the application program in the development environment.

[0029] Each metadata of the application program can refer to one or more dependent objects, and the dependent object of one metadata can be another metadata.

[0030] For each of the developers who collaboratively maintain the application, the developer can update one or more metadata of the application running online in a development environment. Specifically, the developer can initiate an application update instruction in a maintenance interface of the application, and after initiating the application update instruction, the developer can also select a first metadata to be updated in a presented metadata list. The first metadata here can be a metadata that is modified relative to a second metadata set corresponding to the released version. Here, the modification relative to the second metadata set includes adding new metadata to the second metadata set, or modifying original metadata in the second metadata set.

[0031] The first metadata selected by the developer to be updated includes one or more first metadata.

[0032] After the developer initiates an instruction to update the application according to the one or more first metadata, the execution subject can determine a first dependency object corresponding to the first metadata. The first dependency object here can be a metadata other than the first metadata selected by the developer to be updated. The first dependency object is modified relative to the second metadata set.

[0033] S102: Obtain a second metadata set corresponding to a released version of the application; the second metadata set includes a plurality of second metadata.

[0034] The released application can include the second metadata set, and the second metadata set can include all metadata of the application, which is referred to as second metadata corresponding to the released application. The application can also include dependency relationships between different second metadata, and the dependency relationships between different second metadata can be obtained from the application.

[0035] S103: Merge the first metadata, the first dependency object, and the second metadata set to obtain a third metadata set.

[0036] In some embodiments, the step S103 includes:

[0037] In response to the existence of the identifier of the first metadata in the second metadata set, replacing a target metadata corresponding to the identifier in the second metadata set with the first metadata, and replacing a dependency object of the target metadata with the first dependency object;

[0038] In response to the non-existence of the identifier of the first metadata in the second metadata set, adding the first metadata and the first dependency object to the second metadata set.

[0039] In the application program, each metadata has a unique identifier. The identifier of the metadata can include one or more of numbers, letters, symbols and characters, and is used to distinguish different metadata. When the developer modifies the metadata, the identifier of the metadata does not change.

[0040] In some application scenarios, the identifier of the first metadata exists in the second metadata set, that is, the first metadata is the metadata obtained by modifying the metadata already existing in the second metadata set. In these application scenarios, the target metadata already existing in the second metadata set can be found according to the identifier of the first metadata, and the target metadata is replaced by the first metadata. The dependency object of the target metadata in the second metadata set is found using the identifier of the first dependency object, and the dependency object of the target metadata is replaced by the first dependency object.

[0041] In some application scenarios, the identifier of the first metadata does not exist in the second metadata set, that is, the first metadata is the newly added metadata relative to the second metadata set. If the identifier of the first dependency object also does not exist in the second metadata set, the first metadata and the first dependency object can be added to the second metadata set.

[0042] In some application scenarios, the identifier of the first metadata does not exist in the second metadata set, that is, the first metadata is the newly added metadata relative to the second metadata set. If the identifier of the first dependency object exists in the second metadata set, the first metadata can be added to the second metadata set, and the corresponding dependency object in the second metadata set is replaced by the first dependency object.

[0043] In these embodiments, by using the first metadata or the first dependency object of the first metadata to add or replace the second metadata set, the third metadata set obtained by the above merging can be matched with the current update, and the third metadata set can support the normal operation of the application program.

[0044] S104: updating the application program based on the third metadata set.

[0045] The third metadata set can be sent to the online application program through a preset interface to update the online running application program.

[0046] In this embodiment, in response to receiving the application update instruction, the first dependency object of the first metadata is determined according to the first metadata to be updated selected by the developer; the second metadata set corresponding to the published version of the application program is obtained; the second metadata set includes a plurality of second metadata; the first metadata, the first dependency object and the second metadata set are merged to obtain a third metadata set; and the application program is updated based on the third metadata set. The scheme for updating the application program using part of the update metadata combined with the full metadata of the published version of the application program is provided, and in the scheme, the application program can be defect-free when the application program is updated using the local metadata, and the application program update efficiency when the application program is maintained in the low-code platform is improved.

[0047] Please refer to Figure 2 , Figure 2 The flowchart of the application program update method applied to the low-code platform provided by the present disclosure is shown in Figure 2 As Figure 2 shown, the method comprises steps S203-S205 which are the same as steps S102-S104 shown in Figure 1 , and further comprises the following steps:

[0048] S201: In response to receiving the application update instruction, at least one dependency object of the first metadata is obtained according to the first metadata to be updated selected by the user.

[0049] S202: Analyze whether the at least one dependency object is modified with respect to the second metadata set, and determine the dependency object that is modified as the first dependency object of the first metadata.

[0050] The execution subject of the application program update method provided in this embodiment can be a client or a server capable of running the development environment provided by the low-code platform. Here, the user can be a developer.

[0051] One first metadata can refer to other metadata, which can be referred to as the dependency object of the first metadata.

[0052] The reference relationship of each first metadata to other metadata can be configured and pre-saved when each first metadata is modified. For each first metadata, the information of the corresponding dependency object can be obtained through the above-mentioned reference relationship corresponding to the first metadata.

[0053] After determining the dependency object of each first metadata, it can be analyzed whether the dependency object is modified with respect to the second metadata set.

[0054] In one example, each dependent object can have a modification state identifier, which can be set to a first state identifier after the dependent object is modified with respect to the second meta data set. The modification state identifier of the dependent object can be used to determine whether the dependent object is modified with respect to the second meta data set. Illustratively, the first state identifier can be a version number, or a preset value such as "1".

[0055] In one example, the identifier of the dependent object can be matched with the second meta data set. If the matching is unsuccessful, it can be determined that the dependent object is modified with respect to the second meta data set. If the matching is successful, the data of the matched dependent object from the second meta data set can be compared with the data of the dependent object in the current development environment, and the comparison result can be used to determine whether the dependent object is modified with respect to the second meta data set.

[0056] When the developer wants to update the application using the first meta data, the first dependent objects (modified dependent objects) of the first meta data can be determined and merged with the first meta data and the second meta data set, which can ensure that the application will not be crashed when running after the application is updated using the first meta data.

[0057] For example, a meta data can be a page, and the dependent objects of the page can include one or more first fields in a data table. For example, the content of a second field in the page can refer to the content of the one or more first fields in the data table.

[0058] If the developer modifies the one or more first fields in the data table and also modifies the page, and the developer does not choose to publish the data table when publishing the page, the second field in the page can have no data after the page is updated to the application, or the page can be crashed when running.

[0059] In the embodiment, the at least one dependent object of the first meta data is obtained in response to receiving the application update instruction, and it is determined whether the dependent object is modified with respect to the second meta data set. The modified dependent object is determined as the first dependent object, which can avoid the application update failure caused by the fact that the dependent object of the first meta data is not included in the instruction, and can also avoid the resource consumption caused by the same dependent object being merged.

[0060] In some embodiments, the step S201 includes:

[0061] obtaining the identification of at least one dependent object of the first metadata from a pre-stored reference relationship list, the reference relationship list comprising the identification of a plurality of metadata and the association relationship between the identification of the plurality of metadata and the identification of dependent objects referenced by the plurality of metadata respectively.

[0062] The reference relationship list can be configured by the developer when the first metadata is updated or developed, and the reference relationship list of the metadata configured by the developer can be stored. The reference relationship list comprises the identification of a plurality of metadata and the association relationship between the identification of the plurality of metadata and the identification of dependent objects referenced by the plurality of metadata respectively. When the application program is updated, for each first metadata selected by the developer, the identification of the first metadata is matched with the reference relationship list, the identification of the first metadata is matched in the reference relationship list, and the identification of the dependent object referenced by the first metadata is determined from the reference relationship list according to the association relationship.

[0063] Then, for each dependent object indicated by the identification of the dependent object, it is determined whether the dependent object is modified with respect to the second metadata set.

[0064] By obtaining the information of the dependent object of the first metadata from the reference relationship list, the dependent object of the first metadata can be quickly determined.

[0065] And the step S202 comprises:

[0066] The dependent object not selected by the user in the modified dependent object is determined as the first dependent object.

[0067] If the developer selects the modified dependent object of the first metadata when selecting the first metadata, the modified dependent object of the first metadata has been selected. If the developer does not select the modified dependent object of the first metadata when selecting the first metadata, the developer needs to be prompted to select the dependent object.

[0068] In addition, the selection item of the first dependent object can also be displayed in the development environment interface of the application program for the developer to select.

[0069] In these embodiments, by determining the dependent object not selected by the developer in the modified dependent object of the first metadata as the first dependent object, and merging the first dependent object and the first metadata to be updated with the second metadata set, it is ensured that the modified dependent object dependent on the local metadata is not missed when the application program is updated according to the local metadata. It can be ensured that the updated application layer program can run normally.

[0070] In some embodiments, the method further comprises the following steps:

[0071] First, a partial release control is displayed in a development page of an application, and the partial release control is used to update the application using part of metadata;

[0072] Second, in response to a triggering operation on the partial release control, a first list is displayed, and the first list includes information of at least one modified metadata;

[0073] Finally, in response to a selection operation on at least one of the at least one metadata, a first metadata to be updated is determined.

[0074] The following Figure 3 will be described, Figure 3 with reference to a scenario diagram. A partial release control 31 can be displayed in a development page 30 of an application. When a developer performs a triggering operation on the partial release control 31, a first list 32 can be displayed. The first list 32 includes information of “metadata 1” and information of “metadata 2”, and selection controls of “metadata 1” and “metadata 2”.

[0075] The developer can perform a selection operation on “metadata 1” in the first list, and take “metadata 1” as a first metadata to be updated.

[0076] The above execution subject can determine whether the first metadata to be updated includes a modified dependent object of “metadata 1”, and when it is determined that the first metadata to be updated does not include the modified dependent object of “metadata 1”, take the dependent object as a first dependent object, and display information of the first dependent object. For example, a second list 33 is displayed in the development page, and the second list 33 includes information of the first dependent object of “metadata 1”. As Figure 3 shown, information of the first dependent objects “metadata 3” and “metadata 4” of “metadata 1” is displayed, and selection controls of “metadata 3” and “metadata 4” are provided for the developer to select.

[0077] After the developer performs a selection operation on the first dependent objects “metadata 3” and “metadata 4” of “metadata 1”, an instruction for updating the application using “metadata 1” can be generated.

[0078] In these embodiments, by displaying a partial release control in a development page, an entry for updating an application using part of metadata is provided, and convenience is provided for a developer to update the application using part of metadata.

[0079] Please refer to Figure 4 , Figure 4 a flowchart of an application update method applied to a low-code platform provided by the present disclosure Figure 3 , as Figure 4 shown, the method includesFigure 1 In addition to the steps S101-S103, the steps S401-S403 shown in the embodiment also include the following steps:

[0080] S404: For each third metadata in the third metadata set, checking whether the identifier of the dependent object of the third metadata exists in the third metadata set.

[0081] Since the third metadata set is obtained by merging the second metadata set and the first metadata set, the second metadata set includes all metadata corresponding to the published version of the application program, and there is a reference relationship between these metadata. That is, for each second metadata in the second metadata set, the dependent object of the second metadata also exists in the second metadata set.

[0082] The first metadata in the first metadata set is the metadata updated by the developer, and the first dependent object is the updated metadata of the existing metadata in the second metadata set or newly added metadata. In order to ensure that the dependent object of each third metadata in the third metadata set obtained in step S403 exists in the third metadata set, the integrity of the dependent object of each third metadata in the third metadata set needs to be checked.

[0083] S405: In response to the identifier of the dependent object of each third metadata existing in the third metadata set, updating the application program using the third metadata set.

[0084] In the embodiment, by checking the dependent object of each third metadata in the third metadata set, the application program is updated using the third metadata set after the checking is successful, so that the updated application program can run normally.

[0085] In some embodiments, the method further includes: in response to the identifier of the dependent object of any third metadata not existing in the third metadata set, displaying first prompt information, the first prompt information indicating that the application program cannot be updated by the first metadata set.

[0086] In these setting modes, when the dependent object of any one third metadata in the third metadata set does not exist, the above-mentioned first prompt information can be displayed. The developer can be informed in time about the information and reason why the application program cannot be updated, and the developer can conveniently configure the dependent object for the first metadata in time.

[0087] The application program updating method applied to the low-code platform corresponding to the above-mentioned embodiment, Figure 5 A structural block diagram of an application program updating device applied to a low-code platform is provided in the embodiment of the disclosure. For ease of illustration, only parts related to the embodiment of the disclosure are shown. For parts not shown, refer to the description of the prior art. Figure 5The application program updating device 50 applied to the low-code platform comprises a first determining unit 501, an obtaining unit 502, a merging unit 503 and an updating unit 504.

[0088] wherein,

[0089] The first determining unit 501 is configured to, in response to receiving an application program updating instruction, determine a first dependency object of the first metadata according to the first metadata selected by a user to be updated.

[0090] The obtaining unit 502 is configured to obtain a second metadata set corresponding to a released version of the application program, wherein the second metadata set comprises a plurality of second metadata.

[0091] The merging unit 503 is configured to merge the first metadata, the first dependency object and the second metadata set to obtain a third metadata set.

[0092] The updating unit 504 is configured to update the application program based on the third metadata set.

[0093] The application program updating device 50 applied to the low-code platform comprises a first determining unit 501, an obtaining unit 502, a merging unit 503 and an updating unit 504.

[0094] In an embodiment of the present disclosure, the merging unit 503 is further configured to merge the first metadata, the first dependency object and the second metadata set to obtain the third metadata set based on at least one of the following:

[0095] in response to the identifier of the first metadata existing in the second metadata set, replacing target metadata corresponding to the identifier in the second metadata set with the first metadata, and replacing a dependency object of the target source data with the first dependency object;

[0096] in response to the identifier of the first metadata not existing in the second metadata set, combining the first metadata and the first dependency object.

[0097] In an embodiment of the present disclosure, the first determining unit 501 is further configured to:

[0098] acquire at least one dependent object of the first metadata;

[0099] determine the dependent object that is modified as a first dependent object of the first metadata.

[0100] In summary, further, by responding to receiving the application program update instruction, acquiring at least one dependent object of the first metadata according to the first metadata selected by the user to be updated, and determining the modified dependent object as the first dependent object, on the one hand, the application program update failure caused by the dependent object of the first metadata not included in the instruction can be avoided, and on the other hand, the resource consumption caused by the same dependent object being merged can be avoided. In an embodiment of the present disclosure, the first determining unit 501 is further configured to: acquire the identifier of the at least one dependent object of the first metadata from a pre-stored reference relationship list; the reference relationship list includes the identifiers of a plurality of metadata and the association relationship between the identifiers of the dependent objects referenced by the plurality of metadata respectively;

[0101] determine the dependent object that is not selected by the user in the modified dependent object as the first dependent object.

[0102] In summary, further, by acquiring the information of the dependent object of the first metadata from the reference relationship list, the dependent object of the first metadata can be quickly determined.

[0103] In an embodiment of the present disclosure, the updating unit 504 is further configured to:

[0104] for each third metadata in the third metadata set, check whether the identifier of the dependent object of the third metadata exists in the third metadata set;

[0105] in response to the identifier of the dependent object of each third metadata existing in the third metadata set, update the application program using the third metadata set.

[0106] In summary, further, by checking the dependent object of each third metadata in the third metadata set, and updating the application program using the third metadata set after the checking is successful, the updated application program can be normally run.

[0107] In an embodiment of the present disclosure, the updating unit 504 is further configured to:

[0108] in response to the identifier of the dependent object of any third metadata not existing in the third metadata set, display a first prompt information, the first prompt information indicating that the application program cannot be updated by the first metadata set.

[0109] In one embodiment of the present disclosure, the device 50 further comprises a second determining unit (not shown in the figure), configured to:

[0110] display a partial release control in a development page of the application program, the partial release control being configured to update the application program using part of the metadata;

[0111] in response to a triggering operation on the partial release control, display a first list comprising an identification of at least one piece of modified metadata;

[0112] in response to a selection operation performed on the identification of at least one piece of metadata, determine the first piece of metadata to be updated.

[0113] To implement the above-mentioned embodiments, the present disclosure further provides an electronic device.

[0114] Reference Figure 6 , which shows a structural schematic diagram of an electronic device 600 suitable for implementing the embodiments of the present disclosure. The electronic device 600 can be a terminal device or a server. The terminal device can include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, personal digital assistants (PDA), tablet computers, portable multimedia players (PMP), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), and the like, and fixed terminal devices such as digital TVs, desktop computers, and the like. Figure 6 The electronic device shown is only an example and should not impose any limitation on the functions and use range of the embodiments of the present disclosure.

[0115] As shown in Figure 6 , the electronic device 600 can include a processing device (such as a central processor, a graphics processor, etc.) 601, which can perform various appropriate actions and processes according to programs stored in a read-only memory (ROM) 602 or loaded into a random access memory (RAM) 603 from a storage device 608. Various programs and data required for the operation of the electronic device 600 are also stored in the RAM 603. The processing device 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0116] In general, the following devices can be connected to the I / O interface 605: input devices 606 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, and the like; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage devices 608 including, for example, a magnetic tape, a hard disk, and the like; and communication devices 609. The communication devices 609 can allow the electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 The electronic device 600 is shown with various devices, but it is understood that all of the illustrated devices are not required to implement or have the electronic device. More or less devices can alternatively be implemented or have.

[0117] In particular, the processes described above with reference to the flowcharts can be implemented as a computer software program according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for executing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network through the communication devices 609, or installed from the storage devices 608, or installed from the ROM 602. When the computer program is executed by the processing devices 601, the above-mentioned functions defined in the methods of the embodiments of the present disclosure are performed.

[0118] It should be noted that the computer-readable storage medium described above in the present disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. The computer-readable storage medium may, for example, but is not limited to, be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any combination thereof. More specific examples of the computer-readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, the computer-readable signal medium can include a data signal that propagates in a baseband or as part of a carrier wave, carrying computer-readable program code. Such a propagated data signal can take on many forms, including but not limited to, an electromagnetic signal, an optical signal, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable storage medium that is not a computer-readable storage medium and that can send, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable storage medium can be transmitted by any suitable medium, including but not limited to, wire, cable, RF (radio frequency), or the like, or any suitable combination thereof.

[0119] The computer-readable storage medium described above can be included in the electronic device described above; or can exist separately from the electronic device and be not assembled in the electronic device.

[0120] The computer-readable storage medium described above carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods shown in the embodiments described above.

[0121] Computer program code for carrying out operations of the present disclosure can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0122] The computer program instructions can also be loaded onto a computer or other programmable information processing apparatus to cause a series of operations to be performed on the computer or other programmable information processing apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable information processing apparatus implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0123] The units described in the embodiments of the present disclosure can be implemented by hardware, software, or a combination thereof. In some cases, the names of the units do not constitute a limitation on the units themselves. For example, the first obtaining unit can also be described as a unit that obtains at least two Internet protocol addresses.

[0124] The functions described in this specification can be performed at least in part by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.

[0125] The electronic device, the computer readable storage medium and the computer program product provided by the embodiments of the present disclosure determine a first dependency object of the first metadata according to the selected first metadata to be updated in response to receiving the application program update instruction, obtain a second metadata set corresponding to the published version of the application program, the second metadata set includes a plurality of second metadata, merge the first metadata, the first dependency object and the second metadata set to obtain a third metadata set, and update the application program based on the third metadata set. The scheme for updating the application program by using part of the update metadata in combination with the full metadata of the published version of the application program is provided, and in the scheme, the application program can be defect-free when the application program is updated using local metadata, and the application program update efficiency is improved.

[0126] The above description is merely the preferred embodiments of the present disclosure and the explanation of the applied technical principles. Those skilled in the art should understand that the disclosed range of the present disclosure is not limited to the technical solutions formed by the specific combinations of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the disclosed concept. For example, the technical solutions formed by replacing the above features with the technical features disclosed in the present disclosure (but not limited to) having similar functions.

[0127] In addition, although each operation is described in a particular order, this should not be understood as requiring the operations to be performed in the specific order shown or in a sequential order. In certain circumstances, multi-tasking and parallel processing can be advantageous. Similarly, although several implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Certain features described in the context of separate embodiments can also be combined in a single embodiment. Conversely, various features described in the context of a single embodiment can also be separated and implemented in multiple embodiments.

[0128] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. An application update method applied to a low-code platform, characterized in that: include: In response to receiving the application update instruction, determining a first dependent object of the first metadata according to the first metadata to be updated selected by the user; Obtaining a second metadata set corresponding to the published version of the application; The second metadata set includes a plurality of second metadata; Merging the first metadata, the first dependent object, and the second metadata set to obtain a third metadata set; The application is updated based on the third metadata set.

2. The method according to claim 1, characterized in that The merging of the first metadata, the first dependent object, and the second metadata set to obtain a third metadata set includes at least one of the following: In response to the identifier of the first metadata being present in the second metadata set, replacing target metadata corresponding to the identifier in the second metadata set with the first metadata, and replacing a dependent object of the target source data with the first dependent object; In response to the identification of the first metadata not being present in the second metadata set, the first metadata and the first dependent object are added to the second metadata set.

3. The method according to claim 1 or 2, characterized in that The step of determining, in response to receiving the application update instruction, a first dependent object of the first metadata according to the first metadata to be updated selected by the user, includes: Acquire at least one dependent object of the first metadata; Analyze whether the at least one dependent object has been modified relative to the second metadata set, and determine the modified dependent object as the first dependent object of the first metadata.

4. The method according to claim 3, characterized in that The obtaining of at least one dependent object of the first metadata includes: Obtaining an identifier of at least one dependent object of the first metadata from a pre-stored reference relationship list; the reference relationship list includes association relationships between identifiers of multiple metadata and identifiers of dependent objects referenced by the multiple metadata; and determining the modified dependent object as the first dependent object of the first metadata, further comprising: Determine the dependent objects that have been modified and are not selected by the user as the first dependent objects.

5. The method according to any one of claims 1 to 4, characterized in that The updating of the application based on the third metadata set includes: For each piece of third metadata in the third metadata set, verify whether an identifier of a dependent object of the third metadata exists in the third metadata set; In response to the identifier of the dependent object of each of the third metadata being present in the third metadata set, the application is updated using the third metadata set.

6. The method according to claim 5, characterized in that The method further comprises: In response to the identifier of the dependent object of any of the third metadata not being in the third metadata set, first prompt information is displayed, where the first prompt information indicates that the application cannot be updated using the first metadata set.

7. The method according to claim 1, characterized in that The method further comprises: Displaying a partial publishing control on a development page of the application, wherein the partial publishing control is used to update the application using part of the metadata; In response to a triggering operation on the local publishing control, displaying a first list including an identification of at least one modified metadata; In response to a selection operation performed on an identification of at least one metadata among the at least one metadata, the first metadata to be updated is determined.

8. An application update device applied to a low-code platform, characterized in that: include: a first determining unit configured to, in response to receiving an application update instruction, determine a first dependent object of the first metadata according to the first metadata to be updated selected by the user; an acquiring unit, configured to acquire a second metadata set corresponding to a published version of the application; The second metadata set includes a plurality of second metadata; a merging unit, configured to merge the first metadata, the first dependent object, and the second metadata set to obtain a third metadata set; An updating unit is configured to update the application based on the third metadata set.

9. An electronic device, characterized in that: include: processor and memory; The memory stores computer-executable instructions; The processor executes the computer execution instructions stored in the memory, so that the processor executes the application update method applied to the low-code platform as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer execution instructions. When the processor executes the computer execution instructions, the application update method applied to the low-code platform as described in any one of claims 1 to 7 is implemented.

11. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, it implements the application update method applied to a low-code platform as described in any one of claims 1 to 7.

Images