Orion (v1.41) | Release Notes | Release Date: January 2025

Orion (v1.41) | Release Notes | Release Date: January 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:


Feature Enhancements

Customizable Display of Project Indicators in the Set Targets and Add Results Tables

Functional Documentation:

In earlier versions of Amp Impact, all Project Indicators were displayed in the Set Targets and Add Results tables, even if they weren’t relevant for target or result entry. This has been improved so that users can now control the visibility of Project Indicators in the Set Targets and Add Results tables. Using the new “Display On” (ampi__xx_Display_On__c) field, users can choose to display an indicator in the Set Targets table, the Add Results table, both, or neither. By default, Project Indicators are set to display in both tables, but this can be adjusted to keep Set Targets and Add Results tables uncluttered and improve user experience.

Lock Comments after Targets/Baselines and Results are Submitted

In earlier versions of Amp Impact, once targets, results, or baselines were submitted, users could still modify the associated comments, which posed risks of untracked changes in reporting. This has been improved with a new design attribute that allows System Administrators to lock the Comment Popups for Targets/Baselines and Results after submission, making all fields in the comment popups read-only. This enhancement provides greater control over reporting workflows and ensures that comments cannot be used for post-submission reporting.

Lock Comments.gif

Quickly Create Child Framework Objectives on the Manage Framework Lightning Web Component

Functional Documentation:

In earlier versions of Amp Impact, building framework hierarchies required multiple clicks and navigation steps, making it time-consuming for Program and M&E managers. This has been improved with a new action menu in the Manage Framework Lightning Web Component table. Users can now quickly create child framework objectives directly from the table by clicking the dropdown menu icon next to any framework objective and selecting "Add Child Objective." This streamlined process reduces clicks and simplifies the creation of hierarchical logframes, especially for larger organizations with complex frameworks.
Before

Before.gif

After

Define the sort order of Project Indicator Objectives in the manage Logframe table

Technical Documentation:

In earlier versions of Amp Impact, linked Project Indicators on the Manage Framework table followed a fixed, default sort order that could not be customized. With the introduction of a new design attribute
”Project Indicator Objective Sort Order”, System Administrators can now define the sort order of Project Indicator Objectives based on fields from the Project Indicator object. This enhancement offers greater flexibility and control over how data is presented.

Organizations can now tailor the display order of linked Project Indicators to better align with their specific needs, streamlining navigation and improving the management of framework objectives.

Adjust the width of individual columns in the Activity Chart

In earlier versions of Amp Impact, the width of columns in the Activity Chart was fixed, which made it difficult to view fields with a lot of text. This has been improved and users can now adjust the width of individual columns in the Activity Chart to fit more text. This enhancement makes it easier for users to read and manage activity data, especially when dealing with longer text entries.

Scroll Actvity.gif

Align Sorting of Activities in Implementation Plan downloaded template with the Activity Table

In earlier versions of Amp Impact, the default sorting order for Activities in the Excel sheet downloaded through the Implementation Plans Download/Upload functionality was based on the "Start Date" (ampi__Actual_Start_Date__c) field. This behavior differed from the Activity Table (Gantt Chart), which sorts Activities in ascending order by the "Earliest Start Date" (ampi__Earliest_Start_Date__c) field.

This has been improved so that the Excel sheet now also sorts Activities in ascending order by the "Earliest Start Date" (ampi__Earliest_Start_Date__c) field, aligning it with the default sorting order of the Activity Table (Gantt Chart). This enhancement ensures consistency between the two views, making it easier for users to analyze and manage activity data.

Behind the Scenes: Technical Stuff

To ensure Amp Impact’s compatibility with Salesforce’s Winter'25 release:

  1. All apex classes and triggers have been upgraded to API version 62

  2. All flows have been upgraded to API version 62

  3. All LWC and Aura components have been upgraded to API version 62

  4. Flexi pages have been upgraded to API version 62

  5. Visualforce pages have been upgraded to API version 62

This enables users to refer to the following NPC objects when:

  1. Creating an aggregated indicator

  2. Creating a Submissions template (using CreateTemplateData component.)

Objects

GiftDefaultSoftCredit

DocGenerationQueryResult

DonorGiftSummary

OutreachSourceCode

GiftTransaction

FundingAwardRqmtSection

GiftCommitment

Individual Application Task

Security fixes in Orion

We have implemented additional security checks for Read access on Field-Level Security (FLS) and Create, Read, Update, Delete (CRUD) permissions, building upon Salesforce's out-of-the-box (OOTB) security framework. These enhancements ensure that unauthorized users cannot gain read access to fields on Amp Impact Objects by requiring them to have explicit field level access defined in the security matrix. In previous releases field read permission could be inherited from object level permission.
As a result of these changes we have made changes to our permission sets. Please refer to the Packaging Changes to know more.

Resolved Issues

Frameworks, Indicators, and Results Management

Picklist values in Add New Custom Indicator modal now display in the selected language

In the previous version, the Picklist Values for fields like Datatype, Type of Result, Reporting Frequency, Target Frequency, and Geographic Area were not translated to Spanish or Portuguese on the Add New Custom Indicator popup modal. This issue has been resolved, and the Picklist Values now correctly display in the selected language (Spanish/Portuguese).

The “Update Results” button is now visible in French and Spanish

In earlier versions, the “Update Results” button was not visible on the Manage Indicators Lightning Web component when viewed in French or Spanish. This issue has been resolved to ensure that the button is displayed correctly in supported languages - French and Spanish.

Indicator Names with special characters are now displayed correctly in calculation formulas

In earlier versions, when an Indicator Definition contained special or escape characters and was used in a calculation formula, the indicator's name was not displayed correctly on the calculation formula screen. This issue has been resolved to ensure that indicator names with certain special or escape characters are displayed accurately.

“Upload Targets” button visibility corrected for “View Only Mode”

In the Nashira (v1.38) version, when the design attribute “View only mode” was set to TRUE, the “Upload Targets” button was incorrectly visible on Set Targets Lightning Web Component, allowing users to add/modify values via uploaded excel templates. This issue has been resolved, and the “Upload Targets” button is now hidden when “View Only Mode” is enabled, ensuring the expected behavior.

Users can now search by Indicator Definition even if the corresponding field is not added as a filter

In previous releases, the “Indicator Definition Translated” (ampi__Description_Translated__c) field should have been added as a filter if users wanted to search the Set Targets and Add Result tables by the Indicator Definition. Now, indicators on those tables can be searched by Indicator Definition without adding it as a filter. This saves space in the filter section and provides a better user experience.

Targets and Results Upload no longer fails when certain special characters are introduced

In earlier versions, the Results and Targets Excel template upload failed on the Add Results and Set Targets Lightning Web Components when the Project Name, Reporting Period Name, or Geographic Area Name contained special characters (&, <, >, ‘, “). This issue has been resolved to ensure that upload is successful regardless of the presence of these mentioned characters.

Activities

Implementation Plan upload no longer fails when certain special characters are introduced

In earlier versions, the Implementation Plan Excel template upload failed on the activities Lightning Web Component when the Project Name or Implementation Name contained special characters (&, <, >, ‘, “). This issue has been resolved to ensure that upload is successful regardless of the presence of these mentioned characters.

Activity Timeline Bar now resets automatically after Validation Rule errors

In earlier versions, when a validation error was triggered in the Activity timeline component, the timeline bar did not automatically revert to its original position, requiring users to manually refresh the component. This issue has been resolved to ensure when a validation rule is triggered, the timeline bar immediately resets to its original position without needing a refresh.

Financial Management

Budget upload no longer fails when certain special characters are introduced

In earlier versions, the Budget Excel template upload failed on the when the Project Name, Reporting Period Name or Budget Name contained special characters (&, <, >, ‘, “). This issue has been resolved to ensure that uploads are successful regardless of the presence of these mentioned characters.

Release Updates

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  ampi__Activity__c

Field Set Label

Field Set API Name

Change

ACTIVITY_INFO_POPOVER

ampi__ACTIVITY_INFO_POPOVER

The following fields were made available to the fieldset :

  • ampi__Activity_Information__c

  • ampi__Description__c

  • ampi__Duration__c

  • ampi__Earliest_Start_Date__c

  • ampi__Implementation_Plan__c

  • ampi__Parent_Activity__c

  • ampi__Parent_Ids__c

  • ampi__Percent_Complete__c

  • ampi__Planned_End_Date__c

  • ampi__Planned_Start_Date__c

  • ampi__Project_Implementation_Plan_Name__c

  • ampi__Project_Indicator__c

  • ampi__Project_Objective__c

  • ampi__xx_Due_Date__c

  • ampi__xx_Activity_Type__c

ACTIVITY_TABLE_COLUMNS

ampi__ACTIVITY_TABLE_COLUMNS

The following fields were made available to the field set:

  • ampi__Actual_End_Date__c

  • ampi__Actual_Start_Date__c

  • ampi__Contact__c

  • ampi__Duration__c

  • ampi__Earliest_Start_Date__c

  • ampi__Parent_Activity__c

  • ampi__Parent_Ids__c

  • ampi__Percent_Complete__c

  • ampi__Planned_End_Date__c

  • ampi__Planned_Start_Date__c

  • ampi__Project_Implementation_Plan_Name__c

  • ampi__Project_Indicator__c

  • ampi__Project_Objective__c

  • ampi__xx_Activity_Type__c

  • ampi__xx_Disbursement__c

  • ampi__xx_Due_Date__c

 

ACTIVITY_TABLE_SEARCH_FILTER

ampi__ACTIVITY_TABLE_SEARCH_FILTER

The following fields were made available to the field set:

  • ampi__Activity_Information__c

  • ampi__Contact__c

  • ampi__Description__c

  • ampi__Duration__c

  • ampi__Earliest_Start_Date__c

  • ampi__Implementation_Plan__c

  • ampi__Parent_Activity__c

  • ampi__Parent_Ids__c

  • ampi__Percent_Complete__c

  • ampi__Planned_End_Date__c

  • ampi__Project_Implementation_Plan_Name__c

  • ampi__Project_Indicator__c

  • ampi__Project_Objective__c

  • ampi__xx_Activity_Type__c

  • ampi__xx_Disbursement__c

  • ampi__xx_Due_Date__c

CREATE_EDIT_MILESTONE_POPUP

ampi__CREATE_EDIT_MILESTONE_POPUP

The following fields were made available to the field set:

  • ampi__Actual_End_Date__c

  • ampi__Actual_Start_Date__c

  • ampi__Duration__c

  • ampi__Earliest_Start_Date__c

  • ampi__Percent_Complete__c

  • ampi__Planned_End_Date__c

  • ampi__Planned_Start_Date__c

  • ampi__Project_Implementation_Plan_Name__c

  • ampi__Project_Indicator__c

  • ampi__Project_Objective__c

  • ampi__xx_Activity_Type__c

CREATE_NEW_ACTIVITY_POPUP

ampi__CREATE_NEW_ACTIVITY_POPUP

The following fields were made available to the field set:

  • ampi__Duration__c

  • ampi__Earliest_Start_Date__c

  • ampi__Parent_Ids__c

  • ampi__Planned_End_Date__c

  • ampi__Project_Implementation_Plan_Name__c

  • ampi__xx_Activity_Type__c

  • ampi__xx_Disbursement__c

  • ampi__xx_Due_Date__c

EDIT_ACTIVITY_POPUP

ampi__EDIT_ACTIVITY_POPUP

The following fields were made available to the field set:

  • ampi__Duration__c

  • ampi__Earliest_Start_Date__c

  • ampi__Implementation_Plan__c

  • ampi__Parent_Ids__c

  • ampi__Planned_End_Date__c

  • ampi__Project_Implementation_Plan_Name__c

  • ampi__xx_Activity_Type__c

  • ampi__xx_Disbursement__c

  • ampi__xx_Due_Date__c

IMPLEMENTATION_PLAN_EXCEL_COLUMNS

ampi__IMPLEMENTATION_PLAN_EXCEL_COLUMNS

The following fields were made available to the field set:

  • ampi__Implementation_Plan__c

  • ampi__Planned_Start_Date__c

  • ampi__Project_Implementation_Plan_Name__c

MILESTONE_INFO_POPOVER

ampi__MILESTONE_INFO_POPOVER

The following fields were made available to the field set:

  • ampi__Activity_Information__c

  • ampi__Actual_End_Date__c

  • ampi__Actual_Start_Date__c

  • ampi__Description__c

  • ampi__Duration__c

  • ampi__Earliest_Start_Date__c

  • ampi__Implementation_Plan__c

  • ampi__Parent_Activity__c

  • ampi__Parent_Ids__c

  • ampi__Percent_Complete__c

  • ampi__Planned_End_Date__c

  • ampi__Planned_Start_Date__c

  • ampi__Project_Implementation_Plan_Name__c

  • ampi__Project_Indicator__c

  • ampi__Project_Objective__c

  • ampi__xx_Activity_Type__c

Updates to ampi__Indicator__c

Field Set Label

Field Set API Name

Change

ADD_NEW_INDICATOR_POPUP

ampi__ADD_NEW_INDICATOR_POPUP

The following fields were made available to the field set:

  • ampi__xx_Display_On__c

CATALOG_INDICATORS_TABLE

ampi__CATALOG_INDICATORS_TABLE

The following fields were added to the fieldset:

  • ampi__xx_Display_On__c

 

INDICATOR_CATALOG_SEARCH_FILTER

ampi__INDICATOR_CATALOG_SEARCH_FILTER

The following fields were added to the fieldset :

  • ampi__xx_Display_On__c

Field Label

Field API Name

Data Type

Description

Display On

ampi__xx_Display_On__c

Picklist

The following fields are the picklist values:

  • Set Targets

  • Add Results

  • Both

  • None

Field to indicate if child Project Indicator will be displayed on Set Targets or Add Results page or Both or None

Updates to ampi__Project_Indicator__c

Field Set Label

Field Set API Name

Change

ADD_RESULTS_INFO_POPOVER

ampi__ADD_RESULTS_INFO_POPOVER

The following fields were added to the fieldset :

  • ampi__xx_Display_On__c

AR_SEARCH_FILTERS

ampi__AR_SEARCH_FILTERS

The following fields were added to the fieldset :

  • ampi__xx_Display_On__c

DEACTIVATED_PROJECT_INDICATORS_TABLE

ampi__DEACTIVATED_PROJECT_INDICATORS_TABLE

The following fields were added to the fieldset :

  • ampi__xx_Display_On__c

EDIT_PROJECT_INDICATOR_POPUP

ampi__EDIT_PROJECT_INDICATOR_POPUP

The following fields were added to the fieldset :

  • ampi__xx_Display_On__c

FIELDS_TO_COPY

ampi__FIELDS_TO_COPY

The following fields were added to the fieldset :

  • ampi__xx_Display_On__c

INDICATOR_FIELDS_ADD_RESULTS_EXCEL_TEMPL

ampi__INDICATOR_FIELDS_ADD_RESULTS_EXCEL_TEMPL

The following fields were added to the fieldset :

  • ampi__xx_Display_On__c

INDICATOR_FIELDS_SET_TARGETS_EXCEL_TEMPL

ampi__INDICATOR_FIELDS_SET_TARGETS_EXCEL_TEMPL

The following fields were added to the fieldset :

  • ampi__xx_Display_On__c

PROJECT_INDICATORS_SEARCH_FILTERS

ampi__PROJECT_INDICATORS_SEARCH_FILTERS

The following fields were added to the fieldset :

  • ampi__xx_Display_On__c

SELECTED_PROJECT_INDICATORS_TABLE

ampi__SELECTED_PROJECT_INDICATORS_TABLE

The following fields were added to the fieldset :

  • ampi__xx_Display_On__c

 

SELECT_PROJECT_INDICATORS_TO_COPY

ampi__SELECT_PROJECT_INDICATORS_TO_COPY

The following fields were added to the fieldset :

  • ampi__xx_Display_On__c

SET_TARGETS_INFO_POPOVER