Rule checking for requests with self-service
Self-service (SB approval procedure) is always defined as a one-step procedure. That means you cannot set up more approval steps in addition to a self-service approval step.
To realize compliance checking for requests with self-service
Approving requests from an approver
By default, approvers can make approval decisions about requests in which they are themselves requester (UID_PersonInserted) or recipient (UID_PersonOrdered). To prevent this, you can specify the desired behavior in the following configuration parameter and in the approval step.
-
QER | ITShop | PersonOrderedNoDecide configuration parameter
-
QER | ITShop | PersonInsertedNoDecide configuration parameter
-
Approval by affected identity option in the approval step.
If the requester or approver is not allowed to make approval decisions, their main identity and all subidentities are removed from the group of approvers.
NOTE:
-
The configuration parameter setting also applies for fallback approvers; it does not apply to the chief approval team.
-
This configuration parameter does not affect the BS and BR approval procedures. These approval procedures also find the requester and the request recipient if the configuration parameter is not set. For more information, see Finding requesters.
Summary of configuration options
Requesters can approve their own requests if:
Recipients can approve their own requests if:
Requesters cannot approve if:
Recipients cannot approve if:
Example
A department manager places a request for an employee. Both of them are found to be approvers by the approval procedure. To prevent the department manager from approving the request, set the QER | ITShop | PersonInsertedNoDecide parameter. To prevent the employer from approving the request, set the QER | ITShop | PersonOrderedNoDecide parameter.
Approving requests from an exception approver
Similarly, you specify whether exception approvers are allowed to approve their own requests if compliance rules are violated by a request. For more information, see Restricting exception approvers.
Related topics
Setting up approver restrictions
To prevent recipients of requests becoming approvers
-
In the Designer, set the QER | ITShop | PersonOrderedNoDecide configuration parameter.
This configuration parameter takes effect if the Approval by affected identity option is not set on the approval step.
To prevent requesters becoming approvers
-
In the Designer, set the QER | ITShop | PersonInsertedNoDecide configuration parameter.
This configuration parameter takes effect if the Approval by affected identity option is not set on the approval step.
For individual approval workflows, you can allow exceptions to the general rule in the PersonInsertedNoDecide and PersonOrderedNoDecide configuration parameters. Use these options to allow the requester or recipient of requests to make approval decisions themselves in single approval steps.
To allow request recipients or requesters to become approvers in certain cases
Related topics
Automatically approving requests
Approvers may be involved in an approval process more than once, for example, if they are also requesters or determined as approvers in various approval steps. In such cases, the approval process can be speeded up with automatic approval.
NOTE: Automatic approvals apply to all fallback approvers but not to the chief approval team.
Use configuration parameters to specify when automatic approvals are used. You can specify exceptions from default behavior for individual approval steps. Specify the behavior you expect in the following configuration parameters and approval steps.
-
QER | ITShop | DecisionOnInsert configuration parameter
-
QER | ITShop | AutoDecision configuration parameter
-
QER | ITShop | ReuseDecision configuration parameter
-
No automatic approval option in the approval step
Summary of configuration options
Approval steps are automatically approved or denied if:
-
The QER | ITShop | DecisionOnInsert configuration parameter is set.
The No automatic approval option is not set.
- OR -
-
The QER | ITShop | AutoDecision configuration parameter is set.
The No automatic approval option is not set.
- OR -
-
The QER | ITShop | ReuseDecision configuration parameter is set.
The No automatic approval option is not set.
Requests are manually approved or denied if:
-
The QER | ITShop | DecisionOnInsert configuration parameter is not set.
- OR -
-
The QER | ITShop | AutoDecision configuration parameter is not set.
- OR -
-
The QER | ITShop | ReuseDecision configuration parameter is not set.
- OR -
-
The No automatic approval option is set.
Detailed information about this topic
Related topics