
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-13-2020 11:57 AM
Solved! Go to Solution.
- Labels:
-
Virtual Agent

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-13-2020 12:19 PM
These are called "Entities" in ServiceNow parlance and are created in the NLU model but utilized in VA Designer:
Entity extraction
With NLU models, Virtual Agent can determine when user statements in a conversation contain important information to fulfill a task or goal. Entities identify the information that Virtual Agent can extract from the conversation, such as an object or a person's name. To extract the appropriate values, Virtual Agent uses the entity information associated with an intent defined in the NLU model. The input controls that you add to your conversation also have associated NLU entity properties that you can set. Virtual Agent matches the extracted entity with the input control variable that fulfills or completes the action, and skips the prompts asking the user for additional information.
Here's the rest of that documentation: https://docs.servicenow.com/bundle/orlando-performance-analytics-and-reporting/page/administer/virtu...
Here's how to create an Entity in a model and here's how to implement Entities in user inputs in VA Designer:
Natural Language Understanding (NLU) entity properties
If NLU is enabled, the following properties display in the property sheet for the Text, Static Choice, Reference Choice, Boolean, Date Time, and Carousel input controls:
- Associated entity: The entity that corresponds to the input variable for the control. You select the entity from the list of entities associated with the topic intent, as defined in the NLU model you are using for the topic. When Virtual Agent recognizes the entity value in user utterances and the value meets the entity prediction confidence threshold, Virtual Agent extracts the value. It stores the value in the input variable for the node (slot filling).
- Enable NLU at Input Node: You can enable or disable NLU processing for a control. Selecting an Associated entity automatically activates the Enable NLU at Input Node switch. Users can enter text to select items or switch topics from this node when this switch is enabled.
- Skip confirmation for recognized entity: You can enable or disable prompts that ask users to confirm the extracted entity.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-13-2020 12:19 PM
These are called "Entities" in ServiceNow parlance and are created in the NLU model but utilized in VA Designer:
Entity extraction
With NLU models, Virtual Agent can determine when user statements in a conversation contain important information to fulfill a task or goal. Entities identify the information that Virtual Agent can extract from the conversation, such as an object or a person's name. To extract the appropriate values, Virtual Agent uses the entity information associated with an intent defined in the NLU model. The input controls that you add to your conversation also have associated NLU entity properties that you can set. Virtual Agent matches the extracted entity with the input control variable that fulfills or completes the action, and skips the prompts asking the user for additional information.
Here's the rest of that documentation: https://docs.servicenow.com/bundle/orlando-performance-analytics-and-reporting/page/administer/virtu...
Here's how to create an Entity in a model and here's how to implement Entities in user inputs in VA Designer:
Natural Language Understanding (NLU) entity properties
If NLU is enabled, the following properties display in the property sheet for the Text, Static Choice, Reference Choice, Boolean, Date Time, and Carousel input controls:
- Associated entity: The entity that corresponds to the input variable for the control. You select the entity from the list of entities associated with the topic intent, as defined in the NLU model you are using for the topic. When Virtual Agent recognizes the entity value in user utterances and the value meets the entity prediction confidence threshold, Virtual Agent extracts the value. It stores the value in the input variable for the node (slot filling).
- Enable NLU at Input Node: You can enable or disable NLU processing for a control. Selecting an Associated entity automatically activates the Enable NLU at Input Node switch. Users can enter text to select items or switch topics from this node when this switch is enabled.
- Skip confirmation for recognized entity: You can enable or disable prompts that ask users to confirm the extracted entity.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-13-2020 04:25 PM
Thanks a lot. All these articles are very useful. Once I reviewed them I realized I had to make sure I set the "Associated Entity" within the user input control. It is working now!
I can summarize that the steps to make it work are:
1. Create NLU model (Add utterances and entities)
2. Within the topic conversation flow, set the user input control to associate the entity by selecting the entity.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-19-2020 03:44 PM
Does anyone have the REGEX code for handling capitalization in an entity? Thank you!