After performing a work order, the driver can update a user’s information with the results. For example, the driver can add a new extension to the user's list of phone numbers, or remove an extension that has been deleted, as described in Section 7.0, Workforce Tree Configuration.
This functionality works for new and existing users, if the following conditions are met:
The user exists in the Identity Vault.
The policies support updating a User object after performing a work order.
The correct ID for the user object is entered as the ObjectID in the pbxWorkOrder object.
The ObjectID in the work order is what allows the driver to update the user object when the work order is complete.
This means that your ability to manage existing users (perform work orders for their extensions and update their phone information after a work order is performed) is dependent on the accuracy with which the ObjectID is specified in the work order. This is a contrast to some other Identity Manager drivers, which require the user object to have an Identity Manager association with the driver before you can manage existing users.
Unlike some Identity Manager drivers, it is not necessary to use the Migrate into NDS command before being able to manage existing users. In fact, for this driver, the Migrate into NDS command does not affect user objects (unless you create custom policies or tools to do so).
The Migrate into NDS command allows you to import data from an application into Identity Vault. For the Identity Manager Driver for Avaya PBX, the Migrate into NDS command causes all extensions that are configured in the PBX to be created as pbxExtension objects in eDirectory™.
This action does not create associations between existing User objects in eDirectory and existing extensions. However, this list of existing extensions could be used for the following purposes as part of a manual effort or with custom tools you create:
In the PBX, inserting the ID for the User object who uses each extension
When the driver configures an extension, it automatically enters this information in the PBX, using the ObjectID you specify in the work order. However, for existing extensions, the data might not have been filled in correctly.
This is useful if the PBX admin will continue to make changes manually to extensions, as well as using the driver to perform work orders.However, keep in mind that any manual change must include adding the ObjectID in the PBX, or else the driver won't know which user object to update.
You can write a policy for migrating User IDs to the PBX based on their extension numbers. You can also migrate all User objects from eDirectory. To do this, set up a migration policy that creates work orders that modify ObjectID’s based on extension numbers. When the migration policy has finished, change the policy to something you want for normal operations.
Checking the accuracy of existing phone information listed for users in Identity Vault
Although the driver can add, change, or remove phone extensions listed for an existing user object after it performs a work order, it does not verify that the extensions already listed for the user are correct. So, if an incorrect extension is entered manually, that data entry error remains even after you start using the driver.
If you want to make sure that existing phone information listed for users is correct, you can compare the pbxExtension objects with the user objects by looking at the Display Name in the pbxExtension object. If display names are created with some consistency, you might be able to use a tool to match up many of the extension objects with user objects. However, some manual work is probably still required to match all of the extensions, because of duplicate employee names (such as two people who are both named John Smith) or inconsistent format of display names that were entered manually.
Check the PBX for unassigned extensions.
You can use the nwoExtension object to find out whether you have extensions that need to be disconnected but the physical task was never completed.
Check the display name of extensions.
You can check to make sure display names are filled in and are following any applicable corporate standards.
Populating eDirectory with User objects
This might be an option for you if you are fairly confident in the information that is in the PBX, and you are creating a new eDirectory tree and want to populate it with users based on the users represented in the PBX. You can do this through a policy set up as you migrate User objects to eDirectory.