Our release notes offer brief, high-level descriptions of new features, enhancements, and resolved issues. Detailed information on the features, their setup, and configuration are available in the Amp Impact Knowledge Base (specific links below).
Info |
---|
Contact support@verasolutions.org to share feedback. |
This page covers:
Table of Contents | ||
---|---|---|
|
Feature Enhancements
Enhancements to Project Indicators with Numerator/Denominator data type
Download/upload Targets and Results
Panel | ||
---|---|---|
| ||
Functional Documentation: |
Panel | ||
---|---|---|
| ||
Technical Documentation: |
In the previous release of Amp Impact (Mira, v1.37), we introduced the Numerator/Denominator data type Indicators. Users can now use Targets and Results templates to set targets and report results of Project Indicators with Numerator/Denominator data type.
<Add Images>
Indicate out-of-bounds results with validation ranges
Panel | ||
---|---|---|
| ||
Functional Documentation: |
Panel | ||
---|---|---|
| ||
Technical Documentation: |
Users can now set validation ranges for Numerator/Denominator data type Indicators to indicate if the reported results are within the expected range.
<Add Images>
Quickly gauge indicator performance with stoplights
Indicator management functionality in Amp Impact enables users to set stoplights indicating if the reported results have met targets for quantitative (number, percent, currency) Indicators. This functionality has now been extended to support Numerator/Denominator data type Indicators.
<Add Images>
View indicator performance on performance graphs
Numerator/Denominator data type Indicators are now supported on Performance Graphs.
<Add Images>
Read indicator definitions in your language with multi-language support
Panel | ||
---|---|---|
| ||
Functional Documentation: |
Panel | ||
---|---|---|
| ||
Technical Documentation: |
Multi-language capacity in Amp Impact allows organizations to enter data like Indicator definitions and descriptions in multiple languages and show that data to users across geographies in the relevant language. With Nashira (v1.38), this capability now extends to Numerator/Denominator data type Indicators.
<Add Images>
Easily refer to the calculation factor while setting targets and reporting results
Panel | ||
---|---|---|
| ||
Functional Documentation: |
Panel | ||
---|---|---|
| ||
Technical Documentation: |
Users can now refer to the calculation factor while setting targets and reporting results improving the user experience of working with Numerator/Denominator data type Indicators
<Add Images>
Show only relevant options in lookup dropdowns in Lightning components
Panel | ||
---|---|---|
| ||
Functional Documentation: |
Panel | ||
---|---|---|
| ||
Technical Documentation: |
The lookup dropdowns in Lightning components now allow system admins to specify lookup filters and display only relevant options to users. This enhances user experience by minimizing clutter, improving search efficiency, and ensuring more accurate selections.
<Add Images>
Show the relevant field as the label of lookup dropdown options in lightning components
Panel | ||
---|---|---|
| ||
Functional Documentation: |
Panel | ||
---|---|---|
| ||
Technical Documentation: |
Lookup dropdown options in Lightning components now display the relevant field as the label, providing clearer context for selections. This improves usability by making it easier for users to identify the correct option at a glance
<Add Images>
Always show updated data to users by refreshing lightning components from custom flows
Panel | ||
---|---|---|
| ||
Functional Documentation: |
Panel | ||
---|---|---|
| ||
Technical Documentation: |
Lightning components now allow system admins to automatically refresh them from custom flows and display updated data, ensuring users always see the most current information. This improves data accuracy and enhances the overall user experience by eliminating the need for manual updates.
<Add Images>
Streamline the review process by keeping the submitted lightning components unlocked for specified users
Panel | ||
---|---|---|
| ||
Functional Documentation: |
Panel | ||
---|---|---|
| ||
Technical Documentation: |
The system admins can now streamline the review process by allowing submitted Lightning components to remain unlocked for specified users based on custom permissions. This enables seamless collaboration, as designated users can make updates or changes without the need to unlock and resubmit the component.
<Add Images>
Validate the submission responses from quick actions
Panel | ||
---|---|---|
| ||
Functional Documentation: |
Panel | ||
---|---|---|
| ||
Technical Documentation: |
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.
<Add Images>
Resolved Issues
Financial Management
Load more data with budget download/upload functionality
[Confirm with Adil]
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
When a repoting period is updated to be not available for financials, it is not shown in the downloaded template anymore
[Confirm Adil]
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
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 updated criteria. This has now been resolved.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
Summary values are now displayed in the Targets Excel Upload/Download template for Percent Indicators with Calculate Total == Dont Sum Total
[Confirm with Adil]
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
Submissions
Create submissions in bulk from a template
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
Users can now submit a submission response form with multiple sections that contain conditionally displayed questions
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Submission reponse form now loads correctly for users that use languages other than English
[Confirm with Adil]
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Users can now submit a submission response form when a conditionally displayed Date type question is left blank or skipped
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 | ||||||
---|---|---|---|---|---|---|
|
Cloned submissions now follow the copied conditional display logic correctly
In earlier versions of Amp Impact, when the submission response form included conditionally displayed questions or sections, the cloned submission did not follow the same conditional display logic. This has now been fixed.
[Confirm scenario 1 with Srushti]
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
Users can now change the
milestoneMilestone due date by dragging it on the activity gantt chart
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Show custom errors to users on
activityActivity table
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
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 | ||||||
---|---|---|---|---|---|---|
|
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 |
| Aura Component |
| November 2023 |
| Visualforce Page |
| November 2023 |
| Visualforce Page |
| November 2023 |
| Aura Component |
| April 2024 |
| Aura Component |
| April 2024 |
| Visualforce Page |
| August 2024 |
| Visualforce Page |
| November 2024 |
Packaging Changes
<To be added by Anuranjani>