The list below represents the features, updates, and fixes included in the Orbita Voice GA Release for December 2021.

...

Breaking Changes

• Chatbot v3: The Users using the OE Template node to render the v3 bot should follow the changes provided. More information is in the sections below.https://orbita.atlassian.net/wiki/spaces/OCS/pages/edit-v2/2105049233?draftShareId=03d4f725-90f8-4cc3-8772-0c8b788c54a8#Chatbot-2105049233/GA+Release+-+4.0.96#Chatbot-Settings

https://orbita.atlassian.net/wiki/spaces/OCS/pages/edit-v2/2105049233?draftShareId=03d4f725-90f8-4cc3-8772-0c8b788c54a8#Chatbot2105049233/GA+Release+-+4.0.96#Chatbot-v3

• Engage FAQ Hub: The JWT token is moved to the cookie storage instead of the local storage to improve the security standards. The token handling method is now modified in the OE Template nodes. More information is in the section below. https://orbita.atlassian.net/wiki/spaces/OCS/pages/edit-v2/2105049233#Engage/2105049233/GA+Release+-+4.0.96#Engage-FAQ-Hub%3AHub

Core Product Modules

Experience Manager

...

The newly added Template section should have the HTML template for the v3 bot. More information in https://orbita.atlassian.net/wiki/spaces/OCS/pages/edit-v2/886472777#Template-Header886472777/Chatbot+Settings#Template

• We have added the capability to have custom OE_HTTP_NODE root defined at the environment level. The default value is /oeapi

...

• Clicking on the Label header will sort the Labels A-Z on the first click and Z-A on the next click. This sorting will apply even if there is any filter applied on to the content.

• We can add a custom Answer v2 schema now. We can create a new custom schema using the Develop > Schema Menu in the left Navigation. (Check How do I create Schemas?for support). This schema can be referenced while creating the KB in Answers v2 under the drop-down ‘Type of Knowledge Base’.

  

• When all the Answers have been populated in a KB, we would see '0 Missing Answers’ displayed against the Answers header.

...

• The botSettings property has been added to the Template node which helps in selecting the v3 chatbot setting. botSettings: { elementId: 'orbitabot', template: 'default' }

• For existing users who do not use the botSettings functionalities, we must add the botSettings: false in the template node code and have botContainerId: 'bot-v3'

• if the user wants to use the botSettings functionality, they must change the below properties

  Code Block
  botContainerId: 'chatWindow' botSettings: {elementId: 'orbitabot',template: 'default'}

• isCustomUi property is removed. All the element Id properties are made optional. If not specified, default values will be set.

• More information in https://orbita.atlassian.net/wiki/spaces/OCS/pages/edit-v2/1994555401#Template1994555401/Chatbot+V3#Template-node

Engage FAQ Hub

Existing users using the Experience Designer > Engage Manager Tab or Engage Manager v2 Tab please make the appropriate code changes in the Template nodes as given below. For new users and when we take built-in flows freshly, the changes will come with the flows by default.

...