This rule does not allow user objects to be created unless the required attributes are populated. Implement the rule on the Creation policy in the driver. You can implement the rule on either the Subscriber or the Publisher channel or on both channels.
There are two steps involved in using the predefined rules: creating a policy in the Creation policy set and importing the predefined rule. If you already have a Creation policy that you want to add this rule to, skip to Importing the Predefined Rule.
From theview or the view, select the Publisher or Subscriber channel.
Select the Creation policy set in the Policy Set view, then clickicon to create a new policy.
Click, then click .
Name the policy.
Use the default location or browse and select another location to place the policy in the driver.
Selectafter creating policy, then click .
Selectfor the type of policy, then click .
A file conflict window appears with the message “ Before editing this item you need to save. Do you wish to save the editor’s changes and continue?” Click . The Policy Builder is launched and the new Creation policy is saved.
Continue with Section 8.3.2, Importing the Predefined Rule.
Right-click in the Policy Builder and click> or .
Select, then click .
Edit the action by double-clicking thetab.
Deletefrom the field.
Browse to and select the attributes you require for a User object to be created, then click.
Save the rule by selecting> .
This rule is used when your business processes require a user to have specific attributes populated when the user object is created. When a user object is created, the rule vetoes the creation of the object unless the required attributes are provided. You can have one or more required attributes.
If you want more than one required attribute, right-click the action and select. Select , then browse to the attribute you want to require.