Configure subflow conversational settings
Configure conversation settings to make a subflow available to conversational interfaces.
Before you begin
Role required:
- admin or flow_designer
- now.assist.creator
Procedure
Navigate to All > Process Automation > Workflow Studio.
On the homepage, select Subflows.
From the list of all subflows, select the subflow that you want to configure.
From the side panel, open Conversational settings (
Option on the side panel to open conversational settings.\).
Select the skill that you want to edit, or create a new skill.
Configure the general settings.
Example general settings for the Send SMS subflow.
| Field | Description | |
|---|---|---|
| Generate skill metadata | Option to generate descriptions for the conversational skill, inputs, and outputs of the subflow by using generative AI. Workflow Studio generates a description for all the inputs and outputs where the description is empty. Regenerating the descriptions does not overwrite existing descriptions of any of the fields. Tip: This field is disabled if none of the description is field is empty. The AI-generated fields are marked with the AI icon Image omitted: icon-ai-generated.png .No alternative text supplied | |
| Is conversational | The option to make the subflow available to conversational interfaces. When enabled, you can call the subflow from a conversation through the skill. | |
| Subflow skill name | The name that a virtual agent displays for the skill in the list of available topics. | |
| Subflow skill description | The search terms and keywords that someone might use in a conversation to call this subflow. The more descriptive the skill, the better AI Search can be in matching it to an utterance. 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 Image omitted: generate-skill-metadata-icon.png Assistants where subflow is discoverableGenerate skill metadata icon..</td></tr><tr><td> | The list of virtual assistants where this subflow is discoverable. |
| Roles which can access this | The roles you must have to access this subflow from a conversation. Use the condition builder to specify the roles who can access the subflow.During a conversation, the subflow displays the skill only to users who have the specified roles. You must specify the role in the subflow settings and in the Conversational settings. By default, users must have the sn\_conv\_fa.csa\_email\_write role to create records in the sys\_email table. |
- Configure the subflow inputs and outputs.
Example inputs and outputs of the Send SMS subflow.
| Field | Description | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Show/hide checkbox | Controls the visibility of an input or output in a conversation. Select the checkbox if you want to make the field visible in the conversation. Image omitted: conversational-input-checkbox-z.png For 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. For a mandatory field, the checkbox is disabled until you specify a default value.Option to select the visibility of inputs in a conversation. | ||||||||||||||||
| Conversational inputs | The list of subflow inputs that are available to conversational interfaces. | ||||||||||||||||
| Describe this input | The 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 Image omitted: generate-skill-metadata-icon.png Default valueGenerate skill metadata icon..</td></tr><tr><td> | Provides a default value for the conversational input.During a conversation, users can provide their own value or proceed with the default value. Tip: You can pass an input value without user interaction by assigning a default value and making the input field hidden. | |||||||||||||||
| Override with reference | The 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. This option is available for inputs with the Email, GUID, Integer, Long, Long Integer String, String, and String (Full UTF8) data types. 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. Turning on this option displays the Table and Reference field options. | ||||||||||||||||
| Table | The 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. | ||||||||||||||||
| Reference field | The 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 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. Image omitted: example-input-string-user-name-01.png Example conversation where a string input shows a list of user names to choose from.</p> For more information about display values and reference fields, see Display values. 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. Image omitted: reference-field-filter-z.png Conversational outputsOption to apply filter for records in the Reference field.</p></td></tr><tr><td> | The list of subflow outputs that are available to conversational interfaces. | |||||||||||||||
| Describe this output | The 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 Image omitted: generate-skill-metadata-icon.png Generate skill metadata icon..</td></tr></tbody>
Image omitted: conversational-subflow-advanced-setting-z.png Example advanced settings for the Send SMS subflow.
Parent Topic:Building subflows |