22.2 Working with the installed templates

Identity Manager ships with a set of predeployed provisioning request definitions and workflows. You can use these as templates for building your own provisioning system.To set up your system, 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:

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.

For more information on workflow design patterns, see Section 21.1.2, Provisioning and workflow example.

Identity Manager ships with these templates:

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 the activity approves the request and the workitem 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 the activity approves the request and the workitem 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 the activity approves the request and the workitem 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 the activity approves the request and the workitem 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 the activity approves the request and the workitem 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 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 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 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 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 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 the activity approves the request and the workitem 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 the activity approves the request and the workitem 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 the activity approves the request and the workitem 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 the activity approves the request and the workitem 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 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 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 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 the workflow denies the request.

This template supports parallel processing.

Workflows and provisioned resources Each of these provisioning request definitions has a preconfigured binding to a workflow and 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 Entitlements. The category key, which is the value of the srvprvCategoryKey attribute, is entitlements (lower case).

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 lower case. This is necessary to ensure that categories work properly in the Identity Manager user application.

For details on creating provisioning categories, see Section 4.4, Working with lists.