- When you come to the second screen, don't want it to be just "Reset Form". That's fine for the first screen, but this should be back/next/submit (just back/submit since there is not next) - Delivery location is going to be blanked out. Won't rely on swish to do it. Must have them type it. - Group input on the first page must be moved into the tablet form as it's tablet specific - MAYBE Manager name input on the first page (same way as on traveltime -- loaded from swish, though might be from DB at a later point) - Services section has the wrong title on the mobile form - There is too big of gap between section headers and their content (IE6/IE7 problem -- works fine in Chrome/Firefox/IE9) - Services: MMS/Voice to Text/ - Current carrier only cares about whether Telstra or not. New connections can only be done with Telstra. Need some kind of message if they say that they're not with Telsta. - "Is your current carrier telstra?" Yes/No - "Would you like to switch to Telstra?" Yes/No DO NOT INCLUDE "Mobile Email Device" section of pdf in the mobile form - When the user selects an iPhone and new asset, the services selection has a note that says "There will be a 2 year plan at $39 per month for 4GB" - iPhones require level 3 approval - Two divisions: TSO and FNC (Finance & Corporate) -- when swish gives the division - Need a type ahead that pulls company divisions from the database - If swish pulls a division that exists in the database, use it, otherwise show a select box of the ones in the database (basically have the select default to the swish one) - When iPhone TSO and FNC, requires level 2 manager. (level 2 are executive managers -- managing entire divisions -- TSO: Fake Name, FNC: Fake Name 2) - (Any requests for TSO and FNC require level 2 manager) - When form submitted, send an email to manager Emails will include login codes that go straight to the approval/decline page of the request Basically a "You have to approve or decline a new request" Approvals are item by item (can approve an iPhone and not a charger for example) Might eventually have approval grouping where you can either approval 2 items or deny 2 items but cannot separate them Once approved email the employee and tell him - Leanne processes the forms and will thus need a list of all of the approved ones. It should be a page that AJAX refreshes every so often so she doesn't have to be bombarded with emails yet can still see live updates - Leanne does not want to advertise this fact, but 10 users ("bulk order users") will have access to the special version of the form -- if the service number on the first page is one of theirs - Only applies to phones - Can just ask a count after the phone selected - Probably only allowed for Nokia C5 (will need ACLs on which devices the user can place bulk orders on) - If it's a replacement, the employee's supervisor can approve it - Approver asked -- Type ahead like on traveltime - Footnoot of which level is required (depends on device) - Need the approval inputs between Request Type and Services sections - Type ahead for approver unless it's TSO in which case there's only 1 employee