Information processing method and apparatus, electronic device, and computer-readable storage medium

Abstract

The present disclosure provides an information processing method and apparatus, an electronic device, and a computer-readable storage medium, which can be applied to the technical field of computers and software development. The information processing method comprises: in response to receiving trigger information, on the basis of a form to be filled out matching the trigger information, displaying an information entry page for said form; and in response to respective entry information of at least one form item in said form acquired by means of the information entry page, filling out said form on the basis of the respective entry information of the at least one form item, so as to obtain a target form.

Description

Information processing methods and apparatus, electronic devices and computer-readable storage media Technical Field

[0001] This disclosure relates to the fields of computer technology and software development technology, and more specifically, to an information processing method and apparatus, electronic equipment and computer-readable storage medium. Background Technology

[0002] Forms are used to implement data collection functions in internet applications. With the development of information technology, the increasing complexity of business processes, and the diversification of user needs, forms have also become more complex. However, traditional static forms require developers to manually write code for various business scenarios, making it difficult to adequately meet the usage requirements of diverse business scenarios. Summary of the Invention

[0003] In view of the above, this disclosure provides an information processing method and apparatus, an electronic device, and a computer-readable storage medium.

[0004] According to one aspect of this disclosure, an information processing method is provided, comprising: in response to receiving trigger information, displaying an information entry page for the form to be filled based on a form to be filled that matches the trigger information; and in response to the entry information of at least one form item in the form to be filled obtained via the information entry page, filling in the form to be filled using the entry information of at least one form item to obtain a target form.

[0005] According to another aspect of this disclosure, an information processing apparatus is provided, comprising: a display module, configured to, in response to receiving trigger information, display an information entry page for the form to be filled based on a form to be filled that matches the trigger information; and an obtaining module, configured to, in response to input information of at least one form item in the form to be filled obtained via the information entry page, fill in the form to be filled using the input information of the at least one form item, thereby obtaining a target form.

[0006] According to another aspect of this disclosure, an electronic device is provided, comprising: one or more processors; and a memory for storing one or more instructions, wherein, when executed by the one or more processors, the one or more processors cause the one or more processors to perform the method as described in this disclosure.

[0007] According to another aspect of this disclosure, a computer-readable storage medium is provided having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the methods described in this disclosure.

[0008] According to another aspect of this disclosure, a computer program product is provided, which includes computer-executable instructions that, when executed, are used to perform the methods described in this disclosure. Attached Figure Description

[0009] The above and other objects, features, and advantages of this disclosure will become clearer from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0010] Figure 1 schematically illustrates a system architecture to which information processing methods can be applied according to embodiments of the present disclosure;

[0011] Figure 2 schematically illustrates a flowchart of an information processing method according to an embodiment of the present disclosure;

[0012] Figure 3 schematically illustrates an example diagram of a component configuration page in a form designer according to an embodiment of the present disclosure;

[0013] Figure 4 schematically illustrates an example diagram of a form configuration page in a form designer according to an embodiment of the present disclosure;

[0014] Figure 5 schematically illustrates an example of a component configuration page that uses a form designer to configure a custom component of a map type according to an embodiment of the present disclosure;

[0015] Figure 6 schematically illustrates an example diagram of the information entry page display process according to an embodiment of the present disclosure;

[0016] Figure 7 schematically illustrates an example diagram of a web page according to an embodiment of the present disclosure;

[0017] Figure 8 schematically illustrates an example diagram of a smart customer service page according to an embodiment of the present disclosure;

[0018] Figure 9 schematically illustrates a block diagram of an information processing apparatus according to an embodiment of the present disclosure; and

[0019] Figure 10 schematically illustrates a block diagram of an electronic device suitable for implementing an information processing method according to an embodiment of the present disclosure. Detailed Implementation

[0020] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0021] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0022] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0023] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0024] In the technical solution of this invention, the user information (including but not limited to user personal information, user image information, user device information, such as location information) and data (including but not limited to data used for analysis, stored data, and displayed data) involved are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with relevant laws, regulations, and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entry points for users to choose to authorize or refuse.

[0025] Forms are used to implement data collection functions in internet applications. With the development of information technology, the increasing complexity of business processes, and the diversification of user needs, forms have also become more complex. However, traditional static forms require developers to manually write code for various business scenarios, making it difficult to adequately meet the usage requirements of diverse business scenarios.

[0026] In one example, developers can design forms by dragging and dropping components, configuring attributes and styles, and can also generate components that developers can use directly based on the design results.

[0027] However, not all application scenarios are covered during the product development phase. Take the application scenario of park management as an example. This application scenario is complex and ever-changing. Various types of information within the park (such as facility reservations, maintenance requests, visitor registration, and resource applications) need to be collected and managed through efficient and flexible forms. Furthermore, the forms need to support dynamic adjustment and expansion to adapt to changing business processes and user needs. The methods described above are insufficient to meet the needs of modern park management and business operations.

[0028] Therefore, this disclosure provides an information processing method and apparatus, electronic device, and computer-readable storage medium, which can be applied to the fields of computer technology and software development technology. The information processing method includes: in response to receiving trigger information, displaying an information entry page for the form to be filled based on a form to be filled that matches the trigger information; and in response to receiving entry information for at least one form item in the form to be filled obtained via the information entry page, filling in the form to be filled using the entry information for each of the at least one form item, thereby obtaining a target form.

[0029] Figure 1 schematically illustrates a system architecture to which the information processing method can be applied according to embodiments of the present disclosure. It should be noted that Figure 1 is merely an example of a system architecture to which embodiments of the present disclosure can be applied, to help those skilled in the art understand the technical content of the present disclosure, but does not imply that embodiments of the present disclosure cannot be used in other devices, systems, environments, or scenarios.

[0030] As shown in Figure 1, the system architecture 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between different devices.

[0031] It should be noted that the information processing method provided in this embodiment can generally be executed by the server 105. Accordingly, the information processing device provided in this embodiment can generally be located in the server 105.

[0032] Alternatively, the information processing method provided in this embodiment of the present disclosure can also be executed by the first terminal device 101, the second terminal device 102, or the third terminal device 103. Correspondingly, the information processing apparatus provided in this embodiment of the present disclosure can also be disposed in the first terminal device 101, the second terminal device 102, or the third terminal device 103.

[0033] It should be understood that the number of terminal devices, networks, and servers shown in Figure 1 is merely illustrative. Any number of terminal devices, networks, and servers can be used depending on implementation needs.

[0034] It should be noted that the sequence numbers of the operations in the following methods are for descriptive purposes only and should not be considered as indicating the execution order of the operations. Unless explicitly stated otherwise, the method does not need to be executed in the exact order shown.

[0035] The above describes the system architecture for which information processing methods can be applied, as provided in this disclosure. The following will use Figure 2 as an example to further explain the information processing process of this disclosure.

[0036] Figure 2 schematically illustrates a flowchart of an information processing method according to an embodiment of the present disclosure.

[0037] As shown in Figure 2, the information processing method 200 includes operations S210 to S220.

[0038] In operation S210, in response to receiving trigger information, an information entry page for the form to be filled out is displayed based on the form to be filled out that matches the trigger information.

[0039] In operation S220, in response to the input information of at least one form item in the form to be filled obtained via the information input page, the form to be filled is filled using the input information of at least one form item, and the target form is obtained.

[0040] Before implementing the information processing method provided in this disclosure, at least one candidate form can be developed in advance. Different candidate forms are used to implement data collection and recording functions in different application scenarios. Candidate forms may include form labels, form fields, and form buttons. Form labels include the URL of the CGI program used to process form data and the method for submitting data to the server. Form fields include text boxes, password boxes, hidden fields, multi-line text boxes, check boxes, radio buttons, drop-down selection boxes, date pickers, and file upload boxes, etc., used to obtain various types of input fields. Form buttons include submit buttons, reset buttons, and general buttons, etc. The submit button is used to send data to the server, the reset button is used to cancel input, and the general button is used to perform other processing tasks. After developing at least one candidate form, the configuration information of each candidate form can be stored to facilitate subsequent data analysis and record management.

[0041] Each candidate form can be applied to different application scenarios. Application scenarios can include at least one of the following: IT operations and maintenance, customer service, equipment maintenance, project management, and order maintenance. During the development of candidate forms, each candidate form can also be configured with its own preset information set. The preset information set can include preset vocabulary and / or preset statements adapted to the application scenario of that candidate form.

[0042] The trigger information can be user-inputted. The specific format of the trigger information can be configured according to actual business needs and is not limited here. For example, the trigger information can be in text format, which the user can input through an input box on the front-end interface. Alternatively, the trigger information can be in voice format, which the user can input by speaking into a voice receiving device. Another alternative is that the trigger information can be in selection format, which the user can input by manually selecting from the options on the front-end interface. After receiving the trigger information, it can be matched with the preset information sets of at least one candidate form to determine the form to be filled out that matches the trigger information from at least one candidate form.

[0043] After identifying the form to be filled out, for each of the at least one tasks included in that form, the task can be rendered on the front-end interface to obtain the corresponding form item (i.e., Form Element), so that the information entry page for that form can be displayed on the front-end interface. This process involves front-end and back-end development work, using HTML and JavaScript to render the information entry page based on the form. For example, HTML can be used to construct the structure of the form, and JavaScript can be used to handle the form's submission event.

[0044] Form fields are the basic elements that make up a form to be filled out, used to collect user input data. Each form field can correspond to a specific data type or user interaction method. The information entered into form fields refers to the data that the user inputs into these form fields. The specific type of form field can be configured according to actual business needs and is not limited here. For example, the type of form field can include at least one of the following: text input box, multi-line text box, radio button, checkbox, drop-down menu, file upload, and button, etc.

[0045] For each form item, the user can enter the corresponding information on the information entry page. The server then uses this information to fill out the form and obtain the target form. For example, a text input box can be used to collect short text information. A multi-line text box can be used to collect longer text information. A radio button can be used to select one option from multiple options. A checkbox can be used to select multiple options from multiple options. A drop-down menu can be used to select one or more options from a predefined list of options. A file upload function can be used to upload files. Buttons can be used to submit the form or perform other operations.

[0046] It should be noted that the specific application scenarios of the information processing method provided in this disclosure can be configured according to actual business needs, and are not limited here. For example, the application scenarios of the information processing method can include at least one of the following: park infrastructure scenario, internet scenario, healthcare scenario, manufacturing scenario, and logistics and transportation scenario, etc. In one example, in the park infrastructure scenario, the information processing method provided in this disclosure can be applied to the management of new infrastructure in the park, and work order issues can be resolved by customizing and personalizing the settings for work orders. For example, candidate forms suitable for the park infrastructure scenario can include equipment work orders, product work orders, and merchant work orders, etc.

[0047] In another example, in an internet scenario, the information processing method provided in this disclosure can be applied to support front-end transactions, that is, to allow the submission and editing of various work orders during front-end buying and selling, so as to realize back-end work order management. For example, candidate forms suitable for internet scenarios may include product work orders, order management work orders, customer inquiry work orders, and service evaluation work orders from Taobao and JD.com.

[0048] In another example, within a healthcare scenario, the information processing methods provided in this disclosure can be applied to patient service management to optimize internal processes within healthcare enterprises. For instance, candidate forms suitable for healthcare scenarios may include appointment registration forms, consultation service forms, medical equipment maintenance forms, and drug management forms.

[0049] In another example, in a manufacturing scenario, the information processing methods provided in this disclosure can be applied to production process control to improve production efficiency. For instance, candidate forms suitable for manufacturing scenarios may include production planning management forms, production progress tracking forms, and product quality control forms.

[0050] In another example, in a logistics and transportation scenario, the information processing method provided in this disclosure can be applied to logistics scheduling management to improve the efficiency of logistics scheduling. For example, candidate forms suitable for a logistics and transportation scenario may include vehicle management forms and cargo management forms, etc.

[0051] According to embodiments of this disclosure, upon receiving a trigger message, a pre-configured form to be filled is intelligently identified and matched, and an information entry page for the form is displayed. By providing the form to be filled in a form format for the user to fill out, the user can conveniently input the information for each form item. Furthermore, by utilizing the input information for at least one form item to fill out the form, the resulting target form is accurate and complete, optimizing the entire form processing flow and improving the efficiency and accuracy of form filling.

[0052] In the embodiments of this disclosure, candidate forms suitable for different application scenarios can be generated in advance before executing the information processing method. The generation process of the candidate forms will be described below.

[0053] It should be noted that the generation of candidate forms can be supported and implemented by a form designer. The form designer is built on a front-end framework and library, providing a visual interface that allows administrators to generate candidate forms by dragging and dropping components, and then saving the generated candidate forms as configuration information (e.g., JSON data). This configuration information is used to parse and render the actual form interface during subsequent use of the candidate forms. The specific implementation of the form designer can be configured according to actual business needs and is not limited here.

[0054] For example, the form designer can exist as a web application, in which case administrators can access the online form designer through a browser to design and generate candidate forms. Alternatively, the form designer can be packaged as a browser plugin, in which case administrators can design and generate candidate forms based on the form design interface supported by embedded browser technology. Alternatively, the form designer can exist as a desktop application (exe file), in which case administrators can download the exe file and run it on their local computer to design and generate candidate forms. Alternatively, the form designer can be part of a mobile application (APP), in which case administrators can design and generate candidate forms using the mobile application.

[0055] In one example, in response to a form generation request received from the front-end page, an initial form can be generated using the form configuration information entered on the form configuration page. Form configuration information refers to information related to the functional settings and business process management of the candidate form. For example, form configuration information may include at least one of the following: form name, form description, intelligent customer service options, and a set of preset information applicable to the application scenarios of the candidate form.

[0056] In response to the detection that at least one target component among multiple candidate components has been triggered, form fields for at least one target component are generated using at least one component configuration information entered on the component configuration page. Component configuration information refers to information related to the settings and management of each component in the candidate form. Component configuration information may include at least one of the following: field name, field name options, title, placeholder hints, default value, character limits, regular expression validation, smart questions, and answer examples, etc.

[0057] After obtaining the initial form and the form items of at least one target component, a candidate form can be generated based on the initial form and the form items of at least one target component. Therefore, compared to static forms that are predefined and cannot be changed during software development, this disclosure provides a method for dynamically generating forms, allowing administrators to flexibly and dynamically configure or modify forms during product use by dragging or clicking at least one target component in the editor according to the needs of the application scenario.

[0058] According to embodiments of this disclosure, an initial form framework is generated based on form configuration information entered by the user on the form configuration page. Simultaneously, the user can easily create and modify forms by dragging and dropping or clicking components and configuration attributes. By detecting and identifying target components triggered during user interaction, and generating form items for each target component based on component configuration information entered by the user on the component configuration page, candidate forms can be generated based on the initial form framework and the form items for each target component. This process not only improves the flexibility and responsiveness of form generation but also allows users to dynamically configure form content through simple operations to adapt to different business processes and changing needs. This enables the automated creation and management of candidate forms based on the user's personalized needs and configuration information.

[0059] The generation process of the candidate form provided in this disclosure has been explained above. The following will further illustrate the generation process of the candidate form by taking the generation of a candidate form applicable to the application scenario of reporting repairs to park facilities as an example, with reference to Figures 3 and 4.

[0060] Figure 3 schematically illustrates an example diagram of a component configuration page in a form designer according to an embodiment of the present disclosure.

[0061] Figure 4 schematically illustrates an example diagram of a form configuration page in a form designer according to an embodiment of the present disclosure.

[0062] As shown in Figures 3 and 4, both the form configuration page and the component configuration page can be implemented using the Vue and Element component libraries. Each can be divided into three areas: the left area is the component display area, the middle area is the preview area, and the right area is the configuration area. The component display area shows the candidate component tags for at least one candidate component. The preview area allows the administrator to preview the target component and candidate form that have been dragged and dropped.

[0063] In error 300, when the component configuration option above the configuration area on the right is triggered, this configuration area is used to configure the target component; in error 400, when the form configuration option above the configuration area on the right is triggered, this configuration area is used to configure the candidate form.

[0064] For example, during the configuration of a target component, an administrator can drag a target component from at least one candidate component displayed in the component display area to the preview area, select the component configuration option in the configuration area, and use the configuration area in section 300 to complete the component configuration information for that target component. The component configuration information, in turn, affects the display effect of the target component in the preview area.

[0065] Alternatively, during the configuration of candidate forms, administrators can select form configuration options in the configuration area and use the configuration area in the 400 form to set the form configuration information for that candidate form. The form configuration information, in turn, affects the display effect of the candidate form in the preview area.

[0066] Candidate forms are bound to process buttons. Once the form configuration information and component configuration information of the candidate forms take effect, corresponding candidate forms can be added.

[0067] In one example, when saving a newly added candidate form, form configuration information and component configuration information can be stored as the configuration information for that candidate form. For instance, each candidate form can be assigned a first unique identifier, and this first unique identifier can be associated with and stored with the configuration information. When the candidate form needs to be edited again later, the corresponding configuration information can be retrieved through the first unique identifier, and the effect of the last edit can be displayed in the form designer based on the configuration information, which is equivalent to opening the interface from the last configuration and continuing the configuration.

[0068] In another example, when saving a newly added candidate form, each candidate component in the left-hand component display area can be used as a toolbox corresponding to that candidate form. This toolbox includes the candidate component identifiers for each of the multiple candidate components. The form configuration information, component configuration information, and the multiple candidate component identifiers are stored as the configuration information for that candidate form.

[0069] For example, a second unique identifier can be assigned to each candidate form, and this second unique identifier can be associated with and stored in conjunction with configuration information. When the candidate form needs to be edited again later, the corresponding configuration information can be retrieved through this second unique identifier. Based on the multiple candidate component tags in the configuration information, the corresponding components from the toolbox are displayed in the left area of ​​the form designer. The effects of the previous edit are displayed in the middle and right areas based on the component configuration information and the form configuration information. In one example, in response to receiving a form generation request, during the form development process, the administrator can click on the target component in the left component display area or drag the target component to the middle preview area. The form configuration page is then displayed in the right configuration area 403 of Figure 4 (400). In response to detecting user actions on the form configuration page, the form configuration information is retrieved.

[0070] In response to the detection that a target component in the component display area has been triggered, the component configuration page can be displayed in the configuration area 303 on the right side of 300 in Figure 3. In response to the detection of user actions on the component configuration page, the component configuration information is retrieved. Afterwards, the administrator can click the save button to save the form configuration information of the candidate form and the individual component configuration information of each target component, so that users can subsequently use the candidate form to report maintenance issues for park facilities.

[0071] According to embodiments of this disclosure, in response to a user initiating a form generation request, a form configuration page is displayed in the configuration area, allowing the user to intuitively set and adjust the basic information of the form. Simultaneously, the server can dynamically obtain the user's form configuration information to ensure that the generated form accurately reflects the user's needs. Furthermore, in response to detecting that a target component has been triggered, a component configuration page is displayed in the configuration area, allowing the user to configure each component in the form in detail. The server can also dynamically obtain the user's component configuration information to ensure that each component is accurately set according to the user's intent. Thus, intuitive and efficient form generation and management are achieved, improving the accuracy and efficiency of form generation while enhancing the user's experience in customizing forms.

[0072] The component configuration process is further illustrated below using Figure 3 as an example. Referring to Figure 3, at least one candidate component in component configuration area 301 can each have a type. Types can include general types and custom types. A general component library refers to a collection of components designed for widespread use, typically maintained by a community or commercial team, providing a series of standardized, reusable UI components. A custom component library refers to a collection of components created by developers according to their specific needs or project specifications.

[0073] General types can include input types and selection types. For example, input components under the input type can include single-line text components, multi-line text components, password boxes, and counter components. Selection components under the selection type can include dropdown selection components, single-choice components, multiple-choice components, image upload components, date selection components, time selection components, toggle components, and rating components. Custom types can include tree structure types and map types. Tree structure components are used to display data with hierarchical relationships; for example, custom tree structure components can include device trees and spatial trees. Map components are used to display map data on the front end; for example, custom map components can include park maps and room maps. Additionally, custom types can also include license plate input components and protocol checkboxes.

[0074] The different types of candidate components mentioned above can be defined in the array `leftComps`. For example, `[{title: 'Input Component', content: inputComps}, {title: 'Selection Component', content: selectComps}, {title: 'Custom Component', content: bizComps}]`. Furthermore, if a new candidate component of a certain type needs to be added, it can be added to the `leftComps` array in the form of `{title: 'XX Type Component', content: XXComps}`, and the configuration of the corresponding component type can be maintained.

[0075] In one example, when the target component is of a general type (i.e., for input and selection components), a general component library (such as the Element library) can be used on the web side. Its configuration items correspond to the target component tag and its attributes, so that by calling the general component library, the form items for the target component can be displayed in the form preview area 302. When the target component is of a custom type (i.e., for custom components), a `type: 'custom'` attribute configuration field can be added. This attribute configuration field will then be used during subsequent web form rendering to determine when to call the custom component library and display the form items for the target component in the form preview area 302.

[0076] According to embodiments of this disclosure, when the target component is of a general type, a general component library is called and form items for the target component are displayed in the preview area; when the target component is of a custom type, a custom component library is called and form items for the target component are displayed in the preview area. This intelligent component library calling mechanism enables automatic identification of the type of the target component and rapid generation of corresponding form items, thereby improving the flexibility and efficiency of form construction.

[0077] By referencing a Vue-based drag-and-drop component (such as vuedraggable), the array `leftComps` is iterated to render and display the target component tag for each target component. A click event (e.g., `addComp`) can be added to each target component tag. This click event can be used to clone the triggered target component and add it to the relevant form area, performing necessary initialization and activation operations. For example, in response to detecting that a target component tag among the multiple candidate component tags displayed in the component configuration area 301 has been triggered, the form item corresponding to that target component tag can be rendered synchronously in the form preview area 302.

[0078] In one example, for each click event—that is, after the target component label is triggered—the configuration file corresponding to that target component label can be cloned to generate a new clone component. The uniqueness of each clone component in the candidate form is ensured by obtaining the initial data of the clone component and generating a unique target component label and key-value pair for it. The target component with the target component label can be displayed in the form preview area 302, and the target component label can be added to a first list (e.g., displayList) that serves as a drawing list, so that the first list can be used to record the target component labels of at least one target component included in the form preview area 302.

[0079] Based on this, in response to the detection that the current component in at least one target component is triggered, the component tag of the current component can be added to the second list (i.e., activeItem) so that the second list can be used to record the selected current component in at least one target component, and the component configuration information of the target component can be obtained in the configuration area 303 of the component configuration page 300.

[0080] According to embodiments of this disclosure, by using a first list as a recording tool when a user selects a specific target component label from multiple candidate component labels, all target component labels selected by the user can be tracked and managed. By using a second list as a recording tool when the current component in at least one target component is triggered, the currently selected component can be accurately managed. Thus, through the aforementioned intelligent component triggering and recording mechanism, users can easily manage and configure complex form components without manually recording or searching for selected components, thereby improving the user experience and increasing the efficiency and accuracy of form generation.

[0081] The preview area can include a form preview area 302 and an intelligent customer service effect preview area 304. By clicking on a candidate component in the component configuration area 301, or dragging and dropping a candidate component from the component configuration area 301 to the form preview area 302, the target component can be configured in the configuration area 303. After configuration is complete, both the form preview area 302 and the intelligent customer service effect preview area 304 can be updated synchronously to display the preview effect.

[0082] For form preview area 302, drag-and-drop functionality for at least one form item in 302 can be achieved by referencing Element's form component and a Vue-based drag-and-drop component. By wrapping the form items with the Vue-based drag-and-drop component, drag-and-drop sorting is enabled. A defined layout rendering method ensures that the form items in form preview area 302 are displayed in a clear layout.

[0083] By iterating through the first list (e.g., displayList), a component instance is created for each target component tag in the first list, and a unique key is assigned to each component instance so that the updated component can be rendered in the form preview area 302. A component instance refers to a concrete object of a class or component that is instantiated. The name of each component instance can be denoted as... <displayitem>The system then passes the target component tag of the activated component and the component configuration information obtained from configuration region 303 as attributes to the component instance. Based on this, corresponding Vue render function data objects can be generated according to the component data of each passed component instance to dynamically render the component tree.

[0084] In addition, to facilitate administrator operations, copy and delete buttons can be added to each component instance. Clicking the copy button triggers a copy event for the form item, allowing for quick copying of a specific form item. Clicking the delete button triggers a delete event for the form item, allowing for deletion of a specific form item.

[0085] For configuration area 303, which is used for component configuration, component configuration information for a currently active form item (i.e., the form item corresponding to the component tag in the second list, i.e., activeItem)) can be obtained by editing the configuration. Component configuration information may include at least one of the following: field name, field name options, title, placeholder hints, default value, character limit, regular expression validation, smart question, and answer example. The field name, field name options, title, placeholder hints, default value, character limit, and regular expression validation information can be used to support the preview in form preview area 302. The smart question and answer example can be used to support the preview in smart customer service effect preview area 304.

[0086] Configuration area 303 lists all executable configuration items. Each configuration item has a corresponding handler function for all types of value changes to process data updates. The active form field in `activeData` can be used to determine if it includes a specific configuration item, and its display in configuration area 303 can be controlled via VIF. The component configuration information in configuration area 303 also affects the preview form displayed in form preview area 302; the preview form displayed in form preview area 302 can be synchronously updated based on the component configuration information obtained from configuration area 403.

[0087] In one example, when the component type is a selection type, the data for this form item is not static; that is, the form item needs to be configured with a dropdown selection box, and the selected content is dynamically generated based on the administrator's configuration. In this case, a data dictionary can be predefined. The data dictionary can include the component tags for at least one selection type component and multiple options for each component tag. When configuring the target component of the selection type, the component tags in the data dictionary are associated in configuration area 303. This allows the form item for the target component of the selection type to be rendered based on the component tag and displayed to the administrator during form preview or actual web rendering, by associating the component tag with the multiple options corresponding to that component tag in the data dictionary.

[0088] According to embodiments of this disclosure, when it is necessary to display form items of the target component of the selection type, multiple corresponding options are called from a predefined data dictionary, and the form items of the target component of the selection type are rendered based on the multiple options. This realizes the automated configuration and rendering of the target component of the selection type, and improves the flexibility and response speed of form construction.

[0089] The following example, Figure 4, further illustrates the form configuration process. Referring to Figure 4, explanations of the component configuration area 401, form preview area 402, and intelligent customer service effect preview area 404 can be found in Figure 3 related to these areas; they will not be repeated here.

[0090] For configuration area 403 used for form configuration, the form configuration information can be obtained by configuring the entire candidate form currently being edited, and this information is stored in the candidate form's configuration file (i.e., formConfig). When the user configures a new candidate form or changes a configuration item in the form configuration information of an existing candidate form, the form configuration information in the configuration file can be updated.

[0091] In one example, the form configuration information may include at least one of the following: form name, form description, intelligent customer service options, and a set of preset information applicable to the application scenario of the candidate form. The intelligent customer service options can be used to enable or disable intelligent customer service, which can understand and respond to user needs through technologies such as Natural Language Processing (NLP) and Machine Learning (ML).

[0092] If a candidate form can only be created by users via a web page, the intelligent customer service option can be disabled, and the scenario configuration area does not need to be displayed in configuration area 403. If the intelligent customer service option is enabled, the scenario configuration area can be displayed in configuration area 403. The scenario configuration area can be used to retrieve a set of preset information applicable to the application scenario of the candidate form. The preset information set can be used to automatically match candidate forms to the corresponding application scenario based on trigger information. The preset information set includes at least one preset vocabulary and at least one preset statement for the application scenario of the candidate form. Preset vocabulary is equivalent to trigger words, which can be used for coarse matching of trigger information to quickly identify the topic or intent of the user's query. Preset statements are equivalent to datasets, which can be used for fine matching of trigger information to more accurately understand the topic or intent of the user's query.

[0093] According to embodiments of this disclosure, by displaying a scenario configuration area and obtaining a preset information set for the candidate form when the intelligent customer service option is enabled, users can preset relevant preset information sets according to business needs in specific application scenarios. Based on this, at least one preset word and at least one preset statement included in the preset information set can be used to match trigger information, automatically determining candidate forms that match the trigger information, thereby helping to provide more personalized and accurate services.

[0094] The generation of the candidate form provided in this disclosure has been explained above. The following will use Figure 5 as an example to further illustrate the component configuration process, taking a map-type custom component as an example.

[0095] Figure 5 schematically illustrates an example of a component configuration page that uses a form designer to configure a custom component of a map type according to an embodiment of the present disclosure.

[0096] As shown in Figure 5, taking the park map component as an example, in form 500, users can select the current reporting location by dragging the icon of the current reporting location in form 501 corresponding to this component. Map-type components are suitable for application scenarios involving geographical location and can provide users with a rich interactive experience. The application scenarios in which map-type components can be used can be configured according to actual business needs and are not limited here. For example, application scenarios may include at least one of the following: equipment failure reporting, facility maintenance, asset management, security incident reporting, and facility leasing and reservation, etc.

[0097] In equipment failure reporting scenarios, users can mark the specific location of faulty equipment on a map within the park, facilitating rapid problem identification by maintenance personnel. In facility maintenance scenarios, facility managers can mark areas requiring maintenance on a map within the park to track and manage maintenance tasks. In asset management scenarios, assets within the park (such as equipment and furniture) can be marked on a map. Users can record the asset's status, usage, and location changes through forms. In security incident reporting scenarios, when a security incident (such as a fire or theft) occurs within the park, users can mark the specific location of the incident on a map, quickly and accurately recording the incident location, which aids in emergency response and subsequent investigations. In facility leasing and booking scenarios, users can select and book specific facility locations through forms. A visually appealing facility booking interface simplifies the booking process.

[0098] In one example, the design and integration of map-type components can be configured according to actual business needs and are not limited here. For instance, geographic information data collected within the park can be used as the data source. Mapping software can be used to embed the park map, and the coordinate points of the park's edges can be connected to create multiple areas within the park, resulting in a park map. A draggable marker icon can then be added to the completed park map to mark the current location. Based on this, map-type components can be added as custom components.

[0099] When a user actually fills out the form, form items configured as map types can be displayed as a map. Users can select the corresponding current reporting location by dragging marker icons on the map. During this process, the map center and zoom level can be initialized when the map loads. The drag event of the marker icon is listened to, and the dragged position is updated in real time to the configuration information corresponding to the candidate form. For example, the location can be stored in the form of longitude and latitude.

[0100] The application of the aforementioned map-type components is suitable for business scenarios requiring detailed geographic location marking. Through visual maps and drag-and-drop functionality, users can accurately mark locations, reducing errors and communication costs. At the same time, this intuitive map interface and interaction method simplifies the process of location selection and form completion.

[0101] The above describes the process of generating the candidate form provided in this disclosure. After generating the candidate form, the form configuration information of the candidate form and the component configuration information of each of the at least one target component included in the candidate form can be processed, and the processed information can be stored in the data source on the server side so that when the candidate form is used later, the information corresponding to the candidate form can be retrieved from the data source and the candidate form can be rendered and displayed.

[0102] The specific data processing method can be configured according to actual business needs and is not limited here. For example, for each component tag in the candidate form, the component tag can be used as the key and the component configuration information of the component tag as the value to obtain key-value pairs for the component tag. Based on this, the configuration information of the candidate form can be determined according to the key-value pairs of each component tag.

[0103] According to embodiments of this disclosure, after configuring the candidate form, by creating corresponding key-value pairs for each component tag—that is, using the component tag as the key and the component configuration information of that component tag as the value—the configuration of each component can be stored and managed in a structured manner. Furthermore, by storing the configuration information obtained based on the key-value pairs of at least one component tag to the data source, the consistency and integrity of each candidate form and its configuration information are ensured. This allows for accurate access and use of the relevant configuration information throughout the entire lifecycle of the candidate form, whether in the design, preview, or submission phases, simplifying the form management process.

[0104] The generation process of the candidate form provided in this disclosure has been described above. In the embodiments of this disclosure, after the candidate form is generated, the form to be filled in can be determined from the multiple candidate forms that have been generated according to the trigger information, and the information entry page for the form to be filled in can be displayed. The display process of the information entry page is described below with Figure 6 as an example.

[0105] Figure 6 schematically illustrates an example diagram of the information entry page display process according to an embodiment of the present disclosure.

[0106] As shown in Figure 6, in step 600, in response to receiving trigger information 601, a form 603 to be filled out that matches trigger information 601 can be determined from at least one candidate form. In one example, each candidate form may have its own candidate intent, the target intent of trigger information 601 can be determined, and the form 603 to be filled out can be determined based on the candidate intent and target intent of each candidate form.

[0107] According to embodiments of this disclosure, by comparing the triggering information with a preset information set for each candidate intent, the user's request content can be identified and understood, thereby accurately determining the user's target intent. Based on this, by identifying candidate forms with target intents as forms to be filled out, the accuracy of form processing and the personalized experience are improved.

[0108] The method for determining the target intent can be configured according to actual business needs and is not limited here. For example, the trigger information 601 can be analyzed using natural language processing technology to obtain the target intent. Alternatively, each candidate intent can correspond to a preset information set, which can be used to match with the trigger information 601 to obtain the target intent. Alternatively, the trigger information 601 can be input into the intent recognition model to obtain the target intent.

[0109] In one example, at least one candidate form may include candidate form 602_1, candidate form 602_2, ..., candidate form 602_N, where N is a positive integer. Candidate form 602_1 may have candidate intent 1, candidate form 602_2 may have candidate intent 2, and so on, with candidate form 602_N having candidate intent N. After receiving trigger information 601, trigger information 601 can be matched with the preset information sets of each of candidate intent 1, candidate intent 2, ..., candidate intent N to obtain the target intent. Based on this, the candidate form with the target intent can be determined as the form 603 to be filled out.

[0110] In another example, the intent recognition model can be pre-trained using at least one candidate intent and a pre-defined information set for each candidate intent. The pre-defined information set may include at least one pre-defined vocabulary and at least one pre-defined statement suitable for the application scenario of the candidate form. This pre-defined information set can be configured or imported by the administrator using the form configuration page of the form designer, as shown in Figure 4. The trained intent recognition model can be deployed on a server to provide API services. When a user interacts with the intelligent customer service, i.e., enters trigger information 601, the API is called to identify the user's target intent, thereby accurately triggering the matching of candidate forms.

[0111] According to embodiments of this disclosure, determining the target intent is simple and efficient by matching the trigger information with keywords from a preset information set for each candidate form. Furthermore, determining the target intent can also be achieved by inputting the trigger information into an intent recognition model, which facilitates deeper semantic analysis. Thus, through these two methods, trigger information can be flexibly processed, and the user's target intent can be accurately identified.

[0112] Data source 604 may store configuration information for at least one candidate form. After obtaining form 603 to be filled, configuration information 605 for form 603 can be retrieved from data source 604. Based on this, information entry page 607 can be displayed according to the configuration information 605 for form 605, using a preset display method 606.

[0113] According to embodiments of this disclosure, by determining the form to be filled in from at least one candidate form based on trigger information, the accuracy and reliability of the matching are ensured. Furthermore, by displaying the information entry page based on a preset display method and configuration information for the form to be filled in, an intuitive, user-friendly, and efficient information input environment is provided. Thus, through an intelligent matching and display mechanism, the automation level of form processing and the user experience are improved.

[0114] In one example, after identifying the form to be filled that matches the trigger information, configuration information for the form can be retrieved from the data source based on that form. The configuration information can be in JSON format, including at least one key-value pair. The data source can be a structured data source, which refers to a data source that stores data in a fixed format and typically follows a specific data model. The specific choice of data source can be configured according to actual business needs and is not limited here. For example, the data source can include at least one of the following: relational databases, data warehouses, and data lakes. In one example, the data source can be a MySQL database within a relational database to facilitate form configuration.

[0115] As mentioned earlier, during the component configuration phase when the candidate form is generated, each candidate component has its own candidate component tag. The administrator can drag the target component from among the multiple candidate components in the component display area to the preview area, and complete the configuration of the target component by selecting the component configuration option in the configuration area. After obtaining the component configuration information of the target component, the backend can store the candidate component tag and component configuration information of the target component as JSON data.

[0116] Similarly, during the form configuration phase when generating candidate forms, administrators can complete the configuration for the candidate form by selecting the form configuration options in the configuration area. After obtaining the form configuration information of the candidate form, the backend can store the unique identifier of the candidate form and the form configuration information as JSON data.

[0117] Through the aforementioned storage processes for component configuration information after the component configuration stage and for form configuration information after the form configuration stage, JSON-formatted configuration information can be obtained. Therefore, when using candidate forms subsequently, after obtaining the configuration information, it is necessary to parse it to restore and display the configuration information as the previously configured form data, obtaining at least one component tag and its respective component configuration information. The specific parsing method can be configured according to actual business needs and is not limited here. For example, at least one component tag can be identified in the configuration information based on the field name corresponding to the component tag; for each component tag, the corresponding component configuration information can be extracted from the configuration information.

[0118] According to embodiments of this disclosure, before displaying the information entry page based on the configuration information, configuration information for the form to be filled can be obtained from the data source, and the configuration information can be parsed and processed to extract at least one component tag and the component configuration information of each component tag, thereby obtaining the specific configuration requirements of each component and improving the automation level of form generation and data processing.

[0119] The foregoing has provided a preliminary description of the display process of the information entry page provided in this disclosure. In the embodiments of this disclosure, after obtaining the configuration information, the Web page can be rendered according to the configuration information via the Web form rendering module, and the entry information of each form item can be obtained using the Web page. The process of obtaining entry information using the Web page is illustrated below with Figure 7 as an example.

[0120] Figure 7 schematically illustrates an example diagram of a web page according to an embodiment of the present disclosure.

[0121] As shown in Figure 7, in 700, users can input text-based trigger information through the input boxes on the front-end interface, such as "Report a problem / warranty order". Alternatively, users can input voice-based trigger information into the voice receiving device, such as "Equipment XX in the park needs repair". Alternatively, users can manually select "Report a problem / warranty order" on the front-end interface to input selected trigger information.

[0122] After receiving the aforementioned trigger information, the backend can match the trigger information with the preset information sets of at least one candidate form to identify the form to be filled that matches the trigger information from among the candidate forms. Once the backend identifies the form to be filled, it can use a web form rendering module to display the information entry page for that form on the frontend interface. In this case, the display process of the information entry page can include component invocation and form item rendering.

[0123] The template data used by the Web form rendering module comes from the configuration edited in the form designer. It can display at least one component tag and the component configuration information of each component tag in the form of a form on the web page, so that users can fill in information related to facility maintenance.

[0124] Taking a warranty report form as an example, the elform component can be used as a form container based on the form configuration information in the configuration file (i.e., formConfig), and the form's data model and validation rules can be bound.

[0125] During the component invocation phase, each field in the configuration information is iterated. Specifically, for each component tag, the `tag` field within each field distinguishes different component types. This allows for the retrieval of the target component from the target component library for the form item based on the component type indicated by the tag, and the execution of specific processing logic. The target component library can include a general component library or a custom component library. Event handling functions can be written during this process. For example, for the elupload upload component, event handling functions could include events such as before upload, during upload, upload success, and upload failure.

[0126] In the form field rendering stage, after the complete configuration of each component tag is listed, the target component can be rendered on the information entry page according to the component configuration information, resulting in the form fields for each component tag. For example, taking the trigger information "XX equipment in the park needs repair" as an example, the repair service order includes form fields such as repair address, contact number, contact person, repair type, repair manager, manager's phone number, and remarks.

[0127] For the form field "Repair Address", the input box can display "Please enter the repair address"; for the form field "Contact Number", the input box can display "Please enter the contact number"; for the form field "Contact Person", the input box can display "Please enter the contact person"; for the form field "Repair Type", the selection box can display "Please select the repair type"; for the form field "Repair Manager", the input box can display "Please enter the repair manager"; for the form field "Manager's Phone Number", the input box can display "Please enter the manager's phone number"; for the form field "Remarks", the input box can display "Please enter remarks".

[0128] In addition, it can generate two-way data binding for forms, setting default values ​​for form fields and retrieving options. For example, for date or time selection components, the default values ​​can be data configured by the administrator. Alternatively, for selection-type components, such as the "Repair Type" form item, the relevant option data can be obtained by calling an API, with API parameters derived from the form's configuration during design.

[0129] This web page can also be configured with cancel and save buttons. Clicking the cancel button will cancel the current warranty report entry. Clicking the save button will save the current warranty report entry.

[0130] According to embodiments of this disclosure, by intelligently calling the corresponding target component from the target component library based on the component type, this categorized storage and calling method enables the system to quickly locate and load suitable components based on component type, ensuring configuration consistency and ease of operation, and improving the accuracy and response speed of component configuration. Furthermore, by rendering the target component on the information entry page according to the component configuration information to generate specific form items, it ensures that the form items can be correctly displayed and functionally implemented according to the predetermined component configuration information. Thus, through a flexible component calling and rendering mechanism, the automation and personalization of form construction are achieved.

[0131] The foregoing has provided a preliminary description of the display process of the information entry page provided in this disclosure. In the embodiments of this disclosure, after obtaining the configuration information, the intelligent customer service module can render the intelligent customer service page according to the configuration information and use the intelligent customer service page to obtain the entry information of each form item. The process of obtaining the entry information using the intelligent customer service page is illustrated below with Figure 8 as an example.

[0132] Figure 8 schematically illustrates an example diagram of a smart customer service page according to an embodiment of the present disclosure.

[0133] As shown in Figure 8, in 800, users can input text-based trigger information through the input boxes on the front-end interface, such as "Equipment XX in the park needs repair." Alternatively, users can input voice-based trigger information into the voice receiving device, such as "Equipment XX in the park needs repair." Alternatively, users can manually select "Report a Problem / Warranty" on the front-end interface to input selected trigger information.

[0134] After receiving the aforementioned trigger information, the backend can match the trigger information with the preset information sets of at least one candidate form to identify the form to be filled out that matches the trigger information. Once the backend identifies the form to be filled out, the intelligent customer service module can display an information entry page for that form on the frontend interface. In this case, the display process of the information entry page can include a question generation stage and a question output stage.

[0135] The template data used by the intelligent customer service module comes from the configuration edited in the form designer. It can display at least one component tag and the component configuration information of each component tag in the form of questions on the intelligent customer service page, guiding users to reply with information related to each question, thereby completing the filling in of information related to facility maintenance.

[0136] In one example, for each form item, based on the component tag and its configuration information, a question can be output via the information entry page to retrieve the user's input information, thus enabling the retrieval of the user's response. The question can be configured when generating the form in the form designer. During the intelligent customer service application, the session state can be tracked, each step of the user's response recorded, and a question for the next form item extracted from the configuration information, progressively asking the user and recording their answers.

[0137] During the initial design phase, common exceptions and corresponding templates can be predefined. This allows the system to return to the predefined template during the question generation phase when the user's input is incorrect or unrecognizable. Alternatively, if the user's input is ambiguous, the system can ask for further details during the question generation phase. Or, after obtaining valid user input information, the system can perform a second confirmation during the question generation phase to improve the system's robustness and accurately understand the user's intent.

[0138] Furthermore, validation rules can be configured for each form item. The intelligent customer service system extracts the valid parts of the user's response and provides corresponding guidance and feedback on handling exceptions based on the user's response. If the valid part of a form item's response does not meet the validation rules, the user can be prompted to respond again. If the valid part of a form item's response meets the validation rules, that valid part can be temporarily stored, and after all form items are filled out, the complete form can be displayed for the user's secondary confirmation, and automatically submitted after the user's confirmation.

[0139] The specific format of user responses can be configured according to actual business needs and is not limited here. For example, responses can include text input or voice input. When users respond via text input, they can directly enter their responses in the input box at the bottom of the intelligent customer service page.

[0140] When users respond via voice input, the Web Speech API or other audio libraries can be used to capture their voice input. The voice input is preprocessed to obtain preprocessed voice data; preprocessing may include noise reduction, gain adjustment, etc. An interface providing speech recognition services is called, passing the preprocessed voice data to the speech recognition service, receiving the returned text result, and cleaning and processing the text result to obtain processed text data. A natural language understanding service is used to perform intent recognition and entity extraction on the processed text data, and a dialogue management system is used to generate a response based on the result and dialogue context. Based on this, an appropriate speech synthesis service is selected to convert the text data response generated by the dialogue management system into audio synthesized data, and the audio synthesized data is played using an audio playback library or the Web Speech API.

[0141] By processing responses of different types, the system can obtain the input information for each form item to complete the form. This integrated workflow simplifies the user's operation steps.

[0142] The following example, using the trigger message "Equipment XX in the park needs repair," illustrates the service process of the intelligent customer service. Candidate forms suitable for this application scenario can include form items such as repair address, contact number, contact person, repair type, repair manager, manager's phone number, and remarks. During form configuration, when configuring components for each of the above form items, you can configure the corresponding intelligent questions and answer examples for each form item.

[0143] For example, during component configuration, the smart question corresponding to "Repair Address" can be configured as "Okay, could you describe the location in as much detail as possible?", and the example answer can be configured as "XX District, XX Town, XX Industrial Park, XX Road, XX Number". Referring to Figure 8, when the smart customer service module receives the trigger information "Equipment XX in the park needs repair", it can output the smart question and example answer "Okay, could you describe the location in as much detail as possible? (e.g., XX District, XX Town, XX Industrial Park, XX Road, XX Number)" in the question output stage to retrieve the form field entry information corresponding to "Repair Address". Furthermore, the smart customer service module can obtain the user's reply to this question: "Yes, the address is 1, A Road, A Industrial Park, A District, A Town".

[0144] For example, during component configuration, the smart question corresponding to "Contact Number" can be configured as "Recorded. An employee will contact you after the order is dispatched. Would you still like to be contacted via this mobile number, XX?". Referring to Figure 8, after receiving the user's reply to the previous question, the smart customer service module can output the smart question "Recorded. An employee will contact you after the order is dispatched. Would you still like to be contacted via this mobile number, 188XXXXXXXX?" in the question output stage to retrieve the input information for the form field corresponding to "Contact Number". Furthermore, the smart customer service module can retrieve the user's reply to this question, "Contact XX. His mobile number is 135XXXXXXXX".

[0145] For example, during component configuration, the smart question corresponding to "Repair Type" can be configured as "Okay, the repair types are as follows, please select the closest item (A.xx B.xx C.xx D.xx)". Referring again to Figure 8, after receiving the user's reply to the previous question, the smart customer service module can output the smart question "Okay, the repair types are as follows, please select the closest item (A.xx B.xx C.xx D.xx)" in the question output stage. Furthermore, the smart customer service module can obtain the user's reply "B" for this question.

[0146] According to embodiments of this disclosure, by using natural language processing technology, users are guided to fill out forms by outputting questions. Each question is determined based on the component configuration information of the component tag for that form item. Each question is used to obtain the input information for the corresponding form item, thereby guiding users to accurately fill in the required information, improving the accuracy and convenience of information entry, and enhancing the interactivity and user experience of the form. Furthermore, as the component configuration information is updated, the content and format of the questions can be quickly adjusted to adapt to different application scenarios. This dynamic question generation mechanism can flexibly respond to changing data collection scenarios.

[0147] In one example, before obtaining the individual input information for each form item, it can be determined whether the user has previously submitted a similar form based on the user information that initiated the trigger and the user's historical interaction information.

[0148] For example, if it's determined that the user hasn't submitted similar forms before, the input information for each form item can be obtained via the information entry page. Alternatively, if it's determined that the user has submitted similar forms before, it can be determined whether to use the historical information corresponding to that component tag from the previous form. If it's determined to use the historical information corresponding to that component tag, it can be automatically used as the input information for the form item to simplify the filling process. If it's determined not to use the historical information corresponding to that component tag, the input information for the form item can be obtained via the information entry page.

[0149] According to embodiments of this disclosure, for each component tag, it can be determined whether the historical interaction information of the user identifier corresponding to the trigger information includes historical information corresponding to the component tag. If the historical interaction information contains historical information corresponding to the component tag, the historical information can be directly used as the input information for the form item. Thus, the efficiency of form filling can be improved when the user has performed similar requirements or certain form items have been entered.

[0150] In one example, after displaying the information entry page for the form to be filled out and obtaining the initial entry information for each form item through this page, the initial entry information for each form item can be validated separately based on preset validation rules for the form items, yielding a validation result. The validation rules can be set during component configuration through the component configuration page. Specific validation rules can be configured according to actual business needs and are not limited here. For example, validation rules can include at least one of the following: basic validation rules, special validation rules, and regular expression validation rules.

[0151] Basic validation rules can include whether a field is required and character limits. For example, if a form field is required, and the field is marked as `required: true` in the form field's data, then a required field marker will appear before the form field, requiring the user to fill it in before submitting. If a form field is not required, and the field is marked as `required: false` in the form field's data, then no required field marker will appear before the form field, and the user does not need to fill it in before submitting. Special validation rules are rules for certain custom components. For example, for the "Check Agreement" component, the user needs to check the agreement before submitting. Regular expression validation rules are used to configure regular expressions for the form field during form design and to use these regular expressions to validate the initial input information for the form field.

[0152] Based on this, if the verification result indicates that the verification passes, the initial entered information can be used as the entered information for that form item. If the verification result indicates that the verification fails, the user can be prompted to re-enter the entered information for that form item.

[0153] According to embodiments of this disclosure, after obtaining the initial input information for each form item, the initial input information can be validated according to the validation rules used for the form items. This automated validation mechanism reduces the need for manual review, improves the user's filling efficiency, and thus optimizes the overall data entry and processing experience.

[0154] It should be noted that in the embodiments of the present invention, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of the present invention. However, they do not mean that the present invention has used or necessarily used such solutions.

[0155] The above are merely exemplary embodiments, but are not limited thereto. Other information processing methods known in the art may also be included, as long as they can improve the efficiency and accuracy of form filling.

[0156] Based on the above information processing method, the present invention also provides an information processing device. The device will be described in detail below with reference to FIG9.

[0157] Figure 9 schematically illustrates a block diagram of an information processing apparatus according to an embodiment of the present disclosure.

[0158] As shown in Figure 9, the information processing device 900 may include a display module 910 and an acquisition module 920.

[0159] Display module 910 is used to respond to received trigger information and display an information entry page for the form to be filled based on the form to be filled that matches the trigger information.

[0160] The module 920 is used to respond to the input information of at least one form item in the form to be filled obtained via the information entry page, and to fill in the form to be filled using the input information of at least one form item to obtain the target form.

[0161] Any one or more of the modules according to embodiments of this disclosure, or at least a portion thereof, may be implemented in one module. Any one or more of the modules according to embodiments of this disclosure may be implemented by dividing them into multiple modules. Any one or more of the modules according to embodiments of this disclosure may be at least partially implemented as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a System-on-Chip, a System-on-Substrate, a System-on-Package, an Application-Specific Integrated Circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, one or more of the modules according to embodiments of this disclosure may be at least partially implemented as computer program modules, which, when run, can perform corresponding functions.

[0162] It should be noted that the information processing device part in the embodiments of this disclosure corresponds to the information processing method part in the embodiments of this disclosure. The description of the information processing device part is specifically referred to in the information processing method part, and will not be repeated here.

[0163] Figure 10 schematically illustrates a block diagram of an electronic device suitable for implementing an information processing method according to an embodiment of the present disclosure. The electronic device shown in Figure 10 is merely an example and should not be construed as limiting the functionality and scope of the embodiments of the present disclosure.

[0164] As shown in FIG10, a computer electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage portion 1009 into a random access memory (RAM) 1003. The processor 1001 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1001 may also include onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0165] RAM 1003 stores various programs and data required for the operation of electronic device 1000. Processor 1001, ROM 1002 and RAM 1003 are interconnected via bus 1004.

[0166] According to embodiments of this disclosure, the electronic device 1000 may further include an input / output (I / O) interface 1005, which is also connected to a bus 1004. The electronic device 1000 may also include one or more of the following components connected to the input / output (I / O) interface 1005: an input section 1006 including a keyboard, mouse, etc.; an output section 1007 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN card, modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the input / output (I / O) interface 1005 as needed. A removable medium 1011, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 1010 as needed so that computer programs read from it can be installed into the storage section 1008 as needed.

[0167] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the information processing method according to the embodiments of this disclosure.

[0168] In this disclosure, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0169] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods provided in the embodiments of this disclosure. When the computer program product is run on an electronic device, the program code is used to enable the electronic device to implement the information processing methods provided in the embodiments of this disclosure.

[0170] When the computer program is executed by the processor 1001, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0171] According to embodiments of this disclosure, program code for executing computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages.

[0172] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. It should also be noted that in some alternative implementations, the functions indicated in the boxes may occur in a different order than those shown in the drawings.

[0173] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.< / displayitem>

Claims

1. An information processing method comprising: in response to receiving a trigger information, displaying an information entry page for a to-be-filled form based on the to-be-filled form matching the trigger information; and in response to entry information of at least one form item in the to-be-filled form obtained via the information entry page, filling the to-be-filled form with the entry information of the at least one form item to obtain a target form. The response to receiving a trigger information, displaying an information entry page for a to-be-filled form based on the to-be-filled form matching the trigger information comprises:

2. The method of claim 1, wherein, determining, according to the trigger information, a to-be-filled form matching the trigger information from at least one candidate form; and displaying the information entry page based on a preset display mode according to configuration information for the to-be-filled form.

3. The method of claim 2, further comprising, before the displaying the information entry page based on a preset display mode according to configuration information for the to-be-filled form: the configuration information comprises at least one key-value pair; and According to the form to be filled in, the configuration information for the form to be filled in is acquired from a data source, wherein parsing the configuration information to obtain at least one component tag and component configuration information of each component tag. The displaying the information entry page based on a preset display mode according to configuration information for the to-be-filled form comprises:

4. The method of claim 3, wherein, for each component tag, according to a component type of the component tag, calling a target component for the form item from a target component library, wherein the target component library comprises a general component library or a custom component library; and rendering the target component according to the component configuration information to obtain the form item on the information entry page. The displaying the information entry page based on a preset display mode according to configuration information for the to-be-filled form comprises:

5. The method of claim 3, wherein, for each form item, outputting, via the information entry page, a question for obtaining entry information of the form item according to a component tag of the form item and component configuration information of the component tag. Each candidate form has a candidate intent; 6. The method of claim 2, wherein, The determining, according to the trigger information, a to-be-filled form matching the trigger information from at least one candidate form comprises: determining a target intent according to the trigger information and a preset information set of at least one candidate intent; and determining a candidate form having the target intent as the to-be-filled form. The determining a target intent according to the trigger information and a preset information set of at least one candidate intent comprises one of the following modes: performing keyword matching of the trigger information with a preset information set of each of the at least one candidate form to obtain the target intent; or 7. The method of claim 6, wherein, inputting the trigger information into an intent recognition model to obtain the target intent, wherein the intent recognition is trained using at least one candidate intent and a preset information set of each candidate intent. ​ ​ ​ 8. The method of claim 3, further comprising, before the displaying the information input page based on the preset display mode according to the configuration information for the to-be-filled form: for each of the component tags, in a case where the historical information corresponding to the component tag is included in the historical interaction information of the user identifier of the trigger information, taking the historical information corresponding to the component tag as the input information of the form item; and in a case where the historical information corresponding to the component tag is not included in the historical interaction information, obtaining the input information of the form item via the information input page.

9. The method of claim 2, further comprising, after the displaying the information input page for the to-be-filled form based on the to-be-filled form matched with the trigger information: in response to receiving initial input information for each of the form items, performing verification on the initial input information according to a verification rule for the form item to obtain a verification result; and in response to the verification result representing that the initial input information passes the verification, determining the input information according to the initial input information.

10. The method of claim 2, wherein, the candidate form is generated by: in response to receiving a form generation request of a front-end page, generating an initial form by using form configuration information input by a form configuration page; in response to detecting that at least one target component in a plurality of candidate components is triggered, generating a form item of each of the at least one target component by using at least one component configuration information input by a component configuration page; and and generating the candidate form according to the initial form and the form item of each of the at least one target component.

11. The method of claim 10, wherein, the front-end interface includes a component display area, a preview area, and a configuration area; the method further comprises, before the generating the initial form by using the form configuration information input by the form configuration page: in response to receiving the form generation request, displaying the form configuration page in the configuration area; and in response to detecting a user operation on the form configuration page, obtaining the form configuration information; the method further comprises, before the generating the form item of each of the at least one target component by using the at least one component configuration information input by the component configuration page: in response to detecting that the target component in the component display area is triggered, displaying the component configuration page in the configuration area; and in response to detecting a user operation on the component configuration page, obtaining the component configuration information.

12. The method of claim 11, wherein, the component display area is used to display a plurality of candidate component tags, and the preview area is used to display the at least one target component; the generating the form item of each of the at least one target component by using the at least one target component configuration information input by the component configuration page comprises: in response to detecting that a target component tag in the plurality of candidate component tags is triggered, displaying a target component of the target component tag in the preview area and adding the target component tag to a first list, wherein the first list is used to record target component tags of the at least one target component respectively; and in response to detecting that a current component in the at least one target component is triggered, adding a component tag of the current component to a second list and obtaining component configuration information of the target component in the component configuration page, wherein the second list is used to record the current component selected in the at least one target component.

13. The method of claim 12, wherein, The type of the candidate component includes a general type and a custom type. The displaying of the target component of the target component tag in the preview area includes: in a case where the type of the target component is the general type, invoking a general component library to display a form item for the target component in the preview area, wherein the component types in the general component library include at least one of the following: an input type and a selection type; and in a case where the type of the target component is the custom type, invoking a custom component library to display a form item for the target component in the preview area, wherein the component types in the custom component library include at least one of the following: a tree structure type and a map type.

14. The method of claim 13, wherein, in a case where the component type is the selection type, The method further includes: defining a data dictionary, wherein the data dictionary includes at least one component tag of each of the selection type components and a plurality of options of each of the component tags; The displaying of the form item for the target component in the preview area includes: invoking the plurality of options of the component tag from the data dictionary according to the component tag of the target component; and rendering the form item for the selection type target component according to the plurality of options.

15. The method of claim 10, wherein, The form configuration information includes a form name, a form description and an intelligent customer service option; in response to the intelligent customer service option being turned on, displaying a scene configuration area in the form configuration page; and via the scene configuration area, obtaining a preset information set for the candidate form, wherein the preset information set includes at least one preset vocabulary and at least one preset sentence for an application scenario of the candidate form, the preset vocabulary is used for coarse matching of the trigger information, and the preset sentence is used for fine matching of the trigger information. The candidate form includes at least one component tag and component configuration information of each of the component tags; 16. The method of claim 10, wherein, The method further includes, after the generating of the candidate form according to the initial form and the form item of each of the at least one target component: for each of the component tags, taking the component tag as a key and the component configuration information of the component tag as a value to obtain a key-value pair of the component tag; and storing the candidate form and the configuration information based on the at least one key-value pair in a data source.

17. An information processing apparatus, comprising: ​ ​ The display module is configured to, in response to receiving the trigger information, display an information entry page for the to-be-filled form based on the to-be-filled form matched with the trigger information. and The obtaining module is configured to, in response to obtaining respective entry information of at least one form item in the to-be-filled form via the information entry page, fill in the to-be-filled form by using the respective entry information of the at least one form item, and obtain a target form. 18.An electronic device, comprising: one or more processors; a memory configured to store one or more instructions, wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1 to 16. 19.A computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to implement the method of any one of claims 1 to 16. 20.A computer program product, comprising computer-executable instructions that, when executed, implement the method of any one of claims 1 to 16.

Images