SUPER COOL Features for Developers:
Limit Description |
Old Value |
New Value |
Maximum number of methods with the future annotation allowed per Apex invocation |
10 |
50 |
Maximum number of callouts (HTTP requests or Web services calls) in a transaction |
10 |
100 |
Queueable jobs are similar to future methods in that they’re both queued for execution, but they provide you with these additional benefits.
· Getting an ID for your job: When you submit your job by invoking the System.enqueueJob method, the method returns the ID of the new job. This ID corresponds to the ID of the AsyncApexJob record. You can use this ID to identify your job and monitor its progress, either through the Salesforce user interface in the Apex Jobs page, or programmatically by querying your record from AsyncApexJob.
· Chaining jobs: You can chain one job to another by starting a second job from a running job. Chaining jobs is useful if you need to do some processing that depends on another process to have run first.
· It is different from Batch job because the limits are not as high as Batchable interface and it contains only one method execute instead of 3. It is something between Future methods and Apex Batch Jobs
o Clone the repository for the Force.com IDE plug-in for Eclipse on GitHub, customize the plug-in to meet your needs, and collaborate with the growing community of Salesforce developers to build new Force.com IDE features. Check out the Force.com IDE Release Notes to see improvements that we’ve made to the plug-in.
--
You received this message because you are subscribed to the Google Groups "salesforce professionals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salesforce-profess...@googlegroups.com.
To post to this group, send email to salesforce-p...@googlegroups.com.
Visit this group at http://groups.google.com/group/salesforce-professionals.
For more options, visit https://groups.google.com/d/optout.
--
--