<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000A1A3fECQSOkta Identity EngineIdentity GovernanceAnswered2024-08-12T09:05:30.000Z2024-03-05T15:26:14.000Z2024-03-20T07:11:28.000Z

fhjtb (fhjtb) asked a question.

How to choose approver dynamically in Access Request

My request type contains a question and an approval. Question contains a dropdown with a list of Okta groups and the approver should be the owner of the group selected in the question.

Is it feasible to set approvers dynamically? If yes, please let me know how to do it.


  • TimL.58332 (Workflows)

    @fhjtb (fhjtb)​ - The approver portion is dynamic by default if you choose a resource that contains multiple users such as Okta group owner(s).

     

    The portion that determines how dynamic an AR type can be is the group resource config-list you are utilizing. If it is NOT multi-select than the approver and assign portion can be dynamic with just 1 approver task && one action step (such as add or remove user from group). The target for approvers would be group owner of the selected group and the target of the action can be the group selection.

     

    However, if you are leveraging multi-select the AR type becomes much more static. You need an approver step + action step for EACH possible item in the config-list and logic asking if "X is in config-list then approver is group owner of X and target for action is X" Then another that is if "Y is in config-list then approver is group owner of Y and target for action is Y"

     

    Essentially, it will need to evaluate each possible selection and if they were selected perform the steps for the selection.

    Expand Post
    Selected as Best
  • TimL.58332 (Workflows)

    @fhjtb (fhjtb)​ - The approver portion is dynamic by default if you choose a resource that contains multiple users such as Okta group owner(s).

     

    The portion that determines how dynamic an AR type can be is the group resource config-list you are utilizing. If it is NOT multi-select than the approver and assign portion can be dynamic with just 1 approver task && one action step (such as add or remove user from group). The target for approvers would be group owner of the selected group and the target of the action can be the group selection.

     

    However, if you are leveraging multi-select the AR type becomes much more static. You need an approver step + action step for EACH possible item in the config-list and logic asking if "X is in config-list then approver is group owner of X and target for action is X" Then another that is if "Y is in config-list then approver is group owner of Y and target for action is Y"

     

    Essentially, it will need to evaluate each possible selection and if they were selected perform the steps for the selection.

    Expand Post
    Selected as Best
  • fhjtb (fhjtb)

    Thanks for the reply. I am not using multi-select option. I am using Configuration Lists instead of Resources. I shall try with Resources and let you know.

    • TimL.58332 (Workflows)

      @fhjtb (fhjtb)​ - Configuration Lists are a type of resource. You could have a config list that is groups/apps etc. I was trying to be as generic/general as I could be. However, you do need to use a "group" config list if you want to dynamically do stuff with the group. Even though what is displayed to you is the "Group name" behind that it is associated with the Okta Group ID which is actually what is being used in the backend.

      Expand Post
  • fhjtb (fhjtb)

    I have got this figured out, thanks @TimL.58332 (Workflows)​ for the explanation.

Loading
How to choose approver dynamically in Access Request