Skip to main content
Version: 6.0

Upgrade the package

Upgrade steps from 1.2 to 1.3.*​

Fix encoding issues from Webex to Salesforce​

To support non-ISO characters, the Message and Additional Parameters fields of the Web Chat Message request must be Base64 encoded. For details, refer to Base64 Encode Message. Please update your Webex Connect flow accordingly.

As a result of this change, the body of the Web Chat Message request has been updated.

In addition, if Additional Parameters are included in the request, make sure to also adjust that parameter and encode it as described in Additional Parameters.

Asynchronous requests migration​

In order to avoid token-retrieving issues and, at the same time, to limit the amount of API logins to the Salesforce Org, all requests sent to the Salesforce custom REST endpoint are now processed asynchronously (except those used to authenticate to the Org). If successful, the requests return a 202 (Accepted) status with a “queued” response.

Any error that may generate after the "queued" response is returned, will be logged in the new Enhanced Logger.

As a result, the response status code of the Salesforce custom REST endpoints has changed. Please update your Custom Nodes accordingly.

With the same change, the workItemIds in the Web Chat Message request response has been removed.

Multi configuration record per channel​

Starting with release 1.3, you can create separate b+s Partner Messaging Configuration records for each Messaging Channel. After upgrading to 1.3, link existing b+s Partner Messaging Configuration records to a Messaging Channel by setting the Messaging Channel Platform Key. (more details)

Manual update of the Configuration object layout​

After upgrading, the b+s Partner Messaging Configuration page layout must be updated manually.

Go to Setup > Object Manager > b+s Partner Messaging Configuration > Page Layouts, then open the layout currently in use and apply the following changes:

  • Remove the Deprecated field.
  • In the same position, add External Client App Client Id.
  • Move up Messaging Channel Platform Key, preferably directly below the record Name field.
  • Add Configuration Label in your preferred position on the layout.
  • If SMS is enabled, add the two Delivery Receipts fields.

After saving, the layout may not reflect immediately the changes applied due to a known Salesforce limitation. To force the UI cache refresh, click on the profile icon and change density, apply, then switch back to the previous setting. The layout should now display the changes applied.

All fields and their purpose are documented in the related feature sections of the documentation.

### Delivery receipts (for SMS channel only)

In version 1.3 the support for "delivery receipts" from Webex was introduced (for SMS channel only). A new field Webex Receipts Auth Id was added to the b+s Partner Messaging Configurations records. (more details)

Upgrade steps from 0.* to 1.*​

Configuration record migrated from Custom Metadata type to Custom Object​

In order to enhance the security aspect of the configuration data stored in Salesforce and, at the same time, improve scalability, the location for the configuration data was migrated from a Custom Metadata record to Custom object records.

Steps required:

  • Open Setup > Custom Metadata Types
  • Click on Manage Records next to b+s BYOOTT Settings

Copy the values from the Custom metadata (b+s BYOOTT Settings) record to a new Configuration object record according to the guide in the Configure b+s Partner Messaging for Webex Connect section.

  • Once the configuration values have been migrated to the new Configuration record, the Custom Metadata object b+s BYOOTT Settings can be deleted.
Last updated on