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.
Where: This change applies to Lightning Experience and Salesforce Classic (not available in all orgs) in Enterprise, Performance, Unlimited, and Developer editions
When: This update was scheduled to be enforced in Summer ’26. Starting Spring ’26, Salesforce no longer enforces this update
How: When you enable this update, built-in Apex classes that were unavailable become available for Apex actions. Because of this change, the visibility of the no-argument constructor for the invocableVariable Apex class is also enforced. Public no-argument constructors in managed packages are no longer visible unless 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.
From Setup, in the Quick Find box, enter Release Updates, and then select Release Updates. To get the Enforcing No-Argument Constructor on Apex Classes Used for Invocable Action Parameters release update, follow the testing and activation steps.
If you don’t enable this update, a versioned change implements the 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