Kalausi (v1.34) | Upgrade Instructions | September 2023
- Harshula Jhala
- Wilmarié Moreland
Our upgrade instructions provide guidance on new features that require manual updates in order not to conflict with any org-specific customization. Detailed information on Set-up, Configuration and Feature Information can be found through links on the Kalausi Release Notes.
Contact support@verasolutions.org to share feedback.
- 1 Upgrading Amp Impact to Kalausi - (v1.34)
- 2 Packaging Changes
- 3 Update Profiles and Custom Permission Sets for New Objects and Fields
- 4 Activate Triggers using Dynamic Loader
- 5 Deactivate Process Builders and Workflow Rules
- 6 Use the excel template for downloading and uploading targets
- 7 Use Calculated Indicators
Upgrading Amp Impact to Kalausi - (v1.34)
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.34 (Kalausi). 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.
To upgrade to the latest release of Amp Impact, log into your Sandbox environment and use the installation link.
Vera Employees can navigate to this page 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 My Domain has already been set up, replace “test” or “login” in the installation links with the specific domain appended by .my. for the org. See below for an example of a customized installation link: https://customdomain.my.salesforce.com/packaging/installPackage.apexp?p0=04t4o000002FIf5&isdtp=p1
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 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.
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 Kalausi Release |
|---|---|---|---|
New field | Yes | N/A | New LongTextArea field ampi__Chain_Batches__c has been added to object ampi_Batch_Update__e |
Updated field | Yes | N/A | Description of ampi__Disaggregation_Group__c has been changed. |
New custom label | Yes | N/A | New custom label CONFIRM_BASELINE_GA_FOR_UPLOAD has been created |
Updated custom label | Yes | N/A | Short Description of CALCULATION_FORMULA_INVALID has been changed |
New flow | Yes | N/A | New flow Update_Result_and_Target_Values has been created which updates the following fields with the current Date/Time when Result record Result/ Target values are created or updated: ampi__Result_Created_Date__c , ampi__Result_Last_Modified_Date__c, ampi__Target_Created_Date__c, ampi__Target_Last_Modified_Date__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 (New field ampi__Chain_Batches__c on object ampi_Batch_Update__e ), 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.
Activate Triggers using Dynamic Loader
If you’re upgrading from any of the following versions - (v1.27, v1.28, v1.29, v1.31, v1.32 or v1.33) the following triggers are marked deactivated on default. Ensure to mark these triggers as active in case they are in use.
ProjIndicatorGeoArea Error Service
ProjIndiReportingPeriod Error Service
ReportingPeriodError Service
ProjectGeographicArea Error Service
ThematicArea Error Service
DisaggregatedProjIndi Error Service
DisaggregationValue Service
DisaggregationGroup Error Service
All these triggers prevent orphaned records in the org - i.e they ensure that users get an error message while delete the Parent records if there is a related child record in the org. This error message will address users to delete the child records first.
To do so:
Navigate to Setup → Home
Search for “Custom Settings” and click on it
Click on Manage next to “Dynamic Loader”
Click on “Edit” next to the trigger you wish to activate and then mark it as active by clicking on the “Active” checkbox
Click on “Save”
If you’re upgrading from a version before v.1.27 then these triggers are marked activated on default. Ensure to mark them deactivated in case they are not in use.
Deactivate Process Builders and Workflow Rules
Why do this?
To leverage the latest advancements in Salesforce technology for automation and access more customization options, use the Flows which replaces these process builders.
Deactivate the following Process Builders that have been replaced by the corresponding Flow(s):
Process Builder to Deactivate | Corresponding Flow(s) |
|---|---|
Framework_Objective_Before_Insert
| |
Some of the packaged flows have a before save context while their corresponding processes were after save. Please click on the individual links in the table above to know more.
Click here to know more about how to deactivate a process builder.
Deactivate the following Workflow Rules that have been replaced by the corresponding Flow(s):
Workflow Rule to Deactivate | Corresponding Flow |
|---|---|
Update_Result_and_Target_Values
| |
Result values are edited | |
Target values are created | |
Target values are edited |
Click here to know more about how to deactivate a workflow rule
Use the excel template for downloading and uploading targets
In order to view the content version of the downloaded Targets template:
Add Files to the Related List for the Project Geographic Area object
Navigate to Setup → Object Manager
Search for “Project Geographic Area” and click on the object
Navigate to “Page Layouts” and click on “Project Geographic Area Layout”
Click on “Related Lists”
Drag and drop “Files” under “Related Lists”
Click “Save”
Enable Feed Tracking for Project Geographic Area object
Navigate to Setup → Home
In Quick Find, search for Feed Tracking
Navigate to “Project Geographic Area”
Click on “Enable Feed Tracking”
This step is needed only if the organization uses the content version records for the downloaded Targets template.
Use Calculated Indicators
Make sure “Lightning Web Security for Lightning web components and Aura Components’ is enabled in ‘Session settings”. To do so:
Navigate to Setup → Home
Type “Session Settings”
Check the “Use Lightning Web Security for Lightning web components and Aura components” checkbox.
