Salesforce V2 Connector Change Log

The Salesforce V2 integration utilizes a connector which receives updates over time. These changes correspond with fixes, new features, or refined function for the integration. This article will capture and detail changes between versions of the Salesforce V2 connector as updates are deployed.

Update History

Captured below are versions of the connector which have been made available; alongside the changes associated with each connector version.

Connector Version Release Date Changes
2.69 18th of Sept 2023
  • Updated the SFv2 Connector to accommodate the Enhanced Domains change implemented by Salesforce.
2.68 13th of Sept 2023
  • For the time being, we have reverted the change that prevents Contacts and Users from accessing Learner Transcript Data if duplicate Usernames are detected.
2.67 29th of August 2023
  • Fixed an issue where learners with duplicate usernames could potentially access other learner transcript data.
  • Fixed an issue where batches to process deleted records (enrollments, classes, competencies, etc) would process all deleted records, rather than the subset of newly deleted records.
2.66 28th of August 2023
  • Fixed an issue where deleting a large number of records (for example, course enrollments) from the LMS could cause callout limits to be exceeded.
2.65 24th of August 2023
  • Updated the component for mapping default departments from a search box to a validated textbox.

    • This addresses the concern with seeing sub-departments when there are more then 1000.

  • Fixed an issue where failed HTTP requests could cause the sync job to terminate.

  • Fixed an issue where processing large amounts of records caused a performance concern.

  • Fixed an issue where very long session names would push the enrollment button out of view, preventing the ability for users to enroll in sessions.

2.64 Unreleased
  • Depreciated
2.63 11th of August 2023
  • Fixed an issue where downloading a certificate would exceed the 6MB heap limit. If the certificate is actually too large to download, an appropriate error message will now be displayed.

  • Fixed an issue where usernames containing apostrophes would fail to sync to Absorb.

2.62 1st of August 2023
  • Fixed an issue where un-syncing, then resyncing a Contact would not activate the Absorb User record correctly.

2.61 26th of July 2023
  • Fixed an issue that was introduced in v2.59 where a null value was being accessed in cases where the connector had not yet been authorized.
2.59 18th of July 2023
  • Fixed an issue where portals with SecureCDN enabled are unable to see badge images.

  • Fixed an issue where Contacts provisioned with the Invocable method were in an inconsistent state that prevented records (course enrollments, etc.) from being synced.

2.58 8th of July 2023
  • Fixed an issue where sessions with names longer than 80 characters were failing to sync.

  • Updated HTTP requests to improve performance by excluding unused fields from the response. This should reduce the number of timeouts experienced.

2.56 15th of June 2023
  • Clarified the explanation for creating a new department under the Absorb Department section in Setup.

  • Added a 30-minute sync interval.

This update contains a breaking change, and manual steps must be taken before this package is installed for existing users. These steps are not necessary for brand new installations:

1. Go to Setup > Object Manager and select the Setup Data custom object.
2. Select the Fields and Relationships tab
3. Click on Sync Job Frequency
4. Add a new value Every 30 minutes
5. After it is created, edit the new value and change the API Name to 0.5
6. Save the value.

2.55 17th of May 2023
  • Added a new Launch Absorb Lightning Web Component.

  • Renamed the old Launch Absorb Aura component to Launch Absorb (Aura).

2.53 15th of May 2023
  • Fixed a mappings issue for Community Users launching Absorb. 
2.51 24th of April 2023
  • Added extra error handling around missing custom metadata objects.

2.50 10th of April 2023
  • Fixed an issue where the connector was sending null values to our LMS API.


Installation Instructions

Updating between versions of the Salesforce V2 connector is currently a manual process. To confirm if you should update to a new connector version, first check in Salesforce to determine what connector version is currently installed. To check the version of your current connector:

  1. Open the settings for your business unit.
  2. In Account Engagement, click the gear icon and then select Settings.
  3. In the Lightning app, select Account Engagement Settings.
  4. Your version number is shown in the Connector Version row.

If you have confirmed you are using an older version of the Salesforce V2 connector and you would like to update. Please open a support ticket and a support agent will work with you to schedule a meeting and process the update. The current process for updating the connector is as follows:

  1. Schedule a screen-share meeting to facilitate the update.
  2. The Salesforce integration user on your side will login to Salesforce.
  3. The Salesforce integration user will disable the data feed.
  4. The Absorb agent will share a link which redirects to an installation page on the Salesforce side.
  5. The Absorb agent will briefly request access to control your screen so they can enter the password for the new package version.
  6. The new package will be installed for all admins in your Salesforce environment.
  7. After allowing time for the installation to process, the new connector version should be displayed in the 'Connector Version' row discussed above. The installation may take between five to thirty minutes to process.
  8. The Salesforce integration user will enable the data feed.
    • Optionally, the Salesforce integration user can reset the data feed so it starts syncing immediately once enabled rather than having to wait for the next run.



Was this article helpful?
1 out of 3 found this helpful