Contents:

• Overview
• Definitions
• FAQs

 

Overview

As a Saas software, LeanData’s functionality depends on version upgrades which contain the most recent product updates, new features and bug fixes. New versions are released approximately two times per quarter.

 

Definitions

Automatic Upgrade Customers  

• The majority of LeanData customers receive automatic upgrades, which are pushed through Salesforce. Automatic upgrade customers will not need to take any action in order to receive the latest version of LeanData.

Do-Not-Upgrade Customers

• Some customers choose to opt-out of automatic upgrades and instead prefer to work with their Customer Success representative when an upgrade is needed.

 

FAQs

Why should I upgrade my version of LeanData?

• Upgrading your LeanData package ensures you are on the most up to date version of the app which contains upgraded functionality, new features, bug fixes and performance improvements. These upgrades also ensure that your version of LeanData works with the current version of Salesforce. 

What happens if I don’t upgrade my version of LeanData?

• You will not have access to the latest LeanData features, improvements and bug fixes. If your org is on a very old package, it’s also possible that LeanData may not have the ability to help support and troubleshoot for you, without first upgrading to a more recent version. Finally, for very old versions, the upgrade process may be more difficult because you may need to be upgraded first to an intermediate version before upgrading to the latest version.

How do I know what features/updates will be included in the upgrade? Who can I reach out to for more information?

• Check your inbox for the LeanData newsletter which typically contains insight into new major releases or check out the Release Notes in our Help Center.

Will there be any service interruption due to the upgrade?

• There will not be a service interruption due to the upgrade. LeanData will continue to function normally during the upgrade process.

What is required from me for the upgrade?

• Standard Security: Nothing! LeanData can complete the upgrade process without any action from you. Since we are 100% native in SFDC, we simply push a package upgrade directly to your instance via API.
• Non-Standard Security: Depending on how old your version of LeanData is, you may have to load a .bin file which contains updated settings. If you fall in this bucket, your Implementation Consultant and Customer Success Manager will provide the file for you and we can walk you through how to upload the file in your LeanData Dashboard.

What happens during the upgrade process from a technical standpoint?

• Salesforce processes all of the changes to components from the existing version to the new version of the managed app. If there is a LeanData Batch in progress when the upgrade occurs, the Batch is cancelled and will restart once the upgrade is complete. It will resume where it left off, all records will be processed correctly. The "downtime" of the batch is five minutes or less.

When will the upgrade be performed? 

• If you are an auto-upgrade customer, the upgrade will be performed according to LeanData’s upgrade schedule, approximately twice quarterly. If you are on the Do Not Upgrade list, your Customer Success or Support rep will work with you on the upgrade steps and timing.

What if there is an issue after the upgrade?

• While this is rare, this would be treated as any other support inquiry. You would need to reach out to LeanData Support, describing the issue so that our team can troubleshoot.

Do I need an SFDC Admin/Dev Resource from my end as part of the upgrade process?

• Nope! If you are on a non-standard configuration, anyone with the appropriate LeanData permission set can upload the .bin file. Otherwise, no additional resource would be required. 

How long does the upgrade process take?

• The upgrade process typically takes no longer than 15 minutes. Sometimes errors on the Salesforce side are encountered, and subsequent retries may be necessary. This should not significantly impact the upgrade timeframe.

Does the upgrade go directly to my Production instance?

• That depends on your preferences! Typically an upgrade directly to Production is incredibly low risk and non-disruptive. However, if you have a process where a sandbox or UAT environment must be upgraded first, we can definitely work with that. Most customers upgrade directly to Production. 

My org has a non-standard configuration, does that change the process for my org?

• This does not change the process from the LeanData side - since LeanData is a native app in Salesforce, we can still push over upgrades to the LeanData app without API access. If your organization has specific security requirements for upgrades, please let your LeanData representative know what those requirements are so that we can proceed accordingly.

My org has a non-standard configuration, is a .bin file required as part of the upgrade?

• It depends on how old your LeanData version is. Your LeanData rep should be able to tell you if a .bin file is required as part of the upgrade.

My org is on LeanData’s “No Auto Upgrades” list. What are the benefits of removing my org from that list?

• Currently, customers on the Do Not Upgrade list are upgraded only by explicit customer request or permission, as the need comes up. This usually stems from needing a new fix or a specific feature LeanData may have introduced since the last time you were upgraded.
• Taking your org off the Do Not Upgrade list will help prevent many problems before they occur and also ensure that you can leverage LeanData’s latest capabilities.