Issue: When an eGC1 has reached a status of In OSP, the standard OSP approval node will have an approval status of Waiting Approval. If OSP adds a colleague as an “ad hoc” Approver by name, for a second opinion or purposes of training, both the ad hoc Approver node and the standard OSP node will have a status of “Waiting Approval.”
When the application is returned by OSP before the ad hoc node is approved, and campus re-completes the application, the graph’s logic changes. When it is redrawn upon re-completion, the ad hoc OSP Approver node is considered to be a campus approver with an approval status of Waiting Approval, and the standard OSP node will have an approval status of En Route. Therefore, the status of the eGC1 is set to Routing rather than back to In OSP as expected. Unless the OSP staff have included eGC1s with a status of Routing in their tasklist view, the application will not appear on their tasklist.
This causes confusion for both the campus user who can verify that the eGC1 has been re-completed and the OSP Administrator who cannot see the eGC1 because of the unexpected status change.
Note: Once the ad hoc OSP Approver node is “approved” the status of the application will change from Routing to In OSP.
Solution: When an eGC1 does not show up on the Tasklist for an Administrator in OSP but Campus asserts to have Re-Completed it, have OSP include “Routing” on their tasklist filtering, or search for the specific application.
You can change any Funding Action or Admin Action in Approved, Denied, Duplicate, or Returned by GCA status back to In OSP status. Use the In OSP link on the left navigation menu to start the process.
A pop-up window will appear that will allow you to change the status, reassign the item, and add comments if desired.
Add any explanatory comments you wish, reassign the item if necessary, then click on the In OSP button to complete the process. The pop-up window will close, and the item details page will refresh showing the new status.
Note: If you change an Admin Action assigned to the location File back to In OSP status, the system displays a warning message, which reads:
“An Admin Action with status of In OSP may not be assigned to File. Please modify the status or the assignment.”
To complete the process, you will need to reassign the Admin Action to a value other than File.
Issue: When the parent application is changed for an FA that is in Processed status, compliance auto-holds may appear, depending on the data in the new parent application. The process of applying auto-holds does not check the FA’s status when it is re-parented. Since the FA is not editable when in Processed status, the holds cannot be removed.
The system should either not allow re-parenting of processed FAs, or not apply auto-holds when a processed FA is re-parented. The appropriate fix based on business processes needs to be determined.
You can review the status history of any application, funding action, or admin action by clicking on the Status tab.
This is the Status page from an application.
The Status History includes the date and time the status changed, the resulting status, the person whose actions changed the status, and either a system-generated comment or any notes entered by the person at the time.
To understand the different statuses an item may have, see the appropriate section.
Note: You must have the OSP Administrator ASTRA role.
To retrieve the status of the application, first click the Select button to pick the endpoint. The Selected? checkbox to the left switch to checked. You must do this step even if there is only one endpoint.
Next, enter the full Grant Tracking Number, including “GRANT” and click Check Status.
The results of the status check will display.
