Requirements File Name: reg_new_reqs.html
New Registration Page Requirements
 
Change Log
Version Date Author Changes Notes
1.0 11/07/2006 Kevin Puleo Added requirements  
2.0 12/18/2006 Kevin Puleo Changed requirements based on apix strategy  
2.1 1/23/2007 Kevin Puleo Added a "my phone is not supported" form item  


Introduction
This page allows non-apix users to start the process of joining the community. Step one of this process is represented on this page. This step helps mlab identify if the user's phone is capable of handling the apix client. If it is capable then Mlab steps through how the user can find the client on their carrier's deck.

Requirements
All items represented in the registration form on this page are required. Validation of the form happens once the submit button is selected. Once submitted all elements are stored in a separate marketing DB that is not connected to the registered user DB. The information submitted is not used for registration purposes. It is only used to see if the phone is acceptable. Therefore we need to capture the user's information while we have their interest. If they only fill in this information we can ping them at a later time to come back.

The marketing DB of email addresses must be cross checked daily with the actual user DB to see if the email address in the marketing DB has been used to register as an apix user. If the address hasd been used that user should never be sent a message asking them to come back. The DB also needs to store whether or not the person's phone was compatible with aPix or not.



Top Intro
Selecting the privacy link in the intro area will take the user to the privacy page thereby leaving the registration page



The Form (Top to Bottom)
All form elements shuld be validated and stored in a separate Marketing DB.

  1. Email
    1. Required text field
    2. No character max on input
    3. Validation
      1. There must be an @ symbol in the string
      2. There must be a valid "dot" extension in the field like .com, .org, .net, etc.
    4. Possible Errors
      1. Empty field
      2. no @ symbol
      3. improper extension
Mobile Information
All of the following inputs are required once the user goes down the path of entering their phone information. The "click here" link to learn more about th mobile capabilities will be a pop-up and will not take the user to a new page. It will explain in marketing terms why they should enter their phone information.
  1. Carrier
    1. Required pulldown
    2. The actual items in the pulldown are carriers that FM and aPix support, they could include things like: Cingular, Verizon, Sprint, etc. - "Select..." is the default selected state
    3. Validation
      1. The user must select something besides "Select..."
    4. Possible Errors
      1. None if left in its default state
      2. If other fields have been touched in the mobile information area then there will be an error if left in its default state. However, this error will be very rare based on how this portion of the form works
  2. Phone Make
    1. Required pulldown only if Carrier has been changed from its default state - This pulldown remains disabled and unpopulated until Carrier is changed. Based on what carrier is selected then the pulldown gets populated with the relavant phone makers for that carrier that FM and aPix support
    2. The actual items in the pulldown could include things like: Motorola, Sony, Nokia, etc. - "Select..." is the default selected state
    3. Validation
      1. User selects something besides "Select..."
    4. Possible Errors
      1. Left on the "Select..." selection
      2. The user submits the form before completing the rest of the mobile information
  3. Phone Model
    1. Required selection only if Phone Make has been changed from its default state - This area remains disabled and unpopulated until Phone Make has been changed. Based on what Phone Make is selected then the area gets populated with all of the relavant phones from that maker for that carrier that FM and aPix support
    2. The actual items in the area could include the image and model name of the phones
    3. Once a phone has ben selected all other phones are removed from the display except the selected model. If the "I don't see my phone" checkbox is selected then all of the phones are removed leaving only that checkbox. Unchecking the box will reveal the phones again.
    4. Validation
      1. User selects something besides nothing
    5. Possible Errors
      1. Nothing is selected
      2. The user submits the form before completing the rest of the mobile information
  4. Phone Number
    1. Required selection only if a Phone Model has been selected - These text fields remain disabled and unpopulated until a Phone Model has been chosen.
    2. Area Code text field - 3 characters min and max, only numbers are accepted
    3. Phone number prefix text field - 3 characters min and max, only numbers are accepted
    4. Phone Number Suffix text field - 4 characters min and max, only numbers are accepted
    5. When the user finishes entering 3 digits/characters in the first text field they are automatically tabbed to the next text field. After they have entered 3 digits/characters in the second field they are automatically tabbed to the last/thisrd text field
    6. Validation
      1. User enters 10 digit phone number
    7. Possible Errors
      1. Nothing is entered in one or more fields
      2. Character min max has not been met in one or more fields
      3. Unsupported characters are detected in one or more fields
      4. The user submits the form before completing the rest of the mobile information
  5. Mobile Terms and Conditions
    1. Required checkbox button
    2. One checkbox where the user chooses between accepting or not
    3. Unchecked as default
    4. The Link in the question does not take the user to a new page if selected, rather it opens an iframe/div below the checkbox area that loads and allows the user to read the T&Cs. The reading area should be 100% wide and about 250px high
    5. Validation
      1. Must be checked to continue
    6. Possible Errors
      1. Left unchecked
  6. Verify Phone Submit Button
    Once this button is selected all of the form elements are validated. If the form validates then the user is taken to step by step process of showing the user where they can find the apix client on their carriers deck.. If the form does not validate then the user is shown the same form again with their inputs but the errors are called out inline with the form. Click here to see an example error page. Once the form validates all of the form elements get stored in the marketing DB.
  7. Browser Back Button - selecting this will cause a form error
    1. The error page should say that they cannot modify anything and that they need to go to the next page - actual messaging TBD