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.