When you open a document, you see different workflow action buttons at the bottom of the document depending on your relationship to the document and the document’s current workflow status. Some transactional documents contain a separate page dedicated to actions, and only display unique, workflow-specific action buttons at the bottom of that page. These buttons vary depending on what kind of action request you received for the document and on whether or not you are a special kind of KC user, such as an Administrator or Superuser.
Table 18 KC E-Doc Action Command Button Examples
Button |
Description |
Sends certain federal proposals created in Proposal Development directly to the Grants.gov on-line system. This system-to-system (S2S) application transmittal is only available for certain funding opportunities. The eligibility requirements are specified by each sponsoring agency. This button only appears on the Proposal Actions page of the Proposal document and is only functional after full routing and approval. | |
Moves the document (through workflow) to the next level of approval. Once a document is submitted, it remains in ‘ENROUTE’ status until all approvals have taken place. | |
Denotes that the document is void and should be disregarded. Canceled documents cannot be modified in any way and do not route for approval. They may be copied, however, to a new document. | |
Signifies that the user wishes to exit the document. The system displays a message asking the user if they want to save the document before closing. No changes to Action Requests, Route Logs or document status occur as a result of a Close action. If you initiate a document and close it without saving, it is the same as canceling that document. | |
Allows the initiator of a document to save their work and close the document. The document may be retrieved from the initiator’s Action List for completion and routing at a later time. | |
Refreshes the screen and displays the most recently saved information. Changes which are made but not saved prior to reloading a page are not maintained. | |
Returns the document to its Initiator when the initial OSP reviewer has identified changes that are required for approval. This action has the effect of remanding the document back to the originator or preparer for modifications. You will be prompted to enter comments, just as with a disapproval. | |
Signifies that the user has responded to the FYI action request. Only available to users to whom a document has been routed for FYI. The difference between Acknowledgement and FYI is that FYI requests can be cleared directly from the action list without opening the document. FYI requests also have a different effect on the document status than Acknowledgements. A document with no pending approval requests but with pending Acknowledge requests is in Processed status. A document with no pending approval requests but with pending FYI requests is in Final status. FYIs do not interrupt the normal Workflow routing of a document either. To signify that you have responded to the FYI action, you may take one of the two actions: click FYI when you open the document, or select FYI in the Actions column and click take actions directly from the Action List. If you wish to clear all of the FYI actions in the Action List at once, you may first set the default action from NONE to FYI. Click apply default located at the upper right corner and then click take actions. | |
Signifies that the user has responded to the Acknowledgement action request. It is only available to users to whom a document has been routed for acknowledgement. Acknowledgements do not interrupt the normal Workflow routing of a document. They do not stop a document from routing on to other individuals or workgroups who need to take approval actions. | |
Signifies that the document represents a valid business transaction in accordance with institutional needs and policies in the user’s judgment. A single document may require approval from several users, at multiple route levels, before it moves to final status. | |
Signifies that the document does not represent a valid business transaction in the user's judgment. A Disapprove action from any single approver prevents a document from ever posting to the GL. Enter a reason for disapproval, and then click yes to confirm. The reason entered displays in the Notes and Attachment tab once the disapprove action is completed. | |
Bypasses all subsequent levels of approval and immediately moves a document to final status. Anyone who would normally have received the document for approval receives an Acknowledgement request instead. This action may only be taken by an Administrator. If you are an Administrator, you have the option to blanket approve a document routed to you for your approval. Click blanket approve to approve the document bypassing all other approvals. | |
Performs a route report. In other words, clicking this causes a new browser window to pop up that displays the same information that is contained in the Route Log tab. These include sub-tabs within the Route Log tab for Document Id, and possibly Actions Taken, Pending Actions, and Future Actions, depending on the document and route status. | |
Superusers use this to select an action request, select the recipient type, enter the user ID or workgroup ID, and ad-hoc route a document. | |
Superusers click this to return a document to the previous route level, by first selecting a node name from the route level list. |