One Identity Manager provides approval workflows by default. These approval workflows are used in the Identity & Access Lifecycle shop approval processes. Each default approval workflow is linked to a default approval policy. You can edit different properties of the approval step, for example, to configure notifications in the request process.
To edit default approval workflows
In the Manager, select the IT Shop > Basic configuration data > Approval workflows > Predefined category.
You can apply approval policies to different IT Shop structures and service items. If you have multiple approval policies within your IT Shop, which policy is to be used is based on which rules are specified.
Effective approval policies are defined by the following steps: If no approval policy is found in a step, the next one is checked. The following objects are checked in the following sequence:
The requested service item
The service category to which this service item is assigned
Parent service category
The shelf used for requesting the service item
The shop where the shelf is located
The shopping center where the shop is located
Multiple approval policies can also be identified in this way.
An approval policy found by one of these methods is applied under the following conditions:
The approval policy is not assigned a role type.
- OR -
The assigned role type corresponds to the shelf role type.
If more than one effective approval policies are identified by the rules, the effective approval policy is determined by the following criteria (in the given order).
The approval policy has the highest priority (alphanumeric sequence).
The approval policy has the lowest number of approval steps.
The first approval policy found is taken.
Furthermore:
If no approval policy can be found for a product, a request cannot be started.
The same applies for renewals and unsubscriptions.
If no approver can be determined for one level of an approval policy, the request can be neither approved nor denied.
Pending requests are rejected and closed.
Unsubscriptions cannot be approved. Therefore, unsubscribed products remain assigned.
Renewals cannot be approved. Therefore, products for renewal remain assigned until the valid until date is reached.
NOTE: If an approval workflow for pending requests changes, you must decide how to proceed with these requests. Configuration parameters are used to define the desired procedure.
For more information, see Changing approval workflows of pending requests.
Once the currently effective approval policy has been identified, the actual approvers are determined by the approval workflow specified by it. When requests are renewed, a renewal workflow is run. If no renewal workflow is stored with the approval policy, approvers are determined by the approval workflow.
If no approvers can be identified for a renewal, then the renewal is denied. The product remains assigned only until the Valid until date. The request is then canceled and the assignment is removed.
Once the currently effective approval policy has been identified, the actual approvers are determined by the approval workflow specified by it. When a product is unsubscribed, the cancellation workflow runs. If no unsubscribe workflow is stored with the approval policy, approvers are determined by the approval workflow.
If no approvers can be determined for an unsubscription, then the unsubscription is denied. The product remains assigned.
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center
