March 14, 2019

Watson Translate (Beta):

Translates a piece of text into the language of the user’s choosing using three fields: Source language (what language is the message coming in), Target language (what language should it translate to), and Text (the message to be translated, likely using a variable). Languages must be configured using language codes, as in this IBM documentation.

Watson Detect Language (Beta):

Allows the user to detect the language of a given piece of text, perhaps of a received message. That detected language can be used with Watson Translate action to allow two-way communication across different languages.

Watson Assistant:

Allows the user to point to their Watson Assistant configuration on the IBM Watson dashboard to use pre-configured intents to facilitate automated, responsive conversation. The required fields are the Assistant URL and credentials (located in the API details on the user’s configured Watson Assistant instance) and the Workspace ID (located in the API details on the user’s configured Skill, which is associated with the Watson Assistant instance).

Ability to make a copy of a flow:

Allows a user to click to make a copy of a flow from either the Flow Management page (copy button next to the delete button) or using the ‘Clone’ button that is available in the flow metadata section of the configuration panel of the flow. This will users to quickly replicate and edit flows (for a A/B testing inbound text campaigns, for example) and will add strong value for debugging purposes.

Sentiment and Tonality Analysis on SMS:

Users can now conduct sentiment and tonality analysis on text messages using the standalone sentiment and tonality actions in the premium actions menu.

Status Code:

We will now include the server response code as a variable so that users can use control actions to drive logic based on specific response codes. Look for a variable called ‘status code’ on the external web call actions.

Select XML:

Ability to select an XML mime type and post or get XML data. Note: This does not yet include the ability to parse XML into variables; only the entire response body is included. Variable support is a roadmap item.

Validations on Record Response:

Validate against the presence of invalid characters in the record response action to prevent users from mistakenly entering invalid input.

Assign multiple telephone numbers to the same flow:

Allows the user to assign multiple telephone numbers to the same flow. Note: This feature will work best if the user ensures that the desired numbers have already been enabled for SmartFlows (i.e. green thumbs up means go!). This enablement is done in the Customer Portal.

‘Between’ Operator Available on Switch Action:

Allows customer to test for an integer value between two other integer values.

Validation when number of audio plays on the Menu Tree is mismatched to max retries.

There is some nuance to the process of matching Menu Tree Introductory Audio plays to the number of retries, which can be confusing for the user. This validation is present to help guide the user in matching the number of plays to the number of retries.

Bug Fixes:

Fixed a bug related to the Dial action that prevented menu tree, transfer, play audio, and other actions to work correctly after the Dial action was used.
Fixed a confusing user experience where newly opened flow tabs were hidden behind the last active flow when opening them using the ‘new flow/edit flow’ tab on the canvas.
Fixed a bug that allowed a call to continue indefinitely after one party hangs up after a transfer.
Text-to-speech and SMS were very sensitive to special characters and these features would often break if special characters were introduced; we implemented a fix for this.
When the flow name was updated but the flow was already assigned to a number, the new flow name did not propagate to the number assignment page; this issue was resolved.