Skip to content

October 2023 Patch Release

Latest
Latest
Compare
Choose a tag to compare
@aeisses aeisses released this 30 Oct 16:09
246.0.0
7e610d9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Release Notes: Embedded Service SDK for iOS

Note: These release notes describe the Embedded Service Chat SDK. If you're not already using Chat, check out Messaging for In-App, a newer in-app chat solution: Messaging for In-App Developer Guide.

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

  • Chat version 4.1.2
  • ServiceCore version 4.2.8

Update as of the Winter ’23 release: The Knowledge component (3.5.8) and the Case Management component (2.2.8) of the Service SDK have been retired. To learn more, see Knowledge SDK Retirement and Cases SDK Retirement.

To download 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.

New Features

  • Added a Terms and Condition check box to the pre-chat form. You can activate this by setting AttributedString to termsAndCondition on the SCSChatConfiguration object.

Known Issues

  • Adding a plist value in your app for View controller-based status bar appearance and setting it to YES will have no effect in the SDK and in your app. If you set this value to NO, you can then set Status bar style and Status bar is initially hidden in the plist file to control the status bar in the app.
  • Chat: When dragging a finger over UI elements while using VoiceOver, some elements in the chat feed are not read aloud.
  • Chat: Case creation using the SCSPrechatEntity 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
Loading