Mira (v1.37) | Release Notes | May 2024

Our release notes offer brief, high-level descriptions of new features, enhancements, and resolved issues. Detailed information on the features, their setup, and configuration are available in the Amp Impact Knowledge Base (specific links below).

This page covers:

New Features

Numerator/Denominator Data Type for Indicators

From the Mira release, we are introducing the ability to track the Numerator/Denominator data type for Indicators in Amp Impact!

Track Percentage Achievement as well as the Scale of Results

Numerator/Denominator Indicators allow users to track the percentage (or as a fraction of a custom-defined factor) result and the actual numerator and denominator values. These indicators directly highlight the relationship between two numbers (numerator and denominator). It emphasizes the raw counts involved, which can be useful in interpreting the scale and magnitude of results achieved.

Open

Open

Define a Custom Factor for Result Values

Amp Impact allows users to specify a custom factor for Numerator/Denominator results. This allows users to track results as relevant to their program and organization.

Submit and Lock Data Tables

This release of Amp Impact introduces a Submit Application wizard that simplifies the submission process for a Project (or Application). This wizard provides users with a streamlined experience to submit their data tables together.

Once data tables are submitted, they are locked to restrict editing. This feature allows organizations to easily implement relevant submission processes and ensure the data integrity of the system.

Users can now lock the following data tables in Amp Impact:

Feature Enhancements

Input total result for sex-disaggregated percentage Indicators on addResults LWC

Now users can manually input a total result for sex-disaggregated percentage Indicators. This enhancement allows users to capture percentage results at total and disaggregated levels.

Improved data load capacity on addResults LWC

The addResults Lightning Web Component (LWC) can now load up to 2X records of its previous capacity.
This enhanced capacity is achieved by fetching and loading data in chunks, resulting in faster performance for search and filters on setTargets LWC.

However, if organizations have a large data set, (more than 800 result records) the initial load time for the page would be higher.

Upload more data on setTargets LWC

Users can now load 4X more data on setTargets LWC using the download/ upload functionality. This allows users to upload targets for a large number of reporting periods at once.

Resolved Issues

SubmissionResponseForm: Users can now Submit a SubmissionResponseForm (or a Narrative Form) that contains 2 or more conditionally displayed questions in multiple sections

In previous versions of Amp Impact, there were a couple of specific instances when prevented submission of the SubmissionResponseForm. If there were 2 or more conditionally displayed questions added to multiple sections, the users couldn’t submit the SubmissionResponseForm. This has now been resolved.

ActivityChart AURA: Custom validation rules now display while creating or editing activities

ActivityChart AURA component didn’t support displaying the custom validation rules (created by system admins). With this release, defined validation messages are displayed to the user when a validation rule is violated when creating or editing an Activity.

ActivityChart AURA: Support for English (Netherlands) and French(Morroco) locales

From this release, ActivityChart AURA component loads properly for English (Netherlands) and French(Morroco) locales.

manageIndicators LWC: Users can now search by Indicator Definition even if the corresponding field is not added as a filter

In previous releases, the Indicator Definition should have been added as a filter if users wanted to search by the Indicator Definition. Now, the Indicators can be searched by Indicator Definition without adding it as a filter. This saves space in the filter section and provides a better user experience.

addResults LWC: Upload results on addResults LWC successfully if the downloaded results template has sex-disaggregated Project Indicators while the addResults LWC doesn’t (or vice-versa)

Users got an error when uploading a results template to addResults LWC when the downloaded results template had sex-disaggregated Project Indicators while the addResults LWC didn’t (or vice versa). This has now been resolved.

setTargets LWC: Upload targets on setTargets LWC successfully if the downloaded targets template has sex-disaggregated Project Indicators while the setTargets LWC doesn’t (or vice-versa)

Users got an error when uploading a targets template to setTargets LWC when the downloaded targets template had sex-disaggregated Project Indicators while the setTargets LWC didn’t (or vice versa). This has now been resolved.

activities LWC: Users only see fields they have access to when filtering Activities

With this release of Amp Impact, when users filter Activities on activities LWC, they only see the fields they have access to. This resolution further strengthens the data security in Amp Impact.

addResults LWC: Compare Baseline with Results for Indicators that have Target Frequency different than Reporting Frequency

In previous versions of Amp Impact, if an Indicator had a Target Frequency different than the Result Frequency, then the Baseline did not display when the user compared it with the Baseline on addResults LWC. This has now been fixed to enable users to compare Baseline to Results for Indicators that have Targets set at a different frequency than Results.

manageIndicators LWC: Buttons on manageIndicators LWC are hidden if the design attributes are set to hide them

The behavior of some Design Attributes on manageIndicators was unexpected. For example, if the Design Attribute Hide Add New Indicator button was set to TRUE, the button was disabled instead of being hidden on the manageIndicators LWC. This has been fixed such that buttons are now hidden if corresponding Design Attributes are set to hide them.

Behind the Scenes: Technical Stuff

To ensure Amp Impact’s compatibility with Salesforce’s NPC:

1. All apex classes and triggers have been upgraded to API version 60.0

2. All flows have been upgraded to API version 60.0

3. All LWC and Aura components have been upgraded to API version 60.0

4. Flexi pages have been upgraded to API version 60.0

5. Visualforce pages have been upgraded to API version 60.0

This enables users to refer to the following NPC objects when:

1. Creating an aggregated indicator

2. Creating a Submissions template (using CreateTemplateData component)

Release Updates

Packaging Changes

Updates to ampi__Budget__c

Updates to ampi__Implementation_Plan__c

Updates to ampi__xx_Framework__c

Updates to ampi__Indicator__c

Updates to ampi__Project_Indicator__c

Updates to ampi__Project__c

Updates to ampi__Reporting_Period__c

Updates to ampi__Result__c

Updates to Custom Meta Data Type ampi__Dependent_Field_Control_Settings__c

Declarative Automation

New Custom Labels

Permission Sets

Amp Impact Admin

Apex Class Access