Forms: More Than Just Tables, A Bridge for Conversation
DMflow.chat’s form function goes far beyond traditional forms. It allows you to create interfaces containing diverse components like text fields, tags, Markdown text, checkboxes, date pickers, file uploads, encrypted passwords, and reservation slots. More importantly, these forms can be directly integrated with chatbots to achieve a smooth “conversational form filling” experience.
Form Components Explained
When you click “Add” or “Modify” form, you enter the component layout interface. The order of components (from top to bottom) is crucial because it not only determines the display order of the form but also defines the order in which the bot collects data (Slot Filling) in the conversation.
Common Components List
| Component Name | Description & Use Case |
|---|---|
| Text Field | Standard text input box (<input>). |
| Tags | Tag field, allowing multiple tags in a single field, suitable for classification or keywords. |
| Textarea | Multi-line text input box, supports Markdown syntax rendering, suitable for long content. |
| Checkbox | Checkbox, stores boolean value true or false. |
| Radio | Radio button, suitable for mutually exclusive options. |
| DateTime | Complete date and time picker. |
| Date | Component for selecting date only. |
| Select | Dropdown menu, supports single or multiple selection. Advanced Function: Select component can integrate field data from other forms. Even more powerful is the support for “Linked Listening”, e.g., the first Select chooses “City”, the second Select automatically updates to “Towns” under that City. Note: The listened Select must be placed “above” the listener, the order cannot be reversed, otherwise the conversation flow may error. |
| Built-in Email format validation. You can also use Text Field with Regular Expression (Regex) to achieve the same effect. | |
| Upload | File upload component. Currently only supports filling via web form interface, does not support uploading files via chat window. It is recommended to use keywords to guide users. |
| Number | Built-in number format validation. Can also be replaced by Text Field with Regex. |
| Password | Password field. Can be used with Utils tools for encrypted storage and comparison validation. |
| Hidden | Hidden field, used to store system information without displaying to the user. Supported types: Constant (fixed value), Page Parameter (get from link field), Session Info (currently only supports userId). |
| Reserve | Reservation component. A single field contains keyword, start time, and end time. Limit: Start and end times must be on the same day, cross-day reservation is not yet supported. |
| Paragraph | Paragraph text. In the dialogue system, this will be directly output to the user as a bot text message, suitable as introductory or explanatory text. |
Form Presentation Example
** Internal Form Filling **
** External Form Presentation, this will apply the adjusted template for customers **
Form Permission Management
Data security is core. Our permission system is divided into two categories: “Guest” and “User”.
Permission operations include: Create, Read, Update, Delete.
| Role Type | Description | Typical Permission Setting |
|---|---|---|
| Guest | General public users from LINE, Messenger, IG, or Telegram. They usually interact with the bot via conversation. | Usually enable “Create” permission, and “Read data created by the user themselves”. |
| User | Registered users who have bound their DMflow account via links in various channels. | Can open more permissions according to business needs, such as updating or deleting their own data. |
Advanced Form Features
After creating a new form, the chatbot’s operation logic will also update accordingly. You can also set the following validation rules to ensure data quality:
- Required: User must fill in this field.
- Options: Input value must be in the default option list.
- Numerical Validation: Set time range, max/min value for numbers, and Regular Expression (Regex) validation for text.
