Jarvis II (v.1.33) | Upgrade Instructions | Release Date: July 2023

Owned by Harshula Jhala
Last updated: Sept 18, 2023 by Wilmarié Moreland

This page covers:

Upgrading Amp Impact to Jarvis II - v1.33

Note:  
A Salesforce environment with Amp installed can be directly upgraded to the latest version of Amp as long as the current version is v1.17.1 or later. If the version of Amp is an earlier version, you must first upgrade to v1.17.1 before upgrading to v1.33 (Jarvis II). When upgrading to this version and skipping previous upgrades, please be sure to follow the Upgrade Instructions for every intermediate release as well to ensure the app continues working as expected.

  1. To upgrade to the latest release of Amp Impact, log into your Sandbox environment and use the installation link.

    1. Vera Employees can navigate to this page to access the link.

    2. Partners & customers, please get in touch with your Vera point of contact to access the link.

  2. Information will be displayed confirming that you have an earlier version installed and it can be upgraded while preserving existing data. 

  3. Select which users you wish to install the package for (learn more here). 

  4. Click "Upgrade".

  5. Refer to the release notes document and learn about the new features for this release. 

  6. Perform your current use cases in the sandbox and if you are using any of the new features from this release, ensure that they are operating as expected.

  7. When you are ready to deploy to Production, use this installation link.

  8. Update any changes you make, for example to custom settings, in Production as these will not "carry over" from your sandbox. 

Note: 
If My Domain has already been set up, replace “test” or “login” in the installation links with the specific domain appended by .my. for the org. See below for an example of a customized installation link: https://customdomain.my.salesforce.com/packaging/installPackage.apexp?p0=04t4o000002FIf5&isdtp=p1

If you upgrade Amp Impact, records of objects within that package will be updated. If custom validation rules have been created on those objects, the upgrade will fail if the records on those objects do not comply with those custom validation rules.

Packaging Changes

Certain changes to the configuration will be automatically updated on installation of the upgrade, while others will need to be manually updated (in order not to conflict with any org-specific customization). For full details on what Salesforce supports when upgrading managed packages, refer to the Editing Components and Attributes After Installation and Special Behavior of Components in Packages pages.