Versions Compared

Key

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

...

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.41 (Orion). 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. 

...

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 Orion (v1.41) Release

New field

Yes

N/A

New Picklist field ampi__xx_Display_On__c has been added to ampi__Indicator__c

New custom label

Yes

N/A

New custom label AGGREGATED_TYPE has been created

Updated custom label

Yes

N/A

Value of DELETE_FRAMEWORK_ITEM_MODAL_HEADER has been changed

Updated field set

Yes

N/A

The following fields were made available to the ADD_NEW_INDICATOR_POPUP field set:

  • ampi__xx_Display_On__c

Updated Page Layout

No

Object → Page Layouts

Added the following fields to the page layout for ampi__Project_Indicator__c:

  • ampi__xx_Display_On__c

...

  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 thePackaging Changes section in the release notes and give access to determine which all 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

...

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

Upgrade 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 ResultsBoth, 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.

Info

Additional Notes:

  • These steps must be performed on the Project Indicator object.

  • While not necessary, organizations can choose to perform these steps on the Indicator (ampi__Indicator__c) object as well.

Upgrade using List Views and Inline Editing 

  1. Ensure the “Display on” field is added to Indicator or Project Indicator Object Page Layouts.

  2. On the Page Layout; create a List View using the List View Controls menu.

  3. Add "Display On" from Select Fields to Display to the List View.

  4. Use Inline Editing and mass update the records to Both/None/SetTargets/AddResults.

Use the Display On (ampi__xx_Display_On__c) field (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 “Customize “Edit Project Indicator Popup”

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

  6. Click “Save”. 

...

  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

...

Troubleshooting Support for Permission Related issues

Due to the security checks mentioned in this section, users might face errors such as “Object not readable by the user” or “Field not readable by the user”.

...

We recommend going through all out of the box Permission Sets mentioned in the Packaging Changes section in the release notes and give access to all objects and fields to any custom profiles or permission sets. 

Additionally for Object related errors, system administrators can also override the values of the following custom label in English to append {0} at the end.

  • CORE_ERR_SEC_OBJECT_NOT_DELETABLE

  • CORE_ERR_SEC_OBJECT_NOT_INSERTABLE

  • CORE_ERR_SEC_OBJECT_NOT_READABLE

  • CORE_ERR_SEC_OBJECT_NOT_UPDATEABLE

This will ensure that the error message displays the objects for which access is required. Then provide access to those objects.

For field related errors, system administrators can override the values of the following custom labels in English to append {0} {1} at the end.

  • CORE_ERR_SEC_FIELD_NOT_INSERTABLE -> Field not readable by the user.  {0} {1}

  • CORE_ERR_SEC_FIELD_NOT_READABLE -> Field not readable by the user. {0} {1}

  • CORE_ERR_SEC_FIELD_NOT_UPDATEABLE -> Field not updateable by the user. {0} {1}

This will ensure that the error message displays the object followed by field for which access is required. Then provide access to those fields.