The Dashboard and the identity applications allow you to configure the format of displayed user names in your environment based on the user’s current locale. To simply name entry, the identity applications attempt to complete the names as you type them based on the information in the database.
The Dashboard and the identity applications allow you to configure the format of displayed user names in your environment based on the user’s current locale.
You can then use localized user names in Approval forms, using the literal %LocaleFormattedFullName% for forms with the User entity definition key. For more information about creating or configuring forms in Designer, see “Creating Forms for a Provisioning Request Definition”, in the NetIQ Identity Manager - Administrator’s Guide to Designing the Identity Applications.
Open your current project and click the project name in the Outline view.
In the Provisioning view, right-clickand select .
In the Directory Abstraction Layer editor, expand.
Select the locale name pattern that you want to modify.
Modify theexpression to specify the format you want to use for the locale. For example, if you want to display the user’s surname first and given name second, modify the expression as follows:
attr.getValue("Surname") + " " + attr.getValue("Given Name")
You can either modify the expression manually in the Expression field or click the Working with ECMA Expressions” in the NetIQ Identity Manager - Administrator’s Guide to Designing the Identity Applications.icon and use the ECMA Expression Builder to modify the expression. For more information about modifying ECMAScript expressions, see “
Save your changes to the locale name pattern.
Repeat Step 5 through Step 7 for each name pattern you want to configure.
When finished, close the Directory Abstraction Layer editor.
In the Modeler, right-click the User Application driver and select.
Click, then click to restart the driver.
After you configure the Full Name entity in the Directory Abstraction Layer, the identity applications automatically display user names formatted by locale.
However, to use user names with localized name formatting in typeahead fields within the identity applications, you must create one or more custom registry entries. The identity applications use typeahead controls when a supervisor wants to manage a specific or team, and the typeahead controls do not use the %LocaleFormattedFullName% literal.
In the conf directory of your application server installation, create an empty file with the file name UIControlRegistry_CustomProps.xml.
Open the User Application WAR, IDMProv.war by default, and extract the contents.
Locate the UIControlRegistry.xml file in the WAR’s WEB-INF directory.
In the UIControlRegistry.xml file, locate the entries for the UserDNLookup and UserInTeamDNLookup keys.
Copy the <registry> element, <ctrls> element, and both keys to the UIControlRegistry_CustomProps.xml file.
Modify the display-exp property of each of the copied keys as follows:
<prop name="display-exp" type="string"> <value>FirstName LastName</value> <value xml:lang="en">LastName FirstName</value> </prop>
Create an xml:lang value for each localized name format you want to use. You can include a value for each language supported by the identity applications.
Save and close the UIControlRegistry_CustomProps.xml file.
By default, the Identity Applications sorts the list of users on the Dashboard based on the First Name attribute, irrespective of the user name format configured by the administrator in the Directory Abstraction Layer (DAL). For example, if the administrator has configured the Full Name entity to display the user’s surname first and the given name second, then the Dashboard will display a user, John Smith as Smith John, where Smith is the surname and John the given name. However, it will use John (first name of the user) while sorting the order in the list.
Identity Applications provides you an option to change the default setting and sort users based on the attribute of your choice. You must provide the key value of the attribute for sorting. For example, add the property com.netiq.idm.user.sortcol=LastName in the ism-configuration.properties file to sort the users by the LastName.
Consider the following while configuring the property for sorting users:
You can specify only one attribute for the com.netiq.idm.user.sortcol property.
If the configured attribute is not part of the compound index or DAL, the application resets the property com.netiq.idm.user.sortcol to the default value, FirstName in the ism-configuration.properties file. Consequently, the users are sorted based on their FirstName attribute.
Server side sort uses sorting key attributes such as Given Name and Surname in the compound index to perform searches. The application sorts the data based on the order in which these attributes have been configured. The attribute set for the com.netiq.idm.user.sortcol property is used as first sorting key, whereas the second sorting key attribute is selected by the application. For example, when the com.netiq.idm.user.sortcol property is set to LastName, the application uses Surname as the first sorting key attribute and Given Name as second sorting key attribute while sorting the users. Similarly, if you set the property as com.netiq.idm.user.sortcol=TelephoneNumber, the users will be sorted using the Telephone Number and Surname as the first and second sorting attribute respectively.
For more information on compound indexes, see Enabling Compound Index on Identity Vault Attributes.