Skip to content

Bot Framework SDK 4.9
Compare
Choose a tag to compare
@cleemullins cleemullins released this 12 May 19:09
4.9.0
1f4cef9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

May 2020 (version 4.9.0)

Welcome to the May 2020 release of the Bot Framework SDK. There are a number of updates in this version that we hope you will like; some of the key highlights include:

  • Skills - Skills now support adaptive dialogs and all activity types, and have improved support for SSO and OAuth. The v2.1 skill manifest is now GA. We also added Bot Framework Composer support for building and consuming Skills.
  • Microsoft Teams - Improvements in Microsoft Teams API support, including support in Java!
  • Bot Telemetry - Mapping of Dialogs into Azure AppInsights Page View Events.
  • Health Check APIs - Quickly verify a bot is running.
  • Adaptive Dialogs - A more flexible, event driven dialog system for implementing multi-turn conversational patterns.
  • CLI tools for Adaptive Dialogs - new ability to merge and validate adaptive schema assets.
  • Language Generation - Add language and personality responses to your bot conversations.
  • Adaptive Expressions - Use bot aware expressions to react to user input and drive bot functionality.
  • Authentication Improvements - SSO between Bots and Skills and improvements to X.509 auth.
  • Generated Dialogs (Early Preview) - Automatically create robust Bot Framework Composer assets from JSON or JSON Schema that leverage Adaptive Dialogs.
  • VS Code debugger for Adaptive Dialogs (Early Preview) - Create & validate .lu and .lg documents as well as debug declaratively defined adaptive dialogs.

Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build [C#] [JS] [Python] [CLI] and try the latest updates as soon as they are available. And for the latest Bot Framework news, updates, and content, follow us on Twitter @msbotframework!

Skills

Skills have been updated to work with adaptive dialogs, and both adaptive and traditional dialogs will now accept all types of activities.

The skill manifest schema has been updated to version 2.1. Improvements in this version include the ability to declare & share your language models, and define any type of activity that your skill can receive.

This release also includes authentication improvements with skills, including using SSO with dialogs, and OAuth without needing a magic code in WebChat and DirectLine.

Microsoft Teams

We continue to focus on making sure all the Teams-specific APIs are fully supported across our SDKs. This release brings full support for Microsoft Teams APIs in the preview Java SDK, including samples.

The OnTeamsMemberAdded event in the activity handler has been updated to use the get single member endpoint under the covers, which should significantly reduce latency and reliability of this event in large teams.

The TeamsChannelAccount object has been updated to include userRole (one of owner, member, or guest) and tenantId (for the user's tenantId).

Bot Telemetry

Bots now capture Page View events, native to Application Insights, whenever a dialog is started. This allows you to use the User Flows dashboard in Application Insights to see how users move through your bot, between dialogs and where they drop out.
Telemetry In AppInsights

Health Check APIs

Support was added for a new invoke named healthCheck that allows a sender to verify if a bot is responding to requests, and if trust can be established between the sender and the bot. The bot also has the option of overriding the response to add additional health information in the response.

Adaptive Dialogs

We’re also excited to make Adaptive Dialogs generally available in C# and as a preview release in JavaScript!

Adaptive Dialogs, which underpin the dialog design and management authoring features found in Bot Framework Composer, enable developers to dynamically update conversation flow based on context and events. This is especially useful when dealing with more sophisticated conversation requirements, such as context switches and interruptions. Bot Framework Skills can now also leverage Adaptive Dialogs.

Adaptive Dialogs also now support Telemetry. Data from Adaptive Dialogs, including triggers, actions and recognizers now flow into your Azure Application Insights instance.

CLI tools for Adaptive Dialogs

CLI tools for Adaptive Dialogs, Language Generation, QnaMaker and Luis Cross-train - new ability to merge and validate adaptive schema assets, augment qna and lu files, create/ update/ replace/ train/ publish LUIS and or QnA maker application and Language Generation templates manipulation.

New CLI Tools were added for management of Adaptive Dialogs.

  • bf-dialog supports merging dialog schema files and verify file format correctness.
  • bf-luis Adds commands to augment lu files and create/ update/ replace/ train/ publish LUIS
  • bf-qnamaker Adds commands to augment qna files and create/ update/ replace/ train/ publish QnAMaker
  • bf-lg Parse, collate, expand and translate lg files.

Language Generation

LG is Generally Available (GA) on both the C# and JS Platforms.

Language Generation (LG) enables you to define multiple variations of a phrase, execute simple expressions based on context, and refer to conversational memory. At the core of language generation lies template expansion and entity substitution. You can provide one-off variation for expansion as well as conditionally expanding a template. The output from language generation can be a simple text string or multi-line response or a complex object payload that a layer above language generation will use to construct a complete activity. The Bot Framework Composer natively supports language generation to produce output activities using the LG templating system.

You can use Language Generation to:

  • Achieve a coherent personality, tone of voice for your bot.
  • Separate business logic from presentation.
  • Include variations and sophisticated composition for any of your bot's replies.
  • Construct cards, suggested actions and attachments using a structured response template.

Language Generation is achieved through:

  • A markdown based .lg file that contains the templates and their composition.
    Full access to the current bot's memory so you can data bind language to the state of memory.
  • Parser and runtime libraries that help achieve runtime resolution.

Adaptive Expressions

Adaptive Expressions are Generally Available (GA) on both the C# and JS Platforms.

Bots use expressions to evaluate the outcome of a condition based on runtime information available in memory to the dialog or the Language Generation system. These evaluations determine how your bot reacts to user input and other factors that impact bot functionality.

Adaptive expressions were created to address this core need as well as provide an adaptive expression language that can used with the Bot Framework SDK and other conversational AI components, like Bot Framework Composer, Language Generation, Adaptive dialogs, and Adaptive Cards.

An adaptive expression can contain one or more explicit values, pre-built functions or [custom functions. Consumers of adaptive expressions also have the capability to inject additional supported functions. For example, all Language Generation templates are available as functions as well as additional functions that are only available within that component's use of adaptive expressions.

Authentication Improvements

We added support for single sign-on while using Expect Replies. This applies to SSO performed between a pair of bots: host and a skill.

For Bot Identification we've added the ability to specify sendx5c parameter for certificate authentication. This feature was requested by customers and allows for more flexibility when using cert auth.

Additional Sovereign Clouds are supported.

Generated Dialogs - Early Preview

The Bot Framework has a rich collection of conversational building blocks, but
creating a bot that feels natural to converse with requires understanding and
coordinating across language understanding, language generation and dialog
management. To simplify this process and capture best practices, we've created
the bf-generate plugin for the BotFramework CLI tool. The
generated dialogs make use of event-driven adaptive dialogs with a rich and
evolving set of capabilities including:

  • Handle out of order and multiple responses for simple and array properties.
  • Add, remove, clear and show properties.
  • Support for choosing between ambiguous entity values and entity property mappings.
  • Recognizing and mapping for all LUIS prebuilt entities.
  • Help function, including auto-help on multiple retries.
  • Cancel
  • Confirmation

VS Code Debugger - Early Preview

Adaptive tools is a brand new Visual studio code extension you can use to create/ validate .lu and .lg documents as well as debug declaratively defined adaptive dialogs. This extension provides rich authoring & editing capabilities for .lu and .lg file formats including syntax highlighting, auto-suggest and auto-complete.

We anticipate adding an early preview to the VS Marketplace shortly after this release.

Bot Builder Community

During this release, the Bot Builder Community has further raised the bar by adding more features, more adapters, and fixing more bugs.

  1. A revised C# Alexa Adapter and Google Home Adapter Re-built from the ground up, starting with Alexa, to allow the adapters to be consumed by Azure Bot Service and made available as channels. Improvements include better native activity type mapping, improved markdown rendering and support for more complex scenarios (such as merging multiple outgoing activities).

  2. A new C# Zoom Adapter. Currently supports Zoom 1:1 and channel chat capabilities, being converted to native BF activity types. Also supports the subscribing to any event a Zoom as supports (translated into Event activities), with full support for Zoom interactive messages and rich message templates.

  3. A RingCentral Adapter. The RingCentral Engage adapter allows you to add an additional endpoint to your bot for RingCentral Engage Digital Platform integration. The RingCentral endpoint can be used in conjunction with other channels meaning, for example, you can have a bot exposed on out of the box channels such as Facebook and Teams, but also integrated as an RingCentral Engage Digital Source SDK into RingCentral.

Changelog for v4.9.0:

  • Add Dialog / PageView telemetry [PR 2145]
  • Ported AdaptiveSkillDialog class from C# [PR 2177]
  • Adding Datetime Reference Option to recognizer and fixing typo [PR 2174]
  • Added expression binding logic [PR 2172]
  • Fix access levels in botbuilder-dialogs-adaptive, add tests [PR 2171]
  • Update SkillDialog to handle all activity types (e.g. set DeliveryMode for Invokes) [PR 2161]
  • Stevenic/adaptive fixes [PR 2160]
  • Fix CI and align versions of moment and moment-timezone [PR 2159]
  • Add tenantId and userRole to TeamsChannelAccount [PR 2155]
  • Added LuisAdaptiveRecognizer [PR 2149]
  • Added missing adaptive dialog exports [PR 2147]
  • [QnA Maker] ActiveLearningDisable bug fix [PR 2146]
  • Skills use correct ConnectorClient in OAuthPrompt, add ConnectorClientBuilder [PR 2144]
  • Changed GovernmentConstants.ToChannelFromBotLoginUrl [PR 2138]
  • Add HealthCheck Invoke handling [PR 2137]
  • Pinned recognizers-text to 1.1.4 [PR 2135]
  • refactor TestMultiLangImport tests [PR 2128]
  • Support SSO with SkillDialog and expectReplies [PR 2127]
  • [Expression] fix null check in expression [PR 2118]
  • Adjust scoreThreshold validation to not throw when score value provided is 1 [PR 2113]
  • Support empty lg file. [PR 2109]
  • Move ExpressionProperty from botbuilder-dialogs-adaptive to adaptive-expressions package [PR 2107]
  • Locale Fixes [PR 2105]
  • Change onTeamsMembersAdded for Teams to use getMember() [PR 2103]
  • Ported test cases for adaptive dialogs [PR 2100]
  • [Expression] fix utcNow() test cases fail in certain time [PR 2096]
  • Add activity factory test [PR 2095]
  • Update ms-rest-js [PR 2088]
  • Fix the offset issue of diagnostic [PR 2086]
  • Add ConnectorClientOptions to BotFrameworkAdapterSettings [PR 2081]
  • Refactor LGLanguageGenerator tests to address timeout failures [PR 2076]
  • bump chromedriver to ^81.0.0 [PR 2075]
  • [LG] Robust Template CRUD with Two-phase parsing of LG [PR 2074]
  • BotStateScope to get full bot state memory [PR 2073]
  • Add custom endpoint to LuisService [PR 2072]
  • Improve LG Options for replace null and markdown rendering [PR 2071]
  • Add OAuthUrl constants and ensure forwarded activities contain a recipient value [PR 2067]
  • Stevenic/turn state [PR 2065]
  • Change Comparisons to ReturnType of 'template' function use bit opera� [PR 2058]
  • Re-do multiLingualLg [PR 2053]
  • Updates for CallerId [PR 2052]
  • Fixed path resolver not working when alias in middle [PR 2050]
  • Added test case for CancelAllDialogs [PR 2049]
  • Fixed AttachmentInput [PR 2048]
  • InputDialog: fallback to .value if there is no .text in dc.context.activity [PR 2047]
  • Fixed AtPathResolver to deal with complex objects correctly [PR 2046]
  • Bot Change Detection [PR 2044]
  • [Adaptive] QnAMakerRecognizer and OnQnAMatch [PR 2029]
  • Add attachments to telemetry [PR 2025]
  • fix LG error message for template name [PR 2023]
  • [PORT] update adaptive inputs to set inputHint = expectingInput [PR 2022]
  • Add botbuilder-dialogs-declarative, botbuilder-dialogs-adaptive to de� [PR 2020]
  • [Expression] Support byte array input for base64 function [PR 2015]
  • refactor expander [PR 2012]
  • Add EventFactory and HandoffEventNames to botbuilder [PR 2010]
  • [LG] Remove dash in identifier to make sure arithmetic expressions can be parsed correctly [PR 2009]
  • [PORT]Add array return type [PR 2007]
  • Use v5 API host in QnAMakerDialog or construct v4 API host [PR 2004]
  • Added assertNoReply to TestFlow/TestAdapter [PR 2002]
  • [QnA Maker] opim auth header for V5 support [PR 2001]
  • Matched method name in error with actual method's name [PR 2000]
  • [QnA Maker] host name as-is [PR 1999]
  • Merge 4.future to master [PR 1998]
  • [PORT]Refine Error message and remove duplicate code [PR 1987]
  • Move Error logic out of botbuilder into authentication layer [PR 1985]
  • Allow creation of multiple Cosmos containers [PR 1984]
  • [Port] make custom function easier [PR 1981]
  • Remove "botbuilder-core" dependency from LG [PR 1980]
  • [PORT]Fix missing trailing line break [PR 1978]
  • [PORT]Loose grammar to make Structure LG more torren [PR 1976]
  • [Expression] fix parameter name and return type in Expression options [PR 1974]
  • [PORT] Update IMemory interface and tryEvaluate for expression [PR 1967]
  • Add @microsoft/api-extractor to detect public API changes [PR 1962]
  • [Expression] Add support of create object via {key: value} syntax [PR 1958]
  • [PORT] cache Antlr parse result [PR 1956]
  • rankerType got from options in QnA constructor [PR 1953]
  • Make the CRUD of the template consistent [PR 1952]
  • added LUIS error handling [PR 1949]
  • Two small test fixes [PR 1947]
  • update LG escape [PR 1944]
  • [port] remove dynamic [PR 1942]
  • [PORT] Remove unnecessary restrication on memory path [PR 1941]
  • [PORT]update expression escape [PR 1940]
  • [PORT][Expression] Support escape in regex [PR 1938]
  • [PORT]Disambiguation of �!� mark in expression [PR 1933]
  • Move deepEquals and deferences from extensions to Expression class [PR 1927]
  • Add method for create an array by square bracket expression [PR 1926]
  • Add rawLocalTimestamp to new interface [PR 1924]
  • [PORT] [activityfactory] Improve missing type error [PR 1922]
  • Support multiple lines Expression in LG file [PR 1921]
  • [port] fix index access bug [PR 1919]
  • move botbuilder/tests/teams to libraries/teams-scenarios [PR 1915]
  • port dotnet DialogTestClient DialogContext changes [PR 1914]
  • Improve Expression with adding type checking functions [PR 1911]
  • update lg tsconfig and comments [PR 1910]
  • [OAuth]do not set signInLink to empty when OAuthAppCredentials is set [PR 1907]
  • Cherry-picks #1902 and #1894 to master [PR 1906]
  • make WebRequest.on optional [PR 1899]
  • [master, cherry-pick] fix runDialog helper, fix callerId [PR 1898]
  • trust reference.serviceUrl if credentials.appId is truthy [PR 1889]
  • Update preview build to 4.9 [PR 1888]
Assets 2