# | Title | User Story | Importance | Notes |
---|
1 | Persistent cart | A user wants to Save Requests for later. | Must Have | - The Cart will be saved as items are added. If the user logs out of the system and then back in, the cart will be restored.
- The Cart may contain multiple requests.
- The count next to the Cart Icon will indicate how many requests are in the cart, not the number of individual items in the cart.
- Clicking the Cart icon will bring the user to the cart page.
- If the Cart contains multiple requests:
- Individual actions can be moved from one request to another in the cart.
- When the user adds another item to the cart, a prompt will be displayed asking if the item should be added to an existing request or create a new request.
|
2 | Save Incomplete Requests | A user wants to save incomplete requests. | Must Have | - Allow customers to enter partial requests and save them for later.
- Fields required to submit the request do not need to be filled in before saving the request.
|
3 | Allow submitting requests individually | A user wants to submit part of the saved cart. | Must Have | - Give customers the ability to submit some, but not all requests from the cart.
- Submitted requests must specify all required information.
- Requests missing required information cannot be submitted.
- Each request will have a customizable name, limited to 30 characters. The default name will be "Request 1", "Request 2", etc.
- When the requests are submitted, the request name will be saved as a remark on the Request.
|
4 | Redesigned Cart Layout |
| Must Have | |
5 | Select multiple Services and Equipment | A user wants to change or remove multiple Equipment and Service records in a single request. | Must Have | - Customers need the ability to add multiple Service and Equipment records for change or remove requests.
- The user must be able to select items for Change and Remove requests at the same time.
- A combination of Adds, Changes and Removes may be added to a single Request. It will not be necessary to submit multiple Actions as Separate requests.
|
6 | Summary Page of Submitted Requests | A user needs to see all pending requests, including partial requests. | Must Have | - After submitting one or more Requests, the user will be presented with a summary of the Requests.
- The summary page will include a section of Requests that were not submitted and it will list the reason(s) why.
- The summary page is printable; Requests that were not submitted will be excluded from the printout.
- Each Service Request listed will include the following information:
- Service Catalog for add requests
- Service ID for change/remove requests
- Service Reference
- Owner
- Contacts
- Location
- GLA
- Jack (if required)
- List of Attachment file names
- Cost
- Each Equipment request listed will include the following information:
- Equipment catalog for add requests
- Equipment ID/Asset Tag for change/remove requests
- Owner
- Contacts
- Location
- GLA
- List of Attachment file names
- Cost
|