Salesforce Version 11 Release Notes and Log

Consensus for Salesforce, Version 11 Release Notes

Overview: 

In this document we will keep track of releases related to Salesforce Version 11.x. Our first major release was pushed to the AppExchange on 5/1/23, and as improvements or bug fixes need to be made, we will keep track of those follow-up/minor releases below as well.

Version 11.0

Date Released : 5/1/2023

Type: Major

Full Release Notes: Download Here
Technical Guide: Download Here

 

Introduction

*NOTE* Below is a small summary of the release. For full release notes, follow download link above.

A. Overview of the new version and its significance
The 11.0 major update focuses on bringing the Salesforce integration closer in line with Salesforce development best practices:

  • We introduce a new “DemoBoard” custom object to store Consensus data and improve the overall reporting capabilities for DemoBoard ROI on Accounts and Opportunities.
  • We’ve added new flows to help provide better high level totals on all standard objects, so that sales teams and admins alike can quickly see the impact Consensus is having across their accounts, opportunities, contacts, and leads.
  • New Recommended Layouts and Demolytics sections to help aid teams in surfacing up the data they need form Consensus
    • The new DemoBoard object allows for a better aggregate view on Opportunities and Accounts, allowing sales users to see the performance of their DemoBoards as a whole for each opportunity or account rather than seeing only Invitation-level metrics. Invitations are still available for viewing on the Opportunity object.
    • Invitations will be visible at the Contact and Leads level, allowing for simpler views on individual activity levels.
    • Additionally, we now have aggregate demolytics available for each Standard Object, showing total views, shares, watch time, and DemoBoards/Invitations along with averages for each record, instead of just showing these metrics for each demoboard or invite.
  • A new, easier to user DemoBoard creation form component improves user experience, and gives users access to a host of new features for customizing DemoBoards such as
    • DemoBoard Expiration by Days
    • DemoBoard 2FA
    • Improved control over Contact Synchronization on Accounts with large lists of contacts.
    • And more!
  • Simpler Permission Sets
  • New Report Types will now be available for use with our Demolytics, and users will be able to create custom Dashboards to display their Demolytic reports.
    • All metrics that were behind the Aura Component are now visible and available for use in custom reports. This will allow users to make better correlations between Consensus use and changes in Opportunity success.

 

Version 11.1

Date Released : 5/1/2023

Type: Minor

Release Notes: 

  • Minor release focused on improving permission sets for Salesforce version 11. 
  • Removes need to manually customize the permission set. 
  • Now Admins only need to go through a minimal effort to Clone included permission set, and "allow all custom settings" before assigning to the correct profile.

 

Version 11.2

Date Released : 7/27/23

Type: Minor

Release Notes: 

🪲 Bug Fixes

  • Apex Exception error: Consensus.LeadTrigger: execution of BeforeUpdate
  • Apex Exception error: Consensus.OpportuntyTrigger: execution of AfterUpdate
    • Seen in environments where batch jobs or other features focused on bulk updates to Opportunity Name or AccountID changes. The batch process would run, and then call our included opportunity trigger and receive a failure. 
  • When you search in CRM sync for an account name that has an apostrophe, you get an error that says "can't sync with your CRM."
  • When creating new contact roles in Salesforce, there was an issue with creating the correct Job Title value. It was taking the initial job title of the first invite to the DemoBoard, and applying it to all invited contacts. 
  • Duplicate Contact Roles being created in Orgs that had more than 50,000 contact roles. 
  • Flows - DemoBoard Account and Opportunity rollup errors. 
    • Removing both Account and Opportunity rollup flows. 
    • The data aggregation will now occur via apex during our batch updates. 

🔨 Improvements: 

  • When creating new leads into Salesforce, Consensus will now include Country and State information for the lead, if collected from our lead gate form. 
    • If picklists are on within the Lead object for those fields - it will try to use the Country/State  in the picklists - if the value exists in the picklist as id(abbr.) or display it will set it, if not it will not.
    • If picklists are off - it will always set Country/State in the format they are received from Consensus
  • Improvements to Consensus Users permission set.
    • This will now include access to Consensus app custom settings, and admins will no longer need to clone, and then check system permission for "view all custom settings" during configuration. 
    • Further lock downs in place to ensure this permission set is not given access to configuration tabs within our app. 
  • New and Improved "Consensus Admin" permission set:
    • Provides a more clear distinction for standard sales users, and admin users.
    • Admin permission set will provide the access needed to manage the Consensus app.  
    • Admin permission set will grant access to all configuration pages for the app
    • Upon installation, for Admin Permission set only, we still need to give permission to "Manage Applications" (this can be achievable manually). This permission is required for editing custom settings, and so making a "clone" of our included template permission set. and manually enabling this system permission is still necessary. 

 

Version 11.2.1

Date Released : 8/28/23

Type: Patch

Release Notes: 

  • Fix for Queuable job errors caused by the Opportunity Trigger. This patch removes apex code that utilizes a trigger for anytime there is an update to an opportunity Name. The trigger that sends updated name data back to Consensus has been temporarily disabled to fix the error. 
  • Fix for Heap Limit error seen on the Demo Record Update batch apex job. This fix reduces the response size from 500 to 200. 


Version 11.2.2

Date Released : 09/13/23

Type: Patch

Release Notes: 

  • Fix for SSO redirection issue that presented a maintenance page upon login.
  • Fix for scheduled apex jobs. They will now restart on their own in case of any error is found within the batch processing and wont' need manual intervention. 

 

Version 11.3

Date Released : 11/9/2023

Type: Minor

Release Notes: 

🪲 Bug Fixes

  • Notifications and Access List not being updated from demoboards created in SFDC
  • Too many query rows error causing Apex Jobs to fail
  • Recursive update found on included Lead Trigger
  • Rollup errors causing Flow Application emails for invitation and opportunity object fields.
  • Last DB Activity Date is empty on some demoboards
  • Missing DemoBoard affiliations for some View records in Salesforce.
  • CPU Failure error during RecentDemoBoards batch

🔨 Improvements: 

  • Formal Removal of all included Flows to our managed package. 
    • The Flows we introduced in our major 11.0 release have been removed because they were causing too many logical errors for trying to rollup data to the standard object fields we introduce for demolytics. 
    • These Flows will be removed, and all logic is being moved into our existing apex jobs for the time being. 
    • This will reduce Flow error emails, and problems with data being rolled up accurately for Demolytics
  • Introduction of Consensus Dashboard and bundled Reports
    • A new dashboard will be bundled with our package to show a singular view for demolytics and Consensus engagement
     
    • A new folder of reports is included out of the box now, in order to support this new dashboard.


  • Updates to required permissions for viewing the Consensus Configuration Page, and utilizing the Consensus Create Demo Invite component.
    • The Configuration page is now blocked to allow only users with the correct "Admin Permission set" to view.
    • The Create Demo Invite button is also disabled if current user doesn't have either 'Admin Consensus' or 'Consensus Users' permission set assigned.

 

  • CRM Sync Updates
    • Ability to require opportunity tie fields
    • Added additional validation on form fields

 

 

  • Removing need for Secondary Email checkbox on the configuration page.
  • Updates to the Consensus User Info table
    • The table now builds itself as new users authenticate successfully to the Consensus component
    • Logic has been added to our night User Info batch job to check if any users were disabled in the Consensus app. Users will be removed from the table automatically if they have been disabled in the web application. 
  • Improvements to Consensus Users permission set.

 

Versions 11.2.3 and 11.3.1

(automatically pushed to customers on 11.2 and 11.3 versions)

Date Released : 12/19/2023

Type: Patch

Release Notes: 

🪲 Bug Fixes

CRM Sync Filtering

  • Removed unsupported filter field types
  • Fixed input sanitizing
  • Fixed Multipicklist filtering
  • Fixed Long filtering
  • Fixed Email filtering
  • Fixed Percent filtering
  • Added Null and Not Null filter operations
  • Fixed filter not properly used when calculating selections in Selesforce Send Invitation Wizard

CRM Sync (Inactive User match)

  • We will now only run the queries with "Active" users when retrieving Accounts/Contacts/Opportunities for CRM Sync. Previously if there were duplicate users or emails, but one of those entries was inactive, CRM Sync was breaking.

Version 11.4

Date Released : 2/8/2024

Type: minor

Release Notes: 

🪲 Bug Fixes

  • Due to an issue reported by some clients where they had an error with 500 code for SalesLeadUpdate and RecentDemoBoard apex request in Sfdc, we're reduced the the request size and split it into multiple chunks to better process the data.

  • Fixed Apex Heap Size error that was experienced by a couple of customers during apex jobs. 
  • Fixed UI bug that would allow for multiple "add filter" popups to be opened when building CRM Sync filters in Salesforce. 
  • Fixed "Sync related contacts" issue where the contacts were replacing the existing contacts, instead of appending to the list of recipients.
  • The Title field reflects the Internal Title data instead of the External Title
  • The No-views Notifications setting was missing within the New Demo Invite modal
  • Updated the dashboard type from dynamic to standard.
  • Duplicate tasks get created for Demo Watched event. 
  • The 'phone' field was not being populated by leads created by Consensus.
  • New Leads weren't getting created if the Organization field wasn't filled in on the Consensus lead capture form.

🔨 Improvements: 

  • Added functionality to bypass email opt-out settings for contacts in Salesforce when sending DemoBoards within Salesforce native email.
  • Generate permission sets for Standard object. Those should have all the permissions needed for every functionality of the package to work without depending on the Profile permission
  • Generate permission sets groups for Admin and Consensus User

    1. Admin permission set group containing Standard and Custom permission set for Admin

    2. Consensus User permission set group containing Standard and Custom permission set for Consensus User

    3. It is now possible to Assign the Permission Set Group to any profile that can have them and it will contain all the standard and custom setting permission for the package to work. So no more clone and add permission to the Permission Sets, but use the Permission Set Groups instead.
  • Improvements to allow for better debugging.

Versions 11.4.1

(automatically pushed to customers on 11.4)

Date Released : 12/19/2023

Type: Patch

Release Notes: 

 

 

 

Versions 11.4.2

(automatically pushed to customers on 11.4.1)

Date Released : 5/16/2024

Updated Technical Guide: Download Here

Type: Patch

Release Notes: 

🪲 Bug Fixes:

  • Issue with Recipients/Leads when email has a special character inside
  • DemoBoards missing Demo and Invitation data due to synced Leads containing records with the ‘form’ array empty.
  • CPU Timeout due to Lead and Contact Triggers during data load (see below improvement)

🔨 Improvements: 

  • Added functionality to disable selected triggers for whole org, or only for chosen users. Effects of each disabled option are noted below. 
    • Here are the notes on the added functionality for the new Trigger control. 
      • Disable Account trigger - Nothing. This is currently a deprecated trigger
      • Disable Contact trigger - When Contact email is changed related invitations are not deleted
         
      • Disable Opportunity trigger - Nothing. This is currently a deprecated trigger
      • Disable Lead trigger - When Lead email is changed related invitations are not deleted. When Lead is converted, Invitations are not set to the created Contact and remain related to the Lead.
      • Disable DemoBoard trigger - Opportunity and Account rollup fields are not recalculated
      • Disable Invitation trigger - Contact, Lead and Demoboard rollup fields are not recalculated
      • Disable Feature trigger ChildRecordUpdateDate__c field on View is not set
      • Disable View trigger ChildRecordUpdateDate__c field on Invitation is not set
      • Disable Error Log trigger - Error Logs objects are not created even when debug mode is activated
      • Disable Batch Error trigger - Batch errors are no longer send to Error Logger (doesntt exist in 11.4)

Versions 11.4.3

(automatically pushed to customers on 11.4.2)

Date Released : 5/30/2024

Type: Patch

Release Notes: 

🪲 Bug Fixes:

  • Released a quick fix for the "Sync all related contacts" feature during demoboard creation. Previously this function would insert an empty row at the top of the recipient list.

Versions 11.4.4

(automatically pushed to customers on 11.4.3)

Date Released : 8/6/2024

Type: Patch

Release Notes: 

🪲 Bug Fixes:

  • Updated logic to fix instances of duplicate lead records
    • Previously we were looking up Leads by their associated email address, but we weren't paying attention to if the Lead had been converted.
    • Now we are looking up the Lead, checking if the Lead has been converted to a Contact, and then referencing the Contact's updated email address. This was to avoid some instances where we were seeing duplicates lead records getting created. 

🔨 Improvements: 

  • Contact RecordType Exclusion Filter. 
    • A new filter option has been added to the configuration page to allow for Admins to control which Contact RecordTypes should be excluded from our sync logic/batch updates. 
    • If there are Record Types that we should not associated Demoboard data to that share email addresses with other Contacts, you can select the record type and make sure we filter these types of contacts from our daily/nightly syncs. 
    • This will also impact the contacts we auto-populate on demoboards created in Snap and the web app when CRM Sync is utilize. If the Contact is associated to the opportunity, but is a type that should be excluded, we will not populate them as a recipient. 

 

Version 11.4.5

(automatically pushed to customers on 11.4.4)

Date Released : 10/17/2024

Type: Patch

Release Notes: 

🔨 Improvements: 

  • Task Creation:
    • Upon a demoboard invite or watch event, a new task is created on the matching contact/lead record.

    • If an opportunity record exists linked to the contact/demoboard, a task is also created on that opportunity.

    • The task title includes details about the demoboard event (e.g., "Demoboard Invite - [Demoboard Name]"). (Same as we have today)

    • The task description includes relevant information about the event (e.g., date, time, invitee details). (Same as we have today)

    • Demo Watched event

      • Look up dateView from View record in Salesforce to create new Demo Watch events.

      • Do not update the task after it is created the first time. It is meant to represent a moment in time when the view occurred.

    • Demo Invite event

      • Look up creation date of Invite record in Salesforce to create new DemoBoard Invite Event.

      • Do not update the task after it is created the first time. It is meant to represent a moment in time when the view occurred.

  • Automatic Task Assignment: 
    • The integration searches for a Salesforce user with an email address matching the Demoboard owner's email.

    • If a matching user is found, the task is assigned to that user.

    • If no matching user is found, the task remains assigned to the integration user or whatever user is running the plugin batch jobs.