Bellatrix (v1.23) | Release Notes | November 2019

Key Product Features

New Features

Generate XMLs to share your data to the IATI Registry 

Now manage your IATI-related information and data entry XML generation through Amp Impact! Meet funder reporting requirements and adhere to the International Aid Transparency Initiative by generating you Organization and Activity Standard XMLs directly from your Salesforce.

Organizations will be able to customize the following: 

• Reporting Org: define standard Reporting Org details when it is the same across all IATI Activities.

• Generic Contact: define standard Contact details when it is the same across all IATI Activities and/or needs to be anonymized.

• Tag: define which Object will be used by the org for the generic Tag element in the Activity XML.

Risk Management: Identify, Monitor, Mitigate and Evaluate 

Now, manage any potential risks that could impede your impact:

• Identify different types of risk you may face and assess their probability and potential for impact

• Visualize this risk information and evaluate how it was managed 

• Monitor these risks and assign them to individual team members and/or related to particular objectives/goals

• Determine mitigation strategies and track their completion

Feature Enhancements

Enhanced Grantee Reporting experience 

We’ve made enhancements to make the user experience more streamlined for grantees to report to you using Salesforce Community! Now,

• login and select the relevant reporting period

• navigate between tabs to enter indicator results, narrative reports, upload financials and files 

View related data across tabs

Within a Project record, users can toggle between tabs such as ManageFramework page and ManageIndicators page. Previously, if a user made a change on a Visualforce page that impacted data tracked on another page, navigating from one page to the second did not refresh it, and the user would have to refresh the entire Project to see the updated information. 

For example, if a user created a new Project Indicator associated with a Project Objective on the ManageIndicators page, they would need to refresh and then tab to ManageFrameworks page to view the Project Indicator displayed with the relevant Project Objective (Logframe Item). 

Two updates have been made:

1. If the user is currently working on a page and another user’s work on another page impacts their data, the following pop-up will display with a refresh icon.   

2. When the user clicks the refresh icon, only the current tab will refresh, so the user can more efficiently see the updated information without having the refresh the entire project.

Customize the user interface for all Amp Impact features 

Determine and manage which users have access to each Amp Impact page and the action(s) they can take for the following:

• Manage Framework

• Manage Indicators 

• Activities

• Set Targets

• Add Results

• Financials (Manage Disbursements)

For example, on the Manage Indicators page, select

1. which tabs are visible 

2. which buttons and icons are visible  

Search and Filter while Managing Indicators and Entering Targets/Results 

Customize the list of filters displayed on the:

• Selected Indicators and Deactivated Indicators tabs on ManageIndicators

• Set Targets page

• Add Results page

Run all Aggregated and Calculated Indicators with a single button

Using a new “Refresh Indicators” button on the Manage Indicators page, select which type of indicator calculations to run (all calculated indicators or all aggregated indicators). 

Project Indicators inherit Indicator-level disaggregation 

Previously, when an Indicator was selected from the Catalog, the subsequently created Project Indicator did not default to having the same Disaggregation Group assigned. The user would need to manually edit the Project Indicator to add the Disaggregation Group.

Now, when a new Project Indicator record is created, it inherits the Disaggregation Group and Values populated on the parent Indicator. 

Manage Indicators that are required for a Thematic focus

While managing indicators if you are associating them with a Thematic Area, then use a new field (Required) to ensure that if the Thematic Area is added to a Project, any indicators which are required for the Thematic Area will be added to the Project.   

Improvements to managing text limits Submissions Template Builder 

Previously, when creating a new Question or Section in a Template, if the user entered more than 255 characters, they would be able to save the Question/Section but would not be able to save the changes to the template itself. The template would save if the user modified the question/section text to be less than 255 characters. 

Now: User will not be allowed to enter values greater than the field character limit for any fields (custom-built by user or already in Amp data model), when they are creating/editing a Section/Question in the popup 

Resolved Issues

Logframes: Cancel creating a new Framework Item

If a user selects Cancel to close out of the "Create new framework item" popup, any percent or currency baseline/target to date/result to date values render as "0" on page until the user refreshes the page.

This is now resolved to ensure that a user can cancel out (by clicking "X" or Cancel button) and no changes are saved and page does not re-render differently.

Aggregated Indicators: Editing the Aggregation Criteria

If a user edits the Aggregation Criteria for an aggregated Project Indicator and then clicks on the Refresh icon to run the batch (without refreshing the page), the action of running the batch causes the Agg Setting field, which stores the Aggregation Criteria, to overwrite the new value with the previous value, and the batch runs for the incorrect criteria.

This is now resolved so that:

• The Aggregation_Setting__c field retains new value

• The batch runs per the new Aggregation Criteria 

Uploading Financials: Relate Records to Correct Project 

When using the Upload button to add/edit Financial records, users could populate lookups on the Financial record with records from other Project records. For example, if a user has an Activity called "Host workshops" in the "Financial Inclusion" Project, another user can successfully relate their Financial(s) in the "Tanzania Health Education Program" to the "Host workshops" Activity even if that Activity doesn’t exist in the Tanzania project. This is primarily an issue for records that can have the same name across Projects.

This is now resolved using a filter on the Upload functionality so that Financial records can only be related to the other records on the same Project. This must be applied to the following lookup fields on Financial:

• Budget

• Reporting Period

• Activity