The DirXML-nwoWorkOrder object (sometimes referred to as the work order object) is used to tell the driver what tasks to perform in the PBX and to allow the driver to record the results.
If your configuration is intended to update phone information for user objects after PBX tasks are complete, the ObjectID attribute must be filled in correctly on every work order. For example, in the workforce tree configuration explained in Section 7.0, Workforce Tree Configuration, the ObjectID is used to find and update the User object in the Identity Vault, which can subsequently be used to update phone information for the employee in the human resources application. The ObjectID allows this flow of information to take place. Without it, the driver can perform the work order in the PBX, but no user information is updated afterward.
The Avaya driver has two flags to initiate a work order event.
DoItNowFlag When this flag is set to True for a work order, the Subscriber wakes up the Publisher by sending the work order to the Publisher. The Publisher performs the task immediately instead of waiting for the next polling time or polling interval.
This flag is useful in a situation where you want the work order to be completed right away. You can set this flag to True when you manually create a work order, or in an automated solution you can use policies to determine whether the flag should be set. For example, you could configure the driver to set the DoItNow flag to True for an incoming work order if a corresponding attribute is set in a work order database. As another example, you could configure the driver to set the DoItNow flag to True if an Install work order is triggered by a new user in a human resources application.
SendToPublisher Flag When this flag is set to True for a work order, the Subscriber sends the work order to the Publisher, and the Publisher writes the work order object in the correct container according to the work order container specified in the Configuration Parameters.
This flag is not necessary in implementations where the work order object is created in the Identity Vault by an administrator (as in Section 6.0, Base Configuration) or an application (like the solution described in Section 8.0, Work Order Database Configuration).
This flag is useful when the work order is triggered by another Identity Vault event through the use of a policy or style sheet, and the work order does not yet exist in the Identity Vault as an object. This kind of scenario is described in Section 7.0, Workforce Tree Configuration.
The following table shows the required attributes for a work order that you do need to specify:
Table B-2 Required Work Order Attributes That Must Be Specified
The following table shows all of the attributes for a work order:
Table B-3 nwoWorkOrder Object Attributes
The following table shows the pbxWorkOrder association: