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

Core Product Modules

Experience Manager

Import/Export

• Previously, the project export json did not contain the content data and data part. Now, the project export json contains the content data and data part.

Global Settings and User Profile menu

• Previously, the admin user is unable to set a password for the user in the user's detail page. Now, it is fixed.

Survey

• The survey UI is updated to align with the new UI.

Flow Studio

• Previously, in the Agent control, the topics field is getting disappeared when trying to add a mustache tag. Now, this is fixed.

• Previously, in the Flow studio history listing page, the scroll is not working. This is now fixed.

Answers vNext

• Previously, the page count resets after navigating to the next page. Now, the page count retains the user selection even after navigating to the next pages.

• Previously, the “Clear All Filter“ button from the filter window is not accessible. Now, you can use the “Clear All Filter” button to clear the previously selected filters.
  

  Image Added

• You can now access Answers vNext payload at msg.payload.orbita.answers.

• Previously, the build page is empty after importing the questions in a newly created/already existing KB. Now, the build page will be filled with the respective questions after the import.

• Previously the Search field in Answers vNext had auto complete enabled which caused UI issues. Now 'autoComplete' is turned off for all Search fields.

• Previously a long KB title was getting truncated. Now, the long title will be wrapped in the KB listing screen. The Tool tip is removed since it is redundant now.

• The order in which the Labels display in the Question and Answers detail page as well as the Build and Organize tabs will be the same now, in the same order the labels were created by the User.

Core Platform

Engage

• Previously, when the user logs out of the Engage Portal, they are redirected to the Login screen of the Experience Manager instead of Engage Portal Login Screen and the JWT token is not removed. Now, the JWT token is removed and the user is redirected to the Engage Portal Login Screen after he/she logs out of the Engage Portal.