Overview
This release includes multiple enhancements and bug fixes across the eTools suite, improving usability, data integrity, synchronization, and security.
Below is a summary of the updates by module.
Partnership Management Portal (PMP / ePD / SPD)
Humanitarian Reporting Requirement can now be removed when High Frequency Indicator is toggled off (INC0532609)
Previously, if a Programme Document (e.g. PHI/PCA2024163/SPD2025469 by ACCION CONTRA EL HAMBRE) was flagged as High Frequency under the Workplan tab, the system would automatically add a Humanitarian Reporting Requirement under the Timing tab. Disabling the High Frequency Indicator did not remove that Reporting Requirement, and users could not delete it.
Now, when High Frequency is turned off, users can remove any previously added Humanitarian Reporting Requirement. Support can also clear it if needed. This prevents outdated / unnecessary reporting requirements from staying on the PD and confusing partners.
Inactive locations are now protected in Geography pickers across PMP / GDD / ePD
We’ve updated the Strategy > Geographical Coverage and related dialogs so that unchecked or inactive locations are disabled in dropdowns and can’t be re-selected when editing. Inactive locations are still shown (for reference and filtering), but cannot be re-applied in edit mode.
The Import eCN dialog and Activity dialog now hide inactive / unchecked locations at selection time.
This reduces accidental use of deprecated locations while keeping visibility for audit and filtering.
Enhanced logging for PD activities submitted to Vision (traceability for escalations)
Some PDs were reported in Vision with missing activities, but we had no way to prove what eTools actually sent. We’ve added detailed logging to the PD → Vision sync (“send_pd_to_vision”), capturing PD number, activity number, activity name, and cash totals (UNICEF cash, partner cash, total).
These logs are now stored in a persistent log source (e.g. VisionSyncLogs / New Relic) so that support can verify after the fact what was transmitted. This will speed up investigation when Vision receives incomplete data.
Geographical coverage warnings on deactivated locations during record creation
When a user was creating a new object (e.g. Action Point, etc.) and the selected location was deactivated mid-process, the app would hang on “loading” and never recover.
We now display a clear error message and allow the user to continue the creation process without freezing. This prevents data loss and reduces support tickets related to stuck forms.
Partner Reporting Module (PRP)
Indicator locations now stay in sync with the PD (INC0538683)
When colleagues amended PD PGD/PCA2024223/PD2024329-2 and removed Bangladesh, Mexico, and Brazil from indicator locations, those locations continued to appear in PRP.
We fixed the sync/cache issue so that when locations are removed from the Programme Document, they are also removed from the corresponding indicators in PRP. This ensures partners only see valid implementation locations.
Reporting window extended until PD is fully Closed (not just “Ended”)
Partners can now continue reporting on indicators in PRP after the PD status moves to “Ended.” Reporting will only be blocked once the PD is officially “Closed.”
This change reflects real workflows where financial / programmatic wrap-up continues after implementation ends, and prevents premature lockout.
Better partner reporting experience (PRP data entry form updates)
- Character limits for narrative / qualitative questions have been increased to 5,000 characters.
- Partners can now upload up to 7 files (previously 3).
- Accepted formats now include PDF, PNG, JPEG, Word, CSV, and Excel.
When a file fails to upload (for example due to size), PRP now shows a clear error message instead of silently failing.
These changes reduce frustration and cut back-and-forth with UNICEF focal points when submitting progress reports and evidence.
Frontend dependency cleanup and security hardening
We ran a full dependency review of PRP’s front-end libraries and removed / updated outdated packages that were creating known vulnerabilities. This reduces our exposure and improves long-term maintainability.
Reporting period edits without breaking PRP sync
Programme timelines often shift (start pushed back, end extended, etc.). Until now, adjusting the PD start/end dates regenerated reporting periods, which could crash PRP sync with duplicate key errors and block submissions.
We’ve introduced safe editing rules for reporting periods:
- Periods that already have submitted reports are “locked” and cannot be changed.
- Future / empty periods can be shifted.
Before activation of the PD, all periods remain editable because no reports exist yet.
On save, users get a clear warning if some periods are locked.
On the backend, PRP can now update reporting period dates without triggering integrity errors.
Result: offices can adjust timelines without breaking reporting.
Due Date changes in amendments now flow through to PRP
When users changed the QPR due date in an amendment, the merged PD kept the new date — but PRP did not. We’ve fixed the sync so updated reporting due dates in PMP (including amendments) are correctly reflected in PRP.
This ensures partners and UNICEF are looking at the same deadlines.
gPD
Terminology alignment (“CSO Contribution” → “Partner Contribution”)
To reflect that not all partners are CSOs, the “CSO Contribution” field under gPD Details is now labeled “Partner Contribution.” This improves clarity for Government and other partner types.
Results Reported tab cleanup
We reviewed what is displayed in the gPD “Results Reported” tab and removed elements that were not valid for gPD workflows. This reduces noise and prevents users from being asked for data that does not apply to gPD.
Reports tab wording (“QPR” → “PR”)
All references to “QPR” in the gPD Reports tab have been updated to “PR.” This change aligns naming with the Partner Reporting Module and avoids confusion between quarterly / periodic reporting types.
Sub-Activity functionality under a Key Intervention
Country Offices requested the ability to create “sub-activities” beneath an existing activity (mirroring ePD behavior). Users can now add additional activities under the same Key Intervention.
The eWP Activity reference and assigned Locations are inherited and locked (not editable), ensuring financial and geographic traceability.
Other fields of the sub-activity remain editable.
This gives programmes flexibility to break work down operationally without losing alignment to the approved intervention structure.
Budget control warning vs eWP ceilings
eTools now warns users if the budget amounts entered in gPD exceed the budget amounts defined in eWP for the same Output / Key Intervention.
This helps planners avoid creating a gPD that cannot be financed under the approved workplan envelope.
Focal Point info popup text updated
The tooltip text for Partner Focal Point has been updated to:
“If the partner focal point is missing from the dropdown, or if their details are incorrect, please add or update the information via the Access Management Portal.”
This directs users to the right place (AMP) to correct contact data instead of raising manual tickets.
Key Intervention editing rules streamlined
Because eWP may plan at Key Intervention (KI) or Activity level, and gPD duplicates KIs as Activities when planning was done at KI level, allowing users to edit the KI directly in gPD was causing duplication and misalignment.
We removed the ability to edit KIs in gPD.
The Delete option remains, so users can still remove an irrelevant KI from view if needed.
Result: fewer conflicting versions of the same intervention.
Cleaner Government view (hide truly empty sections)
In Government workflows, we were showing an empty placeholder section above “Partner Details” for partner users even when nothing applied to them.
We now automatically hide that empty block and only display relevant compliance fields (e.g. Partner HACT Risk Rating, Core Values Assessment Date) when they exist for that user type.
This reduces confusion on the partner side.
Support for Inactive Partners (Government entities)
RAM allows eWPs to be created for entities marked Inactive. gPD now aligns with that reality: Inactive Government Partners are visible (in red text) in the “Add gPD” form.
If an inactive entity is selected, the user sees a warning:
“Please note that the selected entity is currently inactive. It must be reactivated in Vision before any transactions can be processed.”
Synchronization logic will also be updated to ensure eWPs with inactive partners still sync to gPD.
This lets offices proceed with planning and documentation, while clearly signaling that financial transactions require reactivation in Vision.
Field Monitoring & FMM
Assign BOTH Staff and TPM to the same FM visit (joint monitoring)
When a Field Monitoring visit is conducted jointly by UNICEF Staff and a Third Party Monitor (TPM), assigning the TPM through the STAFF option did not grant the consultant access to the Data Collection form and did not trigger notification emails.
We added a new assignment option: BOTH. BOTH grants data collection access to both the Staff member and the TPM. BOTH triggers notification emails to both assignees and shows both assignees in the visit header and activity log.
This supports joint monitoring missions without manual workarounds.
Hide inactive locations when creating / editing visits
When scheduling or editing an FM visit, inactive locations are now disabled in selection lists so they can’t be (re)assigned by mistake.
Inactive locations remain visible in filters and historical records for traceability.
This prevents new visits from being tied to locations that should no longer receive monitoring, while preserving reporting history.
Cleaner user pickers in FMM
Inactive users no longer show up in the user dropdowns in FMM.
This cuts down on misassignment to staff/consultants who have left or are no longer active, and reduces the need to correct visits after the fact.
Financial Assurance, HACT & Audit / Spot Check
Required Spot Checks now display correctly in PMP Assurance tab
Offices (example: Ukraine) reported that some partners met the HACT threshold for a Spot Check (e.g. ASSOCIATION OF INNOVATIVE AND DIGITAL EDUCATION - 2500246486) but the Assurance tab in PMP still showed “0 Required Spot Checks.”
We aligned the UI with the backend values. The system now correctly surfaces the number of Required Spot Checks derived from HACT minimum requirements / Vision data, instead of the incorrect “planned_engagement” value.
This ensures Budget Owners and Assurance focal points can see accurate Spot Check obligations at a glance.
FACE form data linked to Audit / Spot Check engagements
We introduced the first step toward integrating FACE reporting with Assurance engagements (Audit / Spot Check). This is an upcoming feature that will be showcased by the FAM team in future communications.
Access Management Portal (AMP)
Fixed multi-partner assignment validation errors
When trying to approve a user who was already Approved under one partner and add them to an additional partner, AMP returned a validation error and blocked the action.
We’ve updated validation logic so that a single user can now be associated with multiple partners.
This is critical for rollouts like LMSM training, where one focal point legitimately supports multiple partner entities.