Our release notes offer brief, high-level descriptions of new features, enhancements, and resolved issues. Detailed information on Set-up, Configuration and Feature Information is available in the Installation Guide and User Guide for each release.
Contact support@verasolutions.org to share feedback.
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:
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.
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:
Comparing Baseline data against Results
Entering Results for Picklist Indicators
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:
Sample help text to provide guidance to users on which fields will be printed into the IATI XMLs (see IATI Setup Guide)
Clear documentation of the mapping between the Amp data model and the IATI standard (see IATI User Guide)
Error handling for when the generated XML fails to pass the IATI Validator
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.
System Admin Note:
A new Custom Field Disable Geographic Area Hierarchy (ampi__Disable_Geographic_Area_Hierarchy__c) has been created within the Custom Setting for Set Targets (ampi__SetTargets__c) and Add Results (ampi__AddResults__c).
To disable the hierarchy in the Geographic Area dropdown, check the checkbox ampi__Disable_Geographic_Area_Hierarchy__c as TRUE.
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-organisation
iati-activity
reporting-org
provider-org
receiver-org
total-expenditure
recipient-org-budget
total-budget
transaction
result-type
contact-info
location
recipient-country
recipient-region
recipient-org
budget
budget-line
reference
period
actual
humanitarian-scope
policy-marker
sector
Note: Not all elements and attributes have been covered by this release. Elements or attributes required by IATI may still face this error. If there are any optional elements or attributes printing erroneously into the IATI XMLs, please contact support@verasolutions.org.
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:
Name
ampi__Project__c
ampi__IATI_Type__c
ampi__IATI_Budget_Status__c
ampi__Start_Date__c
ampi__End_Date__c
ampi__IATI_Value_Date__c
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:
Name | Type | Related Lightning Web Component |
ActivityChart | Aura Component | activities |
AddResults | Visualforce Page | addResults |
ManageLogFrames | Visualforce Page | manageLogFrames |
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
Field Label | Field API Name | Data Type |
IATI Activity XML Error Log | ampi__IATI_Activity_XML_Error_Log__c | URL |
IATI Organisation XML Error Log | ampi__IATI_Organisation_XML_Error_Log__c | URL |
IATI Validator Error Response | ampi__IATI_Validator_Error_Response__c | LongTextArea(131072) |
Updated Fields
Field Label | Field API Name | Change(s) |
IATI Organisation Type Code | ampi__IATI_Organization_Type_Code__c | Changed “Organization” to “Organisation” in field label |
IATI Organisation Type | ampi__IATI_Organization_Type__c | Changed “Organization” to “Organisation” in field label |
IATI Organisation XML Link | ampi__IATI_Organization_XML_Link__c | Changed “Organization” to “Organisation” in field label |
Organisation Identifier | ampi__Organization_Identifier__c | Changed “Organization” to “Organisation” in field label |
Updates to ampi__Indicator__c
New Fields
Field Label | Field API Name | Data Type |
IATI Indicator Measure Code | ampi__IATI_Indicator_Measure_Code__c | Formula(Text) |
Has Baseline | ampi__xx_Has_Baseline__c | Checkbox |
Map Picklist Values To Number | ampi__xx_Map_Picklist_Values_To_Number__c | Checkbox |
Numbers Mapped To Picklist Values | ampi__xx_Numbers_Mapped_To_Picklist_Values__c | TextArea(255) |
Reporting Picklist Values | ampi__xx_Reporting_Picklist_Values__c | LongTextArea(2000) |
Updated Fields
Field Label | Field API Name | Change(s) |
Data Type | ampi__Data_Type__c | Created new picklist value “Picklist” |
Type of Results | ampi__Type_of_Results__c | Created new picklist value “Read Only” |
Updated Field Sets
Field Set Label | Field Set API Name | Change(s) |
Add New Indicator Popup | ampi__ADD_NEW_INDICATOR_POPUP | Added the following fields to the field set:
|
Indicator Catalog Search Filter | ampi__INDICATOR_CATALOG_SEARCH_FILTER | Made the following fields available for the field set:
|
Updated Page Layout
The following fields were added to the Indicator Layout:
ampi__xx_Has_Baseline__c
ampi__xx_Reporting_Picklist_Values__c
ampi__xx_Map_Picklist_Values_To_Number__c
ampi__xx_Numbers_Mapped_To_Picklist_Values__c
Updates to ampi__Project_Indicator__c
New Fields
Field Label | Field API Name | Data Type |
IATI Indicator Measure Code | ampi__IATI_Indicator_Measure_Code__c | Formula(Text) |
Has Baseline | ampi__xx_Has_Baseline__c | Checkbox |
Map Picklist Values To Number | ampi__xx_Map_Picklist_Values_To_Number__c | Checkbox |
Numbers Mapped To Picklist Values | ampi__xx_Numbers_Mapped_To_Picklist_Values__c | TextArea(255) |
Reporting Picklist Values | ampi__xx_Reporting_Picklist_Values__c | LongTextArea(2000) |
Updated Field
Field Label | Field API Name | Change(s) |
Type of Results | ampi__Type_of_Results__c | Created new picklist value “Read Only” |
Updated Field Sets
Field Set Label | Field Set API Name | Change(s) |
Add Results Info Popover | ampi__ADD_RESULTS_INFO_POPOVER | Moved ampi__Cross_Disaggregation_by_Sex__c and ampi__Disaggregation_Group__c to be in the field set by default |
Edit Project Indicator Popup | ampi__EDIT_PROJECT_INDICATOR_POPUP | Added the following fields to the field set:
|
Project Indicators Search Filters | ampi__PROJECT_INDICATORS_SEARCH_FILTERS | Made the following fields available for the field set:
|
Selected Project Indicators Table | ampi__SELECTED_PROJECT_INDICATORS_TABLE | Made ampi__xx_Has_Baseline__c available for the field set |
Set Targets Info Popover | ampi__SET_TARGETS_INFO_POPOVER | Moved ampi__Cross_Disaggregation_by_Sex__c and ampi__Disaggregation_Group__c to be in the field set by default |
Updated Page Layout
The following fields were added to the Project Indicator Layout:
ampi__xx_Has_Baseline__c
ampi__xx_Reporting_Picklist_Values__c
ampi__xx_Map_Picklist_Values_To_Number__c
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:
ampi__Active__c
Updates to ampi__Reporting_Period__c
New Record Types
Record Type Label | Record Type Name | Relevant Picklist Fields |
Baseline | Baseline |
|
Reporting Period | Reporting_Period |
|
New Page Layout
The new page layout Baseline Layout was created for the Baseline Record Type, with the following fields:
Name
ampi__Project__c
ampi__Label__c
ampi__Result_Status__c
ampi__Result_Count__c
ampi__Results_Locked__c
ampi__Project_Indicator_Count__c
ampi__Documents_Required_for_RP__c
ampi__Date_Submitted__c
ampi__Reporting_Period_End_Date__c
OwnerId
CreatedById
LastModifiedById
Updates to ampi__Project_Indicator_Reporting_Period__c
Updated Field
Field Label | Field API Name | Change(s) |
Data Tracked | ampi__Data_Tracked__c |
|
Updates to ampi__Result__c
New Fields
Field Label | Field API Name | Data Type |
Female Picklist Result Numeric Value | ampi__xx_Female_Picklist_Result_Numeric_Value__c | Number(18) |
Female Picklist Target Numeric Value | ampi__xx_Female_Picklist_Target_Numeric_Value__c | Number(18) |
Female Results Not Applicable | ampi__xx_Female_Results_Not_Applicable__c | Checkbox |
Male Picklist Result Numeric Value | ampi__xx_Male_Picklist_Result_Numeric_Value__c | Number(18) |
Male Picklist Target Numeric Value | ampi__xx_Male_Picklist_Target_Numeric_Value__c | Number(18) |
Male Results Not Applicable | ampi__xx_Male_Results_Not_Applicable__c | Checkbox |
Picklist Result Numeric Value | ampi__xx_Picklist_Result_Numeric_Value__c | Number(18) |
Picklist Target Numeric Value | ampi__xx_Picklist_Target_Numeric_Value__c | Number(18) |
Results Not Applicable | ampi__xx_Picklist_Target_Numeric_Value__c | Checkbox |
Unknown Picklist Result Numeric Value | ampi__xx_Unknown_Picklist_Result_Numeric_Value__c | Number(18) |
Unknown Picklist Target Numeric Value | ampi__xx_Unknown_Picklist_Target_Numeric_Value__c | Number(18) |
Unknown Results Not Applicable | ampi__xx_Unknown_Results_Not_Applicable__c | Checkbox |
Updated Fields
Field Label | Field API Name | Change(s) |
Data Tracked | ampi__Data_Tracked__c |
|
Female Result Qualitative | ampi__Female_Result_Qualitative__c | Updated description to indicate picklist results are also captured in field |
Female Target Qualitative | ampi__Female_Target_Qualitative__c | Updated description to indicate picklist targets are also captured in field |
Male Result Qualitative | ampi__Male_Result_Qualitative__c | Updated description to indicate picklist results are also captured in field |
Male Target Qualitative | ampi__Male_Target_Qualitative__c | Updated description to indicate picklist targets are also captured in field |
Result Qualitative Value | ampi__Result_Qualitative_Value__c | Updated description to indicate picklist results are also captured in field |
Target Qualitative Value | ampi__Target_Qualitative_Value__c | Updated description to indicate picklist targets are also captured in field |
Total Result | ampi__Total_Result__c | Updated formula to account for Read Only Type of Results |
Unknown Result Qualitative | ampi__Unknown_Result_Qualitative__c | Updated description to indicate picklist results are also captured in field |
Unknown Target Qualitative | ampi__Unknown_Target_Qualitative__c | Updated description to indicate picklist targets are also captured in field |
Updated Page Layout
The following fields were added to the Result Layout:
ampi__xx_Results_Not_Applicable__c
ampi__xx_Female_Results_Not_Applicable__c
ampi__xx_Male_Results_Not_Applicable__c
ampi__xx_Unknown_Results_Not_Applicable__c
ampi__xx_Picklist_Target_Numeric_Value__c
ampi__xx_Female_Picklist_Target_Numeric_Value__c
ampi__xx_Male_Picklist_Target_Numeric_Value__c
ampi__xx_Unknown_Picklist_Target_Numeric_Value__c
ampi__xx_Picklist_Result_Numeric_Value__c
ampi__xx_Female_Picklist_Result_Numeric_Value__c
ampi__xx_Male_Picklist_Result_Numeric_Value__c
ampi__xx_Unknown_Picklist_Result_Numeric_Value__c
Updates to ampi__Allocation__c
New Validation Rule
Rule Name | Error Location (Field API Name) | Purpose |
IATI_Transaction_Organisation_Role_Check | ampi__IATI_Organization_Role__c | Validation rule to restrict Organisation role in IATI transactions to be limited to Funding and Implementing in order to prevent validation errors in the IATI Activity XML. |
Updates to ampi__Disbursement__c
New Validation Rule
Rule Name | Error Location (Field API Name) | Purpose |
IATI_Transaction_Organisation_Role_Check | ampi__IATI_Organization_Role__c | Validation rule to restrict Organisation role in IATI transactions to be limited to Funding and Implementing in order to prevent validation errors in the IATI Activity XML. |
Updates to ampi__Financial__c
New Validation Rule
Rule Name | Error Location (Field API Name) | Purpose |
IATI_Transaction_Organisation_Role_Check | ampi__IATI_Organization_Role__c | Validation rule to restrict Organisation role in IATI transactions to be limited to Funding and Implementing in order to prevent validation errors in the IATI Activity XML. |
New Custom Labels
Name | Categories | Value |
ADD_DISAGG_COMMENT_MESSAGE | AddResults, SetTargets, Amp Impact | Click to add comment(s) |
ADD_COMMENT_MESSAGE | AddResults, SetTargets, Amp Impact | Click here to add comment |
AR_DOWNLOAD_DISABLED_NO_PI | SetTargets, AddResults, Interface, Amp Impact | No project indicators available for download |
BACK | SetTargets, AddResults, Amp Impact | Back |
BASELINE_COLUMN | Amp Impact, AddResults | Baseline |
COMPARE_WITH | Amp Impact, AddResults | Compare With |
CONFIRM_RP_GA_RESULT_UPLOAD | Results, Upload, Popup, Confirm, Warning, Excel, Spreadsheet, Template, AddResults, Amp Impact | Please ensure you have selected the correct result template for: |
CONFIRM_SUBMIT_REVIEW_TARGETS | SetTargets, AddResults, Amp Impact | Are you sure you want to submit targets for selected Reporting Periods? |
CONFIRM_SUBMIT_REVIEW_RESULTS | SetTargets, AddResults, Amp Impact | Are you sure you want to submit Results for this Reporting Period? |
DATA_TRACKED_BASELINE | DO NOT TRANSLATE, SetTargets, AddResults, ManageIndicators, Picklist Value, Amp Impact | Baseline |
DOWNLOAD_BUTTON | SetTargets, AddResults, Excel Download, Interface, Amp Impact | Download |
DOWNLOAD_RESULTS_BUTTON | AddResults, Excel Download popup, Amp Impact | Download Results |
DOWNLOAD_RESULTS_EXCEL_TEXT | AddResults, Excel Download popup, Amp Impact | The Results Template for the selected data has been generated. Please click on the Download button to save this file to your system or click on the View button to view the generated file. |
GENERATE_RESULTS_EXCEL_TEXT | AddResults, Excel Download popup, Amp Impact | Would you like to generate a Results Template excel file for the currently selected data on this page? |
HOVER_MSG_NO_BASELINE_SET | AddResults, Interface, Amp Impact | No Baseline have been set for this indicator. |
IATI_VALIDATOR_NAMED_CREDS | Amp Impact, IATI, Do Not Translate | IATI_VALIDATOR |
IATI_XLSX_TEMPLATE_FRAME | Amp Impact, IATI Validator, Do not Translate | IATIErrorXLSXTemplate |
IATI_XML_GENERATED_NOT_VALIDATED | Amp Impact, IATI, Do Not Translate | IATI_XML_Generated_Not_Validated |
IATI_XML_GENERATED_NOT_VALIDATED_SUBJECT | Amp Impact, Do not Translate, IATI | Your IATI [[XML_TYPE]] standard XML file was generated but could not be validated. |
IATI_XML_GENERATED_VALIDATED_WITHOUT_ERRORS | Amp Impact, IATI, Do Not Translate | IATI_XML_Generated_Validated_Without_Errors |
IATI_XML_GENERATED_VALIDATED_WITHOUT_ERROS_SUBJECT | Amp Impact, IATI, Do not translate | Your IATI [[XML_TYPE]] standard XML file is successfully validated with no errors |
IATI_XML_GENERATED_VALIDATED_WITH_ERRORS_SUBJECT | Amp Impact, IATI, Do not translate | Your IATI [[XML_TYPE]] XML file is validated with errors |
IATI_XML_VALIDATED_WITH_ERRORS | Amp Impact, IATI, Do Not Translate | IATI_XML_Validated_With_Errors |
INDICATOR_PICKLIST_DATA_TYPE | DO NOT TRANSLATE, SetTargets, AddResults, ManageFramework, ManageIndicators, Picklist Value, Amp Impact | Picklist |
LOCKED_PICKLIST_LABEL | Amp Impact, AddResults | Locked |
NA_EXCEL_COLUMN_HEADER | AddResults, Excel Download popup, Amp Impact | Not Applicable? |
NA_OPTION_FALSE | AddResults, Excel Download popup, Amp Impact | FALSE |
NA_OPTION_TRUE | AddResults, Excel Download popup, Amp Impact | TRUE |
NOT_APPLICABLE | SetTargets, Interface, Amp Impact | NA |
PREPARE_EXCEL_FOR_UPLOAD_3A | SetTargets, AddResults, Excel Download, Excel File, Amp Impact | a. For Picklist and Milestone type Result, choose from the result options listed below the indicator definition |
PREPARE_EXCEL_FOR_UPLOAD_3B | SetTargets, AddResults, Excel Download, Excel File, Amp Impact | b. You can mark a result as not applicable by entering TRUE in the "Not Applicable?" column next to the result column |
PREVIEW_IMAGE_TITLE | SetTargets, AddResults | [Image] |
PROJECT_INDICATOR_READ_ONLY_TYPE | DO NOT TRANSLATE, SetTargets, AddResults, ManageIndicators, Picklist Value, Amp Impact | Read Only |
QUALITATIVE_DISAGGREGATION_PREVIEW_TEXT | AddResults, SetTargets, Amp Impact | This disaggregated indicator cannot be previewed. Please click here. |
RELATED_INFORMATION_HEADER | AddResults, SetTargets, Interface, Amp Impact | Related Information |
REPORTING_PERIOD_RECORD_TYPE | Amp Impact, Create Reporting Periods, DO NOT TRANSLATE, Reporting Period | Reporting_Period |
REPORTING_PERIOD_NAME | Reporting_Period | |
RESULTS_FAILED | AddResults, Interface, Amp Impact | Results not uploaded |
RESULTS_SUCCESFULL | AddResults, Interface, Amp Impact | Results successfully uploaded |
RESULT_OPTIONS_LABEL | AddResults, Excel Download, Amp Impact | Result Options: |
SELECT_ALL | SetTargets, AddResults, Amp Impact | Select All |
SEX_DISAGGREGATION | SetTargets, AddResults, Interface, Amp Impact | Sex Disaggregation |
ST_SAVE_HELPTEXT | SetTargets, AddResults, Interface, Amp Impact | Targets entered in this popup will save only when the Save button is clicked |
TARGET_BASELINE_SUMMARY_NA | SetTargets, AddResults, Table, Amp Impact | SUMMARY NOT AVAILABLE |
TARGET_BASELINE_SUMMARY_TOOLTIP | SetTargets, AddResults, Table, Amp Impact | Click on the hyperlinked value or displayed icon on the Results Column to compare with disaggregated Results |
TARGET_NOT_DISAGGREGATED_POPUP_INFO | SetTargets, AddResults, Table, Amp Impact | Since Target Frequency is different than Reporting Frequency for this Project Indicator, the Targets are not displayed |
UPLOAD_DOCS_INSTRUCTION | Results, Upload, Documents, Popup, AddResults LWC, Amp Impact | To upload document(s), click on the Upload Files button and select the file(s) you want to upload. |
UPLOAD_RESULTS | Results, Upload, Excel, Spreadsheet, Template, AddResults LWC, Amp Impact | Upload Results |
VIEW_BUTTON | AddResults, Excel Download popup, Amp Impact | View |
VALUE_COLUMN | SetTargets, AddResults, Table, Amp Impact | Summary Value |
Updated Custom Labels
Name | Categories | Value |
ATTACH_FILE | Targets, Results, Upload, Popup, Button, Excel, Spreadsheet, Template, Amp Impact | Attach Files |
EXCEL_ADDITIONAL_ROWS_ERROR | Warning, Error, Targets, Popup, Results, Upload, Excel, Spreadsheet, Template, Amp Impact | Additional rows will not be processed. Please follow the guidelines given for upload. |
INCORRECT_FILE_TYPE_UPLOADED | Error, Targets, Results, Popup, Upload, Excel, Spreadsheet, Template, Amp Impact | Incorrect file type. Only files in .xlsx format can be uploaded. |
INVALID_FILE_COLUMN | SetTargets, AddResults, Excel Upload popup, Amp Impact | The selected file has one or more invalid column headers on the results/targets tab. Please ensure that the column headers have not been changed. |
INVALID_FILE_HEADER | SetTargets, AddResults, Excel Upload popup, Amp Impact | The selected file has an invalid header on the results/target tab. Please ensure that the header has not been changed. |
NO_VALID_TAB | Error, Targets, Results, Popup, Upload, Excel, Spreadsheet, Template, Amp Impact | The selected file does not have a valid tab. |
UPLOAD_RESULTS_HEADER | Results, Upload, Popup, Header, Excel, Spreadsheet, Template, AddResults, Amp Impact | Upload Results For |
New Email Templates
IATI_XML_Generated_Not_Validated
IATI_XML_Generated_Validated_Without_Errors
IATI_XML_Validated_With_Errors
Updated Email Templates
IATI_Activity_XML_Generation_Failure
IATI_Organization_XML_Generation_Failure
Declarative Automation
API Name | Automation Type | Change |
Copy_Indicator_Field_Values_Onto_Project_Indicator | Process Builder | New fields on ampi__Indicator__c and ampi__Project_Indicator__c added |
IATI_XML_Generation | Screen Flow |
|
Schedule_Reporting_Periods | Screen Flow |
|
Permission Sets
Amp Impact Admin
Object & Field Access
Object API Name | FIeld API Name | Permissions |
ampi__Indicator__c | ampi__xx_Has_Baseline__c | Read, Edit |
ampi__Indicator__c | ampi__xx_Map_Picklist_Values_To_Numbers__c | Read, Edit |
ampi__Indicator__c | ampi__xx_Numbers_Mapped_To_Picklist_Values__c | Read, Edit |
ampi__Indicator__c | ampi__xx_Reporting_Picklist_Values__c | Read, Edit |
ampi__Project_Indicator_Reporting_Period__c | ampi__Parent_Report_Type__c | Read |
ampi__Project_Indicator__c | ampi__xx_Has_Baseline__c | Read, Edit |
ampi__Project_Indicator__c | ampi__xx_Map_Picklist_Values_To_Numbers__c | Read, Edit |
ampi__Project_Indicator__c | ampi__xx_Numbers_Mapped_To_Picklist_Values__c | Read, Edit |
ampi__Project_Indicator__c | ampi__xx_Reporting_Picklist_Values__c | Read, Edit |
ampi__Result__c | ampi__xx_Female_Picklist_Result_Numeric_Value__c | Read, Edit |
ampi__Result__c | ampi__xx_Female_Picklist_Target_Numeric_Value__c | Read, Edit |
ampi__Result__c | ampi__xx_Female_Results_Not_Applicable__c | Read, Edit |
ampi__Result__c | ampi__xx_Male_Picklist_Result_Numeric_Value__c | Read, Edit |
ampi__Result__c | ampi__xx_Male_Picklist_Target_Numeric_Value__c | Read, Edit |
ampi__Result__c | ampi__xx_Male_Results_Not_Applicable__c | Read, Edit |
ampi__Result__c | ampi__xx_Picklist_Result_Numeric_Value__c | Read, Edit |
ampi__Result__c | ampi__xx_Picklist_Target_Numeric_Value__c | Read, Edit |
ampi__Result__c | ampi__xx_Results_Not_Applicable__c | Read, Edit |
ampi__Result__c | ampi__xx_Unknown_Results_Not_Applicable__c | Read, Edit |
ampi__Result__c | ampi__xx_Unknown_Picklist_Result_Numeric_Value__c | Read, Edit |
ampi__Result__c | ampi__xx_Unknown_Picklist_Target_Numeric_Value__c | Read, Edit |
Apex Class Access
The following Apex classes have been added to the permission set:
AddResultLWC_CTRL
AddResult_Service
GenerateReportingPeriods
ProjectIndicatorGeoArea_TestHelper
ReportingPeriodFlowInput
ReportingPeriodFlowOutput
ReportingPeriod_Flow_Handler
ReportingPeriod_Flow_Warning_Handler
ReportingPeriod_TestFactory
Result
ResultRow
Result_TestHelper
STAR_Helper
SetTargetLWC_CTRL
SetTarget_Service
TargetRow
Record Type Access
Object API Name | Record Type |
ampi__Reporting_Period__c | Baseline |
ampi__Reporting_Period__c | Reporting_Period |
IATI Full Access
Object API Name | FIeld API Name | Permissions |
Account | ampi__IATI_Activity_XML_Error_Log__c | Read, Edit |
Account | ampi__IATI_Organisation_XML_Error_Log__c | Read, Edit |
Account | ampi__IATI_Validator_Error_Response__c | Read, Edit |
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.