Entities in Oracle Digital Assistant extract information from user messages based on patterns or values they represent. Users can have a natural conversation with a chatbot as they will only be prompted for information they have not yet provided. “I like a scoop of strawberry ice cream ” implies the intent (to buy ice cream), the flavor (strawberry) and the size (a scoop). The only prompt to display for this example would be “how would you like to pay?”. By various examples, this article explores and explains properties you can set on custom entities.
The Sample Skill (Starter Skill)
The starter sample skill you can download for this article contains a single entity “Pastas” and two dialog flow states. For the feature demonstrations in this article, there s no need for natural language processing (NLP). However, it is important to clarify that the functionality introduced in the following does work the same if intents and NLP are in the picture.
The dialog flow (image below) uses the System.ResolveEntities component to render the user interface. The System.ResolveEntities component doesn’t require a lot of properties to set and instead gets its property setting directly from the entity.
The System.Output component in line 22 has its text property set to an Apache FreeMarker expression that either prints a single value or multiple values (later more about this)
Note: that you could use the System.CommonResponse component instead of the System.ResolveEntities component. Read the complete article here.
For regular information become a member in the Developer Partner Community please register here.