Manage request catalog
Manage request catalog
Manage request catalog use case is part of access right management process, and functional request catalog is one of the most visible feature for users requesting and/or removing access rights or business roles from Self-Service.
In this use case is described how IGA admin can create, update and remove request catalog categories.
Request catalog is very flexible and it can be extended to very complex requests, but when building catalog for access rights main principle is to keep it simple for end-users to easily find correct accesses and for IGA admins to be able efficiently manage content and categories.
Use case description
This use case can be expanded with other processes and those has been marked,
* User lifecycle management
** Governance
*** Automation & provisioning
**** Expanded access right management
| Description | |
Overview |
In this use case is described how entitlement or business role related request catalogs are managed. |
Operators |
IGA solution |
Prerequisites |
IGA admin start managing request catalog without any other use case, but if content is added to the catalog entitlement and business role use cases are required. If users can request access rights or business roles from Self-Service, also request access right use cases are required. |
Result |
Request catalog is visible in Self-Service and IGA admin can manage categories and content according to related other use cases. |
| Operating chain for creating new category |
|
| Operating chain for updating or removing category |
|
IGA admin reporting |
IGA admin can create new or use existing ready-made reports, views and dashboards for reporting access right catalog information.
|
| IGA admin actions |
Most of the work load for managing access right catalog is happening right after Go-Live or even during the delivery project. After catalog has been created, it usually needs updates when end-users are requesting changes, new access rights are added to catalog (there is no existing suitable category) or it is expanded based on organization needs.
|
Delete
Expansion possibilities
Expansion possibilities are categorized in three category, but it is always important to validate if requested change has affect to the delivery schedule or work estimations.
Notice, that these expansion possibilities concerns mostly features that need actual configuration changes. Daily admin tasks are described in the use case.
| Category | Description |
|
Small (less than hour) |
Small changes does not usually affect to the delivery schedule or work estimations and these changes can be done also by IGA admins,
|
|
Medium (0,5 - 2 work days) |
Medium changes can be for example,
|
|
Large (more than 2 work days) |
Large changes usually takes longer time, since they require more detailed definition-, and testing work. Those can be for example,
|
Relations & configuration instructions
Relations to other use cases,
Manage entitlements - entitlement is last level of request catalog (second last, if business roles are taken into use)
Manage business roles - business role is last category in request catalog
Relations to other data cards,
IGA Request Catalog
IGA Entitlement
IGA Business Roles
Configuration instructions,
- With IGA baseline there is no need to edit workflows or EPEtasks to achieve this use case.
- Publish request access right service in Self-Service
Unit testing instructions
- Test the IGA Request Catalog management
- Test user must be Matrix42 ESM admin. Admins are usually managed by Efecte_IGA_Admins Directory Group.
- Create new categories and add those to entitlements.
- Publish entitlement to see that categories are displayed in ESS
System and user approval testing instructions
In this chapter are described system and user approval testing instructions
Preparation tasks for both phases
1. Manage entitlements, business roles, request access right use cases are implemented and tested successfully
1. Create new categories (login as admin)
2. Publish entitlement and business roles in to categories (login as admin)
3. Validate from Self-Service that categories and content are showed correctly (login as end-user)
4. Validate that views, dashboards and reports are showing correctly (login as admin)
Delete