Menu

Expand
Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Flex-Salesforce Integration Release Notes

Sep 20 2019 ( v1.1.0)

New Features

  • Configurable Interaction logging: You can now choose to configure your automated interaction logging - select which interactions ( task start, task complete, task switch) to log or to completely turn them all off. You can configure the interaction logging by navigating to the Configuration Screen.
  • Phone Number and Taskrouter SIDs validation: Configuration screens for Flex Salesforce Integration in the Flex Admin panel now have validations for Phone Number, Workflow SID and Task Channel SID. It means you don’t have to worry about mistakingly configure this with improper values - we will warn you right away.
  • Two new Screenpop Methods: Now you have two additional ways - you can pass either specific SFDC URLs( sfdcUrl ) or SFDC Object( sfdcObjectId) Ids as custom task attributes to dictate the ScreenPop behaviour in your Engagement flows.
    • The priority order between the 4 parameters used for search and screen pop is sfdcUrl > sfdcObjectID > sfdcSearchString > task.name

Fixes

  • Fixed extra whitespace in the CTI window introduced by Summer 19 Salesforce Release. Starting Summer 17 release, a Salesforce bug caused the bottom portion of the CTI window to be hidden behind the Utility bar. We introduced a workaround to this Salesforce bug in the Flex Salesforce Integration, which has now been removed.

Other Changes

  • Flex Salesforce Integration does not perform a `replaceAction` on `AcceptTask` anymore. This means that there will never be any conflicts of Flex Salesforce Integration with any other plugins in your environment.

May 15 2019 ( v1.0.5 )

  • Fixes: Incoming calls not displaying call acceptance controls in some some situations

April 11 2019 ( v1.0.4 )

  • Prevent outbound call when an agent is in an unavialable state in Flex, but clicks on a phone number on Salesforce.

Feb 28 2019 ( v1.0.3 )

GA Features

  • ScreenPop - New Objects are created when a search result is empty (Contact objects by default, other objects configurable)
  • ScreenPop - Search Objects (Contact by default, other objects configurable) and screen pop.
    • Search parameters can be dictated through task attribute – use attribute.name by default
  • (New) ScreenPop - Custom search using sfdcSearchString task attribute
  • Context Switch - change screen views depending on which task the Agent selects
  • Click to Dial (implemented via Twilio functions)
    • Caller IDs can be defined in this order: worker attribute (via SSO or direct) > configuration file > default ID
    • Warning notice if number clicked while already on the call
  • Automatically log activities as Tasks for the above actions
  • (New)Dual Monitor Support

Following features continues to be in Beta

  • Click to Dial (implemented via Twilio functions)
    • Caller IDs can be defined in this order: worker attribute (via SSO or direct) > default ID in Configuration Screen
    • Warning notice if number clicked while already on the call

Jan 29, 2019 ( v0.3.0 )

The current version of the Flex-Salesforce integration offers the following features:

  • ScreenPop - New Objects are created when a search result is empty (Contact objects by default, other objects configurable)
  • ScreenPop - Search Objects (Contact by default, other objects configurable) and screen pop.
    • Search parameters can be dictated through task attribute – use attribute.name by default
  • Context Switch - change screen views depending on which task the Agent selects
  • Click to Dial (implemented via Twilio functions)
    • Caller IDs can be defined in this order: worker attribute (via SSO or direct) > configuration file > default ID
    • Warning notice if number clicked while already on the call
  • Automatically log activities as Tasks for the above actions
Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.