The Submission response form is now validated if it’s being submitted from quick actions. This ensures that correctly filled Submission response forms are submitted even if the form is submitted from a quick action or flow.
Behind the Scenes: Technical Stuff
To ensure Amp Impact’s compatibility with Salesforce’s NPC:
All apex classes and triggers have been upgraded to API version 61.0
All flows have been upgraded to API version 61.0
All LWC and Aura components have been upgraded to API version 61.0
Flexi pages have been upgraded to API version 61.0
Visualforce pages have been upgraded to API version 61.0
This enables users to refer to the following NPC objects when:
Creating an aggregated indicator
Creating a Submissions template (using CreateTemplateData component)
Resolved Issues
Financial Management
Load more data with budget download/upload functionality
The budget planning and reporting templates can now support an increased load. For more details on the record limits, navigate to the above mentioned link.
When a repoting period is updated to be not available for financials, it is not shown in the downloaded template anymore
In earlier versions of Amp Impact, when a Reporting Period that was selected as a Budget Planning Period was marked unavailable for financials, it was still displayed in the Enhanced Excel Upload/Download Template. This has now been resolved such that when a Budget Planning Period is marked as unavailable for Financials it is not displayed in the Excel Upload/Download template.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-7881 |
|---|
|
Flow labels and names have been updated to follow best practices of naming convention
The names and labels associated with the flows that update field values on the Fund object have been changed to follow best practises of naming convention. Read more about these changes in the Packaging Notes section
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-3762 |
|---|
|
Frameworks, Indicators, and Results Management
Parent objective filter now works correctly while adding objectives from the catalog
In previous versions of Amp Impact, the filtering functionality for the Parent Objective field when adding Objectives from the catalog was not working as expected. This issue has now been resolved, and users can successfully filter the table using the Parent Objective field.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-10539 |
|---|
|
Results of numerator/denominator project indicators are updated to reflect the updated calculation factor
In the previous version, editing the Calculation Factor for a Numerator/Denominator Indicator did not update the hover values correctly for updated results. This issue has been resolved, and the correct values now display while hover over the result value on Add Results LWC after editing the Calculation Factor.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-10960 |
|---|
|
If the updated aggregation criteria have no matching records, the updated results are correctly set to zero or blank
In earlier versions of Amp Impact, when the the aggregation setting filter criteria was updated such that there were no records that matched the updated filter criteria, the updated results for these indicators showed previous results instead of zero. This has now been resolved
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-8691 |
|---|
|
Packaged picklist fields now support filtering indicators in other languages
In earlier versions, filtering the Manage Indicators LWC by "Type of Results," "Geographical Disaggregation," "Calculate Total," and "Reporting Frequency" fields in Spanish and Portuguese did not display accurate results. This issue has now been resolved, and these fields can be used correctly to filter the Selected Indicators table on Manage Indicators LWC.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-11266 |
|---|
|
Project indicators with updated disaggregation groups are now displayed as options while specifying the calculation criteria
In previous versions of Amp Impact, on editing a calculated Indicator by adding a custom Disaggregation Group to it, the Indicators available for selection on the "Customize Calculation" screen did not align with the filtering logic for that picklist. This has now been resolved.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-11288 |
|---|
|
Project Indicators with deleted junction records to reporting period records are now accomodated in the targets download template
In the previous version of Amp Impact, when Project Indicator Reporting Period junction records were deleted, an error was shown on downloading the Targets Excel Upload Download template. This has been fixed such that the Targets Upload Download Excel template can be successfully downloaded with uneditable white cells displayed in the Target columns for those Project Indicators whose Project Indicator Reporting Periods have been deleted.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-10395 |
|---|
|
Correct/ Accurate values are displayed in the Total column on the Targets Upload/Download Excel template for Percent sex disaggregated indicators without refreshing the component
In the previous versions of Amp Impact, when the Target Excel Upload Download template was downloaded after entering target/baseline values, without refreshing the component, the Total column for sex disaggregated percent type indicators displayed an incorrect value. This has now been resolved such that correct values are displayed upon download without having to refresh the component.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-11190 |
|---|
|
Baseline values are now visible on Add Results LWC when Compared with Baselines when Targets are Disaggregated is set as FALSE
In the previous versions of Amp Impact, when the “Targets Are Disaggregated” field was set to FALSE, Baseline values were not displayed on the Add Results LWC component when comparing with Baseline. This has been fixed such that the value of “Targets Are Disaggregated” field does not affect the display of Baseline values on the Add Results LWC table.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-11211 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-11184 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-11194 |
|---|
|
Summary values are now displayed in the Targets Excel Upload/Download template for Percent Indicators with Calculate Total == Dont Sum Total
In the previous version of Amp Impact (Mira v.137), the Summary Values were not populated in the downloaded Targets Excel Template for Project Indicators that were of Percent data type with the Calculate Total field set to Don’t Sum total.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-10864 |
|---|
|
Target values are now visible on the Excel Upload/Download template when it is downloaded for a single Project Indicator that is cross disaggregated by sex
In the previous versions of Amp Impact, when the targets for a single Project Indicator that is cross disaggregated were downloaded, the excel file did not reflect the target values. This has now been fixed.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-10407 |
|---|
|
Baseline values are now displayed on AR LWC if Reporting Frequency and Target Frequency are different
In the previous versions of Amp Impact, when the Target Frequency was not equal to the Reporting Frequency, Baseline values were not displayed on the Add Results LWC component when comparing with Baseline. This issue has now been resolved.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-10394 |
|---|
|
Add Results LWC loads without an error when system language is set to Portugese (Brazil)
In the previous version of Amp Impact Mira (v.137), when Numerator/Denominator type Indicators existed in a Project, the Add Results LWC page was showing an error upon loading. This issue has now been fixed.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-11188 |
|---|
|
User can now select a value on the Geographic Area picklist on Set targets VF page when using the system in French, Spanish or Portugese languages
In earlier versions of Amp Impact, users were not able to select values from the Geographic Area picklist on the Set Targets Visualforce component when using the system in French, Spanish or Portugese. This issue has now been fixed.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-6652 |
|---|
|
Submissions
Create submissions in bulk from a template
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | TADD-39 |
|---|
|
Submission response records can now be created in bulk along with the relevant sections and questions copied from the template, using automation (flows).
Special characters print correctly in the downloaded submission word file
In the earlier versions of Amp Impact, when text containing special characters was pasted into Submission responses, special characters were replaced with garbage string in the downloaded word file. This issue has now been resolved such that the special characters are correctly displayed.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-3349 |
|---|
|
In previous versions of Amp Impact, the Submission Response Form was not loading when the system language was set to Spanish. This has now been resolved.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-11274 |
|---|
|
In earlier versions of Amp Impact, when a question of Date type field is conditionally displayed and left blank, it was not possible to submit the submission without refreshing the page. This has now been resolved such that the submission goes through without refreshing the page.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-11192 |
|---|
|
Cloned submissions now follow the copied conditional display logic correctly
In earlier versions of Amp Impact, when the submission template/response form included conditionally displayed questions or sections, the cloned submission did not follow the same conditional display logic. This has now been fixed.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-11213 |
|---|
|
The Last Modified by field is not updated to the user who last viewed the record anymore
In the previous version of Amp Impact, when a Submission record is opened, the ‘Last Modified by’ field was updated to the current user who was viewing the record. This has now been resolved such that , the ‘Last Modified by’ field contains the user who last edited the Submission record.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-10177 |
|---|
|
Activities
Users only see the baseline bar on the activity gantt chart when they have access to the planned start and end dates
In the previous version of Amp Impact, the baseline bar was visible to a user that did not have access to the “Planned Start Date” and “Planned End Date”. This has now been fixed such that the baseline bar is not visible on Activities LWC to a user that does not have access to those fields.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-9238 |
|---|
|
The baseline bar on the activity gantt chart now ends on the Planned End Date
In earlier versions of Amp Impact, the baseline bar on the ganntt chart ended one day prior to the Planned Start Date when the ganntt chart was viewed by month. This issue has now been fixed and the baseline bar ends on the same day as the Planned End Date.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-9264 |
|---|
|
Users can now change the Milestone due date by dragging it on the activity gantt chart
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-8041 |
|---|
|
Show custom errors to users on Activity table
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | TADD-65 |
|---|
|
Cross Cutting Features
Components/Data Tables are automatically refreshed to locked state after they are submitted via Submit Project wizard
In the previous version of Amp Impact (Mira v1.37), after locking data tables through the Submit and Lock Wizard, they had to be manually refreshed for them to be displayed in a locked/view only manner. This has now been resolved such that users do not need to manually refresh them.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 545235eb-e646-375e-aef3-a3145584fd91 |
|---|
| key | INDMP-10846 |
|---|
|
Release Updates
| Note |
|---|
Vera Solutions will no longer enhance or resolve any issues for the following components after the component’s end-of-servicing date. Why: We are focusing development efforts on optimizing the corresponding Lightning Web Components that offer better performance and experience, and introducing new features. How: Before a component’s end-of-servicing date, you must migrate to the corresponding Lightning Web Components to ensure you continue receiving regular updates and enhancements to those features. |
Name | Type of Component | Corresponding LWC | End of Servicing Date |
ActivityChart | Aura Component | activities | November 2023 |
AddResults | Visualforce Page | addResults | November 2023 |
ManageLogFrames | Visualforce Page | manageLogFrames | November 2023 |
BudgetExcelDownload
(Quick Action: Download) | Aura Component | Budget Download
(Quick Action: Download Budget) | April 2024 |
BudgetExcelUpload
(Quick Action: Upload) | Aura Component | Budget Upload
(Quick Action: Upload Budget) | April 2024 |
ManageIndicators | Visualforce Page | manageIndicators | August 2024 |
SetTargets | Visualforce Page | setTargets | November 2024 |
Packaging Changes
Updates to Financial Object
| Expand |
|---|
| title | The following Validation Rule is updated |
|---|
|
Rule Name | Field API Name | Change |
|---|
Is Budget Locked | Is_Budget_Locked | The logic of validation rule has been updated to show an error if user does not have have access to the Custom Permission “Override Locked Budget” and Budget is locked. |
|
Updates to ampi__Indicator__c
| Expand |
|---|
|
Field Label | Field API Name | Data Type |
|---|
Denominator Definition Language 1 | ampi__xx_Denominator_Definition_Language_1__c | TextArea (255) | Denominator Definition Language 2 | ampi__xx_Denominator_Definition_Language_2__c | TextArea (255) | Denominator Definition Language 3 | ampi__xx_Denominator_Definition_Language_3__c | TextArea (255) | Denominator Definition Translated | ampi__xx_Denominator_Definition_Translated__c | Formula (Text) | Number of Decimals for Resultant Value | ampi__xx_Number_of_Decimals_for_Resultant__c | Picklist | Numerator Definition Language 1 | ampi__xx_Numerator_Definition_Language_1__c | TextArea (255) | Numerator Definition Language 2 | ampi__xx_Numerator_Definition_Language_2__c | TextArea (255) | Numerator Definition Language 3 | ampi__x_Numerator_Definition_Language_3__c | TextArea (255) | Numerator Definition Translated | ampi__xx_Numerator_Definition_Translated__c | Formula (Text) | Validation Range Maximum Denominator | ampi__xx_Validation_Range_Maximum_Denominator__c | Number (16,2) | Validation Range Maximum Numerator | ampi__xx_Validation_Range_Maximum_Numerator__c | Number (16,2) | Validation Range Minimum Denominator | ampi__xx_Validation_Range_Minimum_Denominator__c | Number (16,2) | Validation Range Minimum Numerator | ampi__xx_Validation_Range_Maximum_Denominator__c | Number (16,2) |
|
| Expand |
|---|
|
Field Set Label | Field Set API Name | Change |
|---|
Add New Indicator Popup | ampi__ADD_NEW_INDICATOR_POPUP | The following fields were added to the field set: ampi__xx_Denominator_Definition_Language_1__c ampi__xx_Denominator_Definition_Language_2__c ampi__xx_Denominator_Definition_Language_3__c ampi__xx_Denominator_Definition_Translated__c ampi__xx_Number_of_Decimals_for_Resultant__c ampi__xx_Validation_Range_Maximum_Denominator__c ampi__xx_Validation_Range_Maximum_Numerator__c ampi__xx_Validation_Range_Minimum_Denominator__c ampi__xx_Validation_Range_Minimum_Numerator__c ampi__xx_Numerator_Definition_Language_1__c ampi__xx_Numerator_Definition_Language_2__c ampi__xx_Numerator_Definition_Language_3__c ampi__xx_Numerator_Definition_Translated__c
|
|
Updates to ampi__Project_Indicator__c
| Expand |
|---|
|
Field Label | Field API Name | Data Type |
|---|
Denominator Definition Language 1 | ampi__xx_Denominator_Definition_Language_1__c | TextArea (255) | Denominator Definition Language 2 | ampi__xx_Denominator_Definition_Language_2__c | TextArea (255) | Denominator Definition Language 3 | ampi__xx_Denominator_Definition_Language_3__c | TextArea (255) | Denominator Definition Translated | ampi__xx_Denominator_Definition_Translated__c | Formula (Text) | Number of Decimals for Resultant Value | ampi__xx_Number_of_Decimals_for_Resultant__c | Picklist | Numerator Definition Language 1 | ampi__xx_Numerator_Definition_Language_1__c | TextArea (255) | Numerator Definition Language 2 | ampi__xx_Numerator_Definition_Language_2__c | TextArea (255) | Numerator Definition Language 3 | ampi__x_Numerator_Definition_Language_3__c | TextArea (255) | Numerator Definition Translated | ampi__xx_Numerator_Definition_Translated__c | Formula (Text) | Validation Range Maximum Denominator | ampi__xx_Validation_Range_Maximum_Denominator__c | Number (16,2) | Validation Range Maximum Numerator | ampi__xx_Validation_Range_Maximum_Numerator__c | Number (16,2) | Validation Range Minimum Denominator | ampi__xx_Validation_Range_Minimum_Denominator__c | Number (16,2) | Validation Range Minimum Numerator | ampi__xx_Validation_Range_Maximum_Denominator__c | Number (16,2) |
|
| Expand |
|---|
|
Field Set Label | Field Set API Name | Description |
|---|
INDICATOR_FIELDS ADD_RESULTS EXCEL_TEMPLATE | ampi__INDICATOR_FIELDS_ADD_RESULTS_EXCEL_TEMPL | This fieldset controls the display of Indicator attribute fields on the Results Upload Download Excel Template | INDICATOR_FIELDS SET _TARGETS_EXCEL _TEMPLATE | ampi__INDICATOR_FIELDS_SET_TARGETS_EXCEL_TEMPL | This fieldset controls the display of Indicator attribute fields on the Targets Upload Download Excel Template |
|
| Expand |
|---|
|
Field Set Label | Field Set API Name | Change |
|---|
ADD RESULTS INFO POPOVER | ADD_RESULTS_INFO_POPOVER | The position of the fields have been changed: ampi__xx_Denominator_Definition__c ampi__xx_Numerator_Definition__c ampi__xx_Calculation_Factor__c
| EDIT PROJECT INDICATOR POPUP | EDIT_PROJECT_INDICATOR_POPUP | The following newly added fields were made available to the fieldset: ampi__xx_Denominator_Definition_Language_1__c ampi__xx_Denominator_Definition_Language_2__c ampi__xx_Denominator_Definition_Language_3__c ampi__xx_Denominator_Definition_Translated__c ampi__xx_Number_of_Decimals_for_Resultant__c ampi__xx_Numerator_Definition_Language_1__c ampi__xx_Numerator_Definition_Language_2__c ampi__xx_Numerator_Definition_Language_3__c ampi__xx_Numerator_Definition_Translated__c
The following newly added fields are displayed out of the box if the fieldset: ampi__xx_Validation_Range_Minimum_Numerator__c ampi__xx_Validation_Range_Maximum_Numerator__c ampi__xx_Validation_Range_Minimum_Denominator__c ampi__xx_Validation_Range_Maximum_Denominator__c
| FIELDS TO COPY | FIELDS_TO_COPY | The following newly added fields were made available to the fielset: ampi__xx_Denominator_Definition_Language_1__c ampi__xx_Denominator_Definition_Language_2__c ampi__xx_Denominator_Definition_Language_3__c ampi__xx_Denominator_Definition_Translated__c ampi__xx_Number_of_Decimals_for_Resultant__c ampi__xx_Numerator_Definition_Language_1__c ampi__xx_Numerator_Definition_Language_2__c ampi__xx_Numerator_Definition_Language_3__c ampi__xx_Numerator_Definition_Translated__c
|
|
| Expand |
|---|
|
ampi__xx_Number_of_Decimals_for_Resultant__c field was added to the Page layout |
| Expand |
|---|
|
Label | API Name | Change |
|---|
Object Lookup Label Mapping | ampi__Object_Lookup_Label_Mapping__mdt | Description was changed to:
”Custom metadata type to define the label and filter which record field is displayed in a lookup field's dropdown on Amp's Visualforce interfaces. If this is not defined for any lookup field, Name will display by default in the dropdown.” |
|
| Expand |
|---|
|
Label | API Name | Description |
|---|
Lookup Filter Label Mapping | ampi__xx_Lookup_Filter_Label_Mapping__mdt | This custom metadata helps specify the lookup filters and alternate fields to be displayed in lookup dropdowns on lightning components or downloaded templates |
|
| Expand |
|---|
|
Field Label | Field API Name | Data Type |
|---|
Active? | ampi__xx_Active__c | Checkbox | Child Object | ampi__xx_Child_Object__c | Text | Filter Condition | ampi__xx_Filter_Condition__c | LongTextArea | Parent Field Label | ampi__xx_Parent_Field_Label__c | Text | Parent Object | ampi__xx_Parent_Object__c | Text | Related Lookup | ampi__xx_Related_Lookup__c | Text | Source Component | ampi__xx_Source_Component__c | Picklist |
|
| Expand |
|---|
|
The following records are added: Label |
|---|
Activity on Financial Plan DL Excel | Activity on Financial Report DL Excel | Budget on Financial Report DL Excel | FO on IP DL Excel | Parent Activity on IP DL Excel | PI on IP DL Excel |
|
| Expand |
|---|
|
New Page Layout “xx_Lookup_Filter_Mapping Layout” Added |
| Expand |
|---|
|
The following records have been updated Label |
|---|
NumDen Add Indicator Popup | NumDen Edit Indicator Popup |
|
| Expand |
|---|
|
Label |
|---|
NumDen Add Indicator Popup Valid Range | NumDen Edit Indicator Popup Valid Range |
|
Declarative Automation
| Expand |
|---|
|
Flow Label | Flow API Name | Description |
|---|
| | | | | | | | | | | | | | | | | | | | | | | | | | |
|
New Custom Permissions
| Expand |
|---|
| title | New Custom Permissions |
|---|
|
Label | API_Name | Description | Override Locked Baseline | Override_Locked_Baseline | Grants an exception to the "Results Locked" field specifically for Baseline. Assigned users will have the ability to edit the Baseline column within SetTargets LWC despite "Results Locked" field on the Baseline (Reporting Period) record being set to TRUE. | Override Locked Budget | Override_Locked_Budget | Grants an exception to the "Budget Locked" setting. Assigned users will have unrestricted access to manage budgets through the Budget Setup LWC, including uploading templates, even if the Budget Locked field on the Budget object is set to TRUE. | Override Locked Framework | Override_Locked_Framework | Grants an exception to the "Framework Locked" setting. Assigned users will have access to manage frameworks through ManageFrameworks LWC regardless of the Framework Locked field on either the Framework object itself or the Project object. | Override Locked Implementation Plan | Override_Locked_Implementation_Plan | Grants an exception to the "Implementation Plan Locked" setting. Assigned users will have full access to manage activities within the Activities LWC even if the Implementation Plan Locked field on the Implementation Plan object is set to TRUE. | Override Locked Indicators | Override_Locked_Indicators | Grants an exception to the "Indicators Locked" setting. Assigned users will have full access to manage indicators within Manage Indicators LWC even if the. Indicators Locked field on the Project object is set to TRUE. | Override Locked Results | Override_Locked_Results | Grants an exception to the "Results Locked" setting. Assigned users will have the ability to edit Results for the corresponding period within AddResults LWC even if the Results Locked field on the Reporting Period object is set to TRUE. | Override Locked Submissions | Override_Locked_Submissions | Grants an exception to the "Response Locked" setting. Assigned users will have access to edit responses within the Submission Response Form even if the Response Locked field on the Submission object is set to TRUE. |
|
New Custom Labels
| Expand |
|---|
|
Name | Categories | Short Description | Value |
|---|
CF_FOR_BASELINE | SetTargets, Baseline, Table, Amp Impact | Show Calculation Factor on Baseline | Baseline is shown per | CMDT_FILTER_ERROR | ManageIndicators, ManageFramework, Activty, Amp Impact | Controls the error message on CMDT filter on LWC | There seems to be an issue with one or more of your filter criteria. Please contact your System Administrator for further assistance. | UPLOAD_LIMIT_BUDGET | Do Not Translate, Amp Impact, Budget, Budget Excel Upload, Data Table, Upload Limit | Number of financial records uploaded by budget upload in one go | 200 | INVALID_FILE_PROJECT_INDICATOR | Excel Upload popup, Amp Impact | INVALID_FILE_PROJECT_INDICATOR | The selected file has an invalid Indicator information for uploading. Please ensure that the correct indicators are uploaded | NO_RECORDS_FOUND_PERFORMANCE_GRAPH | PerformanceGraphs, Amp Impact< | NO_RECORDS_FOUND_FOR_PERFORMANCE_GRAPH | You must create at least one compatible Project Indicator (Number/Currency/Numerator-Denominator with any disaggregation, or Percent with no disaggregation) and one compatible Reporting Period for this Project. | Per | STAR, Calculation Factor, Amp Impact | Show numerator/denominator calculation per calculation factor | per | PREPARE_EXCEL_FOR_UPLOAD_1_NUMDENM | Numerator/Denominator, SetTargets, AddResults, Excel Download, Excel File, Amp Impact | PREPARE_EXCEL_FOR_UPLOAD_1_NUMDENM | The Result value for Numerator/Denominator is based on this formula - (Numerator/Denominator) * Calculation Factor | PREPARE_EXCEL_FOR_UPLOAD_6_EXCEL | SetTargets, AddResults, Excel Download, Excel File, Amp Impact | PREPARE_EXCEL_FOR_UPLOAD_5 | Do not edit the following: | PREPARE_EXCEL_FOR_UPLOAD_A1 | AddResults, Excel Download, Excel File, Amp Impact | PREPARE_EXCEL_FOR_UPLOAD_A | Do not enter data in white cells. These will not be uploaded. | CF_FOR_TARGET | SetTargets, Table, Amp Impact | Show Calculation Factor on Targets table | Targets are shown per | CF_FOR_RESULTS | AddResults, Table, Amp Impact | Show Calculation Factor on Result table | Targets, Results & Baseline are shown per |
|
Updated Custom Labels
| Expand |
|---|
|
Name | Categories | Change |
|---|
REVIEW_SUBMISSIONS_ERROR_MESSAGE | Submit and Lock Wizard, Amp Impact | Protected Before: “True”
Protected After: “False” | PREPARE_EXCEL_FOR_UPLOAD_1A | SetTargets, AddResults, Excel Download, Excel File, Amp Impact | Value Before: from "2. If you choose to download both Targets and Results from the Results data entry page, Targets cannot be uploaded using the Results data entry page.”
Value After: to “If you choose to download both Targets and Results from the Results data entry page, Targets cannot be uploaded using the Results data entry page." | PREPARE_EXCEL_FOR_UPLOAD_3 | SetTargets, AddResults, Excel Download, Excel File, Amp Impact | Value Before: from "3. Match the data in the input cell(s) to the Project Indicator’s data type (e.g. no text entered for a number indicator)"
Value After:to "Match the data in the input cell(s) to the Project Indicator’s data type (e.g. no text entered for a number indicator)" | PREPARE_EXCEL_FOR_UPLOAD_3B | SetTargets, AddResults, Excel Download, Excel File, Amp Impact | Value Before: from “b. To mark a result as not applicable, replace the contents of the corresponding "Not Applicable?" column cell with”
Value Ater: to “b. For Numerator-Denominator type Result, do not enter 0 as the denominator value. This will result in an error on upload.” | PREPARE_EXCEL_FOR_UPLOAD_4 | SetTargets, AddResults, Excel Download, Excel File, Amp Impact | Value Before: from “4. Do not add any new rows (e.g. adding a new Disaggregation Value to the Excel)”
Value After: to “To mark a result as not applicable, replace the contents of the corresponding "Not Applicable?" column cell with” | PREPARE_EXCEL_FOR_UPLOAD_5 | SetTargets, AddResults, Excel Download, Excel File, Amp Impact | Value Before: from “5. Do not edit the following:”
Value After: to “Do not add any new rows (e.g. adding a new Disaggregation Value to the Excel)” | PREPARE_EXCEL_FOR_UPLOAD_6 | SetTargets, AddResults, Excel Download, Excel File, Amp Impact | Value Before: from “6. Ensure that there is only one tab from which data is uploaded. You can add new tabs to your Excel, but in order to successfully upload, the tab with data to be uploaded must be named according to the Project, Reporting Period, and Geographic Area that you have open in Amp.”
Value After: to “Ensure that there is only one tab from which data is uploaded. You can add new tabs to your Excel, but in order to successfully upload, the tab with data to be uploaded must be named according to the Project, Reporting Period, and Geographic Area that you have open in Amp.” | PREPARE_EXCEL_FOR_UPLOAD_7 | | Value Before: from "7. Check that numeric data has been entered in either the format according to your user locale (if your system preferences have been customized) or the default Excel format (i.e. periods used as decimal points and no thousands separator displayed)."
Value After: to “Check that numeric data has been entered in either the format according to your user locale (if your system preferences have been customized) or the default Excel format (i.e. periods used as decimal points and no thousands separator displayed)." | SUBMIT_RESPONSE_ERROR_MESSAGE | Submissions, Interface, Amp Impact | Protected Before: “True”
Protected After: “False” | UNDERSTANDING_THE_DOWNLOADED_EXCEL_B | SetTargets, AddResults, Excel Download, Excel file, Amp Impact | Value Before: from "2. All columns to the left of the "Indicator" column contain information about the Project Indicator which is displayed when you hover on the "Info" icon on the data entry pages."
Value After: to "2. All columns to the left of the "Disaggregation" column contain information about the Project Indicator." | UNDERSTANDING_THE_DOWNLOADED_EXCEL_C | SetTargets, AddResults, Excel Download, Excel file, Amp Impact | Value Before: from "3. All columns to the right of the "Indicator" column contain data already reported for the Project Indicator."
Value After: to "3. All columns to the right of the "Disaggregation" column contain data already reported for the Project Indicator.” | UNDERSTANDING_THE_DOWNLOADED_EXCEL_D | SetTargets, AddResults, Excel Download, Excel file, Amp Impact | Value Before: from "4. Optional: To view numeric (Currency, Number, and Percent) targets and results in the number format according to User Locale rather than the default number format in Excel, the Number format in your computer system will need to be customized prior to the download."
Value After: to “4. Optional: To view numeric (Currency, Number, Percent, and Numerator/Denominator) targets and results in the number format according to User Locale rather than the default number format in Excel, the Number format in your computer system will need to be customized prior to the download." |
|
New Design Attribute
| Expand |
|---|
|
Label | Page | Help text | Default Value | | | | | | | | |
|
Updated Design Attribute
Apex Class Access
The following Apex classes have been added to the permission set:
FinancialRecordsExcelUpload_LWC_Test
LookupFilterMapping_Domain
LookupFilterMapping_Domain_Test
LookupFilterService
Submission_Validation_Test
Field Access
The following Fields Permission have been added to the permission set:
Indicator__c.xx_Denominator_Definition_Language_1__c
Indicator__c.xx_Denominator_Definition_Language_2__c
Indicator__c.xx_Denominator_Definition_Language_3__c
Indicator__c.xx_Denominator_Definition_Translated__c
Indicator__c.xx_Number_of_Decimals_for_Resultant__c
Indicator__c.xx_Numerator_Definition_Language_1__c
Indicator__c.xx_Numerator_Definition_Language_2__c
Indicator__c.xx_Numerator_Definition_Language_3__c
Indicator__c.xx_Validation_Range_Maximum_Denominator__c
Indicator__c.xx_Validation_Range_Maximum_Numerator__c
Indicator__c.xx_Validation_Range_Minimum_Denominator__c
Indicator__c.xx_Validation_Range_Minimum_Numerator__c
Project_Indicator__c.xx_Denominator_Definition_Language_1__c
Project_Indicator__c.xx_Denominator_Definition_Language_2__c
Project_Indicator__c.xx_Denominator_Definition_Language_3__c
Project_Indicator__c.xx_Denominator_Definition_Translated__c
Project_Indicator__c.xx_Number_of_Decimals_for_Resultant__c
Project_Indicator__c.xx_Numerator_Definition_Language_1__c
Project_Indicator__c.xx_Numerator_Definition_Language_2__c
Project_Indicator__c.xx_Numerator_Definition_Language_3__c
Project_Indicator__c.xx_Validation_Range_Maximum_Denominator__c
Project_Indicator__c.xx_Validation_Range_Maximum_Numerator__c
Project_Indicator__c.xx_Validation_Range_Minimum_Denominator__c
Project_Indicator__c.xx_Validation_Range_Minimum_Numerator__c
