Orion (v1.41) | Upgrade Instructions | January 2025

Upgrading Amp Impact to Orion - (v1.41)

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. 

Additionally, we have implemented additional security checks for Read access on Field-Level Security (FLS) and Create, Read, Update, Delete (CRUD) permissions, building upon Salesforce's out-of-the-box (OOTB) security framework. These enhancements ensure that unauthorized users cannot gain read access to fields on Amp Impact objects by requiring them to have explicit field level access defined in the security matrix.

In previous releases field read permission could be inherited from object level permission.

When upgrading We advise you to:

1. Thoroughly test all existing and new Amp Impact functionalities that will be used by the organization

2. Pay special attention to error messages and ensure that any missing FLS is added as needed. Users will need appropriate access to all fields (including custom fields) used in Amp Impact components, such as pop-ups, tables, and other elements.

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. 

Use Indicators on Set Targets and Add Results Lightning Web Components

This is a mandatory Upgrade Step.

As part of the Orion (v1.41) Release, we introduced a “Display On” field (ampi__xx_Display_On__c) on Project Indicator (ampi__Project_Indicator__c) and Indicator objects (ampi__Indicator__c) that allows users to control the visibility of Project Indicators on Set Targets and Add Results Lightning Web Components.  By default, the value of this picklist field is set to Both for newly created Catalog Indicators and Project Indicators. However, in upgraded orgs, Salesforce does not default the “Display On” field to 'Both' for existing Project Indicators.

As a result, Project Indicators are not visible on the Set Targets and Add Results Lightning Web Components. To resolve this, users need to manually update the “Display On” field using a Data Loader.

1. Export the Data:

   • Use a Data Loader to export all existing Project Indicator data.

   • Include only fields from the Project Indicator object itself, such as:

     •  Indicator Definition (ampi__Description__c)

     •  Display On (ampi__xx_Display_On__c)

2. Update the CSV:

   • Enter the “Display On” field value as either Set Targets, Add Results, Both, or None, as required. If you want to see your existing Project Indicators on the Set Targets and Add Results Lightning Web Components set the value to “Both”.

3. Import the Data:

   • Before importing, double-check the mapping of fields in the Data Loader.

   • Complete the import to update the existing Project Indicators.

Use the Display On (ampi__xx_Display_On__c) field (Optional)

The following steps upgrade steps are relevant to organizations that aim to use the Display On (ampi__xx_Display_On__c) field being introduced in the Orion Release.

It allows users to control the visibility of Project Indicators on Set Targets and Add Results Lightning Web Components.  

Update Field Set for the Project Indicator Object (Optional) 

1. Navigate to Object Manager

2. Navigate to the “Project Indicator”(ampi__Project_Indicator__c) object and click on it

3. Navigate to Field Sets

4. Click on “Edit Project Indicator Popup”

5. Drag “Display On ” field and add it to the field set. 

6. Click “Save”. 

Update Field Set for the Indicator Object (Optional) 

1. Navigate to Object Manager

2. Navigate to the “Indicator” (ampi__Indicator__c) object and click on it

3. Navigate to Field Sets

4. Click on “Add New Indicator Popup”

5. Drag “Display On” field and add it to the field set. 

6. Click “Save”. 

Add the “Display On” field to the Page Layout (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:

1. Navigate to Object Manager

2. Navigate to the “Project Indicator” object (ampi__Project_Indicator__c) and click on it

3. Navigate to “Page Layout” and click on “Project Indicator Layout”

4. Drag the “Display On” field to the Project Indicator Detail section

5. Repeat the same for the Indicator (ampi__Indicator__c) object if needed