지금 지원 담당자와 채팅
지원 담당자와 채팅

Identity Manager On Demand - Starling Edition 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 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 Approval recommendations for requests 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
The request overview Requesting products more than once Requests with limited validity period Relocating a customer or product to another shop Changing approval workflows of pending requests Requests for employees Requesting change of manager for an employee Canceling requests Unsubscribe products Notifications in the request process Approval by mail Adaptive cards approval Requests with limited validity period for changed role memberships Requests from permanently deactivated identities Deleting request procedures and deputizations
Managing an IT Shop
IT Shop base data Setting up IT Shop structures Setting up a customer node Deleting IT Shop structures Restructuring the IT Shop Templates for automatically filling the IT Shop Custom mail templates for notifications Product bundles 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

Displaying the request properties overview

On the overview form, you see, at a glance, the most important information about a request property.

To obtain an overview of a request property

  1. In the Manager, select the IT Shop > Basic configuration data > Request properties category.

  2. Select the request property in the result list.

  3. Select the Request properties overview task.

Related topics

Products for requests with time restrictions

Customers retain their requested products until they cancel them themselves. Sometimes, however, products are only required for a certain length of time and can be canceled automatically after this time. Products that are intended to have a limited shelf life need to be marked with a validity period.

To enter a validity period for products

To specify a validity period for a product request

  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 main data task.

  4. Enter in the Validity period (max. # days) field the time period within which the product can be requested.

    Information: This value has no effect on requests for multi-request resources (QERReuse).
  5. Save the changes.

One Identity Manager calculates the date that the product is automatically canceled from the current data and validity period at the time of request and approval.

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 after the request. In both cases, One Identity Manager checks whether the request recipient and the product belong to the same shop after relocating.

Table 14: Effects of relocating

Request recipient and product

Effect on closed requests

Effect on pending requests

Are in different shops

The request is canceled.

The assignment is removed.

The request is canceled.

Are in the same shop

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

Table 15: 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 main data task.

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

  5. Save the changes.
Related topics

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 main data task.

  4. Set Not available.

  5. Save the changes.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택