Guided Selling - 2024-03 Patch 2

The Guided Selling March 2024 Patch #2 is now available for installation. Below, please find the implementation steps, a list of new features, and links to new Support articles. 

REVENUE INTELLIGENCE PACKAGE REQUIREMENTS - To install the latest version of the Guided Selling version you will need to have installed version 1.101 of the Revenue Intelligence package or later. This install must be made before installing the latest Guided Selling version.

SANDBOX TESTING REQUIRED - All installation of Guided Selling requires sandbox testing to ensure compatibility with all of your core workflows and business-critical steps that have been customized in Salesforce.

Guided Selling March Update

The Guided Selling March 2024 Patch #2 provides key updates to the previously released March 2024 release.

Implementation Steps

Steps by Package Version

Follow the steps below to upgrade to the Guided Selling March 2024 Update release based on your installed version. Not sure what version you are using. Ask your Admin to check the version of the installed packages within Salesforce's setup admin.

  • For customers installing Guided Selling for the first time you can take a look at our getting started guides to make sure that your admins are installing and configuring the package for use by your team.

  • If you have previously installed Version 9.58 of the Guided Selling package, you will need to execute the following installation steps:

    Upgrade the package version v9.58.5 in the same org that previously had v9.58 installed Go to the developer console and run these scripts from the Anonymous window

    Database.executeBatch(new BackfillSequenceAssociationsBatch('Contact'));
    Database.executeBatch(new BackfillSequenceAssociationsBatch('Lead'));

  • Some organizations have reported that actions vanish or disappear from Engage immediately after upgrading. If you encounter this and do not see the " PopulateSeqAssociationLookupBatch" running in your Apex Jobs list, follow the steps provided in the article linked here to manually start the batch:
    Manually Run Sequence Associations Backfill Batch

    Processing time for this batch depends on the volume of records in your Salesforce instance. We recommend running installs after business hours to avoid impact to your end users.

    Disable Campaign and Campaign Member Triggers (Optional)

    When upgrading from some older versions of Guided Selling, we've observed instances where trigger settings will default all objects on. Some organizations choose to disable certain triggers to reduce the number of concurrent batch jobs and triggers running in the background. As a best practice, we recommend enabling triggers for objects you have Sequences created for.

    If your organization contains many Campaign and Campaign Member records and Campaign sequences are not being used, we strongly recommend disabling the Campaign and Campaign triggers for performance purposes. 

    1. Navigate to the Guided Selling App | Settings | Triggers

    2. Validate your list of enabled triggers. For instance, if you are not running any Campaign Sequences, consider disabling Campaign and Campaign Member.

    Assigning Batch Owners:

    1. Click the “Set Batch Owner ” button on the Sequence Settings>Batches page. This will initiate new Apex Jobs and ensure they are owned by your user.   
    2. Navigate to the Users section on Sequence Settings and click “Grant All Permissions ” to ensure the Guided Selling Standard Object Permissions is current based on your Sequences Entrance and Exit criteria.
    3. Change Custom Setting RTE Settings "Use Deprecated" to false in the Salesforce setup. RTE_Settings.png
    4. Update the new Guided Selling Error Email custom setting to specify which email addresses you want Guided Selling errors to be emailed to. By default, the Setting will be configured with the user who clicks the Set Batch Owner button (step 1 above).Error_Email_Setting.png
    5. Create a New Remote Site Setting. Go to SetupRemote Site Settings. Open the one named "Revenue". Clone it. Update name to Revenue_Enhanced. Change URL to https://ringdna.my.salesforce-sites.com. Save.
  • Disable Campaign and Campaign Member Triggers (Optional)

    When upgrading from some older versions of Guided Selling, we've observed instances where trigger settings will default all objects on. Some organizations choose to disable certain triggers to reduce the number of concurrent batch jobs and triggers running in the background. As a best practice, we recommend enabling triggers for objects you have Sequences created for.

    If your organization contains many Campaign and Campaign Member records and Campaign sequences are not being used, we strongly recommend disabling the Campaign and Campaign triggers for performance purposes.

    1. Navigate to the Guided Selling App | Settings | Triggers

    2. Validate your list of enabled triggers. For instance, if you are not running any Campaign Sequences, consider disabling Campaign and Campaign Member.

    Assigning Batch Owners:

    1. Click the “Set Batch Owner ” button on the Sequence Settings>Batches page. This will initiate new Apex Jobs and ensure they are owned by your user.   
    2. Navigate to the Users section on Sequence Settings and click “Grant All Permissions ” to ensure the Guided Selling Standard Object Permissions is current based on your Sequences Entrance and Exit criteria.
    3. Change Custom Setting RTE Settings "Use Deprecated" to false in the Salesforce setup. RTE_Settings.png
    4. Update the new Guided Selling Error Email custom setting to specify which email addresses you want Guided Selling errors to be emailed to. By default, the Setting will be configured with the user who clicks the Set Batch Owner button (step 1 above).Error_Email_Setting.png
    5. Create a New Remote Site Setting. Go to SetupRemote Site Settings. Open the one named "Revenue". Clone it. Update name to Revenue_Enhanced. Change URL to https://ringdna.my.salesforce-sites.com. Save.

      Delete rdnacadence__Unique_Id__c from Participant Sequence History object.

      This is a legacy field that is deprecated, though if left in an org it will cause issues in future upgrades.

      1. Click the “Set Batch Owner ” button on the Sequence Settings>Batches page. This will initiate new Apex Jobs and ensure they are owned by your user.   
      2. Navigate to the Users section on Sequence Settings and click “Grant All Permissions ” to ensure the Guided Selling Standard Object Permissions is current based on your Sequences Entrance and Exit criteria.
      3. Change Custom Setting RTE Settings "Use Deprecated" to false in the Salesforce setup. RTE_Settings.png
      4. Update the new Guided Selling Error Email custom setting to specify which email addresses you want Guided Selling errors to be emailed to. By default, the Setting will be configured with the user who clicks the Set Batch Owner button (step 1 above).Error_Email_Setting.png
      5. Create a New Remote Site Setting. Go to SetupRemote Site Settings. Open the one named "Revenue". Clone it. Update name to Revenue_Enhanced. Change URL to https://ringdna.my.salesforce-sites.com. Save.
      6. Replace the legacy Template Edited field on the Participant Action object. 
        1. Update the page layout for the Participant Action to include the unused "Template Edited" field and remove the legacy one currently on the page layout.  
        2. Delete the legacy Template Edited field from the Participant Action (must be done on Salesforce Classic)

    Disable legacy Process Builders:

      1. Rollup Field on Participants(Email Replied)
      2. Rollup Field on Participants(Email Sent)
      3. Rollup Field on Participants(Email opened)
      4. Rollup Field on Participants(Is Deferred)
      5. Rollup Field on Participants(Is Performed)

Post Implementation Step

As a post-upgrade step, add field ringdna__HasOptedOutOfSms__c to ringDNA_Sequence_Contacts and ringDNA_Sequence_Leads field sets. 

Updates in the March 2024 Patch 2

Bug Fixes 

  • A fix for an issue which caused incorrect values in rollups related to email events (like number of emails sent, opened or replied and links clicked).
  • A fix for an issue where a very large number of actions on the Engage page would cause a Salesforce heap limit to be hit.
  • For sequences that have exit criteria based on the call disposition, a call with a disposition that should cause the Participant to exit the sequence would fail to create a Task activity for the participant to log the call details. This has been fixed.
  • Fixes an issue where delegated sequence agents could not complete their assigned actions when the admin owned the participant.
  • Fixes an issue where User Name values are not properly displayed on the picklist of the Entry or Exit criteria edit view.
  • For customers that are on a patch version (eg 9.135.5), the app would show patch versions lower than that (9.135.4) because we weren't accounting for the patch number.

 

 

Was this article helpful?

/