In continuing with our series on the release of Salesforce Spring ‘15, I have combed through the Salesforce Spring ’15 release notes to find the changes that I am most excited about (on a related note, if you haven’t already, check out Zach’s blog post and Ashley’s blog post for their favorite features). Keep on reading to check out what I’m looking forward to and then make sure you chime in with your favorite new features being updated this season.
The new Quick Deploy feature will offer a noticeable improvement in deployment time, especially for large organizations. Quick Deploy will allow for Apex test execution to be skipped during deployment, as long as the change set was recently validated. This change makes a lot of sense. Currently, all Apex tests are run twice (once during validation and again during deployment), which is redundant and, in my opinion, not necessary. With Quick Deploy, the tests are run during the validation step, and then, assuming everything passes, the deployment step can be completed much faster. Faster deployment means Salesforce Administrators spend less time waiting for a deploy to complete and more time working on other tasks.
This new addition eliminates the need to save callout URLs and credentials in Apex code. Instead, you can now create a named credential in the Salesforce settings, complete with the URL endpoint and authentication details. This means that URLs are no longer hard-coded and can be easily changed in one place. It also greatly simplifies OAuth and other authentication methods for callouts because they do not need to be handled in the code.
Prior to spring ‘15, Salesforce only allowed one callback URL (also known as the redirect_uri) following OAuth authentication. The addition of multiple callback URLs means more flexibility and control for app developers. Apps can now redirect users to various URLs, which allows for more complex callback handling.
Modern websites increasingly use asynchronous processing to handle background tasks and retrieve data from external Web services. This new improvement will allow developers to utilize asynchronous callouts on Visualforce pages. This is a great addition which will lead to more dynamic and interactive Visualforce pages. As an added bonus, these callouts don’t count towards the Apex limit of 10 synchronous requests, so developers will have a lot more flexibility to interact with external services.
Ashley already commented on this feature in her blog post earlier in the week, but I’m also excited about the change and felt it was worth mentioning twice. I’m particularly happy about the ability to search for custom objects, which means no more scrolling through a long list of objects to find the one I’m looking for. I’m hoping that the Advanced Setup Search will continue to expand in what it can find, and, in particular, I would love the ability to search for Apex Classes and Visualforce Pages.
We’ve now covered many of the upcoming Salesforce Spring ‘15 changes, but the list of other noteworthy features is long. What are some of your favorites? Tell us which ones we’ve missed that you think are especially important.