Article
Problem
A Forum reader recently asked:
"I have created a mapping table with 3 columns (Location, Department and Context Code). I would like to create a placement rule that places the users in the correct eDirectory context, based on the Context code. The locations and department names in the table match the OUs in the tree. Does anyone know how to create a placement rule to use the mapping table?"
And here's the response from David Gersic ...
Solution
Here's one I did. I used departmentNumber as the index in to the mapping table, and I put a default phone number attribute on the user as part of the create:
<rule>
<description>Add Department Phone Number</description>
<conditions>
<and>
<if-class-name mode="nocase" op="equal">User</if-class-name>
</and>
</conditions>
<actions>
<do-add-dest-attr-value name="Telephone Number">
<arg-value>
<token-map dest="Default Phone Number" src="Department Number"
table="\[root]\niu\IDM\Policy and Data Library\Department Data Mapping
Table">
<token-op-attr name="departmentNumber"/>
</token-map>
</arg-value>
</do-add-dest-attr-value>
</actions>
</rule> Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 3191 reads


0