To overcome the ViewState limitation of Visualforce pages, the Manage Indicators page has been rebuilt as a Lightning Web Component. The majority of previous functionality is replicated on the new interface, including:

• Create custom indicators - define indicators directly on a project

• Indicators catalog - select indicators from the catalog and add them to a project

• Dynamic search filters - control the filters displayed using field sets

• Custom indicator order - set the default order of the tables based on any field

For the full suite of functionality supported on the new Lightning Web Component, please refer to the User Guide.

While the Lightning Web Component replicates much of the interface of the Visualforce page, some improvements to the user interface have been made in this release, including:

• Action Menu for Project Indicators

• Select Catalog Indicators Across Multiple Pages

• Multi-select Picklists Available in the Search Filters

• Multiple Steps in the Add New Indicator Popup

• Preview Disaggregation Values when Selecting the Disaggregation Group

The action icons on the Selected Indicators table have been deprecated and replaced with a dropdown action menu.

Open

Open

In the Visualforce page, only Indicators on the same page could be selected in the Indicator Catalog and added to a Project at once. This means that only 10 Indicators at maximum can be added at a time to a particular Project. With the latest release, Indicators can now be selected across pages in the Indicator Catalog, so that more than 10 Indicators may be selected and added to a Project. A badge on the bottom left will inform the user of how many Indicators are selected from the total available.

Open

With the introduction of search filters controlled by field sets, the search filters for picklists, lookups, Objective and Thematic Area long text fields will be displayed as input text. In this release, when any picklist, relationship field or the Objective/Thematic Area fields are added onto the search filter field sets, a multi-select picklist interface will be displayed as a filter.

Open

The Add New Indicator Popup has been split into multiple steps/popups to differentiate data that should sit at the Catalog-level (e.g. Data Type, disaggregation levels) and data that should sit at the Project-level (e.g. Baseline, Life of Project Target). This creates a more wizard-like experience, instead of a single popup that one has to scroll through extensively.

Catalog-level Indicator Data

Open

Project-level Indicator Data

Open

In the Visualforce page, when editing an indicator’s Disaggregation Group, a user would only see the Disaggregation Group’s name. Now in the Lightning Web Component, the dropdown picklist used to select a Disaggregation Group  also displays a preview of the Disaggregation Group’s Disaggregation Values. This gives the user more context on the disaggregation levels for which they will be reporting on that indicator.

Open

Alongside the latest release of Amp Impact, a new extension package has been created to expedite the setup of an environment to manage grant applications and reviews for funders. The package includes common configuration that funders can use to create calls for proposals, review proposals, and track grants that receive funding. The package also includes templates for automation and page layouts that can be used as a starting point for building a grant management system.

When creating a template, users can now add both short text and date questions to the submission form using the Submission Template Builder. In the Add New Question popup, in the Response Type field, two new picklist values (Short Text, Date) will be available as an option.

When Short Text is selected as the Response Type and a Submission Response is created from the template, the responding user will now see a text input field for that question in the Submission Response Form.

Open

When Date is selected as the Response Type and a Submission Response is created from the template, the responding user will be able to use a date picker for that question in the Submission Response Form.

Open

Previously, when downloading a Submission Response as a Word document, if any selection had been made in either a picklist or a multi-select picklist answer, then only the selected value(s) would print into the downloaded Word document. This could be challenging when working offline, as users cannot know what the other available options are.

This functionality has been updated such that when downloading a Submission Response as a Word document, if any selection has been made in either a picklist or a multi-select picklist answer, then all picklist values are printed into the document, and the selected picklist value(s) are bolded.

Open

Previously, if multiple Submissions from different templates displayed in the Submission Radar Chart, they would display in a column without any labelling except for the color coding used within each radar chart. As this could be confusing for a user, there will now be a header displayed for each radar chart that prints the Description field of the Template related to each chart.

Open

A bug in previous releases prevented custom lookups from being added to the popups on Manage Framework. In addition to fixing this bug, the new release also enables system administrators to define the field displayed in the dropdown for lookups using a new custom metadata type. This allows for the custom display of fields in lookup dialogs in the component.

This flexibility has been applied to the following three components:

• Manage Framework

• Manage Indicators (Lightning Web Component)

• Financial Download / Upload

In earlier releases, for any value manually entered into Target To Date or Result To Date fields for a percent Project Indicator (that is associated to multiple Project Indicator Geographic Areas and has a child Disaggregated Project Indicator), it would get overwritten to NULL due to triggers on the Result object. This would result in the Logframes table displaying NULL values in the Target To Date and Result To Date fields.

This has been updated such that if the user manually enters the values in the Target To Date and Result To Date fields through the Project Indicator record page, then inputting values on Set Targets and Add Results page will not overwrite previously saved values. The Logframe table does not display NULL values in Target to Date and Result To Date fields if the user manually enters values against a percent Project Indicator (matching the above mentioned criteria) on Set Targets and Add Results pages or from Project Indicator record page.

Previously, the Indicator Definition field was hardcoded to display as the first column of the Selected Indicators table on ManageIndicators VisualForce page.

This has been updated such that any field that is dropped first on the fieldset for Selected Indicators table can dynamically display in the first column of the table. Values in this field will always be displayed as hyperlinks to the Project Indicator record page.

Open

In earlier releases, any help text that was added to a field on Catalog Objective or Project Objective would not be accessible in the Add New Framework Item or Edit Framework Item popups in Manage Frameworks.

This has been updated such that help text is visible in these popups through a popover.

Open

Prior to this release, indicator stoplights were enabled by default in the custom settings, but users would still have to manually populate the threshold fields for them to display on the Add Results page.

This has been updated such that the default value for the Red/Yellow Threshold is 75% and the default value for the Yellow/Green Threshold is 100%.

In earlier releases, when downloading and uploading Financial records via Excel Upload onto either a Budget or a Reporting Period, there would be no guidance for the user on how to populate either picklist or relationship fields. The user would have to manually enter this data into the Excel with no reference to what were the valid values for picklist or relationship fields, leaving room for user error with typos.

This has been updated such that when a Budget or Reporting Period’s Financials are downloaded via Excel Download, a new tab “Reference List” is included in the Excel, providing lists of the valid values that can be entered into each picklist or relationships field that is included as a column in the Excel file.

Open

Previously, when uploading Financial records via Excel Upload onto either a Budget or a Reporting Period, the record page would only refresh if the user exited the final popup by clicking the “Close” button. If a user exited the final popup by clicking the “X”, the record page would not refresh to reflect the newly created or updated Financials.

Open

This has been updated such that, as soon as the user confirms the upload by clicking “Yes”, the record page will refresh and display the updated child Financial records.

Open

Previously, when uploading targets or results using the Excel Upload feature on Set Targets or Add Results, the entire upload would fail, if a new row was added either right under the column header row (Row 3) or at the bottom of the file. If a row was added in either place, then the upload would time out, and the user would get no error messaging to indicate why the upload failed.

With this update, the user can now successfully progress through the popups for Excel Upload, even if they add a row in the file. In the final confirmation popup, the user will now see an error message if they have added rows, notifying them that the additional rows will not be processed.

Open

In earlier releases, any error handling that rendered on a popup on the Disbursements Visualforce page would reappear when another popup was opened, even if all the values (and therefore the error) was cleared from the popup.

This has now been resolved so that any error message clears with the reload of a popup, thereby creating a less confusing user experience.

Prior to this release, date pickers in the popups on the Disbursements Visualforce page behaved unexpectedly:

• Add Disbursement popup: When a user selected a date in the date picker, closed the popup without saving, and then reopened the popup, the previously selected date still displayed as highlighted in the date picker (but not in the field). When the highlighted date was clicked in the date picker to display it in the field and then the user saved the record, it  saved as a  NULL value.

• Edit Disbursement popup: When a user clicked on the calendar icon for a date field, the date picker would open without highlighting the value saved in the field.
  
  

This has now been updated such that in both popups, the date picker behaves as expected, which means the highlighted date and field default value is today for the Add Disbursement popup and the previously saved value for the Edit Disbursement popup.

Open

Previously, users were prevented from creating a new Project Geographic Area record if they did not have access to the Exclude From IATI field on Project Geographic Area. This is because the After Insert trigger on Project Geographic Area would try to populate that field, even if IATI was not being used in the system.

This has been updated such that the trigger does not update the field and the Project Geographic Areas can be created without any involvement of the IATI feature.

In previous releases, when a custom field would be added to any of the field sets for the Excel columns for Financial download/upload, the user would receive an error message and the download would fail.

This has been resolved such that custom fields can be added to the Excel column field sets and the Financials Excel file will download successfully for the user.

In previous releases, when a formula field would be added to any of the field sets for the Excel columns for Financial download/upload, the user would receive an error message when attempting to upload Financial records notifying them that the entire upload failed.

Open

This has been fixed such that the upload succeeds, even if formula fields are included in the Excel.

In previous releases, the downloaded Financial Excel file would open corrupted when there were more than 10 total values in picklist fields on the Financial object, and that picklist field was added to the ampi__BUDGET_EXCEL_COLUMNS or ampi__REPORT_EXCEL_COLUMNS field set.

This has been resolved such that the downloaded Excel file opens uncorrupted regardless of the total number of values in picklist fields on the Financial object.

With the introduction of multiple languages in the last release, if a particular language field was not populated, then the interfaces would display a blank value for the user in that particular language context. For example, a system has one Spanish User and one French User, and USER_LANGUAGE_CODE has been translated in Spanish as ‘1’ and in French as ‘2’. Now, if the field value of ampi__Geographical_Area__c.ampi__Name_Language_1__c is provided in Spanish while ampi__Geographical_Area__c.ampi__Name_Language_2__c is left blank, then, on the Set Targets page, the Spanish User will view the Geographic Area Name in Spanish, while the French User will see a NULL value in the Geographic Area dropdown.

Open

Two updates have been made such that blank values are not displayed in the interfaces for a user if the language field for that user’s language context is left NULL:

1. For Text and TextArea fields that support multiple languages, the formula that prints a value based on the user’s language context will print the default value. The formula field can be dropped into field sets and page layouts, and it will display according to the user’s language context.

2. For LongTextArea fields that support multiple languages, if the default language field is included in the related field set, the interface itself will directly print the default value.

With the updates to triggers to create Disaggregated Project Indicator records in previous releases when the Disaggregation Group field is populated on Project Indicator through native Salesforce, an inconsistency caused the triggers to sometimes created multiple junction records for a particular Project Indicator and sometimes to create no junction records for a particular Project Indicator.

This has been fixed such that the trigger fires correctly and only generates a single child Disaggregated Project Indicator record for any particular Project Indicator record when a user populated Disaggregation Group through native Salesforce.

In earlier versions of Amp Impact, the default value of a field would not populate in the Add New Indicator popup, and instead a blank field would display, despite any default values set. All default values had to be hard-coded directly into the interface.

This has been updated such that default values defined at the field level are automatically printed into the fields in the Add New Indicator popup. This creates a consistency between what a System Administrator defines and what a user sees.

Previously, an incorrect default value would display for percent field on ampi__Indicator__c. For example, if the default value for percent field ampi_Red_Yellow_Threshold__c was set to 0.75, it would display as 0.75 instead of 75% in the Add New Custom Indicator popup.

This has been resolved so that the correct value displays as a percentage (75%) instead of a decimal value (0.75).

Open

Previously, an inaccurate error handling would display if a project consisted of only one Project Indicator which was of percent data type and was related to a Disaggregation Group. The error handling incorrectly stated “You must create one Project Indicator and one Reporting Period for this project”.

The text in error handling has been updated to accurately inform the user. The error handling message states “You must create at least one compatible Project Indicator (Number/Currency with any disaggregation, or Percent with no disaggregation) and one compatible Reporting Period for this Project.”

Open

Previously, if a qualitative response exceeded 20,000 characters and the Submission was downloaded, the Word document would print the qualitative response such that the right edge of the text would be cut off (see below).

Open

This has now been resolved such that qualitative responses are no longer cut off, and this is irrespective of the number of characters in the response.

For certain scenarios, the Submission Radar Chart component would fail to render without any error message, causing a confusing user experience. This error would occur in the following scenarios, in which a Submission would have:

1. One scored Question and no defined Section

2. Multiple scored Questions and no defined Section

3. Multiple scored Questions and multiple unscored Sections

This has now been resolved such that the component will provide error handling to the user to explain why the radar chart is not displaying.

1. New fields:

2. New page layout: Modification Layout

1. Updated page layout Project Layout:

   1. Related list for ampi__Modification__c added

2. Updated Lightning Record Page

   1. Single Related List component for ampi__Modification__c added to the Setup tab

3. Field updates:

   1. The following translation formula field has an updated formula to return the default language value in case the specific language value is left NULL (per this update):

Default values have been set for the following fields on ampi__Indicator__c:

The following translation formula fields have updated formulas to return the default language value in case the specific language value is left NULL (per this update):

Due to the increased flexibility in the display of the Manage Indicators Visualforce page and Lightning Web Component, the following field sets have the following changes:

Help text has been added for the following formula(text) field fields on ampi__Project_Indicator__c:

Character limits have been updated for the following fields on ampi__Project_Indicator__c: