How To - Request Routing works based on Global config and Manager status

[timchengappa]

Use Case

This article explains various approval workflow routing based on global configuration, manager status and using a manager block (for both parallel and serial workflows). The various scenarios and outcomes and defined in the below table

Pre-requisites

A workflow as below is created, saved, and approved. The workflow is then assigned to a security system in scope.

 

Applicable Version(s)

As of V23.3

 

Solution

 

Request Type	Requestor	Beneficiary	Manager	Manager(Approver) Status	Global Configuration -> Requests	Manager Block(Serial WF) Outcome	Manager Block(Parallel WF) Outcome
New Acc / Add Access / Remove Access	John	Alex	N/A	Alex has no manager	Allow Request Without Manager = DISABLED	Unable to submit a request	Unable to submit a request
New Acc / Add Access / Remove Access	John	Alex	N/A	Alex has no manager	Allow Request Without Manager = ENABLED	Assigned to Admin for Approval	Assigned to Admin for Approval
New Acc / Add Access / Remove Access	John	Alex	Andy	Andy is In-Active	Approval for Inactive Users gets redirected to = NONE	Assigned to Admin for Approval	Assigned to Admin for Approval
New Acc / Add Access / Remove Access	John	Alex	Andy	Andy is In-Active	Approval for Inactive Users gets redirected to = User(Tim)	Assigned to Tim for Approval	Assigned to Tim for Approval
New Acc / Add Access / Remove Access	John	Alex	Andy	Andy is Active	N/A	Assigned to Andy for Approval	Assigned to Andy for Approval
New Acc / Add Access / Remove Access	John	John	N/A	John has no manager	Allow Request Without Manager = DISABLED	Unable to submit a request	Unable to submit a request
New Acc / Add Access / Remove Access	John	John	N/A	John has no manager	Allow Request Without Manager = ENABLED	Assigned to Admin for Approval	Assigned to Admin for Approval
New Acc / Add Access / Remove Access	John	John	Andy	Andy is In-Active	Approval for Inactive Users gets redirected to = NONE	Assigned to Admin for Approval	Assigned to Admin for Approval
New Acc / Add Access / Remove Access	John	John	Andy	Andy is In-Active	Approval for Inactive Users gets redirected to = User(Tim)	Assigned to Tim for Approval	Assigned to Tim for Approval
New Acc / Add Access / Remove Access	John	John	Andy	Andy is Active	N/A	Assigned to Andy for Approval	Assigned to Andy for Approval
New Acc / Add Access / Remove Access	John	Alex	John	Andy is In-Active	Approval for Inactive Users gets redirected to = NONE	Assigned to Admin for Approval	Assigned to Admin for Approval
New Acc / Add Access / Remove Access	John	Alex	John	Andy is In-Active	Approval for Inactive Users gets redirected to = User(Tim)	Assigned to Tim for Approval	Assigned to Tim for Approval
New Acc / Add Access / Remove Access	John	Alex	John	Andy is Active	N/A	Assigned to Andy for Approval	Assigned to Andy for Approval
New Acc / Add Access / Remove Access	John	Alex	Alex	Alex cannot be his own manager	N/A	N/A	N/A
New Acc / Add Access / Remove Access	John	Alex is In-active	Andy	Andy is Active	N/A	John will not be able to submit a request for Alex as Alex is In-Active	John will not be able to submit a request for Alex as Alex is In-Active

References

Creating Workflows

[rushikeshvartak]

Who is Tim in your use case

[timchengappa]

HI, @rushikeshvartak please see Global Configuration -> Requests column. 'Tim' is the default user in the global configuration.