Converts the enclosed token’s DN to an alternate format.
Specify the RDN index to start with:
Index 0 is the root-most RDN
Positive indexes are an offset from the root-most RDN
Index -1 is the leaf-most segment
Negative indexes are an offset from the leaf-most RDN towards the root-most RDN
Number of RDN segments to include. Negative numbers are interpreted as (total # of segments + length) + 1. For example, for a DN with 5 segments a length of -1 = (5 + (-1)) + 1 = 5, -2 = (5 + (-2)) + 1 = 4, etc.
Specifies the format used to parse the source DN.
Specify the format used to output the parsed DN.
Specify the custom source DN delimiter set if Source DN Format is set to custom.
Specify the custom destination DN delimiter set if Destination DN Format is set to custom.
If start and length are set to the default values {0,-1}, then the entire DN is used; otherwise only the portion of the DN specified by start and length is used.
When specifying custom DN formats, the eight characters that make up the delimiter set are defined as follows:
Typed Name Boolean Flag: 0 means names are not typed, and 1 means names are typed
Unicode No-Map Character Boolean Flag: 0 means don’t output or interpret unmappable Unicode characters as escaped hex digit strings, such as \FEFF. The following Unicode characters are not accepted by eDirectory: 0xfeff, 0xfffe, 0xfffd, and 0xffff.
Relative RDN Delimiter
RDN Delimiter
Name Divider
Name Value Delimiter
Wildcard Character
Escape Character
If RDN Delimiter and Relative RDN Delimiter are the same character, the orientation of the name is root right, otherwise the orientation is root left.
If there are more than eight characters in the delimiter set, the extra characters are considered as characters that need to be escaped, but they have no other special meaning.
The example uses the Parse DN token to build the value the Add Destination Attribute Value action. The example is from the predefined rules that come with Identity Manager. For more information, see Command Transformation - Create Departmental Container - Part 1 and Part 2. To view the policy in XML, see predef_command_create_dept_container2.xml.
The Parse DN token is taking the information from the source DN and converting it to the dot notation. The information from the Parse DN is stored in the attribute value of OU.