GA Release - 4.0.94

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

 

Breaking Changes

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 on the user's detail page. Now, it is fixed.

Survey

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

Old UI

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.

  • The valid and invalid text can be set in the Single Input control > General tab > Validation tab.
    When the Input Validator Type is set as anything other than “None”, after validating the user input, the Valid text or Invalid text will be displayed to the user.



    Previously, if the Input Validator Type is set as “None”, the Valid text from the Validation tab (if present) is getting appended to the Say/Chat text. Now, if the Input validation type is set as “None”, the Valid text will not get appended to the Say/Chat text.

Answers v2 (Previously known as 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 was not accessible. Now, you can use the “Clear All Filter” button to clear the previously selected filters.

     

  • You can now access Answers v2 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 v2 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 automatically in the KB listing screen. The Tooltip 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 logging out of the Engage Portal.

Release 4.0.94

  • Build 4.0.94-1637120300

Patch Fixes

Build 4.0.94-1638972359

  • Previously in Answers v2, when importing a large content, the import happened for a smaller set of data only. This is not fixed.

  • Previously when we try to Regenerate Key in the Register Application> Choose Application> Edit, the system was throwing an “Application not found” error. This is handled. The Admin user and the respective user who created the application can do this action.

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.