DYNAMIC PLUGIN SYSTEM AND METHOD FOR LOW CODE APPLICATION BUILDER
A method of implementing plugins in a low-code application, performed by at least one processor, includes receiving, from a user equipment (UE), parameters defining a first plugin, generating a first package defining the first plugin based on the received parameters, and generating the first plugin based on the first package.
1 . A method of implementing plugins in a low-code application, performed by at least one processor, the method comprising:
receiving, from a user equipment (UE), parameters defining a first plugin;
generating a first package defining the first plugin based on the received parameters; and
generating the first plugin based on the first package.
2 . The method of claim 1 , further comprising:
determining, based on the first package defining the first plugin, whether the first plugin is a new plugin; and
based on determining that the first plugin is a new plugin, adding the first plugin to a list of plugins of the low-code application.
3 . The method of claim 1 , wherein the first package defining the first plugin comprises metadata corresponding to the first plugin.
4 . The method of claim 3 , wherein the metadata comprises at least one of:
at least one dependency corresponding to the first plugin; and
at least one element image of the first plugin.
5 . The method of claim 1 , further comprising:
receiving, from the UE, a selection to preview the first plugin;
generating a preview of the first plugin based on the received selection; and
displaying the preview of the first plugin in a preview window of the low-code application.
6 . The method of claim 1 , further comprising storing metadata corresponding to the first plugin in a memory corresponding to the low-code application based on determining that the first plugin is a new plugin.
7 . The method of claim 6 , further comprising:
receiving, from the UE, a selection to implement the first plugin with the low-code application; and
retrieving, from the memory, the metadata corresponding to the first plugin in response to the received selection.
8 . The method of claim 1 , further comprising:
receiving a request to update the first plugin, the request comprising a second package comprising updated metadata corresponding to the first plugin; and
determining a type of an update to be performed on the first plugin based on the second package.
9 . The method of claim 8 , further comprising, based on determining the type of the update to be a labelling update type, updating a label corresponding to the first plugin.
10 . The method of claim 8 , further comprising, based on determining the type of the update to be an operational update type, replacing, in a memory, previously stored metadata corresponding to the first plugin with the updated metadata corresponding to the first plugin.
11 . A system for implementing plugins in a low-code application comprising:
at least one memory storing instructions; and
at least one processor configured to execute the instructions to:
receive, from a user equipment (UE), parameters defining a first plugin;
generate a first package defining the first plugin based on the received parameters; and
generate the first plugin based on the first package.
12 . The system of claim 11 , wherein the at least one processor is further configured to execute the instructions to:
determine, based on the first package defining the first plugin, whether the first plugin is a new plugin; and
based on determining that the first plugin is a new plugin, add the first plugin to a list of plugins of the low-code application.
13 . The system of claim 11 , wherein the first package defining the first plugin comprises metadata corresponding to the first plugin.
14 . The system of claim 13 , wherein the metadata comprises at least one of:
at least one dependency corresponding to the first plugin; and
at least one element image of the first plugin.
15 . The system of claim 11 , wherein the at least one processor is further configured to execute the instructions to:
receive, from the UE, a selection to preview the first plugin;
generate a preview of the first plugin based on the received selection; and
display the preview of the first plugin in a preview window of the low-code application.
16 . The system of claim 11 , wherein the at least one processor is further configured to execute the instructions to store metadata corresponding to the first plugin in a memory corresponding to the low-code application based on determining that the first plugin is a new plugin.
17 . The system of claim 16 , wherein the at least one processor is further configured to execute the instructions to:
receive, from the UE, a selection to implement the first plugin with the low-code application; and
retrieve, from the memory, the metadata corresponding to the first plugin in response to the received selection.
18 . The system of claim 11 , wherein the at least one processor is further configured to execute the instructions to:
receive a request to update the first plugin, the request comprising a second package comprising updated metadata corresponding to the first plugin; and
determine a type of an update to be performed on the first plugin based on the second package.
19 . The system of claim 18 , wherein the at least one processor is further configured to execute the instructions to, based on determining the type of the update to be a labelling update type, update a label corresponding to the first plugin, and
based on determining the type of the update to be an operational update type, replace, in a memory, previously stored metadata corresponding to the first plugin with the updated metadata corresponding to the first plugin.
20 . A non-transitory computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to:
receive, from a user equipment (UE), parameters defining a first plugin;
generate a first package defining the first plugin based on the received parameters; and
generate the first plugin based on the first package.