Salesforce is an extremely flexible and powerful platform that works for many different implementations. Its power comes from the degree of configuration that it provides, out-of-the-box.

Taking off from our previous post, configuration allows a user to personalize aspects of the system without having to depend on an experienced programmer. With customization, you need bespoke programming done by an experienced programmer.

With Salesforce, there’s a huge range of things that can be done with just configuration. Starting from adding a few simple custom fields to let’s say an Account or Contact object in Salesforce to configuring complex workflows to automate tasks to managing security and data access through profiles and roles – all of these are possible with just configuration. All with a point-and-click interface, without needing to know any programming. The key is for the user (generally the Salesforce Administrator) to understand the business processes of the organization and to have a clear understanding of objects and how they relate to each other. Configuration is a fast, intuitive and relatively simple way to tailor Salesforce to work exactly the way that your organization needs it to work.

The individual making the changes needs to be business-focused, not code-focused. With no dependence on understanding coding or dependence on syntax of a programming language, a person who understands the business is empowered to completely configure the powerful Salesforce platform to the organization’s exact requirements. And with the vast Salesforce ecosystem, you have an almost unlimited amount of tutorials, knowledge bases, forums, videos and documentation to help you in your configuration quest. Configuration is several orders of magnitude less problematic to deal with than customization. But you really need to understand what you are trying to configure and to understand the complexities of the platform, before you attempt making changes to the system. Fortunately, Salesforce gives you the additional comfort of a “sandbox” system where you can make all your configuration changes and test it out before deploying the changes to your production environment.

As an example, let’s consider Salesforce’s Process Builder.

Process Builder.

One of Salesforce’s most powerful tools is the Process Builder. The Process Builder is a relatively easy-to-use, visual business process automation tool that can trigger a wide variety of automatic tasks or actions. Process Builder takes the work out of repetitive tasks by automating them and streamlining them. Process Builder has a simple user interface, but is powerful enough to send out emails or update fields or for activities to automatically occur based upon preset triggers. The vast majority of automatic tasks can be automated using this simple point-and-click mechanism.

So the crucial question to ask yourself as you start to setup Salesforce for your organization is how deeply you need to modify Salesforce to serve your specific requirements. Break your business process down into various options. See how much of that can be met with configuration. Only after you exhaust all avenues for configuration, should you even consider the possibility of customization.

Some Process Builder examples.

You could use process builder to send out automatic email to a manager when the value of an opportunity value is greater than a preset amount. You could set up an email alert to be sent to a service manager if a Case is not responded to in a specified time-frame. In using dftly Time Tracker, we have customers who set up an automated rule to pre-populate Account related information such as Address to custom fields on the dftly Projects object, when an Opportunity Stage changes to Closed Won.

The bottom line is that with all the configuration tools at your disposal with Salesforce, you really should be able to fit between 70 – 80% of your requirements with configuration. Consider customization only for the remainder of your requirements.

Next week, we’ll talk about how we build on top of the Salesforce configuration to add configurability to the dftly Time Tracker.

As a society we are increasingly using online or cloud-based software in everything from buying clothes to managing our bank accounts. As you look around for cloud software for your organization’s needs, you’re quite likely to hear the terms “configurable” and “customizable” being thrown around, sometimes interchangeably. It’s critical that we understand the difference between these two terms.

A configurable system is an out-of-the-box solution that allows a user to personalize some aspects of the system themselves, without having to depend on experienced programmers. Configurable software is generally flexible and scalable and can be shaped to meet an organization’s requirements. While the system comes with a default configuration that works out-of-the-box, it generally lets you tweak the system with simple drop-down menus and lists to more closely reflect your own business. Configurable software gives you the advantage of best practices from the industry and other organizations. But overall, may not fit your requirements exactly. Since you can do the configuration on your own, there is generally no additional fee that you need to pay.

Customizable software, on the other hand, requires bespoke programming, generally done by the software company’s technical team or by a partner. With customized software, you get software that fits your requirements exactly. But because you are getting it specifically developed for you, the software itself does not evolve with usage from multiple companies. Whenever you need changes, those changes need to be specifically made for you and therefore will be both time-consuming and expensive.

The best example of configuration vs. customization is that of clothes. You could get a shirt custom stitched to your exact size OR you could buy a shirt at a store. The custom stitched shirt is the equivalent of customized software, whereas buying a ready-to-wear shirt in a store is the equivalent of configured software. You can “configure” the shirt in the store by choosing your specific collar size, sleeve length from the variations available in the store. The custom shirt is specifically tailored for each of your lengths and sizes, but takes longer to make and may not have all the bells and whistles that come with the factory-made shirt. In software terms, we would say that the “configured” shirt has all the best practices from the industry.

Coming back to software, configurable software allows for users to re-arrange key elements of the software to suit their own business requirements, without programming changes. While customized software that works exactly to your specifications is alluring, the overall cost and time involved is generally prohibitive.

Like with most things, the 80-20 rule holds true for software implementations too. Check to see if out-of-the-box solution fits 80% of your requirements. If it does, you should be able to get the remaining 20% of the functionality through configurations, eliminating customization completely.

This post is the first in a 3-part series on software configuration. Next week, we’ll talk about how configuration makes Salesforce so powerful that it has become the platform of choice for many different implementations. The following week, as an example, we’ll look at how configuration works with dftly Time Tracker.