Nomenclature of auto generated Intents and Slots
This document will explain the nomenclature behind auto generated slots created in the Orbita platform.
Â
Modules:
While exporting the Project, the auto generated slots and intents do not get exported along with the Project export data. During import action in the destination project, these auto generated intents and slots are created.
Flow Studio
All the auto-generated intents of the Flow studio get created under the OrbitaFlowMessages
Intent.
We will only have one Slot called OrbitaMessages
which will include all the Slot values from all the flows. Every time we deploy, the system will rebuild the OrbitaMessages List from all the flows available.
When we create multiple flows, there will be respective flow studio lists created within OrbitaFlowMessages
Intent.
The Intent slots are defined likewise.
The OrbitaMessages Slot
There is also an option to add utterances when we create a flow. This will create another auto-generated intent using the nomenclature, FLOW_{{6 character token}}
.
When there are multiple flows created with utterances added to them, the system will create multiple intents in this nomenclature. These intents will have the utterances defined by the user.
Survey
All the auto-generated intents of the Survey get created under OrbitaSurveyMessages
Intent.
The individual Survey will have an individual List auto-created. The list follows the nomenclature, SURVEY_{{random 15 characters}}
. When multiple Survey is created by the user, multiple Lists gets created with the same naming convention.
Answers v1
While creating a Knowledge base, there is an option to create auto-generated intents. The system will generate a Knowledge base intent using the nomenclature OA{{KB name}}Intent
. The Topic, Relationship, and the Interrogatives defined are also mapped to this auto generated slot in this Intent.
The slots that are generated for the Topics, Relationships, and Interrogative use the nomenclature {{KB name}}_TOPICS
, {{KB name}}_RELATIONSHIP
, {{KB name}}_INTERROGATIVE
respectively.
The system also generates a second Intent called the Question intent and this is maintained in the Intents tab inside the Knowledge base Listing screen> Settings rather than the main Intents Library, for better management. Every fact with a question will have its relevant question intent.
The naming standard for this Question intent is {{KB name}}_{{6 character question token}}
. The special characters will be trimmed or replaced with an underscore ( _ )
Â
Answers v2
There are two intents created for Answers v2. Question intent and Label intent. Each primary question will have a corresponding Question Intent created in the Intents library. You can see the question intent ID created for a Primary question in the IDs section of a KB.
The question intent follows the nomenclature as {{KBToken}}_{{QuestionToken}}
The tokens are of unique 6 characters each. The question intents will have the KB name as a tag.
Â
Orbita creates one Label intent and one label slot per KB. The Label slot is mapped to the Label intent for that KB. The nomenclature for the Label intent is Label_{{KBToken}}
The KB token is the same 6 character value mentioned above.
Â