Phoenix (v1.45) | Release Notes | Release Date: June 2025

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:

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

image-20250625-061832.png
Setting Up a Budget for Planning and Reporting
image-20250718-101408.png
Plan Budget Interface for Annual Planning Periods
Report Expenditure Interface for Quarterly Reporting Periods

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.

Plan Budget LWC Component: Line item Salaries planned annually across multiple planning periods
Report Expenditure LWC Component: Line item Salaries reported quarterly across multiple reporting periods within an annual planning range

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.

PlanBudget.gif
# Person(s) x Cost Per Person = Total Cost

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.

Financial Line Items Grouped by Categories

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.

IndicatorMD-Creation.gif
Create Project Indicators that can be disaggregated by multiple custom groups

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)

stacked.gif
Setting targets for a Project Indicator that is disaggregated in a stacked manner

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

stackedCD.gif
Adding results for a Project Indicator that is disaggregated by custom groups in a stacked manner and is cross disaggregated by sex

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.

image-20250627-094201.png
Warning Message displayed while entering results for a Project Indicator that is disaggregated in a stacked manner and has unequal total Result values across Disaggregation Groups

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.

Setting Disaggregation Type as Nested while creating a Project Indicator

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.

nested.non-cd.gif
Adding results for a Project Indicator that is disaggregated by multiple groups in a nested manner

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.

nestedMD.gif
Setting Targets for a Project Indicator that is disaggregated by multiple groups in a nested manner and is cross disaggregated by sex

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.

Download and Upload Framework Objectives via an Excel template

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.

Packaging changes

Updates to ampi__Budget__c

Field Label

Field API Name

Data Type

Field Label

Field API Name

Data Type

Budget Available

ampi__xx_Budget_Available__c

Currency(18, 0)

Budget Planning Period(s) Language 1

ampi__xx_Budget_Planning_Periods_Language_1__c

Long Text Area(32768)

Budget Planning Period(s) Language 2

ampi__xx_Budget_Planning_Periods_Language_2__c

Long Text Area(32768)

Budget Planning Period(s) Language 3

ampi__xx_Budget_Planning_Periods_Language_3__c

Long Text Area(32768)

Budget Reporting Period(s) Language 1

xx_Budget_Reporting_Periods_Language_1__c

Long Text Area(32768)

Budget Reporting Period(s) Language 2

xx_Budget_Reporting_Periods_Language_2__c

Long Text Area(32768)

Budget Reporting Period(s) Language 3

xx_Budget_Reporting_Periods_Language_3__c

Long Text Area(32768)

Budget Sort Order

ampi__xx_Budget_Sort_Order__c

Text(255)

Budget Version Number Language 1

ampi__xx_Budget_Version_Number_Language_1__c

Text(255)

Budget Version Number Language 2

ampi__xx_Budget_Version_Number_Language_2__c

Text(255)

Budget Version Number Language 3

ampi__xx_Budget_Version_Number_Language_3__c

Text(255)

Budget Version Number Translated

ampi__xx_Budget_Version_Number_Translated__c

Formula (Text)

Deactivate Budget

ampi__xx_Deactivate_Budget__c

Checkbox

Default Planning Periods

ampi__xx_Default_Planning_Periods__c

Text(255)

Default Reporting Periods

ampi__xx_Default_Reporting_Periods__c

Text(255)

Description Language 1

ampi__xx_Description_Language_1__c

Long Text Area(32768)

Description Language 2

ampi__xx_Description_Language_2__c

Long Text Area(32768)

Description Language 3

ampi__xx_Description_Language_3__c

Long Text Area(32768)

Field Set Label

Field Set API Name

Change

Field Set Label

Field Set API Name

Change

BUDGET_SETUP

ampi__BUDGET_SETUP

The following newly added fields were made available to the fieldset:

  1. Budget_Version_Number__c

  2. xx_Budget_Available__c

  3. xx_Budget_Planning_Period_s__c

  4. xx_Budget_Planning_Periods_Language_1__c

  5. xx_Budget_Planning_Periods_Language_2__c

  6. xx_Budget_Planning_Periods_Language_3__c

  7. xx_Budget_Reporting_Period_s__c

  8. xx_Budget_Reporting_Periods_Language_1__c

  9. xx_Budget_Reporting_Periods_Language_2__c

  10. xx_Budget_Reporting_Periods_Language_3__c

  11. xx_Budget_Sort_Order__c

  12. xx_Budget_Version_Number_Language_1__c

  13. xx_Budget_Version_Number_Language_2__c

  14. xx_Budget_Version_Number_Language_3__c

  15. xx_Budget_Version_Number_Translated__c

  16. xx_Deactivate_Budget__c

  17. xx_Default_Planning_Periods__c

  18. xx_Default_Reporting_Periods__c

  19. xx_Description_Language_1__c

  20. xx_Description_Language_2__c

  21. xx_Description_Language_3__c

ampi__xx_Budget_Available__c field was added to the Page layout

Updates to ampi__Financial__c

Field Label

Field API Name

Data Type

Field Label

Field API Name

Data Type

Actual Cost per Unit

ampi__Actual_Cost_per_Unit__c

Currency(16, 2)

Actual Quantity

ampi__Actual_Quantity__c

Number(16, 2)

Code Language 1

ampi__xx_IATI_Code_Language_1__c

Text(255)

Code Language 2

ampi__xx_IATI_Code_Language_2__c

Text(255)

Code Language 3

ampi__xx_IATI_Code_Language_3__c

Text(255)

Code Translated

ampi__xx_IATI_Code_Translated__c

Formula (Text)

Comments

ampi__xx_Comments__c

 

Text Area(255)

Deactivate Budget Line Item

ampi__xx_Deactivate_Budget_Line_Item__c

Checkbox

Description Language 1

ampi__xx_Description_Language_1__c

 

Text Area(255)

Description Language 2

ampi__xx_Description_Language_2__c

 

Text Area(255)

Description Language 3

ampi__xx_Description_Language_3__c

 

Text Area(255)

Description Translated

ampi__xx_Description_Translated__c

 

Formula (Text)

FTE %

ampi__FTE_Percent__c

Percent(3, 2)

Internal Code Language 1

ampi__xx_Internal_Code_Language_1__c

 

Text(255)

Internal Code Language 2

ampi__xx_Internal_Code_Language_2__c

 

Text(255)

Internal Code Language 3

ampi__xx_Internal_Code_Language_3__c

 

Text(255)

Internal Code Translated

ampi__xx_Internal_Code_Translated__c

Formula (Text)

Planned Cost per Unit

ampi__Cost_per_Unit__c

Currency(16, 2)

Planned Quantity

ampi__Quantity__c

Number(16, 2)

Unit Language 1

ampi__xx_Unit_Language_1__c

Text(255)

Unit Language 2

ampi__xx_Unit_Language_2__c

Text(255)

Unit Language 3

ampi__xx_Unit_Language_3__c

Text(255)

Unit Translated

ampi__xx_Unit_Translated__c

Formula (Text)

Field Label

Field API Name

Change(s)

Planned Cost per Unit

 

ampi__Cost_per_Unit__c

  1. Descriptions was changed from “Currency field to capture the cost per unit in a financial record." to “Currency field to capture the planned cost per unit in a financial record."

  2. Label was changed from “Cost_per_Unit__c" to “Planned Cost per Unit"

Planned Quantity

ampi__Quantity__c

  1. Description was changed from “Number field to capture the quantity value for a financial line item if the record involves some number of units.“ to “Number field to capture the planned quantity value for a financial line item if the record involves some number of units.“.

  2. Label was changed from “Quantity“ to “Planned Quantity“.

Field Set Label

Field Set API Name

Description

Field Set Label

Field Set API Name

Description

Reporting Excel Attribute Columns

ampi__REPORT_EXCEL_ATTRIBUTE_COLUMNS

This fieldset controls the first set of columns in the Budget Reporting file.

Planning Excel Attribute Columns

ampi__PLAN_EXCEL_ATTRIBUTE_COLUMNS

This fieldset controls the first set of columns in the Budget Planning file.

Plan Budget Search Filters

ampi__PB_SEARCH_FILTERS

This field set controls which fields on Financial__c can be used to filter on the Plan Budget Page

Report Expenditure Search Filters

ampi__RE_SEARCH_FILTERS

This field set controls which fields on Financial__c can be used to filter on the Report Expenditure Page

Planning Table Columns

ampi__PLANNING_TABLE_COLUMNS

This field set controls the columns that are displayed before the Total column on the Plan Budget page

Reporting Table Columns

ampi__REPORTING_TABLE_COLUMNS

This field set controls the columns that are displayed before the Total column on the Report Expenditure page

Plan Edit Budget Line Item Popup

ampi__EDIT_BLI_POPUP_PLAN_BUDGET

This field set controls which fields are visible to users in the Edit Budget Line Item Pop-up on the Plan Budget page.

Report Edit Budget Line Item Popup

ampi__EDIT_BLI_POPUP_REPORT_EXPENDITURE

This field set controls which fields are visible to users in the Edit Budget Line Item Pop-up on the Report Expenditure page.

Create Budget Line Item Popup

ampi__CREATE_BUDGET_LINE_ITEM_POPUP

This field set controls which fields are visible to users in the Budget Line Item See More Pop-up on the Plan Budget and Report Expenditure page.

Plan Budget See More Popup

ampi__PLAN_BUDGET_SEE_MORE_POPUP

This field set controls which fields are visible to users in the Budget Line Item See More Pop-up on the Plan Budget page.

Report Expenditure See More Popup

ampi__REPORT_EXPENDITURE_SEE_MORE_POPUP

This field set controls which fields are visible to users in the Budget Line Item See More Pop-up on the Report Expenditure page.

Field Set Label

Field Set API Name

Change

Field Set Label

Field Set API Name

Change

Budget Planning Period

BUDGETPLANNING_PERIODIC_COLUMNS

The following newly added fields were made available to the fieldset:

  1. xx_Comments__c

  2. FTE_Percent__c