This was the first catalog item under development, and it has gone through several loose definitions. We finally have something resembling a spec in the last week of January 2013.

There are three modes of use for Mobile Device:

1) add new device / service
2) change device / service
3) delete service / device

Add new device / service

we should use requirement 46 for this

Fields to collect from user

user currently logged into ServiceNow (this is obviously implicit in the form)

person who will be using the service / receiving the mobile device (this is a reference form to lookup in SN; common throughout the system; default it to the person currently logged in)

physical address where the user would like to receive the physical device. This should be an open-formal text box, no enforcement that it be completed. There is already an address implicit in the person form, as users have an address.

pick a provider: there are four vendor choices, 'none' should also be a choice

pick a device: this should be an open comment field; users should go to their preferred vendor website and pick their preferred device. We may wish to give some advice in the Help field.

pick a data / phone plan: this should be a reference lookup against an internal table, and the maintenance of the data itself needs to be delegate-able to other people; the functionality already exists from previous versions.

2 ptaeos
- ptaeo for one-time costs
- ptaeo for recurring monthly charges

Change device / service

this should be a new requirement

Fields to collect from user

phone number for existing service

plus all the same fields as add service / device

Delete device / service

this should be a new requirement

Fields to collect from user

user currently logged into ServiceNow (this is obviously implicit in the form)
phone number for existing service
person who will be using the service / receiving the mobile device (this is a reference form to lookup in SN; common throughout the system; default it to the person currently logged in)