| \n\nProperty\n\n | \n\nDescription\n\n |
|---|---|
| \n\nNode name\n\n | \n\nName that identifies this node in the topic flow.\n\n |
| \n\nVariable name\n\n | \n\nName of the variable that stores the user response to this prompt. The variable name is automatically created from the **Node name** property.\n\n |
| \n\nAllow automatic slot-filling\n\n | \n\nToggle to allow this node’s value to be automatically set by other nodes, as well as during topic discovery. When this toggle is activated, the Detail description field changes from dynamic Data Pill Picker and script options to a static text field.\n\n |
| \n\nDetail description\n\n | \n\nDescription of the information that you need from users. If the **Allow automatic slot filling** toggle is deactivated, you can create a dynamic detail description by selecting the Data Pill Picker icon \\[Omitted image \"variable-reference-picker.png\"\\] Alt text: to define conditions, or select the Open Editor icon \\[Omitted image \"icon-script.png\"\\] Alt text: to enter a script. If the **Allow automatic slot filling** toggle is activated, you can only enter a static description.\n\n \\[Omitted image \"LLM-input-discoverable-toggle.png\"\\] Alt text: When the Allow automatic slot-filling toggle is inactive, the detail description includes Data Pill Picker and script dynamic options. When the toggle is active, the Detail description field becomes static.\n\n |
| \n\nAdvanced\n\n | |
| \n\nEnforce user prompt\n\n | \n\nToggle to open a field for a custom message shown to the user instead of the message generated by the large language model \\(LLM\\). You can create custom messages in plain language, input a script, or define conditions with the data pill picker.\n\n |
| \n\nValidation\n\n | \n\nAdd a script to validate the user input. For example, check if the user entered a valid email address.\n\n |
| \n\nAdditional instructions for LLM\n\n | \n\nFurther instructions to the LLM, such as adding data formats, restrictions, or default values for user responses. You can create additional instructions in plain language, input a script, or define conditions with the data pill picker.\n\n |
| \n\nHide this node\n\n | |
| \n\nConditionally show this node if\n\n | \n\nNo-code condition statement or low-code script that specifies a condition for presenting this node in the conversation. The condition must evaluate to true.\n\n |
| \n\nAllow user to skip this node if\n\n | \n\nNo-code condition statement or low-code script that specifies a condition for letting users skip this node in the conversation. The condition must evaluate to true. You can set this field using either the condition builder or a script.\n\n If users enter a value such as `skip this step` when the conditions do not allow skipping, they receive a message saying the node cannot be skipped and are re-prompted to provide an answer.\n\n |
| \n\nInput properties\n\n | \n\nInput user prompt\n\n |
|---|---|
| \n\n\\[Omitted image \"va-boolean-llm-3.png\"\\] Alt text: All basic Boolean user input fields are openly available. Select any of the advanced options to toggle them open individually.\n\n | \n\n\\[Omitted image \"va-boolean-input-slack.png\"\\] Alt text: An example prompt reads, \"Would you like to add a comment?\" Answers are Yes and No.\n\n \\[Omitted image \"nass-boolean-user-prompt.png\"\\] Alt text: An example prompt reads, \"Would you like to leave a comment?\" Answers are Yes and No.\n\n |
| \n\nProperty\n\n | \n\nDescription\n\n |
|---|---|
| \n\nNode name\n\n | \n\nName that identifies this node in the topic flow.\n\n |
| \n\nVariable name\n\n | \n\nName of the variable that stores the user response to this prompt. The variable name is automatically created from the **Node name** property.\n\n |
| \n\nPrompt\n\n | \n\nPrompt or question for the user. The prompt can be either a text string or a script that returns text. This value is used only when the default value is not specified. For example: `What's your name?`\n\n |
| \n\nNLU entity\\[NLU topic discovery only\\]\n\n | \n\nOption to associate an NLU entity with the node. If an NLU entity is associated with the input variable for this node, Virtual Agent can slot-fill the specified value based on the user's utterance. Select an entity from the list of entities associated with the topic intent. When you specify an entity for the node, the Do not ask users to confirm recognized entity toggle switch is displayed. When enabled, users are not prompted to confirm the extracted entity.\n\n |
| \n\nAdvanced\n\n | |
| \n\nDefault value\n\n | |
| \n\nPredefine a value for user input\n\n | \n\nPredefined value for the user response to the question or prompt. The response defined in the **Default value confirmation** field asks the user to confirm the default value. If the user responds with `no`, the value becomes null. The default value can be either a text string or a script that returns text. For example, if you're using dot-walking, the default value might be: `Script Variables > Last username`. Or if you're using a script, the default value might be: `{{vaScripts.lastUsername}}`.\n\n |
| \n\nConfirmation messages\n\n | |
| \n\nInput completion confirmation\n\n | \n\nBot response shown to the user when the node interaction is complete. The message can be either a text string or a script that returns text. For example, if you're using dot-walking: `Thanks, (Input Variables > Username)!` Or if you're using a script, the acknowledgement might be: `Thanks, {{vaInputs.username}}!`\n\n |
| \n\nDefault value confirmation\n\n | \n\nMessage that asks the user to verify that the value in the **Default value** field is correct. This message is used instead of a value in the **Prompt** field. It can contain either a text string or a script that returns text. For example, if you're using dot-walking: `Are you (Input Variables > Username)?` Or if you're using a script, the confirmation message might be: `Are you {{vaScripts.lastUsername}}?`.\n\n |
| \n\nConversation switching\n\n | |
| \n\nThis section is available only when NLU discovery is enabled on the instance.\n\n | |
| \n\nTurn on to let users change the subject\n\n | \n\nOption to enable NLU prediction for this node. If enabled, users can enter text to answer questions, regardless of the type of input control being used. Virtual Agent uses this utterance to match another existing intent, letting the user switch topics.\n\n |
| \n\nHide or skip this node\n\n | |
| \n\nConditionally show this node if\n\n | \n\nNo-code condition statement or low-code script that specifies a condition for presenting this node in the conversation. The condition must evaluate to true.\n\n |
| \n\nAllow user to skip this node if\n\n | \n\nNo-code condition statement or low-code script that specifies a condition for letting users skip this node in the conversation. The condition must evaluate to true. You can set this field using either the condition builder or a script.\n\n |
| \n\nSkip reprompting if\n\n | \n\nNo-code condition statement or low-code script that specifies a condition for letting users skip reprompting in the conversation. When a preceding node is revisited through a topic loopback or Dialog Act, Virtual Agent bypasses this node and automatically retains its original value.\n\n |
| \n\nInput properties\n\n | \n\nInput prompt\n\n |
|---|---|
| \n\n\\[Omitted image \"va-boolean-properties.png\"\\] Alt text: Basic properties include the node name, prompt, and NLU entity.\n\n | \n\n\\[Omitted image \"va-boolean-input-web.png\"\\] Alt text: An example prompt reads, \"Would you like to add a comment?\" Answers are Yes and No.\n\n |
| \n\n\\[Omitted image \"va-boolean-input-slack.png\"\\] Alt text: An example prompt reads, \"Would you like to add a comment?\" Answers are Yes and No.\n\n |