Page Comparison

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).

This page covers:

Feature Enhancements

Dynamically display fields based on the context in the “Add Indicator” & “Edit Indicator” popup on manageIndicators LWC

This enhancement makes navigating the Add and Edit Indicator pop-ups more intuitive. Input fields are now conditionally displayed based on the values of certain other fields such as “Data Type”. For example, the Reporting Currency field is conditionally displayed only when the Data Type is selected as Currency.

Organizations can choose to set this enhancement on or off, ensuring adaptability to specific use cases. They can also set their own dynamic conditions for custom fields, tailoring the Manage Indicators LWC to meet unique organizational needs.

Configure comment popup to capture relevant information along with targets on setTargets LWC & results on addResults LWC

This enhancement enables users to add relevant context when setting Targets or reporting Results on the setTargets LWC and addResults LWC components respectively.

The comment popups are now controlled via field-sets giving organizations the ability to add custom fields like rich text to facilitate the inclusion of longer comments and content such as images and links.

The comment pop-up also provides the flexibility to display fields conditionally. Visibility of specific fields can be controlled based on predefined conditions, ensuring only relevant information is presented.

Show only relevant options in the related Submission dropdown on the SubmissionResposneForm component

This enhancement makes navigating and filtering Submissions easier. It allows for filtering the Submissions options presented in the dropdown on the SubmissionResponseForm page using a response value of a field on Submissions.

This ensures that only relevant submissions for completing the Application Review are presented.

View weekly sub-columns in the Gantt chart on the activities LWC

Users can now track Activities on a weekly timeline on the Activity Gantt Chart:

1. Weekly Sub-Columns in Monthly View: Users can now view weekly sub-columns under the monthly view of the Activity Gantt Chart. This addition provides a more detailed perspective, allowing for in-depth tracking of project progress on a weekly basis within the broader monthly context

   

2. Daily Sub-Columns in Weekly View: Users can also view daily sub-columns within the weekly view of the Activity Gantt Chart. This granular level of detail empowers users to closely monitor project advancements on a day-to-day basis within the weekly timeframe.

   

Improved data load capacity on setTargets LWC

The setTargets Lightning Web Component (LWC) can now load up to 7x records of it’s previous capacity.
This enhanced capacity is achieved by fetching and loading data in chunks, resulting in faster performance for search and filters on setTargets LWC.

However, if organizations have a large data set, (more than 800 result records) the initial load time for the page would be higher.

Filter Reporting Period columns on setTargets LWC

This enhancement empowers users to filter reporting period columns by specifying a date range on setTargets Lightning Web Component (LWC). This enhancement allows users to easily navigate the setTargets table especially if they have quite a lot of reporting periods for setting targets (e.g. if they set monthly targets on a 5-year-long project, resulting in 60 reporting periods).

Compatibility with latest Salesforce Non Profit Cloud objects

The Salesforce Non Profit Cloud (NPC) includes features for nonprofit organizations to manage Programs and Cases. The Libertas version of Amp Impact includes several updates to ensure compatibility with Salesforce’s NPC. The Libertas (v1.36) release enables users to refer to the following NPC objects when:

1. Creating an aggregated indicator

2. Creating a Submissions template (using CreateTemplateData component)

Amp Impact features (Manage Framework, Manage Indicators, Set Targets, Add Results, Performance Graphs, and Manage Disbursements) can be configured on NPC objects. To do so refer to this page.

Resolved Issues

SubmissionResponseForm (on Experience Cloud): Users can submit a narrative form when the response to a required numeric field is 0

In previous versions of Amp Impact, there were some specific instances where Submissions could not be successfully submitted on Salesforce Communities, particularly when a response of 0 was provided for a required numerical field. This issue has since been addressed, ensuring that Submissions can now be submitted successfully.

activities LWC (on Experience Cloud): Activity can be created on the first attempt when the Project record is initially loaded

In earlier versions of Amp Impact when users tried to create a new Activity for the first time on Salesforce Communities or Console App, they were redirected to the default tab on the Project page. This has now been resolved such that users can create a Task or a Milestone Activity when they click on the “Add New Activity” button on Activities LWC for the first time on Salesforce Communities or Console App.

setTargets LWC: Project Indicators that have Project Indicator Reporting Periods with different Reporting Frequencies are displayed properly

Targets can now be set for an indicator across multiple reporting frequencies on setTargets LWC which was not possible on the previous version, Kalausi (1.34)

manageLogFrames LWC: Target To Date & Result To Date fields for Project Indicators display comma separators as expected

Proper comma separators are now displayed on the Baseline, Target To Date, and Result To Date fields on the table in manageLogFrames LWC, when more than one Project Indicator is linked to a Framework Objective

manageIndicators LWC: Result records are created when Aggregated Project Indicators are filtered using the “Does Not Contain” operator

In earlier versions, Result records were not created when Aggregated Project Indicators were filtered using the “Does Not Contain” operator for Picklist data types. This has now been resolved in the manageIndicators LWC

setTargets LWC and addResults LWC: Downloaded Targets & Results of qualitative Project Indicators can be viewed without HTML tags

For Qualitative indicators, users can now view downloaded targets and results on the Excel template without HTML tags. The option to disable HTML tags is controlled through a design attribute.

manageIndicators LWC: The formula builder for calculated Indicators displays correct/ accurate Indicator options even when certain fields are excluded from the Edit Indicator popup

The picklist to choose source indicators within the calculation formula builder popup now displays relevant indicators even if the following fields Reporting Frequency, Geographic Disaggregation, Cross Disaggregation by Sex and Group Disaggregation are not present in the Edit Indicator popup

addResults LWC: Project Indicators are not displyed on selecting a Reporting Period when the corresponding Project Indicator Reporting Period record had Data Tracked = None

In the previous version of Amp Impact, Kalausi (1.34), on adding a Project Indicator Reporting Period (PIRP) record to an indicator, the indicator would be available for reporting on AddResults LWC irrespective of the Data Track field value. This has now been addressed so that the indicator is available for reporting only when the Data Track field is set to either “Results” or “Targets and Results”

setTargets LWC: “Something Went Wrong” error is not displayed when users manually delete a few Project Indicator Reporting Period records from a Project Indicator

When removing multiple Project Indicator Reporting Period (PIRP) records from an indicator, the Set Targets page would show a “Something Went Wrong” error message. This is now resolved such that, on removing Project Indicator Reporting Period (PIRP) records from an Indicator, it becomes unavailable for reporting for that PIRP and Reporting Frequency and is marked as NA on the setTargets LWC page.

setTargets LWC: Users can download targets when Project Indicator results are disaggregated but Targets are not

While trying to download targets for Project Indicators whose results were disaggregated but targets were not, the “Something went wrong“ error was displayed on the screen and users were unable to complete the download. This has now been fixed.

setTargets LWC: Users do not get an error when the value of the “Targets are Disaggregated” field on Project Indicator is updated from FALSE to TRUE

When a Project Indicator was created with Targets Not Disaggregated = TRUE and it’s value was then changed from TRUE to FALSE, the Set Targets LWC page would break. This has now been resolved.

Release Updates

Packaging Changes

Updates to ampi__Activity__c

Updates to ampi__Indicator__c

Updates to ampi__Project_Indicator__c

Updates to ampi__Result__c

New Custom Meta Data Type ampi__Dependent_Field_Control_Settings__c

Custom Meta Data Records under ampi__Dependent_Field_Control_Settings__c

Updates to Risk Layout

New Custom Labels

Updated Custom Labels

New Design Attribute

Updated Design Attribute

Apex Class Access

The following Apex classes have been added to the permission set:

• AggregateQueryBuilder

• DynamicFieldSet_Ctrl

• PicklistData

• SObject_Domain

• Submission_Domain

• Submission_TestFactory

Field Access

The following Fields Permission have been added to the permission set:

• Question__c.xx_Allow_Multiple_Files__c