Okta Access Request has a new feature enhancement that supports the “includes” operator for conditional logic. "Includes" now provides more flexibility when using multiple resources in a dropdown input type or list. This article covers the basic concept of configuring and using “includes” to create advanced logical branching of request-type actions in Okta Access Request. 

• Okta Access Request

First, a little context, previously, Access Request administrators had to combine conditionals such as AND/OR with operators like “is”, “is not”, “in configuration list,” “not in configuration list,” and “is not empty” to determine if a list contained a specific combination of values. This step would need to be repeated as many times as the number of combinations required. Okta has added the “includes” operator to simplify the conditional logic and steps required to support Question cards configured to support multi-value options.

In the screenshot below, there are several Task cards, each with its own conditions that Access Request will execute based on the values chosen in the “Pick from list” Question card.
 

From this example, we can infer that when a requestor selects options “Sales Agent Group” and “Sales Manager Group,” the flow will trigger the “execute task 1 & 2” task and no others. We can also see that if a requestor selects any other group along with “Sales Agent Group” and “Sales Manager Group,” then the flow will trigger “execute task 1 & 2,” and the additional task associated with the other group(s) selected. 

As a prerequisite to adding the “includes” operator to logic for a Task, Action, Approval, or Timer card, it is important to note that it can only be used when a Question card allows for multiple selections. See the screenshot below.
 

Understanding the complexity of the request flow, where branching is required, and how using multiple selection lists with the “includes” operator will simplify the flow and allow for less administrative maintenance. 

Here is a quick reference guide on the list of Operators supported by Access Request logic. 

* For custom and action tasks, the operator label is completed. For approval tasks, the operator labels are completed, approved, and denied.

Related References

• Okta Access Request - Request Types
• Looking for Okta Identity Governance help? Visit the Okta Identity Governance Product Hub or schedule Office Hours with the Okta Identity Governance team.