This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
4386members
1425posts
This is a verified product documentation article. For case-based resolutions articles, please reference the Knowledge Base section of Invoca Community.

Salesforce Sales Cloud: Version release notes

stevestormoen
Employee
Employee

on ‎10-12-2018 05:32 PM - edited on ‎11-13-2024 10:27 AM by Employee

This is the seventh article in a series teaching you everything you need to set up, support, and succeed with the Invoca for Salesforce Sales Cloud integration.
 

  1. Integration Overview 
  2. Pre-installation checklist 
  3. Installation guide 
  4. Data flow and matching logic 
  5. Using your integration 
  6. FAQs and Troubleshooting 
  7. Version release notes (You are here)


The newest version of the package can be installed from Invoca’s AppExchange listing. See below for information about version 5.7 and the process to upgrade.

To view the Salesforce package version your org currently has installed, click Setup, App Setup, Installed Packages. Search for “Invoca Enterprise”.

Attention all customers:
Salesforce will be retiring Salesforce API versions 20.0 - 30.0 in their Summer 2025 Release. All Invoca package versions from v1.0 to v5.2 use Salesforce API versions in this range. You will need to upgrade to Invoca package v5.6 before the Salesforce Summer '25 release.

 

November 2024 version 5.7 - Matching and Conversion Reporting Enhancements

We're excited about the matching and conversion reporting enhancements in our latest version. Here is a rundown of what's new in version 5.7:

  • There was a bug around populating the AdWords Matchtype and IVR Duration fields on the Invoca Call Log. This has been fixed.
  • When configuring Field Mapping in the Invoca Admin tab, you can now map Invoca data to Picklist-type fields on standard object records. Note that we still do not support mapping Invoca data to Multi-select Picklist type fields. When mapping Invoca data to Picklist type fields, make sure the Invoca values match the values available in the field's drop down menu.
  • With this update, our "matchback" matching logic will now run when Phone-type fields on the standard object records are updated. In previous versions, "matchback" logic only executed when the standard object record was first created. As an example, this will allow the package to catch matches when a Lead is created without a Phone field or with an incorrect Phone field that is then updated later.
  • In version 5.7, the logic to report Lead Statuses or Opportunity Stages back to Invoca will execute as soon as the record is matched to the Call Log. In versions 5.5 and 5.6, conversion reporting was only triggered after a Call Log was matched to the record and the Lead Status or Opportunity Stage was actually updated. This change will result in more complete conversion data being reported back to Invoca.
  • The package now supports "future methods" in conversion reporting. This comes into play if your Salesforce org has a batch job that auto-updates Lead Statuses or Opportunity Stages in bulk. Prior versions do not support future methods when reporting Lead Statuses or Opportunity Stages back to Invoca. 

 

General Steps to Upgrade to Invoca Enterprise Version 5.7

1. Before upgrading to v5.7 from older versions, take a screenshot of your current Invoca Admin page
When upgrading to 5.7 from versions 1.0-5.4, the Invoca Admin settings must be reconfigured. Having a screenshot to reference will help you reconfigure the settings quickly.

However, if you are upgrading from 5.5+, you will not need to reconfigure the Invoca Admin settings. 

2. Install version 5.7 in your sandbox
It is a best practice to install and test managed packages in your sandbox, and most ideally a full copy sandbox. Click the following link to install in your sandbox org: 

https://test.salesforce.com/packaging/installPackage.apexp?p0=04tKk0000004dwA 

Please note that once you upgrade to version 5.7, it is not possible to revert back to a prior version!

3. Configure your Invoca Admin settings
When upgrading from versions 1.0-5.4 and after installing 5.7, go to the Invoca Admin tab and re-configure your settings according to your preference. When upgrading from versions 5.5+, double check your Invoca Admin settings to confirm everything carried over correctly.

Note: versions 1.0-4.8 were able to match Invoca Call Log records to Contacts and Leads. In newer versions, you will have the option to match Invoca Call Log records to additional objects (Contacts, Leads, Accounts/Person Accounts, Opportunities, and Cases).  If you are interested in maximizing your closed loop conversion reporting of Opportunity Stages back to Invoca, we recommend you select the check boxes to match to Leads, Accounts, and Opportunities.

4. Connect Invoca to your sandbox org
In order to test the data flow from Invoca to your Salesforce sandbox, you will need to connect a Salesforce Sales Cloud connect app tile in Invoca with your Salesforce sandbox org.

The best practice is to set-up a new Salesforce connect app tile, so you can keep your production org(s) connected with the existing connect app tile(s) you have configured. If you integrated your production org at the "Network" level, choose a Profile to integrate with your sandbox org. Click into the specific Profile and go to Integrations > Manage Integrations. Find the Salesforce Sales Cloud tile and proceed through the steps to authorize with your sandbox org. If you integrated your production org(s) at the "Profile" level, you may wish to integrate your sandbox org at the "Network" level and follow the steps to authorize with your sandbox. Once connected, you may wish to choose specific Invoca Campaigns to filter the calls that are sent to the integrated sandbox. Only one connect app can be configured at the Network level and one can be configured in each Profile. 

If you aren't seeing the "Ready to Integrate" option in the Salesforce Sales Cloud connect app tile, please reach out to the Technical Services representative assisting with your upgrade or reach out to your Customer Success Manager for help.

Once authorized, double check the Campaigns specified, when you want data sent to Salesforce, and the version should be "3.x to 4.x".

5. Complete test calls and convert Leads / Opportunities
Data should be flowing to your sandbox! You can complete a few test calls to Invoca promo numbers to verify the matching logic. If configured for closed loop conversion reporting to send Lead Statuses or Opportunity Stages back to Invoca, we recommend proceeding through a normal sales flow by converting a Lead and an Opportunity to make sure the Signals make it back to Invoca as expected. Look in the Transaction Details report and filter for the Post Call Event types to more easily find the data coming from Salesforce. If matching to Cases, it is recommended to complete a standard Case flow as well.

6. When all looks good in your sandbox, install in Production
Once you feel comfortable with the data and how the managed package is working in your sandbox (again, preferably your full copy sandbox), it's time to upgrade the package in your production org. You can install the package from AppExchange or click this link: 

https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKk0000004dwA 

Note, once you upgrade, you cannot revert to previous versions!

7. Configure your Invoca Admin settings
Once version 5.7 is successfully installed in your production environment, go ahead and reconfigure or double check your Invoca Admin tab settings. 

8. Re-establish the Invoca Salesforce Sales Cloud Connect App connection
It's a best practice to re-authorize the connection from the Invoca side, particularly if you upgraded from a much older version (e.g. 3.x and below). To reauthorize, navigate to the Salesforce Sales Cloud connect app. Click the hyperlink to de-activate the integration. Then click the + New Connect App button, choose Salesforce Sales Cloud, and proceed through the authorization wizard. Double check the Campaigns specified, when you want data to send, and the version should reflect "3.x to 4.x".

9. Monitor to make sure things look good
You're all set-up! Now it's just time to check in and monitor things periodically to make sure all is flowing, matching, and passing through successfully. 

-----

Install from AppExchange or use the package install links below:

 

June 2024 version 5.6 - Invoca Admin Enhancements

The Invoca managed package had a facelift! We have a completely reimagined Invoca Admin UI. The settings are separated out into different sections for easier navigation. We also added a few enhancements based on customer demand, including:

  • Added Marketing Data Category, Short Text, and Long Text/URL fields. The package has slots for 30 Category fields, 60 Short Text fields, and 10 URL fields.
  • Added Field Mapping support when the Call Log is matched to objects using “match back” and (optionally) any time the Invoca Call Log is updated.
  • Added the ability to enable/disable match back logic
  • Added the ability to enable/disable Tasks (i.e. Invoca Call Activity) for each object
  • Option to enable/disable Phone field matching when Call Log is first created
  • In Conversion Reporting, made the option to send a partner unique ID more intuitive.
  • We will no longer match to converted Leads.
  • When mapping an Invoca field to a field on the matched Salesforce record, we will no longer attempt to overwrite a field when the Invoca value is null or empty.
  • Removed the "stripped phone" fields, "formattedphone" fields, and "textphone" fields for net new installs.
  • Support for when Invoca sends multiple transactions in a single request (i.e. "batch").
  • Conversion reporting now supports mapping picklist field values.

-----

Install from AppExchange or use the package install links below:

 

 

March 2023 version 5.5.4 - Major Matching Enhancements

Version 5.5.4 is a massive release! It's probably the biggest development effort we've tackled since the package was first introduced way back in 2014. 

Here is a rundown of what's different between version 5.5 and prior versions:

NEW 5.5.x version Invoca Version 5.2 Invoca Older Versions
     
Additional Marketing Data Category fields
Supports up to 12 Marketing Data "Category" type fields


Why is this important? If you have 2 additional Category fields (most often to support Invoca for Contact Center use cases), adding the 11th and 12th Marketing Data Categories broke your Salesforce integration! That's not good, so we fixed it in version 5.5.		 Supports up to 10 Marketing Data "Category" type fields Supports up to 10 Marketing Data "Category" type fields
     
Upgraded Salesforce APIs
Uses Salesforce APIs > version 30.0


Why is this important?
Salesforce is retiring their API versions 20.0 - 30.0 in their Summer '25 release. Older versions of the Invoca package use some of the versions that will be retired. Once the API versions are retired in 2025, older versions of the Invoca package will start to see errors and key functionality will not work. Customers need to upgrade to the new package version to avoid issues.		 Uses Salesforce APIs to be retired in the Salesforce Summer '25 Release Uses Salesforce APIs to be retired in the Salesforce Summer '25 Release
     
Match to more object types
Supports matching to Leads, Contacts, Accounts/Person Accounts, Opportunities, Cases


Why is this important?
By matching directly to Accounts, call insights will more reliably match to Opportunities. This will help ensure your conversion reporting back to Invoca is as complete and accurate as possible. In addition, the ability to match to Cases provides call insights to your support and care teams. 		Supports matching to Leads, Contacts, Accounts/Person Accounts, Opportunities, and Cases Supports matching to Leads, Contacts, and Person Accounts
     
Match to Opportunities through related Account
Matches to Opportunities by referencing the Phone fields on the related Account


Why is this important?
Opportunities do not have phone fields by default, so it is more accurate and turn-key to match to Opportunities by looking up the phone fields on the related Account record.		 For Opportunities, matches using a custom Phone field added to the Opportunity when the package is installed. Requires the customer to map a phone number to the Phone field on the Opportunity Does not match Call Logs directly to Opportunities
     
Searches all phone-type fields
Uses SOSL to search across all fields of type:Phone to find matching records


Why is this important?
SOSL searches phone fields and doesn't require exact matches! This eliminates the need to copy phone numbers to custom Invoca "stripped" phone fields. Plus, searching across all phone fields helps to maximize matches. 		Uses SOQL to match using the a pre-defined list of fields of type:Phone to find matching records. Uses SOQL to match using only the default 'Phone' field.
     
Matching does not rely on custom "stripped" phone fields
The package no longer copies phone field values to custom "stripped" fields created by the package.


Why is this important?
When previous packages would copy and paste phone field values to the custom Invoca "stripped" phone fields, it would count as a record modification. If customers had any automated processes based on record updates, this would unintentionally kick them off. This created undesirable consequences, so we changed our processes to "touch" standard object records as little as possible!		 Creates custom fields on all the standard objects (Leads, Contacts, Accounts, Opportunities, and Cases). Has triggers to copy phone field values to custom "stripped" phone fields every time a new standard object record is created or edited. Creates custom fields on the Lead and Contact objects. Has triggers to copy phone field values to custom "stripped" phone fields every time a new Lead or Contact is created or edited.
     
No batch processes
Since we moved to SOSL and no longer use the "stripped" phone fields for matching, we no longer execute batch processes at the time the package is installed.


Why is this important?
For cusomers with many records, these batch processes took a significant amount of time and bandwidth to run! They are no more!		 Has batch processes at install to copy phone values to "stripped" phone fields for every record of each object type (Leads, Contacts, Accounts, Opportunities, and Cases) Has batch processes at install to copy phone values to "stripped" phone fields for every Conact and Lead record
     
Custom matching expanded to all object types
Provides the option to customize the fields to use for matching across all objects (Lead, Contact, Account/Person Account, Opportunity, Case)


Why is this important?
Just a little bonus enhancement in case customers have more advanced matching needs for their Accounts/Person Accounts, Opportunities, or Cases!		 Provides the option to customize the fields to use for matching for Leads and Contacts Provides the option to customize the fields to use for matching for Leads and Contacts
     
Field mapping expanded to all object types
Provides the option to map Invoca data to Salesforce fields when a Call Log is first created and matched to a Lead, Contact, Account, Opportunity, or Case record


Why is this important?
This is another optional little bonus enhancement. It can help to provide Invoca call data at a glance, right on the record! Note that if you map Invoca fields to fields on matched records, that will count as a record modification, so double check any automated flows or processes that are based on modified records!		 Provides the option to map Invoca data to Salesforce fields when a Call Log is first created and matched to a Contact or Lead record. Provides the option to map Invoca data to Salesforce fields when a Call Log is first created and matched to a Contact or Lead record.
     
Enhanced "match back" logic to support +1
When a new standard object record is created, we will attempt to search all "orphaned" Invoca Call Log records to see if any match this new record. This "match back" logic now supports numbers that include the North American Numbering Plan country code (e.g. +1 or a leading 1)


Why is this important?
Without this special logic to account for the North American Number Plan country code, the match back logic doesn't actually work if you happen to include the leading 1 or +1 in your phone numbers, so it's a good thing!		 "Match back" logic does not support e164 format or Phone fields values that include country codes. There is no "match back" logic.

 


Note: There are some small code changes between v5.5 and the 5.5.1-5.5.4 patch versions.

Version 5.5.1 addresses 3 things:
- Expands the options available in the Salesforce field drop down in the Field Mapping section of the Invoca Admin tab. 5.5 did not include Text Area and Phone-type fields. 5.5.1 does. 
- Addresses an issue if you set-up the Field Mapping section to map multiple Invoca fields to the same object type.
- Addresses an issue with the matching query if you created a custom field on your Opportunity object with a Field Name that matches exactly to Phone__c. 

Version 5.5.2 addresses 1 thing:
- For customers that match to Cases, 5.5.2 addresses an error if a user selected a Contact to associate to the Case record when creating new Case.

Version 5.5.3 addresses 1 thing:
- For customers that choose to create new Leads when there is no match, 5.5.3 now supports mapping Invoca values to fields on the Lead that the Invoca package creates. 

Version 5.5.4 addresses 2 things:
- There was an issue in previous versions that prevented reporting Lead Status changes back to Invoca if there was a mismatch between the field label and API name. That is fixed up in v5.5.4.
- Very rarely, a customer might encounter a Salesforce bug when installing the package related to the WhatId in the RelatedContent section of the Task layout. We have removed the WhatId from the RelatedContent section in the Task layout in 5.5.4 to avoid this error.  

 

-----

Install from AppExchange or use the package install links below:

 

 

DO NOT INSTALL PREVIOUS PACKAGE VERSIONS.
Salesforce will be retiring Salesforce API versions used in previous packages in their Summer 2025 release. 

 

 

February 2021 version 4.8 - Shield Ready

There have been a few behind-the-scenes iterations to get Shield ready and we're excited to make version 4.8 available to you. In this release, we made a few updates to make sure the managed package is compatible with organizations that have Shield Encryption enabled. A couple notes:

  • If you destroy your encryption key that is stored in Salesforce at any point, matching logic will not function as expected. 
  • If you expect Invoca to match the Invoca Call Log to Contacts/Person Accounts or Leads using the caller ID and Phone field value, you must use deterministic encryption and you cannot encrypt the custom FormattedPhone field that is created when the package is installed.
  • Further, if you are configuring custom matching rules, the fields you choose to match against cannot be encrypted. 
  • Here is a specific list of fields we have validated you can encrypt without compromising the default matching functionality:

Account
    Billing Address
    Phone
    Shipping Address

Contact
    Assistant Phone
    Email
    Fax
    HomePhone
    MailingAddress
    MobilePhone
    Name
    OtherAddress
    OtherPhone
    Phone

Lead
    Address
    Email
    Fax
    MobilePhone
    Name
    Phone

Invoca Call Log
    INVOCA_FOR_SF__calling_phone_number__c
    INVOCA_FOR_SF__City__c
    INVOCA_FOR_SF__whitePagesData_Address__c
    INVOCA_FOR_SF__whitePagesData_City__c
    INVOCA_FOR_SF__whitePagesData_State__c
    INVOCA_FOR_SF__whitePagesData_Region__c
    INVOCA_FOR_SF__whitePagesData_Zipcode__c
    INVOCA_FOR_SF__whitePagesData_FName__c
    INVOCA_FOR_SF__whitePagesData_LName__c
    INVOCA_FOR_SF__linked_email_addresses_data_append__c
    INVOCA_FOR_SF__primary_email_address_data_append__c
    INVOCA_FOR_SF__address_coountry_data_append__c
    INVOCA_FOR_SF__display_name_data_append__c

 

App Requirements/Package Install Links

 
 

 

August 2019 version 4.2 - Select the Opportunity Stages that will report Revenue back to Invoca

In version 4.1, we introduced the option to report multiple Opportunity Stages to Invoca. These Stages appear as Signals in Invoca reports. In cases where a Salesforce field was mapped to the Invoca Revenue field, the revenue was reported for each Opportunity Stage. This made it so multiple Signal transactions associated with the same call had revenue attached. For many Invoca Networks, this made the revenue for the call appear inflated (specifically in cases where the back-end feature "Signal transactions roll-up" was not enabled).

With this version, we're introducing more control as to when revenue is actually reported to Invoca. For example, it's now possible to report every Opportunity Stage to Invoca, but only pass revenue with the Closed/Won stage.

 

App Requirements/Package Install Links

 

 

June 2019 version 4.1.1 - Support Reporting Lead Statuses or Opportunity Stages to Invoca as Signals while the Call is still in Progress

We have learned there are some scenarios where a Lead progresses through different Statuses or an Opportunity progresses through different Stages while still on the call with the customer. The integration now supports sending those Statuses or Stages to Invoca while the call is still in progress. The Signals will post to Invoca reports after the call completes. 
 

App Requirements/Package Install Links

 

 

October 2018 version 4.1 - Invoca Console Compatibility with Salesforce Lightning and Option to Report Multiple Lead Statuses and Opportunity Stages

This is a big release! There were three noteworthy enhancements.

1. New option for matching an Invoca Call Log to a Contact or Lead record

In previous versions, there were only three matching options. 

- Assign to Matching Caller ID or Create New Lead
- Assign to Matching Caller ID Only
- Create New Lead for Every Call

In version 4.1, there is now a fourth option to have the package create the Invoca Call Log, but to skip matching the Call Log record to a Contact or Lead record. This is very beneficial for customers that wish to build their own custom matching through apex triggers or Process Builder rules to match an Invoca Call Log to a Contact or Lead record (or even another Custom Object record). 

2. The Invoca Console component is now compatible with Lightning

In previous versions, the Invoca Console was only a custom homepage component. The component appeared in the sidebar in Salesforce Classic. Since Salesforce Lightning has a side navigation menu, the original component was not compatible in Lightning.

In v4.1, we now offer a new Invoca Console for Lightning component. It utilizes the utility bar (the sticky ribbon at the bottom of the Invoca for Lightning app pages) to display in progress and recently completed calls.

3.  Select multiple Lead Statuses and Opportunity Stages to report back to Invoca as Signals.

In previous versions, customers had the option to report a Signal to Invoca when a Lead converted and when an Opportunity moved to a specific Stage (only one Opportunity Stage could be selected). We heard the demand loud and clear to be able to understand the different milestones for a Lead or Opportunity associated with an Invoca call. Customers can now select multiple Lead Statuses and multiple Opportunity Stages to report as Signals back to Invoca.

Note, if upgrading to the new package from a previous version, be sure to take a screenshot of your Invoca Admin settings in Salesforce. Once you upgrade to the newest package, you will need to review the Invoca Admin settings. Since there were changes to the conversion mapping section, you may need to re-set those settings to your desired configuration.

App Requirements/Package Install Links

 

 

May 2018 version 4.0 - Report Signals and Custom Data from Salesforce back to Invoca

When reporting conversions from Salesforce back to Invoca, the conversions will be reflected as “Signals”. In previous app versions, conversions from Salesforce were reflected as “Reported Conversions” in Invoca. 

By reporting conversions from Salesforce as Signals, you can automatically share the conversions from Salesforce to other platforms through our other integrations, like AdWords Offline Conversions or Facebook. 

When a Lead converts to an Account/Contact/Opportunity, the Signal Name will be “Lead Converted”. When an Opportunity converts based on the designated stage in the Invoca Admin settings, the name of the stage will appear as the Signal Name (e.g. “Closed/Won”).

In addition, you can map Salesforce fields to Custom Data fields when reporting a Signal back to Invoca. This allows you to view Salesforce information and incorporate Salesforce data in Signal rule builder.

Important Information:
Prior to upgrading to this new app version, customers should confirm the Signal feature is enabled for their Invoca account. 

There were two additional, smaller enhancements in v4.0:

  1. We have modified the default call log layout to show more data points and to provide better grouping. This will only apply if you are installing the package for the first time. If you are upgrading the package from a prior version, any customizations you have made to the Invoca Call Log will persist.
  2. We have also removed a few deprecated fields from the Invoca Call Log (old Voice Signals).


App Requirements/Package Install Links

0 Kudos
Need more help?

Don't see what you are looking for? You can ask the Community or contact support.

Copyright © 2024 Khoros, LLC