Bookshelf Home | Contents | Index | PDF     

Application Guide for Oracle Self-Service E-Billing (Consumer Edition) > Enrollment and Login Use Cases >

Logging In

In this use case, a user logs in to the Web site to access Oracle Self-Service E-Billing. Table 5 lists and describes the use case functions.

Table 5. Logging In
Functions
Description

Name

Logging In

Functional Area

User Management

Primary Users

Consumer user

Trigger

The user navigates to the Login page by entering the URL into a supported browser or user follows a link from service provider's landing page available to all anonymous users.

Standard Features
  • Validation of the user name and password input.
  • Authentication of the user name and password.
  • Enroll as a new user link.
  • Disclaimer text and standard footer links.

Configuration Points
  • Validation rules for user name and password:
    • User name: The user's telephone number (the default). An alternative user name can be the user's first initial and full last name when not logged in using a phone.
    • Password: (Default) Must be at least six characters and must contain at least one uppercase letter, one lowercase letter, and one number to comply with Sarbanes-Oxley guidelines.
  • Ability to force users to change their passwords at first login if the user name and password were created by a CSR or a company administrator.
  • Parameters can be passed through the URL with a secure token that contains the preferred language, currency, and market segment information to personalize the user's experience. For example, if a user has changed the language preference on the service provider's consumer portal page, the Login screen must be presented in the same language, if available, and set for the remainder of the user's session until changed by the user.
  • Ability to bypass the Login screen to use single sign-on (SSO) applications (for example, Siebel CRM, Oracle Identity Manager, CA SiteMinder or other third-party application). Along with the Login information, the user's language and currency preference can be passed to Oracle Self-Service E-Billing to set user preferences.

Main Path for Logging In

The main path to log in is as follows:

  1. The user enters login information:
    • User name
    • Password
  2. The user clicks Submit.
  3. Oracle Self-Service E-Billing validates data and identifies the user's data access and permissions:
    • Vertical. The type of vertical application, either Telco or Utility.
    • Market. Consumer
    • Role. Determines permissions
    • Access. Data access
  4. Oracle Self-Service E-Billing displays the default page determined by the user's attributes (Vertical, Market, Role, Method, Access, and Language).

Alternate Paths for Logging In

This use case can have various alternate paths.

  • The customer attempts to log in with invalid credentials.

    The UI displays the following message: The sign-in information you have entered does not match what we have on file, Please reenter your sign-in information.

  • Oracle Self-Service E-Billing prompts the user to enter a valid email address due to undeliverable notifications:
    1. After the user logs in successfully, Oracle Self-Service E-Billing displays the following message: We are unable to confirm delivery of email notifications using the address in your personal profile. Please enter the email address you would like to receive billing related notifications.
    2. The user enters a new email address, enters the email address again to confirm, and then clicks Submit.
    3. Oracle Self-Service E-Billing verifies that email addresses match and are valid, prompting the user to reenter if necessary.
    4. The following message displays: An email notification has been sent to the email address you have supplied. Please follow the link in the message to complete the validation.
    5. The user clicks the link provided in the email message, which displays the Login screen where a message states: Thank you! Your email address has been successfully verified.
The user clicks the Enroll tab

The UI displays the Enrollment use case.

Exceptions for Logging In to the Billing and Payment Application

Exceptions can occur with this use case.

The User Does Not Click the Verification Link in Email After Entering a New Email Address

If a user entered a new email address in the alternate scenario where she had undeliverable notifications, and if she does not click the validation link in the new notification she receives, then that alternate scenario is repeated.

    
Application Guide for Oracle Self-Service E-Billing (Consumer Edition) Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.