« PaaS | Main | Features Added to DupeCatcher »

Salesforce Summer '11 Features

I am working my way through the Salesforce Summer '11 Features and Release Notes. There are good upgrades worthy of note and too many for one post. I started a chart for myself that I will share and found a good and brief description of the new features on, that I have used on the chart below. For more detail, click here to access the release notes or here to look at the page on

I am only going to show part of my chart today, saving more for another day, because I think it's enough to take in for one day! This list comes from the categories, App Distribution and App Logic. More in the next post!

Package Upload Monitoring

In Summer ’11, you can now track your package uploads through every step, including Apex test runs. During the upload process, you can view real-time upload indicators on the package and package-version pages to track progress and ensure success.


Better Batch Job Testing

Starting with Apex saved using Salesforce API version 22.0, exceptions that occur during the execution of a batch Apex job that is invoked by a test method are now passed to the calling test method, and as a result, causes the test method to fail.


If you want to handle exceptions in the test method, enclose the code in try and catch statements. You must place the catch block after the stopTest method.
Apex REST (pilot) The (pilot) Apex REST feature lets you implement custom web services in Apex and expose them via REST architecture.

Six new annotations have been added to Apex. They are used to annotate the Apex class you develop to implement your REST API. The primary annotation is @RestResource(urlMapping='yourURL'), used to identify the Apex class that provides an implementation for your REST API.

You can authenticate when calling the REST services using either a session ID, or via OAuth 2.0. The REST services themselves support both XML and JSON.


Cloning Enhancements An additional optional argument has been added to the List deepClone and the sObject clone methods that allows you to choose whether the read-only fields CreatedById, CreatedDate, LastModifiedById, and LastModifiedDate are copied to the cloned copy.

This can also be used to choose whether the auto number fields are copied to the cloned copy.


New System.URL Class

Use the methods of the System.URL class to create links to objects in your organization. Such objects can be files, images, logos, or records that you want to include in external emails, in activities, or in Chatter posts.


Class & Trigger Log Filters Summer ’11 lets you toggle the log fidelity at the class or trigger level, so that you can immediately filter unwanted information from the debug logs and find the information you need.

For example, to evaluate the output of a complex process, you can raise the log verbosity for a given class while turning off logging for other classes or triggers within a single request.

When you override the debug log levels for a class or trigger, these debug levels also apply to the class methods that your class or trigger calls and the triggers that get executed as a result. All class methods and triggers in the execution path inherit the debug log settings from their caller, unless they have these settings overridden.


Async Test Console Summer ’11 brings real-time visibility into your test-code execution. The Async Test Console is the latest of many features that help developers test and debug code. The new console is packed with useful features, letting you add and abort tests within a run, persist test results, and even look at an historical view of test execution. This feature makes it easier to evaluate code coverage without spending time to re-run all your tests.

Two new pages have been added that make it even easier to run your Apex unit tests.

Apex Test Execution Run just one, a set, or all the tests in your organization. Tests are run asynchronously: start them, then go work on other things. You can then monitor the tests, add more tests to the ones that are running, or abort running tests. Once a test finishes running, you can see additional information about that test run. For example, if there were any errors, the first error message displays, as well as the stack trace. Click Your Name ➤ Setup ➤ Develop ➤ Apex Test Execution.

Apex Test Results See all the test results for your organization. Click Your Name ➤ Setup ➤ Develop ➤ Apex Test Execution ➤ View Test History. You can add filters to view just the results you want to see by creating a view. Test results remain for 30 days after they finish running, or until cleared.



PrintView Printer Friendly Version

EmailEmail Article to Friend

References (1)

References allow you to track sources for this article, as well as articles that were written in response to this article.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
All HTML will be escaped. Hyperlinks will be created for URLs automatically.