Requirements File Name: reg_stepXstep_reqs.html
Registration Download Step X Step 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  


Introduction
This page allows non-apix users to start the process of joining the community. This step helps users find the Apix client on their carrier's deck.

Requirements
If the user's phone is validated as an eligible phone for the Apix client then based on the "Carrier" entry from the form input this page displays in a step by step process how the user can find the Apix client and download it from their carrier's deck. If the user finds the client and downloads it right away and also registers their new application then they can also sign-in on the web as well from this page.



The Sign In Form (Top to Bottom)
The Apix module will have a username and password form. The user will be instructed to enter their APix FM Universal Login information. Once the submit button is clicked the form will be validated and the contents will either be accepted or rejected. NOTE: The submit button may become an image rather than a standard submit button but this will be deternmined during the UI/Design Phase.
  1. Username
    1. Required text field
    2. No character max on input
    3. Validation
      1. All characters accepted
    4. Possible Errors
      1. Empty field
      2. spaces
      3. improper input
  2. Password
    1. Required text field
    2. 6 character minimum on input
    3. 20 character max on input - no spaces allowed
    4. Symbols and alphanumeric text inputs will be taken
    5. On input the characters are masked in the iput field to look like this
    6. Validation
      1. No spaces
      2. Between 6 and 20 characters
    7. Possible Errors
      1. Empty field
      2. Less than 6 characters entered
      3. Spaces were used
  3. Submit Button
    1. If accepted the user is taken to their profile page.
    2. If rejected, the system will display a message by the submit button without refreshing the page that their password could not be validated. The user will only be allowed three rejections before a contact customer service notice is displayed. At this point the user may contect customer service for help.
Accepted
If accepted, the user will be taken to their profile page.

Rejected
If rejected, the system will display a message by the submit button without refreshing the page that their login is incorrect. The user will only be allowed three rejections before a contact customer service notice is displayed. At this point the user may contect customer service for help or select the "forgot password?".

"Forgot Password?" Link
If the user select the "forgot password?" link then they will be taken to a new page where they will be prompted to enter their email address that they used to register the account with. After they enter their email in the form and select the submit button. The message will change to say that their password has been emailed to their xyz@email.com account (where xyz@email.com is the email adress entered by the user in the form). The email the registrant receives should look something like this:
  1. Email contains: Example: “Dear Username, You have requested that your login information be emailed to you. Your Login: Username and Password: password. Please do not reveal this information to anyone. Thanks, MLab Staff”
  2. A value proposition message/site feature should be delivered to the user in content of email.
Once the user recovers their password then they can begin the registration process again.