https://wellsoffice.wellsfargo.com/ceo_public/tutorial/ceo_portal_overview/player.html
Event msging:
Event msging:
·
When a notification is successfully scheduled to
be sent to a user, the system records that the notification was successfully sent. This enables it to resend notifications
that were not successfully scheduled, the next time it processes notifications.
eg: User’s password will be disabled in 10 days
·
This use case describes how the system (CEO)
allows a CEO user to manage their user profile. The user profile includes contact information, secret questions and answers (SQSA),
and certain system or application preferences. If the user does
not provide the additional authentication correctly within
the allowed number of attempts, the user’s session may be ended
and they may be blocked from further access to CEO
system (CEO) authenticates a CEO user using two-factor
authentication (2FA). CEO currently supports two types of 2FA:
Token verification using a PIN and token from a fob (SecurID) device
Secure Validation where a one-time code (OTC) is sent to a user by an automated
phone call or text message, and
then entered by the user, the system checks if the user’s
enrollment in it is complete. If enrollment was started in this session
but is not complete, the system directs the user through completion of
enrollment.
When Secure Validation is required, the system prompts the
user to select how to deliver the Secure Validation one-time code. The user selects one of the phone numbers set up
in the Secure Validation preferences, and whether the code is delivered by a recorded message in a voice call or by a text
message.
The system sends the Secure Validation one-time code using
the delivery option selected by the user and prompts the user to enter it. If the user enters the correct code within a
specified time limit, authentication succeeds and they are allowed to continue with their requested task. If the user
does not enter the code within the time limit, it is treated as an invalid entry. Consecutive, invalid entries beyond a
limit will terminate the session and block the user from future access to CEO without help from customer service.
When token verification is required, the user is prompted to
enter the token value and a PIN. The system may require the user to set their PIN if it has not been created yet, or
reset it if it has expired.
If the token and PIN are entered correctly within the number
of specified retries, the user is allowed to continue with their requested action. If the token and PIN are not
entered correctly within a certain number of attempts, the user’s session will be terminated and they will be blocked from
future access.
·
how the system (CEO) allows a CEO user to launch
one of their CEO services. A user may launch a service directly or may
·
launch a service indirectly by requesting direct access from
CEO Home to the service or one of its features.
When a service is launched, the system checks for outage or
impairment of the service first to make sure it is available.
The system also checks if the user is authorized to use the
service or feature at the time it is requested, in case an
administrator has changed the entitlements to the service
while the user was in session. In some cases, 2-factor
authentication may be required before a service may be
launched.
A service splash page may be presented when a service is
launched. For services that use Automatic Access, a splash page
to set the Automatic Access preference of that service is
presented under certain conditions. Service splash pages can be
targeted in various ways, similar to system splash pages.
Once the service is launched, the user may perform various
actions supported by that service. This use case provides an
extension point for use by use cases in various services.
A bank operator may act as a perusal user if they are
perusing a customer. They may attempt to launch a service, but in
general are not allowed to actually launch a service.
CEO shall present a splash page during launch of a service
when the following criteria are satisfied:
- user has not already viewed a splash page for
this service in the current session
- user launched the service directly and did not
request a specific feature of the service
- this splash page is to be displayed to all
users, or the company ID and user ID of this user have been targeted to
receive the splash page
- if there is a maximum number of times to
display this splash page, user has not viewed it the maximum number of times
- user has not viewed this splash page
previously and indicated to prevent its display in future sessions
When a splash page is presented CEO shall:
- increment the number of times a user has
viewed it
- require the user to explicitly take action on
it before continuing to the service
- for splash pages providing this option, record
a user’s selection to prevent the splash page from being presented when
the service is launched in the future
- for splash pages providing this option, allow
the user to be reminded of the same choices at some point in the future
when they launch the service
- for Automatic Access splash pages, when a user
selects to enable or disable Automatic Access, record this selection in
the preferences in their user profile
The Automatic Access splash page is provided only when the
Auto Access preference is not set, and user has a single product
that is fully integrated with CEO. When a service requires
an Automatic Access splash page, it takes precedence over all
other splash pages for that service.
If the system is unable to display a splash page, it shall
ignore this error and continue.
·
CEO shall provide the ability to search for
checks when a user provides an account number and at least one of the following
·
criteria, subject to constraints defined in the rest of this
rule:
- check numbers (single value, range of values,
or list of up to 20 values)
- amount (single value or range of values)
- posting date (single value or range of values)
·
For users entitled to Self Administration, CEO
shall provide search for a user by user ID
*perform one of the following
(when authorized) for a user found through such a search
-
reset password
-
edit user profile
-
edit product access
*add a new user
*ability to enable
online activation of services for their company
- for users receiving either the legacy
experience or new experience display the number of tasks in the company’s dual
custody queue as follows:
*if the company
has Group Management, display the number of tasks in the company’s queue minus
any requests that
were initiated by that user
*if the company does
not have Group Management, display the number of tasks the user may take action
on
*display no value
if the number that would be displayed following these rules is zero
If a user’s company has dual control enabled and at least
one task awaits disposition, the system shall provide access to
the dual custody queue in Self Admin to disposition
them.
The system shall allow a user to perform actions described
in this rule only for users with the same company ID as the user
initiating the action.
The system shall also provide an indication when Self
Administration is unavailable or impaired and provide error messaging
when actions fail as described in the table below.
Introductory content about this capability shall also be
presented the first time it is viewed.(legacy experience only)
·
wires:
wire type is one of: Domestic, International, Federal Tax
Payment, Book Transfer, Drawdowns, International Request for Transfer
- wire has not been rejected or already approved the
number of times required
For each wire in this list, the system shall provide:
- summary information about the wire:
*value date-template
name
*type of wire
*debit account
number
*amount and
currency
*beneficiary
*beneficiary
account number
*status
- access to detailed information about the wire
- ability to approve or reject one wire at a
time from this list
*when rejecting a wire,
a rejection reason (35 characters) is required
The system shall include consumer (Dodd-Frank) wires in this
list but shall not allow their disposition from CEO Home. If a user
attempts to disposition one of these wires, the system shall open the Wires
application if the user is authorized to view or disposition it.
The system shall allow a user to manage this list of wire
tasks as follows:
- sort in ascending or descending order, for any
field displayed
- filter by type of wire
- refresh contents of list (with updated
timestamp or message on error)
- default is sorted ascending by value
date-template name with no filtering
When attempting to disposition a wire, the system shall
first require a user to authenticate using token validation if this has not yet
been done in the current session. There will be a message when there are
no wires (CEP189).
When no wires for a user’s company are waiting dispositioning,
the number of wires and list of tasks are not displayed.
The system shall provide confirmation (XXX ) i a wire is
successfully dispositioned, notices if the Wires service is impaired or
unavailable, and messages defined in the table below.
The system shall also provide direct access to the approval
queue in the Wires service