Okta Workflows - Preview release notes

Execution History Inspector is now Generally Available

Execution History Inspector provides various detailed usage metrics directly to you. This diagnostic view helps you to understand flow performance and provides you with the ability to diagnose issues and optimize your flows.

See View flow execution history.

Execution Log Streaming is now Generally Available

With Execution Log Streaming, customers can monitor execution history and performance across all of their flows. This is done by sending execution logs to a downstream security information and event management (SIEM) tool.

This feature allows you to configure alerts and dashboards to provide proactive identification and resolution of potential issues. The centralized monitoring capability also provides a holistic view across all Workflows operations for better insights and decision making.

See Execution Log Streaming.

The feature adds the following new System Log events:

• workflows.user.execution_log_stream_connection.activate

• workflows.user.execution_log_stream_connection.deactivate

• workflows.user.execution_log_stream_connection.update

• workflows.user.flow.execution_log_stream.activate

• workflows.user.flow.execution_log_stream.deactivate

Simplified onboarding for new Workflows users

In this release, Okta introduces a new guided experience to help new Okta Workflows users get started quickly. This experience includes a short set of questions to personalize your homepage with recommended templates and connectors, and a step-by-step checklist to guide you through learning core concepts.

See Workflows Console.

Continuous Sign-On Policy Evaluation is now Generally Available in Production orgs

User sessions are periodically refreshed, invoking an evaluation of the sign-on policy. If the policy requirements aren't met, users are prompted to re-authenticate.

Fixes in Okta Workflows

• OKTA-908293
  

  The Remove User from Group card in the Okta connector deleted the group if it contained a valid group ID followed by a hash sign (#) and any additional characters.

• OKTA-986834
  

  This update fixes several display issues in execution history.

• OKTA-812043
  

  In execution history, flows containing an API Endpoint card sometimes showed an entry indicating that a card had been deleted, even when no card was removed from the flow.

• OKTA-972584
  

  In Connector Builder, when creating a test connection with multiple authentications, the Client ID and Client Secret fields appeared even when the client ownership was set to developer.