RFS 6.15 release notes

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

Following on from the Project Closure functionality introduced in v6.15, we have added the facility to add a Project Closure Checklist that enables you to ensure all appropriate checks are undertaken prior to a Project being closed.  Further details are available here.

Where a user doesn't have access to a closure action (e.g. Research Manager (Funding) does not have access to Budget Transfers), rather than being directed to a screen that informs them they are unable to perform the action, this messaging is now available on the Closure screen, with the relevant action button disabled.

The Closed Projects search screen has been updated:

• Updated layout with new table columns

• New filters

• New export fields available

In this release, we have introduced a new function to enable the bulk upload of funder outcome data, helping users save time by not having to manually key in funder outcomes.  Further details are available here.

In response to client feedback, we have introduced an additional Funder outcome of 'Reserve', where the funder has indicated that funding may be awarded at some point in future, should other awards from the funding call not proceed.  Further details are available here.

• The Submitted to Funder search page has been updated to include 'Funder outcome' as a results column, filter, and export field.  'Funder outcome received date' has also been added as a filter and export field.

• When capturing an Unsuccessful funder outcome and processing the action, it is now possible to capture more granular details on the unsuccessful reasons (if these have been provided by the funder).  Default values are:

  • Unsuccessful - due to funding constraints

  • Unsuccessful - on administration grounds

  • Unsuccessful - on scope of round

  • Unsuccessful - no specific reason

  • Any existing records with the old “Unsuccessful - funder application” reason have been replaced with "Unsuccessful - no specific reason".

• This release also includes a datamodel update such that the 'Submitted by' field is no longer mandatory when capturing funder submission details.

In this release, we have expanded the relationship types to include a new 'Sub-grant - External distribution of funds' relationship type, aimed at supporting projects where a portion of the main parent project budget distributed to external parties (e.g. sub-contractors).

We have also added a new organisation type for sub-contractors, to enable such organisations to be identified appropriately in reporting.  See the 'A note on the 'Institution External Source' control' section on the Organisations support article for guidance on how to configure Proposal forms to capture sub-contractors.

We have updated the Relationships screen to provide more on-screen information, filters, and export options.  Further details are available here.

We have also updated the permissions for this page to ensure appropriate access to content for Group users.

In this release, we have updated the default behaviour of RFS as a datasource for Awarded Grants, to ensure that Awarded Grants are only created for specified sub-grant types (i.e. Internal and External contributions), and the main award's Award Amount is accurately stated where the sub-grant is not harvested (i.e. Extensions, Distributed budget, and External distribution of funds).

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

• Change requests

• Eligibility form data (as held against the Funding Opportunity)

We have also made a number of smaller improvements to existing tables and views, expanding the RFS data available for reporting.  This includes:

• Funding opportunities

  • Proposal outcome workflow name

  • Funder currency

  • Proposal form template name

  • Eligibility form template name

• Projects

  • Closure details

  • Funder Outcome Non Financial Variance Type

• Organisations

  • Include all external organisations, not just those flagged as 'Active'

• Include Primary Group descriptor against individuals in relevant views

• We have resolved some on-screen datetime inconsistencies to ensure your instance's configured timezone is accurately reflected.  Resolved pages / areas include:

  • Reviews

  • Documents and the display of document dates on the Proposal details page for researchers

  • Scheduled jobs pages in the Management Console

  • Saved search filters in the Management Console

• We have resolved the issue when a user clicked on a review / funding opportunity link sent to them in an email while they were logged out, the login page would return the user to the home page instead of the review / funding opportunity they were trying to access. The login page now re-directs the user directly to the review / funding opportunity.

• It is now possible to delete Funding Opportunities that have no associated proposals or projects.