Setting up an Approval Step
Setting up an Approval Step
Approval steps can be automatically escalated once the specified timeout is exceeded. The request is presented to another approval body. The request can subsequently be processed again in the normal workflow.
To configure escalation of an approval step
- Open the approval workflow in the Workflow Editor.
- Add an additional approval level with one approval step for escalation.
- Connect the approval step that is going to be escalated when the time period is exceeded with the new approval step. Use the connection point for escalation to do this.
Figure 10: Example of an Approval Workflow with Escalation

- Configure the behavior for the approval step to be escalated when it times out.
Table 63: Approval Step Properties for Abort on Timeout
TimeOut (working hours) |
Number of working hours to elapse after which the approval step is automatically granted or denied approval.
The approvers work time applies to the time calculation.

|
NOTE: Ensure that a state and/or county is entered into the employee‘s master data for determining the correct working hours. | |
Timeout behavior |
Action, which is executed if the timeout expires.
Table 64: Possible Methods for Escalation on Timeout
Escalation |
The request process is escalated. The escalation approval step is called. | |
Emails can be sent to the new approvers and requesters on escalation.
Related Topics
Approvers cannot be Established
Approvers cannot be Established
You can specify a fallback approver if requests cannot be approved due to lack of approver. A request is always returned to the fallback approver for approval if the approval step in a specified approval procedure, cannot determine an approver.
To specify fallback approvers, define application roles and assign these to an approval step. Different approver groups in the approval steps may require different fallback approvers. Specify different application role for this, to which you can assign employees who can be determined as fallback approvers in the approval process. For more information, see the One Identity Manager Application Roles Administration Guide.
To specify fallback approvers for an approval step
- Select the category IT Shop | Basic configuration data | Approval workflows.
- Select a workflow in the result list. Select Change master data in the task view.
- Mark the approval step in the workflow editor.
- Select Toolbox | Approval levels | Add....
- Assign an application in Fallback approver or create a new application role.
- Save the changes.
Request sequence with fallback approvers
- An approver cannot be established for an approval step in an approval process. The request is assigned to all members of the fallback approver application role.
- Once a fallback approver has made an approval decision, the request is passed onto the approvers of the next approval level.

|
NOTE: Specify in the approval step, how many attestors must approve this approval step. This limit is not valid for the chief approval team. The approval step is considered approved the moment one fallback approver has approved the request. |
- The request is aborted if no fallback approver can be established.
Fallback approvers can approve requests for all manual approval steps. The fallback approvals are not permitted for approval steps with the approval procedures CR, SB, CD, EX and WC as well as OC and OH.
Related Topics
Automatic Approval on Timeout
Automatic Approval on Timeout
Requests can be automatically approved once a specified time period has been exceeded.
To configure automatic approval if the timeout expires
- Enter the following data for the approval step.
Table 65: Properties for Automatic Approval on Timeout
TimeOut (working hours) |
Number of working hours to elapse after which the approval step is automatically granted or denied approval.
The approvers work time applies to the time calculation.

|
NOTE: Ensure that a state and/or county is entered into the employee‘s master data for determining the correct working hours. | |
Timeout behavior |
Action, which is executed if the timeout expires.
Table 66: Possible Methods for Escalation on Timeout
Approval |
The request is granted approval in this approval step. The next approval step is called. |
Deny |
The request is denied approval in this approval step. The next approval step is called. | |
If a request is decided automatically, the requester can be notified by email.
Related Topics
Abort Request on Timeout
Abort Request on Timeout
Requests can be automatically aborted once a specified time period has been exceeded. The abort takes place when either a single approval step or the entire approval process has exceeded the timeout.
To configure an abort after the timeout of a single approval step has been exceeded
- Enter the following data for the approval step.
Table 67: Approval Step Properties for Abort on Timeout
TimeOut (working hours) |
Number of working hours to elapse after which the approval step is automatically granted or denied approval.
The approvers work time applies to the time calculation.

|
NOTE: Ensure that a state and/or county is entered into the employee‘s master data for determining the correct working hours. | |
Timeout behavior |
Action, which is executed if the timeout expires.
Table 68: Method for Abort on Timeout
Abort |
The approval, and therefore the entire approval process for the request, is aborted. | |
To configure abort on timeout for the entire approval process
- Enter the following data for the approval workflow.
Table 69: Approval Step Properties for Abort on Timeout
System abort (days) |
Number of days to elapse after which the approval workflow, and therefore the system automatically ends the entire approval process. |
If a request is aborted, the requester can be notified by email.
Related Topics