GA Release - December 2020

Owned by Rajkiran Alla (Deactivated), created
Last updated: Jan 04, 2021
6 min read

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

GA Release at a glance

Breaking Changes

  • The msg.payload.orbita.multimodal property will be deprecated from the next release (v4.0.78) due to its redundancy with msg.payload.multiagent property in the msg object while working with Answers Manager node in Experience Designer. Please consider using msg.payload.multiagent instead.

Experience Manager

  • The Profile options field type in Global menu > Provider (Settings) > Provider create/edit page is changed to JSON editor style.

  • Added a new field in Global menu > Organization (Settings) > Application setting. The Invite Token Expiration (Hrs) is the number of hours the forgot password token will be valid for. More info at https://orbita.atlassian.net/wiki/spaces/OCS/pages/7536905/How+do+I+set+up+Experience+Manager#Application-settings

Experience Designer

  • For the HTML directive, we have introduced two new properties:

    • id - This property helps to set the id value of the iframe.

    • renderBubble - This property defines how to render the html5 directive in the chatbot. If it is set to true, it will render the HTML content inside the chat bubble and if it is set to false it will render the HTML content outside of the chat bubble. By default, the renderBubble is set to true.

renderBubble: true

renderBubble: false

  • We have introduced a new directive removebubble that will allow developers to control message rendering in the chatbot.

    msg.payload.orbita.directive=[ { type: 'removebubble', direction: 'request', removeLast: true, // replaceLast : 'some html text' } ]

    removeLastBubble: Using this property, the developer can remove the last bubble when a response is rendered.

    replaceLastBubble: Using this property, the developer can choose to replace the content of the last message when a response is rendered.

If you choose to use both properties at the same time, only the replaceLast property will be considered.

  • Added a new checkbox to the Bot Provider V2 node that can record the chatbot conversations to the content data named “Transactiondata“.

New Nodes

  • Flow Group Intent: This intent will group all the auto-generated intents created for the utterances you add while creating/editing the Flow Studio.

Answers

  • While bulk importing topics, you can navigate to other pages to continue your work on the platform. The import will continue in the background.

  • As an admin user, the fact you are working on will be locked for other users to edit. If any other admin user tries to edit the locked fact, he/she will get a pop-up message where he/she can choose to force edit the fact by clicking on Continue.

  • You can now let chatbot users give their Feedback on the content displayed, using the feedback feature.

    To enable feedback, navigate to Answers > Settings > Advanced tab and toggle the Enable Feedback option.

  • In the relationship listing screen, the Relationships that are not mapped to a fact will have an “unused” label above their name.

Flow Studio

  • The flow studio history will capture the creation of flow studio only if the flow studio contains flow controls in it. The create action of flow studio is labeled as Update in the flow studio history.

  • While creating/editing a Flow studio flow, you can add utterances in the Utterances field.
    These utterances are grouped in an autogenerated intent. The intent can be accessed using the Flow Group Intent.
    You can add the Flow Group Intent to the Flow Manager node in the Experience designer to use these utterances to invoke the corresponding flow.

    Flow Group Intent node should be added to the Flow Manager node in the Experience designer to use these utterances to invoke a flow.

  • The yes/no responses are stored in the Flow Data with a checkbox.
    If the response is yes, the check box is checked.
    If the response is no, the checkbox is unchecked.

  • We have upgraded the Flow studio search. You can now search for flow name, description, flow-id, or flow content to get the corresponding flow studio flows in the search result.

  • A chatbot user can go to the previously answered question by saying utterances such as go back, skip back, and so on which will invoke the Inbuilt Previous Intent. For Single Input questions with the Free Text option enabled, the users were unable to go to the previously answered questions using these utterances.
    The Previous Intent is added to the Bypass NLP list of intents so that the utterances such as go back, skip back will not invoke the free text input event. The Previous Intent is instead used to render the previous question that the user had answered.

  • Added Restored to the Action list on the Flow History page.

  • For the same flow studio history record, you can see all the previous versions for restore, using the next and previous buttons on the upper right corner of the page.

Orbita Insights

  • You can track the Google Device ID and anonymous Chatbot user id in Insights at express.voiceAnalytics.voiceAgent.users.agentUserId and the Orbita user id at express.voiceAnalytics.voiceAgent.users.platformUserId

  • The data sent from the Orbita NLP node, Send SMS node, and Send Email Node can be captured in insights at the express.metric.event.

  • You can now capture and monitor custom properties in Insights. For more information, see https://orbita.atlassian.net/wiki/spaces/OCS/pages/873463935

  • A new visualization Engage - Dashboard Details [Beta] is created that visualizes data such as Most Used intents, Most visited flows, Unmatched Intent Utterances, Sessions by Visitors, Total Sessions, and so on.

Chatbot

  • Orbita will now generate unique user ids for anonymous users. These user ids will be stored as persistent cookies within the browser to identify anonymous users. The anonymous user ids can be found in the msg object at msg.payload.session.user.userId.
    The Logged in user ids can be found in the msg object at msg.payload.session.user.userId and msg.payload.session.user.currentUserId for consistency.

  • Added a new property startAlignmentTop to App settings to load the chatbot from the top. When this property value is set to true, the chat bubbles are loaded from the top of the chatbot first. For more App Settings properties, see https://orbita.atlassian.net/wiki/spaces/OCS/pages/886472777

General Improvements

  • Login button for chatbot V1 will not throw 504 Gateway Time-out error.

  • Keyboard navigation with tab key is extended to the Carousel, Scheduler, and filter screen.

  • Fixed the 504 error that occurs while importing Answers using CLI.

  • In some cases, indexing a knowledgebase is throwing an error. This is now fixed.

  • From this release, the Content Security Policy header is included in Static files.

  • The bug that doesn't allow importing answers knowledge bases that have more than 300 topics is now fixed.

  • When the user selects the textbox option in Flow Studio > Single Input Control > Directive Tab > Input type dropdown, the Hidden radio button is selected by default.

  • When invoking the Yes/no Intent, sporadically the platform failed to recognize the state assigned to it. This bug is fixed.

  • The search filter in the https://<domain-name>/apidoc is now working.

  • The Cookie property SameSite is set to 'Strict'.

  • The intents that were created as a part of the Generate intent per fact in KB option will be removed when this option is toggled off.

Engineering Notes

Additional technical information can be found in the Engineering Notes for each of the builds included in the GA Release.

Engineering Notes for Build 4.0.75

Engineering Notes for Build 4.0.76