1. Click the Display Filter button in the upper right corner of the Resource Catalog display.

   

2. In the Filter dialog, specify a filter string for the resource name or description, or select one or more categories for which you want to see resources. Click Filter:

   

3. To remove the current filter, click Clear.

1. Click on the Rows dropdown list and select the number of rows you want to be displayed on each page:

   

1. To scroll to another page in the resource list, click on the Next, Previous, First or Last button at the bottom of the list.

To sort the resource list:

1. Click the header for the column you want to sort on.

   The pyramid-shaped sort indicator shows you which column is the new sort column. When the sort is ascending, the sort indicator is shown in its normal, upright position.

   When the sort is descending, the sort indicator is upside down.

   The initial sort column is determined by the administrator.

1. Click the Entitlement tab.

2. Click Browse Entitlements to select the entitlement:

   

   The User Application displays a tree-view list of available entitlements:

   

   The list shows all drivers and entitlements found in the User Application driver set.

   NOTE:If you have not configured the resource correctly, when you access the Browse Entitlements page to select an Entitlement, you will see a message indicating that you have not configured your entitlements for resource mapping.

   For information about configuring your drivers and entitlements for resource mapping, see Enabling Drivers for Resource Mappings, in the NetIQ Identity Manager User Application: Administration Guide.

3. Select the entitlement you want to use and click OK.

   The Entitlement tab shows information about any values that might be required for the entitlement:

   

4. Specify the details of the entitlement binding. The details vary depending on the type of entitlement you are associating with the resource:

   Type of Entitlement	Description
   Valueless entitlement	The entitlement accepts no parameter values. For example, a resource might be bound to an entitlement called Health Benefits that simply makes the recipient eligible for health care benefits. This type of entitlement has a fixed behavior and thereby requires no further information from the requester. When you bind to a valueless entitlement, no further configuration is required.
   Free-form valued entitlement	The entitlement that requires a parameter value specified as a free-form string at request time. For example, a resource might be bound to an entitlement called Clothing that allows the requester to specify a value that represents their favorite color. You can assign a value at design time when you’re defining the resource, or allow the user to assign a value at request time. For more information, see Binding to a Free-Form Valued Entitlement.
   Single-valued entitlement	The entitlement that requires a single parameter value. For example, a resource might be bound to an entitlement called Parking Permission that allows the requester to select a parking location. The allowable values are provided by an entitlement list, which can include a static list of values defined by an administrator or a dynamic list of values generated from an LDAP query. You can assign a value at design time when you’re defining the resource, or allow the user to assign a value at request time. For more information, see Binding to a Single-Valued Entitlement.
   Multi-valued entitlement	The entitlement that accepts one or more parameter values. For example, a resource might be bound to an entitlement called Building Pass that allows the requester to select one or more buildings. The allowable values are provided by an entitlement list, which can include a static list of values defined by an administrator or a dynamic list of values generated from an LDAP query. You can assign a value at design time when you’re defining the resource, or allow the user to assign a value at request time. For more information, see Binding to a Multi-Valued Entitlement.

To define the request form:

1. Click the Request Form tab.

   

   The Request Form tab shows a list of fields that correspond to entitlement parameters for which values will be specified at request time. The properties for entitlement parameter fields are configured on the Action tab. You cannot change the behavior of fields that map to entitlement parameters.

2. To add a decision support data field:

   1. Click the plus sign (+) to add a new field:

      

   2. The Request Form tab adds a new field (with the default label Field Label 1) to the list of fields, and displays the Properties panel to allow you to define the characteristics of the field:

      

   3. To assign the decision support value right away, click Now.

      

      Provide a display label for the field, as well as the data type and value. The following data types are supported:

      Data type	Description
      Boolean	A logical data type having one of two possible values: true or false.
      Integer	A sequence of natural numbers.
      List	A set of predetermined values from which a value is selected.
      String	A sequence of values representing text.

      To hide the value on the request form, click Hide. A field that is hidden on the request form is still visible on the approval form.

   4. To allow the user to assign the value at request time, click At resource request time.

      

      Provide a display label for the field, and specify whether the value must be of a particular data type or come from a list.

To define the approval process:

1. Click the Approval tab.

   

2. Specify whether the approval process for the resource can be overridden by the approval process for a role by selecting or deselecting the Allow role approval process to override resource approval process checkbox.

   If the Allow role approval process to override resource approval process checkbox is selected, the role approval process will always override the resource approval process whenever the resource is associated with a role. Once the associated role has been approved, the resource is automatically provisioned, without any need for approval.

3. Define the approval process for a grant operation, as follows:

   1. Open the Grant Approval section of the Approval tab.

   2. Specify the approval details, as described below:

      Field	Description
      Required	Select this box if the resource requires approval when requested. Deselect this box if the resource does not require approval when requested.
      Custom Approval	When you select Custom Approval, you need to select a custom Resource Assignment Approval Definition. This is the name of the provisioning request definition executed when the resource is requested.
      Standard Approval	When you select Standard Approval, the resource uses the standard resource assignment approval definition specified in the Resource Subsystem configuration settings.
      Approval Type	Select Serial if you want the role to be approved by all of the users in the Approvers list. The approvers are processed sequentially in the order they appear in the list. Select Quorum if you want the role to be approved by a percentage of the users in the Approvers list. The approval is complete when the percentage of users specified is reached. For example, if you want one of four users in the list to approve the condition, you would specify Quorum and a percentage of 25. Alternatively, you can specify 100% if all four approvers must approve in parallel. The value must be an integer between 1 and 100. HINT:The Info button displays text that explains the approval types.
      Approvers	Select User if the role approval task should be assigned to one or more users. Select Group if the role approval task should be assigned to a group. Select Role if the role approval task should be assigned to a role. To locate a specific user, group, or role, use the Object Selector or History buttons.To change the order of the approvers in the list, or to remove an approver, see Section 1.4.4, Common User Actions.

4. Define the approval details for a revoke operation, as follows:

   1. Open the Revoke Approval section of the Approval tab.

   2. Specify the approval details, as described below:

      Field	Description
      Required	Select this box if the resource requires approval when requested. Deselect this box if the resource does not require approval when requested.
      Same as Grant Configuration	Select this box to copy the settings you used for the grant operation to the settings for the revoke operation.

      For all other approval details, see the field descriptions for the grant operation, which are presented in Step 3.b.

1. Click the Request Status tab.

   

   For each field on the request form, the Request Status display shows a separate column in the list. For example, the Parking Garage column is added to the request list to show entitlement values specified for the resource assignment:

   

2. To see the detailed status information for a request, click the status:

   

   The Assignment Details window is displayed:

   

   For details on what the status values mean, see Section 10.4, Viewing Your Request Status.

3. To retract a request, select the request and click Retract.

   If the request has been completed or terminated, you will see an error message if you try to retract the request.

1. Select a previously defined resource in the Resource Catalog and click Assign.

   

   The User Application displays the resource request form:

   

   The Initial Request Description and User fields are required fields that are present in all resource request forms. You can use the Object Selector to select the users for the resource assignment.

   Assigning a resource to multiple users You can select one or more users for the resource assignment. If you select multiple users, all of the users receive the same resource assignment parameter values.

   

   The request form may include additional fields to accept values for dynamic parameter values or decision-support values, as shown below:

   

   In the example shown above, the Building permission field is used to accept an entitlement parameter value, whereas the Company Name and Require parking? fields are decision-support fields. These fields are not part of the entitlement definition. Instead, these have been added to the resource definition.

2. Fill in the fields on the request form.

3. Click Submit.

1. In the Resource Catalog, select a resource and click Edit to open the Edit Resource dialog.

2. Click the Assignments tab.

   The Assignments tab displays a list of assignments that have been granted for the selected resource.

3. To add a new assignment, click Assign.

   The User Application displays the resource request form:

   

   For details on working with the request form, see Assigning a Resource From the Catalog.