# Week 16, 2024
### New Okta Workflow Connector
We’re thrilled to announce that our Okta Workflow Connector is now live in production for Okta workflow users. Setting up an API client within the Cisco Identity Intelligence platform is the first step in utilizing Okta Workflows. Once completed simply navigate to Okta workflows and choose ‘New Connection’ to find the ‘Cisco Identity Intelligence’ connector. Once configured, you’ll gain the ability to establish the ‘Identity Intelligence Webhook’ and construct your workflow. Whenever a check failure event occurs in the Cisco Identity Intelligence platform, it will kick off your automated workflow.
This provides a more automated method to build customized flows using failed check data from ‘Cisco Identity Intelligence’ to retrieve end-user information and initiate additional actions seamlessly.
Read more about how to set-up Okta Workflows [here](https://docs.oort.io/integrations/okta-workflows).
### Activity Flow Enhancements
In a previous release, we introduced the ‘Activity Flow over the Past 30 days’ widget on the Users Overview tab. The widget offers a visual representation of users’ activities, including locations visited, applications access, and related events. In this latest release, we’ve enhanced the functionality by enabling filtering of the Activity Flow for deeper investigation of events.
By clicking on the colored bands in the activity flow, you’ll be directed to a filtered ‘Activity’ tab displaying events related to what was shown on the activity flow.
### Bug Fixes and Minor Improvements
* **Sensitive applications widget.** Bug fix for sensitive applications widget showing blank when you have sensitive applications defined.
* **Search by provider user key and employee type.** You can now search by provider user key and employeetype when querying in advance mode.
* **User actions are now tailored to user integrations.** Now in the platform, the ‘Actions’ button will only show the available actions depending on the user integrations that are configured for the tenant.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.oort.io/release-notes/week-16-2024.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.