Workforce Tree Configuration

The workforce tree configuration demonstrates how the driver can be configured to provision users in the PBX system by doing the following:

• Assigning an extension to new users by creating a work order when a new user is added
• Enforcing business policies about phone use restrictions, based on user attributes
• Performing work orders to install, modify, move, disable, or disconnect existing extensions, based on user events such as change in location or job status.
• Updating user objects with new phone extension information to reflect changes made in the PBX.

Like the base configuration, the workforce tree configuration is meant to be instructional, used 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, in the workforce tree configuration, rules are in place to maintain the relationships between users in the workforce tree and extensions in the PBX. For example, changes to users will 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 will want to 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 intended to be used is explained in Work Order Database Configuration.

In this section:

• How the Workforce Tree Configuration Works
• Planning for the Workforce Tree Configuration
• Using Log/Reporting Functionality to Report Warnings