---
schema_version: "1"
id: 3e4d426dbc7b5629615c917624ace992bd954f4f36d8be144d4b2bf39fc5e39e
title: Flow and Process Release Updates
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_automate_flow_release_update.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_release_update.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 45790b149195487170db17c7bac5abf7870d80af6a1e631c8d11e1ba5db90560
description: Salesforce Flow has several release updates that are scheduled to be enforced in future releases.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Flow and Process Release Updates

Salesforce Flow has several release updates that are scheduled to be enforced in future releases.

- **[Enforcing No-Argument Constructor on Apex Classes Used for Invocable Action Parameters (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_release_update_enforce_perm_requirements_on_built_in_apex_classes.htm&release=260&type=5)**  
    When this update is enabled, you get access to certain built-in Apex classes that are available to be used as invocable action parameters. Additionally, this update enforces the visibility of the no-argument constructor on any class. This update was scheduled to be enforced in Summer ’26. Starting in Spring ’26, Salesforce no longer enforces this update, but we recommend that you enable it. This release update was previously named Enforce Permission Requirements Defined on Built-In Apex Classes Used as Inputs.
- **[Sort Apex Batch Action Results by Request Order (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_release_update_sort_apex_batch_action_result_by_request_order.htm&release=260&type=5)**  
    With this update enabled, Apex batch action results are shown in the order that the requests are received. Currently, error-prone requests are prioritized at the top of the result list, and successful requests are at the bottom.