This article addresses the situation when an Okta Access Request is configured with the Run a Workflow action, and the Request appears as though it is stuck on the step where the Workflow Action step is not automatically running as expected.
- Okta Identity Governance
- Access Request
- Run a (Delegated) Workflow Action from within a Request
The Run a Workflow action will only automatically run the workflow when ALL inputs for the delegated flow are provided. This applies even if the Question used for the input is optional or has not met the required Logic to be visible to the user.
Example Request Type and Request where this can be experienced:
- There is a Request that has an action to Run a Delegated Workflow with three inputs, and the step will not run automatically until all three inputs are provided with values:
- Business Justification;
- Permissions;
- Comments (in this example, this is an optional question and will not be answered in the next step)
- Create a Request using the Request Type above, and do not enter a value for one of the questions. As a result, the Run a Workflow step will not run automatically since one of the inputs for the Workflow does not have a value provided.
For an existing/open request where the action is not running automatically, and the Request should proceed:
- Ensure all inputs needed for the Workflow action are answered and have values (may need to compare against the Request Type buildout).
- If there is a question that cannot be answered since Logic is not true for the Question and it will not appear for the user, then the Request Assignee can either:
- Run Manually - Allows the ability of the Request Assignee to run the Workflow action with the current inputs.
- Mark as Complete - This allows the Request Assignee to mark the action as complete, handle/address the flow (manually) outside of the Request, and allow the Request to progress.
Options for the design of a Request Type to Run a Workflow for future Requests:
- Keep the Request Type and Workflow as is, and the Request Assignee can take manual action on the step as needed (as indicated above).
- Alter the Request Type to have the optional Question marked as required (even if the user enters none or n/a) so the workflow always has all required inputs satisfied to run automatically.
- Depending on the Delegate Workflow and its inputs, have multiple Delegated Workflows set up with different input variations, and in the Request Type, add Logic to different Run a Workflow action steps to make sure a field is not empty to run the associated flow
- If the questions answered may vary and the Workflow can be run right after the Request is created, have a Workflow get triggered when an Access Request is created. See the following on How to Integrate Access Request Questions and Answers into an Okta Workflow.
Related References
- How to Integrate Access Request Questions and Answers into an Okta Workflow
- OIG Access Requests – Calling an Okta Workflow from Within a Request Type
- Okta Access Request - Create an Access Request type
- Okta Workflows - See Delegated flows and Build a delegated flow
- Okta Workflows actions in Access Requests is an Early Access Feature. To learn how to enable it, see Manage Early Access and Beta features
