Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
stylenone

Upgrading Amp Impact to

...

Nashira - (v1.

...

38)

Info

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 38 (LibertasNashira). 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.

  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 /wiki/spaces/PS2/pages/3906633729 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. 

...

Note

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.

Info

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 Nashira(v1.38) Release

Updated New field

Yes

N/A

Default value of New Picklist field ampi__xx_Number_of_Decimals_for_Resultant__c has been added to ampi__TargetsIndicator_Are_Disaggregated__c has been changed._c

Updated Validation Rule

Yes

N/A

Is_Budget_Locked has been updated

New custom label

Yes

N/A

New custom label STCF_HOVERFOR_HELPTEXT BASELINE has been created

Updated custom label

Yes

N/A

Value of PREPARE_EXCEL_FOR_UPLOAD_3 1A has been changed

New fieldsetfield set

Yes

N/A

New fieldset ampiINDICATOR_FIELDS ADD_COMMENT_POPUP_ADDRESULT has been createdNew Custom Meta Data RESULTS EXCEL_TEMPLATE has been created

Updated field set

Yes

N/A

The following newly added fields were made available to the fielset:

  • ampi__xx_Denominator_Definition_Language_1__c

  • ampi__xx_Denominator_Definition_Language_2__c

  • ampi__xx_Denominator_Definition_Language_3__c

  • ampi__xx_Denominator_Definition_Translated__c

  • ampi__xx_Number_of_Decimals_for_Resultant__c

  • ampi__xx_Numerator_Definition_Language_1__c

  • ampi__xx_Numerator_Definition_Language_2__c

  • ampi__xx_Numerator_Definition_Language_3__c

  • ampi__xx_Numerator_Definition_Translated__c

New Custom Metadata Type

Yes

N/A

New CMDT ampi__Dependent_Field_Control_Settings__c has been createdxx_Lookup_Filter_Label_Mapping__mdt has been created

Updated Flow

Yes

N/A

Submit_Lock_Wizard flow has been updated

New Custom Permission

Yes

N/A

Override_Locked_Baseline has been created

Updated Custom Metadata Type

No

Home → Custom MetaData

ampi__Objective__c and ampi__Thematic_Area_Text__c removed from Dependent Fields on NumDen Edit Indicator Popup CMDT record

Updated Page Layout

No

Object → Page Layouts

Added the following fields to the page layout for ampi__Project_Indicator__c:

  • ampi__xx_Number_of_Decimals_for_Resultant__c

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 thePackaging Changes section in the release notesto 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

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

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

    Image Added

    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

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

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

    Image Added
  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”

    Image Added

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

    Image Added

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

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

    Image Added

  1. Click “Edit”

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

  3. Click Save

    Image Added

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

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

    Image Added

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

    Image Added
  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”

    Image Added
  4. Click on Edit

  5. Remove the Custom Permissions

    Image Added

6. Repeat the steps for all necessary Profiles.

  1. Add the Custom Permissions to the necessary Permission Sets