...
| Table of Contents | ||
|---|---|---|
|
Upgrading Amp Impact to
...
Nashira - (v1.
...
38)
| Info |
|---|
Note: |
To upgrade to the latest release of Amp Impact, log into your Sandbox environment and use the installation link.
Vera Employees can navigate to /wiki/spaces/PS2/pages/3906633729 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 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 field | Yes | N/ADefault value of ampi__Targets_Are_Disaggregated__c has been changed. | |
New custom label | Yes | N/ANew custom label ST_HOVER_HELPTEXT has been created | |
Updated custom label | Yes | N/AValue of PREPARE_UPLOAD_3 has been changed | |
New fieldsetfield set | Yes | N/A | |
New fieldset ampi__COMMENT_POPUP_ADDRESULT has been createdNew Custom Meta Data Custom Metadata Type | Yes | N/ANew CMDT ampi__Dependent_Field_Control_Settings__c has been created | |
Updated Custom Metadata Type | No | Home → Custom MetaData | |
Updated Page Layout | No | Object → Page Layouts |
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 (Optional)
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:
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 “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:
Navigate to Object Manager
Navigate to the “Project Indicator” object (ampi__Project_Indicator__c) and click on it
Navigate to “Field Sets” and click on “Add Results Info Popover”
Remove the “Calculation Factor” field from the Field Set
Click “Save”
Remove the fields “Objective” and “Thematic Area” 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:
Navigate to Home →In Quickfind, type Custom Metadata Types and click on it
Click on Manage Records, next to Dependent Field Control Setting
Click on “Edit” next to NumDen Edit Indicator Popup
Click “Edit”
Remove the Objective (ampi__Objective__c) and Thematic Area (ampi__Thematic_Area_Text__c) from Dependent Fields.
6. Click Save
Ensure the fields “Validation Range Maximum Denominator”, “Validation Range Minimum Denominator“, “Validation Range Maximum Numerator” and “Validation Range Minimum Numerator” 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:
Navigate to Object Manager
Navigate to the “Project Indicator” object (ampi__Project_Indicator__c) and click on it
Navigate to “Field Sets” and click on “Edit Project Indicator Popup”
Ensure that the 4 fields are added in the field set
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:
Navigate to Home →In Quickfind, type Profiles and click on it
Click on the profile that does not need these custom permissions
Click on “Enabled Custom Permissions”
Click on Edit
Remove the Custom Permissions
6. Repeat the steps for all necessary Profiles.
Add the Custom Permissions to the necessary Permission Sets