CN115826963A - Process event development multiplexing method and system based on low-code development platform - Google Patents
Process event development multiplexing method and system based on low-code development platform Download PDFInfo
- Publication number
- CN115826963A CN115826963A CN202211638771.4A CN202211638771A CN115826963A CN 115826963 A CN115826963 A CN 115826963A CN 202211638771 A CN202211638771 A CN 202211638771A CN 115826963 A CN115826963 A CN 115826963A
- Authority
- CN
- China
- Prior art keywords
- event
- component
- page
- model
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Stored Programmes (AREA)
Abstract
The invention relates to the technical field of computers, in particular to a flow event development multiplexing method based on a low-code development platform, which comprises the following steps: establishing an event flow through a flow model, and setting corresponding required event data at different flow nodes after associating corresponding forms; acquiring page metadata of a server through a related form, and storing the data in a storage model; the beneficial effects are that: the flow event development multiplexing method and system based on the low-code development platform, which are provided by the invention, add identification ID rule variables capable of being calculated and managed to conventional metadata of a design flow, so that the original static metadata has the characteristic of dynamic use, and provide basic support for multiplexing rendering and event isolation operation of all components in a flow example by combining a page metadata example, a component event script example and a calling API method which are generated by a back-end rendering flow model and a view model.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a system for developing and multiplexing a flow event based on a low-code development platform.
Background
The Low Code Development Platform (LCDP) is a development platform that can quickly generate an application without encoding (0 code) or with a small amount of code. The method for developing the application program through visualization (referring to a visual programming language) enables developers with different experience levels to create web pages and mobile application programs through a graphical user interface by using a dragging component and model-driven logic.
In the prior art, there are many low code platforms in the industry. Low-code platforms frequently appear in applications in the Internet industry to reduce development cost and realize effective cost reduction of enterprises.
However, in practical research, most low-code platforms can only perform simple logic function configuration on each component on an application page in a specific scene, and cannot flexibly configure complex functions of multiple logic actions according to the application scene to realize interactive configuration among multiple components.
Disclosure of Invention
The invention aims to provide a method and a system for developing and multiplexing process events based on a low-code development platform, so as to solve the problems in the background technology.
In order to achieve the purpose, the invention provides the following technical scheme: the process event development and multiplexing method based on the low-code development platform comprises the following steps:
s1, establishing an event flow through a flow model, and setting corresponding required event data at different flow nodes after associating corresponding forms;
s2, acquiring page metadata of the server through the associated form, and storing the data in a storage model;
s3, triggering an event corresponding to the process node according to the process node required by the user to obtain event data;
and S4, interacting according to the event process instance correlation form.
Preferably, the step S1 includes the following sub-steps:
s11, selecting a designated flow node type based on components in a flow model component library, and establishing a flow instance in a dragging mode;
s12, configuring event node types and event data of the components based on the components of the process model to obtain an event process; the event node type comprises a component identification ID, authority information for establishing an event flow and corresponding event data, and each component metadata comprises the identification ID, the component type, a style definition, an attribute definition, an event definition and a method definition; the component type is used for associating a packaged component template to perform data binding rendering, the style defines a rendering style script for defining the component, and the event definition defines a linkage operation event which can be triggered by the component; the method defines a built-in processing callback method for defining the component.
Preferably, the step S2 includes the following sub-steps:
s21, calling a rear-end storage model instance according to the page table unit data to generate a data storage instance, wherein the generated page metadata storage instance is provided with a rendering batch number, and the generation method specifically comprises the following steps: processing the ID of the page metadata through a rear-end rendering storage model to generate a storage instance ID;
s22, calling a view model according to the page data storage example to generate a page view; and according to the components in the page metadata example, designating the rendered components through the view model, and dynamically binding the component metadata corresponding to the designated rendered components with the component template to generate the page view.
Preferably, the step S3 specifically includes:
and triggering the assembly binding event based on the fact that a user needs to use a specified page view, acquiring a rendering batch number of page metadata, and calling the rendering batch number and the process instance ID through a rear-end rendering service module to perform event script query to obtain an event script instance.
Preferably, the step S4 specifically includes:
s41, triggering a page interaction event according to an event script example, and calling a view model to request a page view which is used in a correlation manner;
s42, storing the used form page metadata examples of the model through the front end; and returning the storage model instance ID in the page metadata;
s43, determining a component corresponding to the ID in the event script according to the returned ID of the storage model instance, backfilling page data according to a mounting method for data interaction of the determined component, and realizing data interaction of the page view;
in step S4, the mounting method of data interaction specifically includes:
acquiring a data mount KEY value, creating an interactive mount object, caching the mount object on a root instance object of an AWS root container component, issuing the mount object as a KEY value subject message to an interactive component embedded in a page, and judging whether the interactive component is created or not;
if yes, immediately executing a mount interaction method according to the KEY value theme message received by the interaction component, and updating the executed identification state;
and if not, asynchronously initializing and creating the interactive component, acquiring a data mount KEY value of the interactive component, inquiring a mount object cached on a root instance object of the AWS root container component, executing a mount interactive method when the mount object exists, and updating the executed identification state.
A flow event development and reuse system based on a low-code development platform is composed of a flow model, a storage model and a view model;
the process model is used for designing an event execution process;
the storage model is used for storing the metadata in the form in the process;
and the view model is used for rendering the page layout.
Preferably, the view model is specifically a low-code development platform, which is provided with a view page component library and a deployment end; the view page component library comprises a plurality of components.
Preferably, the deployment end comprises a back-end rendering service module and a front-end rendering framework.
Preferably, the back-end rendering service module is configured to generate an instance of the page metadata and a rendering batch number.
Preferably, the front-end rendering framework is used for rendering the instances of the page metadata and the component templates into a page view.
Compared with the prior art, the invention has the beneficial effects that:
the flow event development multiplexing method and system based on the low code development platform, which are provided by the invention, add identification ID rule variables capable of being calculated and managed to conventional metadata of a design flow, so that the original static metadata has the characteristic of dynamic use, and provide basic support for multiplexing rendering and event isolation operation of all components in a flow example by combining a page metadata example, a component event script example and a calling API method which are generated by a back-end rendering flow model and a view model, and can realize flexible multiplexing interaction of the flow example in the low code development platform; by carrying out event interaction on the process instance, the general flexibility of the process event data model can be enhanced, the structure of the whole process is not overstaffed any more, the management and maintenance become simpler, and the design requirements of more system functions can be met.
Drawings
FIG. 1 is a system framework diagram of the present invention;
FIG. 2 is a flow chart of the method of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clear and fully described, embodiments of the present invention are further described in detail below with reference to the accompanying drawings. It is to be understood that the specific embodiments described herein are merely illustrative of some embodiments of the invention and are not limiting of the invention, and that all other embodiments obtained by those of ordinary skill in the art without the exercise of inventive faculty are within the scope of the invention.
Example one
The invention provides a technical scheme that: the process event development and multiplexing method based on the low-code development platform comprises the following steps:
s1, establishing an event flow through a flow model, and setting corresponding required event data at different flow nodes after associating corresponding forms;
s11, selecting a designated process node type based on components in the process model component library, and establishing a process instance in a dragging mode;
s12, configuring event node types and event data of the components based on the components of the process model to obtain an event process; the event node type comprises a component identification ID, authority information for establishing an event flow and corresponding event data, and each component metadata comprises the identification ID, the component type, a style definition, an attribute definition, an event definition and a method definition; the component type is used for associating a packaged component template to perform data binding rendering, the style defines a rendering style script for defining the component, and the event definition defines a linkage operation event which can be triggered by the component; the method defines a built-in processing callback method for defining the component;
s2, acquiring page metadata of the server through the associated form, and storing the data in a storage model;
s21, calling a rear-end storage model instance according to the page table unit data to generate a data storage instance, wherein the generated page metadata storage instance is provided with a rendering batch number, and the generation method specifically comprises the following steps: processing the ID of the page metadata through a rear-end rendering storage model to generate a storage instance ID;
s22, calling a view model according to the page data storage example to generate a page view; according to the components in the page metadata example, designating the rendered components through a view model, and dynamically binding the component metadata corresponding to the designated rendered components with a component template to generate a page view;
s3, triggering an event corresponding to the process node according to the process node required by the user to obtain event data; triggering a component binding event based on the fact that a user needs to use a specified page view, acquiring a rendering batch number of page metadata, and calling the rendering batch number and a process instance ID through a rear-end rendering service module to perform event script query to obtain an event script instance;
s4, interacting according to the event process instance correlation form;
s41, triggering a page interaction event according to an event script example, and calling a view model to request a page view which is used in a correlation manner;
s42, storing the used form page metadata examples of the model through a front end; and returning the storage model instance ID in the page metadata;
s43, determining a component corresponding to the ID in the event script according to the returned ID of the storage model instance, backfilling page data according to a mounting method for data interaction of the determined component, and realizing data interaction of the page view;
in step S4, the mounting method of data interaction specifically includes:
acquiring a data mount KEY value, creating an interactive mount object, caching the mount object on a root instance object of an AWS root container component, issuing the mount object as a KEY value subject message to an interactive component embedded in a page, and judging whether the interactive component is created or not;
if yes, immediately executing a mount interaction method according to the KEY value theme message received by the interaction component, and updating the executed identification state;
and if not, asynchronously initializing and creating the interactive component, acquiring a data mount KEY value of the interactive component, inquiring a mount object cached on a root instance object of the AWS root container component, executing a mount interactive method when the mount object exists, and updating the executed identification state.
Example two
Referring to fig. 1, on the basis of the first embodiment, in order to implement a flow event development and multiplexing system based on a low-code development platform, the flow event development and multiplexing system is composed of a flow model, a storage model and a view model;
the process model is used for designing an event execution process;
the storage model is used for storing the metadata in the form in the process;
the view model is used for page layout rendering, and is specifically a low-code development platform which is provided with a view page component library and a deployment end; the view page component library comprises a plurality of components, and the deployment end comprises a back-end rendering service module and a front-end rendering frame; the back-end rendering service module is used for generating an example of page metadata and a rendering batch number; the front-end rendering framework is used to render instances of the page metadata and component templates into a page view.
EXAMPLE III
The embodiment is directed to a method for multiplexing process event development based on a low-code development platform. As shown in fig. 2, a method for multiplexing process event development based on a low-code development platform includes the following steps: s1, establishing an event flow through a flow model, and setting corresponding required event data at different flow nodes after associating corresponding forms; s2, acquiring page metadata of the server through the associated form, and storing the data in a storage model; s3, triggering an event corresponding to the process node according to the process node required by the user to obtain event data; and S4, interacting according to the event process instance correlation form. The step S1 comprises the following sub-steps: s11, selecting a designated flow node type based on components in a flow model component library, and establishing a flow instance in a dragging mode;
s12, configuring event node types and event data of the components based on the components of the process model to obtain an event process; the event node type comprises a component identification ID, authority information for establishing an event flow and corresponding event data, and each component metadata comprises the identification ID, the component type, a style definition, an attribute definition, an event definition and a method definition; the component type is used for performing data binding rendering by associating with a packaged component template, the style definition is used for defining a rendering style script of the component, and the event definition is used for defining linkage operation events which can be triggered by the component; the method defines a built-in processing callback method for defining the component. In this embodiment, when a user designs a management system page, a design page needs to be newly built in a data file directory of a visual design end, and after the design page is opened, a suitable component is selected for drag design. When a user designs a data table with an expansion row, a table component needs to be dragged and placed in a design page, and the attribute of a table column object needs to be configured. When a user designs a new adding/editing button and clicks and pops up an external dialog box to maintain a form information interface, the new adding/editing button needs to be dragged and placed in a main operation page, and then the form information content is designed in a dialog box design page independently. S12, configuring metadata of a component based on a view model page to obtain page metadata; the page metadata comprises a view model identification ID and all component metadata for establishing a view page, wherein each component metadata comprises the view model identification ID, a component type, a style definition, an attribute definition, an event definition and a method definition; the view model identification ID of the page metadata can keep that the rendering batch number is globally unique when the whole page is multiplexed, so that any sub-component in the page can quickly acquire the root page object rendered in the same batch. The UUID in the view identification ID is used for keeping the component to be globally unique during dragging design, and the separator is used for acquiring a rendering batch number and distinguishing the component when the front end performs rendering processing. The view model identifier of the invention is used for keeping the rendering batch number globally unique when the whole page is multiplexed, the view identifier is used for keeping the UUID globally unique when the component is dragged, and the separator is used for acquiring the rendering batch number and distinguishing the component when the front end performs rendering processing. And the page root container identification ID is only the rendering batch number, so that any sub-component in the page can quickly acquire the process model instance object rendered in the same batch. In this embodiment, when a process system page is configured, a metadata attribute of a menu item of a node menu component needs to be configured, the metadata attribute is bound with a node menu component template and displayed as a node menu selection item, then a node menu item selection event of the menu component continues to be configured, a user-defined method for adding a tab to a public new tab is called in a processing script of the event, and a page address of a selected node menu item dynamically requests to generate a metadata instance and renders the metadata instance to be displayed in a corresponding tab area. When a data form with an expansion row is configured, a multiplexing process expanded by a form component row is embedded into a detailed information page with address attributes independently designed in advance, then a form row expansion event is configured, a data interaction processing script embedded into the multiplexing process is defined, the processing script traverses all table element component identifications ID in the expanded detailed page, and then assignment and backfill data operation are carried out on the table element components by referring to a self-defined data mounting method.
Configuring a click event script of a button assembly when a newly added/edited button is configured to click and pop up an external dialog box to maintain a form information interface, defining and popping up an independently designed target form page in the script to execute the step, adding event execution logic before popup window triggering, and backfilling and assigning values to newly added/edited form data when the form internal assembly is initialized by calling a flow data mounting and rendering method; and then, configuring a click event of a submission button in the dialog box form, adding a step script for calling a service interface to process form data, and caching interface request return data into step variables. The step S2 comprises the following sub-steps:
s21, calling a rear-end storage model instance according to the page table unit data to generate a data storage instance;
and S22, calling the view model according to the page data storage example to generate a page view. In step S21, the generated page metadata storage instance is provided with a rendering batch number, and the generating method specifically includes: processing the ID of the page metadata through a rear-end rendering storage model to generate a storage instance ID; the step S22 specifically includes: and according to the components in the page metadata example, designating the rendered components through the view model, and dynamically binding the component metadata corresponding to the designated rendered components with the component template to generate the page view. In this embodiment, the main page has already called the backend service to uniformly generate rendering batch numbers of all component view model identification IDs during rendering (excluding the multiplexed sub-process), and also needs to call the backend service to generate the rendering batch numbers of the sub-process when the multiplexed rendering sub-process is used. The steps of multiplexing the rendering sub-processes are as follows: accessing a home page address; requesting a homepage surface element data template; returning a page metadata instance of the main page rendering batch number and rendering; requesting to render a sub-page metadata instance; and returning the page metadata instance of the sub-page rendering batch number and rendering. The step S22 specifically includes: and according to the components in the page metadata example, designating the rendered components through the view model, and dynamically binding the component metadata corresponding to the designated rendered components with the component template to generate the page view. The usage of the view model is as follows: rendering a meta-component as a dynamic component, and determining that a component is rendered according to the is value; the is value is a string that can be either the HTML tag name or the component name. The step S3 specifically comprises the following steps: and triggering the assembly binding event based on the fact that a user needs to use a specified page view, acquiring a rendering batch number of page metadata, and calling the rendering batch number and the process instance ID through a rear-end rendering service module to perform event script query to obtain an event script instance. . In this embodiment, the method for triggering the main page data list row expansion event includes: the method comprises the following steps that a user triggers a line expansion event bound by a data list, a back-end service request line is called to expand a related multiplexing sub-process, a front end renders a sub-process metadata example of the multiplexing (after the front end rendering is finished, all related component objects can be cached and managed so as to be used by obtaining view identification IDs of component metadata later, a back-end service request line is called to expand a defined event script, and a front end declares an event script example of a data list rendering batch (when an event definition calling component method is arranged in a main page, only components belonging to the same batch can be operated, and view model identification ID rendering batch numbers of component reference page metadata in the event script need to be synchronously updated).
S41, triggering a page interaction event according to an event script example, and calling a view model to request a page view which is used in a correlation manner;
s42, storing the used form page metadata examples of the model through a front end; and returning the storage model instance ID in the page metadata;
s43, determining a component corresponding to the ID in the event script according to the returned storage model instance ID, and backfilling page data according to a mounting method for data interaction of the determined component to realize data interaction of the page view. In step S4, the mounting method of data interaction specifically includes: acquiring a data mount KEY value, creating an interactive mount object, caching the mount object on a root instance object of an AWS root container component, issuing the mount object as a KEY value subject message to an interactive component embedded in a page, and judging whether the interactive component is created or not; if yes, immediately executing a mount interaction method according to the KEY value theme message received by the interaction component, and updating the executed identification state; and if not, asynchronously initializing and creating the interactive component, acquiring a data mount KEY value of the interactive component, inquiring a mount object cached on a root instance object of the AWS root container component, executing a mount interactive method when the mount object exists, and updating the executed identification state. The data interaction method for the data table with the development rows comprises the following specific steps: and carrying out data backfill processing on the detailed information page in the event script of the line expansion of the table, calling a rear-end rendering service module to obtain a page metadata example corresponding to the expanded page address in the event, transmitting the example data to the event script as a JSON parameter, so that a user can traverse all component view identification ID information of the detailed information page and table line data object attribute values associated with the components, and processing backfill assignment of the components in the detailed information page by calling a page data mounting method. The data interaction method for maintaining the form information interface by clicking and popping up the external dialog box by the newly added/edited button specifically comprises the following steps: when the new adding/editing button pops up an external public dialog box, if data of a main page need to be transmitted, interaction needs to be carried out through a data mounting method, the whole AWS root container component of the main page is taken as a father container component of the external dialog box embedded page by default, and the view identification ID of the root container component of the main page is embedded into the UUID suffix of the interactive component. When the event script triggers the data mounting method, the view identification ID of the direct father container component of the mounting point is transmitted to the father container component instance object, the mounting KEY value temporarily stored by the father container component object is obtained to serve as an iterative service data KEY value, the transmitted UUID suffix of the embedded interactive component is intercepted, and the data mounting KEY value is generated.
By adding identification ID rule variables which can be calculated and managed to conventional metadata of a design flow, the original static metadata has the characteristic of dynamic use, and by combining a page metadata instance, a component event script instance and a calling API method which are generated by a back-end rendering flow model and a view model, basic support is provided for multiplexing rendering and event isolation operation of all components in a flow instance, and flexible multiplexing interaction of the flow instance can be realized in a low-code development platform. According to the invention, by carrying out event interaction on the process instance, the general flexibility of the process event data model can be enhanced, the structure of the whole process is not too bloated, the management and maintenance become simpler, and the design requirements of more system functions can be met.
Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that changes, modifications, substitutions and alterations can be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.
Claims (10)
1. The process event development and multiplexing method based on the low-code development platform is characterized by comprising the following steps of:
s1, establishing an event flow through a flow model, and setting corresponding required event data at different flow nodes after associating corresponding forms;
s2, acquiring page metadata of the server through the associated form, and storing the data in a storage model;
s3, triggering an event corresponding to the process node according to the process node required by the user to obtain event data;
and S4, interacting according to the event process instance correlation form.
2. The method for multiplexing process event development based on the low-code development platform according to claim 1, wherein the step S1 comprises the following substeps:
s11, selecting a designated flow node type based on components in a flow model component library, and establishing a flow instance in a dragging mode;
s12, configuring event node types and event data of the components based on the components of the process model to obtain an event process; the event node type comprises a component identification ID, authority information for establishing an event flow and corresponding event data, and each component metadata comprises the identification ID, the component type, a style definition, an attribute definition, an event definition and a method definition; the component type is used for associating a packaged component template to perform data binding rendering, the style defines a rendering style script for defining the component, and the event definition defines a linkage operation event which can be triggered by the component; the method defines a built-in processing callback method for defining the component.
3. The method for multiplexing process event development based on the low-code development platform according to claim 2, wherein the step S2 comprises the following substeps:
s21, calling a rear-end storage model instance according to the page table unit data to generate a data storage instance, wherein the generated page metadata storage instance is provided with a rendering batch number, and the generation method specifically comprises the following steps: processing the ID of the page metadata through a rear-end rendering storage model to generate a storage instance ID;
s22, calling a view model according to the page data storage example to generate a page view; and according to the components in the page metadata example, designating the rendered components through the view model, and dynamically binding the component metadata corresponding to the designated rendered components with the component template to generate the page view.
4. The method for multiplexing process event development based on the low-code development platform according to claim 1, wherein the step S3 specifically comprises:
and triggering the assembly binding event based on the fact that a user needs to use a specified page view, acquiring a rendering batch number of page metadata, and calling the rendering batch number and the process instance ID through a rear-end rendering service module to perform event script query to obtain an event script instance.
5. The method for multiplexing process event development based on the low-code development platform according to claim 1, wherein the step S4 specifically comprises:
s41, triggering a page interaction event according to an event script example, and calling a view model to request a page view which is used in a correlation manner;
s42, storing the used form page metadata examples of the model through a front end; and returning the storage model instance ID in the page metadata;
s43, determining a component corresponding to the ID in the event script according to the returned ID of the storage model instance, backfilling page data according to a mounting method for data interaction of the determined component, and realizing data interaction of the page view;
in step S4, the mounting method of data interaction specifically includes:
acquiring a data mount KEY value, creating an interactive mount object, caching the mount object on a root instance object of an AWS root container component, issuing the mount object as a KEY value subject message to an interactive component embedded in a page, and judging whether the interactive component is created or not;
if yes, immediately executing a mount interaction method according to the KEY value theme message received by the interaction component, and updating the executed identification state;
and if not, asynchronously initializing and creating the interactive component, acquiring the data mounting KEY value of the interactive component, inquiring a mounting object cached on a root instance object of the AWS root container component, and executing a mounting interactive method and updating the executed identification state when the mounting object exists.
6. A process event development multiplexing system based on a low code development platform according to any one of claims 1 to 5, wherein: the process event development multiplexing system is composed of a process model, a storage model and a view model;
the process model is used for designing an event execution process;
the storage model is used for storing the metadata in the form in the process;
and the view model is used for rendering the page layout.
7. The system for multiplexing process event development based on a low-code development platform according to claim 6, wherein: the view model is specifically a low-code development platform, and is provided with a view page component library and a deployment end; the view page component library comprises a plurality of components.
8. The system for multiplexing process event development based on a low-code development platform according to claim 7, wherein: the deployment end comprises a back-end rendering service module and a front-end rendering framework.
9. The system for multiplexing development of process events based on a low-code development platform according to claim 8, wherein: the back-end rendering service module is used for generating an instance of the page metadata and a rendering batch number.
10. The system for multiplexing process event development based on a low-code development platform according to claim 8, wherein: the front-end rendering framework is used to render instances of the page metadata and component templates into a page view.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211638771.4A CN115826963A (en) | 2022-12-20 | 2022-12-20 | Process event development multiplexing method and system based on low-code development platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211638771.4A CN115826963A (en) | 2022-12-20 | 2022-12-20 | Process event development multiplexing method and system based on low-code development platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115826963A true CN115826963A (en) | 2023-03-21 |
Family
ID=85516918
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211638771.4A Pending CN115826963A (en) | 2022-12-20 | 2022-12-20 | Process event development multiplexing method and system based on low-code development platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115826963A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116560637A (en) * | 2023-04-13 | 2023-08-08 | 珠海沃德尔软件科技有限公司 | Method and system for developing application system in configuration form for digital transformation |
| CN116627391A (en) * | 2023-07-21 | 2023-08-22 | 上海秉匠信息科技有限公司 | UI component detection method, device, equipment and storage medium |
-
2022
- 2022-12-20 CN CN202211638771.4A patent/CN115826963A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116560637A (en) * | 2023-04-13 | 2023-08-08 | 珠海沃德尔软件科技有限公司 | Method and system for developing application system in configuration form for digital transformation |
| CN116560637B (en) * | 2023-04-13 | 2023-10-20 | 珠海沃德尔软件科技有限公司 | Method and system for developing application system in configuration form for digital transformation |
| CN116627391A (en) * | 2023-07-21 | 2023-08-22 | 上海秉匠信息科技有限公司 | UI component detection method, device, equipment and storage medium |
| CN116627391B (en) * | 2023-07-21 | 2023-10-27 | 上海秉匠信息科技有限公司 | UI component detection method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109597814B (en) | Online rapid delivery system of background management information system | |
| TW202141300A (en) | Page processing method, device, apparatus and storage medium | |
| US7685609B1 (en) | Using a distributed form object model to facilitate form event processing | |
| CN115826963A (en) | Process event development multiplexing method and system based on low-code development platform | |
| CN100380318C (en) | Method and computer system for handling incremental data in client-server communication | |
| US8584082B2 (en) | System for dynamic discovery, configuration, and development of process-bound widgets | |
| US8166396B2 (en) | User interface rendering | |
| US8983935B2 (en) | Methods for utilizing a javascript emulator in a web content proxy server and devices thereof | |
| US20130174014A1 (en) | Systems and methods for configuring a mobile-optimized website | |
| US20070079282A1 (en) | Browser based designer and player | |
| CN115033235A (en) | System and method for flexibly multiplexing web page based on low-code development platform | |
| CN109614565B (en) | Webpage generation method and device | |
| WO2020207232A1 (en) | Sub-application development method, apparatus, computer device, and storage medium | |
| CN114064024A (en) | Method, apparatus, device, storage medium, and program product for developing micro-application | |
| CN113032708A (en) | Code-free Web development system | |
| CN103530338A (en) | Frame for carrying out page rendering on calculation equipment and page generation method | |
| CN111338626B (en) | Interface rendering method and device, electronic equipment and medium | |
| CN101937335A (en) | Method for generating Widget icon, method for generating Widget summary document and Widget engine | |
| CN117093316A (en) | Cross-platform page rendering system, electronic equipment and storage medium | |
| CN112988175A (en) | Cross-platform application installation package generation method, device, medium and electronic equipment | |
| CN112235132A (en) | Method, device, medium and server for dynamically configuring service | |
| CN114237583A (en) | Cross-platform visual code generation device and method | |
| CN111124386B (en) | Animation event processing method, device, equipment and storage medium based on Unity | |
| CN111708519B (en) | Service component processing method, device, equipment and storage medium | |
| CN101676905A (en) | Layout for modifying resource contents based on customized rules |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |