Chatee ahora con Soporte
Chat con el soporte

Identity Manager 8.1.4 - IT Shop Administration Guide

Setting up an IT Shop solution
One Identity Manager users in the IT Shop Implementing the IT Shop Requestable products Preparing products for requesting Assigning and removing products Preparing the IT Shop for multi-factor authentication Assignment requests and delegating Creating IT Shop requests from existing user accounts, assignments, and role memberships Adding Active Directory and SharePoint groups to the IT Shop automatically Adding Privileged Account Management user groups to the IT Shop automatically
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 Cancel 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
Resolving errors in the IT Shop Configuration parameters for the IT Shop Request statuses Examples of request results

Product request on customer or product relocation

If a customer requests a product from a shop or shopping center and then changes to another at a later date, you must decide how the existing request should be handled. The same applies if a product is moved to another shelf. One Identity Manager checks whether the request recipient and the product belong to the same shop after relocating.

Table 11: Effects of relocating

Request recipient and product

Effect on closed requests

Effect on pending requests

In different shops

The request is canceled.

The assignment is removed.

The request is canceled.

In the same shop

Behavior is defined by Retain service item assignment on relocation in the service item.

Table 12: Effect of the "retain service item assignment on relocation" option

Option Value

Effect on approved requests

Effect on pending requests

Not set

The request is canceled.

The assignment is removed.

The request is canceled.

Enabled

The request remains intact. Shelf and shop are updated in the request procedure.

Assignment of requested company resources remains intact.

The request remains intact. Shelf and shop are updated in the request procedure.

Approvals already granted, are reset. The request runs through the approval process implemented in the new shop.

NOTE: The request is realized in the shop in which the request recipient is customer and that contains the requested product. If several shelves or shops are found to which the condition applies, One Identity Manager selects one of the shelves or shop, respectively, to relocate.

The complete approval sequence is shown in the approval history.

To obtain a product's requests on relocation

  1. In the Manager, select the IT Shop | Service catalog | Hierarchical by service categories | <service category> category.

    - OR -

    In the Manager, select the IT Shop | Service catalog | Hierarchical by service categories | Singles category.

  2. Select the service item in the result list.

  3. Select the Change master data task.

  4. Set the Retain service item assignment on relocation option.

  5. Save the changes.

Non-requestable products

Products that have already been requested but can only be requested for a limited period, can be specially labeled for it. Existing request for the product remain intact. However, no new requests may be made for the product.

To label a product as not requestable

  1. In the Manager, select the IT Shop | Service catalog | Hierarchical by service categories | <service category> category.

  2. Select the product's service item in the result list.

  3. Select the Change master data task.

  4. Set Not available.

  5. Save the changes.

Entering terms of use

Terms of use that explain conditions of use for a product can be stored for individual service items (for example, software license conditions). When someone requests this product, the requester, and request recipient must accept the terms of use before the request can be finalized.

To add or edit terms of use

  1. In the Manager, select the IT Shop | Service catalog | Terms of use category.

  2. In the result list, select a terms of use and run the Change master data task.

    - OR -

    Click in the result list.

  3. Edit the terms of use master data.

  4. Save the changes.

Enter the following properties for the terms of use.

Table 13: General master data for terms of use

Property

Meaning

Terms of use

Name of the terms of use.

Description

Text field for additional explanation.

Contents

Full text of the terms of use.

In order for the request recipient to accept the terms of use, the request must be assigned to the request recipient in the approval process. Set an approval workflow for such requests that contain a BR approval step and enable the No automatic approval option for this approval step. One Identity Manager provides a default approval procedure and a Terms of Use acknowledgment for third-party orders (sample) default approval policy that you can use for this.

Related topics

Additional tasks for terms of use

After you have entered the master data, you can run the following tasks.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación