Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

While exporting the Project, the autogenerated auto generated slots and intents does not get exported along with the Project export data. During import action in the destination project, these autogenerated auto generated intents and slots are created.

Flow Studio

We have the option to create autogenerated intents while creating a Flow studio flow. All the autogenerated auto generated intents of the Flow studio gets created under 'OrbitFlowMessages' OrbitaFlowMessages Intent. Each flow will have its corresponding List created. the List follows the nomenclature, 'Flow_{{random 15 characters}}'. When we create multiple flows, there will be respective flow studio lists created within OrbitaFlowMessages Intent.

...

The Intent slots are defined like wise.

...

There is also an option to add utterances when we create a flow. This will create another autogenerated 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 autogenerated auto generated intents of the Survey gets created under OrbitaSurveyMessagesIntent.

...

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 standard.

...

While creating a Knowledge base in Answers v1, there is an option to create auto-generated intents. This The system will make the system generate an intent in generate a Knowledge base intent using the nomenclature , ‘OA{{KB name}}Intent. The Topic, Relationship, and the Interrogatives defined are also mapped to autogenerated slots in the 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 Intent Intents library.
You can see the Intent 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 Label intent and one label slot per KB. The Label slot is mapped to the Label intent for that KB. Each label you create will add a new line item in the label slot. Synonyms of a label are added to the respective slot line item as synonyms.

...

The nomenclature for the Label intent is Label_{{KBToken}} The KB token is the same 6 character value mentioned above.

...