Phoenix (v1.45) | Release Notes | Release Date: June 2025
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).
Contact support@verasolutions.org to share feedback.
This page covers:
- 1 New Features
- 1.1 Financials: Plan and Report with Greater Flexibility and Ease
- 1.1.1 Flexible Planning and Reporting Frequencies
- 1.1.2 Plan and Report Budget Line Items Across Multiple Reporting Periods
- 1.1.3 Auto-Calculation of Amounts Using Quantity and Unit Cost
- 1.1.4 Group Budget Line Items for Better Visibility
- 1.1.5 Submit Budgets for Review and Lock the Budgets for Edits
- 1.1.6 Filtering the Planning and Reporting Tables
- 1.2 Use Multiple Custom Groups to Disaggregate Project Indicators
- 1.3 Download and Upload Framework Objectives Using Excel templates
- 1.4 Behind the Scenes: Technical Stuff
- 1.5 Resolved Issues
- 1.6 Packaging changes
- 1.6.1 Updates to ampi__Budget__c
- 1.6.2 Updates to ampi__Financial__c
- 1.6.3 Updates to ampi__Indicator__c
- 1.6.4 Updates to ampi__Objective__c
- 1.6.5 Updates to ampi__Project_Indicator__c
- 1.6.6 Updates to ampi__Result__c
- 1.6.7 Updates to Custom Metadata Type ampi__Dependent_Field_Control_Setting__mdt
- 1.6.8 Updates to Custom Metadata Type ampi__Framework_Objective_Upload_Download__mdt
- 1.6.9 Custom Labels
- 1.6.10 Apex Class Access
- 1.6.11 Field Access
- 1.1 Financials: Plan and Report with Greater Flexibility and Ease
Related Pages: Upgrade Instructions
New Features
Financials: Plan and Report with Greater Flexibility and Ease
Users can now plan, track, and manage project budgets more effectively through a powerful new Financials interface. Moving beyond static, spreadsheet-based workflows, this interface enhances collaboration and improves data quality.
At the core of this experience are two Lightning Web Components (LWCs) that provide a consistent and seamless interface:
Plan Budget Lightning Web Component
Users can create budget line items, define planned amounts (either directly or by using quantity and unit cost) and submit budget plans for approval.
Report Expenditure Lightning Web Component
Users can record actual expenditures against planned line items, log unplanned expenses, and submit financial actuals for specific reporting periods.
These components are flexible to be used on other Amp Impact objects such as Budget and Reporting Period allowing for greater flexibility in managing financial workflows.
Flexible Planning and Reporting Frequencies
Users can use the Plan Budget Lightning Web Component and Report Expenditure Lightning Web Component to plan and report their budgets at different frequencies, for example they can plan their budget at an annual frequency and report it at a quarterly frequency, tailoring financial tracking to the specific needs and timelines of their programs
Plan and Report Budget Line Items Across Multiple Reporting Periods
Users can use the Plan Budget Lightning Web Component and Report Expenditure Lightning Web Component to define and track budget line items across various reporting periods at once. This offers greater flexibility in financial planning and a clearer picture of financial performance over time.
Auto-Calculation of Amounts Using Quantity and Unit Cost
Organizations can now configure budget line items to automatically calculate planned and actual amounts based on defined formulas (e.g., number of staff × salary). This is particularly useful for categories such as salaries or travel expenses.
Specific categories/subcategories (e.g., “Salaries”) can be set to always use auto-calculation, reducing manual errors and ensuring consistency.
Group Budget Line Items for Better Visibility
Finance teams can now group budget line items by key attributes such as Category or Subcategory, enabling users to toggle between high-level summaries and detailed views with expandable and collapsible groupings.
Submit Budgets for Review and Lock the Budgets for Edits
Users have the ability to Submit Budgets for internal or external review and lock them to prevent further edits once finalised. While the Planning Budget can be locked as a whole, Reporting Budgets can be locked for specific Reporting Periods.
Filtering the Planning and Reporting Tables
Users have the ability to apply filters to Planning and Reporting tables based on fields such as Type, Category and Code. This allows users to quickly locate relevant data, analyze spending patterns, and generate tailored insights—especially valuable for large budgets or multi-stakeholder projects.
Use Multiple Custom Groups to Disaggregate Project Indicators
Users can now add up to six different Disaggregation Groups while creating a Project Indicator, allowing them to break down data across multiple dimensions simultaneously.
This eliminates the need to create separate indicators for each Disaggregation Group and enables more efficient, consolidated reporting. For example, instead of creating three separate indicators to track learner progress by age, location type, and household income, users can now combine all three into a single indicator and break down the data accordingly. By allowing multiple custom groups on a single indicator, this feature streamlines data collection and analysis—saving time, reducing duplication and errors, and improving reporting clarity.
Disaggregate Indicators in 2 Different Ways
Stacked Disaggregation Type : View Totals for Each Group
When disaggregating Indicators by custom groups, users can do so in a “Stacked” manner, which displays each Disaggregation Group independently. This provides a clear summary of totals for each group—without showing how the groups intersect.
This is especially useful when users want a high-level overview of their data across multiple dimensions but don’t need to analyze combinations of those categories.
Example:
For an Indicator tracking the number of learners who improved in literacy, users can apply Disaggregation Groups such as:
Age Group (5–10 years, 11–15 years)
Location Type (Urban, Rural)
Household Income (Low, Medium, High)
With Stacked Disaggregation, users can view:
Total learners by Age Group
Total learners by Location Type
Total learners by Household Income
However, the results will not show how these groups overlap—such as how many low-income learners also live in urban areas.
Additionally, users also have the ability to cross disaggregate by sex when using Stacked Disaggregation Type
Get a Warning if the Totals across Disaggregation Groups are not Equal
While entering targets in the Set Targets Lightning Web Component or reporting results in the Add Results Lightning Web Component, the system compares aggregate values across disaggregation groups. If the totals do not align—for example, if the total number of learners by age group differs from the total by location type—a warning message will be displayed, as shown below.
Nested Disaggregation: Analyse Intersections Across Groups
Users can also choose to enter data using the “Nested” manner, which reveals how multiple Disaggregation Groups relate to one another. This hierarchical structure allows users to drill down into more detailed patterns by showing how each group nests within the previous one.
Nested Disaggregation is ideal when users want to understand the intersections between groups and uncover deeper insights into their data or if data collection is done in that manner.
Example:
Using the same literacy indicator, users can disaggregate as follows:
Age Group
Location Type
Household Income
This allows users to see:
How many 5–10-year-olds in urban areas are in each income group
How many 11–15-year-olds in rural areas are in each income group
In the given example, this would have only been possible if the organization is tracking individual learner data across all these attributes.
By using Nested Disaggregation, users gain a clearer picture of how different categories combine and influence outcomes—enabling more meaningful analysis and reporting.
We recommend disaggregating Nested Indicators with 5 custom Disaggregation Groups
Additionally users have the ability to cross disaggregate by sex when using Nested Disaggregation Type.
Users can also add/edit Targets, Baselines and Results for Project Indicators disaggregated by multiple custom groups using the Excel Download/Upload templates
Download and Upload Framework Objectives Using Excel templates
Users can now download and upload Framework Objectives through Excel, making it easier to manage their frameworks/logframes. The downloaded file includes all existing Framework Objective records and an "Instructions" tab to guide users.
Users can work on the file offline and collaborate with their team members to build their logic model/theory of change.
On uploading the file users can:
Update existing Framework Objectives
Create new Framework Objectives
Establish parent-child relationships between Framework Objectives
As with other Excel Upload/Download features in Amp Impact, the uploaded file is validated, and Success and Error logs are also created to easily identify successful uploads and any errors made during data entry.
This functionality enables offline collaboration and simplifies large-scale edits or data migration for Framework Objectives.
Behind the Scenes: Technical Stuff
We've updated the Lightning Messaging Service setup to restrict its visibility only within the package, in alignment with Salesforce Security Guidelines. This means users or implementers will not be able to access or use the packaged LWC Lightning Message Channels outside of the out-of-the-box Amp Impact functionalities.
Resolved Issues
Frameworks, Indicators, and Results Management
When 'Disable Geographic Area Hierarchy' design attribute is TRUE, Project Geographic Areas that are inactive are not displayed on the Set Targets and Add Results Lightning Web Components
In the previous version, When 'Disable Geographic Area Hierarchy' design attribute was marked TRUE, Project Geographic Areas that were marked inactive were displayed on the Geographic Area picklist on Set Targets and Add Results Lightning Web Components. This issue has now been resolved.
Duplicate result records are not created when only a comment is added to a Project Indicator before entering the result on Add Results Lightning Web Component
In the previous version, for a Project Indicator that was disaggregated by a custom group when comments were entered very quickly for one of the disaggregation values before entering a result, an additional duplicate result record was created. This issue has now been resolved.