Version: 5.12

New Features and Bug Fixes Voice

New Features

This section lists new features in b+s Connects for Salesforce – CCE/CCX Editions.

#962: Make Directory Lookup configurable (for all Salesforce and custom objects)

Requirements: Users need the ability to search for phone numbers in the directory gadget by entering a name or number. The search should include phone numbers stored in standard objects and optionally in custom objects if configured. Additionally, the displayed fields in the search results should be configurable.

Solution Abstract: The feature introduces configurable search capabilities, allowing users to define which objects are included in the search—both standard and custom objects. Users can specify which field should be displayed as the name in the result list and which phone fields should appear. The search logic remains unchanged: name searches across all text fields and number searches across phone fields. Only fields containing values are displayed. Default configurations will be pre-set in the b+s Config record, but users can modify, add, or remove object configurations as needed.

Limitation: When enabled, directory numbers are always displayed at the end of the search results list.

Enhancements

This section lists enhancements in b+s Connects for Salesforce – CCE/CCX Editions.

#4346: As administrator I want the No softphone error message wording to be changed

Requirements: As an admin, I want the error message displayed when no softphone layout is set as default to be clearer. Currently, the message states: "No Softphone Layout is configured in the Salesforce settings." However, this message appears even when a softphone layout exists but is not set as default, which can be misleading.

Solution Abstract: The error message will be updated to: "No default Softphone Layout is configured in the Salesforce settings." This change ensures that admins understand the issue more accurately and can resolve it by setting a default layout.

Limitation: No functional changes; this enhancement only updates the error message wording.

#14210: Wrap-up Icons Added to DOM Multiple Times

Symptom: Wrap-up icons are repeatedly added to the DOM each time the UI is programmatically refreshed. While this is not currently visible to agents, it may impact performance.

Conditions: The issue occurs when the UI undergoes programmatic refreshes. Each refresh results in duplicate wrap-up icons being appended to the DOM.

Workaround: No direct workaround is available for users.

Further Problem Description: The accumulation of redundant wrap-up icons in the DOM could lead to unnecessary memory consumption and performance degradation over time. Fixing this issue will optimize resource usage and improve overall UI efficiency.

#14357: As customer I want to know how to configure Messaging (In-App and Web) in Routing Adapter

Requirements: Customers need clear instructions on how to configure Messaging (In-App and Web) in the Routing Adapter to adjust it to their specific needs. Currently, the documentation does not cover this configuration.

Solution Abstract: A new section will be added to the UQ Documentation targeted at Cisco administrators, explaining how to configure RoutingAdapter.ini for Messaging (In-App and Web). This will enable customers to modify the Routing Adapter according to their requirements.

Limitation: This enhancement is documentation-only; no functional changes to the Routing Adapter are included.

#14396: Replace CRM Session ID with CRM User ID as SSID in JavaScript

Requirements: For security reasons, the sessionId retrieved via UserInfo.getSessionId() must not be used as a user identifier in JavaScript. The session ID is currently written in clear text in multiple locations, including logs accessible to agents, posing a potential security risk.

Solution Abstract: The sessionId will be replaced with the user’s Id as the identifier in JavaScript. This change ensures that sensitive session data is not exposed while maintaining necessary functionality.

Limitation: SessionId will no longer be accessible for use in JavaScript-based operations. This change is classified as a security fix and will be reflected in the changelog.

Bug Fixes

This section lists priority 1 (Critical) and 2 (Major) issues that have been resolved in b+s Connects for Salesforce – CCE/CCX Edition but that may have been open in previous releases.

#14275: "Clear Connects Local Data" Does Not Clear Package Version

Symptom: After triggering "Clear Connects Local Data," the PackageVersion remains in LocalStorage instead of being deleted.

Conditions: The issue occurs when using the Clear Connects Local Data functionality.

Workaround: Users must manually delete the PackageVersion entry from LocalStorage to fully clear the data.

Further Problem Description: It's a cosmetic issue appearing in the logs generated by b+s Connects for Salesforce.

#14323: Format Rules Documentation Is Not Rendered Correctly

Symptom: The Format Rules documentation is not displayed correctly due to broken formatting.

Conditions: The issue occurs consistently in the documentation.

Workaround: N/A

Further Problem Description: The issue is caused by incorrect Markdown (MD) syntax in the Format Rules section, leading to improper rendering.

#14403: b+s Connects for Salesforce does not load with b+s Configuration Editor permission assigned to User

Symptom: b+s Connects for Salesforce does not load. SERVER_ERROR message is displayed when opening the gadget and the logs.

Conditions: b+s Configurator Editor permission assigned. No b+s Agent permission assigned.

Workaround: Assign b+s Agent permission to the user.