There are multiple processes in Salesforce to execute your law asynchronously. In this post, we will bandy using the unborn system in Salesforce.
What Is the Future Method In Salesforce?
An unborn run asynchronously. You can call an unborn system for executing long-running operations, similar to callouts to external Web services or any operation you’d like to run in its thread, on its own time. Each future system is queued and executes when system coffers become available. That way, the prosecution of your law doesn’t have to stay for the completion of a long-running operation.
Unborn system in Salesforce
Future system syntax
To define an unborn system, simply annotate it with the unborn reflection, as follows-
global class MyClass{
public static void myFutureMethod(){
/ Perform some operations
unborn system Consideration
styles with the unborn reflection must be stationary styles
can only return a void type
styles with the unborn reflection can not take sObjects or objects as arguments.
You can bring unborn styles the same way you bring any other system. Still, an unborn system can’t bring another future system
No further than 50 system calls per Apex incantation
Asynchronous calls, similar as@future or executeBatch, called in a startest, stopTest block, don't count against your limits for the number of queued jobs
The maximum number of unborn system conjurations per a 24-hour period is 250,000 or the number of stoner licenses in your association multiplied by 200, whichever is lesser
To test styles defined with the unborn reflection, call the class containing the system in a startTest(), stopTest() law block. All asynchronous calls made after the start test system are collected by the system.
Why sObjects cannot be passed as arguments in the unborn system?
In this case, the unborn system will get the old subject values and might overwrite them. To work with sObjects that formerly lived in the database, pass the sObject ID ( or collection of IDs) and use the ID to perform a query for the most over-to-date record.
What Is The Use Of The Unborn System In Salesforce?
There are numerous use cases when we can use the unborn styles in Salesforce.
Avoid the CPU time limit Error To avoid the log running talk and avoid the CPU time limit we can use the@Future system in Salesforce. Learn further about Apex CPU Time Limit Exceeded.
Callout from Detector As we know we can not do the callout from the detector but we can bring callouts from triggers by recapitulating the callout's future styles.
Avoid Mixed DML operation A Mixed DML operation error occurs when you try to persist in the same sale, change to a Setup Object, and anon-Setup Object.
You can also make use of unborn styles to insulate DML operations on different sObject types to help the mixed DML error.
Advanced governor limit A benefit of using unborn styles is that some governor limits are advanced, similar to SOQL query limits and mound size limits.
