How The Rule Works - Novell POLICY IN DESIGNER 3.5 - 09-18-2009 Manual

Policies in designer 3.5
Table of Contents

Advertisement

5 Save the rule by clicking File > Save.
There is no information to change that is specific to your environment.
IMPORTANT: Make sure that the rules are listed in order. Part 1 must be executed before Part 2.

8.1.3 How the Rule Works

This rule is used when the destination location for an object does not exist. Instead of getting a veto
because the object cannot be placed, this rule creates the container and places the object in the
container.
Part 1 looks for any Add event. When the Add event occurs, two local variables are set. The first
local variable is named target-container. The value of target-container is set to the destination DN.
The second local variable is named does-target-exist. The value of does-target-exist is set to the
destination attribute value of objectclass. The class is set to OrganizationalUnit. The DN of the
OrganizationalUnit is set to the local variable of target-container.
Part 2 checks to see if the local variable does-target-exist is available. It also checks to see if the
value of the local variable does-target-exist is set to a blank value. If the value is blank, then an
Organizational Unit object is created. The DN of the organizational unit is set to the value of the
local variable target-container. It also adds the value for the OU attribute. The value of the OU
attribute is set to the local variable of target-container. It uses the source format as the destination
DN and the destination format is dot format.
112 Policies in Designer 3.5

Advertisement

Table of Contents
loading

This manual is also suitable for:

Designer for identity manager 3.5

Table of Contents