...

Experience Manager

Answers v2

• The design for locking the ability to lock a question is updated to show the User user details.

  

• The Answers v2 KB can now export Labels along with the KB data. The Labels Sheet Questions sheet within the exported Excel file will have the KB data and its relevant Labels. The Labels sheet within the exported Excel file will have all of the Labels in the project and the Questions Sheet will have KB data and relevant Labels.

  Image Removed

  The Search functionality inside a KB . Going forward, the data export/import actions will use the .xlsx format only.

  Image Added

• The .xlsx file structure:

  • 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 in common. Other new properties will be ignored in the target location during importing.

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

  • Excel file header reference:

• The search functionality is extended to search using the Labels, the data in Voice/ Text/ Screen/ Buttons, Question variationsVariations, Intent ID and the content Content ID.

...

• In For Answers v2, there are some changes done as part of the v4.0.98 Patch updates patch updates which are also available in v4.0.100. Please refer to them in https://orbita.atlassian.net/wiki/spaces/OCS/pages/2143092942/GA+Release+-+4.0.98#Answers-v2.1 The changes are available in v4.0.100 as well. Please refer to them.

Flow Studio

• Hide Message Bubble- This new option is available only for Text box input type in allows for accepting input utilizing a Single Input control . Check this checkbox if you need to hide the Single input control in the chatbot. By default it is unchecked. This overrides all the other options in the Text box input type ie. Hidden, Single line, and Multiline.

...

• with NO output rendered to prompt the user. You can find this in the Single Input control. This is useful in scenarios where the expectation is that an indicator is presented via another mechanism, such as when using a hook that renders HTML5 directives or Adaptive Cards. In these scenarios, instructions for input are generally provided with the mechanism itself, making the additional bubble redundant.

  In previous versions of the platform, when you had a hook & Single Input combination, both controls would be rendered, presenting an additional message bubble with every hook rendered. More information in https://orbita.atlassian.net/wiki/spaces/OCS/pages/1659830303/3.3.9+Flow+Studio+Controls#Single-Input

...

• The formatting of the Bot now formats the input types for date and phone number input type while getting inputs from the User in a chatbot is made better now. in a more intuitive way. For example, if the user

...

• inputs 9876543210, it will be formatted as +1 (987) 654-3210

...

• . For dates,

...

• if the user inputs

...

• February 9 2022, the bot

...

• displays in the format 02/09/2022

...

• Newly introduced an .

• In the Link Flow control, a new option called “Enable continuation of flow after completion“ in the Link flow control is introduced. This will allow allows the users to jump seamlessly between the flows. More information in https://orbita.atlassian.net/wiki/spaces/OCS/pages/1659830303/3.3.9+Flow+Studio+Controls#Link-flow

  

• One Output output pin- This new option is available in the Choose One and YesNo control> Yes/No controls under the Choice tab. A new section to choose the number of output pins to display for the control is added. The new option, One Output output pin will render only one output pin from the control in the flow studio canvas rather than showing output pins equivalent to the number of choices. Flow Studio canvas. This option lets the user connect the out pin of Choose One or Yes/No to the next control easily. This will be helpful where the flow is the same regardless of the chosen option.

By default, One output pin per option will be selected

...

...

as previously set. This will give us output pins equal to the number of choices in the control.

...

• When loading the Flow Studio listing page, the sorting was not working correctlyproperly. This is handled has now been resolved.

• The Agent control in the flow studio now supports the Answers V2 v2 KB. After choosing the v2 KB, we should choose the Primary question. In case we have v1 KB in the project, we will be able to choose the v1 KB in the Select Answers dropdown itself.

  Image Removed

  Regards to the Flow studioWe will continue to support Answers v1 KB. More information on the Agent control is available here https://orbita.atlassian.net/wiki/spaces/OCS/pages/1659830303/3.3.9+Flow+Studio+Controls#Agent

  Image Added

• In regards to the Flow Studio, there are some changes done as part of v4.0.98 Patch updates which are also available in v4.0.100. Please refer to them in here https://orbita.atlassian.net/wiki/spaces/OCS/pages/2143092942/GA+Release+-+4.0.98#Flow-Studio The changes are available

Chatbot Settings

• We have updated the Default Bot Settings in v4.0.100 as well. Please refer to them.

...

• . When upgrading the platform to v4.0.100, other existing copies of the Default Bot settings of v4.0.98 will be renamed ‘Default legacy'. The reference made in the Bot Provider OE node will not be changed by the system.

• All Chatbot Settings (Settings, Custom CSS, Custom JS and Header) are editable except the Template. To update the Template settings, we should make a copy of the Default Chatbot settings file.

• Previously when copying the Default chatbot Chatbot settings, the Header content was not copied. This is handled has now been resolved.

• For Chatbot Settings, there are a few changes done as part of v4.0.98 Patch updates which are also available in v4.0.100. Please refer to them here https://orbita.atlassian.net/wiki/spaces/OCS/pages/2143092942/GA+Release+-+4.0.98#Chatbot-Settings The changes are available in v4.0.100 as well. Please refer to them.While upgrading the platform to v4.0.100, other existing copies of the ‘Default’ bot settings of v4.0.98 if present, will be renamed as 'Default legacy'.

Package Solutions

• Auto indexing of content will happen when installing the Solution packages. Previously, this indexing process was done manually after the installation.

Experience Designer

Chatbot v3

• For chatbot v3, there are a few changes done as completed in the v4.0.98 patch updates . The changes which are also available in v4.0.100 as well. Please refer to them . in https://orbita.atlassian.net/wiki/spaces/OCS/pages/2143092942/GA+Release+-+4.0.98#Chatbot-V3

• Now, by using the property send_advance_message, we can pass different Value and Text data in the hook function. A simple use case will be in a Button action where the display text and the value passed to the backend can be different now. Similar This is similar to the submitQuery property in the v2 bot.

Sample code snippet

self.parent.OrbitaChatBotV3.hook('send_advance_message', `You chose an appointment for ${WEEKDAYS[formattedDate.getDay()]} ${MONTHS[formattedDate.getMonth()]} ${formattedDate.getDate()}, ${formattedDate.getFullYear()} at ${selectedTime}`, null, {
        date: selectedDate,
        time: selectedTime,
        timezone: timezone
    });

Package Solutions

• Auto indexing of content will happen when installing the Solution packages. Earlier this indexing process was done manually post the installation.

...

• The Go Back feature is implemented for the Flow Studio controls, Adaptive Card, Carousel, Card list, and the HTML Directive. To know more on the Go Back feature, refer to this How to enable go back feature in Flow Studio

Release 4.0.100

Build number: 4.0.100-1645641079

Patch 4.0.100

Build number: 4.0.100-1647291926

General fixes

• We have now corrected the "Skill publish error" on the Deployment page.

• When utilising the CLI export/import tool, there was an issue with the Link nodes connection.
  This has now been resolved.