You can define provisioning request definitions from scratch in the Designer for Identity Manager. Alternatively, you can define provisioning requests by modeling them after the provisioning request templates that ship with the product. To use the templates, you define new objects based on the installed templates and customize these objects to suit the needs of your organization.
The installed templates let you determine the number of approval steps required for the request to be fulfilled. You can configure a provisioning request to require:
No approvals
One approval step
Two approval steps
Three approval steps
Four approval steps
Five approval steps
You can also specify whether you want to support sequential or parallel processing, and whether you want to approve or deny the request in the event that the workflow times out during the course of processing.
Identity Manager ships with the templates listed in Table 16-2.
Table 16-2 Templates for Provisioning Requests
|
Template |
Description |
|---|---|
|
Self Provision Approval |
Allows a provisioning request to be fulfilled without any approvals. |
|
One Step Approval (Timeout Approves) |
Requires a single approval for the provisioning request to be fulfilled. If an activity times out, the activity approves the request and the work item forwards to the next activity. |
|
Two Step Sequential Approval (Timeout Approves) |
Requires two approvals for the provisioning request to be fulfilled. If an activity times out, the activity approves the request and the work item forwards to the next activity. This template supports sequential processing. |
|
Three Step Sequential Approval (Timeout Approves) |
Requires three approvals for the provisioning request to be fulfilled. If an activity times out, the activity approves the request and the work item forwards to the next activity. This template supports sequential processing. |
|
Four Step Sequential Approval (Timeout Approves) |
Requires four approvals for the provisioning request to be fulfilled. If an activity times out, the activity approves the request and the work item forwards to the next activity. This template supports sequential processing. |
|
Five Step Sequential Approval (Timeout Approves) |
Requires five approvals for the provisioning request to be fulfilled. If an activity times out, the activity approves the request and the work item forwards to the next activity. This template supports sequential processing. |
|
One Step Approval (Timeout Denies) |
Requires a single approval for the provisioning request to be fulfilled. If an activity times out, the workflow denies the request. This template supports sequential processing. |
|
Two Step Sequential Approval (Timeout Denies) |
Requires two approvals for the provisioning request to be fulfilled. If an activity times out, the workflow denies the request. This template supports sequential processing. |
|
Three Step Sequential Approval (Timeout Denies) |
Requires three approvals for the provisioning request to be fulfilled. If an activity times out, the workflow denies the request. This template supports sequential processing. |
|
Four Step Sequential Approval (Timeout Denies) |
Requires four approvals for the provisioning request to be fulfilled. If an activity times out, the workflow denies the request. This template supports sequential processing. |
|
Five Step Sequential Approval (Timeout Denies) |
Requires five approvals for the provisioning request to be fulfilled. If an activity times out, the workflow denies the request. This template supports sequential processing. |
|
Two Step Parallel Approval (Timeout Approves) |
Requires two approvals for the provisioning request to be fulfilled. If an activity times out, the activity approves the request and the work item forwards to the next activity. This template supports parallel processing. |
|
Three Step Parallel Approval (Timeout Approves) |
Requires three approvals for the provisioning request to be fulfilled. If an activity times out, the activity approves the request and the work item forwards to the next activity. This template supports parallel processing. |
|
Four Step Parallel Approval (Timeout Approves) |
Requires four approvals for the provisioning request to be fulfilled. If an activity times out, the activity approves the request and the work item forwards to the next activity. This template supports parallel processing. |
|
Five Step Parallel Approval (Timeout Approves) |
Requires five approvals for the provisioning request to be fulfilled. If an activity times out, the activity approves the request and the work item forwards to the next activity. This template supports parallel processing. |
|
Two Step Parallel Approval (Timeout Denies) |
Requires two approvals for the provisioning request to be fulfilled. If an activity times out, the workflow denies the request. This template supports parallel processing. |
|
Three Step Parallel Approval (Timeout Denies) |
Requires three approvals for the provisioning request to be fulfilled. If an activity times out, the workflow denies the request. This template supports parallel processing. |
|
Four Step Parallel Approval (Timeout Denies) |
Requires four approvals for the provisioning request to be fulfilled. If an activity times out, the workflow denies the request. This template supports parallel processing. |
|
Five Step Parallel Approval (Timeout Denies) |
Requires five approvals for the provisioning request to be fulfilled. If an activity times out, the workflow denies the request. This template supports parallel processing. |
Workflows and provisioned resources. When you create a new provisioning request definition, you bind it to a provisioned resource. You can change the provisioned resource associated with the request definition, but not the workflow or its topology.
Categories for provisioning requests. Each provisioning request template is also bound to a category. Categories provide a convenient way to organize provisioning requests for the end user. The default category for all provisioning request templates is . The category key, which is the value of the srvprvCategoryKey attribute, is (lowercase).
You can create your own categories by using the directory abstraction layer editor. When you create a new category, make sure the category key (the value of srvprvCategoryKey) is lowercase. This is necessary to ensure that categories work properly in the Identity Manager User Application.
For details on creating provisioning categories, see the Identity Manager User Application: Design Guide.