Make a property required and specify its format

Adaxes allows you to make any property of directory objects required. If a property is required and the user leaves it blank, they will receive an error message prompting to enter a value.

Also, you can ensure that values for object properties are entered in the correct format. The format can be defined either with the help of regular expressions or using constraints like must start with or must not contain. If the format is defined using a regular expression, you can customize the error message that will be shown if the validation fails.

To make a property required and define its format, you need to use property patterns. Adaxes provides a built-in property pattern, User, that is applied to all user accounts by default. In this tutorial, you will learn how to use the property pattern to make a specific property of user accounts mandatory, and how to use regular expressions to specify the format for the property.

Launch Adaxes Administration console.
How { #collapse1}
- On the computer where Adaxes Administration console is installed, open Windows Start menu.
- Click Adaxes Administration Console.
Expand Adaxes service \ Configuration \ Property Patterns \ Builtin and select User.
In the section located to the right, click Add and select the property you want to configure.
To make the property mandatory, select The property is required checkbox.
To specify the format for the property, select Must match regexp and enter a regular expression in the edit box.

Example 1 – six digits
```
^[0-9]{6}$
```
Example 2 – three digits, dash, three digits
```
^[0-9]{3}\-[0-9]{3}$
```
Click the button located next to the edit box and enter the error message that will be shown if the validation fails.

When done, click OK.
Click Save changes.

For information on how to validate object properties using a PowerShell script, see Validate/modify user input using a script.

Different patterns for different users

By default, property pattern User is applied to scope All Objects.

This means that the list of allowed values for the property will be the same for all users in all domains managed by Adaxes. If you want to apply different settings for different organizational units or domains, create a separate property pattern for each OU or domain.

How to create a property pattern { #howto_multiple_pattern}

Right-click Property Patterns, point to New and click Property Pattern.
Enter a name for the new property pattern and click Next.
On the Object Type step, select User.

Click Next.
On the Configuration step, configure options for a property and click Next.
On the Activity Scope step, click Add.

Select from the following items:
- Domain – select to apply the property pattern to all users in a specific domain.
- OU or Container – select to apply the property pattern to users located in an organizational unit or container.
- Group – select to apply the property pattern to members of a group.
  
  Assignments over group members are not applied during user creation.
- Business unit – select to apply the property pattern to members of a business unit. To select a business unit, open the Look in drop-down and select the Business Units item.
You can exclude specific organizational units, business units, groups, and domains from the activity scope of the property pattern. For example, if you've assigned the property pattern over the whole domain, but do not want it to apply to a specific organizational unit, you can exclude the organizational unit from the activity scope. To exclude an object, select the Exclude the selection option in the Assignment Options dialog.
Step by step { #exclude_scope}
- Click the object you want to exclude.
- In the Assignment Options dialog, select the Exclude the selection option.
- Click OK.
When done, click Finish.