Salesforce Apex @future after summer 14

@future @summer'14
@future is an annotation that tells the system to process the data asynchronously, When you specify @future, the method executes when Salesforce has available resources.
In integrations, There are times when other systems may not respond immediately when you make a request. And in case of triggers, Apex governors do not allow callouts as it cannot keep the resources idle until the other systems respond. That's when you opt for @future.
To make a method in a class execute asynchronously, define the method with the future annotation. For example:
global class MyFutureClass {

  @future
  static void myMethod(String a, Integer i) {
    System.debug('Method called with: ' + a + ' and ' + i);
    // Perform long-running code
  }
}
See this link: https://www.salesforce.com/us/developer/docs/apexcode/Content/apex_classes_annotation_future.htm
And there are limitations which have been really headaches for a developer. Salesforce has been made aware of it by some ideas and MVPs, so they made some relaxations in this summer 14.
Some important things that have been changed in Summer 14:
Limitations
Before Summer'14
After Summer'14
Heap size  
12MB
36 MB
CPU timeout  
60,000 milliseconds
180,000 milliseconds
Number of SOQL queries
200
600
 Number of DML statements  
150
 450
Number of records that were processed as a result of DML operations
10000
20000



Happy Coding.

Comments

Post a Comment

Popular posts from this blog

Lightning spinner inside Button

I just came across this idea when I looked at some of the standard components by salesforce, for some reason they look way cooler. I thought of sharing this with you... We many a times try to use the spinner different ways, like, on the entire component, by blurring the whole area out, when I compare salesforce's components, they don't ALWAYS do that, they just show the spinner somewhere at the bottom/ top or just next to the button or disabling / replacing the button etc... Well, when I cracked it, it looked amazing. here is a simple component: <aura:component > <aura:attribute name="boooo" type="boolean" default="false"/> <lightning:buttonGroup> <lightning:buttonIcon iconName="utility:email" variant="brand" disabled="{!v.boooo}" onclick="{! c.handleClick }" alternativeText="Click to send Email" /> <lightning:button variant="brand" title
Read more

Passing URL parameters to controller in Lightning components/ AURA

Image
The following example helps you understand how to pass parameters from URL to components. In AURA/ Salesforce1 platform, it is made easy to pass the parameters to the controllers. We know that we can create attributes in the components as variables and they are meant for the scope of the components. So we create application attributes for the entire scope of application. So when we need to get the values from the URL, it is easy to pass them to application attributes, in other words, application attributes can take the values from URL directly. Here is a simple example: 1. Create an application - 'URLApp' 2. Create an attribute in the application XML. <aura:application> <aura:attribute name="fromURL" type="String" default="this is default value"/> Value in Attribute: {!v.fromURL}! </aura:application> Save the XML and run it, your output should be: Now, If you just pass a value to the url the
Read more

Nested AURA:IFs in Lightning Components Salesforce

Image
You can use use the nested IFs on the framework. Go to Developer Console>>New>>Lightning Application Give it a name, Submit Here is a sample code: <aura:application >  <aura:iteration items="1,2,3,4,5" var="item">  Iteration {!item} -  <aura:if isTrue="{!item=='1'}"> <b>In The First IF </b> <br/> <aura:set attribute="else"> <aura:if isTrue="{!item=='2'}"> <b>In The Second IF </b> <br/> <aura:set attribute="else"> <aura:if isTrue="{!item=='3'}"> <b>In The Third IF </b> <br/> <aura:set attribute="else"> <aura:if isTrue="{!item=='4'}">
Read more