Chat now with support
Chat with Support

Identity Manager On Demand Hosted - IT Shop Administration Guide

Setting up an IT Shop solution
One Identity Manager users in the IT Shop Implementing the IT Shop Using the IT Shop with the Application Governance Module Requestable products Preparing products for requesting Assigning and removing products Preparing the IT Shop for multi-factor authentication Assignment requests Delegations Creating IT Shop requests from existing user accounts, assignments, and role memberships Adding system entitlements automatically to the IT Shop Deleting unused application roles for product owners
Approval processes for IT Shop requests
Approval policies for requests Approval workflows for requests Determining the effective approval policies Selecting responsible approvers Request risk analysis Testing requests for rule compliance Approving requests from an approver Automatically approving requests Approval by peer group analysis Gathering further information about a request Appointing other approvers Escalating an approval step Approvers cannot be established Automatic approval on timeout Halting a request on timeout Approval by the chief approval team Approving requests with terms of use Using default approval processes
Request sequence Managing an IT Shop
IT Shop base data Setting up IT Shop structures Setting up a customer node Deleting IT Shop structures Templates for automatically filling the IT Shop Custom mail templates for notifications Request templates Recommendations and tips for transporting IT Shop components with the Database Transporter
Troubleshooting errors in the IT Shop Configuration parameters for the IT Shop Request statuses Examples of request results

General main data of a request template

Enter the following properties on the General tab.

Table 81: General main data of a request template



Request template

Name of the request template.


Any additional name for the request template.

Short name

Short name for the request template.

Voucher number

A combination of any characters to uniquely identify the request template. If you leave this field empty, One Identity Manager automatically allocates a number when you save.


Owner of the request template. The employee that created the template is automatically entered as the owner. This value can be changed at any time.


Text field for additional explanation.

Public template

Specifies whether the request template is available to all One Identity Manager users.


Specifies whether the request template is can be used by all One Identity Manager users. This option can only be changed in the Manager through the user with the Request & Fulfillment | IT Shop | Administrators application role.

If Public template is not set on a shared template, Shared is also disabled.

Request templates can be automatically share once Public template has been set.

To automatically share request templates

  • In the Designer, set the QER | ITShop | ShoppingCartPattern | AutoQualified configuration parameter.

Cart items

Use Cart items to assign the product.

To add a new request item to the request template

  • Click .

    The data fields for entering properties are shown.

Table 82: Cart items




Products that can be requested with this request template. All service items are shown in the menu, whose products are assigned to at least one shelf in the IT Shop.

  • To add other products to the request template, click .

  • To delete a cart item, click .


Number of products to request.

You need to customize your Web Portal in order to use these values. For detailed information, see One Identity Manager Web Designer Reference Guide.

Additional request data

Additional information is required for the request.

Deleting request templates

To delete a request template

  1. In the Manager, select the IT Shop > Request templates category.

  2. Select a request template in the result list.

  3. Click in the result list.

NOTE: Every owner can delete his own request templates in the Web Portal. One Identity Manager users with the Request & Fulfillment | IT Shop | Administrators application role can delete the request templates of all owners.

Recommendations and tips for transporting IT Shop components with the Database Transporter

For detailed about working with change labels and about transporting changes with the Database Transporter, see the One Identity Manager Operational Guide.

To transport IT Shop components with the Database Transporter, take the following into account:

  • In one transport package, only include a maximum of one shop with shelves and customer nodes including the dynamic roles and, if necessary, associated approval policies.

  • You should not transport products that reference target system entitlements. Target system entitlements are loaded into the database by synchronization and obtain different UIDs in different databases. This means that references to these entitlements do not match up in the products.

  • Approval policies, approval workflows, approval steps, and approval procedures should be transported together. If necessary, mail templates and mail definitions must be transported as well.

  • If IT Shop components reference application or business roles, they must also be transported along with their child roles.

  • Transport translations if required.

  • If you want to group several objects and dependencies and other changes into a transport package, work with change labels where possible. In the Database Transporter, you can export change labels to a transport package. You can import the transport package with the Database Transporter.

  • Alternatively, you can transport a single object with its dependencies by creating an export in transport format. Then you can import the export with the Database Transporter.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating