|Attribute Name||This is the unique name for the attribute. It is also used as the caption when this attribute is displayed on the User profile page.|
|Backend Attribute Name||This is the name of the field that will be created in the user backend schema to store the value specified for this attribute while creating or modifying users . Oracle Identity Manager automatically prefixes the Backend Attribute Name with “USR_UDF.”.|
|Category Name||This is the category name to which the attribute belongs. The categorization is used to organize the data in the UI.
Note: For information about category configuration, see “Performing Category Configuration”.
|Display Type||This indicates the display type of the attribute in the UI. This is an attribute property and is stored in the User.xml file as metadata attachment. The available display types are:
Selecting Display Type sets the appropriate backend and frontend data types.
Backend data type is the data type of the attribute in the backend datastore. This is stored in the User.xml file along with the attribute definition.
Frontend data type indicates the data type of the attribute as interpreted by Oracle Identity Manager. This is stored in the User.xml file along with the attribute definition. This is not displayed in the UI.
See Also: The “Attribute Properties” section for information about properties to be configured for each attribute
|LOV Type||This field is hidden by default. If the display type is selected as List Of Values, then the LOV-related fields are displayed. The LOV Type can be System Generated, Admin Configured, and By Query.|
|System Generated||The user can specify existing LOVs. For example:
After saving the attribute, a drop-down list with employee type codes is displayed in the user details page.
|Admin Configured||The user can add this LOV. For example:
After saving the attribute, a drop-down list with the values specified in the LOV Options Description field are displayed in the user details page.
|By Query||The LOV Code and LOV Options fields are not displayed. Instead, the following fields are displayed:
– LOV Query: In this field, you can specify any SQL query that is valid in the Oracle Identity Manager database schema.
– LOV Column to Display: This is a list showing all the columns from the select query. The selected column values are available on clicking a search icon on the pages for creating or modifying the user entity. For example, you might want to display Manager Name instead of Manager Key.
– LOV Column to Save: This is a list showing all columns from the select query. The selected column value is the one that is saved in the backend store when the user makes a selection in the dropdown available on the pages for creating or modifying the user entity. For example, you can display Manager Name, but want to save Manager Key value.
Note: Oracle Identity Manager represents sets by using two tables, the LKU and LKV tables. The LKU table holds keys that identify each set. The LKV table defines the members of each set, in which each row in the LKV table uses one column to identify the set (a LKU_KEY column in the LKU table), and another column to declare a value that will be a member of that set. A list of values is already defined in the LKU and LKV tables in the database. For administrator specified, the user must specify an LOV code. This is stored in the LKU table. Associated with each code are the list of values. The user must add new values here. These values are stored in the LKV table and are used as this attribute’s LOV values. For system generated, the user can search for LOV codes, and then select a code. Values already exist for this code in the LKV table and are used as this attribute’s LOV values. See “LKU and LKV Table Definitions” for the list of columns in the LKU and LKV tables.
The following is an example of setting the By Query LOV type:
After saving the attribute, a search icon against this attribute is displayed in the user details page. The user can search and select value for the attribute. FIRSTNAME is displayed in the user details page and USERLOGIN is saved in the backend store.
|LOV Code||This is the code to identify the LOV. For system-generated LOV, this value must be of an existing LOV code.
Note: The LoV Code, LOV Options, and LOV Options Description fields are displayed only when Display Type is selected as List Of Values. For other display types, these fields are not displayed.
|LOV Options||This is displayed only if the LOV Type is administrator specified. The user must specify the LOV values here.|
|LOV Options Description||These are the descriptive LOV options.
- OIM 11g R2 – Modify the value of the Log In Required field
- OIM 11g R2 – LKU Table Schema