Buttons that present options to the user are typically only shown for the current turn in conversation for which they were meant to be shown. Once the user clicks a button or moves the conversation forward through text or voice, the button options in the response are removed from the UI.
Under certain scenarios you can make some buttons or options remain permanently - regardless of the turn of conversation.
You can configure the map such that some custom request parameters are sent back to Teneo when a specific button is clicked. This might be useful for metadata reporting in Teneo Data or you might just want to trigger a flow based on the existence of a certain request parameter.
As before you can display buttons but you can optionally define custom icons shown in the buttons and you can optionally control what is sent back to Teneo as user input text. Therefore the button says one thing but the text that is sent back after a click could be something different.
Variable
def buttonIconOptions =["title":"Some UI Elements","items": [ ["name":"Form Button Text","text":"This is sent as user input","icon":"book-information-variant"], ["name":"Map Button Text","text":"Where are you located","icon":"google-maps"], ["name":"Youtube Button Text","text":"Tell me about your company","icon":"youtube"], ]]
The default color for buttons comes from the success theme color configured for the solution. If you want to change the color of a specific button you can define a color property in the json.
You can configure the map such that some custom request parameters are sent back to Teneo when a specific button is clicked. This might be useful for metadata reporting in Teneo Data or you might just want to trigger a flow based on the existence of a certain request parameter.