Interaction method of form data management platform and related device

Abstract

The invention relates to the technical field of interface interaction, in particular to an interaction method of a form data management platform and a related device. The method comprises the following steps: displaying a first sub-interface of a form data management platform; in response to a trigger instruction for the first control, switching the first sub-interface to a second sub-interface; in response to a trigger instruction for the second control, selecting an interface sub-region corresponding to the second control; and if an input instruction for the interface sub-region is received, displaying data corresponding to the input instruction in the interface sub-region. According to the method, a user can conveniently set the attribute data of the custom button according to preferences, and when the custom button is triggered subsequently, the needed interface and the corresponding data can be displayed in a one-key mode. Therefore, the experience and impression of the user can be improved, and meanwhile, a major pain point of lack of an inherent display mode and an expansion function in the prior art can be solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of interface interaction, in particular to an interaction method of a form data management platform and a related device. BACKGROUND

[0002] In the interface of a traditional form data management platform, the interface display and function display are usually performed according to an inherent mode (for example, a mode set during application development), so that the user cannot subsequently set the application and the form used by the application according to a favorite mode, and there is a great pain point in the extensible function. At the same time, it is not conducive to improving the overall effect of interface interaction, and affects the perception and experience of the user in using the form data management platform. SUMMARY

[0003] The embodiment of the present application provides an interaction method of a form data management platform and a related device, which can facilitate the user to newly create a custom button according to a favorite mode, so that the user can one-click display the required interface data when triggering the custom button, improve the overall effect of interface interaction, and further improve the experience and perception of the user.

[0004] According to an aspect of the embodiment of the present application, an interaction method of a form data management platform is provided, which comprises:

[0005] displaying a first sub-interface of a form data management platform, the first sub-interface comprising a first control for newly creating a custom button;

[0006] in response to a triggering instruction for the first control, switching the first sub-interface to a second sub-interface, the second sub-interface comprising a plurality of second controls for defining the custom button, each second control being located in a corresponding interface sub-region;

[0007] in response to a triggering instruction for the second control, selecting the interface sub-region corresponding to the second control;

[0008] if an input instruction for the interface sub-region is received, displaying data corresponding to the input instruction in the interface sub-region.

[0009] In the above scheme, the plurality of second controls for defining the custom button comprise an editing control for editing the style of the custom button, a filtering control for filtering form data, and an action execution control for setting the execution action of the custom button, and the response to the triggering instruction for the second control to select the interface sub-region corresponding to the second control comprises:

[0010] In response to a triggering instruction for the editing control, a style of a custom button is displayed in an interface sub-region corresponding to the editing control;

[0011] In response to a triggering instruction for the filtering control, filtering condition data that has been added is displayed in an interface sub-region corresponding to the filtering control;

[0012] In response to a triggering instruction for the action execution control, action type data that has been added is displayed in an interface sub-region corresponding to the action execution control.

[0013] In the above solution, the interface sub-region corresponding to the filtering control includes a plurality of option boxes for defining filtering conditions, and the filtering condition data is obtained by the following manner:

[0014] In response to a triggering instruction for the plurality of option boxes for defining filtering conditions, if an editing instruction for each of the option boxes is received, filtering condition data corresponding to the editing instruction is generated.

[0015] In the above solution, the second sub-interface further includes a text box for setting a name of the custom button and a plurality of display option boxes for setting a display type of the form data, and the method further includes:

[0016] In response to an input instruction for the text box, text data corresponding to the input instruction is displayed in the text box;

[0017] In response to a selection instruction for the display option box, a display option box corresponding to the selection instruction is selected as the display type of the form data.

[0018] In the above solution, the method further includes:

[0019] A third sub-interface of the form data management platform is displayed, and the third sub-interface includes a plurality of notification option boxes for defining notification attributes of a push reminder of the form data;

[0020] In response to a selection instruction for the notification option box, a notification mode corresponding to the selection instruction is displayed in the notification option box;

[0021] The third sub-interface further includes a text box for setting notification content, and the method further includes:

[0022] In response to a text input instruction for the text box for setting notification content, text corresponding to the text input instruction is displayed in the text box for setting notification content.

[0023] In the above solution, the method further includes:

[0024] The fourth sub-interface of the form data management platform is displayed, and the fourth sub-interface includes multiple third controls for setting the process of form data.

[0025] In response to a trigger command for the third control, a sub-area of ​​the interface corresponding to the trigger command for the third control is displayed in the fourth sub-interface.

[0026] In the above scheme, the method further includes:

[0027] The fifth sub-interface of the form data management platform is displayed, and the fifth sub-interface includes multiple text input boxes for defining the attributes of the form data;

[0028] In response to a text input command for the text input box, text corresponding to the text input command is displayed in the text input box.

[0029] According to one aspect of the embodiments of this application, an interactive device for a form data management platform is provided, the device comprising:

[0030] The first display unit is used to display the first sub-interface of the form data management platform. The first sub-interface includes a first control for creating a custom button.

[0031] The first response unit is used to switch from the first sub-interface to the second sub-interface in response to a trigger command for the first control. The second sub-interface includes a plurality of second controls for defining the custom button, and each second control is located in its corresponding interface sub-area.

[0032] The second response unit is used to select the interface sub-area corresponding to the second control in response to the trigger command for the second control;

[0033] The second display unit is configured to display data corresponding to the input instruction within the interface sub-area if an input instruction for the interface sub-area is received.

[0034] According to one aspect of the embodiments of this application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the interactive method of the form data management platform as described above.

[0035] According to one aspect of the embodiments of this application, a computer program product is provided, the computer program product including a computer program, the computer program being read and executed by a processor of an electronic device, causing the electronic device to perform the interaction method of the form data management platform as described above.

[0036] The beneficial effects of this application are as follows: This application can respond to a trigger command on a first control within a first sub-interface, switching from the first sub-interface to a second control comprising multiple controls for defining the custom button. Each second control is orderly distributed within its respective sub-area of ​​the interface. Users can select the sub-area corresponding to the second control and input content into these sub-areas. In other words, users can set the attributes of the custom button through input commands on the sub-areas. This allows users to set the attribute data of the custom button according to their preferences. Subsequently, when the custom button is triggered, the required interface and corresponding data can be displayed with a single click. Therefore, this application can improve the user experience and visual appeal, while also addressing a major pain point in existing technologies: the inherent display methods and lack of extended functionality. Attached Figure Description

[0037] Figure 1 This is a system architecture diagram of the interaction method of the form data management platform provided in the embodiments of this application;

[0038] Figure 2 A flowchart illustrating the interaction method of the form data management platform provided in this application embodiment;

[0039] Figure 3 A schematic diagram of the first sub-interface provided in an embodiment of this application;

[0040] Figure 4 A schematic diagram of the second sub-interface provided in an embodiment of this application;

[0041] Figure 5 Another schematic diagram of the second sub-interface provided in the embodiments of this application;

[0042] Figure 6 A schematic diagram of a third sub-interface provided in an embodiment of this application;

[0043] Figure 7 A schematic diagram of the fourth sub-interface provided in an embodiment of this application;

[0044] Figure 8 A schematic diagram of the fifth sub-interface provided in an embodiment of this application;

[0045] Figure 9 A block diagram of the interactive device of the form data management platform provided in the embodiments of this application;

[0046] Figure 10 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0047] Figure 11 This is a schematic diagram of the structure of a server provided in an embodiment of this application;

[0048] Figure 12 An example diagram of a data display interface provided in an embodiment of this application;

[0049] Figure 13 The main interface of the form data management platform provided in this application embodiment

[0050] Figure 14 The logic engine sub-interface provided in the embodiments of this application;

[0051] Figure 15 This application provides a new business logic sub-interface;

[0052] Figure 16 A schematic diagram illustrating the execution of the logic engine provided in the embodiments of this application.

[0053] Figure 17 A schematic diagram of the logic engine component library provided in the embodiments of this application;

[0054] Figure 18 A schematic diagram illustrating the execution and configuration of the logic engine provided in the embodiments of this application;

[0055] Figure 19 A schematic diagram illustrating the logic engine tracing provided in an embodiment of this application;

[0056] Figure 20 A schematic diagram illustrating the logic engine provided in the embodiments of this application. Detailed Implementation

[0057] To enable those skilled in the art to better understand the solutions of this application, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0058] It should be noted that while some processes described in the specification, claims, and accompanying drawings include multiple steps appearing in a specific order, it should be clearly understood that these steps may not be performed in the order they appear herein, or may be performed in parallel. The step numbers are merely used to distinguish different steps and do not themselves represent any execution order. Furthermore, descriptions such as "first," "second," or "objective" in this document are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. "Multiple" in this document refers to at least two.

[0059] It is worth noting that in the specific embodiments of this application, form data and other related data are involved. When the above embodiments of this application are applied to specific products or technologies, permission or consent from the target object is required, and the collection, use, and processing of related data must comply with relevant laws, regulations, and standards. For example, when an embodiment of this application needs to obtain form data, separate permission or consent from the target object can be obtained through pop-up windows or redirection to a confirmation page. After obtaining the separate permission or consent from the target object, the necessary form data for the normal operation of the embodiment of this application can then be obtained.

[0060] Please see Figure 1 , Figure 1 This is a system architecture diagram of the interactive method of the form data management platform provided in this application embodiment. It includes a terminal 140, an Internet connection 130, a gateway 120, a server 110, etc.

[0061] Terminal 140 can take various forms, including desktop computers, laptops, PDAs (personal digital assistants), mobile phones, vehicle terminals, and dedicated terminals. Furthermore, it can be a single device or a collection of multiple devices. For example, multiple desktop computers can be interconnected via a local area network, sharing a single monitor to work collaboratively, forming a single terminal 140. Terminal 140 can communicate with the Internet 130 via wired or wireless means to exchange data.

[0062] Server 110 refers to a computer system capable of providing certain services to terminal 140. Compared to ordinary terminal 140, server 110 has higher requirements in terms of stability, security, and performance. Server 110 can be a single high-performance computer in a network platform, a cluster of multiple high-performance computers, a portion of a single high-performance computer (e.g., a virtual machine), or a combination of portions of multiple high-performance computers (e.g., virtual machines). Server 110 can also communicate with the Internet 130 via wired or wireless means to exchange data.

[0063] Gateway 120, also known as an internetwork connector or protocol converter, is a computer system or device that acts as a translator, enabling network interconnection at the transport layer. It bridges the gap between two systems using different communication protocols, data formats, languages, or even completely different architectures. Gateways can also provide filtering and security functions. Messages sent from terminal 140 to server 110 are forwarded to the corresponding server 110 via gateway 120. Messages sent from server 110 to terminal 140 are also forwarded to the corresponding terminal 140 via gateway 120.

[0064] The specific implementation methods of the embodiments of this application are described in detail below:

[0065] Please see Figure 2 , Figure 2 This is a flowchart illustrating the interaction method of the form data management platform provided in this application embodiment. The interaction method of the form data management platform can be implemented by server 110 and / or terminal 140. Figure 2 The interactive methods shown in the form data management platform include:

[0066] Step 210: Display the first sub-interface of the form data management platform, the first sub-interface including a first control for creating a custom button;

[0067] Step 220: In response to the trigger command for the first control, switch from the first sub-interface to the second sub-interface. The second sub-interface includes a plurality of second controls for defining the custom button, and each second control is located in its corresponding interface sub-area.

[0068] Step 230: In response to the trigger command for the second control, select the interface sub-area corresponding to the second control;

[0069] Step 240: If an input command is received for the interface sub-region, display the data corresponding to the input command in the interface sub-region.

[0070] The complete embodiment of this application will be explained in detail below with reference to steps 210-240:

[0071] In step 210, the first sub-interface of the form data management platform can be as follows: Figure 3 As shown, Figure 3 The "Create Custom Button" shown is the first control described in this application.

[0072] In step 220, by clicking as Figure 3 The "Create Custom Button" control shown can respond to a trigger command on the first control. At this time, the first sub-interface will switch to the second sub-interface, as shown below. Figure 4 As shown, it includes an editing control for editing the style of the custom button, a filtering control for filtering form data, and an action execution control for setting the action of the custom button. Figure 4 In the middle, the second control is marked with a red box, and the interface sub-areas are marked with green boxes.

[0073] In step 230, in response to a trigger command for the edit control, the style of the custom button can be displayed in the interface sub-area corresponding to the edit control. Similarly, in response to a trigger command for the filter control, the added filter condition data can be displayed in the interface sub-area corresponding to the filter control. In response to a trigger command for the action execution control, the added action type data can be displayed in the interface sub-area corresponding to the action execution control.

[0074] In some embodiments, the interface sub-area corresponding to the filtering control includes multiple option boxes for defining filtering conditions, and the filtering condition data is obtained in the following way:

[0075] In response to a trigger command for the plurality of option boxes used to define filter conditions, if an edit command is received for each of the option boxes, filter condition data corresponding to the edit command is generated.

[0076] like Figure 5 The multiple option boxes shown are for defining filter criteria, namely "Name," "Equal to," "Value," and "Field." These option boxes contain pre-defined data, which can be selected based on the pre-defined data. Figure 5 In the image, the option boxes are marked in red.

[0077] In step 240, if an input command is received for the interface sub-region, data corresponding to the input command is displayed within the interface sub-region. Specifically, the input command for the interface sub-region can be for the interface sub-region where the second control is located, for example... Figure 4 The "Edit" control shown is located in the same sub-area of ​​the interface as the "Button Style" sub-area. Alternatively, it could be the sub-area of ​​the interface containing "Available Conditions." By clicking the option box below "Available Conditions" and selecting the data pre-set in that option box, an input command for that sub-area can be generated. The corresponding data will then be displayed instantly within the sub-area and in the option box.

[0078] In some embodiments, the second sub-interface further includes a text box for setting the name of the custom button and multiple display option boxes for setting the display type of the form data; the method further includes:

[0079] In response to an input command for the text box, text data corresponding to the input command is displayed in the text box;

[0080] In response to a selection command for the display option box, the display option box corresponding to the selection command is selected as the display type of the form data.

[0081] Specifically, such as Figure 4 As shown, Figure 4 It also includes a text box for customizing button names, that is... Figure 4 The "Button Name" text box allows users to enter the desired text. Once the desired text is entered into the text box, the text data corresponding to the input instruction will be displayed in the text box in response to the input instruction. Figure 4 The "available locations" in the text refer to the interface sub-regions. Figure 4 The "Data Details Page" and "View Data List" options are display option boxes. Selecting one of them will determine the display method (or display type) of the subsequent form data. For example... Figure 12 As shown, Figure 12 This displays the view data list's display type; at the same time, you can also click on options such as... Figure 12 The "Details" control shown is used to navigate to the data details page and view its display type.

[0082] In some embodiments, the method further includes:

[0083] The third sub-interface of the form data management platform is displayed. The third sub-interface includes multiple notification option boxes for defining the notification attributes of the form data to be pushed.

[0084] In response to a selection command for the notification option box, a notification method corresponding to the selection command is displayed in the notification option box;

[0085] The third sub-interface also includes a text box for setting notification content, and the method further includes:

[0086] In response to a text input instruction for the text box used to set notification content, text corresponding to the text input instruction is displayed in the text box used to set notification content.

[0087] like Figure 6 As shown, Figure 6 This is a diagram of the third sub-interface, which includes multiple notification option boxes such as "Reminder Type", "Notification Method", "Notified Person", and "Notification Category", as well as a text box for "Notification Content". Users can select the data type in these notification option boxes using the selection command, and can also enter text into the text box using the text input command.

[0088] In some embodiments, such as Figure 7 As shown, Figure 7 This is the fourth sub-interface of the form data management platform, which includes multiple third-party controls. For example, the third-party controls can be... Figure 7The interface includes multiple process controls and small icons. Clicking on these controls and icons will display the corresponding sub-areas for editing. Figure 7 It also includes a sub-area of ​​the interface for setting process node properties, which includes controls such as "Name" and "Associated Forms", which can be used to associate form data.

[0089] In some embodiments, such as Figure 8 As shown, Figure 8 This is a schematic diagram of the fifth sub-interface, which includes multiple text input boxes for defining attributes of form data, such as... Figure 8 The text input boxes shown include "Title Width" and "Input Length". Figure 8 It also includes several basic and advanced controls for setting more comprehensive attributes of form data, facilitating subsequent management of form data.

[0090] In some embodiments, please refer to Figure 13 As shown, Figure 13 This is the main interface of the form data management platform. Within the main interface, there are logic engine controls corresponding to the logic engine (i.e., such as...). Figure 13 The logic engine shown above, in response to a trigger command for the logic engine, displays as follows: Figure 14 The logic engine sub-interface shown includes multiple folders, such as... Figure 14 The folders shown, such as "CSS" and "610", can display the following in response to the open command for each folder: Figure 15 The "Create New Business Logic" sub-interface shown allows you to create new business logic, which can be done through methods such as... Figure 16 The business logic interface shown allows for custom configuration of business logic. Specifically, business logic debugging and execution are as follows: Figure 17 As shown (supports 37 components, each with corresponding input / output parameter configurations), after entering the input parameters, click Execute (e.g. Figure 18 As shown), after execution, view "Tracking" to see the input, output, and execution status of each node (e.g., ...). Figure 19 (As shown), finally, click Publish, as... Figure 20 As shown.

[0091] Business logic may include:

[0092] 1. Logic Preview: Allows previewing configured logic.

[0093] 2. Basic Information: You can view basic information about the business logic.

[0094] 3. Execution Log: Allows you to view the logs of the business logic execution.

[0095] 4. Historical Versions: Records the historical versions of this business logic, and also supports switching to the current version.

[0096] In summary, this application allows users to easily set the attribute data of custom buttons according to their preferences. When the custom button is triggered, the required interface and corresponding data can be displayed with a single click. Simultaneously, this application also allows for the creation of custom business logic, enabling rapid business workflow transitions. This logic can be combined with custom buttons to provide applications with richer business functionalities. Therefore, this application enhances the user experience and visual appeal, while also addressing a major pain point in existing technologies: the inherent display methods and lack of extended functionality.

[0097] Please see Figure 9 , Figure 9 This is a schematic diagram of the structure of the interactive device 300 of the form data management platform provided in this application embodiment. The interactive device 300 of the form data management platform is applied to a computer device, and the interactive device 300 of the form data management platform may include:

[0098] The first display unit 301 is used to display the first sub-interface of the form data management platform. The first sub-interface includes a first control for creating a custom button.

[0099] The first response unit 302 is used to switch from the first sub-interface to the second sub-interface in response to a trigger command for the first control. The second sub-interface includes a plurality of second controls for defining the custom button, and each second control is located in its corresponding interface sub-area.

[0100] The second response unit 303 is used to select the interface sub-area corresponding to the second control in response to the trigger command for the second control;

[0101] The second display unit 304 is configured to display data corresponding to the input instruction in the interface sub-area if an input instruction for the interface sub-area is received.

[0102] Reference Figure 10 , Figure 10 To implement the structural block diagram of a portion of the terminal 140 in this application embodiment, the terminal 140 includes: a radio frequency (RF) circuit 710, a memory 715, an input unit 730, a display unit 740, a sensor 750, an audio circuit 760, a wireless fidelity (WiFi) module 770, a processor 780, and a power supply 790, among other components. Those skilled in the art will understand that... Figure 10The terminal 140 structure shown does not constitute a limitation on a mobile phone or computer, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0103] The RF circuit 710 can be used to receive and transmit signals during information transmission or calls. In particular, it receives downlink information from the base station and processes it with the processor 780; in addition, it transmits uplink data to the base station.

[0104] The memory 715 can be used to store software programs and modules. The processor 780 executes various functional applications of the terminal and interactive processing of the form data management platform by running the software programs and modules stored in the memory 715.

[0105] The input unit 730 can be used to receive input numeric or character information, and to generate key signal inputs related to the terminal's settings and function control. Specifically, the input unit 730 may include a touch panel 731 and other input devices 732.

[0106] The display unit 740 can be used to display input or provided information, as well as various menus of the terminal. The display unit 740 may include a display panel 741.

[0107] Audio circuitry 760, speaker 761, and microphone 762 provide an audio interface.

[0108] In this embodiment, the processor 780 included in the terminal 140 can execute the interaction method of the form data management platform in the previous embodiment.

[0109] The terminal 140 in this application embodiment includes, but is not limited to, mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle terminals, and aircraft. This application embodiment can be applied to various scenarios, including but not limited to cloud technology, artificial intelligence, smart transportation, and assisted driving.

[0110] Figure 11This is a partial structural block diagram of a server 110 implementing an embodiment of this application. The server 110 can vary significantly due to different configurations or performance characteristics, and may include one or more central processing units (CPUs) 822 (e.g., one or more processors) and memory 832, and one or more storage media 830 (e.g., one or more mass storage devices) for storing application programs 842 or data 844. The memory 832 and storage media 830 can be temporary or persistent storage. The program stored in the storage media 830 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the server 110. Furthermore, the CPU 822 may be configured to communicate with the storage media 830 and execute the series of instruction operations in the storage media 830 on the server 110.

[0111] Server 110 may also include one or more power supplies 826, one or more wired or wireless network interfaces 850, one or more input / output interfaces 858, and / or one or more operating systems 841, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0112] The central processing unit 822 in server 110 can be used to execute the interactive method of the form data management platform of this application embodiment.

[0113] This application also provides a computer-readable storage medium for storing program code, which is used to execute the interaction method of the form data management platform of the foregoing embodiments.

[0114] This application also provides a computer program product, which includes a computer program. A processor of a computer device reads and executes the computer program, causing the computer device to perform the interactive method for implementing the aforementioned form data management platform.

[0115] Furthermore, the terms “comprising” and “including”, and any variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product, or apparatus.

[0116] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0117] It should be understood that in the description of the embodiments of this application, "multiple" means two or more, "greater than", "less than", "exceeding" etc. are understood to exclude the number itself, and "above", "below", "within" etc. are understood to include the number itself.

[0118] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0119] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0120] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0121] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0122] It should also be understood that the various implementation methods provided in this application can be combined arbitrarily to achieve different technical effects.

[0123] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0124] The above is a detailed description of the embodiments of this application. However, this application is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. An interaction method for a form data management platform, characterized in that, The method includes: Displays the first sub-interface of the form data management platform, the first sub-interface including a first control for creating a custom button; In response to a trigger command for the first control, the interface switches from the first sub-interface to the second sub-interface. The second sub-interface includes multiple second controls for defining the custom button, and each second control is located in its corresponding interface sub-area. In response to a trigger command for the second control, select the interface sub-area corresponding to the second control; If an input command is received for the interface sub-region, the data corresponding to the input command is displayed in the interface sub-region.

2. The interaction method of the form data management platform according to claim 1, characterized in that, The plurality of second controls for defining the custom button include an editing control for editing the style of the custom button, a filtering control for filtering form data, and an action execution control for setting the action of the custom button. The step of selecting the interface sub-area corresponding to the second control in response to a trigger command for the second control includes: In response to a trigger command for the editing control, a custom button style is displayed in the interface sub-area corresponding to the editing control; In response to a trigger command for the filter control, the added filter condition data is displayed in the interface sub-area corresponding to the filter control; In response to a trigger command for the action execution control, the added action type data is displayed in the interface sub-area corresponding to the action execution control.

3. The interaction method of the form data management platform according to claim 2, characterized in that, The interface sub-area corresponding to the filter control includes multiple option boxes for defining filter conditions, and the filter condition data is obtained in the following way: In response to a trigger command for the plurality of option boxes used to define filter conditions, if an edit command is received for each of the option boxes, filter condition data corresponding to the edit command is generated.

4. The interaction method of the form data management platform according to claim 3, characterized in that, The second sub-interface also includes a text box for setting the name of the custom button and multiple display option boxes for setting the display type of the form data. The method further includes: In response to an input command for the text box, text data corresponding to the input command is displayed in the text box; In response to a selection command for the display option box, the display option box corresponding to the selection command is selected as the display type of the form data.

5. The interaction method of the form data management platform according to claim 1, characterized in that, The method further includes: The third sub-interface of the form data management platform is displayed. The third sub-interface includes multiple notification option boxes for defining the notification attributes of the form data to be pushed. In response to a selection command for the notification option box, a notification method corresponding to the selection command is displayed in the notification option box; The third sub-interface also includes a text box for setting notification content, and the method further includes: In response to a text input instruction for the text box used to set notification content, text corresponding to the text input instruction is displayed in the text box used to set notification content.

6. The interaction method of the form data management platform according to claim 1, characterized in that, The method further includes: The fourth sub-interface of the form data management platform is displayed, and the fourth sub-interface includes multiple third controls for setting the process of form data. In response to a trigger command for the third control, a sub-area of ​​the interface corresponding to the trigger command for the third control is displayed in the fourth sub-interface.

7. The interaction method of the form data management platform according to claim 1, characterized in that, The method further includes: The fifth sub-interface of the form data management platform is displayed, and the fifth sub-interface includes multiple text input boxes for defining the attributes of the form data; In response to a text input command for the text input box, text corresponding to the text input command is displayed in the text input box.

8. An interactive device for a form data management platform, characterized in that, The device includes: The first display unit is used to display the first sub-interface of the form data management platform. The first sub-interface includes a first control for creating a custom button. The first response unit is used to switch from the first sub-interface to the second sub-interface in response to a trigger command for the first control. The second sub-interface includes a plurality of second controls for defining the custom button, and each second control is located in its corresponding interface sub-area. The second response unit is used to select the interface sub-area corresponding to the second control in response to the trigger command for the second control; The second display unit is configured to display data corresponding to the input instruction within the interface sub-area if an input instruction for the interface sub-area is received.

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the interaction method of the form data management platform according to any one of claims 1 to 7.

10. A computer program product, the computer program product comprising a computer program, characterized in that, The computer program is read and executed by the processor of the electronic device, causing the electronic device to perform the interaction method of the form data management platform according to any one of claims 1 to 7.

Images