This pop-up window displays when you select the Check for Errors link on either the left navigation menu or the Certify & Route page. The eGC1 Final Validation section will list any errors that you need to correct before you can route your eGC1 to reviewers.
If you are creating a Grant Runner application, the Grant Runner Sponsor Forms Validation section will display below the eGC1 section.
Note: When you select the Route to Reviewers button on the Certify & Route page, the error check is also done. For a standard eGC1, this window will display only if there are errors.
eGC1 Final Validation
If any eGC1 page has errors, you will see a heading for that page, followed by a bulleted list of errors. The information displays in the same order as the eGC1 pages.
Examples of the types of errors listed would be:
- Required fields without a value.
- “Yes” answers to compliance questions without any required additional explanations or information.
The image below shows examples of eGC1 page errors.
Grant Runner Sponsor Forms Validation
For a Grant Runner application, the Check for Errors process includes all of the Grant Runner mandatory forms and any selected optional forms.
The forms will be checked for any Grants.gov errors and the basic NIH errors, some of which are specific to Activity Type. Once all of those errors are cleared, your forms will be checked by an additional NIH service. It provides warnings and errors specific to your opportunity.
Note: If you select Ready to Submit = No on the Certify & Route page, you can route your application for review before all of the Grant Runner errors are fixed.
Once you select Ready to Submit = Yes, you must have fixed all error in order to re-route your application, and for it to be submitted to Grants.gov.
Warnings will not block you from routing your eGC1 but may reveal other issues to be considered prior to submission.
The Check for Errors list identifies the form page in your Grant Runner on which the error appears, and describes the error or problem.
- Required or optional form not yet viewed
- Required data not completed
- Required attachments – “Biographical Sketch is required.”
- Conditionally required data or attachments – “X is required when Y condition occurs.”
The image below shows two examples of Grant Runner form errors.
There are several ways to verify that you have entered all of the required data, and included any required attachments, on your Grant Runner application forms.
- On the left navigation menu, you can look for any red exclamation mark “validation icons” to the right of the form name. This indicates missing data. When the form is complete, you will see a green check mark icon.
- For a single form, you can use Field Pop-Overs and the Show Form Errors link, described below.
- For an overall check, select Check for Errors from either the left navigation menu or the Certify & Route page to see the Errors and Warnings Summary, described in its own article.
If you select Ready to Submit = No on the Certify & Route page, you can route your Grant Runner application for review even if it still has outstanding Grants.gov or NIH errors.
You must fix all errors for your application to be eligible for submission via Grants.gov.
The following image shows the left navigation menu with the validation icons.
As you work on a form, you will notice some fields outlined in red. Generally, this indicates a required field, as does the red asterisk (*) following the field’s label. If you click on that field, a “pop-over” explanation will display.
Note: Some fields may not be marked with the asterisk (*) but may still be required based on other data entered.
Show Form Errors
Another way to look for errors on a form is to use the Show Form Errors link on the “icon bar” at the upper right of the form.
Clicking the Show Form Errors link displays a list of errors at the top of the page. Once you click the link, it changes to Hide Form Errors so that you can turn this feature off.
In addition to the list, all of the corresponding pop-overs display to help you spot the errors on the form.
Additional FG-3 compliance question validation for RRF eGC1s
- eGC1s that have Royalty Research Fund (RRF) as the sponsor will display a validation error if question FG-3, the question about F&A cost reimbursement, on the Compliance Questions page is marked as ‘Yes’. RRF requires FG-3 to always be marked as ‘No’, so this validation error is intended to ensure that the eGC1 preparer selects the correct response prior to completing the eGC1.
Increase character limit in “Reason” field when adding Approvers and Watchers
- The “Provide a reason” field when adding an Approver or Watcher on the Approval Flow Screen has been increased from 250 characters to 1000. Department and School reviewers who add additional Approvers and Watchers like to include detailed instructions in that comment box and needed a higher character limit.
We now will show all recipients on the TO line of SAGE auto-generated email notifications.
- SAGE users will be able to see all persons who received the same Auto-generated SAGE email on the TO: line of the email. This was a frequent request from campus through our help desk and survey responses.
Inadvertent sending of disclosure notifications
- Fixed the system to prevent investigators from receiving disclosure notifications when an old awarded eGC1 is opened. The system will now only trigger disclosure notifications when there is an investigator change made to the eGC1 (addition of an investigator or change of personnel to an investigator role).
HSD JIT email notifications are suppressed for RRF eGC1s
- Human Subjects Just-In-Time emails will no longer be sent to the owners of eGC1s where the Royalty Research Fund (RRF) is the sponsor. RRF is an internal UW sponsor and operates differently than external sponsors. Unique characteristics of RRF opportunities include shorter application/review/award timelines and the lack of “fundable score” notifications. These unique characteristics therefore made the Human Subjects JIT email irrelevant and confusing for the owners of the eGC1.
New clarifying message displayed when clicking on Investigator Disclosure History and FIDS Profile is not yet established
- If an Investigator has never completed a disclosure in FIDS, or does not have any disclosure history for the past 12 months, a new user-friendly message stating there is no history will display when the Investigator Disclosure History link is clicked.
New error message displayed when you have attachment upload errors due to hidden or invalid characters in file name
- A new error message will display in SAGE if you attempt to upload eGC1 attachments with invalid characters in the file name. To correct this issue, rename the file on your computer by directly typing in the characters before attempting to upload it in SAGE.