Skip to content

@sfyz sfyz released this May 29, 2019

Release Notes: Embedded Service SDK for Android

This release (SDK version 220.1.0) includes the following components:

  • Chat version 3.5.0
  • Knowledge version 4.3.1
  • Case Management version 4.2.1
  • SOS version 4.0.6
  • ServiceCore version 7.2.1

To install the SDK, follow these installation instructions. For additional info about the SDK, check out the Service SDK Developer Center. Refer to the version release history to learn about past versions of the SDK.

NOTE: Version 220 of the Embedded Service SDK was designed for the Summer ’19 version of Salesforce (release 220, API 46.0). Make sure that your production org is updated to Summer ’19 before using this SDK in your app.

Summary

This patch release addresses an issue for customers upgrading from version 216 or 218 of the SDK who were getting a blank screen when using Case Management or authenticated Knowledge. The patch also adds access to the Session ID from the ChatUIClient object. See API Changes for more details.

See the May 2019 Major Release for previous updates to the SDK.

API Changes for Chat

This version allows you to add a SessionInfoListener implementation from the ChatUIClient. From this listener, you can access the Session ID with getSessionId().

Sample SessionInfoListener:

public class MySessionListener implements SessionInfoListener {
    public void onSessionInfoReceived (ChatSessionInfo chatSessionInfo) {
        String sessionID = chatSessionInfo.getSessionId(); // NEW!
        // TO DO: Store the session ID for later use
}

Sample ChatUIClient code:

// Create a chat session and add a session listener
ChatUI.configure(uiConfig.build())
  .createClient(getApplicationContext())
  .onResult(new Async.ResultHandler<ChatUIClient>() {
      @Override public void handleResult (Async<?> operation, 
        ChatUIClient chatUIClient) {
            MySessionListener listener =
                ((MyApplication)getApplication()).getSessionListener();
            chatUIClient.addSessionStateListener(sessionStateListener);
            chatUIClient.addSessionInfoListener(sessionInfoListener); // NEW!
            chatUIClient.startChatSession(MainActivity.this);
        }
});

To learn more about starting a chat session, see Chat Quick Setup.

Known Issues

  • Authenticated Knowledge and Case Management: An update to the Summer '19 version of Salesforce may cause features for authenticated users to fail when using the SDK. To remedy this problem, see the upgrade instructions below.
  • Chat Accessibility: A screen reader doesn’t read the event text when an agent invites another agent to the chat session.
  • Chat: If you use an incorrect button ID in your chat configuration, the chat will fail and your SesssionStateListener will report a ChatEndReason of NetworkError. Workaround: If you receive a NetworkError, verify that the button ID is correct.
  • Chat: Case creation using the ChatEntity class does not work for Omni-Channel routing without a setup change to your org. Workaround: Raise a ticket with Salesforce.com to ensure that Omni-Channel is enabled to create a Case in your org. Note that Contact creation works fine with Omni-Channel, and Live Agent routing works correctly for both Cases and Contacts.
  • Case Management: Case SDK Activity instances that are restarted by the OS may not display any content until the SDK is re-initialized within the app. Workaround: Create a CaseUIClient during Application.onCreate() to avoid this problem.
  • Knowledge: The order in which articles and categories are displayed on Knowledge UI may differ while the device is offline compared to when it is online.
  • Knowledge: Articles and categories that have been unpublished or re-categorized in your community knowledge base may still appear in the UI while the device is offline. At this time, articles and categories are not removed from the cache.
  • Knowledge: Search accuracy is limited to matching terms found within article titles and article summaries while offline. Online search makes use of the remote server's ability to view the entirety of the knowledge base for obtaining search results.
  • Case Management: If the "Edit Read Only Fields" permission is turned on in your org, a community user can see (and seemingly edit) read only fields when creating a case. Workaround: Turn off the "Edit Read Only Fields" permission so that read only fields are not shown when creating a case. See this Knowledge article for more information.

Upgrade Instructions When Using Authenticated Knowledge or Cases

An update to the Summer '19 version of Salesforce may cause authenticated Knowledge and authenticated Case Management to fail when using the SDK. To remedy this problem, update your community's profile to re-allow API access. From Setup in your org, enter "Profiles" in the Quick Find box, then select Profiles. Edit the profile for your community. Under Administrative Permissions, ensure that "API Enabled" is checked.

Assets 2

@sfyz sfyz released this May 8, 2019

Release Notes: Embedded Service SDK for Android

This release (SDK version 220.0.0) includes the following components:

  • Chat version 3.4.0
  • Knowledge version 4.3.0
  • Case Management version 4.2.0
  • SOS version 4.0.6
  • ServiceCore version 7.2.0

To install the SDK, follow these installation instructions. For additional info about the SDK, check out the Service SDK Developer Center. Refer to the version release history to learn about past versions of the SDK.

NOTE: Version 220.0.0 of the Embedded Service SDK was designed for the Summer ’19 version of Salesforce (release 220, API 46.0). Make sure that your production org is updated to Summer ’19 before using this SDK in your app.

Summary

This release improves accessibility, adds support for right-to-left languages, and includes bug fixes.

NOTE: If you are using Knowledge or Case Management with authenticated users, see the Upgrade Instructions below for an important update.

New Features

  • This version of Chat includes accessibility enhancements for customers that use a screen reader. To learn more, see Accessibility for the Service SDK.
  • We now support right-to-left (RTL) languages such as Arabic and Hebrew.
  • SOS: Upgraded to OpenTok version 2.15.3.

API Changes

No API changes for this release.

Fixes

  • Changed the contrastSecondary color from #767676 to #6D6D6D to improve the contrast ratio for accessibility. To learn more, see Customize Colors.
  • Fixed UI issues to support right-to-left languages.
  • Chat: Updated the input text placement string (salesforce_message_input_hint) to 'Send a message…'. This value is still customizable. To learn more, see Customize Strings with the Service SDK.
  • Chat: The user is brought back to the app when they tap a notification.
  • Chat: Chatbot quick reply buttons now appear on the same side as the typed text.
  • Chat: Increased the default color contrast of the hyperlink preview URL.
  • Knowledge: Added support for Arabic and Hebrew languages in article queries.
  • Case Management: Fixed an issue where the case publisher would not load if the device language used non-English numerals.
  • SOS: Fixed a persistent blank screen when the session begins with field masking.
  • SOS: Fixed an issue where the Android session did not properly end. This was fixed by the OpenTok update.

Known Issues

  • Upgrading from earlier versions of the Case Management SDK may result in the following message: "Something went wrong. Unable to load your queries. Try Again Later." This issue is fixed in version 220.1.0.
  • Authenticated Knowledge and Case Management: An update to the Summer '19 version of Salesforce may cause features for authenticated users to fail when using the SDK. To remedy this problem, see the upgrade instructions below.
  • Chat Accessibility: A screen reader doesn’t read the event text when an agent invites another agent to the chat session.
  • Chat: If you use an incorrect button ID in your chat configuration, the chat will fail and your SesssionStateListener will report a ChatEndReason of NetworkError. Workaround: If you receive a NetworkError, verify that the button ID is correct.
  • Chat: Case creation using the ChatEntity class does not work for Omni-Channel routing without a setup change to your org. Workaround: Raise a ticket with Salesforce.com to ensure that Omni-Channel is enabled to create a Case in your org. Note that Contact creation works fine with Omni-Channel, and Live Agent routing works correctly for both Cases and Contacts.
  • Case Management: Case SDK Activity instances that are restarted by the OS may not display any content until the SDK is re-initialized within the app. Workaround: Create a CaseUIClient during Application.onCreate() to avoid this problem.
  • Knowledge: The order in which articles and categories are displayed on Knowledge UI may differ while the device is offline compared to when it is online.
  • Knowledge: Articles and categories that have been unpublished or re-categorized in your community knowledge base may still appear in the UI while the device is offline. At this time, articles and categories are not removed from the cache.
  • Knowledge: Search accuracy is limited to matching terms found within article titles and article summaries while offline. Online search makes use of the remote server's ability to view the entirety of the knowledge base for obtaining search results.
  • Case Management: If the "Edit Read Only Fields" permission is turned on in your org, a community user can see (and seemingly edit) read only fields when creating a case. Workaround: Turn off the "Edit Read Only Fields" permission so that read only fields are not shown when creating a case. See this Knowledge article for more information.

Upgrade Instructions When Using Authenticated Knowledge or Cases

An update to the Summer '19 version of Salesforce may cause authenticated Knowledge and authenticated Case Management to fail when using the SDK. To remedy this problem, update your community's profile to re-allow API access. From Setup in your org, enter "Profiles" in the Quick Find box, then select Profiles. Edit the profile for your community. Under Administrative Permissions, ensure that "API Enabled" is checked.

Assets 2

@sfyz sfyz released this May 15, 2019

Release Notes: Embedded Service SDK for Android

This release (SDK version 218.0.0) includes the following components:

  • Knowledge version 4.2.2
  • Live Agent Chat version 3.3.0
  • Case Management version 4.1.4
  • SOS version 4.0.5
  • ServiceCore version 7.1.1

To install the SDK, follow these installation instructions. For additional info about the SDK, check out the Service SDK Developer Center. Refer to the version release history to learn about past versions of the SDK.

Summary

This release supports knowledge article previews in chat sessions, provides more chat event notifications, and contains bug fixes and other enhancements to the SDK.

New Features

  • Chat: Now supports knowledge article previews in chat sessions when an agent sends a URL to a knowledge article from their community. To learn more, see Display Knowledge Article Previews in Chat.
    • Added support for showing knowledge article previews in chat sessions.
    • Added support for showing the knowledge article detail view in the app when a user clicks on an article preview.
  • Chat: Added a new ChatEventListener so that you can listen for chat events. To learn more, see Listen for State Changes and Events.
  • Chat: Hyperlink preview messages now display the favicon image adjacent to the hostname.
  • Chat: When in a chat session, a banner displays when you've lost the connection. This banner can be overridden from the SalesforceConnectionBanner class.
  • SOS: Updated to the latest version of OpenTok: version 2.15.2.

API Changes

Fixes

  • Chat: Added the ability to select (and copy) sent chat messages.
  • Chat: SDK closes previous chat minimized views when a new chat session is initiated.
  • Chat: Fixed text coloring of chatbot menu buttons when using TalkBack accessibility.
  • Chat: Initial data appears correctly when used on required pre-chat fields.
  • Chat: Fixed accessibility scanner issue with chat message heights for single-line messages.
  • Chat: Fixed accessibility scanner issue with duplicate item descriptions on pre-chat fields.
  • Improved the touch responsiveness of picklist views.
  • Cases: Fixed an infinite loading spinner when the case publisher was invoked without a network connection.

Known Issues

  • Upgrading from earlier versions of the Case Management SDK may result in the following message: "Something went wrong. Unable to load your queries. Try Again Later." Although there is no workaround for this issue at the moment, we're actively investigating a fix for this issue.
  • SOS: The ProGuard instructions in the developer guide (Decrease the Size of Your App) do not contain one important rule (-keep class com.salesforce.android.sos.** { *; }) to ensure that SOS sessions end correctly. This issue will be corrected in next week's update to the documentation. In the meantime, refer to the upgrade instructions below.
  • Case Management: Case SDK Activity instances that are restarted by the OS may not display any content until the SDK is re-initialized within the app. Workaround: Create a CaseUIClient during Application.onCreate() to avoid this problem.
  • Knowledge: The order in which articles and categories are displayed on Knowledge UI may differ while the device is offline compared to when it is online.
  • Knowledge: Articles and categories that have been unpublished or re-categorized in your community knowledge base may still appear in the UI while the device is offline. At this time, articles and categories are not removed from the cache.
  • Knowledge: Search accuracy is limited to matching terms found within article titles and article summaries while offline. Online search makes use of the remote server's ability to view the entirety of the knowledge base for obtaining search results.
  • Live Agent Chat: If you use an incorrect button ID in your chat configuration, the chat will fail and your SesssionStateListener will report a ChatEndReason of NetworkError. Workaround: If you receive a NetworkError, verify that the button ID is correct.
  • Live Agent Chat: Case creation using the ChatEntity class does not work for Omni-Channel routing without a setup change to your org. Workaround: Raise a ticket with Salesforce.com to ensure that Omni-Channel is enabled to create a Case in your org. Note that Contact creation works fine with Omni-Channel, and Live Agent routing works correctly for both Cases and Contacts.
  • Case Management: If the "Edit Read Only Fields" permission is turned on in your org, a community user can see (and seemingly edit) read only fields when creating a case. Workaround: Turn off the "Edit Read Only Fields" permission so that read only fields are not shown when creating a case. See this Knowledge article for more information.

Upgrade Instructions

SOS: When using ProGuard to compile your app, you may find that SOS sessions do not end on the device
when the agent has ended the session from the Service Console. As a precaution, we recommend
ensuring that you add the following ProGuard rules so that SOS behaves correctly:

-keep class com.opentok.** { *; }
-keep class org.webrtc.** { *; }
-keep class com.salesforce.android.sos.** { *; } 
Assets 2

@sfyz sfyz released this Dec 14, 2018

Service Cloud Snap-Ins for Android Release Notes

This patch release (SDK version 216.0.3) applies to the following component versions:

  • Knowledge version 4.2.1
  • Live Agent Chat version 3.2.0
  • Case Management version 4.1.3
  • SOS version 4.0.4
  • Common version 7.1.0

To install the SDK, follow these instructions. For additional info about the SDK, check out the Snap-Ins SDK Developer Center. Refer to the version release history to learn about past versions of the SDK.

Summary

Patch release that fixes an issue that prevented an SOS session from starting when sending custom data from the app.

See the October 2018 Major Release for general details about the SDK.

Fixes

  • SOS: Fixed an issue that prevented an SOS session from starting when sending custom data from the app.

Known Issues

  • Case Management: Case SDK Activity instances that are restarted by the OS may not display any content until the SDK is re-initialized within the app. Workaround: Create a CaseUIClient during Application.onCreate() to avoid this problem.
  • Knowledge: The order in which articles and categories are displayed on Knowledge UI may differ while the device is offline compared to when it is online.
  • Knowledge: Articles and categories that have been unpublished or re-categorized in your community knowledge base may still appear in the UI while the device is offline. At this time, articles and categories are not removed from the cache.
  • Knowledge: Search accuracy is limited to matching terms found within article titles and article summaries while offline. Online search makes use of the remote server's ability to view the entirety of the knowledge base for obtaining search results.
  • Live Agent Chat: If you use an incorrect button ID in your chat configuration, the chat will fail and your SesssionStateListener will report a ChatEndReason of NetworkError. Workaround: If you receive a NetworkError, verify that the button ID is correct.
  • Live Agent Chat: Case creation using the ChatEntity class does not work for Omni-Channel routing without a setup change to your org. Workaround: Raise a ticket with Salesforce.com to ensure that Omni-Channel is enabled to create a Case in your org. Note that Contact creation works fine with Omni-Channel, and Live Agent routing works correctly for both Cases and Contacts.
  • Case Management: If the "Edit Read Only Fields" permission is turned on in your org, a community user can see (and seemingly edit) read only fields when creating a case. Workaround: Turn off the "Edit Read Only Fields" permission so that read only fields are not shown when creating a case. See this Knowledge article for more information.
Assets 2

@sfyz sfyz released this Nov 15, 2018

Service Cloud Snap-Ins for Android Release Notes

This patch release (SDK version 216.0.2) applies to the following component versions:

  • Knowledge version 4.2.1
  • Live Agent Chat version 3.2.0
  • Case Management version 4.1.3
  • SOS version 4.0.3
  • Common version 7.1.0

For more info about the SDK, see the Snap-Ins SDK Product Page. Check out the version release history to learn about past versions of the SDK.

Summary

Patch release that fixes an issue when using an apostrophe in Knowledge category names.

See the October 2018 Major Release for general details about the SDK.

Fixes

  • Knowledge: Fixed an issue where using an apostrophe in a category name prevents the Knowledge home from listing the categories.

Known Issues

  • Case Management: Case SDK Activity instances that are restarted by the OS may not display any content until the SDK is re-initialized within the app. Workaround: Create a CaseUIClient during Application.onCreate() to avoid this problem.
  • Knowledge: The order in which articles and categories are displayed on Knowledge UI may differ while the device is offline compared to when it is online.
  • Knowledge: Articles and categories that have been unpublished or re-categorized in your community knowledge base may still appear in the UI while the device is offline. At this time, articles and categories are not removed from the cache.
  • Knowledge: Search accuracy is limited to matching terms found within article titles and article summaries while offline. Online search makes use of the remote server's ability to view the entirety of the knowledge base for obtaining search results.
  • Live Agent Chat: If you use an incorrect button ID in your chat configuration, the chat will fail and your SesssionStateListener will report a ChatEndReason of NetworkError. Workaround: If you receive a NetworkError, verify that the button ID is correct.
  • Live Agent Chat: Case creation using the ChatEntity class does not work for Omni-Channel routing without a setup change to your org. Workaround: Raise a ticket with Salesforce.com to ensure that Omni-Channel is enabled to create a Case in your org. Note that Contact creation works fine with Omni-Channel, and Live Agent routing works correctly for both Cases and Contacts.
  • Case Management: If the "Edit Read Only Fields" permission is turned on in your org, a community user can see (and seemingly edit) read only fields when creating a case. Workaround: Turn off the "Edit Read Only Fields" permission so that read only fields are not shown when creating a case. See this Knowledge article for more information.
Assets 2

@sfyz sfyz released this Nov 5, 2018

Service Cloud Snap-Ins for Android Release Notes

This patch release (SDK version 216.0.1) applies to the following component versions:

  • Knowledge version 4.2.0
  • Live Agent Chat version 3.2.0
  • Case Management version 4.1.3
  • SOS version 4.0.3
  • Common version 7.1.0

For more info about the SDK, see the Snap-Ins SDK Product Page. Check out the version release history to learn about past versions of the SDK.

Summary

Patch release that fixes a potential crash when using Case Management.

See the October 2018 Major Release for general details about the SDK.

Fixes

  • Case Management: Fixed a crash that could occur when re-launching the app after the process has been killed by the OS.

Known Issues

  • Case Management: Case SDK Activity instances that are restarted by the OS may not display any content until the SDK is re-initialized within the app. Workaround: Create a CaseUIClient during Application.onCreate() to avoid this problem.
  • Knowledge: The order in which articles and categories are displayed on Knowledge UI may differ while the device is offline compared to when it is online.
  • Knowledge: Articles and categories that have been unpublished or re-categorized in your community knowledge base may still appear in the UI while the device is offline. At this time, articles and categories are not removed from the cache.
  • Knowledge: Search accuracy is limited to matching terms found within article titles and article summaries while offline. Online search makes use of the remote server's ability to view the entirety of the knowledge base for obtaining search results.
  • Live Agent Chat: If you use an incorrect button ID in your chat configuration, the chat will fail and your SesssionStateListener will report a ChatEndReason of NetworkError. Workaround: If you receive a NetworkError, verify that the button ID is correct.
  • Live Agent Chat: Case creation using the ChatEntity class does not work for Omni-Channel routing without a setup change to your org. Workaround: Raise a ticket with Salesforce.com to ensure that Omni-Channel is enabled to create a Case in your org. Note that Contact creation works fine with Omni-Channel, and Live Agent routing works correctly for both Cases and Contacts.
  • Case Management: If the "Edit Read Only Fields" permission is turned on in your org, a community user can see (and seemingly edit) read only fields when creating a case. Workaround: Turn off the "Edit Read Only Fields" permission so that read only fields are not shown when creating a case. See this Knowledge article for more information.
Assets 2

@sfyz sfyz released this Oct 17, 2018

Service Cloud Snap-Ins for Android Release Notes

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

  • Knowledge version 4.2.0
  • Live Agent Chat version 3.2.0
  • Case Management version 4.1.2
  • SOS version 4.0.3
  • Common version 7.1.0

For more info about the SDK, see the Snap-Ins SDK Product Page. Check out the version release history to learn about past versions of the SDK.

Summary

This release includes hyperlink previews in chat sessions, hyperlinks between knowledge articles, and other enhancements to the SDK.

New Features

  • SDK now targets Android Pie (Android 9, API 28).
  • Chat: Chat sessions display a hyperlink preview for supported sites when an agent sends a URL. This preview can contain an image from the page, along with the title and some of the content. To learn more, see Live Agent Chat in the Snap-Ins SDK for Android. To disable hyperlink previews, set enableHyperlinkPreview on the ChatUIConfiguration builder to false.
  • Added an on-screen indicator when the internet connection is lost.
  • Knowledge: Added support for hyperlinks ("smart links") to navigate between Knowledge articles.
  • Knowledge: Added support for images embedded in non-public articles.
  • Knowledge: Added a new API to directly display the details of an article: KnowledgeUIClient.launchArticle(Context, ArticleSummary).
  • Chat: Improved the appearance of the "agent typing" indicator.
  • Chat: Added support for full-screen chat. Applications wishing to start chat sessions in full-screen mode instead of the classic minimized view can configure it using the defaultToMinimized method on the ChatUIConfiguration builder.
  • Chat: Added the option to hide the character counter on a pre-chat field using the counterEnabled method on the PreChatTextInputField builder.
  • SOS: Removing dependency on Volley.

API Changes

Fixes

  • Knowledge: Fixed a problem that prevented Japanese users from searching with a single character.
  • Knowledge: Improved the accuracy of search results.
  • Knowledge: Fixed a rare crash that could occur while scrolling through a long list of article summaries while pressing the back button.
  • Chat: Minimized view unread message count now increments when an agent joins and when the session ends.
  • Cases: Fixed a problem where picklist options would display in alphabetical order.
  • SOS: Improving stability on the LG G4 devices.

Known Issues

  • Knowledge: The order in which articles and categories are displayed on Knowledge UI may differ while the device is offline compared to when it is online.
  • Knowledge: Articles and categories that have been unpublished or re-categorized in your community knowledge base may still appear in the UI while the device is offline. At this time, articles and categories are not removed from the cache.
  • Knowledge: Search accuracy is limited to matching terms found within article titles and article summaries while offline. Online search makes use of the remote server's ability to view the entirety of the knowledge base for obtaining search results.
  • Live Agent Chat: If you use an incorrect button ID in your chat configuration, the chat will fail and your SesssionStateListener will report a ChatEndReason of NetworkError. Workaround: If you receive a NetworkError, verify that the button ID is correct.
  • Live Agent Chat: Case creation using the ChatEntity class does not work for Omni-Channel routing without a setup change to your org. Workaround: Raise a ticket with Salesforce.com to ensure that Omni-Channel is enabled to create a Case in your org. Note that Contact creation works fine with Omni-Channel, and Live Agent routing works correctly for both Cases and Contacts.
  • Case Management: If the "Edit Read Only Fields" permission is turned on in your org, a community user can see (and seemingly edit) read only fields when creating a case. Workaround: Turn off the "Edit Read Only Fields" permission so that read only fields are not shown when creating a case. See this Knowledge article for more information.

Upgrade Instructions

Push Notification for Chat Upgrade Info

For those who use our connected-app module to consume Apex push notifications, we have migrated from GCM to Firebase Messaging. This requires some modifications to your app. For complete information, see Push Notifications with the Snap-Ins SDK for Android. In summary, this change requires that you:

  • Set up Firebase in your app: Add Firebase to Your Android Project.
  • Remove any references to GCM in your build dependencies and your AndroidManifest.xml file.
  • If you experience a NoClassDefError which claims that GcmReceiver is missing, it may be included in your final merged manifest by one of your dependencies, such as the Salesforce Mobile SDK. To resolve the error, add the following remove instruction to your AndroidManifest.xml: <receiver android:name="com.google.android.gms.gcm.GcmReceiver" tools:node="remove"/>.
  • Update your connected-app dependency version to 7.1.0.
  • Update your PushNotificationListener.onPushNotificationReceived method to receive a RemoteMessage parameter instead of Bundle.
Assets 2

@sfyz sfyz released this Sep 11, 2018

Service Cloud Snap-Ins for Android Release Notes

This patch release (SDK version 214.0.2) applies to the following component versions:

  • Knowledge version 4.1.0
  • Case Management version 4.1.1
  • Live Agent Chat version 3.1.0
  • SOS version 4.0.2
  • Common version 6.1.0

For more info about the SDK, see the Snap-Ins SDK Product Page. Check out the version release history to learn about past versions of the SDK.

Summary

Patch release that fixes a few Case Management issues.

See the June 2018 Major Release for general details about the SDK.

Fixes

  • Case Management: Fixed a problem where pre-chat picklist only displayed the default value.
  • Case Management: Fixed an issue where the create case button didn't appear if there were no cases in the case list.
  • Case Management: Previously, an empty view appeared if there were no cases in the case list. Now a friendly message appears.
  • Case Management: Fixed a scenario where chatter posts from unauthenticated users prevented the case feed from showing in the app.

Known Issues

  • SOS: Unable to start an SOS session when running Android 9 Pie on apps that target API level 28. Workaround: App developers should target API level 27 or earlier until we release an update.
  • Knowledge: The order in which articles and categories are displayed on Knowledge UI may differ while the device is offline compared to when it is online.
  • Knowledge: Articles and categories that have been unpublished or re-categorized in your community knowledge base may still appear in the UI while the device is offline. At this time, articles and categories are not removed from the cache.
  • Knowledge: Search accuracy is limited to matching terms found within article titles and article summaries while offline. Online search makes use of the remote server's ability to view the entirety of the knowledge base for obtaining search results.
  • Live Agent Chat: If you use an incorrect button ID in your chat configuration, the chat will fail and your SesssionStateListener will report a ChatEndReason of NetworkError. Workaround: If you receive a NetworkError, verify that the button ID is correct.
  • 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.
  • Case Management: If the "Edit Read Only Fields" permission is turned on in your org, a community user can see (and seemingly edit) read only fields when creating a case. Workaround: Turn off the "Edit Read Only Fields" permission so that read only fields are not shown when creating a case. See this Knowledge article for more information.
Assets 2

@sfyz sfyz released this Jun 21, 2018

Service Cloud Snap-Ins for Android Release Notes

This patch release (214.0.1) applies to the following component versions:

  • Knowledge version 4.1.0
  • Case Management version 4.1.0
  • Live Agent Chat version 3.1.0
  • SOS version 4.0.2
  • Common version 6.1.0

For more info about the SDK, see the Snap-Ins SDK Product Page. Check out the version release history to learn about past versions of the SDK.

Summary

Patch release that fixes a potential crash during an SOS session.

See the June 2018 Major Release for general details about the SDK.

Fixes

  • SOS: Fixed a logging-related crash that may occur when starting an SOS session.

Known Issues

  • Knowledge: The order in which articles and categories are displayed on Knowledge UI may differ while the device is offline compared to when it is online.
  • Knowledge: Articles and categories that have been unpublished or re-categorized in your community knowledge base may still appear in the UI while the device is offline. At this time, articles and categories are not removed from the cache.
  • Knowledge: Search accuracy is limited to matching terms found within article titles and article summaries while offline. Online search makes use of the remote server's ability to view the entirety of the knowledge base for obtaining search results.
  • Live Agent Chat: If you use an incorrect button ID in your chat configuration, the chat will fail and your SesssionStateListener will report a ChatEndReason of NetworkError. Workaround: If you receive a NetworkError, verify that the button ID is correct.
  • 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.
  • Case Management: If the "Edit Read Only Fields" permission is turned on in your org, a community user can see (and seemingly edit) read only fields when creating a case. Workaround: Turn off the "Edit Read Only Fields" permission so that read only fields are not shown when creating a case. See this Knowledge article for more information.
Assets 2

@sfyz sfyz released this Jun 12, 2018

Service Cloud Snap-Ins for Android Release Notes

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

  • Knowledge version 4.1.0
  • Case Management version 4.1.0
  • Live Agent Chat version 3.1.0
  • SOS version 4.0.1
  • Common version 6.1.0

For more info about the SDK, see the Snap-Ins SDK Product Page. Check out the version release history to learn about past versions of the SDK.

Summary

This release supports the use Einstein bots to complement the chat experience with a smart, automated system that saves your agents time and keeps your customers happy. To learn more, see Use Einstein Bots with Live Agent Chat. We've also made some general enhancements to the SDK.

New Features

  • Live Agent Chat: Added Einstein bot support in a chat session. Chat bot context menus, buttons, and persistent footer menus are all supported. To learn more, see Use Einstein Bots with Live Agent Chat.
  • Live Agent Chat: Added support for displaying a custom chat bot avatar and a custom chat bot banner. To learn more, see Use Einstein Bots with Live Agent Chat.
  • Live Agent Chat: Improved the user experience for chat agent transfers.
  • Knowledge: Updated caching strategy to improve performance when articles have been previously cached.
  • Case Management: Updated caching strategy to improve performance when content has been previously cached.
  • SOS: Updated to version 2.14.0 of OpenTok.

API Changes

Fixes

  • Knowledge: Fixed broken anchor tags within Knowledge article view.

Known Issues

  • Knowledge: The order in which articles and categories are displayed on Knowledge UI may differ while the device is offline compared to when it is online.
  • Knowledge: Articles and categories that have been unpublished or re-categorized in your community knowledge base may still appear in the UI while the device is offline. At this time, articles and categories are not removed from the cache.
  • Knowledge: Search accuracy is limited to matching terms found within article titles and article summaries while offline. Online search makes use of the remote server's ability to view the entirety of the knowledge base for obtaining search results.
  • 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.
  • Case Management: If the "Edit Read Only Fields" permission is turned on in your org, a community user can see (and seemingly edit) read only fields when creating a case. Workaround: Turn off the "Edit Read Only Fields" permission so that read only fields are not shown when creating a case. See this Knowledge article for more information.

Upgrade Tips

Pre-Chat Changes

  • If you are using PreChatField and related classes to pass user data through the chat session, migrate to using ChatUserData, ChatEntity and ChatEntityField instead. Ensure that you
    are providing these objects to ChatConfiguration.Builder.chatUserData() and ChatConfiguration.Builder.chatEntities(). To learn more, see Find or Create Salesforce Records from a Chat Session.
  • If you are using PreChatField to build a pre-chat experience for your users, switch to PreChatTextInputField or PreChatPickListInputField for building text input fields and pick list
    fields. These classes extend ChatUserData, so all pre-chat and user data objects may be provided to ChatConfiguration.Builder.chatUserData(). See Show Pre-Chat Fields to User.

ProGuard Tips

Assets 2
You can’t perform that action at this time.