REGISTER NOW FOR THE 2023 INTERFOLIO SUMMIT

How Can We Help?

Search Results

  • Share
P16.02 Release notes

Release date: Monday 10 November 2025

 

Version: P16.02

 

Take a look at the improvements and fixes added to the platform in the latest release.

 

Added: this sprint sees the release of support for outcome prioritisation

  • For each of the 15 common outcome types, funder and centre administrators can now (optionally) identify if reporting against the outcome type is a low priority, or even if reporting is not required.
    • Note: the deprecated “Other Outputs/Outcomes” common outcome type is always marked as “Not Required”, for all awards.
  • They can adjust this prioritisation on a per-award basis.
  • Researchers are presented with information about outcome prioritisation, to guide their reporting activities.

 

Improved: this sprint sees the release of a rewrite of the RHT process. This work delivers some immediate benefits to funders, as well as addressing technical debt and laying the groundwork for future improvements. Immediate benefits include:

  • Support for larger RHT file sizes
  • Support for cofunders data
  • Support for Grant DOI data
  • The PI Title not required
  • Column order is no longer enforced
  • Validation won't fail if optional columns are missing (note: cofunders and Grant DOI will be optional columns)
  • It’s now possible to remove data (where allowable, eg, a category) by using "DELETE"
  • Improved automated validation

Note: the current version of the RHT file template will still work with the new process.

 

Improved: upgraded to PHP 8.3, as part of on-going management of supporting technologies.

 

Fixed: addressed a data issue with a small number of Collaboration and Partnership records.

 

Fixed: addressed an issue that meant it was possible to complete a specific Additional Question with an empty Company subform.

 

Note: As with many sprints, there is development work in this sprint that has not yet been released to the platform.

 

If you have questions about improvements or fixes, please contact c.millerchip@elsevier.com

 

Was this article helpful?
Give feedback about this article