Summer ’13 Second Look

The release notes are out for Summer ’13 and they are amazing. There are so many changes that  it is going to take me a few blog posts to make it through all the ones I want to talk about. Go read them yourself, but don’t download them and think you’ve got them. These are a living document until the release happens, so always download the latest version each time you want to look at them.

This release really feels like they’ve addressed many items core to CRM. There are still a lot of bells and whistles too that will be cool, but I’m most excited about core enhancements. This blog post will focus on those.

Customizable Price Books Price Books are becoming a first class object! You can add custom fields, modify page layouts, define Apex triggers, and more.

Record Types in Permission Sets Permissions Sets have been awesome additions to Salesforce and this new improvement really makes them even more functional. There’s a lot of details in the release notes about how this works.

Owner Fields in Custom FormulasYes, I mentioned this one in my last post. Can you tell how happy I am to have this feature? In the past you had to use triggers to get at Owner fields. We are now in button-click land! There are so many uses for this, I’m sure it could be its own blog post.

Checkbox Formulas Sometimes little improvements like this one make me so happy. I’ve always hated creating formula fields that you want to be a simple checkbox and instead have to have the output be test like YES or NO. Now there is a new formula type that results in a checkbox.

checkbox formulas

Custom Settings Copied to All Sandboxes I’m not sure how I feel about this. I think I like that custom settings will be copied to all sandbox types now including developer ones. In the past, custom settings were like data and not copied over. This could be a “gotcha” if you are storing endpoints for callouts in your custom settings and they point to production.

DML Before Mock Callouts Best practice when testing is to insert your test own test data rather than relying on data already existing in the org. The problem until now has been that you would receive an error when testing callouts. They’ve fixed this!

TestVisible Annotation This little improvement is going to help greatly with writing unit tests. Before this release, classes with private methods were kind of a black box and you couldn’t get down to the individual components to test them. Well, now with the TestVisible annotation, you can mark private methods, inner classes and more as visible to tests, so you can write your tests more easily.

Approval Processes in Change Sets and Metadata API Ever spent a painstaking amount of time creating an amazing approval process in your sandbox and then realized you can’t deploy it to production? Now that the Metadata API supports approval processes, you can actually deploy them to production.

3 thoughts on “Summer ’13 Second Look”

  1. Good point about endpoints in Custom Settings being copied to Sandboxes. I work with a number of managed packages that use custom settings to store record IDs or record type IDs. Once our sandboxes refresh for preview/testing we’ll have to see what happens there carefully.

Leave a Reply