Skip to content

January 2022 Patch Release 2
Compare
Choose a tag to compare
@sfyz sfyz released this 20 Jan 17:24
· 14 commits to master since this release
224.2.1
e9d6931
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.

Release Notes: Embedded Service SDK for Android

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

  • Chat version 4.3.1
  • Knowledge version 4.3.6
  • Case Management version 4.2.7
  • ServiceCore version 8.0.5

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.

Running into an issue? Create a case.

Fixes

  • Fixed a bug where the order wasn't persisted in AppEventList, which led to issues with app link expressions.

Known Issues

  • Chat: If you set defaultToMinimized to false then when a user gets transferred to another agent, the chat feed becomes hidden behind the chat queue and you can't speak with the agent. Workaround: Set defaultToMinimized to true, which is also the default value for this setting: chatUIConfigurationBuilder.defaultToMinimized(true)
  • Chat: If you use an incorrect button ID in your chat configuration, the chat will fail and your SessionStateListener 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.
Assets 2
Loading