Nashira (v1.38) | Upgrade Instructions | October 2024

Upgrading Amp Impact to Nashira - (v1.38)

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. 

Use Enhancements to Numerator Denominator Indicators

Update the Page layout for the Project Indicator Object

Page layout changes made to the Project Indicator (ampi__Project_Indicator__c) object will not be reflected when you upgrade to Nashira. This is to ensure that any customizations made by users are not overridden. To meet the modifications made to the page, you may modify the Project page layout by adding relevant fields.

Add the “Number of Decimals for Resultant Value” field to the Page Layout

This step allows users to define the number of decimal places that are displayed for Numerator/Denominator resultant values. You can add the field Number of Decimals for Resultant Value (ampi__xx_Number_of_Decimals_for_Resultant__c) to the Project Indicator page layout 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

   Open

   

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

   Open

   

4. Drag the “Number of Decimals for Resultant Value” field to the Project Indicator Detail section

   5. Click “Save”

Remove the field “Calculation Factor” from the “Add Results Info Popover” field set

The UX enhancements introduced in the Nashira v(1.38) release display the Calculation Factor value inside the popup to enter result values for Numerator/Denominator indicators.

As a result, the Calculation Factor field (ampi__xx_Calculation_Factor__c) can be removed from the Add Results Info Popover field set (ampi__ADD_RESULTS_INFO_POPOVER) by performing the following steps:

1. Navigate to Object Manager

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

3. Navigate to “Field Sets” and click on “Add Results Info Popover”

4. Remove the “Calculation Factor” field from the Field Set

5. Click “Save”

Ensure that the fields controlling Validation Ranges are added to the “Edit Project Indicator Popup”

To use the Validation Ranges functionality for Numerator/Denominator type of Project Indicators ensure that the following fields are added to the Edit Project Indicator Popup (ampi__EDIT_PROJECT_INDICATOR_POPUP)

• Validation Range Maximum Denominator (ampi__xx_Validation_Range_Maximum_Denominator__c)

• Validation Range Minimum Denominator(ampi__xx_Validation_Range_Minimum_Denominator__c)

• Validation Range Maximum Numerator (ampi__xx_Validation_Range_Maximum_Numerator__c)

• Validation Range Minimum Numerator (ampi__xx_Validation_Range_Minimum_Numerator__c)
  
  To do so:

1. Navigate to Object Manager

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

3. Navigate to “Field Sets” and click on “Edit Project Indicator Popup”

    

4. Ensure that the 4 fields are added in the field set

Add the fields “Validation Range Maximum” and “Validation Range Minimum” to the NumDen Edit Indicator Popup Valid Range record in Dependent Field Control Setting Custom Metadata Type

In order to use Validation Ranges for Numerator/Denominator targets, the fields Validation Range Minimum (ampi__Validation_Range_Minimum__c) and Validation Range Maximum (ampi__Validation_Range_Maximum__c) should be displayed on the Customize Project Indicator Popup (ampi__EDIT_PROJECT_INDICATOR_POPUP). To do so perform the following steps:

1. Navigate to Home →In Quickfind, type Custom Metadata Types and click on it

2. Click on Manage Records, next to Dependent Field Control Setting

3. Click on “Edit” next to “NumDen Edit Indicator Popup Valid Range”

4. Click “Edit”

5. Add these semicolon seperated field API names “ampi__Validation_Range_Minimum__c; ampi__Validation_Range_Maximum__c“to the Dependent fields.

6. Click Save

In order to view the Validation Range Minimum (ampi__Validation_Range_Minimum__c) and Validation Range Maximum (ampi__Validation_Range_Maximum__c) fields on the “Add New Custom Indicator” Popup (ampi__ADD_NEW_INDICATOR_POPUP) , add them to the Dependent Fields on the “NumDen Add Indicator Popup Valid Range” Custom Metadata record.

Ensure the the fields “Objective” and “Thematic Area” are removed from the “NumDen Edit Indicator Popup" record in Dependent Field Control Settings Custom Metadata Type

In order for the Objective (ampi__Objective__c) and Thematic Area (ampi__Thematic_Area_Text__c) to be displayed on the Customize Project Indicator Popup follow the following steps:

1. Navigate to Home →In Quickfind, type Custom Metadata Types and click on it

2. Click on Manage Records, next to Dependent Field Control Setting

3. Click on “Edit” next to NumDen Edit Indicator Popup

    

4. Remove the Objective (ampi__Objective__c) and Thematic Area (ampi__Thematic_Area_Text__c) from Dependent Fields.

5. Click Save

Integration with a Third Party Tool to download Performance Graphs

With the Salesforce Release of Summer 2024, Performance Graphs will no longer be downloadable through Amp Impact out of the box. To continue accessing this functionality, users will need to integrate with a third-party tool such as Highcharts (https://export.highcharts.com).

Please note that while Highcharts was bundled with Amp Impact in previous versions, starting with the Nashira (v1.38) release, it has been removed from the package. Users are now required to configure access to Highcharts or a comparable tool separately to enable the download functionality for Performance Graphs.

Disable Custom Permissions

The custom permissions packaged in Nashira (v1.38) are assigned to a profile when packaged. These custom permissions need to be manually removed from Profile and assigned to the permission sets that require it. Skipping this step will result in users not being able to lock components after they have been submitted. To remove the Custom Permissions from Profile:

1. Navigate to Home →In Quickfind, type Profiles and click on it

2. Click on the profile that does not need these custom permissions

3. Click on “Enabled Custom Permissions”

4. Click on Edit

5. Remove the Custom Permissions

6. Repeat the steps for all necessary Profiles.

7. Add the Custom Permissions to the necessary Permission Sets