Users 
Description
Attribute Names for USERS
Attribute |
Required/ Optional/ Multiple |
Description |
[Member] |
Required |
Any expression in square brackets serves as delimiter to separate user records Example 1: [Member] Example 2: [User] Empty lines are skipped and are not treated as delimiters. |
Org_ID |
Optional |
Name of the company to which the user belongs. The company must exist. |
UID |
Required |
ID that the user uses to log on. |
Password |
Optional |
If no password specified, the application generates a password.
User creation may fail if the password does not conform to the security policy. |
Role |
Optional, multiple |
Role being assigned to the user. If the role does not exist, a warning will be generated. |
$usermapping$:<system_alias>:user |
Optional |
User ID to which the user is mapped in the system <system_alias>. <system_alias> is the system alias as defined in the portal system landscape editor. See System Landscape. |
$usermapping$:<system_alias>:mappedpassword |
Optional |
Password of mapped user in system <system_alias>. <system_alias> is the system alias as defined in the portal system landscape editor. See System Landscape. |
$usermapping$:<system_alias>:<attribute_name> |
Optional |
Any other attribute value required by an external system <system_alias> to which the user is mapped. <system_alias> is the system alias as defined in the portal system landscape editor. See System Landscape. |
<namespace>:<name> |
Optional |
Additional field in the form: namespace:name=<text_value> By default the value is interpreted as a text value. If you want to use a binary value, you must use the base64 encoded value with the prefix {BINARY}. Example: myApplication:largeUserPhoto={BINARY}h&%AShja4zu8923h(=!&62h345kljhs |
Email_Address |
Required |
The user’s email address |
First_Name |
Required |
self-explanatory |
Last_Name |
Required |
self-explanatory |
Job_Title |
Optional |
self-explanatory |
Country |
Optional |
self-explanatory |
Language |
Optional |
self-explanatory |
Time_Zone |
Optional |
self-explanatory |
Currency |
Optional |
self-explanatory |
Street |
Optional |
self-explanatory |
City |
Optional |
self-explanatory |
State |
Optional |
self-explanatory |
ZIP |
Optional |
self-explanatory |
Telephone |
Optional |
self-explanatory |
Fax |
Optional |
self-explanatory |
For the telephone, fax and mobile phone fields, the following rules apply:
· Valid characters are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, (, ), +, /, -, SPACE
· Open bracket ‘(‘ and closed bracket ‘)’ must be in pairs
· ‘+’ must be the first or second character (after a leading open bracket ‘(‘). For example:
· +1 650 123-4567
· (+1) 650 123-4567
· 1+ 650 123-4567 is not valid
Example
The following is an example of users in standard format.
[User] |
The following example shows how you can change the user mapping data of an existing user, user2. When you import the data, choose the option Overwrite Existing Data in the import tool.
The user user2 is mapped to the user ID ext_user2 in the system BCE, where BCE is the system alias of the system defined in the portal system landscape.
[User] |