Specify the following settings when you create or edit
a user.
Canonical Name: (Mandatory) Unique identifier for the
user. Each user and group in a domain must have a unique canonical
name. Select the System Generated checkbox to let User Management
assign a unique value, or clear the checkbox and specify a custom
value for the Canonical Name.
Avoid using underscore characters (_) in canonical names, for
example, sample_user. When you search for users
based on their canonical name, those containing underscore characters
are not returned.
First Name: (Mandatory) User’s given name
Last Name: (Mandatory) User’s family name
Common Name: Full name or display name for the user. For
example, if First Name = Gloria and Last Name = Rios, then Common
Name = Gloria Rios.
Email: User’s email address
Telephone: User’s telephone number
Description: Optional description. Use this field as suits
your organization’s needs.
Address: User’s mailing address
Organization: Organization to which the user belongs
Email Aliases: User’s email aliases. Separate the email
aliases with commas.
Domain: Domain to which the user belongs
Locale: User’s ISO locale
Business Calendar Key: Enables you to map a business calendar
to a user, based on the value for this setting. Business calendars
define business and non-business days. LiveCycle can use business
calendars when calculating future dates and times for events such
as reminders, deadlines, and escalations. The way that you assign
business calendar keys to users depends on whether you are using
an enterprise, local, or hybrid domain. (See Adding domains.)
If you are using a local or hybrid domain, information about
users is stored only in the User Management database. For these
users, set the Business Calendar Key to a string. Then map the business
calendar key (the string) to a business calendar in Process Management.
If you are using an enterprise domain, information about users
resides in a third-party storage system, such as an LDAP directory.
User Management synchronizes user information from the directory
with the User Management database. This feature allows you to map
a business calendar key to a field in the LDAP directory. For example,
consider a scenario where each user record in your directory contains
a country field, and you want to assign business calendars based
on the country where the user is located. In this case, you specify
the country field name as the value for the Business Calendar Key
setting. You can then map the business calendar keys (the values
defined for the country field in the LDAP directory) to business
calendars in Process Management.
For additional information on business calendars, including how
to map business calendar keys to business calendars, see Configuring Business Calendars.
Limit the name to less than 53 characters. A shorter name helps
prevent problems displaying the business calendar key in the Process
Management pages in Administration Console.
User ID: (Mandatory) User ID that the user uses to log
in. User ID is not case sensitive and it must be unique across the
domain.
In enterprise domains, use a non-DN attribute as the user ID
because a user’s DN can change if they move to another part of the
organization. This setting depends on the directory server. The
value is objectGUID for Active Directory 2003, nsuniqueID for
Sun™ One, and guid for eDirectory.
Ensure that the user ID is unique. Do not use one that was assigned
to a deleted user.
LiveCycle cannot differentiate between user accounts that have
identical user IDs and passwords but belong to different domains.
To avoid this problem, do not create accounts that have the same
user ID on multiple domains.
When using SQL Server as your database, you cannot create a user
ID that exceeds 255 characters.
When using MySQL, the user ID can contain extended characters.
However, when a comparison is made between two strings, such as
abcde and âbcdè, they are considered the same. For example, when
syncing, if a new user was added to the database, a comparison is
made to check whether a user with the same user ID exists in the
database. If user abcde already exists in the database when
the new user âbcdè is added, the comparison cannot distinguish
between the two names. It is assumed that the user already exists
in the database, and the new user is ignored and not added.
Avoid creating user names that begin with a number sign (#).
Performing task searches returns no results for those user names.
(See Working with tasks.)
Password and Confirm Password: Password the user uses
to log in. It must have a minimum of eight characters. A password
is not required for a user who is part of a hybrid domain.
