Picture this… it’s already 9pm on deployment night (Friday night of course). You’ve pushed to three environments already and spent at least three hours resolving unit test failures. If all your tests pass this time, you can go home and enjoy a well deserved hot cocoa….
THEN THIS HAPPENS:
Someone else deployed a Validation Rule that is causing almost half your unit tests to fail, effectively ruining your weekend and destroying all your dreams. Has this ever happened to you? Well you’re not alone…
If you work on the clicks side of the force and you haven’t heard of Custom Settings and the cool things you can do with them using declarative functionality then this is the blog post for you! There are also many other great blog posts for you out there and a few Dreamforce sessions as well. Why should you keep reading this particular blog post and not crawl off down the internet rabbit hole I just dug for you? Because I’m going to explain what Custom Settings are and then document three examples of how you can use them with clicks not code, but more importantly, my examples are kind of funny… I hope.
What are Custom Settings?
Custom Settings, like Custom Objects., have custom fields that allow you to create records that contain data. However, unlike Custom Objects, Custom Settings can be accessed in any formula, workflow rule, and process builder organization-wide. Custom Settings are indeed settings for your org or application!