5.25.25.25.2

We would like to advise our community module customers of a change made in v5.25.2 that affects how person records are chosen and updated as the consequence of a deduplication/merge exercise.

Previously any subsequent post-merge changes made to the primary community instance of the person record (based on the source ID) would be applied as expected in the central community instance, however any changes from any of the secondary community instances would be silently omitted. The consequence of this behaviour was that affiliation changes made on the secondary instance would not update, for example when one affiliation became former or a new one was added.

To resolve this issue the community synchronisation has been updated so that it will also update the primary ID used in the community instance each time changes have been harvested from a primary or secondary community instance of a merged person record. This ensures that affiliation changes from a secondary instance are applied as expected, and the changed source record will be considered the primary instance going forward (at least until a subsequent change is harvested from a different community instance)

2. Unified Project Model and Award Management

UPDATE - Changes to Web Service for derived Total Amount fields

In version 5.25.2 a change has been implemented that fixes (retrospectively in v5.23 and v5.24 web services) a security issue in which a number of funding fields were exposed in the Pure API despite their associated fundings having a backend status. The fields affected are as follows;

• getTotalAwardedAmount
• getTotalSpendAmount

The issue occurred as the listed fields were derived from other fields in the funding records. The calculation used to derive these values was not talking the visibility settings into account and could therefore have made accessible data that should only have been available to administrators, editors and contributors.

As of 5.25.2 these values have been deprecated and may therefore have a detrimental impact for customers using this information as part of their external BI reporting. The fields are still available from within the reporting module and according to the reporting level permissions. For purposes of ongoing BI reporting, the values must therefore be calculated based on the data made accessible via the individual fundings data at point of use. We will review the availability of these values as part of a future version of Pure.