---
schema_version: "1"
id: 9bd131ee33c0fdd6e1dc925ca95a8b06e0c0aca22062df6c9dbc45fbba0c4303
title: Provide Visible No-Argument Constructors for Custom Apex Classes Used as Invocable Action Parameters in API Version 66.0 and Later
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_apex_constructor_visibility_invocable_custom_classes_v66.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_apex_constructor_visibility_invocable_custom_classes_v66.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c24595b1cc13c3b94db176420b7691f8ad2d7b5b9db6c6199e426dec39d101ee
description: If you haven't enabled the Enforcing No-Argument Constructor release update, a versioned change now implements this requirement. Starting in API version 66.0, Apex classes used for invocable action parameters must have a visible no-argument constructor. The constructor must be public for non-packaged classes or global for packaged classes invoked from outside the package. Use API version 65.0 or earlier with the release update disabled to maintain the previous behavior.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Provide Visible No-Argument Constructors for Custom Apex Classes Used as Invocable Action Parameters in API Version 66.0 and Later

If you haven't enabled the Enforcing No-Argument Constructor release update, a versioned change now implements this requirement. Starting in API version 66.0, Apex classes used for invocable action parameters must have a visible no-argument constructor. The constructor must be public for non-packaged classes or global for packaged classes invoked from outside the package. Use API version 65.0 or earlier with the release update disabled to maintain the previous behavior.

**Where:** This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.

#### See Also

- [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.")