Microsoft Social Engagement 2016 Update 1.5

Microsoft Social Engagement 2016 Update 1.5 is ready and will be released in May 2016. This article describes the features, fixes, and other changes that are included in this update.

New features introduced in Microsoft Social Engagement 2016 Update 1.5

Update 1.5 introduces the following features:

• Introducing auto tags and adaptive learning on tags
  You can now enable adaptive learning on your custom tags by adding them to your list of auto tags. Social Engagement applies adaptive machine learning on these tags to predict tags for new incoming posts. This allows the system to learn from users' edits on tags and the tagging of posts.
  Custom tags use text analytics and Azure machine learning techniques to learn patterns from posts manually tagged by users. As more labeled data becomes available, the service can continually learn and improve quality. Labeled data includes tags that are added by the user manually, tags that are added by the system and confirmed by the user, or tags that are added by the system and removed by the user. New, incoming (unlabeled) posts can be scored automatically by the service and analyzed throughout Social Engagement. Auto scoring quality can be monitored in the corresponding Settings page.
  The feature will be rolled out gradually for a smooth transition. No action is required on your part. You'll find the new page in Settings > Global Settings > Auto Tags when the feature is available.
• Introducing Chinese and Japanese sentiment detection
  Social Engagement now includes sentiment calculation for Chinese and Japanese in addition to the already available languages. Understand at a glance how the perception of your audience is toward the terms you search for.
• Extended source coverage: Blogs
  We have extended the current coverage of the Blogs source. The extended source is automatically included if you set up a new search topic with a keyword rule. To avoid an unintentional surpassing of your monthly post quota, your existing search topics will continue to acquire posts with the previous source coverage. If you want to update existing search topics to include the extended coverage of the Blogs source, you can edit your existing keyword search rules, for example by adding a comma (,) and save the edited rule.
• Open linked social posts with the interactive experience in Dynamics CRM
  Dynamics CRM recently introduced the new interactive service hub that offers a different user experience from the web client. For CRM entities that are enabled for interactive experience, we now automatically take you to the interactive service hub when you open a record on a social post that is linked to CRM. CRM entities not enabled for interactive experience will continue to be opened in the web client.
• Engage with social profiles
  The social profiles page is redesigned in preparation for future functionality changes. You can easily add tokens to interact with posts and view the health state of your tokens.
• Fewer pop-ups when linking posts to CRM Online
  The authentication mechanism has changed for linking a social post to Dynamics CRM from client-side to server-side. With this change you will no longer see authentication pop-ups when linking a post or viewing a linked post in Social Engagement,
  However, you may still see pop-ups when you link or view a post if you have a CRM instance that is older than the CRM Online 2016 update, is located in the North America 2 datacenter, or is on-premises.
  The feature will be rolled out gradually for a smooth transition. No action is required on your part.

Issues that are resolved in Microsoft Social Engagement 2016 Update 1.5

In addition to the new features, Update 1.5 addresses the following issues and improvements:

• Improved freshness of data for private messages by increasing acquisition cycles from 10 to every 2 minutes.
• Improved usability of handling filters in Analytics. When opening a post list in Analytics while the filters are expanded, the filter dialog now closes and displays the post list in focus.
• Improved usability on event hub configuration experience: Azure Event Hubs connection strings now include the Event Hub name. When establishing or updating a connection to Azure Event Hubs in Social Engagement, you are no longer required to match the Event Hub name to the actual name of the Event Hub in the Azure Portal.
• Improved usability on working with posts: Posts details now has clearer labels for the tabs which show threads: Rather than mentioning the author of each post it is now referring to whether the thread is for the parent or the child post.
• Improved feedback messaging on publish actions: When publishing to a social network from Social Engagement the response didn't distinguish between failures to publish and failures to load the publish history. This lead to confusing error messages which implied that the publishing didn't work. These two actions now show dedicated error states, so you can be sure Social Engagement informs you if your post wasn't successfully published.
• Improved visual consistency and readability of Authors widget in Analytics by adjusting font sizes and column width.
• Fixed and issue when filtering for unassigned posts in the assignee filter resulted in an error notification.
• Fixed and issue with Twitter handle search rules showing as @undefined in some cases, resulting in no posts acquired for this rule.
• Fixed an issue with private messages where earlier messages were acquired if a new interaction with the earlier message occurred.
• Fixed an issue with Facebook posts containing media. Certain Facebook posts with videos didn't show the embedded video as expected. We fixed this for the majority of cases and will continue to address this with upcoming updates.