The driver can be configured to create work orders based on creation of or changes to a User object, as discussed in Section 7.0, Workforce Tree Configuration.
Two existing attributes of a User object are used in the workforce tree configuration. Because these attributes already exist in the eDirectory schema, the schema extension that is part of the driver installation does not make any changes to User objects.
User objects receive an Identity Manager association for the driver when they are sent to the Subscriber channel. The table below shows the value of the association for a User object.
Table B-8 User Object Association
|
Driver |
State |
Association |
|---|---|---|
|
AvayaPBXDriver |
Associated |
/PBXName/WorkOrderCommonName/Time |
You might expect that the association for a user object for the Avaya PBX Driver is the phone extension. However, this is not the case. The association for the user object is made before a work order is performed. For a work order to install a new extension, the number of the new phone extension is not known until the work order is performed, so the extension can’t be used.