Okta Workflows - Preview release notes

Streamlined new flow creation from Workflows homepage

When you start a new flow from scratch on the homepage by clicking New Flow and selecting From scratch, a pop-up now appears allowing you to choose an existing folder or create a new one for your flow. Previously, you had to navigate to a separate page to make this selection. These improvements simplify the process for quickly building new flows. See Workflows Console.

Continuous Sign-On Policy Evaluation is now active in Okta Workflows

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.

Step execution limits in Free Trial plans

In Free Trial plans, progress for step executions now appears in the Usage and plan limits dashboard on the Okta Workflows Console landing page. Also, a banner appears when you reach the execution limit.

Update to date format in tables

Previously in tables, Date columns appeared and accepted dates in a MM/DD/YY, h:mma [UTC] format. Now, these columns accept dates in your local format.

OAuth Client ID and Secret usability improvements in Connector Builder

Users creating connectors with OAuth authentication can now use passed-through Client ID and Secret values in their connector flows.

UI Update

Some font and text colors have been updated to provide a more consistent look and feel.

Fixes in Okta Workflows

• OKTA-944770
  

  Users without permission to edit flows could still select Secure with OAuth 2.0 from the API endpoint settings.

• OKTA-884256
  

  Users without permissions to view usage for some resources saw an error on the Usage and plan limits dashboard.

• OKTA-844579
  

  On the Deployment tab in Connector Builder, the page refreshed and returned to the top when admins scrolled to the bottom of the list.

• OKTA-950388
  

  When creating, reauthenticating, or checking the connection health of a SendGrid connection, an error message appeared even if the connection was successful.

• OKTA-958093
  

  In the BambooHR connector, the List Employees card wasn't passing employee IDs to helper flows when streaming the first 200 records.