This configuration would be appropriate to import and configure in a test environment for instructional purposes, to help you learn how to configure the solution you need. It is not meant to be an out-of-the-box solution.
The rules and policies in the base configuration are set up so that you can create work order objects (using a new object class, nwoWorkOrder) in a Work Order container, and the driver will perform the work orders in the PBX and show the results by creating a pbxExtension object and updating the nwoWorkOrder object in eDirectory.
Most real-life implementations would want User objects to be updated when an extension is assigned or changed, but to keep the configuration sample as simple as possible, the base configuration does not include rules to do this. Instead, pbxExtension objects are used to represent extensions, and User objects are not affected by the changes.
To see how user objects can be involved in the process, review the workforce tree configuration, explained in Section 7.0, Workforce Tree Configuration.
Similarly, the base configuration does not demonstrate a connection between eDirectory and a work order database. In implementations that have an existing work order database, you should connect to it so that the Identity Manager Driver for Avaya PBX can send and receive work order data. This connection could be made using another driver such as the Identity Manager Driver for JDBC*. This kind of implementation is described in Section 8.0, Work Order Database Configuration.