Skip to main content

November updates

1. Studio

1.1 Options to publish selective flows and revert to previously released bot version

| New feature

  • Selective publish allows you to publish only selected flows from the flows you made changes to.
  • Revert option is available on the Live environment, it allows the admins to revert to any previously released bot version.
    Learn more here.

1.2 Search bar functionality is extended for Flows, FAQs, and Intents

| Enhancement

To avoid scrolling through different sections for finding the right flow/FAQ/Intent, Studio search bar is enhanced to supports Flows, FAQs, and Intent search apart from documentation search.


2. Marketplace

2.1 Option to export bot template to marketplace

| Enhancement

Export a single flow or multiple flows from the bot with the Export option available on the Studio page (home flow and other flow pages).

  • Export bot template: You can export the entire bot.
  • Export flow template: You can select the flows to be exported as a single template by providing details such as key features, channels supported, industry, description, etc.
  • Export FAQs: A toggle is added to choose if the template must be exported with FAQs.
  • Export table data: A toggle is added to choose if the template must be exported with selected database tables.
    Learn more here.

2.2 Option to import templates to private marketplace/ specific subscriptions

| Enhancement

Users can now export templates to:

  • Private marketplace: These templates will be visible and available for import only for the respective user (it will be hidden from the external users).
  • Subscription: Export templates to a marketplace with accessiblity only to members of a particular subscription. These templates will be visible and available for import only for the subscription users (it will be hidden from the other users).

2.3 Review and Publish templates process updated for private and public marketplace

| Enhancement

  • Private: The templates exported to a private marketplace will be published automatically without a review process.
  • Subscription: The templates exported for a subscription will be submitted for review and will be available on the export page (Profile > Exports). The admin of the subscription will be able to view, test, and publish the templates.
  • Public: The templates exported to the public marketplace will be submitted for review and will be available on the export page (Profile > Exports). The admin of the public marketplace will be able to view, test, and publish the templates.
    Learn more here.

2.4 View exported templates

| Enhancement

Details and status of the templates submitted for review will now be available on the Exports page (Profile > Exports).


3. Integrations

3.1 Live chat integrations are available on app.yellow.ai

| Enhancement

The live chat integrations can now be used on App bots, this allows app bots to leverage the same capabilities as cloud bots in terms of integrations supported.
Learn more here.

3.2 Multiple live agent integrations within a single bot

| Enhancement

While using the raise ticket node, the bot developer can chose any of the live chat service that are enabled on the integrations module.

3.3 Zendesk Sunshine integration available on the cloud

| New feature

Zendesk Sunshine Integration is now supported for executor-cloud bots.
Learn more here.

3.4 Custom Live agent integration v2

| Enhancement

Custom live agent was enhanced with the following features:

  • Ticket queuing.
  • Option to send the conversation that happened prior to connecting with the agent as a JSON file.
  • Adding additional user information (name and email) while sending messages/media files from user to agent.
  • A new field in the Raise ticket node for providing the group ID using which the ticket can be created and assigned to a specific group of agents.

3.5 Magento integration

| New feature

Magento integration is available for usage through GIF.

3.6 Sticky Agents for Salesforce Live chat

| Enhancement

Salesforce Live chat is enabled with Sticky agents (a type of ticket assignment where the customers can connect to an agent, of their choice i.e., agents they are familiar/have conversed with before).

3.7 Automated delivery report to WebEngage

| New feature

Previously, the delivery event was sent to the bot and the bot developer was responsible for using the action node to send the event data to WebEngage. Currently, this process is automated to avoid any unintended bugs and failures by the users.

3.8 Support for Nested Objects for Integration Action Nodes V2

| Custom Enhancement

Objects inside Objects are now supported for V2 Action Nodes.

3.9 Added code coverage

| Enhancement

Moving towards better code quality and assurance, boilerplate code coverage has been written for integrations which will be extended through more test cases.