Phoenix (v1.45) | Upgrade Instructions | June 2025
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 Release Notes.
Contact support@verasolutions.org to share feedback.
Please note that the previous release Orion was v1.41 and Phoenix is 1.45
All the versions in between were not released.
Upgrading Amp Impact to Phoenix - (v1.45)
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 Impact is an earlier version, you must first upgrade to v1.17.1 before upgrading to v1.45 (Phoenix). 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 this page 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 Phoenix (v1.45) Release |
|---|---|---|---|
New field | Yes | N/A | New field ampi__xx_Budget_Available__c has been added to ampi__Budget__c |
Updated field | Yes | N/A | Label of Disaggregation Group(s) Language 1 was changed from “Disaggregation Group Language 1“ to “Disaggregation Group(s) Language 1“. |
New custom label | Yes | N/A | New custom label BUDGET_PLANNING_PERIOD has been created |
Updated custom label | Yes | N/A | Short description of VIEW_UPLOAD_SUCCESShas been changed |
New fieldset | Yes | N/A | New fieldset ampi__REPORT_EXCEL_ATTRIBUTE_COLUMNS has been created |
Updated field set | Yes | N/A | The following fields were made available to the ADD_NEW_INDICATOR_POPUP field set:
Additionally the description of the ADD_NEW_INDICATOR_POPUP field was changed |
Updated Page Layout | No | Object → Page Layouts | Added the following fields to the page layout for ampi__Financial__c:
|
Updated Custom Metadata Type | Yes | N/A | New records were added such as:
|
|
|
|
|
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 notes to determine which objects and fields need to be added to any custom profiles or permission sets.
Upgrade Steps to use Multiple Disaggregations:
The following steps upgrade steps are relevant to organizations that aim to disaggregate their Project Indicators by multiple custom groups. Read more about the feature here.
Update Field Set for the Project Indicator Object (Optional)
Navigate to Object Manager
Navigate to the “Project Indicator”(ampi__Project_Indicator__c) object and click on it
Navigate to Field Sets
Click on “Edit Project Indicator Popup”(ampi__EDIT_PROJECT_INDICATOR_POPUP)
Rearrange the “Disaggregation Type” field from the bottom of the fieldset and place it below the “Disaggregation Group(s)” field
Click “Save”.
Update Field Set for the Indicator Object (Optional)
Navigate to Object Manager
Navigate to the “ Indicator”(ampi__Indicator__c) object and click on it
Navigate to Field Sets
Click on “Add New Project Indicator Popup”(ampi__ADD_NEW_INDICATOR_POPUP)
Rearrange the “Disaggregation Type” field from the bottom of the fieldset and place it below the “Disaggregation Group(s)” field
Click “Save”.
Add the “Disaggregation Type” field to the Page Layout of Indicator and Project Indicator Objects (Optional)
You can add the “Display On” field to the page layouts of the Project Indicator(ampi__Project_Indicator__c) and Indicator (ampi__Indicator__c) objects by following the steps mentioned below:
Navigate to Object Manager
Navigate to the “Project Indicator” object (ampi__Project_Indicator__c) and click on it
Navigate to “Page Layout” and click on “Project Indicator Layout”
Drag the “Disaggregation Type” field to the Project Indicator Detail section
Repeat the same for the Indicator (ampi__Indicator__c) object if needed
Add Help Text for the “Disaggregation Group(s)” field on the Indicator Object (Optional)
Navigate to Object Manager
Navigate to the “Indicator” object (ampi__Indicator__c) and click on it
Navigate to “Fields and Relationships”
Search for and click on the Disaggregation Group(s) (ampi__Disaggregation_Group__c) field
Click on “Edit”
Add the following Help Text: “Select between 0 to 6 disaggregation groups in this field. They will appear on the Set Targets and Add Results LWC in the order they have been added here either in a left to right manner or top to down manner for Nested and Stacked Indicators respectively. For Stacked Indicators the Disaggregation group added first would be the primary disaggregation group.”.
Optionally you can customise the help text to meet the needs of your organization.
Repeat the same for the Project Indicator (ampi__Project_Indicator__c) if needed
We recommend using this feature for Project Indicators in new Projects/Applications or for existing Project Indicators that do not have result records created.
Limiting Disaggregation Groups on Project Indicators (Optional)
If your organization wants to restrict the maximum number of Disaggregation Groups that can be assigned to a Project Indicator across all Projects in the system, follow the steps mentioned here.
Use Plan Budget and Report Financials Lightning Web Components
The following steps upgrade steps are relevant to organizations that aim to use the new Plan Budget and Report Expenditure Lightning Web Components to define and track their budgets. Read more about it here.
Note: If you plan to use the Enhanced budget Templates, the fields defined in BUDGET_ATTRIBUTE_COLUMNS must also be added to the ampi__PLAN_EXCEL_ATTRIBUTE_COLUMNS and ampi__REPORT_EXCEL_ATTRIBUTE_COLUMNS fieldsets, since the Enhanced budget Template relies on these two fieldsets.
Add Lightning Web Components to the Project Lightning Record Page
These steps assume that the packaged Project Lightning Record Page is being used. If a custom page has already been created, edit that Lightning Record Page directly.
Navigate to Lightning App Builder
Click on the “Financial” tab to open up the Tab component editor on the right-hand pane
Drag tabs
Rename the tabs. Out of the box the tabs are named “Plan Budget” and “Report Expenditures”
On the left-hand pane, scroll down to Custom-Managed Components.
Drag Plan Budget Lightning Web Component and drop it to the Plan Budget tab
Similarly Drag the Report Expenditures Lightning Web Component and drop it to the Report Expenditures tab
Add the “Budget Available” field to the Page Layout (Optional)
You can add the “Budget Available” field (ampi__xx_Budget_Available__c) to the page layout of the Budget (ampi__Budget__c) object by following the steps mentioned below:
Navigate to Object Manager
Navigate to the “Budget” object (ampi__Budget__c) and click on it
Navigate to “Page Layout” and click on “Budget Layout”
Drag the “Budget Available” field to the Budget Detail section
Before you can use the Plan Budget or Report Expenditure LWCs for a specific budget, the parent Budget record in Amp Impact must be created and ensure that is setup correctly. This is a critical step needed to use the functionality
Note: Attempting to access the Financials tab for a Budget record that is not set up will result in a "Something Went Wrong" error message.
If you are upgrading to this feature in a project/application with existing budget and financial line items, ensure that you do not make any edits to the line items that have already been planned or reported. Only do it for those whose values haven’t been entered previously
Use the Excel template to download/upload Framework Objectives
The following steps upgrade steps are relevant to organizations that aim to download and upload Framework Objectives on an Excel template and work on them offline.
Enable Feed Tracking to track content versions for the Downloaded Template/Error Logs or Success Logs (Optional)
If your organization tracks content versions for downloaded template or the error logs/success logs created during upload then follow these steps:
Navigate to Setup
Search "Feed Tracking" in Quick Find
Find “Framework” Object
Check “Enable Feed Tracking”
Click on “Save”