Using Context Variable as inputs
If you collected user input via the Data Collection block OR retrieved data via other Service Actions, then you can set the Input Type to "Context" to utilize data stored in the Context.
|  | |Using Text Value as inputs
If you want to use raw text as Input, you can set the Input Type to "Text Value".
|  | **5) Outputs** The Outputs specify the data that the Function can return after it is executed successfully. This is defined by the development team who built the Middleware Service. | There are 2 types of Outputs: | | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |Data Outputs
Referenced later using:
\
Display Outputs
Referenced in Dynamic Component using:
\
\
Quick Replies
Supports:
Button List
Supports:
Card
Supports:
Carousel
A Carousel is a series of Card components.
Minimum number of cards: 1
Maximum number of cards 10
|  | |Dynamic Component
Dynamic Component allows us to display dynamically generated Message Components returned by Service Actions
| For an example of how Service Actions and Dynamic Components are used together, please see [Building Transactional Flows](/taiger-converse/v2.7.0/advanced/building-transactional-flows.md). | #### **Button & Quick Reply Configuration Options** Buttons and Quick Replies provide prompts to the Chat User. Users can click on them to advance through the conversation. #### Button Types The Button Type allows Bot Admins to configure what clicking on the Button/QuickReply does. | **Type** | **Description** | | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Trigger State | Advances the conversation to the specified State within the same Intent's Flow | | Trigger Intent | Brings the Chat User to the specified Intent's Flow | | Send Postback | Sends text on behalf of the Chat User to the dialog engine. By default, the text sent is the same as the Button Name. Bot Admins can configure a custom text value that is different from the Button Name. | | Open URL | Opens a specified Web URL in a new browser window or tab. | | Open Webview | Opens a specified Web URL in a Webview, which is an overlay on top of the Chat Interface. | #### Button Concept Set an *Ontology Concept* on the Button to allow it to be triggered by Text Input. If a new Ontology Concept is created, the *Synonym Editor* will pop up. Bot Admins can define Synonyms of the Concept, which help the Bot match user inputs to the Ontology Concept.  When a Chat User sends an input that matches any Synonym of the Button's Ontology Concept, the Button is triggered as though it was clicked. If you want to change the synonyms, you can open the Synonym Editor again by clicking on the selected Concept Tag in the text input field (see below)  #### **Typing Delay** Each Component allows you to set a Typing Delay which simulates the Bot typing the response to the user. This delay allows Chat Users to read the previously displayed content before the new Message Component is displayed, and contributes to a better user experience. #### **Data Collection Block** Use this configuration to collect data from the Chat User. Data collected is stored in Variables in the [Conversation Context](/taiger-converse/v2.7.0/essentials/intent-and-dialog-building/conversation-context.md), and can be used in following States. | **Field Name** | **Description** | | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Variable | Specify the Variable Name to store the value captured from the user input. | | Variable Type |This is the type of the variable that validates and restricts the user input to specific types: Date, Number, and File.
File: Displays a file picker
Validation type Indicates the type of validation to be applied on the user's input.
There are 5 possible validation types to choose from.
For each of these types the following configuration options are provided:
Specify the number of attempts allowed.
Validation Message
(if validation type is selected)
| The message being displayed to the user if the value submitted is invalid. | |Basic Usage Example:
Scenario Collecting Email from a User
| | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | This configuration will store the Email in the **userEmail** variable |  | |In the following State, The you can utilize the stored Variable in the Content Editor by using the syntax:
%(answers.VariableName)
IF the chat user says \
IF the Service Call returned an error message
ELSE IF the numHits data property in the getHotelsApi Service call is exactly "0":
ELSE IF the numHits data property in the getHotelsApi Service call exists:
Available Comparisons\*
IF none of the Transitions in the State triggered
Set Context Variable to a Text Value
Example:
Set the variable favouriteCity to the Text value "BALI"
|  | |Set Context Variable to another existing variable (reassignment)
Example:
Set the variable userFirstName to the value in the variable answers.firstName
|  | #### **Dialog Settings** Dialog Settings allow Bot Admins to configure advanced dialog behaviors. These settings change the way the Dialog Engine behaves for the specific state. | Field | Description | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Jump Intent |If this is configured, then when this State is triggered, the Chat User is brought to the specified Intent's Flow.
We recommend using Trigger Intent functionality found in Button/QuickReply and Transitions (available in v2.6.0+).
Important Notes:
Default Value: true
\\
If true:
If false:
Default Value: true
Indicates whether the dialog engine should advance to the next State or stay in the current state.
|