Request List Result Grid Section

Use Case Statement

By Manuel Dennis III

Name	Request List Result Grid Section
Description	How is the information returned and displayed for the Request List Result Grid
Dependencies	Request List Query Section Request Business Logic Layer
Scope	To offer a quick concise list of requests that meet the users scope
Primary Actors	· Assigner, Approver, Worker
Secondary Actors	· Requester, Administrator
Pre Conditions	· The user should enter a Query and press Search
Success End Conditions	· The request list result grid is displayed with proper information for the particular user based on her personid
Failure End Conditions	· Incorrect information or no information is displayed

Document Revision #	Action Taken, Notes	When?	By Whom?
0.1

UseCase

#	Action / Stimulus	Reaction
1	User presses Search on the form to activate a Query	The system calculates the Query, constructs the appropriate Search path, and returns a view to bind to the data grid.
2		The grid should contain the following fields at a minimum. Request Number, Category, Requester, Subject. The grid also contains a checkbox for the Quick Approval feature(Approval or Cancellation).
3		Request Number should return as a hyper link Requester should return as a hyper link

Alternative / Additional Scenario:

#	Action / Stimulus	Reaction
A1	Approver can select a checkbox	This works in conjunction with the Request List Quick Approval Section
A2
A3

Alternative / Additional Scenario:

#	Action / Stimulus	Reaction
B1	User clicks on the Request Number link	The system redirects the browser to the appropriate ManageRequest page for the particular Request selected
B2
B3

Alternative / Additional Scenario: Cancel

#	Action / Stimulus	Reaction
C1	User clicks on the Requester link	Popup a PersonInfo page with the appropriate Requester info

Notes:

Issues: