RFS 6.14 release notes

In this release of the Elements Research Funding Solution (RFS), we are pleased to introduce Project Closure functionality, along with a number of additional improvements and enhancements, supporting various aspects of the research funding lifecycle.  

We have introduced Project closure functionality in this release, enabling users to:

• easily identify and resolve any outstanding actions prior to closure, 

• close a Project (with relevant outcome, dates, reasons, and notes), 

• modify closure metadata post-closure, and 

• easily re-open a Project that was closed prematurely.

Further details are available here.

We have added new tables and views to the Elements reporting database relating to the following content:

• Projects

• Budgets

• Deliverables

• Relationships

And just a reminder - Proposal record data in the Elements reporting database is frozen at the point of Project activation (where relevant), and the new Project object is created and then updated with any modifications made to the record post-activation.  This enables reporting on Project changes during its lifecycle.

System Administrators and Research Funding Administrators are now able to revert activation and approval where these have been actioned in error.

• Reverting activation of a Project returns the record to the Approved state

• Reverting approval of a Proposal returns the record to the Pre-approved state (if an internal award), or to the Submitted to funder state (if an external award)

These functions are available in the Management Console, in the Funding Record > Edit page:

We have updated the individual Project Deliverables and Change requests pages to enable filters and export.

We have made further improvements to the RFS API in this release:

• New Eligibility Form endpoint updates, enabling easier identification of new / updated forms

• Update to the Funding Records endpoint to include:

  • Finance codes

  • Project closure information

• Improvements to the Funding Opportunities write API to support the specification of User and Group view access for hidden opportunities

• We have resolved an issue where, if a user becomes Not Current since being selected as having submitted the application to the Funder (in the Funder submission screen), it is now possible to process the Proposal through to the capture of the Funder outcome with no error messages

• The Grant Manager Email email template merge tag now populates with the Grant Manager email address, as intended

• RFS's email integration has been enhanced to support sending and receiving email using Google Workspace accounts (please get in touch for further information on configuration requirements to enable this functionality).