Matt’s Favorite Salesforce Winter ’15 Release Features

Red Argyle logo

Salesforce Winter 15 Release

Somewhat recently, Salesforce released the Winter ’15 Release Notes, and there are quite a few things in there. So many things, in fact, that it can be hard to go through and figure out the most important updates for your business. Now I’m not going to tell you what is most important for your business, but there are a couple things that I think are pretty cool about the Salesforce Winter ‘15 release. These features are not in any particular order of awesomeness–you’ll need to judge that for yourself.


It is now possible to use change sets to deploy classes that have active jobs on the target system. I’ve had multiple instances of making a change set, uploading it, and then during the deployment finding out there was a job running. Now you’ve got to put the deployment on hold, cancel the jobs, redo the deployment, and remember to re-set up the original jobs the same as they were previously. This leaves lots of room for human error. But now, after you change the deployment settings, you can just deploy with active jobs running on the target org. HUZZAH!


If you’ve uploaded and validated a change set but not yet done the deployment, you can click a new button called “Quick Deploy” that allows you to skip all the production tests and just deploy the change set directly. After you’ve done the validation on a change set, you have 4 days before you are no longer able to do a Quick Deploy. This allows you to validate your deployment ahead of time and make the last full deployment to production in a much shorter period of time–very useful when you have a small window for deployments. This is a pilot program, but at least we know it’s coming down the pipe. Learn more about Salesforce Quick Deploy here.


Salesforce is now letting us use 50 future methods and 100 callouts per transaction, much more than before. Giving us more future methods and callouts is just good across the board.


We’ve also been given an interface for a new way to do asynchronous processing. With the Queueable interface you can take a class and throw it into a queue to be processed later. It’s much like future methods but allows us to also track what is happening with the queued job. When you enqueue a job you are given an ID that can be used to monitor the AsyncApexJob. You can enqueue 50 jobs at a time, but each successive job is delayed for execution by a progressively longer amount. Eventually, the job may be delayed by 4 hours. But since you can chain Queueable jobs, you could potentially have a large number of queued jobs waiting at one time. This also allows for processing one task before another. You would just need to enqueue the first job and then wait for it to be finished before continuing your current processing.


I’m excited about the new EventLogFile functionality. The ability to log behind-the-scenes activity and get information about what users are doing and how the org is processing can be quite useful when you are trying to understand what is going on. If you are tracking down an error, it could be even more useful. I don’t know how much I’ll be able to apply this in real life yet, but I’m excited for the functionality.

This is just a small sampling of the Winter ‘15 release notes, and I recommend you look through it yourself. There are quite a few hidden nuggets of joy to be found in each Salesforce release, so go ahead and read the notes then share your comments about what things you’re most looking forward to. For more about our favorite Winter ‘15 features, check out Garry’s post here.

Red Argyle logo
Red Argyle logo

Related Blog Posts