Raven (v1.48) | Upgrade Instructions | May 2026

Upgrading Amp Impact to Raven - (v1.48)

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 and bug fixes for this release.

6. After reviewing the release notes, follow the steps outlined below.

7. 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.

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

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

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.

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 backfill Locked Budget Planning and Reporting Periods

After upgrading to Raven (v1.48), the Locked Budget Planning Period(s) and Locked Budget Reporting Period(s) fields on the Budget object will be empty, even if Reporting Periods were previously submitted. If left empty, submitting a new Reporting Period will unintentionally unlock previously submitted periods. Follow the steps below to backfill these fields.

1. In Salesforce, navigate to Reports and create a new report using the Reporting Periods report type

2. Add the following columns:

   • Reporting Period ID

   • Project Reporting Period Name

   • Project

   • Budget Locked

3. Add a filter: Budget Locked = TRUE

4. Run the report — this will show all Reporting Periods that were previously submitted and locked

5. For each Project in the report results, navigate to the Project record and open the relevant Budget record

6. Open the Budgeting Cycle component on the Budget record

7. In the Locked Budget Planning Period(s) field, select the Reporting Periods that were previously submitted from the Plan Budget LWC

8. In the Locked Budget Reporting Period(s) field, select the Reporting Periods that were previously submitted from the Report Expenditure LWC

9. Save the changes

10. Repeat steps 5–9 for each Budget on the Project

    Open

    

Upgrade steps to remove the Budget Locked field from Reporting Period page layout (Optional)

The following upgrade step is relevant to organisations that have the Budget Locked field displayed on their Reporting Period page layout. With the Raven release, the locking functionality has moved to the new Locked Budget Planning Period(s) and Locked Budget Reporting Period(s) fields on the Budget object. The Budget Locked field on the Reporting Period object no longer serves a purpose in the locking flow.

If you have not built any custom automation, flows, or validation rules on top of this field, you can safely remove it from your page layout:

1. Navigate to Setup → Object Manager

2. Navigate to the Reporting Period (ampi__Reporting_Period__c) object and click on it

3. Navigate to Page Layouts and click on Reporting Period Layout

4. Remove the Budget Locked (ampi__xx_Budget_Locked__c) field from the layout

5. Click Save

Open

Upgrade Steps for Deprecated Visualforce Pages

As part of the Raven (v1.48) release, the following Visualforce pages have been deprecated and all internal package references to them have been removed:

• SetTargets.page

• AddResults.page

• ManageIndicators.page

• ManageLogFrames.page

The corresponding Lightning Web Component equivalents continue to work as expected and are unaffected by these changes.

Action required for upgrade orgs:

The following buttons on the Project__c object are no longer linked to the Visualforce pages but will still appear on your Project page layout if your org has previously customized it. You must remove them manually:

• Add Results

• Manage Framework

• Manage Indicators

• Set Target

You can safely remove it from your page layout by following the steps mentioned below:

1. Navigate to Setup → Object Manager

2. Navigate to the Project object and click on it

3. Navigate to Page Layouts and click on Project Layout

4. Remove these buttons from your page layout.

Open