Key Product Features

New Features

Copy Objectives and Indicators from Another Framework

Further improving the ability to build frameworks, the Gemini release introduces a new popup that enables users to select objectives from other frameworks and copy those components into the framework that they are currently building. While copying these objectives, they can also choose to copy related project indicators, reducing the time it takes to build a framework from scratch.

Open

Note: This image is for illustrative purposes and may not represent the final product.

Feature Enhancements

Submissions: Conditionally Display Questions and Sections

The Submissions feature has been enhanced to allow for skip logic to be defined on questions and sections in the SubmissionTemplateBuilder. If a question or section has skip logic criteria defined, it will not display in the SubmissionResponseForm until the criteria on the controlling question has been met. Controlling questions can have either Picklist or Multi-select Picklist response types.

Open

Note: This image is for illustrative purposes and may not represent the final product.

Framework (LWC): Hide Indicator Columns

Previously, the project indicator column with the indicator definition could not be removed from the table, as this field was displayed by default. For organizations that build frameworks without project indicators, this took up an unnecessary amount of space in the framework table that could be better used for framework objective information. With this release, a new design attribute “Hide Indicator Columns” has been added to the manageLogFrames LWC component., when this design attribute is set to TRUE, all project indicator data is hidden from the framework table.

Note: This image is for illustrative purposes and may not represent the final product.

Framework (LWC): Expanded height for catalog of objectives popup

With the introduction of the catalog of objectives, the popup previously would only display a limited number of objectives in the catalog due to the limited height of the popup. This has been improved by increasing the maximum height of the popup by 33%, making it easier for users to build their frameworks with the catalog of objectives.

Note: The image on the right is for illustrative purposes and may not represent the final product.

Activities (LWC): Define the default sort order for the table

In previous versions of Amp Impact, the activities in the Activities Lightning Web Component were ordered in ascending order of Activity Earliest Start Date by default. The sort order could be changed by clicking on column headers, but for some organizations that would only view the table by a specific field order, that was an extra step to fruitfully interact with the table.

Note: This image is for illustrative purposes and may not represent the final product.

In this release, a new design attribute Activity Table Sort Order has been added to the Activities LWC component. System Administrators can enter up to two comma-separated field API names to customize the default order as well as a secondary order of activities. For example, if the System Administrator enters “Name, ampi__Type__c”, the table will sort first by Name, then by Type.

Set Targets / Add Results: Control the number of round-off digits to be displayed for large numbers (>1 million)

Note: This image is for illustrative purposes and may not represent the final product.

Large number (> 1 million) targets or results are rounded-off to display in the view-only status on Set Targets or Add Results (e.g. submitted targets or results, target values on Add Results, etc.), and the full number is visible when the user hovers over the rounded value. 

In previous releases, the number of round-off digits was controlled by the Number of Decimals field on the Project Indicator record (this field primarily controls the number of decimal places that can be entered for a numerical target or result). This sometimes led to misleading rounded-off numbers (e.g. 1,463,000 being displayed as 1M if the value of Number of Decimal Places field is 0).

This has been now resolved and now System Admins can define the round-off digits to be displayed for large numbers by assigning a value from 0 to 5 to field ‘Round off digits for large numbers’ on custom setting records Add Results and Set Targets (e.g. 1,463,000.00 can be displayed as 1.463M on the Set Targets page if the field ‘Round off digits for large numbers’ on custom setting record Set Targets has value 3).

Resolved Issues

Activities (LWC): Gantt Chart snaps back to Implementation Plan start date after edit

In the previous releases, as the Edit Activity popup closes after editing and saving an activity, the Activity table would refresh to store and display updated information. Due to this, the Gantt chart reloaded and snapped back to the beginning of the activity timeline, such that the user would lose their place in the implementation plan timeline. This has been resolved such that the user’s place in the timeline is preserved as they modify activities, creating a smoother user experience.

Activities (Aura): Customized labels for lookup fields not displaying in Add/Edit Activity popups

With the introduction of the Object Lookup Label Mapping custom metadata type, system administrators should have been able to define which field on the parent object displays in the lookup dropdown in the Add New Activity and Edit Activity popups  

However, this feature was not working on the Add New Activity or Edit Activity popups in the Activities Aura Component, instead displaying the default Name field in the lookup dropdowns. This has been resolved so that the custom metadata type Object Lookup Label Mapping is respected and displays the correct field values in the lookup dropdowns.

Activities (Aura & LWC): Incorrect dates displayed on the Gantt Chart when End Date is set to last week of December

The dates on the Activities Gantt Chart were appearing one year later than they were entered in and stored on the record. This issue was seen when the user inputs dates from the last week of the year (e.g. when 12/31/2021 was entered, 12/31/2022 was being displayed on the page and in the popup). This issue has now been resolved so that the correct dates are displayed in the Gantt Chart and popups.

Activities (Aura & LWC): Component does not load if user locale does not have country specification

Previously, the Activities Aura Component and Lightning Web Component would not load at all for a user if their locale does not have a country specification (e.g. Spanish instead of Spanish (Spain)). This has been fixed so that both components load for any locale, including the ones that do not specify a country.

Manage Frameworks (LWC): Order project indicators alpha-numerically by default

In the framework table, framework objectives are ordered alphabetically ascending based on objective name; however, related project indicators previously did not have a default order, thus creating an inconsistent user experience. This has been resolved so that, like framework objectives, project indicators are ordered alpha-numerically by ascending indicator definition.

Before Gemini:

After Gemini:

Note: This image is for illustrative purposes and may not represent the final product.

Manage Frameworks (LWC): Text wrapping at incorrect indentation level in hierarchy of objectives

For any framework objective that is a child, the initial line of the objective name is indented to indicate its position in the hierarchy of objectives. However, if the objective name exceeds one line, the text wraps but without indentation, creating a poor UI that makes the hierarchy difficult to observe. This has been resolved so that UI is cleaner, such that the text wraps at the same indentation level as the first line of an objective name.

Manage Frameworks (LWC): When adding multiple child/nested objectives from the catalog to a framework, the parent objective is added multiple times to that framework

When adding objectives to a framework via the catalog of objectives, if a user selects a catalog-level objective that is a child, then the parent objective is also auto-selected to be added to the framework. However, when a user manually selects multiple objectives that are children to the same parent objective in the catalog, and adds them to the framework, then the parent objective is added to the framework multiple times, once for each child objective that was manually selected. For example, if three objectives are manually selected, all of which are child to the “Increase gender parity in employment” impact-level objective, then the “Increase gender parity in employment” objective will be added three times to the framework. 

This has been resolved so that an objective is only added once to the  into a framework, irrespective of how many child objectives are added.

IATI Publishing: Default language attribute not printing in Activity or Organisation XML

The IATI public validator requires that the Activity and Organisation XMLs either define a language at the file level (i.e. a default language attribute) or at the level of each narrative element. However, Amp’s IATI functionality was printing neither into the generated XMLs. This has been resolved so that the default language attribute is now being printed into the XML based on the system’s default language or the user language.

Before Gemini:

After Gemini:

Calculated Indicators: Calculation batch fails to run for all disaggregated result values if even one denominator is entered as zero OR left blank

If a sex-disaggregated, percent type calculated indicator that was being calculated by input numerator indicator and denominator indicator such that denominator was either zero or left blank (NULL), the entire calculation used to fail and no results were returned for any disaggregation of the calculated indicator. This issue has now been resolved such that only those disaggregations that have a zero (or NULL) denominator are displayed as blank in the Result table, and other disaggregations are calculated and displayed correctly.

Add Results / Calculated Indicators: Sum of calculated results for sex-disaggregated percent indicators displays incorrect value

For a sex-disaggregated percent indicator where Type of Results is set as “Calculated” and Calculate Total is set as “Sum Total”, an incorrect Total Result value would display in the total column on the Add Results Visualforce page. Even though the calculation is correctly performed and the correct value is stored in the Result Value field on the result record, the total percent values displayed on the Add Results page was a simple sum of sex-disaggregated percent result values. 

This discrepancy has been resolved so that the correct Result Value (that is printed into the Result record) is displayed in the table.

Manage Indicators (LWC): Error message on deletion of project indicator does not clear for subsequent delete operations

On the first attempt to delete a project indicator with existing result data by confirming the action in the deletion popup, the error message indicating to the user that the delete action failed displays correctly, i.e. with a red border at the top of the confirmation popup. However, when the user again clicks the delete icon to open the confirmation popup, the error message continues to display, without the red border, even though the delete action has not been confirmed. 

This has been fixed so that the error message does not display on load of the popup, but only when the delete action is confirmed.

Manage Indicators (LWC): Component does not display as expected in two- or three-region Lightning Page layouts

The Manage Indicators Lightning Web Component was previously not responsive to the smaller container size provided in Lightning Pages with either two- or three-region layouts. This resulted in a poor UI that included text wrapping within buttons, buttons overlapping with search bars, search bar width exceeding the component width, etc. 

This has been resolved so that the Lightning Web Component, as well as all sub-components within the component, are responsive to container size.

Manage Indicators (Visualforce) / Aggregated Indicators: User can save a milestone or qualitative indicator as an aggregated indicator

In earlier versions of Amp Impact, there was no dependency between the Data Type and Type of Results field on Project Indicator. A user could successfully save a Project Indicator with Type of Results as Aggregated, even though the Data Type was Milestone or Qualitative, two data types that are incompatible with the aggregation feature. This has been resolved so that an error message now displays if a user tries to set the Type of Results to Aggregated while the Data Type is set to either Milestone or Qualitative.

Lightning Web Components: Info icon for help text not displaying next to lookup fields with existing values in pop ups

In all Lightning Web Components, if help text was defined for a lookup field that was included in Add New Custom Indicator/ Customize Project Indicator popup field set, the help text icon would not display next to the lookup field in the popup if the lookup field was already populated before loading the popup. This has been resolved so that if the help text is defined, the info icon and help text is always accessible by the user.

Lightning Web Components: Values in custom date fields display inconsistently across the Lightning Web Components

Across all three Lightning Web Components, custom date fields exhibited inconsistent behavior when included in the table field sets.

• Activities - Date values displayed incorrectly.

• Manage Frameworks & Manage Indicators - Date values displayed in MMM DD, YYYY format, instead of per the system/user locale.

This has been addressed so that any custom date field in the tables on the Lightning Web Components displays according to the system or user locale.

Risk: Unable to save a Risk Assessment record with a blank Reporting Period value 

When creating or editing a Risk Assessment record (e.g. via Risk Assessment related list on a Risk record), a user would receive an error message and be unable to save the record if they left the Reporting Period lookup blank, even though the field was not marked as required in the page layout. This has been resolved so that the validation rule that generated the error message now accepts null values in the Reporting Period lookup, and users can successfully create or edit Risk Assessments without populating the field.

Manage Disbursements: Finnish locale preventing users from saving disbursements

If a user locale was set to Finnish, then whenever they populated the Amount field in the Add or Edit popup on the Manage Disbursements page, they would receive an error message of “Invalid currency” and be prevented from saving the record, even if they entered a valid value. This has been resolved so that the user does not receive that error message unnecessarily and can successfully create or modify disbursements in the page.

Packaging Changes

Changes to ampi__Activity__c

Updated field

Changes to ampi__Objective__c

New field

New fieldsets

Changes to ampi__Project_Indicator__c

New field

New fieldsets

Changes to ampi__Question__c

New fields

Updated fieldsets

Changes to ampi__Section__c

New fields

Updated fieldsets

Custom Labels

New Custom Labels

Updated Custom Labels

Declarative Automation

Process Builder

Permission Sets

Amp Impact Admin

Submission Response

Submission Review

Submission Template

Design Attribute

Manage Frameworks LWC Component