Buttons and Lists

Leopard can show buttons and per line option lists in the Chat response.

Introduction

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.

Buttons

Output Parameter

If you wanted the buttons to persist and remain active for any reason then specify this output parameter:

If you wanted the buttons to persist and automatically disable after the conversation moves on.

Where yesNoMaybeOptions is a groovy map stored either as a flow or global variable

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.

JSON

Buttons with Icons

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

Output Parameter

If you wanted the buttons to persist for any reason then specify this output parameter:

JSON

Buttons with Colors

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.

Line Based Options

Output Parameter

If you wanted the buttons to persist and remain active for any reason then specify this output parameter:

If you wanted the buttons to persist and automatically disable after the conversation moves on.

Where yesNoMaybeOptions is a groovy map stored either as a flow or global variable

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.

JSON

Line Based Options - Background Color

If you want to change the background color of all the line based option then you can define a color property in the json.

Quick Button Format

If you just want to quickly produce some buttons then it might be easier to call simpleDisplayClickableList

Output Parameter

Last updated