October 2017 Release

Service Cloud Snap-ins for Android Release Notes

This release (210.0.0) applies to the following component versions:

• Knowledge version 3.0.0
• Case Management version 3.0.0
• Live Agent Chat version 2.0.0
• SOS version 3.0.0

For more info about the SDK, see the Snap-ins SDK Product Page.

See the version release history to learn about past versions of the SDK.

New Features

• Supports Android API level 26 (Android O).
• Added support for Android notification channels.
• Uses Salesforce Mobile SDK version 5.3.
• Live Agent Chat: Supports pre-chat entity mapping. Now you can map fields in your pre-chat form in your app to fields in a record in your org. See Show Pre-Chat Fields to User.
• Live Agent Chat: Added sensitive data rules for Chat. You can specify a regular expression in your org that detects when sensitive data is typed by the user (such as a credit card number or social security number) and then prevent that data from getting sent to the agent. See Block Sensitive Data in a Chat Session.
• Live Agent Chat: Chat sessions now attempt to reconnect to the server in the event of a connection interruption.
• Knowledge: Added the ability to embed a knowledge article directly into your own layout using ArticleWebView. See Show Knowledge Articles.
• Case Management: Added the ability to specify push notification importance when configuring the Case UI by using CaseUIConfiguration.create(caseConfiguration, IMPORTANCE).
• SOS: Updated OpenTok to 2.12.0

API Changes

• Live Agent Chat: The PreChat class, which was used to fetch fields, has been removed. Use PreChatField and PreChatEntity instead.
• Live Agent Chat: Added a PreChatEntity object and a PreChatField object.
• Live Agent Chat: Added a preChatEntities property to ChatConfiguration.Builder.
• Live Agent Chat: The customDetail property in the ChatConfiguration.Builder class has been removed. Use the preChatFields property instead.
• Live Agent Chat: Added a new model, ChatSentMessageReceipt, which contains information about any Sensitive Data Rule violations found in an outgoing chat message.
• Live Agent Chat: Changed the method signature of ChatClient.sendChatMessage(String) to return Async<ChatSentMessageReceipt> instead of Async<Void>.
• Live Agent Chat: ChatClient.sendChatMessage(String) now provides a SessionDoesNotExistException to your ErrorHandler instead of a RuntimeException when it is invoked without an active session.
• Live Agent Chat: ChatClient.sendChatMessage(String) provides an EmptyChatMessageException to your ErrorHandler if the provided string is empty, or the string has been scrubbed clean of offending text after processing with Sensitive Data Rules. If the latter is true, the exception contains a list of related Sensitive Data Rules that were triggered to produce an empty string.
• Knowledge: Added ArticleWebView API so that you can launch articles to without navigating the Knowledge tree.
• Case Management: Added the ability to specify push notification importance when configuring the Case UI. Default value is IMPORTANCE_HIGH. Use CaseUIConfiguration.create(caseConfiguration, IMPORTANCE_LOW) to configure the importance.
• Case Management: Changed the default notification priority to be PRIORITY_HIGH for API < 26. Priority changes to match the IMPORTANCE provided to CaseUIConfiguration.create(caseConfiguration, IMPORTANCE).

Fixes

• Live Agent Chat: “Chat with Agent” button now has background set to 30% opacity when required fields aren't filled out, and button cannot be pressed.
• Live Agent Chat: Fixed a bug where the title text color on the pre-chat UI was not being set to salesforce_toolbar_inverted.
• Fixed a bug where the NetworkError end reason was being reported twice. End reasons will only be reported to onSessionEnded(ChatEndReason) during the Ending state.
• Knowledge: Fixed a bug where long data category titles would overlap with the expand/collapse chevron.
• Knowledge: Fixed bug causing offline caching to break when using the core API to fetch articles directly for known IDs.
• SOS: SOS Halo UI now shows a play icon when it is paused, instead of a pause icon regardless of state.
• SOS: Updated the “back to app” bar and information icon animations in the two-way video mode.
• SOS: Fixed a crash that occurred when the SosConfigurationBuilder was configured with connectingUi(false).
• SOS: Fixed a crash when the name of the agent did not arrive before the SOS session connects.
• SOS: Fixed an existing issue where the device screen appears zoomed on the agent console during screen sharing if a live agent org migration occurs.
• SOS: Fixed a bug where the mute and two-way video controls on the SOS Halo UI disappear when the agent pauses an SOS session.
• SOS: Fixed a bug where the SOS Halo UI would not accept user actions after rotating the device.
• Case Management: Fixed crash on startup caused when offline cases database cannot be read.

Known Issues

• KitKat (Android 4.4) devices crash when using the Snap-ins SDK and Google Play Services Security Provider. Workaround: Avoid invoking ProviderInstall on KitKat devices by checking the current build version in your code.
• Live Agent Chat: Case creation via pre-chat entity mapping does not work when using Omni-Channel routing. Contact creation still works correctly. Workaround: Use Live Agent routing instead, or avoid creating cases with pre-chat fields. Note that Live Agent routing is currently only available in Salesforce Classic.
• Live Agent Chat: There are missing translations for strings present in chat-ui. Currently, only English text exists for the following strings:
  • chat_dialog_select_image_source_choose
  • chat_session_ended_by_agent
  • chat_feed_content_description
  • chat_file_transfer_requested
  • chat_file_transfer_canceled
  • chat_file_transfer_failed
  • chat_image_selection_failed
  • chat_permission_not_granted
  • pre_chat_toolbar_title
  • pre_chat_button_start
  • pre_chat_field_list_description
  • pre_chat_banner_text
  • salesforce_message_input_hint
• Knowledge: When caching content for offline use, the log may show "Error inserting using {redacted sql} into {TableName}". There is no impact on the application behavior beyond this log statement.