Like the base configuration, the workforce tree configuration is meant to be instructional, and to demonstrate what the driver can do. It is not meant to be an out-of-the-box solution.
In contrast with the base configuration, rules are in place in the workforce tree configuration to maintain the relationships between users in the workforce tree and extensions in the PBX. For example, changes to users cause appropriate work orders to be created. And, when an extension is assigned in the PBX, the phone number is added to the user object’s attributes.
In some implementations, you should connect to an existing work order database so that the Identity Manager Driver for Avaya PBX can perform work orders from a system that is already in place. The workforce tree configuration does not demonstrate this functionality. This aspect of how the Avaya PBX driver is explained in Section 8.0, Work Order Database Configuration.