---
schema_version: "1"
id: f599a5b89447730c1b6a55b73c21d74ed533d8aff8512a66d60f9b540e8a681e
title: Flow and Process Run-Time Changes in API Version 66.0
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_versioned_updates.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_versioned_updates.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ddb232ed5f07abc8c7c1f852af0d0f13f3d2dc29d2d5a20e9b3934f67f057ceb
description: These updates affect only flows and processes that are configured to run on API version 66.0 or later.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Flow and Process Run-Time Changes in API Version 66.0

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

**Where:** This change applies to Lightning Experience, Salesforce Classic, and all versions of the mobile app in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

**How:** With versioned updates you can test and adopt run-time behavior changes for individual flows and processes at your convenience. To change the run-time API version of a flow, open it in Flow Builder and edit the flow version properties. To change the run-time API version of a process, open it in Process Builder and edit its properties.

Enforce No-Argument Constructor on Apex Classes

With this versioned update, you can access certain built-in Apex classes that are available to be used as invocable action parameters. This versioned update enforces no-argument constructor visibility of all Apex classes, including the `invocableVariable` Apex class. Public no-argument constructors in managed packages are visible only when the access code is in the same package. An Apex action that refers to a non-visible no-argument constructor `invocableVariable` Apex class results in errors.

Record-Triggered Flows Issue with Non-Insertable Fields Was Fixed

Record-triggered flows that run before records are saved now respect the internal writeable status of non-insertable fields. If existing flows try to update fields that aren’t editable, this error message appears: Invalid target field for field update.