> For the complete documentation index, see [llms.txt](https://docs.valorx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valorx.com/valorx-fusion/versions-and-release-notes/windows/fusion-version-23.md).

# September 26 Release (v23)

Fusion v23 introduces new ways to work with API data, making it easier to bring external data into your workflows and display it in Grid Maps and Form Maps. This release also adds more flexibility to Dynamic API authentication and Notification Tasks, along with fixes for State Management and Microsoft Dynamics authentication.

Explore what’s new in **Fusion v23** and download the latest version [here](https://valorx.com/fusion-support/)!

***

<h2 align="center"><mark style="color:purple;">New Enhancements</mark><span data-gb-custom-inline data-tag="emoji" data-code="2728">✨</span></h2>

### Turn API Responses into Datasets for Grid and Form Maps

You can now turn a Dynamic API response into a **Dataset** and display it in a **Grid Map or Form Map** using a Display Task.

To set it up, map the records in the API response to a Dataset, then link each value, such as **Id, Name, or Type**, to a Dataset field. Add a Display Task, and your API data appears in a Grid Map or Form Map, ready for users to view and work with.

This makes it easy to bring data from Salesforce or other systems into Fusion and display it in a layout users already know.

Learn more about saving the response as a Dataset [here](/valorx-fusion/design-studio/tasks/dynamic-api.md#save-the-response-as-a-dataset).

<figure><img src="https://2472585788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFqFFf4143HS0_Wagnz%2Fuploads%2FpJs9mMIexWDX7dGFYcAj%2FTurn%20API%20Responses%20into%20Datasets%20for%20Grid%20and%20Form%20Maps.gif?alt=media&amp;token=71f45ec9-ef3d-4c73-99b6-ea29bb0305ce" alt=""><figcaption><p>Turn API Responses into Datasets for Grid and Form Maps</p></figcaption></figure>

### Use the Logged-In User Token with Bearer Token Authentication

Dynamic API now supports [**Logged-In User Token**](/valorx-fusion/design-studio/tasks/dynamic-api.md#authorization) with [**Bearer Token**](/valorx-fusion/design-studio/tasks/dynamic-api.md#authorization) authentication. Instead of generating a new token at runtime using OAuth or entering an API token manually, you can select the signed-in user's token from the **Token** dropdown.

This makes Salesforce API connections easier to set up and maintain, without the need to manually copy, store, or refresh tokens.

<figure><img src="https://2472585788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFqFFf4143HS0_Wagnz%2Fuploads%2F1jutO2nVYwUvcrfGtsSJ%2FUse%20the%20Logged-In%20User%20Token%20with%20Bearer%20Token%20Authentication.gif?alt=media&amp;token=981f1a96-efa4-4c0f-8dbc-95c6960685a4" alt=""><figcaption><p>Use the Logged-In User Token with Bearer Token Authentication</p></figcaption></figure>

### Capture Data on the False Button in Notification Tasks

[Notification Tasks](/valorx-fusion/design-studio/workflow-and-ux/common-tasks.md#notification) using **Custom options** with **Configure Data Capture** can now capture data when users click the **False** button, in addition to **True** button.

The new **Allow Data Capturing on False Button** option lets you choose whether the False button saves the user's input to the assigned cell or Named Range before continuing along the False workflow path.

This is especially useful for approvals, rejections, or feedback prompts where the reason behind the response matters.

<figure><img src="https://2472585788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFqFFf4143HS0_Wagnz%2Fuploads%2F6o9xDJcN8vAdbWcYK3WO%2FCapture%20Data%20on%20the%20False%20Button%20in%20Notification%20Tasks.gif?alt=media&amp;token=681eb990-75b7-45f1-8358-dbdda294fedb" alt=""><figcaption><p>Capture Data on the False Button in Notification Tasks</p></figcaption></figure>

***

<h2 align="center"><mark style="color:blue;">Bug Fixes</mark> 🐞</h2>

Along with other improvements, this release fixes the following issues. Here are the details of the bug fixes included:

* **State Management Named Range Configuration**

  Fixed an issue where the selected Named Range was not saved in the State Management task configuration. The selected Named Range and its value are now saved correctly and used to match values at runtime.
* **Microsoft Dynamics Authentication**\
  Fixed an issue with processing client information returned by Microsoft during authentication. Dynamics connections can now be established successfully.

***

Thank you for using Valorx Fusion. We’re continuously improving Fusion to make it easier to build, manage, and work with your workflows.

For assistance, please visit our [Valorx Support page](https://valorx.com/support/).