---
schema_version: "1"
id: 1e4e39f9f912b59f8e84cad376c700a432dd7296ee192a0531befd4837474a0c
title: Spring ’25 (API Version 63.0)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_flow_versioned_updates_63.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_flow_versioned_updates_63.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 27da849fe1966dc89dd8e8107ef5b1968f444a5ce38a1a18f433dc7eca80c345
description: These updates affect only flows that are configured to run on API version 63.0 and later.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Spring ’25 (API Version 63.0)

These updates affect only flows that are configured to run on API version 63.0 and later.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr></tbody></table>

## Clear a Reactive Data Table If the Source Collection Isn't Set

If a Data Table component's source collection is the output of a screen action, and the screen action's autolaunched flow doesn't set a value for the output collection, the Data Table contents are cleared. For example, let's say that a Data Table component is populated with records from a screen action's output record collection. Then, the screen action is triggered again, but this time the output record collection isn't assigned any records. The records that were in the Data Table from the first time the screen action ran are now cleared from the Data Table. Previously, the records that were in the Data Table from the first time the screen action ran would remain in the Data Table.

## Variables with Same Names in Parent and Referenced Flows Were Changed

Variables with the same API names in a referenced flow and parent flow no longer inherit values from the parent flow. For example, a screen flow creates an account that assigns a value to the group\_type variable. The screen flow includes the Subflow element that runs a referenced flow. The referenced flow also includes a group\_type variable. The Decision element in the referenced flow checks the value of the group\_type variable that’s set in the referenced flow and not inherited from the parent flow. The flow follows different outcome paths depending on the value of the group\_type variable.

## View Immediate Feedback from Screen Components with Invalid Values

Your flow user can see whether an input value in a flow screen component is invalid when the user changes the focus to outside the component. For example, the user enters a value for an email component. The component validates that the input value contains the right domain as soon as your user clicks another screen component. Previously, component validation error messages appeared only when you moved to another screen or finished the flow.