Working with placeholder variables

Any value of an attribute can be defined as a placeholder for another. These values are interpreted by runtime. Additional you can specify global variables to use in any source file you work with. The folder samples contains such files. For the attribute displayName for example you can define "%sn%, %givenname%". This means depending attributes are predefined with a placeholder, the only differences for the user objects are the attributes givenName and sureName. All other attributes are dynamically linked to each other. You can even specify the folder name in the attribute homeDirectory as a placeholder.

homeDirectory=\\Server\Share\%sAMAccountName%

The user interface will automatically replace the placeholder with the current content. The tooltips inform the user, which placeholder is currently active. The real attribute name is shown in the left window part inside the tooltip.

Besides the original string values string, manipulation operations also supported. If you need only some characters of the string value you can define the count of characters in front of the attribute name:

%1s : Uses the first letter of the surname
%5g : Uses the first five letters of the given name

sAMAccountName=%1:givenname%.%sn%

cn=%givenname%.%1:sn%

Here are some examples:

Surname: Wilson
Given name: James

%1:givenname%%s% JWilson
%1:givenname%%3:sn% Jwil

You can also prevent the creation of duplicate entries for the same user object. The program will then use the next available option. The: %1:givenname%.%sn% is converted to %2:givenname%.%sn% etc. This means that mass import activities executed in a high quality will prevent most of the errors which may occur. These opportunities offer a wide range of options for the conversion of very complex organizational structures with a few steps to another place.

The object properties are based on a centralized configuration database. New added attributes through LDAP-Schema explorer are listed under the category Custom attributes. You will find more information under the paragraph Reading the LDAP schema of the producer.