Lucent Technologies INTUITY Messaging Solutions Enhanced-List Application 585-310-575 - Manual (Page 47)

Guidelines for Naming Enhanced Lists
Issue 1 July 1997 37
3. Press (F3) to save the ELA server information to the system
database.
The system displays the message “ Successfully Updated! ” and asks
you to press F1 acknowledge the message.
4. Press (F1) .
The system redisplays the Enhanced List Manager menu.
5. Continue with the next procedure or press (F6) repeatedly to
return to the main menu.
Guidelines for Naming Enhanced Lists
We recommend that you use the following guidelines when you name an
enhanced list. These guidelines can help prevent users from inadvertently
sending their messages to the enhanced list, instead of to a person.
■
Do not use embedded spaces in the name. If you would like a list to be
called Marketing Department, type it
Marketing_Department_LIst .
■
Avoid naming an enhanced list after a person. I NTUITY Message Manager
does not differentiate between an enhanced list and a person’s name.
Examples of names to avoid:
— Jane_Doe
— Doe_Jane
DEFAULT ENHANCED-LIST
MAILBOX ATTRIBUTES
Class of Service:
Valid Input:
a number from 2 to 11
Enter the number of the COS assigned to the enhanced-list
mailbox and the shadow mailbox.
ELA uses this COS number when you create new enhanced lists.
DEFAULT ENHANCED-LIST
MAILBOX ATTRIBUTES
Community ID:
Valid Input:
a number from 1 to 15
Enter the number of the community assigned to the
enhanced-list mailbox. This cannot be the same number as the
shadow mailbox Community ID.
The enhanced-list mailbox community must be administered to
be able to send messages to all other communities and receive
messages from the community(ies) containing users with access
to enhanced lists. See "Setting Up ELA and Shadow Mailbox
Community IDs" on page 3-19.
Table 4-1. Field Definitions: Set Up Enhanced-List System Data Window — Continued
Field Name Description/Procedure
Continued on next page
SAVE
ACKNOWLG MESSAGE
CANCEL