Skip to main content
Version: 5.9

New Features and Bug Fixes Ext MRI 2.5.1

New Features​

This section lists new features in b+s Connects for Salesforce – Ext MRI 2.5.1

  • None

Enhancements​

This section lists enhancements in b+s Connects for Salesforce – Ext MRI 2.5.1

FIN-11958 - As an Administrator I want to have an improved Default .ini Configuration File​

Requirements: Logs everything as per default on info level. The default .INI files include a section for Live Agent Chats. Added a commented out section for sandboxes.

Solution Abstract: Change the default .INI configuration.

Limitation: n/a

FIN-12230 - As an Administrator I want the Cisco Task Information to be updated when a Task is rerouted​

Requirements: When a task is re-routed, the RA Ext-MRI should query the latest task data from Salesforce.

Solution Abstract: Add a setting per entity to enable this behavior: RequestFieldsOnReroute=false

Limitation: Does not apply to timeouts and overflows from the ICM script.

FIN-12328 - Support the latest Salesforce REST and Streaming API version​

Requirements: The RA Ext-MRI supports the latest REST and Streaming API version.

Solution Abstract: Use v55 in the default .INI file.

Limitation: n/a

Bug Fixes​

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

FIN-12669 - RA Ext-MRI Queue can get stuck if Routing is Disabled​

Symptom: The RA Ext-MRI routing queue can become stuck if the PIM sends a routing disabled message.

Conditions: Routing disabled must be sent.

Workaround: Restart the RA.

Further Problem Description: The queue is not properly reset when the routing gets disabled.

FIN-1753 - RoutingAdapter stays offline after network interruption​

Symptom: Agents are not able to login into media domain. Agent Adapter stays offline.

Conditions: Routing Adapter loses connection to salesforce, recovers connection and starts to recover tasks and loses network connection again during recovery.

Workaround: Restart Sfdc Routing Adapter

Further Problem Description: N/A