GA Release - 4.0.96

Owned by Bharathi Manohar (Unlicensed)
Last updated: Jan 25, 2022
6 min read

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

 

Breaking Changes

https://orbita.atlassian.net/wiki/spaces/OCS/pages/2105049233/GA+Release+-+4.0.96#Chatbot-v3

Core Product Modules

Experience Manager

Chatbot Settings

  • Added the ability to have multiple sets of chatbot settings. Navigate to Develop > Chatbot Settings. A default bot setting will be available. We can also create a new Bot Setting. We can delete the User created bot setting but not the default bot setting.

The newly added Template section should have the HTML template for the v3 bot. More information in

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

Flow Studio

  • Evaluate node now has support to test for Null and not Null conditions.

  • Choose One Option node will have the type 'Default' preset when using the node in the flow studio. Further any new Choice added will also have the type 'Default' chosen as usual.

  • When the user saves their changes in the Flow, they will be able to continue working on the flow. They will not be redirected to the listing page like before.

  • For better user experience, the pins on the Yes/ No node have been changed. The Yes pin is on the left and the No pin on the right. This will not affect existing flows.

  • Previously while making changes in the Source code of the Voice tab or the Text tab of any Node that has an editor in it, the changes were not getting saved. Now it is fixed.

  • Previously when we use search in the Flow Studio listing page, it was fetching results from the Flow history page as well. Not it is corrected to bring results from the Listing screen only.

Answers v2

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

  • When we import a KB using a new custom schema, rather than its original type, we will only import the data for the properties that are common. Other new properties will be ignored in the target location during import. Refer

  • When we create a KB using a custom schema, the user-defined properties will be exported in customData.propertyName format. For example, If we have the properties firstName, and location in the custom schema, the exported CSV header will be

 

Project Import

  • While importing projects using a zip file, we will be shown options to choose which modules from the zip content need to be imported, just like how importing happens using the clipboard.

 

Calendar

  • Previously when creating an event in the Calendar, there were two events getting created after refreshing the Calendars listing screen. The issue is fixed.

Survey

  • Previously when a Survey was modified by a different User (Other than the one who created it) the user: property was not updated. Now it is fixed. The User who created will be found in createdBy: property.

  • Previously, a UI issue occurred when choosing the list & the grid view on the Survey Builder page. It's fixed now.

Lists

  • Previously in the Slot Types, when we import projects with flow studio and auto-generated slots, we were getting superscript tags on the slot names, similar to Answers v2. Now it is fixed. The slots imported as part of the Flow studio won't have any tags.

Deployment

  • Previously when the default intents are deleted, those will not be created again when deploying the Google agent. This is now fixed.

Experience Designer

Chatbot v3

  • 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

    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

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.

  • Engage Hub /hub/:name - FAQ Landing page

Please refer to the file above. The new changes are made in the last <script> tag below the <body>. Please make copy-paste this section or make relevant changes in your code if you have custom code.

 

  • Engage Hub Question /hub/:name/:question- FAQ Topics Landing page

Please refer to the file above. The changes are made in the last <script> tag below the <body>. Please make copy-paste this section or make relevant changes in your code if you have custom code.

Adaptive cards for v3 chatbot

  • The chatbot v3 will support Login using Adaptive cards. Additionally, v3 will support the success call back function.

For more information read through

Release 4.0.96

  • Build number: 4.0.96-1639690288

Patch 4.0.96

  • Build number: 4.0.96-1642548506

  • Chatbot v3: Added the capability to trigger Adaptive card submit action with event name for chatbot v3

  • Previously, the custom templates/ buttons etc. were rendered within the chatbot bubble. This is now fixed and will not come inside the bubble.