| \n\nShow/hide checkbox\n\n | \n\nControls the visibility of an input or output in a conversation. Select the checkbox if you want to make the field visible in the conversation.\\[Omitted image \"conversational-input-checkbox-z.png\"\\] Alt text: Option to select the visibility of inputs in a conversation.\n\nFor example, you can take the message text as an input from the user during the conversation or you can have a default text and hide the input field during the conversation.\n\nFor a mandatory field, the checkbox is disabled until you specify a default value.\n\n |
| \n\nConversational inputs\n\n | \n\nThe list of subflow inputs that are available to conversational interfaces.\n\n |
| \n\nDescribe this input\n\n | \n\nThe search terms and keywords that someone might use in a conversation to set this input. The more descriptive the input, the better AI Search can be in matching it to an utterance. You must provide a description for mandatory inputs. **Tip:** You can enter the description manually or use generative AI. To generate the description with generative AI, make sure that the field is empty and select **Generate skill metadata** \\[Omitted image \"generate-skill-metadata-icon.png\"\\] Alt text: Generate skill metadata icon..\n\n |
| \n\nDefault value\n\n | \n\nProvides a default value for the conversational input.During a conversation, users can provide their own value or proceed with the default value.\n\n**Tip:**\n\nYou can pass an input value without user interaction by assigning a default value and making the input field hidden.\n\n |
| \n\nOverride with reference\n\n | \n\nThe option to look up and insert an existing value from a selected table and reference field. Rather than require users to manually type in a value, this option allows users to select from a list of existing record values. When run, the input uses the value that the user selected from the list.\n\n This option is available for inputs with the Email, GUID, Integer, Long, Long Integer String, String, and String \\(Full UTF8\\) data types.\n\n**Note:** The Document ID and Reference data types are not valid options, because the system automatically overrides these input types with a list of display values as defined by the table's reference field. For more information about display values and reference fields, see [Display values](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_DisplayValues.md).\n\n Turning on this option displays the **Table** and **Reference field** options.\n\n |
| \n\nTable\n\n | \n\nThe table containing the reference field that you want to use to display a list of existing values. For example, the User \\[sys\\_user\\] table contains string fields to select a user by name.\n\n |
| \n\nReference field\n\n | \n\nThe field whose existing record values you want to display as a list of options. This input displays a list of options based on the reference field's data type. The data type of the reference field you select should match the data type of the input. Select a field that contains both meaningful and unique values. For example, if you have a string input for user names, then select a string field such as name from the User \\[sys\\_user\\] table. In a conversation, the input displays a list of string user names to choose from such as `Abel Tuter` or `Beth Anglin`.\n\n**Note:** This option is not available for inputs with the GUID data type, because each table already has a unique field that stores its Sys ID value.\n\n \\[Omitted image \"example-input-string-user-name-01.png\"\\] Alt text: Example conversation where a string input shows a list of user names to choose from.\n\n For more information about display values and reference fields, see [Display values](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_DisplayValues.md).\n\n You can use condition in the filter to limit the records that are referenced in this field. The filter helps you reduce the number of records from the referenced table and provide the most relevant options in the conversation.\n\n \\[Omitted image \"reference-field-filter-z.png\"\\] Alt text: Option to apply filter for records in the Reference field.\n\n |
| \n\nConversational outputs\n\n | \n\nThe list of subflow outputs that are available to conversational interfaces.\n\n |
| \n\nDescribe this output\n\n | \n\nThe search terms and keywords that someone might use in a conversation to set this output. The more descriptive the output, the better AI Search can be in matching it to an utterance. You must provide a description for mandatory outputs. **Tip:** You can enter the description manually or use generative AI. To generate the description with generative AI, make sure that the field is empty and select **Generate skill metadata** \\[Omitted image \"generate-skill-metadata-icon.png\"\\] Alt text: Generate skill metadata icon..\n\n |
\n