Okta Workflows release notes (2022)

OKTA-481683

For connectors created in Connector Builder that use a helper flow as an input, the helper flow didn't log any executions when the card was tested using the Test this card button.

OKTA-563852

Changes made to the Suspicious Activity Reported event card weren't reflected in the same event card used in the Suspicious Activity Reported template. See Suspicious Activity Reported template.

OKTA-509865

The type names available for the output of Selected Outputs fields didn't reflect the new user-friendly values in Connector Builder.

OKTA-549082

Deployed cards didn't show the Click or drop here to create input option. Also the input to output mapping and the group ordering for a deployed card didn't match the order shown on the preview card.

OKTA-552021

If a dynamic input group used a helper flow with an input named extensible, the dynamic group action failed to load.

OKTA-503928

For cards that accept multiple input fields, new entries weren't created with unique field names. This resulted in a Choose a unique name error and prevented the flow from being saved.

OKTA-547809

Adding several conditions in rapid succession on an If/Else If card sometimes resulted in a condition showing that couldn't be edited.

OKTA-554161

Flow cards that return an error as output didn't report the error unless the flow was accessed during the execution of the event.

OKTA-552535

Sometimes an execution was simultaneously presented as both complete and in progress in the Workflow history until it was manually refreshed.

OKTA-555302

Some Workflows Starter users couldn't view the terms of service dialog if they had the zoom level of their resolution set too high.

OKTA-530438

The List Users Assigned to Application card in the Okta connector didn't successfully complete when large payloads were sent through the action.

OKTA-540947

The ServiceNow connector returned an unauthorized request error for some customer authorization credentials.

OKTA-525875

When renaming a folder in the Workflows console, different naming behavior occurred if the user selected the flow and clicked the pencil icon next to the name, or if they clicked the gear icon in the flow.

OKTA-531559

Creating a folder failed with a server error if the folder name was longer than 255 characters.

OKTA-537031

Sometimes testing an unsaved flow that included a helper flow event with a defined input crashed the flow designer.

OKTA-543474

A flow on the Flow Page shows errors when there weren’t any in its flow history.

Google Docs

The Google Docs connector is now available in Workflows with the following action cards:

• Create Document
• Read Document
• Update Document
• Custom API Action

See Google Docs connector.

Miro User Management

The Miro User Management connector is now available in Workflows with the following cards:

• Create User
• Read User
• Update User
• Status Upgrade
• User License Type to Full

See Miro User Management connector.

Miro Administration

The Miro Administration connector is now available in Workflows with the following cards:

• Create Team
• Search Teams
• Get Team Settings
• Add Member to Team
• Update Team Invitation Settings
• Update Team Member Role
• Update Team Discovery Settings
• Update Team Collaboration Settings
• Update Team Sharing Policy Settings
• Update Team Copy Access Settings

See Miro Administration connector.

Recorded Future Identity Intelligence

For the Recorded Future Identity Intelligence connector, the following action cards are now available:

• Get Compromised Customer Identities
• Get Compromised Workforce Identities
• Lookup Compromised Identity Details

See Recorded Future Identity Intelligence connector.

Freshservice

Freshservice updated their API to V2 on November 30, 2022. To maintain functionality for your Freshservice connector, you must replace existing cards with the updated cards.

The following action cards are updated:

• Create Ticket

• Read Ticket

• Update Ticket

• Search Tickets

• Delete Ticket

• Create User

• Read User

• Update User

• Search Users

• Deactivate User

The following event cards are updated:

• Ticket Updated

• New Ticket

See Freshservice connector.

Searchable Flow History

Workflows users can see a list of past executions in the Flow History tab of the Workflows Console, but finding specific executions can be time consuming. To make finding a specific execution easier, Workflows is introducing a new quick search text box and expanding the date filtering capabilities. This allows admins to quickly identify specific executions by performing a full-text search over any data that has passed through the flow and/or constraining executions to a short timeframe. See Check execution history.

User Notification UI improvements

We have updated the visual design of user notifications.

Dynamic group properties and fields

Workflows admins can now dynamically create a group name and fields. This gives them more control over the end user’s experience and how the group names are displayed. See Add dynamic fields and groups.

Security Solution Pack

Security Solution Pack is now available on the Workflows Console homepage and in Templates search. The Solution Pack contains a carefully curated set of templates to help solve distinct automation challenges.

Edit Properties dialog redesign

The Edit Properties dialog is redesigned for better user experience.

Updated Terms of service for Workflows Starter

A one-time disclaimer about revised terms of service is displayed to orgs on the Workflows Starter Plan.

Folder deletion enhancement

Folder deletion now supports deleting folders with inactive flows and tables.

OKTA-484456

Unexpected cards were created when an admin clicked a loading card multiple times.

OKTA-490363

The Choose Table pop-up had an incorrect title.

OKTA-534032

Some icons weren’t displayed properly in Solution Pack.

OKTA-536724

When the Searchable Flow History feature was enabled, Flow History didn’t filter results correctly if the end time was set to midnight.

Indicator for manually triggered flows (Early Access)

A loading indicator is now displayed for manually triggered flows. The indicator helps admins know that their flows were successfully triggered.

OKTA-475136

Flow Builder fields failed to render when the spelling or case didn’t match the field name.

OKTA-503448

Flows weren't properly validated when non-list object data types were used as list input.

OKTA-523362

Flow exports failed when folders were used as an input field.

OKTA-523374

In scheduled flows, the between ranges were calculated after admins clicked Save.

OKTA-507905

The Wait For function incorrectly allowed admins to set the wait time longer than 30 days.

OKTA-471074

The Find last card didn’t correctly calculate character lengths when the text contained special characters.

OKTA-509331

On the Difference card, the millisecond difference between two Date Now cards was calculated incorrectly.

OKTA-515104

Saving an authentication bottom sheet with the option Select Auth Type returned an error.

OKTA-518597

An invalid flow in Flo Designer could be successfully saved.

OKTA-530390

The Clear Empty card didn’t clear empty keys of type: date.

OKTA-514841

In Connector Builder, the User Documentation URL and Support Email Address fields weren't checked for their validity.

OKTA-515512

Dynamic drop-down menus didn’t refresh the mappings when a helper flow was selected.

OKTA-529347

Internal table column names were displayed in the UI when admins used the Tables function.

OKTA-530839

The Read Computer Group card for the JAMF Pro Classic API Connector failed with a 404 error.

Office 365 Solution Packs

The IT Operations and Seamless Office 365 Integration Solution Packs are now discoverable on the Workflows Console homepage and in Templates search. Each Solution Pack contains a carefully curated set of templates to help solve distinct automation challenges.

Searchable Flow History (Early Access)

Workflows users can see a list of past executions in the Flow History tab of the Workflows Console, but finding specific executions can be time consuming. To make finding a specific execution easier, Workflows is introducing a new quick search text box and expanding the date filtering capabilities. This allows admins to quickly identify specific executions by performing a full-text search over any data that has passed through the flow and/or constraining executions to a short timeframe. See Check execution history.

OKTA-522559

Switching between contexts in the Card Creator panel sometimes caused the panel to close.

OKTA-522554

UI elements in Flow Builder didn’t align properly.

OKTA-516576

Items in the event selection window were incorrectly aligned.

OKTA-518284

Sometimes, the templates catalog search bar didn't trigger a search.

OKTA-518285

Clearing all search filters in the template catalog didn't clear the text search.

OKTA-519404

Test connections couldn’t be viewed or created in the Connections tab or on action cards.

OKTA-493658

If an executed flow didn't contain data, the Close and go back link in its Flow History dialog didn't lead to the expected interface.

OKTA-503645

Even when cleared by a user, an input field on an action card passed data (such as zero for a number-type field) to the connector’s third-party service.

OKTA-507787

The Preview Card dialog didn’t display card details properly if a connection was not already selected.

OKTA-512229

In the Options, Inputs, or Outputs dialogs, validation markers didn’t appear when group or field names were re-edited or invalid names were added.

OKTA-512214

In the templates catalog, if a template contained only helper flows, preview screenshots didn’t appear properly in full view mode.

OKTA-512234

In the templates catalog, for templates that contain multiple flows, full view mode didn’t consistently display the selected preview image.

OKTA-512303

After full view mode was exited, the templates catalog displayed unexpected scrolling behavior.

OKTA-521959H

The XML Build card returned incorrect results in Preview environments.

OKTA-501930

On the Activate User action card for the Okta connector, when the Send Email? option was set to No, the type for the Url output field was changed to Number (instead of Text). This caused any flow that contains the card to fail if the Url output value was mapped to other fields. See Activate User.

OKTA-501951

On the Read User action card for the Okta connector, the Credentials - Emails output field was not populated with any data. See Read User.

OKTA-502931

For the SendGrid connector, the Send Email action card returned an error when the From field was populated with an email address of a verified sender. See Send Email.

OKTA-351973

In the Authentication dialog, when OAuth 2.0 was selected as the authentication type, a change to the selected option in the Client Ownership dropdown field was not displayed.

OKTA-505216

A test deployment of a connector didn’t execute authping or revoke flows.

OKTA-498102

The Read Issue action card of the Jira connector returned values that weren’t mapped correctly.

OKTA-505057

The dynamically generated input and output fields of some Smartsheet connector cards weren't displayed.

OKTA-472594

On the Inputs and Outputs dialogs, strings in the Group Name field weren’t validated.

OKTA-477744

A connection for a test deployment instead of a local deployment was unexpectedly used by locally deployed cards in a project flow.

OKTA-479715

In Connector Builder, the display for the number of flows wasn’t refreshed when a flow in a project was deleted.

OKTA-507743

For connectors that are built with Connector Builder and use OAuth 2.0 authentication, access tokens expired unexpectedly.

OKTA-489670

The Office 365 Mail authorization page was missing information about how to create a connection with a regular Office 365 account.

OKTA-501083

Third-party connector test versions were sometimes available in production orgs.

OKTA-503757

For the Tables in the Search Rows function card, a null value was returned when no search results were found.

OKTA-504021

In the Workflows app catalog, names for connectors didn’t render properly.

OKTA-485614

The Authentication dialog didn't display a validation icon and tooltip for auto-generated Config Values.

OKTA-501072

Connectors developed by customers and deployed by Okta weren't displayed properly in Workflows Designer when the local test connector and deployed connector had the same version.

OKTA-499453

Sometimes the Okta connector experienced a connection failure.

OKTA-500375

For the Okta connector, the Update Group card returned a 400 Bad Request error when the Description input field wasn't selected.

OKTA-498150

Sometimes when a connector was already available in production and a new version was submitted, a local deployment mistakenly occurred in both the connector builder’s local environment and other instances of Workflows.

OKTA-499889

Dynamic options fields didn't load the dropdown values on event or action cards.

OKTA-479605

For the Tables - Search Rows function card, the Row ID, Created, and Updated output fields were displayed even when they weren't selected as outputs in the Select fields and click “Save” dialog.

Secure Code Warrior

An Instance Region parameter is now available in the Secure Code Warrior connector’s authentication dialog. The enhancement allows users to specify a value for a data location.

See Secure Code Warrior.

Smartsheet connector

For the Smartsheet connector, the following action cards are now available:

• Add User to Group

• Add User to Organization

• List Group

• Read Group

• Read User

• Remove User from Group

• Remove User from Organization

• Search Users

• Update User

See Smartsheet connector.

OKTA-486100

For Google Workspace User cards, the Organization Path appeared incorrectly.

OKTA-491249

On the Get Users Groups action card for the Okta connector, some fields appeared incorrectly.

OKTA-496577

The Office 365 Mail Get Message card input and output fields are reformatted with no impact to performance.

Additional context-sensitive help links

Contextual help documentation is now available for the following features:

• Extensible inputs

• Test flows

• Dynamic fields

• Outputs

• Config values

OKTA-483348

For a connector whose authentication settings contained an access token, testing an authping or httphelper flow resulted in an error.

OKTA-492983

For some Workflows environments, the name of an org didn’t appear properly in the header pane.

OKTA-446171

The Add app action and Add function dialogs inside an Error Handling - If Error function card didn't render properly.

OKTA-481743

For the URL - Parse function card, a UTF-8 encoded input value with invalid characters didn’t produce an error message nor return any output values.

OKTA-488501

For a throttled flow, the delay icon didn’t render properly in the Flow History pane if it also displayed a long status message.

OKTA-492153

In list view on the Flows page, data in the History column was garbled.

New deployment validation messages

In Connector Builder, deployment validation messages for the following scenarios are now available:

• An action flow is removed.

• Static or dynamic input fields are removed from an action card.

• Static or dynamic output fields are removed from an action card.

Field preview for action cards

While adding options or fields to an action card in Connector Builder, users can now preview the fields of the card before it is deployed.

Connector Builder button

The Connector Builder button replaces the Connectors navigation item and now opens Connector Builder in a new tab.

Third-party contact fields in the connector's profile

The User Documentation URL field for a link to externally hosted documentation and the Support Email Address field for third-party contact information are now available in the connector’s Settings dialog.

OKTA-467156

For dynamically generally input fields, fields of the type option didn’t render properly.

OKTA-477034

In the Test Connection dialog, the selection of a test connection wasn’t retained from previous tests for an action flow.

OKTA-489625

A message indicating that a connector passed validation for deployment didn’t appear properly.

Execution limits for flows

The Workflows platform now includes execution limits on flows. Flow throttling is a Workflows feature that automatically detects, limits, and notifies users when specific flows consume excessive resources during a defined window of time. Flow throttling doesn't impact or prevent the completion of a flow.

See Execution limits.

Okta connector

For the Okta connector, the following event cards are now available:

• Device Activated
• Device Added to User
• Device Deactivated
• Device Deleted
• Device Enrolled
• Device Suspended
• Device Unsuspended

See Okta connector.

OKTA-448687

On the Send Email action card for the SendGrid connector, the Attachments field disappeared under the conditions in this sequential order:

1. The Attachments field contained an object.

2. The Choose fields dialog was opened and closed.

OKTA-467169

For dynamically generated fields, available field types weren't displayed.

OKTA-481450

For an action flow that invoked an inactive helper flow, the link to the flow in the connector Validation dialog didn’t lead back to the flow editor.

Office 365 Mail

For Office 365 Mail connector, the Get Message action card now includes mail options for users to access a shared or delegated email account and updated input and output fields. See Get Message.

For the Office 365 Mail connector, the following action cards are now available:

• Download Message Attachment

• Search Emails

See Office 365 Mail connector.

Google Workspace

For the Google Workspace connector, the Search Users action card now includes streaming. See Search Users.

Connector Fixes

OKTA-352387

In the Basic authentication dialog, if username or password was added as a value in the Key field, the parameter was added unexpectedly to the Credentials section and became uneditable.

OKTA-467587

The use of ? and & characters in field labels caused an unexpected validation error.

OKTA-480684

In the OAuth authentication dialog, the values in the Key field for Client ID and Client Secret were editable and deletable.

OKTA-481366

In any authentication dialog, if access_token or refresh_token was added to the Key field for a parameter, the parameter row disappeared.

OKTA-391123

A connection for a deployed connector that was created in Connector Builder using OAuth authentication wasn't refreshed when its access token expired.

OKTA-472777

In the Config Values section of the Authentication dialog, an expected validation error didn’t occur when the Value from Helper Flow option was selected but a helper flow wasn’t specified.

OKTA-478212

In the Authentication dialog, the key for a config value wasn’t generated automatically if the Label field contained special characters only.

OKTA-460727

For the Tables function, an error was returned if the Search Rows card was included in a flow that ran every five minutes, or if the Table ID field contained an invalid value.

OKTA-463583

Using the Download in SVG format button to download a flow chart resulted in an error.

OKTA-467211

In the Workflows interface, the loading icon wasn’t visible.

OKTA-478578

For the GitHub connector, the Update File Content action card returned an error when the target file exceeded 1MB in size.

Jamf Pro Classic API

For the Jamf connector, the following action cards are now available:

• Add Computer to Static Computer Group

• Add Mobile Device to Static Mobile Device Group

• Create Static Computer Group

• Create Static Mobile Device Group

• Delete Computer Group

• Delete Mobile Device Group

• Read Computer Group

• Remove Computer from Static Computer Group

• Remove Mobile Device from Static Mobile Device Group

See Jamf Pro Classic API connector.

Azure Active Directory

For the Azure Active Directory connector, the following action cards are now available:

• Assign Manager

• Create Contact

• List Contact Folders

• Read User Manager

• Revoke User Sign In Sessions

• Search Contacts

See Azure Active Directory connector.

Atlassian Admin

For the Atlassian Admin connector, a Jira Account ID output field is now available on the following cards:

• Create User

• Get User

• Search Users

See Atlassian Admin connector.

AWS S3

For the AWS S3 connector, the following action cards are now available:

• Copy Object

• Custom API Action

• Search Buckets

• Search Objects

• Tag Object

See AWS S3 connector.

Okta

For the Okta connector, the following event and action cards are now available:

• Search System Logs (action)

• User Account Locked

• User Account Unlocked

See Okta connector.

AWS S3

The AWS S3 connector is now available with the following action cards:

• Create Bucket

• Delete Bucket

• Delete Object

• Download Object

• Read Object

• Read Object Tags

See AWS S3 connector.

Secure Code Warrior

The Secure Code Warrior connector is now available with the following action cards:

• Check Assessment Completion for User

• Check Course Completion for User

• Custom API Action

• Get Assessment Attempts for User

• List Course Enrollments for User

See Secure Code Warrior.

Gmail

For the Gmail connector, several enhancements are now available in action cards:

• The Google Cloud Platform Project and Service Account dropdown fields now list a maximum of 100 options.

• The Enter Service Account Email option is now available on the Google Cloud Platform Project and Service Account dropdown fields.

• If options on the Google Cloud Platform Project or the Service Account dropdown fields fail to load, the Enter Service Account Email option will appear as the only available option.

• When Enter Service Account Email is selected from the Service Account dropdown field, an additional Email input field in the Service Account section of the card appears.

These enhancements are available on the following cards:

• Add Delegate

• Add Send-As Alias

• Delete Delegate

• Delete Send-As Alias

• Forward Emails

• List Delegates

• Set Auto Reply

• Update User Gmail Settings

See Gmail connector.

Slack

For the Slack connector, several enhancements are now available in event and action cards:

• A maximum of 200 public and 200 private channels (as applicable on some cards) now appear in the Channel dropdown field.

• For action cards, when a failure occurs and no channels are listed in the Channel dropdown field, an Enter Channel ID option appears.

These enhancements are available on the following cards:

• Archive Channel

• Get Users in Channel

• Invite User to Channel

• Join Channel

• Leave Channel

• New Message in Channel (event)

• New Message in Private Channel (event)

• New Pinned Message (event)

• Read Message History

• Remove User from Channel

• Rename Channel

• Send Ephemeral Message

• Send File to Channel

• Send Message to Channel

See Slack connector.

Zendesk

For the Zendeskconnector, retries for error handling are no longer available on the following event cards:

• New Comment on Ticket

• New Ticket

• Updated Organization

• Updated Ticket

See Zendesk connector.

Microsoft Teams

For the Microsoft Teams connector, the following action cards are now available:

• Create Chat

• Search Channels

• Search Chats

• Send Message to Channel

• Send Message in Chat

For the Create Channel card, the Members field has been replaced with the User IDs field.

The following scopes are now available:

• Channel.Create

• ChannelSettings.ReadWrite.All

• ChannelMessage.Send

• Chat.ReadWrite

See Microsoft Teams connector.

Office 365 Calendar

The Office 365 Calendar connector is now available with the following action cards:

• Create Event

• Custom API Action

• Delete Event

• List Calendars

• Read Event

• Search Events

• Search Rooms

• Update Event

See Office 365 Calendar connector.

Office 365 Mail

For the Office 365 Mail connector, the Custom API Action card and the following scopes are now available:

• Mail.ReadWrite

• Mail.Send

• Mail.Send.Shared

• Mail.ReadWrite.Shared

• offline_access

See Office 365 Mail connector.

OneDrive

The OneDrive connector is now available with the following event and action cards:

• Create Folder

• Create Organization Sharing Link

• Create Recipients Sharing Link

• Custom API Action

• Delete Permission

• Download File

• File or Folder Updated (event)

• List Permissions

• Move File or Folder

• Read File or Folder

• Search Files or Folders

• Upload File

See OneDrive connector.

Secure Code Warrior

The Secure Code Warrior connector is now available with the following action cards:

• Check Assessment Completion for User

• Check Course Completion for User

• Custom API Action

• Get Assessment Attempts for User

• List Course Enrollments for User

See Secure Code Warrior.

HubSpot CRM

For the HubSpot CRM connector, the contacts scope has been deprecated. The following scopes are now available:

• crm.objects.contacts.write
• crm.objects.contacts.read
• crm.objects.companies.write
• crm.objects.companies.write

To ensure that these granular scopes are granted to your HubSpot CRM application, reauthenticate your HubSpot CRM connections by February 28, 2022.

See Authorization

Box

For the Box connector, the following event cards are now available:

• Collaboration Created

• File Moved

• File Uploaded

• Folder Created

• Shared Link Created

• Shared Link Updated

See Box connector.