Workorder Driver Policy; Human Resource Example Without An Hr Driver - Novell IDENTITY MANAGER 3.6.1 - WORKORDER DRIVER IMPLEMENTATION GUIDE 18-12-2009 Implementation Manual

6.2.2 WorkOrder Driver Policy

The WorkOrder driver policy uses only the Publisher Command Transformation policy. The
Command Transformation policy checks to see that a DirXML-WorkToDo object is being added. If
it is, the policy gets the DN of the user from the DirXML-nwoContent attribute. It then sets the
user's Login Disable attribute to False. This allows the user to log in.
NOTE:
<do-add-dest-attr-value class-name="User" direct="true" name="Login
should not be used.
Disabled">
When direct is equal to True, the action is performed as desired, but the results are not returned to
the driver. Therefore, the driver cannot report the results of the write correctly. You can view the
sample at hr-wo-drv-pub-cmd-transform.xml (http://www.novell.com/documentation/idm36drivers/
work_order/samples/hr-wo-drv-pub-cmd-transform.xml).
6.3 Human Resource Example without an HR
Driver
This example creates a new user and postpones activating the new employee's access to the system
until the hire date by putting policies in the WorkOrder driver to create the work order. Figure 6-2
illustrates this sample configuration.
Data Flow without an HR Driver
Figure 6-2
When a new user object is created in the Identity Vault, a policy in the WorkOrder driver checks to
see if the loginDisabled attribute is set to True. If it is not set to True, the Create rule blocks the
event. If it is set to True, the policy creates a work order to set the loginDisabled attribute on the user
to False on the loginActivationTime.
The following policies show how to implement the sample configuration:
Customizing the Driver 33