Our upgrade instructions provide guidance on new features that require manual updates in order not to conflict with any org-specific customization. Detailed information on Set-up, Configuration and Feature Information can be found through links on the Libertas Release Notes.
Contact support@verasolutions.org to share feedback.
Upgrading Amp Impact to Libertas - (v1.36)
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.36 (Libertas). 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.
To upgrade to the latest release of Amp Impact, log into your Sandbox environment and use the installation link.
Vera Employees can navigate to /wiki/spaces/PS2/pages/3906633729 to access the link.
Partners & customers, please get in touch with your Vera point of contact to access the link.
Information will be displayed confirming that you have an earlier version installed and it can be upgraded while preserving existing data.
Select which users you wish to install the package for (learn more here).
Click "Upgrade".
Refer to the release notes document and learn about the new features and bug fixes for this release.
After reviewing the release notes, follow the steps outlined below.
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.
When you are ready to deploy to Production, use this installation link.
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 the 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.
Note: The table below details which types of configuration changes need to be made manually in this release, and if so, also include an example of where to change them. Additionally, the table also displays examples of some automatic changes that will occur when the package is upgraded. For full details of what has been added or modified, refer to the Packaging Changes section in the Release Notes.
Change | Automatic Update? | Manual Update Location | Example from Libertas Release |
|---|---|---|---|
Updated field | Yes | N/A | Default value of ampi__Targets_Are_Disaggregated__c has been changed. |
New custom label | Yes | N/A | New custom label ST_HOVER_HELPTEXT has been created |
Updated custom label | Yes | N/A | Value of PREPARE_UPLOAD_3 has been changed |
New fieldset | Yes | N/A | New fieldset ampi__COMMENT_POPUP_ADDRESULT has been created |
New Custom Meta Data Type | Yes | N/A | New CMDT ampi__Dependent_Field_Control_Settings__c has been created |
Update Profiles and Custom Permission Sets for New Objects and Fields
While permission sets in the package are automatically updated to provide access to these new fields, profiles and custom permission sets must be manually updated to include these new artifacts if the relevant user(s) requires access to them.
Refer to the Packaging Changes section in the release notesto determine which objects and fields need to be added to any custom profiles or permission sets.