Find Matching Object - Novell POLICY IN DESIGNER 3.5 - 09-18-2009 Manual

Find Matching Object

Finds a match for the current object in the destination data store.
Fields
Scope
Select the scope of the search. The scope might be an entry, a subordinate, or a subtree.
DN
Specify the DN that is the base of the search.
Match Attributes
Specify the attribute values to search for.
IMPORTANT: To improve performance when using the find matching object verb, create an
index for the attributes that you are going to use when querying the Identity Vault. For more
information about indexes, see the
www.novell.com/documentation/edir88/edir88/index.html?page=/documentation/edir88/
edir88/data/a5tuuu5.html).
Remarks
Find Matching Object is only valid when the current operation is an add.
The DN argument is required when the scope is "entry," and is optional otherwise. At least one
match attribute is required when the scope is "subtree" or "subordinates."
The results are undefined if the scope is "entry" and there are match attributes specified. If the
destination data store is the connected application, then an association is added to the current
operation for each successful match that is returned. No query is performed if the current operation
already has a non-empty association, thus allowing multiple find matching object actions to be
strung together in the same rule.
If the destination data store is the Identity Vault, then the destination DN attribute for the current
operation is set. No query is performed if the current operation already has a non-empty destination
DN attribute, thus allowing multiple find matching object actions to be strung together in the same
rule. If only a single result is returned and it is not already associated, then the destination DN of the
current operation is set to the source DN of the matching object. If only a single result is returned
and it is already associated, then the destination DN of the current operation is set to the single
character . If multiple results are returned, then the destination DN of the current
operation is set to the single character �.
Example
The example matches on User objects with the attributes CN and L. The location where the rule is
searching starts at the Users container and adds the information stored in the OU attribute to the DN.
The rule is from the predefined rules that come with Identity Manager. For more information, see
Section 8.13, "Matching - By Attribute Value," on page
predef_match_by_attribute.xml
Novell eDirectory 8.8 Administration Guide (http://
130. To see the policy in XML, see
(../samples/predef_match_by_attribute.xml).
Actions 257