Salesforce Summer’24 Release Notes | Apex – Page 4 – Salesforce Training Articles & Latest News

Use Cursors for Expanded SOQL Query Result Support

With Apex cursors, you can work with large query result sets while not actually returning the entire result set. Cursors will break up the processing of a SOQL query result into pieces that can be processed within the bounds of a single transaction. Query results can be traversed in parts, with the flexibility to navigate forward and back in the result set. Cursors are a more powerful alternative to batch Apex that can be used in a chain of queueable Apex jobs, addressing this way of batch Apex’s limitations.

How: A cursor is created when a SOQL query is executed on a Database.getCursor() or Database.getCursorWithBinds() call. When a Cursor.fetch(integer position, integer count) method is invoked with an offset position and the count of records to fetch, the corresponding rows are returned from the cursor. To get the number of cursor rows returned from the SOQL query, use Cursor.getNumRecords() . You must track the offsets or positions of the results within your particular processing scenario

Exceptions: Apex cursors throw the following new system exceptions: - System.FatalCursorException - System.TransientCursorException , transactions that fail with System.TransientCursorException can be retried

Limits: Apex cursors have the same expiration limits as API Query cursors: - Maximum number of rows per cursor: 50 million (both synchronous and asynchronous) - Maximum number of fetch calls per transaction: 10 (both synchronous and asynchronous) - Maximum number of rows per day (aggregate limit): 100 million - Maximum number of rows per day (aggregate limit): 100 million To get these limits, use these new methods in the Limits class: - Limits.getApexCursorRows() and its upper bound Limits.getLimitApexCursorRows() method - Limits.getFetchCallsOnApexCursor() and its upper bound Limits.getLimitFetchCallsOnApexCursor() method

Apex Cursor Class Example

Evaluate Dynamic Formulas in Apex (Beta)

Dynamic formulas in Apex now support using an Sobject as the context object

How: Use the new Formula.builder() method to create and build an instance of the FormulaBuilder and uses an SObject type as the context object in the withType() method

// Below formula will be true when account Type is populated

FormulaEval.FormulaInstance ff = Formula.builder() .withReturnType(FormulaEval.FormulaReturnType.Boolean) .withType(Account.SObjectType) .withFormula('NOT(ISBLANK(TEXT(Type)))') .build();

Boolean typeIsNotBlank = (Boolean)ff.evaluate(new Account(Name='Test Account', Type='Prospect')); Assert.isTrue(typeIsNotBlank);

Support up to Five-Level Parent-to-Child Relationship SOQL Queries in Apex

Apex now supports in API versions 61.0 and later SOQL relationship queries that traverse up to five levels of parent-child records (the parent root as the first level of the query and child relationships up to four levels deep from the parent root). Each parent-child relationship subquery counts towards the number of aggregate queries processed in an SOQL query statement. The following aggregate methods are available:

Limits.getAggregateQueries(), track the number of aggregate queries processed in an SQL statement

Limits.getLimitAggregateQueries(), returns a value of 300, which is the total number of aggregate queries that can be processed with SOQL query statements

SOQL Query and aggregate methods

Limits.getAggregateQueries() & Limits.getLimitAggregateQueries() output

[NEW] defaultValue and placeholderText Modifiers for Invocable Actions

The following two new modifiers are available when annotating a InvocableVariable:

defaultValue (optional), set the default value for the variable. Valid invocable variable data types are: Boolean

Decimal

Double

Integer

Long

String

placeholderText (optional), provides examples or additional guidance about the invocable variable, such as examples of values that can set the invocable variable. Valid invocable variable data types are: Double

Integer

String

Both new modifiers appear in Flow Builder for the Action elements that correspond to an invocable method

defaultValue and placeholderText modifiers for invocable variable

Monitor and Schedule Apex Scheduled Jobs More Efficiently

Starting from Summer '24, you will be able to do the following from the All Scheduled Jobs page

Track the percentage of the scheduled jobs used

Mitigate potential limit problems before they happen by tracking the percentage of the scheduled jobs used.

How: From Setup, in the Quick Find box, enter Scheduled Jobs, and then select Scheduled Jobs. On the All Scheduled Jobs page, view the current consumption stats for the scheduled jobs along with the allowed org limit

Percentage of Scheduled Jobs Used

Schedule Apex jobs or Reschedule scheduled jobs using cron expressions

How: From Setup, in the Quick Find box, enter Scheduled Jobs, and then select Scheduled Jobs. On the All Scheduled Jobs page

Click Scheduled Apex button and select Cron Expression to schedule a new job using a cron expression instead of the Schedule Builder

Click Manage next to the Scheduled job you want to reschedule, change the current Cron Expression and then click Reschedule Job

Schedule new apex job using cron expression

Reschedule existing apex job using cron expression

View the ID of the CronTrigger object associated with scheduled jobs

How: From Setup, in the Quick Find box, enter Scheduled Jobs, and then select Scheduled Jobs. Cron Trigger Id is in the scheduled job details on the All Scheduled Job page

Private Methods of Abstract or Virtual Classes Not Overridden in Newer API Versions

Starting from API version 61.0 and later, private methods are no longer overridden by an instance method with the same signature in a subclass. This change is versioned, so to prevent the override, update your abstract or virtual classes that contain private methods to API version 61.0 or later.

Previously: In API version 60.0 and earlier, if a subclass declares an instance method with the same signature as a private method in one of its superclasses, the private method is overridden by the method in the subclass.

Monitor Setup Methods Using ApexTestResult

Benchmark Test Setup performance along with Test Methods in order to improve the run time of your test classes by using ApexTestResult and ApexTestRunResult objects. ApexTestResult rows are now generated for Apex tests run with the @testSetup annotation. A new IsTestSetup column is set to true for these annotated tests to distinguish them from other test methods and a new TestSetupTime column to track the cumulative time of all setup methods for the given ApexTestRunResult.

Previously: Information about Apex test methods with @testSetup annotation limits and cumulative run time was available only by parsing the appropriate method sections in the debug log

How: After the tests are executed, run the following query to get the results of an Apex test method execution

SELECT ID, AsyncApexJobId, IsTestSetup, MethodName, Outcome, RunTime FROM ApexTestResult

ApexTestResult object

To get a summary information about all the test methods that were run in a particular Apex job, run the following query

SELECT ID, AsyncApexJobId, JobName, Status, TestSetupTime, TestTime FROM ApexTestRunResult

ApexTestRunResult Object

Scheduled and Batch Apex Error Messages Improved

You can now see CronTrigger and batch job IDs in error messages generated when you delete or modify a class in use by a scheduled or batch job. If you try to uninstall a package containing a class that’s in use by a batch job, the error message also includes the Apex batch job ID. Also, if you modify a class that’s being used by a batch job, the error message includes the AsyncApexJob ID

Compilation of Apex Classes is more Secured

Run the Compile all classes on the Apex Classes page in Setup to compile all the Apex classes in your organization. If you have classes that are installed from a managed package and that have test methods or are test classes, you must compile these classes first before you can view them and run their test methods from the Apex Test Execution page. Managed package classes can be compiled only through the Compile all classes link because they cannot be saved. Otherwise, saving Apex classes that aren't from a managed package causes them to be recompiled. This link compiles all the Apex classes in your organization, whether or not they are from a managed package

Improved Logging When FOR UPDATE Locks Are Released

Information regarding released record locks that are obtained in Apex using FOR UPDATE when you roll back to a savepoint that's set using the Database.setSavePoint() method is now logged in the debug log

// Create a savepoint Savepoint sp = Database.setSavepoint();

// Get the account to change Account a = [SELECT ID, Name, AccountNumber FROM ACCOUNT WHERE Name = 'xyz' LIMIT 1 FOR UPDATE];

// Change the account number a.AccountNumber = '123'; update a;

// Rollback to the previous value Database.rollback(sp);

Logging message in debug log after FOR UPDATE locks released

Additional Information in Apex Exception Emails Included for faster Resolve Unhandled Exceptions

When Apex code encounters unhandled exceptions, Apex exception emails now include the org name and My Domain name where the exception occurred. These additional details can be used to resolve the exception faster and improve the performance of your Apex code.

Previously: Apex exception email included only the Apex stack trace, exception message, and the customer’s org and user ID

getRelationshipOrder Method Support Standard Fields

Standard fields are now supported when calling DescribeFieldResult.getRelationshipOrder method. The method will return 0 if the field is the primary relationship field or 1 if the field is the secondary relationship field

Previously: The method always returned null for standard fields

Integer locationRelationshipOrder = LocationGroupAssignment.LocationId.getDescribe().getRelationshipOrder(); Integer locationGroupRelationshipOrder = LocationGroupAssignment.LocationGroupId.getDescribe().getRelationshipOrder(); System.debug('Location relationship order : ' + locationRelationshipOrder); System.debug('Location Group relationship order : ' + locationGroupRelationshipOrder);

Orders for primary and secondary master-detail fields of Location Group Assignment object

Salesforce Summer’24 Release Notes | Apex

Salesforce Summer’24 Release Notes | Permissions and Sharing

Salesforce Summer’24 Release Notes | General Setup

Antonis Melakis

Salesforce Summer'24 Release Notes | General Setup

Leave a Reply Cancel reply

Recent Posts

Recent Comments

Welcome Back!

Retrieve your password