Form Message
This page describes where to use and find a form block message type
Last updated
This page describes where to use and find a form block message type
Last updated
The form message lets you create more complicated message inputs that are great for capturing structured information about the user use as addresses or full names.
Each form message has the follow properties:
Text: Form text can optionally be set and will be displayed at the top of the form message if set
Button text: The text to display on the submit button shown at the bottom of the form message.
Callback: Similarly to the 'simulate user intent' button messages, this field needs to be set to point to the next intent in the conversation flow. When clicked on, a list of all conversations for the current scenario is show listing each intent that is part of them. Either select the correct user intent, or create a new one using the drop down interface. See button message for more info
Validation: When creating your form message, you can also set validation for your input fields. There are two ways you can do this, through the regular expression for validation field, and through the error text for use with regular expression validation field. Both of these are optional, but are there if you wish to use them
Each form message can have as many fields as needed to capture the information required.
There are many different situations in which a form message would be used within an OpenDialog chatbot. For example, user registration. If you require your users to input their information, it is much easier to do this through having them fill out a form, rather than manually input all their text.
Navigate to the Message Editor and create a form block by clicking the Add form block icon in the Layout section.
Navigate to the Message Editor and create a Custom Message. Select form-message from the message type drop down menu and the XML Snippet field will automatically be populated with a code template.
Fill in the template with the properties of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
Open your OpenDialog application
Select the Scenario that you wish to edit
Select Design from the left hand panel and select Messages
Go into the message that you want to add a message block to
Add a 'Custom Message' block
Select 'Form message' from the drop down
Add in your own text to the fields you want to customise
To preview your message, go to the Preview section
Form messages allow for user to input data in standard web form rather than text entry. When submitted, the values entered by the user are sent back along with the defined callback. All form messages must contain the following elements:
Here, the text value is shown at the top of the form message and the submit_text value is shown on the form submit button. When auto_submit is set to true, the form will automatically be submitted when the user selects a value. This works best when just 1 element is added to the form
Elements
Form messages have support for a number of different elements (matching what is possible in a standard HTML form). All elements are defined in the same way, and there is no limit to how many can appear on a form message.
Each element must define a type and display, and can optionally define required and default_value. If required is set to true, the form cannot be submitted unless the field has a value.
When using checkbox or select elements, you must define an options block giving the options to be presented in the checkbox list or select element:
The email element type acts just like a text element, but on submission, is validated to ensure it is formatted like an email address
This form message example was created with the following XML:
Saves Message: Always remember to hit 'Save Message' before closing or navigating away from the edit screen
When a user fills out your form, you may be wondering where that data is kept/stored for you to be able to have access to.
When your user fills out your form, all of their information is added to the User Context. Each field that is available to fill out has an attribute. This means, that once the information is added, it is then added to that attribute for you to use and reference throughout the rest of your conversation. For more information on how to use and create attributes, click here.
When structuring a message, you are able to use multiple different message blocks together to create the message that you are looking for. However, when it comes to ordering and structuring these, there are some rules that need to be followed. To learn more about this, please head to the Constructing Messages page for more information.
You can only add one form message type to each message, and it should be the last message in the list to work properly.
For all message types, a key element to take into consideration is Accessibility, especially for messages that include customisation with multimedia types such as buttons, images and links. For all information on accessibility within OpenDialog, please click here.
