Event action configuration method and device for low-code scenario, equipment and medium
Patent Information
- Application Number
- CN202211336963.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-10-28
- Publication Date
- 2026-10-30
- Estimated Expiration
- 2042-10-28
AI Technical Summary
[0002]目前,要实现页面的事件动作交互设计,尤其是复杂交互,通常比较困难,如需要耗费较大的人力和时间成本,且效率低下
[0016]应当理解,本部分所描述的内容并非旨在标识本公开的实施例的关键或重要特征,也不用于限制本公开的范围。本公开的其它特征将通过以下的说明书而变得容易理解。
Smart Images

Figure CN115756632B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of artificial intelligence technology, and in particular to event action configuration methods, apparatuses, devices and media for low-code scenarios in the fields of cloud computing, low-code and enterprise application technologies. Background Technology
[0002] Currently, implementing event-driven interactive design on web pages, especially complex interactions, is usually quite difficult, requiring significant manpower and time investment and is inefficient. Summary of the Invention
[0003] This disclosure provides methods, apparatus, devices, and media for configuring event actions in low-code scenarios.
[0004] An event action configuration method for low-code scenarios includes:
[0005] For the selected component, obtain the corresponding configuration information, event list, and action list. The configuration information is script language object simplified configuration information, and the component is a front-end low-code framework component.
[0006] The configuration panel is rendered and displayed based on the obtained content. The user can then interact visually with the first user through the configuration panel to obtain the configurations made by the first user for events and / or actions.
[0007] An event action configuration device for low-code scenarios includes: an information acquisition module and an interaction configuration module;
[0008] The information acquisition module is used to acquire corresponding configuration information, event list and action list for the selected component. The configuration information is script language object simplified configuration information, and the component is a front-end low-code framework component.
[0009] The interactive configuration module is used to render and display a configuration panel based on the acquired content, and to conduct visual interaction with the first user through the configuration panel to obtain the configuration made by the first user for events and / or actions.
[0010] An electronic device, comprising:
[0011] At least one processor; and
[0012] A memory communicatively connected to the at least one processor; wherein,
[0013] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method described above.
[0014] A non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the methods described above.
[0015] A computer program product includes a computer program / instructions that, when executed by a processor, implement the method described above.
[0016] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description
[0017] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:
[0018] Figure 1 A flowchart illustrating an embodiment of the event action configuration method for low-code scenarios described in this disclosure;
[0019] Figure 2 This is a schematic diagram of the configuration panel initially shown in this disclosure;
[0020] Figure 3 This is a schematic diagram of the configuration panel for the component feature actions described in this disclosure;
[0021] Figure 4 This is a schematic diagram of the composition structure of Embodiment 400 of the event action configuration device for low-code scenarios described in this disclosure;
[0022] Figure 5 A schematic block diagram of an electronic device 500 that can be used to implement embodiments of the present disclosure is shown. Detailed Implementation
[0023] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.
[0024] Furthermore, it should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.
[0025] Figure 1This is a flowchart illustrating an embodiment of the event action configuration method for low-code scenarios described in this disclosure. Figure 1 As shown, the specific implementation methods are as follows.
[0026] In step 101, for the selected component, the corresponding configuration information, event list, and action list are obtained. The configuration information is JavaScript Object Notation (JSON) configuration information, and the component is a front-end low-code framework (amis) component.
[0027] In step 102, a configuration panel is rendered and displayed based on the obtained content. The configuration panel is used to perform visual interaction with the first user to obtain the configuration made by the first user for events and / or actions.
[0028] The above-described method and embodiments allow for the configuration of event actions in a visual (i.e. graphical) manner to achieve complex page interactions. This simple approach improves processing efficiency and saves manpower and time costs.
[0029] For a selected component, such as a component dragged into the canvas, its corresponding configuration information, event list, and action list can be obtained. The configuration information can be JSON configuration information, and the component can be an Amis component.
[0030] Preferably, configuration information, event lists, and action lists can be obtained in a plug-in format. This plug-in design allows for faster and smoother component integration.
[0031] In practical applications, each component can correspond to one or more events, and each event can correspond to one or more actions. The automatic registration / definition of the event and action lists for each component can be achieved through a plugin mechanism. Similarly, the configuration information for a component can also be implemented using a plugin mechanism.
[0032] Based on the obtained configuration information, event list, and action list, a corresponding configuration panel can be rendered and displayed. Furthermore, the user can interact visually with the first user through the configuration panel to obtain the configurations made by the first user for events and / or actions.
[0033] Preferably, the configuration panel may include configuration panels at different levels. Accordingly, visual interaction with the first user through the configuration panel to obtain the configuration made by the first user for events and / or actions may include: saving the configuration made by the first user for events and / or actions on the displayed configuration panel; and in response to determining that the first user has performed a predetermined operation on the displayed configuration panel, displaying the next level configuration panel corresponding to the predetermined operation.
[0034] In other words, for the configuration panel currently displayed, the first user can directly configure events and / or actions on the configuration panel, or they can trigger the display of the next level configuration panel by performing a pre-defined operation, such as clicking a button or icon displayed on the configuration panel. In terms of implementation, it is very flexible and convenient.
[0035] Preferably, the configuration for events may include one or all of the following: adding a listener event, deleting a listener event, and the listener event being an event in the event list; the configuration for actions may include one or any combination of the following: configuring a component-specific action for any listener event, configuring a general action for any listener event, and configuring a custom action for any listener event. Here, a component-specific action refers to an action in the action list corresponding to the component, and a general action refers to an action common to all components, i.e., it is general and not specific to any particular component.
[0036] Figure 2 This is a schematic diagram of the initial display (which can be considered the highest level) of the configuration panel described in this disclosure. Figure 2 As shown, the content corresponding to the right rectangle is the initial configuration panel. When the user selects the "Form" component, the corresponding configuration panel is rendered and displayed. Furthermore, the first user can click "Add Event Listener," which displays a list of events corresponding to the "Form" component. The first user can select one or more events to listen to, i.e., as listener events, such as... Figure 2 The "Value Change", "Form Validation Successful", and "Submission Successful" events shown are all listener events.
[0037] like Figure 2 As shown, if the first user clicks the "+" icon after the listener event, it can be determined that the first user wants to add an action for the corresponding listener event. Accordingly, a corresponding configuration panel can be displayed. Different action types may correspond to different configuration panels. The action types may include component-specific actions, general actions, and custom actions, etc. Component-specific actions refer to the actions in the action list. The action type that the first user wants to configure can be determined in some way, the specific method is not limited, such as displaying a drop-down list for the first user to choose from, which may include three action types: component-specific actions, general actions, and custom actions.
[0038] Figure 3 This is a schematic diagram of the configuration panel for the component characteristic actions described in this disclosure. Figure 3As shown, when the first user clicks the "∨" icon corresponding to "Component Actions," a list of actions for that component will be displayed to the user. Assuming the first user selects the "Update**" action, further configuration can be applied to that action, such as setting specific "variable assignments." In practical applications, the configuration can take various forms, including strings, JavaScript code snippets, and formula editors.
[0039] The above explanation uses component feature actions as an example. For other action types, the configuration can also be completed through the corresponding configuration panel.
[0040] Additionally, when displaying Figure 2 When the configuration panel is displayed, events and actions can be shown according to the previous configuration made by the first user. This includes information such as which listener events were selected in the last configuration, the actions included in each listener event, and the specific configurations of these actions. The previous configuration can then be displayed. Based on this, the first user can add new listener events and delete existing listener events as described above, for example, by clicking... Figure 2 The trash can icon corresponding to the "numerical change" listener event shown in the image is used to delete the "numerical change" listener event. Additionally, with... Figure 2 Taking the "Link other components" action as an example, the first user can click the pencil icon corresponding to the "Link other components" action to re-edit its specific configuration. In addition, the first user can also click the trash can icon corresponding to the "Link other components" action to delete this action, etc.
[0041] In practical applications, it can be followed Figure 2 The actions shown are executed in the order they appear, and the execution order can be adjusted by dragging or dropping the actions.
[0042] As can be seen, through the above visualization method, the first user can easily and intuitively implement the event and / or action configuration of the component, that is, implement the orchestration design logic, and then implement page interaction based on the logic.
[0043] Preferably, in the solution described in this disclosure, the context information of the component can also be obtained. Accordingly, obtaining the configuration made by the first user for the event and / or action can refer to obtaining the configuration made by the first user for the event and / or action in combination with the context information.
[0044] The context information may include event variables, data domain variables, and system variables.
[0045] It can support visualization operations based on context data, which further facilitates the first user to configure events and / or actions and improves the configuration effect.
[0046] Preferably, in the scheme described in this disclosure, a unique identifier (id) can be assigned to the component, and the identifier can be used to realize the positioning of the component and the linkage with other components, wherein the linkage supports visual component selection.
[0047] For example, when a component is selected, it can be assigned a unique identifier, which can then be passed to the corresponding configuration panel. This identifier allows for precise location of the specified component and enables accurate interaction between components. This supports cross-level interaction design capabilities and unlimited levels of nesting between components. Furthermore, it allows for the visual selection of linked components; linkage could mean that an update in one component triggers a corresponding update in another.
[0048] In practical applications, the implementing entity of the solution described in this disclosure can be a page designer. Specifically, the rendering and display of the above configuration panel and the interaction with the first user can be achieved by a visual renderer started by the page designer.
[0049] Preferably, in the scheme described in this disclosure, the configuration information may include: customized configuration information. Accordingly, the customized configuration information made by the second user for the overall or partial display form of the configuration panel can be obtained and saved through the provided interface.
[0050] In practical applications, the first user can be understood as the user of the product corresponding to the solution described in this disclosure, and the second user can be understood as the developer.
[0051] The solution described in this disclosure can provide various different interfaces for use by a second user, such as the following interfaces:
[0052] 1) Actions: The type is {[propName:string]:PluginActions}, which is a collection of action definition objects (map) containing a list of actions corresponding to / supported by the component. Each action in the action list can include an action name, action identifier, and action description definition, etc.
[0053] 2) Events: The type is {[propName:string]: PluginEvents}. The event definition map contains a list of events corresponding to / supported by the component. Each event in the event list can include the event name, event identifier, and JSON schema definition of the event parameters, etc.
[0054] 3) Components: The type is () => Component Data Information (ComponentInfo[]), which is the component tree outline, that is, all the components corresponding to the canvas. This structure is a tree structure, and the components in it can be selected;
[0055] 4) Action Tree: This type consists of action type nodes (ActionTypeNode[]). The action tree can correspond to... Figure 3 The "Execution Action" shown supports group display and is defined as a tree structure. The ActionTypeNode definition includes the action name, action identifier, and sub-actions, etc.
[0056] 5) Action Configuration Object Collection (actionConfigItemsMap): The type is ActionConfigItemsMap, which is a configuration map for general actions. It is used to customize the configuration of general actions, such as rewriting the interaction configuration and text description of the send request action.
[0057] 6) Get ContextSchemas: The type is () => DataSchema, used to obtain context data information, mainly for context-based visualization operations, etc.
[0058] 7) Value: The type is ActionEventConfig, which is the initialization schema for the action event configuration and is used to echo the action event configuration;
[0059] 8) Update (onChange): The type is (value: any) => void. The onChange event is triggered after the event action configuration is updated. The latest event action configuration can be obtained by listening to this event.
[0060] With the help of the above interfaces, the second user can make various flexible configurations according to actual needs, such as customizing the overall or partial display form of the configuration panel. Through customized configuration, it is possible to customize what content needs to be displayed on the configuration panel, what content needs to be further displayed in response to user operations, and the specific display form / style of different content, thereby meeting the different needs of the second user.
[0061] It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of actions. However, those skilled in the art should understand that this disclosure is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this disclosure. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this disclosure.
[0062] In summary, the solution described in the embodiments of this disclosure can realize event action configuration in a visual way, which improves processing efficiency and saves manpower and time costs. Moreover, it can realize customized panel display through customized configuration and eliminate the development and learning costs brought by the front-end technology stack.
[0063] The above is an introduction to the method embodiments. The following describes the solution described in this disclosure further through device embodiments.
[0064] Figure 4 This is a schematic diagram of the structural composition of embodiment 400 of the event action configuration device for low-code scenarios described in this disclosure. Figure 4 As shown, it includes: an information acquisition module 401 and an interaction configuration module 402.
[0065] The information acquisition module 401 is used to acquire the corresponding configuration information, event list and action list for the selected component. The configuration information is JSON configuration information and the component is an Amis component.
[0066] The interactive configuration module 402 is used to render and display a configuration panel based on the acquired content, and to conduct visual interaction with the first user through the configuration panel to obtain the configuration made by the first user for events and / or actions.
[0067] By adopting the solution described in the above device embodiment, event action configuration can be realized in a visual way to achieve complex page interactions, etc. The implementation method is simple, thereby improving processing efficiency and saving manpower and time costs.
[0068] For a selected component, such as a component dragged into the canvas, the information acquisition module 401 can obtain its corresponding configuration information, event list, and action list. The configuration information can be JSON configuration information, and the component can be an Amis component.
[0069] Preferably, the information acquisition module 401 can acquire configuration information, event list, and action list in a plug-in format.
[0070] In practical applications, each component can correspond to one or more events, and each event can correspond to one or more actions. The automatic registration / definition of the event list and action list corresponding to each component can be achieved through the plugin mechanism.
[0071] Based on the obtained configuration information, event list, and action list, the interaction configuration module 402 can render and display the corresponding configuration panel. Furthermore, it can perform visual interaction with the first user through the configuration panel to obtain the configuration made by the first user for events and / or actions.
[0072] Preferably, the configuration panel may include configuration panels at different levels. Accordingly, visual interaction with the first user through the configuration panel to obtain the configuration made by the first user for events and / or actions may include: saving the configuration made by the first user for events and / or actions on the displayed configuration panel; and in response to determining that the first user has performed a predetermined operation on the displayed configuration panel, displaying the next level configuration panel corresponding to the predetermined operation.
[0073] In other words, for the configuration panel currently displayed, the first user can directly configure events and / or actions on the configuration panel, or they can trigger the display of the next level configuration panel by performing a pre-defined operation, such as clicking a button or icon displayed on the configuration panel.
[0074] Preferably, the configuration for events may include one or all of the following: adding a listener event, deleting a listener event, and the listener event being an event in the event list; the configuration for actions may include one or any combination of the following: configuring a component-specific action for any listener event, configuring a general action for any listener event, and configuring a custom action for any listener event. Here, a component-specific action refers to an action in the action list corresponding to the component, and a general action refers to an action common to all components, i.e., it is general and not specific to any particular component.
[0075] Preferably, the interaction configuration module 402 can also obtain the context information of the component. Accordingly, obtaining the configuration made by the first user for the event and / or action can refer to obtaining the configuration made by the first user for the event and / or action in combination with the context information.
[0076] Preferably, the information acquisition module 401 can also assign a unique identifier to the component. Correspondingly, the interaction configuration module 402 can use the identifier to realize the positioning of the component and the linkage with other components. In the case of linkage, visual component selection is supported.
[0077] In addition, preferably, the configuration information may include customized configuration information. Accordingly, the information acquisition module 401 can acquire and save the customized configuration information made by the second user for the overall or partial display form of the configuration panel through the provided interface.
[0078] In other words, through customized configuration, the second user can customize what content needs to be displayed on the configuration panel, what content needs to be further displayed based on the user's operations, and the specific display format / style of different content.
[0079] Figure 4 The specific workflow of the device embodiment shown can be found in the relevant descriptions in the foregoing method embodiments, and will not be repeated here.
[0080] In summary, the solution described in the embodiments of this disclosure can realize event action configuration in a visual way, which improves processing efficiency and saves manpower and time costs. Moreover, it can realize customized panel display through customized configuration and eliminate the development and learning costs brought by the front-end technology stack.
[0081] The solutions described in this disclosure can be applied to the field of artificial intelligence, particularly in areas such as cloud computing, low-code, and enterprise application technologies. Artificial intelligence is the study of enabling computers to simulate certain human thought processes and intelligent behaviors (such as learning, reasoning, thinking, and planning). It involves both hardware and software technologies. Artificial intelligence hardware technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, and big data processing. Artificial intelligence software technologies mainly include computer vision, speech recognition, natural language processing, machine learning / deep learning, big data processing, and knowledge graph technologies.
[0082] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.
[0083] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.
[0084] Figure 5A schematic block diagram of an electronic device 500 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.
[0085] like Figure 5 As shown, device 500 includes a computing unit 501, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 502 or a computer program loaded from storage unit 508 into random access memory (RAM) 503. RAM 503 may also store various programs and data required for the operation of device 500. The computing unit 501, ROM 502, and RAM 503 are interconnected via bus 504. Input / output (I / O) interface 505 is also connected to bus 504.
[0086] Multiple components in device 500 are connected to I / O interface 505, including: input unit 506, such as keyboard, mouse, etc.; output unit 507, such as various types of monitors, speakers, etc.; storage unit 508, such as disk, optical disk, etc.; and communication unit 509, such as network card, modem, wireless transceiver, etc. Communication unit 509 allows device 500 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0087] The computing unit 501 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 501 performs the various methods and processes described above, such as those described in this disclosure. For example, in some embodiments, the methods described in this disclosure can be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 508. In some embodiments, part or all of the computer program can be loaded and / or installed on device 500 via ROM 502 and / or communication unit 509. When the computer program is loaded into RAM 503 and executed by the computing unit 501, one or more steps of the methods described in this disclosure can be performed. Alternatively, in other embodiments, the computing unit 501 can be configured to perform the methods described in this disclosure by any other suitable means (e.g., by means of firmware).
[0088] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.
[0089] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0090] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.
[0091] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).
[0092] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.
[0093] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.
[0094] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.
[0095] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.
Claims
1. A method for configuring event actions in low-code scenarios, comprising: For the selected component, obtain the corresponding configuration information, event list, and action list. The configuration information is script language object simplified configuration information, and the component is a front-end low-code framework component. Each component corresponds to at least one event, and each event corresponds to at least one action. Rendering and displaying a configuration panel based on the acquired content includes: displaying the configuration panel according to the configuration made by the first user last time, including the listening events selected in the last configuration, the actions included in each listening event, and the specific configuration of each action; the configuration panel includes configuration panels at different levels; saving the configurations made by the first user for events and / or actions on the displayed configuration panel; and displaying the next level configuration panel corresponding to the predetermined operation in response to determining that the first user has performed a predetermined operation on the displayed configuration panel. The configuration information includes: customized configuration information; The method further includes: obtaining and saving customized configuration information made by the second user for the overall or partial display form of the configuration panel through the provided interface; The method further includes: obtaining context information of the component, the context information including event variables, data domain variables and system variables; wherein, saving the configuration made by the first user for the event and / or action includes: saving the configuration made by the first user for the event and / or action in combination with the context information; The method further includes: assigning a unique identifier to the component, using the identifier to locate the component and link it with other components, wherein the linking supports visual component selection.
2. The method according to claim 1, wherein, The step of obtaining the corresponding configuration information, event list, and action list includes: obtaining the configuration information, event list, and action list in a plug-in format.
3. The method according to claim 1 or 2, wherein, The configuration of events includes one or all of the following: adding a listener event, deleting a listener event, wherein the listener event is an event in the event list; The configuration of actions includes one or any combination of the following: configuring component characteristic actions for any listener event, configuring general actions for any listener event, or configuring custom actions for any listener event, wherein the component characteristic actions are the actions in the action list.
4. An event action configuration device for low-code scenarios, comprising: Information acquisition module and interaction configuration module; The information acquisition module is used to acquire corresponding configuration information, event list, and action list for a selected component. The configuration information is script language object simplified configuration information, and the component is a front-end low-code framework component. Each component corresponds to at least one event, and each event corresponds to at least one action. The interactive configuration module is used to render and display a configuration panel based on the acquired content, including: displaying the configuration panel according to the configuration made by the first user last time, including the listening events selected in the last configuration, the actions included in each listening event, and the specific configuration of each action; the configuration panel includes configuration panels at different levels; saving the configurations made by the first user for events and / or actions on the displayed configuration panel; and displaying the next level configuration panel corresponding to the predetermined operation in response to determining that the first user has performed a predetermined operation on the displayed configuration panel. The configuration information includes: customized configuration information; The information acquisition module is further used to acquire and save customized configuration information made by the second user for the overall or partial display form of the configuration panel through the provided interface. The interaction configuration module is further used to obtain the context information of the component, the context information including event variables, data domain variables and system variables, and save the configuration made by the first user for events and / or actions in combination with the context information; The information acquisition module is further used to assign a unique identifier to the component; The interaction configuration module is further used to locate the component and link it with other components using the identifier, wherein the linking supports visual component selection.
5. The apparatus according to claim 4, wherein, The information acquisition module acquires the configuration information, the event list, and the action list in a plug-in format.
6. The apparatus according to claim 4 or 5, wherein, The configuration of events includes one or all of the following: adding a listener event, deleting a listener event, wherein the listener event is an event in the event list; The configuration of actions includes one or any combination of the following: configuring component characteristic actions for any listener event, configuring general actions for any listener event, or configuring custom actions for any listener event, wherein the component characteristic actions are the actions in the action list.
7. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-3.
8. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-3.
9. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the method of any one of claims 1-3.
Citation Information
Patent Citations
Page generation method and system, terminal and medium
CN114489648A
Event configuration method, system and equipment for low-code platform and medium
CN114564252A
