| \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\nInput format\n\n | \n\nText format that is validated when a user enters certain text items. If the user doesn't enter the expected format, an error message indicates that the format is not valid and asks the user to reenter the text. Choose the format of the text item to be validated:\n\n- Text: Any text string \\(no validation\\).\n- Email: Format that consists of an email prefix \\(user name\\), the @ symbol, and domain.\n- IP address \\(IPV4, IPV6\\): Data communication delivery format for Internet Protocol version 4 or version 6.\n- Phone number \\(E.164\\): Internationally recognized standard phone number format.\n- URL: Web address format.\n- Custom: A script that provides a validation rule for a custom text format. The script should include related error messages that are displayed when the expected format is not entered.\n\nFor phone and IP address format examples, see [E.164 phone formats](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/r_ConfigureE.164PhoneNumberFields.md) and [IP address field types](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/r-IPAddressFieldType.md).\n\n |
| \n\nNLU entity\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.\n\n 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\nMake this input secure\n\n |
| \n\nEnable\n\n | \n\nToggle switch that encrypts the input control. When enabled, the user input is masked and appears as a series of dots in the chat window.\n\n |
| \n\nHash function\\[Visible when Make this input secure is enabled\\]\n\n | \n\nThe method digest algorithm based on the standard WS-security standard. Choose one of the following:\n\n- **SHA-256 \\(lower case\\)**\n- **SHA-1 \\(lower case\\)**\n\nFor more information about the WS-security standards, see [WS-Security properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/ws-security-properties.md).\n\n |
| \n\nEncryption salt\\[Visible when Make this input secure is enabled\\]\n\n | \n\nRandom data that is used as an additional input to a one-way function that hashes data.\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\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\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