...

• Contextual information about the page where the bot is embedded will be included in the Bot data. The x-orbi-headers property under msg.req.context property headers can be used to get these facts. Information on the Query This property stores information about the query string, IP, Cookie, Headers, User-Agent, Session etc. are captured in this property.

...

• , and so on. The content header object is accessible using msg.alexaRequest.getContextParams() as well.

To get a specific property we can define that as msg.alexaRequest.getChatParameters("x-real-ip")

...

• Similar to the v2 bot, the keyboardPlaceholderText property in the ChatBot settings may be used to control the placeholder for keyboard input. Jira Legacy

  server	System JIRA
  serverId	29f4e8cf-6a01-3d48-be4c-d6978b973292
  key	PD-3343

  Image RemovedFeedback system with Thumbs Image AddedImage Added

• The thumbs up/down feedback method is now supported in the bot Bot v3. More info information is provided available here. How to use the Feedback (Thumbs Up/Down) feature Jira Legacy

  server	System JIRA
  serverId	29f4e8cf-6a01-3d48-be4c-d6978b973292
  key	PD-1328

Flow Studio

• A Flow Studio flow being developed can be previewed now as a bot using the Preview the bot button from the Flow Studio canvas itself.

  Jira Legacy
  server System JIRA serverId 29f4e8cf-6a01-3d48-be4c-d6978b973292 key PD-3197

...

• The Bot v3 now has a redesigned user interface. This design adheres to the WCAG guidelines and uses semantic markup. The design is enabled by default in the default Chatbot settings, allowing us to automatically send upgrades to the default bot in future versions. To construct any bot, it's a good idea to make a duplicate of the default Chatbot settings.

...

Flow Studio

• Preview in Chat-Bot This button on the Flow Studio canvas may now be used to preview a chatbot flow under development. The Bot preview will open in a new tab using the Default Bot Settings in the project. In order for this functionality to perform properly, the Agent must be deployed.

  Image Added

  In the Experience Designer, the user must have the Flow Manager flow with Flow Group intent set up for existing projects. To support this functionality, a new Flow preview intent will be built. The Experience Designer flows will be configured automatically for new projects.

  Image Added

• The flows were malfunctioning when utilising Flow Studio Link node controls in conjunction with a Flow Manager node configured to not store data to Orbita. This has been taken care of.

• Domains with '_' can now be entered as Allowed domains in Application Settings.

• The phone numbers will be formatted in “+1 (XXX) XXX-XXX” US Canada format. This formatting will get applied only when the user has selected either Input Type as Phone number or selects Validator as Input Validator Type as Phone (US/CAN).

  Image Added

• The mustache tags used in the End Node control of the Flow Studio is being printed as tags themselves, instead of the actual value. This has been taken care of.