Manage Request Issues still to do....

• Shrink Header and menu a bit more
• Change some fields to definitely Read Only from Manage Request
  1. Request Number
  2. Request ID
  3. Requester
• Change some fields to dependent Read Only
  1. Subject 
  2. Description
• Modify visibility routine for Request ID
  1. Only show Request ID when user is in developer role
• Approval Button Validation 
  1. for Category drop down list - must have a category to be approved
  2. for Action drop down list
• Action drop down list must be dependent on Category
  1. use dependent drop down client side script method
  2. try using XML combo example
• Move title of Page to Header label
• Rearrange drop down lists
  1. Requested Completion Date down
  2. Client up and to the right of Division
• Move Requester drop down list to Notify section
• Pop up windows
  1. Enable Requester link
     1. Should we encrypt PersonID in Person lookup?
     2. This will prevent users from accessing other users info
  2. Enable Rank link
     1. Finish up Ranked Requests page
• Machine List
  1. Narrow scope of machines visible
     1. Related to Request Only
     2. Not related to Request
     3. All
  2. Sort and place selected machines on top (not necessary if Scope is narrowed)
  3. Allow for a pick all and pick none
  4. Find a check all picture and a check none picture or make them
• Display just the Current Status Code
• Break the Status History Grid Current Status Description and Code into separate columns (Code 1st)
• Grids and Templates
  1. Convert all templates to use ItemCreated event/method instead 
  2. fix dynamic display of IDs
  3. Compress some functionality and make classes for lookups instead of functions
• Status History section
  1. Dynamically change enabled state of buttons 
     1. completed doesn't make sense for a new request
     2. approve doesn't make sense for assigned request
  2. Move the buttons to the Status History Grid Header
  3. Approve button method
  4. Wish List button method
  5. Complete button method
  6. Cancel button method
  7. Add status comment entry textbox
• Comment section
  1. Create a comment entry form
  2. Possibly allow the user to enter a comment via the grid
  3. Add a new button to the Comment Grid Header
  4. Do we need to encrypt comment notes?
• Notify section
  1. Rename Email button to Notify button
  2. Move the Requester drop down list here on a notify line
  3. Create an Approver notify line
  4. Create an Assigner notify line
  5. Create a Worker notify line
  6. Create Worker Department notify line
  7. Create a notify all and notify not necessary check box
  8. Hook email notification to EMAIL class
  9. Adjust checkboxes to determine who should be notified
• Assignment section
  1. Move New Assignment button to header of assignment grid
  2. New Assignment button should jump to New Assignment Page
  3. Check problem with Assignment date 
  4. Check problem with Assignment status
  5. Remove assignment id from Assignment grid
  6. Add project to show what project the assignment is related to?
  7. Can we work with a highlighted grid line example?
  8. Move Request Status becomes Assigned Status to New Assignment Page Submit button
• Estimate section
  1. Possibly change the data types to allow decimals for estimates
  2. Add a modify button to the Estimate grid header
  3. Warn user when modifying estimates
  4. Should we allow in grid editing?
  5. Possibly validate when no estimate is submitted by approver/assigner
• Work Time section
  1. Work on subtotaling Worker Time from Assignment entries
  2. Service code/description needs to be looked up
  3. Add percentage symbol behind Billable and capitalized values
• Attachment section
  1. Conditionally show Directly from Server link column when user has rights 
     1. Check IsInRole() 
     2. Create a Power to see if a user has Direct Server Access
  2. Add more attachment fields
     1. Content Size
     2. Content Type
  3. Add new/upload button (and file upload control) to Attachment grid footer
  4. Test this button
  5. Check for existence of files before allowing links
     1. display to the user when a  file is offline/online
  6. Finish up GetAttachment page
• Build Cancel button method
  1. track changes to help role back changes (sub grids etc...)
• Build Submit button method
  1. validate changes
  2. save changes to Request object
• Can we dynamically hide the menu bar when printing? No

Copyright 2002 - 2003 XOCOMP, llc
Contact: md3@protocolla.com or md3@xocomp.net after March 2003

All materials and notes are the intellectual property of XOCOMP with expressed permission for use by PROTOCOL.