New Features

Set Targets Rebuilt as a Lightning Web Component

To continue our trend of improving the performance of Amp Impact, the Set Targets page has been rebuilt as a Lightning Web Component. This change will include quicker load and processing times, as well as a cleaner and more consistent user interface. Alongside these performance improvements, the interface has also been updated to enable the following:

Set Targets Across Reporting Periods

In the Visualforce page version of Set Targets, users could only enter targets for one geographic area and reporting period combination (e.g. Eastern Europe and 2022) at a time. Recognizing that many organizations define their targets across all reporting periods at once, the component now displays reporting periods as columns, instead of the previous dropdown menu.

Before:

Open

After:

This enables users to enter targets for all of their indicators at once, as well as to better plan out the intended progress of their project over time. If the indicator has any level of disaggregation, the user can enter disaggregated targets in a pop-up.

Open

This enables users to enter targets for all of their indicators at once, as well as to better plan out the intended progress of their project over time. If the indicator has any level of disaggregation, the user can enter disaggregated targets in a pop-up.

Enter Baseline Data for Indicators

This release introduces the ability to enter baseline data for indicators on the Set Targets page, enabling users to more easily plan their targets for an indicator based on the baseline information.

Preview Qualitative Targets

In earlier versions of Amp Impact, users had to click into the edit popup for a qualitative indicator in order to see the data that had been entered. This has been improved so that when a user hovers their cursor over the icon for editing or viewing the qualitative targets, they will see a popover with a preview (first 255 characters) of the qualitative target value.

Preview Comments

To better support users in understanding what data has already been entered when the user hovers their cursor over the comment icon, they will see a popover with a preview of the comment.

Deactivate Reporting Periods for Target Entry

With the new interface of displaying all reporting periods across the Set Targets table, this release also introduces the ability to deactivate reporting periods for target entry, in order to ensure the table only displays relevant/active reporting periods. When the Active checkbox is set to TRUE, the reporting period will display as a table in the column.

Add Results Rebuilt as a Lightning Web Component

To continue our trend of improving the performance of Amp Impact, the Add Results page has been rebuilt as a Lightning Web Component. This change will include quicker load and processing times, as well as a cleaner and more consistent user interface. Alongside these performance improvements, the interface has also been updated to enable the following:

Compare Baseline Data to Results

This release introduces the ability to view baseline data for indicators on the Add Results page, enabling users to compare their actuals to their starting point for the indicator and better understand their progress. On Add Results, users will be able to make the selection to compare their results with either targets or baseline, and see the selected comparison in the table.

Preview Qualitative Results

In earlier versions of Amp Impact, users had to click into the edit popup for a qualitative indicator in order to see the data that had been entered. This has been improved so that when a user hovers their cursor over the icon for editing or viewing the qualitative results, they will see a popover with a preview (first 255 characters) of the qualitative result value.

Reporting Period Locked Status Displays in Dropdown

When a Reporting Period is submitted and/or locked in the Add Results Visualforce page, there is no differentiation between that Reporting Period and unlocked Reporting Periods, so a user has to toggle between all Reporting Periods in the dropdown picklist to know the status of each Reporting Period. In the new Add Results Lightning Web Component, the label “Locked” will appear in parentheses in the dropdown picklist for any Reporting Period that has been submitted and/or locked.

Preview Comments

To better support users in understanding what data has already been entered, the comment icon now displays differently based on whether there is an existing comment that has been entered. In addition, when the user hovers their cursor over the comment icon, they will see a popover with a preview of the comment.

Deactivate Reporting Periods for Result Entry

This release also introduces the ability to mark reporting periods as inactive in their result reporting, in order to ensure the table only displays relevant / active reporting periods. When the Active checkbox is set to TRUE, the reporting period will display in the dropdown picklist on the Add Results page.

Download / Upload Results Table

The Excel download template on Add Results has been modified to account for the new features, including:

1. Comparing Baseline data against Results

2. Entering Results for Picklist Indicators

3. Marking Results as Not Applicable

New Indicator and Result Types

With this release, users can now set targets and add results for new indicators and result types, including Picklist Indicators and Read-Only Results. Users will also be able to mark Results as not-applicable.

Picklist Indicators

Users can now create Picklist Indicators, with which they can define a set of target/result values that will then display as a dropdown picklist on both the Set Targets and Add Results Lightning Web Components. These Picklist Indicators can be used for various scenarios, such as Likert scales, Red-Amber-Green statuses, or Low-Medium-High ratings.

Read-Only Results

For Project Indicators with data that is not entered manually and also is neither aggregated nor calculated, the new value “Read-Only” has been added to the Type of Results picklist on Project Indicator. When “Read-Only” is selected, the Project Indicator’s Results will display as output values in the Add Results Lightning Web Component, and the data will not be editable by the user. This will prevent Results that are coming from external sources or integrations from being updated in error.

Not Applicable Results

Occasionally, Results cannot be reported due to irrelevance or extenuating circumstances. In these cases, Results can now be marked as “Not Applicable” in the comment popup. This will update a field on the Result record so that not-applicable results can be filtered out of any reports or dashboards.

Feature Enhancements

Improved Usability for IATI Reporting

To improve the IATI XML Generator user experience, the following updates will be made:

1. Sample help text to provide guidance to users on which fields will be printed into the IATI XMLs (see IATI Setup Guide)

2. Clear documentation of the mapping between the Amp data model and the IATI standard (see IATI User Guide)

3. Error handling for when the generated XML fails to pass the IATI Validator

4. Simplified data entry for tracking organization roles in projects and their related transactions

Details of each of these changes are logged in the IATI Setup Guide and the IATI User Guide. Please also review the Resolved Issues section of these release notes to see the bugs that have been fixed in this release.

Automation: Optimization of Reporting Period scheduler flow

The earlier Fornax release introduced the ability to schedule reporting periods based on the duration of a project and its reporting frequency/ies. In this release, the flow that schedules reporting periods has been updated with the following improvements:

• Create baseline reporting periods

• Prevent the creation of duplicate records

• Allow the user to input values into the flow to define the reporting period schedule (i.e. not rely entirely on project field values)

• Match the labels of reporting periods to the time period (e.g. changing a reporting period’s label from “M6” to June 2022).

Added Custom Setting to toggle structure of Geographic Areas in dropdown on Set Targets & Add Results Visualforce Page

Users can now toggle the structure of Geographic Areas between hierarchy and non-hierarchy in the dropdown on the Set Targets & Add Results Visualforce pages via Custom Settings. Using this is recommended if you have created more than 50,000 catalog-level geographic areas, which will cause the Visualforce page(s) to fail to load due to Salesforce governor limits. 

Resolved Issues

Activities Lightning Web Component: Custom fields for Milestone Activities not displaying in popover

Previously, if the System Administrator added custom fields to the MILESTONE_INFO_POPOVER field set, those custom fields would not be shown in the popover that displays when the user hovers their cursor over the Activity row. This has been updated so that any field (whether custom, standard Salesforce, or standard Amp Impact) added to the field set displays correctly in the popover.

Add Results Visualforce: Sex-disaggregated Results not saving if Targets are not disaggregated

If a Project Indicator was created such that its Results were only cross-disaggregated by sex, but its Targets were tracked in aggregate (i.e. without sex-disaggregation), then the Result values entered on the Add Results Visualforce page were not saving into the Result records. This has been resolved so that, irrespective of the level of disaggregation of the Targets, the Result values entered on the Add Results Visualforce page save correctly.

Manage Frameworks Visualforce: Project indicators not hyperlinked when associated with framework objectives

On the Manage Frameworks Visualforce page, Project Indicators would display next to their related Framework Objectives. However, even though the Project Indicators would display in blue text and as clickable, the click action would not open the Project Indicator record in a new tab. In this release, this has been resolved so that the Project Indicators’ appearance of being hyperlinked on the Manage Frameworks Visualforce page matches the user’s ability to click on the Project Indicator description and open the record.

IATI XML Generation: Transaction Type 11 is not printing into the IATI Activity XML

Although the initial release of IATI XML Generation was supposed to support Incoming Commitments (transaction type 11), the data set up in Allocation records (which map to Incoming Commitments) would not print into the IATI Activity XML. This has been fixed so that if the Allocation record is set up correctly (see the IATI User Guide), then it will successfully print into the IATI Activity XML.

IATI XML Generation: Empty elements and attributes are printed into the IATI Organisation and Activity XMLs when the related fields are left blank in Amp

Previously, when certain fields in Amp objects were left blank, the corresponding IATI element or attribute would still print into the IATI Organisation and Activity XMLs with a null value. This would result in the XML(s) failing the IATI validator due to blank values for elements and attributes being considered invalid. This was especially problematic for elements and attributes recognized as optional by IATI, as there was no way to omit those optional elements.

This has been fixed so that if a particular field is left blank, the relevant element and/or attribute simply does not print into the XML and avoids any validation errors. This approach has been applied to a number elements and their attributes in IATI, including the following:

IATI XML Generation: Optional fields on Budget are required to be populated in order for Activity XML to successfully generate

Previously, the IATI Activity XML would only successfully generate if the following fields on Budget were populated:

However, according to both IATI and Amp, the ampi__IATI_Budget_Status__c field is optional and should not be required for successful XML generation. This has been resolved so that only the fields required by IATI for validation need to be populated for the IATI Activity XML to generate successfully.

IATI XML Generation: Vocabulary attribute in iati-activity, transaction, and sector elements not printing correctly

In the iati-activity, transaction, and sector elements, the @vocabulary attribute would print the vocabulary label instead of the vocabulary code in the IATI Activity XML. This would cause errors with the IATI Validator, which would see a violation of their sector vocabulary code list. This has been resolved so that the vocabulary code value, according to the IATI Standard, is printed into the XML instead of the vocabulary label.

Before:

After:

Submissions: Questions that are scored but not part of a section do not show up in the scoring component

For Submissions that used Sections, if they contained any Question that was not assigned to a Section but still needed scoring, then that Question would not display in the Submission Scoring Aura Component. This has been fixed so that a Question need not be assigned to a Section in order to display in the Submission Scoring Aura Component.

Release Updates

As of the November 2023 release, the following Visualforce pages and Aura components will no longer be serviced by Vera Solutions:

This means that Vera Solutions will no longer enhance or resolve any issues for these components after November 2023.

Why: We are focusing development efforts on optimizing the new Lightning Web Components as well as introducing new features.

How: Before the November 2023 release, you must migrate to the related Lightning Web Components to ensure you continue receiving regular updates and enhancements to those features.

Packaging Changes

Updates to Account

New Fields

Updated Fields

Updates to ampi__Indicator__c

New Fields

Updated Fields

Updated Field Sets

Updated Page Layout

The following fields were added to the Indicator Layout:

1. ampi__xx_Has_Baseline__c

2. ampi__xx_Reporting_Picklist_Values__c

3. ampi__xx_Map_Picklist_Values_To_Number__c

4. ampi__xx_Numbers_Mapped_To_Picklist_Values__c

Updates to ampi__Project_Indicator__c

New Fields

Updated Field

Updated Field Sets

Updated Page Layout

The following fields were added to the Project Indicator Layout:

1. ampi__xx_Has_Baseline__c

2. ampi__xx_Reporting_Picklist_Values__c

3. ampi__xx_Map_Picklist_Values_To_Number__c

4. ampi__xx_Numbers_Mapped_To_Picklist_Values__c

Updates to ampi__Project_Geographic_Area__c

Updated Page Layout

The following field was added to the Project Geographic Area Layout:

1. ampi__Active__c

Updates to ampi__Reporting_Period__c

New Record Types

New Page Layout

The new page layout Baseline Layout was created for the Baseline Record Type, with the following fields:

1. Name

2. ampi__Project__c

3. ampi__Label__c

4. ampi__Result_Status__c

5. ampi__Result_Count__c

6. ampi__Results_Locked__c

7. ampi__Project_Indicator_Count__c

8. ampi__Documents_Required_for_RP__c

9. ampi__Date_Submitted__c

10. ampi__Reporting_Period_End_Date__c

11. OwnerId

12. CreatedById

13. LastModifiedById

Updates to ampi__Project_Indicator_Reporting_Period__c

Updated Field

Updates to ampi__Result__c

New Fields

Updated Fields

Updated Page Layout

The following fields were added to the Result Layout:

1. ampi__xx_Results_Not_Applicable__c

2. ampi__xx_Female_Results_Not_Applicable__c

3. ampi__xx_Male_Results_Not_Applicable__c

4. ampi__xx_Unknown_Results_Not_Applicable__c

5. ampi__xx_Picklist_Target_Numeric_Value__c

6. ampi__xx_Female_Picklist_Target_Numeric_Value__c

7. ampi__xx_Male_Picklist_Target_Numeric_Value__c

8. ampi__xx_Unknown_Picklist_Target_Numeric_Value__c

9. ampi__xx_Picklist_Result_Numeric_Value__c

10. ampi__xx_Female_Picklist_Result_Numeric_Value__c

11. ampi__xx_Male_Picklist_Result_Numeric_Value__c

12. ampi__xx_Unknown_Picklist_Result_Numeric_Value__c

Updates to ampi__Allocation__c

New Validation Rule

Updates to ampi__Disbursement__c

New Validation Rule

Updates to ampi__Financial__c

New Validation Rule

New Custom Labels

Updated Custom Labels

New Email Templates

1. IATI_XML_Generated_Not_Validated

2. IATI_XML_Generated_Validated_Without_Errors

3. IATI_XML_Validated_With_Errors

Updated Email Templates

1. IATI_Activity_XML_Generation_Failure

2. IATI_Organization_XML_Generation_Failure

Declarative Automation

Permission Sets

Amp Impact Admin

Object & Field Access

Apex Class Access

The following Apex classes have been added to the permission set:

1. AddResultLWC_CTRL

2. AddResult_Service

3. GenerateReportingPeriods

4. ProjectIndicatorGeoArea_TestHelper

5. ReportingPeriodFlowInput

6. ReportingPeriodFlowOutput

7. ReportingPeriod_Flow_Handler

8. ReportingPeriod_Flow_Warning_Handler

9. ReportingPeriod_TestFactory

10. Result

11. ResultRow

12. Result_TestHelper

13. STAR_Helper

14. SetTargetLWC_CTRL

15. SetTarget_Service

16. TargetRow

Record Type Access

IATI Full Access

Translations

Spanish Translation

Amp Impact is now available to be used in Spanish (language code “es”). Refer to the Upgrade Instructions for guidance on how to set up users to use Amp in Spanish. Note that certain elements will not be translated by default, such as custom labels marked as “Do not translate”, as translations for those elements may break functionality.

Portuguese Translation

For new labels in this and previous releases, Portuguese (language code “pt_BR”) translations are now available by default.