AS A service administrator
I WANT to add field values to the intent declaration
SO THAT the intent declaration has all necessary fields to classify service intents
Instead of linking services created in the Service Module to Rasa intents in the Training Module, this new functionality allows services to be created and activated only using the Service Module.
Each service needs an accompanying intent declaration with the following fields:
id — machine friendly service name where all characters are lower case and words are separated by underscore (e.g. "company_contacts_service"). (not visible in backoffice)
name — human friendly name (e.g. "Company contacts service").
description — a brief summary of the functionality of the service (e.g. "This service returns the contact details of the requested company.").
examples — an array of examples which help the model to classify the service intent (e.g. ["can i get the contact details of the company", "what are the company contacts", "please give me the telephone number of the company"]).
entities — an array of entities to be extracted from the user query (e.g. "company_name"). this array can be empty if the API doesn't require any inputs.
text_for_embedding — a field which includes the description and all the examples separated by newlines (\n). (not visible in backoffice)
Acceptance Criteria:
Example JSON:
{
"id": "company_contacts_service",
"name": "Company contacts service",
"description": "This service returns the contact details of the requested company.",
"examples": [
"can i get the contact details of the company",
"what are the company contacts",
"please give me the telephone number of the company"
],
"entities": [
"company_name"
],
"text_for_embedding": "This service returns the contact details of the requested company.\ncan i get the contact details of the company\nwhat are the company contacts\nplease give me the telephone number of the company"
}
AS A service administrator
I WANT to add field values to the intent declaration
SO THAT the intent declaration has all necessary fields to classify service intents
Instead of linking services created in the Service Module to Rasa intents in the Training Module, this new functionality allows services to be created and activated only using the Service Module.
Each service needs an accompanying intent declaration with the following fields:
id— machine friendly service name where all characters are lower case and words are separated by underscore (e.g. "company_contacts_service"). (not visible in backoffice)name— human friendly name (e.g. "Company contacts service").description— a brief summary of the functionality of the service (e.g. "This service returns the contact details of the requested company.").examples— an array of examples which help the model to classify the service intent (e.g. ["can i get the contact details of the company", "what are the company contacts", "please give me the telephone number of the company"]).entities— an array of entities to be extracted from the user query (e.g. "company_name"). this array can be empty if the API doesn't require any inputs.text_for_embedding— a field which includes the description and all the examples separated by newlines (\n). (not visible in backoffice)Acceptance Criteria:
idfield is filled with snake casednamestring.text_for_embeddingfield is filled withdescriptionfollowed by "\n" and all examples fromexamplesseparated by "\n".Example JSON: