Salesforce's Summer ’16 release is here

Apex Enhancements

Previously, there were individual limits on the number of calls that could be made to the following types of asynchronous actions (per transaction):

Methods with the future annotation (@future)

Jobs added to the queue with the System.enqueueJob method

Classes scheduled concurrently with the System.schedule method

Batch Apex jobs scheduled with the Database.executeBatch method

Salesforce replaced these limits with a consolidated limit. You can now make up to 200 asynchronous calls of any type in a single Apex transaction. Feel free to mix and match future, queued, scheduled, and batch calls within a single transaction, up to a limit of 200.

Two new methods have been added to the System.Limits class that return information about the new asynchronous limit:

Salesforce increased the number of unique, certified namespaces that can be invoked during a single Apex transaction. Previously, the limit during a single transaction was 10. Salesforce removed this limit and added a cumulative cross-namespace limit.

There’s now no limit on the number of certified namespaces that can be invoked in a single transaction. However, the number of operations that can be performed in each namespace must not exceed the per-transaction limits. In place of the former limit, there’s a new limit on the cumulative number of operations that can be made across namespaces in a transaction. This cumulative limit is 11 times the per-namespace limit. For example, if the per-namespace limit for SOQL queries is 100, a single transaction can perform up to 1,100 SOQL queries. In this case, the cumulative limit is 11 times the per-namespace limit of 100. These queries can be performed across an unlimited number of namespaces, as long as any one namespace doesn't have more than 100 queries.

To access Apex REST classes from JavaScript in a web browser, add the origin that’s serving the script to the CORS whitelist. To add an origin to the CORS whitelist, from Setup, enter CORS in the Quick Find box, then select CORS. Click New, and then enter an origin URL pattern.

Lightning Components

To use Lightining components in VF page/Community or as a tab. We have to write some kind of interfaces to code itself. With this release, Salesforce makes it easy for developers by giving these options at time of creation of Lightning component/bundle. The following configurations are available for creating a component.

Debugging in lightining components were very difficult before this. With this release, Salesforce Lightning Inspector gives you more insight into what’s happening under the covers when you’re developing Lightning components.

The Salesforce Lightning Inspector is a Google Chrome DevTools extension that helps you debug Lightning components and profile component performance.

Capture the essential values of your visual design into named tokens. Define the token values once and reuse them throughout your Lightning components CSS resources. Tokens make it easy to ensure that your design is consistent, and even easier to update it as your design evolves.