...
When the "New username duplicate handling" setting is set to "Append counter", an auto-increment counter will be appended to duplicate usernames produced by the template. For example, if the CSV file contains the users named John Doe, Jane Doe and Jenny Doe without explicit usernames, the default username is %-1f%-l and New username duplicate handling is set to Append counter, then the usernames produced will be jdoe, jdoe2 and jdoe3.
| Info | ||
|---|---|---|
| ||
User Mapping & "Strict" ControlYou can now specify a different "key" other than username when updating users. This is useful in the event that your HRIS does not track the user's username, which is typically only in Active Directory. You could for example user use this feature to upload users by using their Employee ID as demonstrated in the screenshot below. If you do not have the username in the CSV file when uploading users, simply map the column from the CSV file to the database column in the learning environment using the "User mapping" option in the "Upload users" wizard. Note that the username is still required when creating users and as such, this feature is only available when updating users. New in 3.5.8.2. If you enable the "Strict" option, the user mapping will ONLY be done on the Employee ID in the example below. In other words, if the Employee ID in the CSV file does not match an Employee ID in the database, then the system will skip the user. If the "Strict" option is disabled, the system will first attempt to match the users by Employee ID and if it doesn't find a match, it'll then make a second attempt and try to match the skipped users by mapping the username in the CSV to the username in the database. (Note that the username is still required when creating users and as such, this feature is only available when updating users.)
|
Deleting Accounts
...